March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6515) Cannot add security role to security-setting using CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6515?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6515: ---------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 910322|https://bugzilla.redhat.com/show_bug.cgi?id=910322] This did not get to any EAP 6.1.0.ERx release yet. Setting status Modified. This blocks testing automation. > Cannot add security role to security-setting using CLI > ------------------------------------------------------ > > Key: AS7-6515 > URL: https://issues.jboss.org/browse/AS7-6515 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > Not possible to add security role to security-setting using CLI: > [standalone@localhost:9999 hornetq-server=default] ./security-setting=#/role=franta:add() > { > "outcome" => "failed", > "failure-description" => "JBAS014746: send may not be null", > "rolled-back" => true > } -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6648) pooled-connection-factory's inbound-config is not persisted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6648?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6648: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 900842|https://bugzilla.redhat.com/show_bug.cgi?id=900842] from NEW to POST > pooled-connection-factory's inbound-config is not persisted > ----------------------------------------------------------- > > Key: AS7-6648 > URL: https://issues.jboss.org/browse/AS7-6648 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The code to persist pooled-connection-factory's inbound-config is not correct in MessagingXMLWriter (the pooled-connection-factory ModelNode layout does not have an intermediate inbound-config node): any changes to AS7 configuration will discard the <inbound-config> element from the persisted XML files -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6750) "HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed" on clean shutdown

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-6750: ----------------------------------- Summary: "HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed" on clean shutdown Key: AS7-6750 URL: https://issues.jboss.org/browse/AS7-6750 Project: Application Server 7 Issue Type: Bug Affects Versions: No Release Reporter: Radoslav Husar Fix For: 8.0.0.Alpha1 Attachments: server.log Just saw this when I was closely looking through clustering testsuite logs. Affected version: master 8a6aac3c8eb6bc94b7eddfa4d090c9ac05c7e37b Seems like the connection pool closes earlier than the entiti manager shutdown? {code}15:09:34,473 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 54) HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-168] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:169) at org.h2.message.DbException.get(DbException.java:146) at org.h2.message.DbException.get(DbException.java:135) at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1384) at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1359) at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:403) at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:880) at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1589) at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:298) at org.hibernate.tool.hbm2ddl.DatabaseExporter.<init>(DatabaseExporter.java:54) at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:367) at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:318) at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:314) at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1386) at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:194) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2.run(PersistenceUnitServiceImpl.java:124) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] at org.jboss.threads.JBossThread.run(JBossThread.java:122){code} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6750) "HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed" on clean shutdown

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-6750?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated AS7-6750: -------------------------------- Attachment: server.log > "HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed" on clean shutdown > ------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6750 > URL: https://issues.jboss.org/browse/AS7-6750 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: No Release > Reporter: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > Attachments: server.log > > > Just saw this when I was closely looking through clustering testsuite logs. > Affected version: master 8a6aac3c8eb6bc94b7eddfa4d090c9ac05c7e37b > Seems like the connection pool closes earlier than the entiti manager shutdown? > {code}15:09:34,473 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 54) HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-168] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1384) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1359) > at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:403) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:880) > at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1589) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:298) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.<init>(DatabaseExporter.java:54) > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:367) > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:318) > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:314) > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1386) > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:194) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2.run(PersistenceUnitServiceImpl.java:124) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > at org.jboss.threads.JBossThread.run(JBossThread.java:122){code} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-83) Cannot use imported classes in declared types fields initialization

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-83?page=com.atlassian.jira.plugin.... ] Mario Fusco resolved DROOLS-83. ------------------------------- Fix Version/s: 5.6 6.0.0.Alpha1 Resolution: Done > Cannot use imported classes in declared types fields initialization > ------------------------------------------------------------------- > > Key: DROOLS-83 > URL: https://issues.jboss.org/browse/DROOLS-83 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 5.6, 6.0.0.Alpha1 > > > Having added the following import statements in the drl: > import org.drools.compiler.test.Person > import org.drools.compiler.test.Man > this field initialization in a declared type in the same drl doesn't compile: > persons: Person[] = new Person[] { new Man() } > As a workaround, note that adding the full class names fixes the problem: > persons: Person[] = new org.drools.compiler.test.Person[] { new org.drools.compiler.test.Man() } -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6749) EJB 2.1 transactions per method

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/AS7-6749?page=com.atlassian.jira.plugin.s... ] Wolf-Dieter Fink updated AS7-6749: ---------------------------------- Description: If the Class annotation is 'Supports' (better different to 'Required') and the method annotation is 'Required', it will not be respected. (was: If the Class annotation is 'Supports' the method annotation is 'Required', it will not be respected.) > EJB 2.1 transactions per method > ------------------------------- > > Key: AS7-6749 > URL: https://issues.jboss.org/browse/AS7-6749 > Project: Application Server 7 > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Pawel Wilk > Assignee: jaikiran pai > > If the Class annotation is 'Supports' (better different to 'Required') and the method annotation is 'Required', it will not be respected. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-2166) Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-2166?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-2166: ---------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 899644|https://bugzilla.redhat.com/show_bug.cgi?id=899644] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/j... - red ball for one node == No space left on device shared testsuite manualy hacked in local repo to reflect #17389 JBWS3140 tests didn't fail > Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea > ---------------------------------------------------------------------------- > > Key: AS7-2166 > URL: https://issues.jboss.org/browse/AS7-2166 > Project: Application Server 7 > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Labels: eap6_prd_req > Fix For: 7.1.2.Final (EAP) > > > James Perkins: > {quote} > At one point there was a JIRA for OpenJDK 6, in fact I think a couple. The issue with OpenJDK 6 is in the build we use some JavaScript and OpenJDK 6 doesn't come with a JavaScript engine. I tried a couple things to get Rhino working with it as that's what the Sun JDK uses, but I think it needs to implement an SPI to get it to work. I didn't look into it much beyond that. > JDK 7 is a different issue. It's a bug in the annotation processing API which the JBoss Logging Tooling uses. I just refreshed my OpenJDK 7 update source and it looks like the bug is fixed in there. It's fixed in IcedTea as well. There could be the JavaScript issue here as well I can't actually remember, but I thought I had some successful builds with custom JDK's I compiled. > I did just try with IcedTea 7 and got some other errors. I'm building the latest upstream of OpenJDK 7 now and we'll see if it works. I'll let you know either way. > Let me know if you have any more questions on this. I did dig into a while ago a little. > {quote} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-186) java.lang.VerifyError: Inconsistent args count operand in invokeinterface in method

