Is there something I can do to solve this problem, or is
this a bug? Any suggestion is welcome. Thx.


Below are the specific code snippets I used in the client
app:

- for the connection:
properties.put
(Context.INITIAL_CONTEXT_FACTORY, "org.exolab.jms.
jndi.rmi.RmiJndiInitialContextFactory");
properties.put
(Context.PROVIDER_URL, "rmi://10.50.34.29:1099/");
...
TopicConnectionFactory factory =
(TopicConnectionFactory) context.lookup
("JmsTopicConnectionFactory");

- I used a seperate sessions for sending and receiving
(spawn from the same connection).

//for sending
topicsession =
connection.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
...
publisher.publish(topic, jms_message,
DeliveryMode.NON_PERSISTENT, 4, 0);


//for receiving
topicsession_2 =
connection.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
...
topic = (Topic)context.lookup(topic_name);


- OPENJMS version: openjms-0.7.6.1


----------------------------------------------------------------------
Date: 2005-09-19 08:36

Message:
Logged In: YES
user_id=1335539

Yep, using the tcp connector did the job perfectly! The only
difference is that it takes a view seconds 'to connect' to the
topic for the very first time.

Thank's a lot!



----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)
Date: 2005-08-29 14:14

Message:
Logged In: YES
user_id=557161

You may need to use the tcp connector in order for this to work
properly. It provides support for NAT firewalls/multihomed hosts.
See the configuration reference
($OPENJMS_HOME/docs/config/reference.html#TcpConfiguratio
n) for more details.

Also note that you should be
using "org.exolab.jms.jndi.InitialContextFactory" instead
of "org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory" - the
latter doesn't exist beyond version 0.7.6.x.



----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1273923&group_id=54559