You are probably running eclipse on the JRE rather than the JDK. Ensure when
you configure JBoss 4 in JBoss IDE that you set the JDK correctly.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854524#3854524
Reply to the post :
http://www.jboss.org/index.htm
Its a bug in JDK 1.4.2_xx
Javasoft bug 4880633
The class XMLEncoder, which is meant to be threadsafe, uses the class
java.beans.Statement which is also meant to be threadsafe, but isn't as it uses
HashMap.
Must say, once we managed to get a coredump in the right format to HP, they found the
Hi all. I actually like talking to myself ;)
I guess noone else is daft enough to run JBoss on HP-UX. Well, we are finally all
patched up on the HP-UX front, and, yes, still the JVM locks up at irregular intervals
hours/days.
Is there anybody else out there who is daft enough to be attempti
Don't do it.Are you mad ?:)
I would watch out for the JVM on HP-UX locking up and even refusing to respond to
"kill -3" to get a thread dump.
We have been chasing this issue with HP for weeks now. Try this patch, try that
patch, but it still locks up at random intervals from a few h
Well, we installed the latest pthreads patch PHCO_30544, but the process still hangs...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848638#3848638
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848638
-
Well, removing the clustering made no difference. Kill -3 produced no thread dump.
The JVM is well and truely locks up and chews 100% of a CPU.
Have gone back to HPUX patches.Seems we don't have some critical patches for
running Java reliably on HPUX. What I don't understand is why HP d
Its true that in general you will see better performance on WinTel than LinTel.
However, the differences are not as dramatic as the comparison of JBoss start-up times
would suggest.
WinTel especially, non-server based, when not running JBoss as a service, will give
the JVM every ounce of CPU
JBoss 3.2.3 on HPUX 11 (dual CPU) on JDK 1.4.2_00
We have today seen two servers stop. Logging stops, everything stops and the CPU sits
at 100% i.e. all of one processor. The application is very vanilla. There are no
loops. Just plain JBoss.Net to SSB. We did have clustering enabled but
You almost got it right.
But you must reference the container configuration from your ejb in the jboss.xml.
|
|
|
|
|
| MyFacadeManager
| MyFacadeManagerLocal
| Hibernate Stateless SessionBean
|
|
|
|
| ...
So JBoss 3.2.6 includes the HARDeployer;
http://www.jboss.org/wiki/Wiki.jsp?page=JBossHibernate
has this slated for inclusion into 4.x and when ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844079#3844079
Reply to the post :
http://www.jboss.org/ind
That worked.
thanks.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824265#3824265";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824265>Reply
to the post
---
This SF.Net email is spon
Yes. I guess you have both the SAR and EJB inside the same EAR file. The MBean in
the SAR willl be started before the EAR deployment is complete. Until the EAR
deployment is complete, the EJB will not be found in the JNDI tree.
One way around this, crusty but works, is to change your mbean
Have a problem trying to use different versions of an EJB.
Have successfully deployed two EAR files, manager-v1.ear and manager-v2.ear, each
containing an EJB Jar with an EJB named "Manager" with the same named remote and home
interfaces. The two EJBs bind to JNDI under the names ejb/Manager
13 matches
Mail list logo
