You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Stan Lewis (Commented) (JIRA)" <ji...@apache.org> on 2011/12/07 21:16:40 UTC
[jira] [Commented] (APLO-104) Internal Server Error with latest
snapshot
[ 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