[JBoss JIRA] (JBJCA-952) JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-952?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated JBJCA-952:
----------------------------------
Fix Version/s: 1.0.15.Final
1.1.0.Beta4
Affects Version/s: 1.1.0.Beta3
1.0.14.Final
> JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor
> ------------------------------------------------------------------------
>
> Key: JBJCA-952
> URL: https://issues.jboss.org/browse/JBJCA-952
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.0.14.Final, 1.1.0.Beta3
> Reporter: James Livingston
> Assignee: Jesper Pedersen
> Fix For: 1.0.15.Final, 1.1.0.Beta4
>
>
> The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should
> 1) return itself or a proxy when the reicever implements the interface
> 2) return the wrapped object or a proxy when the wrapped object implements the interface
> 3) call the wrapped object's unwrap() method if the receiver is a wrapper
> 4) other throw a SQL exception
> JBossWrapper only does 2 and 4.
> This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection.
--
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 years, 9 months
[JBoss JIRA] (AS7-6226) Illegal domain configuration
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6226?page=com.atlassian.jira.plugin.s... ]
Heiko Braun commented on AS7-6226:
----------------------------------
its in the runtime model as well:
{noformat}
{
"deployment-overlay" => undefined,
"jvm" => undefined,
"management-subsystem-endpoint" => false,
"profile" => "full",
"socket-binding-group" => "full-sockets",
"socket-binding-port-offset" => 0,
"system-property" => undefined,
"deployment" => {"jboss-as-login.war" => undefined}
}
{noformat}
Legacy?
> Illegal domain configuration
> ----------------------------
>
> Key: AS7-6226
> URL: https://issues.jboss.org/browse/AS7-6226
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 7.2.0.Alpha1
>
>
> Not sure which operation created the 'management-subsystem-endpoint' attribute. but it sneaked during a create/copy operation somehow.
> {noformat}
> [Host Controller] Message: JBAS014788: Unexpected attribute 'management-subsystem-endpoint' encountered
> [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:105) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.server.parsing.CommonXml.parseSocketBindingGroupRef(CommonXml.java:682) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.parseServerGroups(DomainXml.java:753) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.readDomainElement1_4(DomainXml.java:432) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.readElement(DomainXml.java:140) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.readElement(DomainXml.java:110) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] ... 3 more
> [Host Controller]
> [Host Controller] 08:36:35,162 FATAL [org.jboss.as.host.
> {noformat}
--
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 years, 9 months
[JBoss JIRA] (AS7-6226) Illegal domain configuration
by Heiko Braun (JIRA)
Heiko Braun created AS7-6226:
--------------------------------
Summary: Illegal domain configuration
Key: AS7-6226
URL: https://issues.jboss.org/browse/AS7-6226
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.2.0.Alpha1
Not sure which operation created the 'management-subsystem-endpoint' attribute. but it sneaked during a create/copy operation somehow.
{noformat}
[Host Controller] Message: JBAS014788: Unexpected attribute 'management-subsystem-endpoint' encountered
[Host Controller] at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:105) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.server.parsing.CommonXml.parseSocketBindingGroupRef(CommonXml.java:682) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.parseServerGroups(DomainXml.java:753) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.readDomainElement1_4(DomainXml.java:432) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.readElement(DomainXml.java:140) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.DomainXml.readElement(DomainXml.java:110) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
[Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
[Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] ... 3 more
[Host Controller]
[Host Controller] 08:36:35,162 FATAL [org.jboss.as.host.
{noformat}
--
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 years, 9 months
[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating runtime-exception
by Barnabas Bodnar (JIRA)
[ https://issues.jboss.org/browse/AS7-5432?page=com.atlassian.jira.plugin.s... ]
Barnabas Bodnar updated AS7-5432:
---------------------------------
Git Pull Request: https://github.com/jbossas/jboss-as/pull/3719, https://github.com/jbossas/jboss-as/pull/3718 (was: https://github.com/jbossas/jboss-as/pull/3004, https://github.com/jbossas/jboss-as/pull/3003)
> TransactionRolledbackLocalException doesn't reference the originating runtime-exception
> ---------------------------------------------------------------------------------------
>
> Key: AS7-5432
> URL: https://issues.jboss.org/browse/AS7-5432
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP)
> Reporter: Barnabas Bodnar
> Assignee: jaikiran pai
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> If a runtime-exception thrown by an EJB v2.x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()).
> The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here.
> This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException().
--
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 years, 9 months
[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating runtime-exception
by Barnabas Bodnar (JIRA)
[ https://issues.jboss.org/browse/AS7-5432?page=com.atlassian.jira.plugin.s... ]
Barnabas Bodnar commented on AS7-5432:
--------------------------------------
New pull requests: https://github.com/jbossas/jboss-as/pull/3719, https://github.com/jbossas/jboss-as/pull/3718
> TransactionRolledbackLocalException doesn't reference the originating runtime-exception
> ---------------------------------------------------------------------------------------
>
> Key: AS7-5432
> URL: https://issues.jboss.org/browse/AS7-5432
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP)
> Reporter: Barnabas Bodnar
> Assignee: jaikiran pai
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> If a runtime-exception thrown by an EJB v2.x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()).
> The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here.
> This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException().
--
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 years, 9 months
[JBoss JIRA] (JBJCA-952) JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor
by James Livingston (JIRA)
[ https://issues.jboss.org/browse/JBJCA-952?page=com.atlassian.jira.plugin.... ]
James Livingston updated JBJCA-952:
-----------------------------------
Description:
The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should
1) return itself or a proxy when the reicever implements the interface
2) return the wrapped object or a proxy when the wrapped object implements the interface
3) call the wrapped object's unwrap() method if the receiver is a wrapper
4) other throw a SQL exception
JBossWrapper only does 2 and 4.
This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection.
was:
The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should
1) return itself or a proxy when the reicever implements the interface
2) return the wrapped object or a proxy when the wrapped object implements the interface
3) call the wrapp object's unwrap() method if the receiver is a wrapper
4) other throw a SQL exception
JBossWrapper only does 2 and 4.
This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection.
> JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor
> ------------------------------------------------------------------------
>
> Key: JBJCA-952
> URL: https://issues.jboss.org/browse/JBJCA-952
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Reporter: James Livingston
> Assignee: Jesper Pedersen
>
> The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should
> 1) return itself or a proxy when the reicever implements the interface
> 2) return the wrapped object or a proxy when the wrapped object implements the interface
> 3) call the wrapped object's unwrap() method if the receiver is a wrapper
> 4) other throw a SQL exception
> JBossWrapper only does 2 and 4.
> This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection.
--
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 years, 9 months
[JBoss JIRA] (JBJCA-952) JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor
by James Livingston (JIRA)
James Livingston created JBJCA-952:
--------------------------------------
Summary: JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor
Key: JBJCA-952
URL: https://issues.jboss.org/browse/JBJCA-952
Project: IronJacamar
Issue Type: Bug
Components: JDBC
Reporter: James Livingston
Assignee: Jesper Pedersen
The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should
1) return itself or a proxy when the reicever implements the interface
2) return the wrapped object or a proxy when the wrapped object implements the interface
3) call the wrapp object's unwrap() method if the receiver is a wrapper
4) other throw a SQL exception
JBossWrapper only does 2 and 4.
This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection.
--
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 years, 9 months
[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)
by Alvin Thompson (JIRA)
[ https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s... ]
Alvin Thompson commented on AS7-6068:
-------------------------------------
The enhancement which implemented the "use-physical-code-source" attribute (AS7-308) specifically states that it does not fix this issue, but I'll give it a try sometime when I have some free time.
> jar file system is broken again (regression)
> --------------------------------------------
>
> Key: AS7-6068
> URL: https://issues.jboss.org/browse/AS7-6068
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.1.Final
> Reporter: Alvin Thompson
> Assignee: JBoss SET
> Priority: Critical
>
> Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always.
> This was supposedly fixed in previous versions, but it's back in 7.
--
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 years, 9 months
[JBoss JIRA] (AS7-6225) MessagingSubsystemParser swallows exceptions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6225?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6225:
----------------------------------
Attachment: AS7-6225.patch
> MessagingSubsystemParser swallows exceptions
> --------------------------------------------
>
> Key: AS7-6225
> URL: https://issues.jboss.org/browse/AS7-6225
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Attachments: AS7-6225.patch
>
>
> In numerous places, MessagingSubsystemParser calls ParseUtils.missingRequired but does not throw the returned exception.
> I'll attach a patch showing all the places where Intellij reported this. I'd just send a pull request, but when I run with this patch, the messaging module testsuite has failures and I don't have time today to investigate.
--
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 years, 9 months