[JBoss JIRA] Created: (JBAOP-398) No such field: jboss
by Flavia Rainone (JIRA)
No such field: jboss
--------------------
Key: JBAOP-398
URL: http://jira.jboss.com/jira/browse/JBAOP-398
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.alpha4, 1.5.5.GA
Reporter: Flavia Rainone
Fix For: 2.1.0.GA, 1.5.6.GA
If a POJO class being instrumented has a field called "org", jboss aop will eventually throw an exception with this error message (it might be after setting a field wrapper body, or after CtCasslass.toByteCode() , for example).
An example is:
javassist.CannotCompileException: [source error] no such field: jboss
at javassist.CtBehavior.setBody(CtBehavior.java:364)
at javassist.CtBehavior.setBody(CtBehavior.java:333)
at org.jboss.aop.instrument.OptimizedFieldAccessTransformer.buildWrappers(OptimizedFieldAccessTransformer.java:278)
at org.jboss.aop.instrument.OptimizedFieldAccessTransformer.doBuildFieldWrappers(OptimizedFieldAccessTransformer.java:100)
at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:102)
at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:724)
at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:107)
at org.jboss.aop.AspectManager.translate(AspectManager.java:910)
at org.jboss.aop.AspectManager.transform(AspectManager.java:853)
at org.jboss.aop.standalone.AOPTransformer.aspectTransform(AOPTransformer.java:88)
at org.jboss.aop.standalone.AOPTransformer.transform(AOPTransformer.java:75)
The moment in which the exception is being thrown seems to have to do with what joinpoint of POJO class are being instrumented. If the "org" field is being intercepted, the moment in which the field wrapper body is being set is the moment in which javassist throws the exception. If the field "org" is not being intercepted, it seems that the moment in which the exception is being thrown is right after jboss aop instrumentation execution, when toByteCode method is invoked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month
[JBoss JIRA] Created: (JGRP-455) Problem with retransmission: message not found
by Bela Ban (JIRA)
Problem with retransmission: message not found
----------------------------------------------
Key: JGRP-455
URL: http://jira.jboss.com/jira/browse/JGRP-455
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4.1 SP1
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5
Sometimes a sender cannot find a message with a seqno as requested by a receiver. The seqno requested (47176) was already purged, sent_msgs: [48059 - 48090] (32)
This could be either an issue in STABLE, which prematurely purges messages although not all members agreed on the highest seqnos seen, or NAKACK, which might incorrectly 'change' seqnos. Very hard to reproduce !
Trace:
42032 [ERROR] [OOB Thread,perf,10.68.32.33:32968] NAKACK.handleXmitReq(): - (requester=10.68.28.33:33763, local_addr=10.68.32.33:32968) message 10.68.32.33:32968::47176 not found in sent msgs [48059 - 48090] (32)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month