This:
anonymous wrote : Needed to change:
| import javax.ejb.Interceptors;
| into:
| import javax.interceptor.Interceptors;
clearly shows that you are not running a good seam/jboss AS combination.
The starting guide states that you need JBoss 1.0.1.GA with the EJB3 profile of JBoss Jems installer
The "necessary Jars" are shipped (for compilation) with JBoss Seam (under the name jboss-ejb3-all.jar)
Finally it seems that you are now running your own example created with the Hibernate tools, you could show us the Java source file so we can help you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965965#3965965
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965965
Timfox,
I am sorry. I was not able to reproduce it. I dont know what caused the problem but must be some error on my part.
Is is possible to view from the some console the durable subsriber information. I am guessing that I had more created some more durable subsribers because of which the messages were not removed from the database. Thanks for your quick replies. I really appreciate your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965964#3965964
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965964
Correction: These props is diffrent from the replAsync-service.xml from the dist:
| <!--
| <attribute name="UseReplQueue">true</attribute>
| <attribute name="ReplQueueInterval">100</attribute>
| <attribute name="ReplQueueMaxElements">1</attribute>
| <attribute name="UseRegionBasedMarshalling">true</attribute>
| <attribute name="InactiveOnStartup">true</attribute>
|
|
And loopback is set to true in JGroups UDP-config.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965963#3965963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965963
How can I force an MBean to be unregistered on undeploy?
I use Spring to manage my beans and it exports one of my beans as a MBean when the application is loaded. When I redeploy my application the MBean server throws an InstanceAlreadyExistsException because my MBean from the previous deployment is still alive while Spring is trying to inject a new one..
Anyone knows a work-a-round?
cheers,
Geir
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965960#3965960
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965960