Sending to a remote JMS queue - [ConnectionAspect] Caught ex

[bport]

Hello.

I realize this may be a JBoss Remoting issue, please tell me if it is, but I decided to post here because it may be an issue with the config for JBoss Messaging (the lines get blurry).

I have just upgraded my jboss-4.0.4.GA installations with jboss-messaging-1.0.1.CR4. I have used the default installation configuration - with one caveat - I had to remove the jboss-aop.jar file from the SAR, as I was getting ClassCast exceptions, since I already had jboss-aop from the ejb3 install.

My scenario is this: I send a message to a queue on a remote server that is configured as above. (The client is an app running from within JBoss). The message is received, and everything appears to be sucessful. A few seconds later, I receive the following message in the server.log:

ERROR [ConnectionAspect] Caught exception from connection
java.lang.NullPointerException
at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:1
14)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

My remoting-server.xml is the default:

<server>

 <mbean code="org.jboss.remoting.transport.Connector"
 name="jboss.messaging:service=Connector,transport=socket"
 display-name="Socket transport Connector">
 <attribute name="Configuration">
 <config>
 <invoker transport="socket">
 <attribute name="marshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
 <attribute name="unmarshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
 <attribute name="serializationtype" isParam="true">jboss</attribute>
 <attribute name="dataType" isParam="true">jms</attribute>
 <attribute name="socket.check_connection" isParam="true">false</attribute>
 <attribute name="timeout">0</attribute>
 <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
 <attribute name="serverBindPort">4457</attribute>
 <attribute name="leasePeriod">20000</attribute>
 </invoker>
 <handlers>
 <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
 </handlers>
 </config>
 </attribute>
 <depends>jboss.messaging:service=NetworkRegistry</depends>
 </mbean>

 <!-- TODO: Do I need this> -->
 <mbean code="org.jboss.remoting.network.NetworkRegistry"
 name="jboss.messaging:service=NetworkRegistry"/>

</server>

and the code making the call looks like:

QueueConnection cnn = null;
 try {
 cnn = remoteFactory.createQueueConnection();
 QueueSession remoteSess =
 cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
 QueueSender remoteSender = remoteSess.createSender(remoteQueue);
 ObjectMessage obj = remoteSess.createObjectMessage();
 obj.setObject(theLog);
 remoteSender.send(obj);
 }
 finally {
 if (cnn != null) {
 cnn.close();
 }
 }

- where remoteFactory has been looked up from an InitialContext with an environment pointing it to the remote server.


Thanks for any help!

-brad

[bport]

Please disregard.

I had an exceptionListener set on the connection that was causing the issue.

THanks.
-brad

[fastmhaavald]

Hi,

Just a question:

Do you have example code using this config?


I have a similar issue, but in my case some beans need to send to a remote queue and others to a local queue.

I guess I have to configure two JMS Providers for this.

Have you tried this?

[timfox]

This may be of help:

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingUser_Enabling_access_to_remote_JBoss_Messaging_instance

[gsoing]

Hello,

I have the same problematic : need to send messages on a remote queue and others on a local queue. I tried a lot of things but I can't connect to the remote queue.

Can you give me which configuration applied on my local server and on my remote server ?

Thanks in advance !

Delphine

[timfox]

In the distro there is a file call jms-ds.xml.

This contains all the configuration for a *local* jms provider.

If you use the JCA resource adaptor at java:/JmsXA then you will be talking to the local JMS provider (via a resource adaptor).

You can create another one of these files (or you can put in the same file - it doesn't matter) with all the information corresponding to your remote JMS provider.

Make sure you give the tx-connection-factory a name different to your local one!

Then when you use your java:/MyRemoteJMSXA or whatever you have called it, you will be talking to your remote provider.

The above method is recommended if you want to take advantage of the transaction enlistment, security propagation features of the JCA adaptor.

Alternatively you can just create your own InitialContext with a map of JNDI properties corresponding to the remote provider as per standard JNDI. But then you won't get automatic transaction enlistment, in EJBs for example.

There are lots of wiki pages that cover this.

[gsoing]

I tried this but it doesn't work.

I tried the solution on the HowDoIConfigureAnMDBToTalkToARemoteQueue wiki page. It doesn't work.

I tried the solution on the topic http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074717#4074717. The same : it doesn't work.

I really tried a lot of things...

Is there a wiki that explains step by step the configuration for both servers ?

Thanks.

Delphine