activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (Commented) (JIRA)" <>
Subject [jira] [Commented] (APLO-104) Internal Server Error with latest snapshot
Date Thu, 08 Dec 2011 07:05:41 GMT


Lionel Cons commented on APLO-104:


I double checked and I'm using the default I have the feeling that a broker
should be able to give meaningful error messages without
enabling debugging. A production broker would have debugging disabled but, in case of error,
you still want to understand what is going on. Don't you
think so?

Independently from this point (enough information in the error messages or not), I've enabled
debugging and I could see what caused this error. I got:

2011-12-08 07:50:29,143 | DEBUG | org.apache.activemq.apollo.stomp.StompProtocolHandler$ProtocolException:
Invalid stomp destiantion name: some destination | org.apache.activemq.apollo.stomp.StompProtocolHandler
| hawtdispatch-DEFAULT-1

Indeed, I had in my message "reply-to:some destination". Interestingly, this was working previously
in Apollo and not ActiveMQ. I reported this as a bug
against ActiveMQ ( and now it works in ActiveMQ
and not Apollo! Shall I open a separate APLO bug for it?

Finally, there is a typo (destiantion instead of destination), 4 occurrences in the code it
> Internal Server Error with latest snapshot
> ------------------------------------------
>                 Key: APLO-104
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: Apollo 1.0-20111207.032904-215
>            Reporter: Lionel Cons
> 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 '/' error: Internal Server
> 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:!default.jspa
For more information on JIRA, see:


View raw message