Nabble - SwiftMQ JMS Forum

Re: How to specify an ip address for router using if the server has 2 network cards?

2009-11-21T02:38:15Z

The best is to create a new JMS listener on a dedicated port and use the "bindaddress" attribute to bind it to the network card you want to use. Look here (Element "listeners").

How to specify an ip address for router using if the server has 2 network cards?

2009-11-20T20:58:04Z

Here is my situation:
My server has 2 network cards with different ip address and domain. There is only one ip address that I can access from my PC.
After starting the router, I cannot create a connect with my JMS Client and get the exception as follows. The ip address it shows is not the one that I can access. Can I specify the another one for my client?
Thanks.

javax.jms.JMSException: error creating socket connection to 10.100.100.238:4001,
message: Connection timed out: connect
at com.swiftmq.jms.ConnectionFactoryImpl.createQueueConnection(Connectio
nFactoryImpl.java:82)
at com.swiftmq.jms.ConnectionFactoryImpl.createQueueConnection(Connectio
nFactoryImpl.java:52)
at SimpleSender.main(SimpleSender.java:34)

Re: Monitor Swiftlet

2009-11-20T07:26:22Z

It's explained in the docs.

Monitor Swiftlet

2009-11-20T06:58:07Z

I was looking at the garbage collector interval parameter of the Monitor Swiftlet and noticed it has a default value of [-1]. What does a [-1] indicate? Does this mean that the GC is inactive? Does a [+1] indicate that it is active?

Thanks in advance!

Re: Error when sending large message

2009-11-19T11:36:34Z

Right, and now I see you already said that. Okay I think I'm awake now. Thanks for your help!

Re: Error when sending large message

2009-11-19T11:33:05Z

That's right. The properties are attributes, mostly used in message selectors to pick up the right messages. The data goes into the body.

Re: Error when sending large message

2009-11-19T11:23:46Z

It's been a while since I worked with JMS coding, and I'm no more of an expert than I was back then. But I think I'm waking up now... what you're suggesting is that I shouldn't be using a message property to send a large volume of data? That large volumes of data should go in the message body instead?

Re: Error when sending large message

2009-11-19T11:12:41Z

No since the object you set must be of a primitive or String type. setStringProperty(s) and setObjectProperty(s) are equivalent.

Re: Error when sending large message

2009-11-19T11:01:32Z

I didn't know that. So it looks like I have some fixing to do as well. If I use setObjectProperty instead of setStringProperty will that fix it? Assuming I change the receiver to expect an object property?

Re: Error when sending large message

2009-11-19T10:54:01Z

Paul Clapham wrote:

Yes. My test program sends a message with a string property containing 70,000 characters (plus a couple of other small string properties) and it hangs. If it does the same thing with only 65,000 characters then the message is sent successfully.

Ahh, that explains it. String message properties have a maximum size of 64 KB which is the UTF-8 limit. The body can have unlimited size but not a property. We miss to throw a JMSException if the size is > 64 KB. Will be fixed.

Re: Error when sending large message

2009-11-19T10:34:36Z

Yes. My test program sends a message with a string property containing 70,000 characters (plus a couple of other small string properties) and it hangs. If it does the same thing with only 65,000 characters then the message is sent successfully.

I recently noticed this happening in our production system. Usually our messages aren't that big, but there's nothing to limit their size.

Re: Error when sending large message

2009-11-19T09:10:00Z

So you are now using a 7.5.3 client, sending 1 message of a size <n> and it hangs?

Re: Error when sending large message

2009-11-19T09:04:40Z

Oops, you are right about that. I don't use this test client much, so it was using an old swiftmq.jar. In production we are using SwiftMQ version 7.5.3 and that's what I am connecting to for this test. I put that jar file into my test client and now I'm getting the same behaviour as in production, namely that when I call send(Message) on the MessageProducer, it just hangs. The send method never returns.

Here's what I see in the logs when I ran the test (2 successful messages followed by a failure):

