3:05 p.m.
ami tabak created JASSIST-177:
---------------------------------
Summary: javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:05 p.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
ami tabak updated JASSIST-177:
------------------------------
Attachment: javassist-3-17-GA-weblogicBugSample.zip
Example project attempting as simple insertBefore/After
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:13 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
Shigeru Chiba resolved JASSIST-177.
-----------------------------------
Fix Version/s: 3.17.1-GA
Resolution: Done
This bug is because weblogic.jar has been compiled by Java 6 but contains JSR
instructions, which Oracle/Open JDKs do not use. It works on Java 6 but not Java 7, which
does not allow JSR.
I've modified Javassist so that it will not generate StackMapTables when it finds
JSR.
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
ami tabak commented on JASSIST-177:
-----------------------------------
Which svn tag/branch is the fix committed to ?
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:51 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-177:
---------------------------------------
It's HEAD.
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:58 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
ami tabak reopened JASSIST-177:
-------------------------------
Bad byte code now appears on Oracle's JDBC driver classes.
Will attach sample test
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
ami tabak updated JASSIST-177:
------------------------------
Attachment: weblogicBugSampleWithOracleDriver.zip
Getting the following error.
One thing I noticed is that simple one line instrumentation, for example
System.out.println("foo");
didnt reproduce the issue. Once I add a try catch clause it appears.
The error
=========
(45)javassist.CtMethod@33a644f9[public synchronized close ()V]
(53)javassist.CtMethod@e8e92e3d[public synchronized close (Ljava/util/Properties;)V]
Found method:(Ljava/util/Properties;)V
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: close (Ljava/util/Properties;)V in
oracle.jdbc.driver.PhysicalConnection: dead code detected at 52. No stackmap table
generated.
at javassist.CtBehavior.insertAfter(CtBehavior.java:867)
at javassist.CtBehavior.insertAfter(CtBehavior.java:788)
at com.optier.bug.report.Test.oracleTestCase(Test.java:94)
at com.optier.bug.report.Test.main(Test.java:18)
Caused by: javassist.bytecode.BadBytecode: close (Ljava/util/Properties;)V in
oracle.jdbc.driver.PhysicalConnection: dead code detected at 52. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:110)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertAfter(CtBehavior.java:858)
... 3 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 52. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:328)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:311)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:165)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:107)
... 6 more
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip,
weblogicBugSampleWithOracleDriver.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
ami tabak updated JASSIST-177:
------------------------------
Priority: Critical (was: Major)
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Priority: Critical
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip,
weblogicBugSampleWithOracleDriver.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 a.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
ami tabak commented on JASSIST-177:
-----------------------------------
I noticed a mismatch between the ojdbc6.jar manifest and the actual major number of the
problematic class in the example. The class major number is 50 but the manifest states jar
was build using java 1.5 which as far as I understand should result in major number 49.
I see that javassist bases its decision whether to support the java6 based on the major
number. Could it be that Oracle had a bug on their side in one of the compilers which
wrote the wrong major number to the class file ? Is there any other way to verify class
file structure?
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Priority: Critical
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip,
weblogicBugSampleWithOracleDriver.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:51 p.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-177:
---------------------------------------
This is a bug of CtBehavior#insertAfter, which may actually generate dead code. I will
fix it.
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Priority: Critical
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip,
weblogicBugSampleWithOracleDriver.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 p.m.
[
https://issues.jboss.org/browse/JASSIST-177?page=com.atlassian.jira.plugi...
]
Shigeru Chiba resolved JASSIST-177.
-----------------------------------
Resolution: Done
I have fixed.
javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
-----------------------------------------------------------
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Priority: Critical
Fix For: 3.17.1-GA
Attachments: javassist-3-17-GA-weblogicBugSample.zip,
weblogicBugSampleWithOracleDriver.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by
javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect
(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in
weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table
generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4241
days inactive
4255
days old
10 comments
2 participants
participants (2)
-
ami tabak (JIRA) -
Shigeru Chiba (JIRA)