[EJB/JBoss] - Problem acessing entity bean on the second started node in t
by maralcbr
Hi,
I am having the following problem:
I have a JBoss Cluster with some apps. Some use EJB2 and others EJB3.
There is a specific application that uses entity bmp.
When an entity bean is fist accessed at one node of the cluster, it works fine. But when you access the same bean on the other node of the cluster, the ejbLoad is not called - and although it returns after the findByPrimaryKey is called, all properties remains null (as ejbLoad was not called). I debugged it over and over.
I did dozens of testes already. The problem always happens with the second started node in the cluster. Just the session beans in this app are marked "clustered" on the descriptor. The entities are not marked clustered.
My JBoss server version is 4.2.2GA.
Someone has a hint or some idea on this issue?
Thanks in advance.
Marcelo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145023#4145023
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145023
18 years, 3 months
[JBoss Messaging] - Re: MQ migration help
by clebert.suconic@jboss.com
Here is a list from our build-thirdparty
| <componentref name="retrotranslator" version="0.9.6jboss"/>
| <componentref name="sun-javacc" version="3.2-brew"/>
| <componentref name="oswego-concurrent" version="1.3.4.patch01-brew"/>
| <componentref name="apache-log4j" version="1.2.14-brew"/>
| <componentref name="javassist" version="3.5.0.GA-brew"/>
| <componentref name="jgroups" version="2.4.2.GA_CP01-brew"/>
| <componentref name="trove" version="1.0.2-brew"/>
| <componentref name="jboss/common" version="1.2.1.GA-brew"/>
| <componentref name="jboss/aop" version="1.5.5.GA_CP01-brew"/>
| <componentref name="jboss/remoting" version="2.2.2.SP7-brew"/>
| <componentref name="jboss/jbossts14" version="4.2.3.SP5_CP01-brew"/>
| <componentref name="jbossas/core-libs" version="4.2.0.GA"/>
|
|
As for core-libs, consider whatever is necessary to locate a JNDI.
As for the exception.. I'm not really sure what you're doing.
An easy way would be to use a kill -3, using a Histogram, as I have described here:
http://wiki.jboss.org/wiki/StackTrace
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145021#4145021
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145021
18 years, 3 months