2009-11-19 08:57:58.409/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-19 08:57:59.797/sys$jms/INFORMATION/JMSConnection v750/10.20.230.6:3301/receiving disconnect request, scheduling connection close
2009-11-19 08:57:59.799/10.20.230.6:3301/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached
2009-11-19 08:57:59.799/sys$jms/INFORMATION/JMSConnection v750/10.20.230.6:3301/connection closed
2009-11-19 08:57:59.827/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-19 08:57:59.849/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-19 08:57:59.882/sys$jms/INFORMATION/JMSConnection v750/10.20.230.6:3304/receiving disconnect request, scheduling connection close
2009-11-19 08:57:59.883/10.20.230.6:3304/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached
2009-11-19 08:57:59.884/sys$jms/INFORMATION/JMSConnection v750/10.20.230.6:3304/connection closed
2009-11-19 08:58:00.186/10.20.230.6:3303/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached
2009-11-19 08:58:00.197/sys$jms/INFORMATION/JMSConnection v750/10.20.230.6:3303/connection closed
2009-11-19 08:58:10.182/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-19 08:58:59.858/10.20.230.6:3310/BlockingHandler/INFORMATION/Exception, EXITING: java.io.EOFException
2009-11-19 08:58:59.916/sys$jms/INFORMATION/JMSConnection v750/10.20.230.6:3310/connection closed

Re: Error when sending large message

2009-11-19T03:22:22Z

Messages of 126 KB are not considered as large messages. That should work out of the box and without any problems.

But what I see is this:

Paul Clapham wrote:

at com.swiftmq.jms.v400.MessageProducerImpl.processSend(Unknown Source)
at com.swiftmq.jms.v400.MessageProducerImpl.send(Unknown Source)

and here's the SwiftMQ log entries which I believe correspond to the events leading up to the exception:

2009-11-18 13:43:30.126/10.20.230.6:3769/BlockingHandler/INFORMATION/Exception, EXITING: java.net.SocketException: A connection with a remote socket was reset by that socket.

Your client is at release 4.x (v400). That's quite old. You should upgrade it to the version of the router. May be the problem disappears then. Which release do you use router-side?

Error when sending large message

2009-11-18T13:58:31Z

I am having a problem when trying to send large messages via SwiftMQ. In my experiments "large" seems to mean over about 130,000 bytes. I read the information on swiftmq.com about transferring very large messages and it appears to say that SwiftMQ can transfer very large messages with its default configuration, although not in an optimal way. However what happens in my case is that I get an exception thrown. Here's the stack trace:

javax.jms.JMSException: com.swiftmq.tools.requestreply.TransportException: Connection closed
at com.swiftmq.jms.ExceptionConverter.convert(Unknown Source)
at com.swiftmq.jms.v400.MessageProducerImpl.processSend(Unknown Source)
at com.swiftmq.jms.v400.MessageProducerImpl.send(Unknown Source)

and here's the SwiftMQ log entries which I believe correspond to the events leading up to the exception:

2009-11-18 13:43:28.401/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-18 13:43:29.705/sys$jms/INFORMATION/JMSConnection v400/10.20.230.6:3768/receiving disconnect request, scheduling connection close
2009-11-18 13:43:29.707/10.20.230.6:3768/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached
2009-11-18 13:43:29.707/sys$jms/INFORMATION/JMSConnection v400/10.20.230.6:3768/connection closed
2009-11-18 13:43:29.711/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-18 13:43:29.729/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.20.230.6
2009-11-18 13:43:29.743/sys$jms/INFORMATION/JMSConnection v400/10.20.230.6:3770/receiving disconnect request, scheduling connection close
2009-11-18 13:43:29.744/10.20.230.6:3770/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached
2009-11-18 13:43:29.745/sys$jms/INFORMATION/JMSConnection v400/10.20.230.6:3770/connection closed
2009-11-18 13:43:30.126/10.20.230.6:3769/BlockingHandler/INFORMATION/Exception, EXITING: java.net.SocketException: A connection with a remote socket was reset by that socket.
2009-11-18 13:43:30.126/sys$jms/INFORMATION/JMSConnection v400/10.20.230.6:3769/connection closed

I am using basically the default router configuration and I haven't changed it in any of the ways suggested in the "Transferring very large messages" document. Should I be playing with connection factories or should SwiftMQ actually send the large messages in a non-optimal way?

Re: Consumers hang trying to deque messages

