[JBoss JIRA] (JASSIST-149) ClassFormatError when using an ExprEditor, replacing a MethodCall after replacing a FieldAccess with a throw-Statement
by Ben Romberg (JIRA)
Ben Romberg created JASSIST-149:
-----------------------------------
Summary: ClassFormatError when using an ExprEditor, replacing a MethodCall after replacing a FieldAccess with a throw-Statement
Key: JASSIST-149
URL: https://issues.jboss.org/browse/JASSIST-149
Project: Javassist
Issue Type: Bug
Affects Versions: 3.15.0-GA
Environment: JRE 1.6
Reporter: Ben Romberg
Assignee: Shigeru Chiba
To reproduce, use the following ExprEditor:
new ExprEditor() {
edit(FieldAccess fieldAccess) {
fieldAccess.replace("throw new ...");
}
edit(MethodCall methodCall) {
methodCall.replace(...);
}
}
Now, use the ExprEditor on a method assigning a field first and then calling a method. When loading the modified class, the following exception should occur:
java.lang.ClassFormatError: Invalid pc in LineNumberTable in class file de/andrena/next/systemtest/pure/PureOnlyForOwnMethodsFieldsAndParametersSystemTest$TargetClass
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
...
Expected behavior:
* Either correctly replacing the methodCall without corrupting the line-number-table, or
* throwing a CannotCompileException when trying to modify/insert code after a throw-Expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JGRP-1419) UNICAST / UNICAST2: combine retransmission for all members
by Bela Ban (JIRA)
Bela Ban created JGRP-1419:
------------------------------
Summary: UNICAST / UNICAST2: combine retransmission for all members
Key: JGRP-1419
URL: https://issues.jboss.org/browse/JGRP-1419
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.1
UNICAST:
- The sender has an AckSenderWindow, the receiver an AckReceiverWindow
- The sender keeps retransmitting until the receiver delivers the message and acks it
UNICAST2:
- The sender has an AckSenderWindow (without retransmission) and the receiver a NakReceiverWindow
- The receiver asks the sender for retransmission only if there's a gap
- Stability ensures that the sender doesn't keep messages around forever
Suggestions:
- Similar to NAKACK, don't use a separate retransmitter for every member (window), but have just 1 retransmitter task scan the message tables and do retransmission
- In UNICAST2, Table<Message> can replace the NakReceiverWindow on the receiver side
- In UNICAST2, we can probably also replace the sender's window with a Table<Message>
- in UNICAST, the sender's AckSenderWindow can also be replaced with a Table<Message>
- In UNICAST, investigate whether the receiver window can be replaced with a Table<Message> as well !
If we can do this, then we have
- only 1 proven data structure (Table<Message>)
- not 1 retransmitter per window, but 1 for all the windows (saving space) !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1804) Fix the Web Services description providers for the improved validation in jboss-as-subsystem-test
by Kabir Khan (JIRA)
Fix the Web Services description providers for the improved validation in jboss-as-subsystem-test
--------------------------------------------------------------------------------------------------
Key: AS7-1804
URL: https://issues.jboss.org/browse/AS7-1804
Project: Application Server 7
Issue Type: Feature Request
Reporter: Kabir Khan
Assignee: Alessio Soldano
Fix For: 7.1.0.Alpha1
I added a test called WebServicesSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days.
To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() and isValidateOperations() as follows:
@Override
protected ValidationConfiguration getModelValidationConfiguration() {
return null;
}
@Override
protected boolean isValidateOperations() {
//TODO fix providers https://issues.jboss.org/browse/AS7-1789
return false;
}
Returning null basically turns off validation of the providers, and the isValidateOperations() override turns off validation of the contents of the actual operations. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples.
The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes
The above is standard text as I'm going through and creating tests. The test has been @Ignored due to a further failure once validation 'passes' (i.e. the validation is not run due to the flags set)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-2977) Add sun.io package to the sun.jdk module
by Robert Reimann (Created) (JIRA)
Add sun.io package to the sun.jdk module
----------------------------------------
Key: AS7-2977
URL: https://issues.jboss.org/browse/AS7-2977
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.0.Beta1
Reporter: Robert Reimann
Please add the sun.io package to the sun.jdk module to support IBM DB2 JDBC drivers. Current DB2 JDBC drivers require access to the sun.io package as described in http://www.ibm.com/developerworks/forums/message.jspa?messageID=14230275
Otherwise it is likely to get the following exception:
{com.ibm.db2.jcc.a.SqlException: [jcc][t4][10199][10462][4.0.100] Required character converter is not available. ERRORCODE=-4220, SQLSTATE=null
at com.ibm.db2.jcc.a.yc.a(yc.java:55)
at com.ibm.db2.jcc.a.yc.a(yc.java:119)
at com.ibm.db2.jcc.a.dc.a(dc.java:1788)
at com.ibm.db2.jcc.a.dc.n(dc.java:496)
at com.ibm.db2.jcc.a.dc.F(dc.java:1262)
at com.ibm.db2.jcc.a.mk.d(mk.java:938)
at com.ibm.db2.jcc.a.mk.getString(mk.java:916)
at com.ibm.db2.jcc.a.mk.getString(mk.java:1368)
at org.jboss.jca.adapters.jdbc.WrappedResultSet.getString(WrappedResultSet.java:1359)}
After adding the following path to the sun.jdk module descriptor ($JBOSS_HOME/modules/sun/jdk/main/module.xml), the required character converter classes are found and the application behaves as expected:
{<path name="sun/io"/>}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months