disappearing topic

[jgilbert]

i am trying to get messaging 1.3.0 to work with AS 4.2. the first time i deploy everything is fine. when i restart the server my topic disappears.

any idea what is wrong?

note, this only happens when i have deployed an ejb3 mdb that subscribes to the topic.

btw, this mdb has been working with messaging 1.0.1.SP5 and AS 4.0.5 with no problems.

[timfox]

Not sure what you mean by "disappears"?

Does the xml file in which you describe your topic disappear? Or maybe you're saying the topic doesn't deploy even though it's in the xml?

Can you post step by step instructions to replicate?

Thanks.

[jgilbert]

i can start and stop my server with just the topic deployed and everything is fine. every time i restart my topic is still in the jndi tree.

however, as soon as i deploy an ear with an mdb that uses the topic, the topic will disappear from the jndi tree on a restart.

also, when i look in the DefaultDS the post office table does have the subscription for the mdb to the topic.

this same ear worked fine on 4.0.5 with 1.0.1.SP5

my ejb3 mdb does explicitly define all the various metadata like client id, subscription name, etc.. which is different from the example included with messaging.

[timfox]

"jgilbert" wrote:

this same ear worked fine on 4.0.5 with 1.0.1.SP5

The same ear won't work in 1.3.0.

1.0.1 required a scoped deployment, but 1.3.0 does not allow scoped deployments.

[jgilbert]

i'm not sure i follow. if you are talking about the classpath my ear is not scoped. i have not specified a loader-repository in the jboss-app.xml.

[timfox]

I find in situations like this a process of elimination works well.

Have a look at the ejb3 example in the distro. First verify that it works for you.

Then have a look at the differences between that and your application.

Eliminate the differences one by one. At some point it will start working. Then you'll know what the problem is.

My guess is there's probably some incorrect config somewhere.

[timfox]

Also check you're not including messaging-client.jar or any other messaging or remoting jars in your ear.

[jgilbert]

found it!

i have been using dots (.) in my subscriptionNames and clientIds.

MessageQueueNameHelper now relies on dot as a delimiter.

so i removed my dots and all is well.

[timfox]

Ah right.

This was fixed by Sergey today in TRUNK and will be in 1.4.0.CR1 out in a few days.

http://jira.jboss.com/jira/browse/JBMESSAGING-1008