2009-11-02T10:20:14Z

There could also be another consumer on that queue locking the messages or the connection has not been started.

Did you check with smart tree disabled as mentioned in a prev post?

Re: Consumers hang trying to deque messages

2009-11-02T09:18:28Z

They show as locked. I have double checked that I am listening on the correct queue.

Also, because they are locked, my understanding is that they are already delivered into a specific consumer's cache, which would indicate that I am listening on the correct queue. Correct?

Re: SwiftMQ 7.5.4 with Spring and com.swiftmq.jms.springsupport.SingleSharedConnectionFactory

2009-10-30T06:34:04Z

Just for clarification: Spring's JMS support is primarily designed to work inside a J2EE container where the container provides connection pooling etc. If you use Spring's JMS support outside a J2EE container - in a normal Spring app - you miss the pooling and it turns sub-optimal. Therefore we provide our springsupport lib which provides the pooling you normally get from the app server.

Re: javax.jms.InvalidDestinationException: Queue is not local! Can't create a XAConsumer on it!

2009-10-30T04:02:57Z

It works !
Thanks a lot.

I made the change :

<jonas-adminobject>
<id>testqueue2</id>
<description>com.swiftmq.jms.QueueImpl</description>
<jndi-name>jms/default/testqueue2</jndi-name>
<jonas-config-property>
<jonas-config-property-name>QueueName</jonas-config-property-name>
<jonas-config-property-value>testqueue2</jonas-config-property-value>
</jonas-config-property>
</jonas-adminobject>

to

<jonas-adminobject>
<id>testqueue2</id>
<description>com.swiftmq.jms.QueueImpl</description>
<jndi-name>jms/default/testqueue2</jndi-name>
<jonas-config-property>
<jonas-config-property-name>QueueName</jonas-config-property-name>
<jonas-config-property-value>testqueue2@router1</jonas-config-property-value>
</jonas-config-property>
</jonas-adminobject>

in jonas-ra.xml as you suggest.

Re: javax.jms.InvalidDestinationException: Queue is not local! Can't create a XAConsumer on it!

2009-10-30T03:51:46Z

These entries must contain the fully qualified queue names such as:

<jonas-config-property-name>QueueName</jonas-config-property-name>
<jonas-config-property-value>testqueue2@router1</jonas-config-property-value>

You must do that for all queues you have defined in jonas-ra.xml.

Re: javax.jms.InvalidDestinationException: Queue is not local! Can't create a XAConsumer on it!

2009-10-30T03:49:24Z

That looks fine. Did you configure your Jonas javax.jms.queue (that one which is returned on your JNDI lookup) with the proper queue name? It must be fully qualified: testqueue2@router1. I do not mean the JNDI name but the queue name property.

Re: javax.jms.InvalidDestinationException: Queue is not local! Can't create a XAConsumer on it!

2009-10-30T03:44:07Z

How can I state the router is local ?

In attachment, the routerconffig of the router.

routerconfig.xml

Re: javax.jms.InvalidDestinationException: Queue is not local! Can't create a XAConsumer on it!

2009-10-30T03:36:11Z

Is testqueue2 defined on your local router or not? The exception states it is not...

javax.jms.InvalidDestinationException: Queue is not local! Can't create a XAConsumer on it!

2009-10-30T03:24:59Z

I have this error when trying to receive a message from a queue inside a J2EE container by a rar connection :

Queue 'testqueue2' is not local! Can't create a XAConsumer on it!

I have a swiftmq router 7.5.3.
My J2EE container is JONAS 4.8.3.
I deploy a swiftmq rar in jonas autoload dir with rar.xml and jonas-ra.xml in attachment.

My client code is in a Session Bean service and is very simple :

Context ctx = new InitialContext();
ConnectionFactory connectionFactory = (ConnectionFactory) ctx.lookup("jms/default/ConnectionFactory");
Destination queue = (Destination) ctx.lookup("jms/default/testqueue2");
Connection connection = connectionFactory.createConnection();
Session session = connection.createSession(true, Session.AUTO_ACKNOWLEDGE);
MessageConsumer consumer = session.createConsumer(queue);
connection.start();
Message message = consumer.receive(100);
session.commit();