by Guillaume Alvarez (JIRA)

[ https://issues.jboss.org/browse/JASSIST-186?page=com.atlassian.jira.plugi... ] Guillaume Alvarez commented on JASSIST-186: ------------------------------------------- We had the very same issue. Is there any ETA for a correction? > java.lang.VerifyError: Inconsistent args count operand in invokeinterface in method > ----------------------------------------------------------------------------------- > > Key: JASSIST-186 > URL: https://issues.jboss.org/browse/JASSIST-186 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.17.0-GA, 3.17.1-GA > Reporter: Lauri Tulmin > Assignee: Shigeru Chiba > Attachments: javassist-bug2.zip > > > Happens when the argument of interface method call comes from anoter method call, like > {code} > m.insertBefore( > "{" + > " java.util.List l = new java.util.ArrayList();" + > " l.add(this.toString());" + > "}" > ); > {code} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6648) pooled-connection-factory's inbound-config is not persisted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6648?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6648: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900842 > pooled-connection-factory's inbound-config is not persisted > ----------------------------------------------------------- > > Key: AS7-6648 > URL: https://issues.jboss.org/browse/AS7-6648 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The code to persist pooled-connection-factory's inbound-config is not correct in MessagingXMLWriter (the pooled-connection-factory ModelNode layout does not have an intermediate inbound-config node): any changes to AS7 configuration will discard the <inbound-config> element from the persisted XML files -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-83) Cannot use imported classes in declared types fields initialization

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-83: --------------------------------- Summary: Cannot use imported classes in declared types fields initialization Key: DROOLS-83 URL: https://issues.jboss.org/browse/DROOLS-83 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Having added the following import statements in the drl: import org.drools.compiler.test.Person import org.drools.compiler.test.Man this field initialization in a declared type in the same drl doesn't compile: persons: Person[] = new Person[] { new Man() } As a workaround, note that adding the full class names fixes the problem: persons: Person[] = new org.drools.compiler.test.Person[] { new org.drools.compiler.test.Man() } -- 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

13 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2013