Failure to start JMS listener badly reported
--------------------------------------------
Key: AXIS2-3485
URL: https://issues.apache.org/jira/browse/AXIS2-3485
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.3
Environment: JBoss 4.0.5, Windows XP
Reporter: George Marrows
Priority: Minor
1. In ListenerManager.start() exceptions are reported using log.info();
log.error would be more appropriate
2. ClassCastExceptions in JMSConnectionFactory.connect() (and presumably
elsewhere under ListenerManager.start()) are badly reported as eg
14:04:33,633 INFO [ListenerManager]
org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl
They should be better handled by ListenerManager.start(), or perhaps by
exception code in the connect() method.
Background: when deploying a JMS-enabled Axis2 war on JBoss 4.0.5, the line
conFactory = (ConnectionFactory) context.lookup(jndiName);
in JMSConnectionFactory.connect() throws a ClassCastException, which is caused
by javax.jms.ConnectionFactory being loaded twice by different class loaders.
This is easily fixed by removing WEB-INF/lib/geronimo-jms_1.1_spec-1.1.jar,
once the underlying problem has been identified. Unfortunately the combination
of problems 1 and 2 mean that I was only able to see what was going wrong by
stepping through the code.
See also https://issues.apache.org/jira/browse/AXIS2-3377
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
