You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jeff Ward (JIRA)" <ji...@apache.org> on 2008/10/02 17:52:53 UTC
[jira] Created: (AMQ-1963) The JmsFrameTranslator for stomp outputs
"is null" to the console on every recieved message
The JmsFrameTranslator for stomp outputs "is null" to the console on every recieved message
-------------------------------------------------------------------------------------------
Key: AMQ-1963
URL: https://issues.apache.org/activemq/browse/AMQ-1963
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.2.0, 5.1.0
Reporter: Jeff Ward
JmsFrameTranslator.java has a console write line to output "is null" whenever it creates a new xstream object. This can occur on every frame and can clutter log files. Either it needs to be changed to a log4j call or it needs to be removed entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1963) The JmsFrameTranslator for stomp
outputs "is null" to the console on every recieved message
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-1963.
--------------------------------
Assignee: Dejan Bosanac
Fix Version/s: 5.3.0
Resolution: Fixed
Fixed in SVN revision 701333
> The JmsFrameTranslator for stomp outputs "is null" to the console on every recieved message
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-1963
> URL: https://issues.apache.org/activemq/browse/AMQ-1963
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.1.0, 5.2.0
> Reporter: Jeff Ward
> Assignee: Dejan Bosanac
> Fix For: 5.3.0
>
>
> JmsFrameTranslator.java has a console write line to output "is null" whenever it creates a new xstream object. This can occur on every frame and can clutter log files. Either it needs to be changed to a log4j call or it needs to be removed entirely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.