12:26 p.m.
Default instrumentation mode unexpected
---------------------------------------
Key: JBAOP-391
URL: http://jira.jboss.com/jira/browse/JBAOP-391
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.alpha4
Reporter: Flavia Rainone
Fix For: 2.0.0.alpha5
In the before/after advice examples, I needed to set the instrumentation mode in the
build.xml file, because jboss-aop wasn't running in generated-advisor mode.
--
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
4:33 p.m.
New subject: [JBoss JIRA] Commented: (JBAOP-391) Default instrumentation mode unexpected
[ http://jira.jboss.com/jira/browse/JBAOP-391?page=comments#action_12359627 ]
Kabir Khan commented on JBAOP-391:
----------------------------------
This is weird, it always runs as expected for me?
Default instrumentation mode unexpected
---------------------------------------
Key: JBAOP-391
URL: http://jira.jboss.com/jira/browse/JBAOP-391
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.alpha4
Reporter: Flavia Rainone
Fix For: 2.0.0.alpha5
In the before/after advice examples, I needed to set the instrumentation mode in the
build.xml file, because jboss-aop wasn't running in generated-advisor mode.
--
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
4:39 p.m.
New subject: [JBoss JIRA] Commented: (JBAOP-391) Default instrumentation mode unexpected
[ http://jira.jboss.com/jira/browse/JBAOP-391?page=comments#action_12359629 ]
Flavia Rainone commented on JBAOP-391:
--------------------------------------
Please, remove the instrumentation mode and advisor configurations from the build file,
and try to run the example (it can be beforeafter example).
Default instrumentation mode unexpected
---------------------------------------
Key: JBAOP-391
URL: http://jira.jboss.com/jira/browse/JBAOP-391
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.alpha4
Reporter: Flavia Rainone
Fix For: 2.0.0.alpha5
In the before/after advice examples, I needed to set the instrumentation mode in the
build.xml file, because jboss-aop wasn't running in generated-advisor mode.
--
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
5:18 p.m.
New subject: [JBoss JIRA] Commented: (JBAOP-391) Default instrumentation mode unexpected
[ http://jira.jboss.com/jira/browse/JBAOP-391?page=comments#action_12359634 ]
Kabir Khan commented on JBAOP-391:
----------------------------------
Aha, I thought we were talking about the tests and not the examples :-)
I think it is just an error in what is output by InstrumentorFactory. If I change the
beforeafter example to
<target name="run.50.instrumented"
depends="compile50standalone">
<java fork="yes" failOnError="true"
className="Driver">
<sysproperty key="jboss.aop.path"
value="jboss-aop.xml"/>
<jvmarg value="-javaagent:${aop50jar}"/>
<classpath refid="classpath50"/>
</java>
</target>
I think it works as expected?
[java] SETUP
[java] =====
[java] Creating account 'A' with initial balance of $30.0
[java] Creating account 'B' with initial balance of $50.0
[java] Creating account 'C' with initial balance of $0.0
[java] TRANSACTIONS
[java] ============
[java] >>> Retrieved concurrency lock
[java] Withdrawing £10.00 from account A
[java] <<< Releasing concurrency lock
[java] >>> Retrieved concurrency lock
[java] Transfering £100.00 from account B to account C
[java] <<< Releasing concurrency lock
[java] >>> Retrieved concurrency lock
[java] Transfering £89.11 from account C to account A
[java] <<< Releasing concurrency lock
[java] >>> Retrieved concurrency lock
[java] Withdrawing £0.11 from account C
[java] <<< Releasing concurrency lock
[java] >>> Retrieved concurrency lock
[java] Withdrawing £5.00 from account B
[java] <<< Releasing concurrency lock
[java] >>> Retrieved concurrency lock
[java] Depositing £50.00 to account A
[java] <<< Releasing concurrency lock
[java] >>> Retrieved concurrency lock
[java] Depositing £51.00 to account B
[java] <<< Releasing concurrency lock
[java] FINAL BALANCE
[java] ===== =======
[java] A: £159.11
[java] C: £10.78
[java] B: -£4.00
Default instrumentation mode unexpected
---------------------------------------
Key: JBAOP-391
URL: http://jira.jboss.com/jira/browse/JBAOP-391
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.alpha4
Reporter: Flavia Rainone
Fix For: 2.0.0.alpha5
In the before/after advice examples, I needed to set the instrumentation mode in the
build.xml file, because jboss-aop wasn't running in generated-advisor mode.
--
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
9:16 p.m.
New subject: [JBoss JIRA] Closed: (JBAOP-391) Default instrumentation mode unexpected
[ http://jira.jboss.com/jira/browse/JBAOP-391?page=all ]
Flavia Rainone closed JBAOP-391.
--------------------------------
Resolution: Done
Assignee: Kabir Khan
Somehow, the problem is fixed.
I'm pretty sure that it was not an output error. Running an example (like beforeafter)
with load-time weaving enabled, and no jboss.aop.instrumentor set, was resulting in no
before/after advices running. I've run the same test several times before creating
this issue.
The good news is that I've saved the build.xml file with the configuration that was
causing the error, and, now, running the example using this file on trunk, I can see that
the error is gone.
Default instrumentation mode unexpected
---------------------------------------
Key: JBAOP-391
URL: http://jira.jboss.com/jira/browse/JBAOP-391
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.alpha4
Reporter: Flavia Rainone
Assigned To: Kabir Khan
Fix For: 2.0.0.alpha5
In the before/after advice examples, I needed to set the instrumentation mode in the
build.xml file, because jboss-aop wasn't running in generated-advisor mode.
--
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
6980
days inactive
7037
days old
4 comments
2 participants
participants (2)
-
Flavia Rainone (JIRA) -
Kabir Khan (JIRA)