I know that the topic connection is open at the time
createTopicSession is called? but do I need to start it first??
Any help is very useful.
Rob
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManag
er.java:121)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.jav
a:503)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.ja
va:272)
at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:26
1)
at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.ja
va:238)
at com.db.gmr.core.jms.Publisher.init(Publisher.java:269)
at com.db.gmr.eds.util.JMSBridge.init(JMSBridge.java:249)
at com.db.gmr.eds.service.BridgeApp.run(BridgeApp.java:37)
at java.lang.Thread.run(Thread.java:484)
Do you have a small test program that reproduces this?
_sjz.
"Rob Hayes" <robert...@db.com> wrote in message
news:fcd31e2f.01081...@posting.google.com...
I seem to have isolated down the problem, don't totally understand it
and can't find much information on what's happening but I'll try and
explain.
I basically have an application that needs to connect to two different
JMS servers (one in London and one in New York).
My application subscribes to a number of topics on New York (this
works fine), then I initialse the connection by getting the topic
connection factory, creating the topic connection, creating a session
etc.. and do everything except call start.
Then I set-up publications for a number of topics on London, but when
I run initialise (which creates completely seperate connections from
the above and using a different JNDI server), I get the Connection not
Found exception when I try to use a method on the Topic connection.
does anyone know if Weblogicc 6.1 JMS supports connecting to two
different JMS servers?
"Zach" <za...@nospam.com> wrote in message news:<3b7bfea9$1...@newsgroups.bea.com>...
JMS sees that it is already talking to "myserver" and replaces
the stub with the stub of the first "myserver" it was talking to.
So you do get a connection to the second instance of "myserver"
but then we replace the remote stub and any subsequent calls
are all going to the first instance of "myserver".
Could you please check what the server names are for your
London and New York. If they are the same, change the
configuration to make them unique and the problem should
go away.
This has been entered as CR055031 in our database and it
will be addressed in a future release. For now, make sure
your server names are unique.
_sjz.
"Rob Hayes" <robert...@db.com> wrote in message
news:fcd31e2f.01081...@posting.google.com...
You are my knight in shinning armour, I've changed my server names to
be unique and hey presto my application is now functioning perfectly.
Thanks for all you help over the last week.
Rob