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 (Created) (JIRA)" <ji...@apache.org> on 2011/12/07 13:52:40 UTC
[jira] [Created] (APLO-104) Internal Server Error with latest
snapshot
Internal Server Error with latest snapshot
------------------------------------------
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
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
[jira] [Commented] (APLO-104) Internal Server Error log message
does not provide enough information
Posted by "Lionel Cons (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (APLO-104) Internal Server Error with latest
snapshot
Posted by "Stan Lewis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164668#comment-13164668 ]
Stan Lewis commented on APLO-104:
---------------------------------
Hi Lionel, did you try turning up the logging to debug? Looking at the logging code the next line should have the exception message, if you turn up the logging to DEBUG then the whole exception stack trace should be printed.
> Internal Server Error with latest snapshot
> ------------------------------------------
>
> 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
>
> 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
[jira] [Updated] (APLO-104) Internal Server Error log message does
not provide enough information
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-104:
-------------------------------
Assignee: Hiram Chirino
Summary: Internal Server Error log message does not provide enough information (was: Internal Server Error with latest snapshot)
> 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
>
> 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
[jira] [Commented] (APLO-104) Internal Server Error log message
does not provide enough information
Posted by "Hiram Chirino (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165216#comment-13165216 ]
Hiram Chirino commented on APLO-104:
------------------------------------
I created APLO-106 to track the reply-to issue.
> 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
[jira] [Commented] (APLO-104) Internal Server Error with latest
snapshot
Posted by "Lionel Cons (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165052#comment-13165052 ]
Lionel Cons commented on APLO-104:
----------------------------------
Stan,
I double checked and I'm using the default log4j.properties. 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 (https://issues.apache.org/jira/browse/AMQ-3496) 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 seems...
> Internal Server Error with latest snapshot
> ------------------------------------------
>
> 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
>
> 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
[jira] [Issue Comment Edited] (APLO-104) Internal Server Error with
latest snapshot
Posted by "Lionel Cons (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165052#comment-13165052 ]
Lionel Cons edited comment on APLO-104 at 12/8/11 7:06 AM:
-----------------------------------------------------------
Stan,
I double checked and I'm using the default log4j.properties. 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 (https://issues.apache.org/jira/browse/AMQ-3496) 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 seems...
was (Author: lionel.cons):
Stan,
I double checked and I'm using the default log4j.properties. 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 (https://issues.apache.org/jira/browse/AMQ-3496) 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 seems...
> Internal Server Error with latest snapshot
> ------------------------------------------
>
> 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
>
> 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
[jira] [Resolved] (APLO-104) Internal Server Error log message does
not provide enough information
Posted by "Hiram Chirino (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved APLO-104.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0-beta6
I've updated the logging so that the Internal Server Error log lines provide more information about the error.
I've also updated the regex that validate destination names so that you can use destinations with spaces in them.
> 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
[jira] [Commented] (APLO-104) Internal Server Error log message
does not provide enough information
Posted by "Hiram Chirino (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165189#comment-13165189 ]
Hiram Chirino commented on APLO-104:
------------------------------------
Right now the only reason we parse the reply-to header is to translate /temp-queue/xxx style destination names to actual destination names. So, if it's not a temp destination we should avoid generating the error.
> 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