Can't listen on existing JBoss JMS topic
----------------------------------------
Key: SYNAPSE-66
URL: https://issues.apache.org/jira/browse/SYNAPSE-66
Project: Synapse
Issue Type: Bug
Components: Core
Affects Versions: 0.91
Reporter: Gerald Loeffler
following sample 110 i'm trying to listen to a pre-defined JMS topic hosted by
a JBoss application server instance. Synapse can connect to JBoss JNDI
allright, and it seems to lookup the JMS ConnectionFactory (as specified in
axis2.xml), but instead of looking up an existing destination (topic) (as
specified in synapse.xml) to listen to, it seems to try to create a new queue.
the error i'm getting:
--------------------------------------------
[SynapseHTTPServer] Started HTTP on port : 8080 INFO [12 Mar 13:15:19]
DefaultConnectionListener - Listening on port 8080
DEBUG [12 Mar 13:15:19] DefaultConnectionListener - Waiting for incoming HTTP
connection
DEBUG [12 Mar 13:15:19] JMSConnectionFactory - Connected to the actual
connection factory : UIL2ConnectionFactory
INFO [12 Mar 13:15:20] JMSListener - JMS Transport Receiver (Listener)
initialized...
DEBUG [12 Mar 13:15:20] JMSConnectionFactory - Connection factory : default
initializing...
WARN [12 Mar 13:15:20] JMSConnectionFactory - Cannot find destination :
synapse Creating a Queue with this name
ERROR [12 Mar 13:15:20] JMSListener - Error starting connection factory :
default
javax.jms.JMSException: This destination does not exist !QUEUE.synapse
at
org.jboss.mq.server.JMSDestinationManager.createQueue(JMSDestinationManager.java:613)
at
org.jboss.mq.server.JMSServerInterceptorSupport.createQueue(JMSServerInterceptorSupport.java:111)
at
org.jboss.mq.server.TracingInterceptor.createQueue(TracingInterceptor.java:259)
at
org.jboss.mq.server.JMSServerInvoker.createQueue(JMSServerInvoker.java:117)
at
org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:136)
at
org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
--------------------------------------------
synapse.xml:
--------------------------------------------
<proxies>
<proxy name="StockQuoteProxy" transports="jms">
<property name="transport.jms.Destination" value="topic/MY_TOPIC"/>
<wsdl key="proxy_wsdl"/>
</proxy>
</proxies>
--------------------------------------------
axis2.xml:
--------------------------------------------
<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="default" locked="false">
<parameter name="java.naming.factory.initial" locked="false">
org.jnp.interfaces.NamingContextFactory
</parameter>
<parameter name="java.naming.provider.url" locked="false">
jnp://localhost:1099
</parameter>
<parameter name="java.naming.factory.url.pkgs" locked="false">
org.jnp.interfaces:org.jboss.naming
</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">
UIL2ConnectionFactory
</parameter>
</parameter>
</transportReceiver>
--------------------------------------------
Asankha C. Perera commented as follows:
--------------------------------------------
The cause of this issue is that it we for a Destination with a JNDI name
of "synapse" to map into the special Axis2 service named "synapse" that
we use internally. This is a defect from our part as this is not a
service we want to target to the JMS transport when its enabled. As we
use ActiveMQ for testing, we do not get this exception - since ActiveMQ
creates any destination on demand. Could you file a JIRA for this? I
will fix this ASAP.
--------------------------------------------
--
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]
