You need to login using a user/password.
The anonymous subscription is only useful
if the connection remains open, which is not true
for a client crash.
The combination of user/subscription will allow
the new client to regain the subscription.
I was. I was using the dynsub user, but looking closer at jbossmq-state.xml I realize now that user doesn't have an ID associated with it. Associating one with it solved the problem. Thanks for the help.
I am a newbie.I have a question about "Odd durable subscription behavior" too.
I have a application as below:
1. An application client that calls an session bean.
2. This session bean publishes several messages to a topic.
3. A message-driven bean that receives and processes the messages,using a durable topic subscriber and a message selector .
Now I can run this program.but this message-driven bean always miss some messages that Published by session bean. I had already config this message-driven bean as a
some times STDOUT looks like this:
invalid console appender config detected, console stream is looping
Can you tell me Why? Thank you very much!!!
Comment:I use Jboss3.0.6 and connectionFactory JNDI is
This is a different problem, please start a new
Sorry,Thank you !