When createConsumer method is called, I a this exception :

Caused by: javax.jms.InvalidDestinationException: Queue 'testqueue2' is not local! Can't create a XAConsumer on it!
at com.swiftmq.tools.requestreply.ReplyNE.createException(Unknown Source)
at com.swiftmq.tools.requestreply.ReplyNE.readContent(Unknown Source)
at com.swiftmq.jms.smqp.v750.CreateConsumerReply.readContent(Unknown Source)
at com.swiftmq.tools.dump.Dumpalizer.construct(Unknown Source)
at com.swiftmq.jms.v750.ConnectionImpl.dataAvailable(Unknown Source)
at com.swiftmq.net.client.BlockingConnection.chunkCompleted(Unknown Source)
at com.swiftmq.net.protocol.smqp.SMQPInputHandler.setBytesWritten(Unknown Source)
at com.swiftmq.net.protocol.smqp.SMQPInputHandler.setBytesWritten(Unknown Source)
at com.swiftmq.net.client.BlockingConnection.run(Unknown Source)

Thanks for your help.

ra.xml jonas-ra.xml

Re: SwiftMQ 7.5.4 with Spring and com.swiftmq.jms.springsupport.SingleSharedConnectionFactory

2009-10-30T01:46:05Z

This is wrong. You may not use SingleSharedConnectionFactory nor can you invoke start() in a J2EE environment. As a J2EE component you have nothing to do with pooling etc. That's the responsibility of the app server in conjunction with the resource adapter. You simple create connection/session/producer, send your messages and close everything down. Behind the scene the app server allocates ManagedConnection instances (out of connection pools) and associates it with the connection you have created. Your connection is only a "handle". Have a look at the sample MDB (with send) in the How To.

Re: Consumers hang trying to deque messages

2009-10-30T01:14:52Z

If the messages are in the queue, are they locked or not? May be you're listening on a wrong queue?

If you switch "smart tree" off (under "Router Environment"), save and reboot the router, you can see under JMS Swiftlet/Usage as well as under Queue Manager Swiftlet/Usage on which queue the client has a receiver.

Re: Consumers hang trying to deque messages

2009-10-29T15:48:39Z

They arrive there, I've checked. I see the messages sitting in the physical queue looking in the explorer. This happens no matter what I set the message timout to (-1 all the way up to minutes long).

SwiftMQ 7.5.4 with Spring and com.swiftmq.jms.springsupport.SingleSharedConnectionFactory

2009-10-29T15:40:28Z

We are building a small test-app to evaluate solutions to the problem posted by michaelzilske in http://www.nabble.com/Messages-out-of-sequence-%28jboss-and-swiftmq%29-td12734756.html

Our test-app starts a transaction, sends 5 messages in it and commits. For each message it does the following:
- retrieve a connection from a SingleSharedConnectionFactory and invoke start() on it
- create Session, MessageProducer and Message
- send the message
- close producer, session and connection

The first transaction works fine. The second one gives the following exception when trying to invoke start() on the connection for the first time:

javax.jms.IllegalStateException: This connection is not associated with a ManagedConnection instance!
at com.swiftmq.connector.v15.outbound.ConnectionImpl.start(Unknown Source)
at com.swiftmq.jms.springsupport.SharedJMSConnection.start(Unknown Source)
at de.ivu.jmsxatest.beans.JMSXAFacadeImpl.sendMessageAndCloseConnection(JMSXAFacadeImpl.java:54)
[...]

The setup is as follows:
- Websphere 6.1 with SwiftMQ 7.5.4 (extra-vm via RA)
- JMSXAFacadeImpl is a Spring bean into which an instance of SingleSharedConnectionFactory is injected. We have also tried Spring's SingleConnectionFactory and CachingConnectionFactory. They exhibit the same behaviour.
- Transaction manager is JTA as defined by spring config (<tx:jta-transaction-manager/>)

A test EAR that exhibits the described behaviour is attached jmsxatestEAR.ear (contains source code) If deployed it offers a servlet under /jmsxatestservlet/test. Each call to the servlet corresponds to one transaction, hence you need to call it twice. The EAR uses the JNDI-Names "jms/CF" and "jms/testqueue".

