[JBoss JIRA] (JASSIST-207) Inconsistent Stack Map when inserting throw Expression with Java 7
by Ben Romberg (JIRA)
Ben Romberg created JASSIST-207:
-----------------------------------
Summary: Inconsistent Stack Map when inserting throw Expression with Java 7
Key: JASSIST-207
URL: https://issues.jboss.org/browse/JASSIST-207
Project: Javassist
Issue Type: Bug
Affects Versions: 3.18.0-GA
Reporter: Ben Romberg
Assignee: Shigeru Chiba
Priority: Critical
I wrote a unit-test for javassist, reproducing the issue:
public class ThrowExpressionCorruptsStackMapTableTest extends JvstTestRoot {
public ThrowExpressionCorruptsStackMapTableTest(String name) {
super(name);
}
public void testInsertLocalVars() throws Exception {
CtClass cc = sloader.get("test4.LocalVars");
CtMethod m1 = cc.getDeclaredMethod("run");
m1.insertBefore("throw new AssertionError((Object) \"assertion error\");");
cc.writeFile();
Object obj = make(cc.getName());
assertEquals(10, invoke(obj, "run"));
}
}
Throws:
java.lang.VerifyError: Expecting a stack map frame in method test4.LocalVars.run()I at offset 45
My use-case is almost the same, inserting a "throw AssertionError(...)" expression with insertBefore. However, I get a slightly different error message:
Stack map does not match the one at exception handler 37 in method timeofday.TimeOfDay.getSecond()I at offset 27
--
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 years, 4 months
[JBoss JIRA] (WFLY-1512) jboss-cli.sh throws NPE in batch mode with certain commands
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1512?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-1512:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=977426
> jboss-cli.sh throws NPE in batch mode with certain commands
> -----------------------------------------------------------
>
> Key: WFLY-1512
> URL: https://issues.jboss.org/browse/WFLY-1512
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.0.0.Alpha2
> Environment: Linux 3.9.4-200.fc18.x86_64 #1 SMP Fri May 24 20:10:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Thomas Hauser
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.Alpha2
>
>
> When the jboss-cli.sh (and by extension, the CommandContext API in java) is given certain commands while not connected to the client, an unhandled NPE is thrown from org.jboss.as.cli.handlers.GenericTypeOperationHandler.getOperationDescription(GenericTypeOperationHandler.java:886)
> Certain other commands succeed:
> [disconnected / #] /subsystem=datasources/jdbc-driver=ibmdb2:add(driver-name=ibmdb2,driver-module-name=com.ibm.db2)
> #1 /subsystem=datasources/jdbc-driver=ibmdb2:add(driver-name=ibmdb2,driver-module-name=com.ibm.db2)
> The line in question is here, in org.jboss.as.cli.handlers.GenericTypeOperationHandler:
> result = ctx.getModelControllerClient().execute(request);
> At the time of this call, the client field of the context is null; therefore, calling the execute method results in this NPE. This code is not hit with the /subsystem command because of some logic I see in CommandContextImpl.
--
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 years, 4 months
[JBoss JIRA] (WFLY-1512) jboss-cli.sh throws NPE in batch mode with certain commands
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1512?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1512:
-----------------------------------------------
Alexey Loubyansky <olubyans(a)redhat.com> changed the Status of [bug 977426|https://bugzilla.redhat.com/show_bug.cgi?id=977426] from NEW to ASSIGNED
> jboss-cli.sh throws NPE in batch mode with certain commands
> -----------------------------------------------------------
>
> Key: WFLY-1512
> URL: https://issues.jboss.org/browse/WFLY-1512
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.0.0.Alpha2
> Environment: Linux 3.9.4-200.fc18.x86_64 #1 SMP Fri May 24 20:10:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Thomas Hauser
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.Alpha2
>
>
> When the jboss-cli.sh (and by extension, the CommandContext API in java) is given certain commands while not connected to the client, an unhandled NPE is thrown from org.jboss.as.cli.handlers.GenericTypeOperationHandler.getOperationDescription(GenericTypeOperationHandler.java:886)
> Certain other commands succeed:
> [disconnected / #] /subsystem=datasources/jdbc-driver=ibmdb2:add(driver-name=ibmdb2,driver-module-name=com.ibm.db2)
> #1 /subsystem=datasources/jdbc-driver=ibmdb2:add(driver-name=ibmdb2,driver-module-name=com.ibm.db2)
> The line in question is here, in org.jboss.as.cli.handlers.GenericTypeOperationHandler:
> result = ctx.getModelControllerClient().execute(request);
> At the time of this call, the client field of the context is null; therefore, calling the execute method results in this NPE. This code is not hit with the /subsystem command because of some logic I see in CommandContextImpl.
--
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 years, 4 months
[JBoss JIRA] (WFLY-1512) jboss-cli.sh throws NPE in batch mode with certain commands
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-1512?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky updated WFLY-1512:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/4644
> jboss-cli.sh throws NPE in batch mode with certain commands
> -----------------------------------------------------------
>
> Key: WFLY-1512
> URL: https://issues.jboss.org/browse/WFLY-1512
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.0.0.Alpha2
> Environment: Linux 3.9.4-200.fc18.x86_64 #1 SMP Fri May 24 20:10:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Thomas Hauser
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.Alpha2
>
>
> When the jboss-cli.sh (and by extension, the CommandContext API in java) is given certain commands while not connected to the client, an unhandled NPE is thrown from org.jboss.as.cli.handlers.GenericTypeOperationHandler.getOperationDescription(GenericTypeOperationHandler.java:886)
> Certain other commands succeed:
> [disconnected / #] /subsystem=datasources/jdbc-driver=ibmdb2:add(driver-name=ibmdb2,driver-module-name=com.ibm.db2)
> #1 /subsystem=datasources/jdbc-driver=ibmdb2:add(driver-name=ibmdb2,driver-module-name=com.ibm.db2)
> The line in question is here, in org.jboss.as.cli.handlers.GenericTypeOperationHandler:
> result = ctx.getModelControllerClient().execute(request);
> At the time of this call, the client field of the context is null; therefore, calling the execute method results in this NPE. This code is not hit with the /subsystem command because of some logic I see in CommandContextImpl.
--
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 years, 4 months
[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted
by Khalil Ghasemzadeh (JIRA)
[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ]
Khalil Ghasemzadeh commented on JBRULES-2936:
---------------------------------------------
I had same problem in loading Persian characters. This problem is solved by fixing two lines of code:
org.drools.rule.builder.dialect.java.JavaDialect.addClassCompiledTask(final String className, final BaseDescr descr, final String text, final MemoryResourceReader src, final ErrorHandler handler):
src.add(fileName, text.getBytes()) --> src.add(fileName, text.getBytes(Charset.forName("UTF-8"))
org.drools.commons.jci.compilers.EclipseJavaCompiler. getContents():
return new String(content).toCharArray() --> return new String(content, Charset.forName("UTF-8")).toCharArray()
> Importing decision table from Excel: Non Ascii chars should not be corrupted
> ----------------------------------------------------------------------------
>
> Key: JBRULES-2936
> URL: https://issues.jboss.org/browse/JBRULES-2936
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Fix For: 6.0.0.Alpha1
>
>
> see
> http://stackoverflow.com/questions/5298748/guvnor-rules-encoding
> Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding.
--
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 years, 4 months
[JBoss JIRA] (WFLY-1496) @Transactional doesn't work
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-1496?page=com.atlassian.jira.plugin.... ]
jaikiran pai reassigned WFLY-1496:
----------------------------------
Assignee: Stefano Maestri (was: jaikiran pai)
{quote}
at org.jboss.jca.adapters.jdbc.WrapperDataSource.checkTransactionActive(WrapperDataSource.java:247)
{quote}
It looks like the WrapperDataSource uses UserTransaction for the sake of checking a transaction status. The EE spec states that the UserTransaction isn't supposed to be allowed access for certain invocation (like the one above). If the WrapperDataSource really needs to just check the transaction status then it can use the TransactionSynchronizationRegistry instead http://docs.oracle.com/javaee/6/api/javax/transaction/TransactionSynchron.... Specifically, the getTransactionStatus() method http://docs.oracle.com/javaee/6/api/javax/transaction/TransactionSynchron.... The application server makes the TransactionSynchronizationRegistry available under (vendor specific) java:jboss/TransactionSynchronizationRegistry JNDI name. The other way would be to just use some internal transaction manager API to check the status.
> @Transactional doesn't work
> ---------------------------
>
> Key: WFLY-1496
> URL: https://issues.jboss.org/browse/WFLY-1496
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Stefano Maestri
> Attachments: testcase-WFLY-1496.zip
>
>
> I just tried the WildFly Alpha 2 snapshot containing Narayana 5.0.0.M3 and get the error message below. The classes causing the error are:
> @Path("/bestellungen")
> @Produces({ APPLICATION_JSON, APPLICATION_XML })
> //@RequestScoped is default for JAX-RS
> @Transactional
> public class BestellungResource {
> @Inject
> private BestellungService bs;
> ...
> }
> @Transactional(TxType.MANDATORY)
> public class BestellungServiceImpl implements Serializable {
> private static final long serialVersionUID = ...L;
>
> @PersistenceContext
> private transient EntityManager em;
> // method invoking JPA / Hibernate
> }
> The fragment of server.log:
> 15:11:43,254 DEBUG [org.hibernate.SQL]
> /* named HQL query Bestellung.findKundeById */ select
> distinct abstractku1_.id as id2_8_,
> abstractku1_.aktualisiert as aktualis3_8_,
> abstractku1_.bemerkungen as bemerkun4_8_,
> abstractku1_.email as email5_8_,
> abstractku1_.erzeugt as erzeugt6_8_,
> abstractku1_.file_fk as file18_8_,
> abstractku1_.kategorie as kategori7_8_,
> abstractku1_.nachname as nachname8_8_,
> abstractku1_.newsletter as newslett9_8_,
> abstractku1_.password as passwor10_8_,
> abstractku1_.rabatt as rabatt11_8_,
> abstractku1_.seit as seit12_8_,
> abstractku1_.umsatz as umsatz13_8_,
> abstractku1_.version as version14_8_,
> abstractku1_.vorname as vorname15_8_,
> abstractku1_.familienstand_fk as familie16_8_,
> abstractku1_.geschlecht_fk as geschle17_8_,
> abstractku1_.art as art1_8_
> from
> Bestellung bestellung0_
> inner join
> kunde abstractku1_
> on bestellung0_.kunde_fk=abstractku1_.id
> where
> bestellung0_.id=?
> 15:11:43,254 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null
> 15:11:43,254 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER
--
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 years, 4 months
[JBoss JIRA] (WFLY-1496) @Transactional doesn't work
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-1496?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-1496:
-------------------------------
Component/s: JCA
> @Transactional doesn't work
> ---------------------------
>
> Key: WFLY-1496
> URL: https://issues.jboss.org/browse/WFLY-1496
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Transactions
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Stefano Maestri
> Attachments: testcase-WFLY-1496.zip
>
>
> I just tried the WildFly Alpha 2 snapshot containing Narayana 5.0.0.M3 and get the error message below. The classes causing the error are:
> @Path("/bestellungen")
> @Produces({ APPLICATION_JSON, APPLICATION_XML })
> //@RequestScoped is default for JAX-RS
> @Transactional
> public class BestellungResource {
> @Inject
> private BestellungService bs;
> ...
> }
> @Transactional(TxType.MANDATORY)
> public class BestellungServiceImpl implements Serializable {
> private static final long serialVersionUID = ...L;
>
> @PersistenceContext
> private transient EntityManager em;
> // method invoking JPA / Hibernate
> }
> The fragment of server.log:
> 15:11:43,254 DEBUG [org.hibernate.SQL]
> /* named HQL query Bestellung.findKundeById */ select
> distinct abstractku1_.id as id2_8_,
> abstractku1_.aktualisiert as aktualis3_8_,
> abstractku1_.bemerkungen as bemerkun4_8_,
> abstractku1_.email as email5_8_,
> abstractku1_.erzeugt as erzeugt6_8_,
> abstractku1_.file_fk as file18_8_,
> abstractku1_.kategorie as kategori7_8_,
> abstractku1_.nachname as nachname8_8_,
> abstractku1_.newsletter as newslett9_8_,
> abstractku1_.password as passwor10_8_,
> abstractku1_.rabatt as rabatt11_8_,
> abstractku1_.seit as seit12_8_,
> abstractku1_.umsatz as umsatz13_8_,
> abstractku1_.version as version14_8_,
> abstractku1_.vorname as vorname15_8_,
> abstractku1_.familienstand_fk as familie16_8_,
> abstractku1_.geschlecht_fk as geschle17_8_,
> abstractku1_.art as art1_8_
> from
> Bestellung bestellung0_
> inner join
> kunde abstractku1_
> on bestellung0_.kunde_fk=abstractku1_.id
> where
> bestellung0_.id=?
> 15:11:43,254 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null
> 15:11:43,254 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER
--
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 years, 4 months