Yes. I started the connection.
Actually I am using the same code to connect to a topic. Everything runs OK. For the durable subscriber, I just look up another destination.
if (client.isDurable()) {
| String clientName = getClientName();
| LOG.info("Creating durable subscriber (" + clientName + ") to: " + dest.toString());
| jmsConsumer = getSession().createDurableSubscriber((Topic) dest, clientName);
| } else {
| LOG.info("Creating non-durable consumer to: " + dest.toString());
| jmsConsumer = getSession().createConsumer(dest);
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165112#4165112
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165112
This is what I would do:
1) Create a *-ds.xml file in a temporary location (anywhere other than server/xxx/deploy).
2) Either copy that file to server/xxx/deploy or, better yet, use the deploy operation on the MainDeployer MBean to deploy the *-ds.xml file.
3) When I am done with the data source, I would remove the *-ds.xml file from the deploy directory (or call the undeploy operation on MainDeployer if that is how I deployed it)
I hope you don't expect to get any kind of decent performance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165108#4165108
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165108
Hmm, this post gives no hint as to what version of JBossAS this is. Nor the JDK version. Nor the operating system. Nor does the post indicate if JBossAS is being started clean (no additional apps deployed) or if other apps were deployed before staring the app server.
On top of that, the error message is coming from a class (com.proximities.common.cache.BaseCacheManager) that is not even part of JBossAS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165107#4165107
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165107