Can I use durable topic to send and receive at the same time

[arabin]

If receiver uses durable subscription to receive messages, and sender is trying to establish connection at the same time (or vice versa), I have an exception:

Exception in thread "main" org.jboss.mq.SpyJMSException: Cannot get a client ID;
- nested throwable: (javax.jms.JMSSecurityException: The login id has an assign
ed client id. That client id is already connected to the server!)
at org.jboss.mq.Connection.askForAnID(Connection.java:866)
at org.jboss.mq.Connection.(Connection.java:242)
at org.jboss.mq.SpyConnection.(SpyConnection.java:49)
at org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnection
Factory.java:97)
at com.teamworks.client.DurableTopicClient.setupPubSub(DurableTopicClien
t.java:57)
at com.teamworks.client.DurableTopicClient.sendRecvAsync(DurableTopicCli
ent.java:71)
at com.teamworks.client.DurableTopicClient.main(DurableTopicClient.java:
97)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client i
d. That client id is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.j
ava:213)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationMan
ager.java:735)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerIn
terceptorSupport.java:273)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.j
ava:618)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:
275)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.
java:325)
at java.lang.Thread.run(Thread.java:536)

Is there a way to use durable subscription so that to send messages from one client and receive them from another one?

[adrian.brock]

A durable subscription is connected to the client id.
The client id can only login once.

You do not need to be logged in as that client to send a message
to the topic.

Regards,
Adrian

[arabin]

Can several subscribers listen to the durable topic at the same time? Could they possibly have separate client ids?

[adrian.brock]

Yes, each gets their own copy of the message.
As opposed to a queue where all receivers compete for the
same messages.

Regards,
Adrian

[arabin]

Can thise ids be created programmatically? (Versus entries in the file jbossmq-state.xml ?

[adrian.brock]

javax.jms.Connection.setClientID()

Have you read the spec?

Regards,
Adrian

[arabin]

I have this, even if I use the same client id, that is inside jbossmq-state.xml file:

javax.jms.IllegalStateException: The connection has already a clientID
at org.jboss.mq.Connection.setClientID(Connection.java:339)
at com.teamworks.client.DurableTopicClient.setupPubSub(DurableTopicClient.java:60)
at com.teamworks.client.DurableTopicClient.sendRecvAsync(DurableTopicClient.java:72)
at com.teamworks.client.DurableTopicClient.main(DurableTopicClient.java:99)
Exception in thread "main" Process terminated with exit code 1

[adrian.brock]

You cannot set the client id on the connection
if it is configured in jbossmq-state.xml

Also, only that user can use that client id.

Regards,
Adrian

[arabin]

Thanks.
It works