[JBoss JIRA] Created: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
7:04 a.m.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic
10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:43 a.m.
New subject: [JBoss JIRA] Commented: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
Shigeru Chiba commented on JASSIST-125:
---------------------------------------
The reason might be that weblogic.jdbc.jta.DataSource.class was generated by the Java 1.4
compiler.
Can you check (by javap -verbose) the major/minor version of that class file?
Or, is there any way to freely get com.bea.core.datasource6_1.4.0.0.jar? For further
investigation,
I need that class file.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 a.m.
New subject: [JBoss JIRA] Commented: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
Adam Honen commented on JASSIST-125:
------------------------------------
The Major version is 50 (Java 6).
The jar can be freely downloaded as part of WebLogic 10.3.
I would have attached it to the issue except I'm not sure if the license terms are.
You can freely download WebLogic 10.3 from Oracle's site here:
http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html.
It may require you to create an OTN account (which is free), though.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:08 p.m.
New subject: [JBoss JIRA] Commented: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
Shigeru Chiba commented on JASSIST-125:
---------------------------------------
Thanks, I could donwload com.bea...datasource6_..jar.
It seems that this bug happened because the bytecode of getConnection() includes jsr
instruction,
which should not be used in JDK 5 or later as far as I know. I tried the compiler of
JRocket but
it also generated bytecode without jsr. I will study this more.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:24 p.m.
New subject: [JBoss JIRA] Commented: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JASSIST-125:
-------------------------------------
I believe that Java 1.5 does allow jsr and in fact may use it for dealing with nested
finally blocks; it was not forbidden until Java 6. So class files of version 49.0 and
earlier should be expected to have jsr instructions, whereas 50 should not.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:37 a.m.
New subject: [JBoss JIRA] Commented: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
Shigeru Chiba commented on JASSIST-125:
---------------------------------------
You are right. But weblogic.jdbc.jta.DataSource.class is in Java 6 (version 50). This
confuses me.
My understanding is a class file can use either jsr or StackMapTable. So Javassist can
generate a
StackMapTable only if a class file does not contain jsr. That's why Javassist fails
to run your test code
(DataSource.class uses both jsr and StackMapTable).
Anyway, what I would like to discuss is how to fix this problem. One idea is not to
generate a StackMapTable
if a class file contains jsr. Another idea is to try to generate a StackMapTable as long
as it is possible (this
means Javassist may fail but normally should succeed)
Any comments are welcome.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:32 p.m.
New subject: [JBoss JIRA] Commented: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
Shigeru Chiba commented on JASSIST-125:
---------------------------------------
I fixed this problem. I modified Javassist to produce a StackMapTable even if the
bytecode contains JSR/RET.
The produced StackMapTable is similar to the original one in a Weblogic's jar file but
it is invalid.
This is not a problem because the original one is also invalid (even jrocket reports its
bytecode is invalid) and
the JVM should just ignore such a wrong StackMapTable.
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:34 p.m.
New subject: [JBoss JIRA] Resolved: (JASSIST-125) Compilation fails with "javassist.bytecode.BadBytecode: jsr at 406" WebLogic 10.3 JTA data source class
[
https://jira.jboss.org/browse/JASSIST-125?page=com.atlassian.jira.plugin....
]
Shigeru Chiba resolved JASSIST-125.
-----------------------------------
Fix Version/s: 3.13.0.GA
Resolution: Done
Compilation fails with "javassist.bytecode.BadBytecode: jsr at
406" WebLogic 10.3 JTA data source class
-------------------------------------------------------------------------------------------------------
Key: JASSIST-125
URL: https://jira.jboss.org/browse/JASSIST-125
Project: Javassist
Issue Type: Bug
Affects Versions: 3.12.0.GA
Environment: Reproduced on Linux x86 and Windows XP (x86).
Reporter: Adam Honen
Assignee: Shigeru Chiba
Fix For: 3.13.0.GA
Trying to add code at the beginning of the method getConnection in the class
weblogic.jdbc.jta.DataSource I got the following error:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: jsr at 399
at javassist.CtBehavior.insertBefore(CtBehavior.java:728)
at javassist.CtBehavior.insertBefore(CtBehavior.java:685)
at Test.main(Test.java:26)
Caused by: javassist.bytecode.BadBytecode: jsr at 399
at javassist.bytecode.stackmap.Tracer.throwBadBytecode(Tracer.java:144)
at javassist.bytecode.stackmap.Tracer.visitJSR(Tracer.java:133)
at javassist.bytecode.stackmap.Tracer.doOpcode148_201(Tracer.java:563)
at javassist.bytecode.stackmap.Tracer.doOpcode(Tracer.java:101)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:182)
at javassist.bytecode.stackmap.MapMaker.traceException(MapMaker.java:213)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:175)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:192)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:141)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:96)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:416)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:398)
at javassist.CtBehavior.insertBefore(CtBehavior.java:719)
... 2 more
I've created a small program that simulates this problem outside the Weblogic
container.
The class can be found inside <Weblogic
home>\modules\com.bea.core.datasource6_1.4.0.0.jar.
And additional dependency which is required in order to load this class (although it is
not needed in order to modify the byte codes) is <Weblogic
home>\modules\com.bea.core.transaction_2.5.0.0.jar.
Both of these files are available when installing Weblogic 10.3.
I suspect this might be some sort of collision with WebLogic's Diagnostic framework.
I'm not sure how calls to WLDF are added, but it is possible they were added by some
other tool for manipulating byte codes (at compile time), in which case this issue is a
bit more interesting (could indicate collisions with certain other AOP tools).
Just for the sake of pin pointing the source of the problem, I also used AspectJ to add
code to the method. It worked fine with no errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5843
days inactive
5857
days old
7 comments
3 participants
participants (3)
-
Adam Honen (JIRA) -
David Lloyd (JIRA)
-
Shigeru Chiba (JIRA)