Re: Using SwiftMQ as external JMS Provider with Websphere Application Server 6.1

2009-10-29T14:47:17Z

Actually that was a good piece of advice =) It works as an extra-vm RA. The fact that there was only an inter-vm howto mislead me to think there is only an intra-vm RA.

Re: Using SwiftMQ as external JMS Provider with Websphere Application Server 6.1

2009-10-29T05:37:29Z

Btw, if you try to configure SwiftMQ as a WAS 3rd party JMS provider instead of using our ResourceAdapter, you might ask your questions in a IBM forum as we did not test that because we provide the RA.

Re: Using SwiftMQ as external JMS Provider with Websphere Application Server 6.1

2009-10-29T05:24:24Z

No idea. Should work actually. However, the exception state you're looking up a javax.jms.Topic...

Re: Using SwiftMQ as external JMS Provider with Websphere Application Server 6.1

2009-10-29T04:48:40Z

Thanks for the quick answer! The QueueName is set to "testqueue@router1". Forgot to mention that.

Re: Using SwiftMQ as external JMS Provider with Websphere Application Server 6.1

2009-10-29T04:05:56Z

Seems you did not set the QueueName property of the queue object. Look here, last 3 pictures. QueueName must be set to testqueue@router1.

It's recommend to configure exactly as described in the How To (except intravm vs extravm).

Using SwiftMQ as external JMS Provider with Websphere Application Server 6.1

2009-10-29T03:37:14Z

We are having some problems trying to use SwiftMQ as external JMS Provider with Websphere Application Server 6.1.

We have a test EAR that first retrieves the ConnectionFactory (jms/CF) and then a Destination via JNDI. The JNDI lookup for the destination hangs for a while (presumably the configured timeout) and then we get the following exception:

29.10.09 11:19:06:061 CET] 00000028 Helpers W NMSV0605W: Ein im Kontext "piperomatNode01Cell/nodes/piperomatNode01/servers/server1" gefundenes javax.naming.Reference-Objekt mit dem Namen "jms/testqueue" wurde an den JNDI Naming Manager gesendet. Dabei ist eine Ausnahme eingetreten. Die Referenzdaten folgen:
Klassenname der Referenz-Factory: com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
Positions-URLs der Referenz-Factory-Klasse: <null>
Reference Class Name: javax.jms.Topic
Type: JndiLookupInfo
Content: JndiLookupInfo: jndiName="testqueue@router1"; providerURL="smqp://blo.ivu-ag.com:4001/timeout=10000;debug=true"; initialContextFactory="com.swiftmq.jndi.InitialContextFactoryImpl"
Address Type: IndirectJndiLookupAdditionalProperties
AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...

Die Daten zur Ausnahme folgen:
javax.naming.NameNotFoundException: Name '' not found (timeout occured)!
at com.swiftmq.jndi.v400.ContextImpl.lookup(Unknown Source)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:369)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:893)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:705)
at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:2097)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1951)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1866)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1556)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:149)
at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:144)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191)
at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(javaURLContextRoot.java:407)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1280)
at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:384)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:205)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:145)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at de.ivu.jmsxatest.ejb.JMSXATestBean.ejbCreate(JMSXATestBean.java:45)
[...]

Our config is as follows:
Both swiftmq and WAS run on the same machine, but in different VMs. For swiftmq we are using the vanilla "router1" config. Websphere is configured as follows:

JMS Provider:
External Initial Context Factory = com.swiftmq.jndi.InitialContextFactoryImpl
External Provider URL = smqp://blo.ivu-ag.com:4001/timeout=10000;debug=true

ConnectionFactory:
Type = Unified
JNDI-Name = jms/CF
External JNDI-Name = ConnectionFactory (we also tried plainsocket@router1)

Queue:
Type = QUEUE
JNDI-Name = jms/testqueue
External JNDI-Name = testqueue@router1

Re: Consumers hang trying to deque messages

2009-10-28T22:08:01Z

The problem is certainly not our springsupport if it works with a non-composite queue.

Since composite queues work fine, it seems to be a kind of configuration problem on your side. May be the messages don't arrive at the phys. queue where you listen on. You might check that with Explorer.