[JBoss AOP] - *** java.lang.instrument ASSERTION FAILED ***
by dunks80
Has anyone ever run across this error message when running aop? I've gotten it using both jdk 1.6 and jdk 1.5 on Fedora Core 5 64-bit
jdk 1.6
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at ../../../src/share/instrument/JPLISAgent.c line: 806
jdk 1.5
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message transform method call failed at ../../../src/share/instrument/JPLISAgent.c line: 831
The errors occur...memory skyrockets and then maybe a minute later aspects and interceptors are no longer called.
I'm sure it is something in my code because i've been using JBoss-AOP for a while and never run into this problem. I just have no idea what causes something like this to happen and couldn't find much information. I took a look at the source file for JPLISAgent.c for 1.5 and there is a comment near the line that says "/* Finally, unmarshall the parameters (if someone touched the buffer, tell the JVM) */" Does this mean one of my aspcts is causing a buffer overflow?
Any one have any ideas?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008033#4008033
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008033
19 years, 2 months
[EJB 3.0] - Deployment of node 2 fails in JBoss 4.0.5.GA + EJB3 RC9 patc
by J.Hedin
We use JBoss 4.0.5.GA + EJB3 RC9 Patch 1+ jBPM 3.1.3 with store in MySQL 5 for our application. The application runs in an active-active cluster on two nodes. The flow is mainly
MDB (starts TX) -> token.signal() -> jBPM actions (often calls EJB3 SLSB -> EJB3 entity beans) -> JMS send tokenId to queue
and
EJB3-timer (starts TX) -> jBPM timers -> jBPM actions (SLSB -> Entity beans) -> JMS send tokenId to queue
We had problems with lockup with previous version of JBoss AS/EJB3, but all is stable now. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008021#4008021
Thanks all for great help.
We can however not add a second node under a heavy loaded cluster. By turning on some log4j debugging, the load on the cache is reduced enough to make the second node start. The application uses opportunistic locks. The test data generating the load is a worse case scenario with loads of lock errors and roll backs. Also the MDB sleeps 5s +- a small random time on lock error.
| 2007-01-28 22:52:17,475 ERROR [org.jboss.cache.TreeCache] failed to activate /se
| /ecare/ib/ejb/entity/Priority
| org.jboss.cache.CacheException: Failed getting state due to timeout on othernode
| -ext1:33264
| at org.jboss.cache.TreeCache._loadState(TreeCache.java:2076)
| at org.jboss.cache.TreeCache.loadState(TreeCache.java:1933)
| at org.jboss.cache.TreeCache.activateRegion(TreeCache.java:1825)
| at org.jboss.ejb3.entity.JBCCache.activateCacheRegion(JBCCache.java:293)
| at org.jboss.ejb3.entity.JBCCache.(JBCCache.java:61)
| at org.jboss.ejb3.entity.TreeCacheProviderHook.buildCache(TreeCacheProvi
| derHook.java:58)
| at org.hibernate.cache.CacheFactory.createCache(CacheFactory.java:61)
| at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:
| 214)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.jav
| a:1218)
| at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
| figuration.java:691)
| at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFa
| ctory(HibernatePersistence.java:127)
| at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnit
| Deployment.java:264)
| at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[
| Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
| at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
| J)Ljava.lang.Object;(Unknown Source)
| at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWra
| pper.java:102)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
| upport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
| eanSupport.java:245)
| at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[
| Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
| at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
| J)Ljava.lang.Object;(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
| ler.java:978)
| at $Proxy0.start()V(Unknown Source)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008027#4008027
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008027
19 years, 2 months