You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (Commented) (JIRA)" <ji...@apache.org> on 2011/12/08 12:56:40 UTC
[jira] [Commented] (APLO-104) Internal Server Error log message
does not provide enough information
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165169#comment-13165169 ]
Lionel Cons commented on APLO-104:
----------------------------------
Thanks for the fix.
However, is it correct to restrict what can be put in the reply-to field (i.e. only a valid Apollo destination)? I've seen nowhere in the JMS spec the mention that the reply-to header must be set to a valid destination on the broker that delivered the message.
We could imagine a reply-to set to "exchangeX@amqp_brokerY" (= send replies to this other broker that speaks AMQP) or "sms:+123456789" (= send me a SMS on this number)...
Of course, clients could use x-reply-to instead of reply-to for these exotic cases.
> Internal Server Error log message does not provide enough information
> ---------------------------------------------------------------------
>
> Key: APLO-104
> URL: https://issues.apache.org/jira/browse/APLO-104
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: Apollo 1.0-20111207.032904-215
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> Fix For: 1.0-beta6
>
>
> Using the latest snapshot, I get:
> apollo.log:
> 2011-12-07 13:47:00,407 | WARN | Internal Server Error | org.apache.activemq.apollo.stomp.StompProtocolHandler | hawtdispatch-DEFAULT-3
> connection.log:
> 2011-12-07 13:47:00,407 STOMP connection '/192.168.0.10:51075' error: Internal Server Error
> Could more information be added to understand what is wrong?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira