December 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2577) CDR Input/Output streams need SerializablePermission("enableSubclassImplementation") when Security Manager is in force

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-2577: ----------------------------------- Summary: CDR Input/Output streams need SerializablePermission("enableSubclassImplementation") when Security Manager is in force Key: JBTM-2577 URL: https://issues.jboss.org/browse/JBTM-2577 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.2.8.Final Reporter: Ivo Studensky Assignee: Ivo Studensky Since JDK 7u25 version {{org.omg.CORBA_2_3.portable.Output/InputStream}} classes need extra permissions if Security Manager is enabled. Because of a previous vulnerability, it now checks {{SerializablePermission("enableSubclassImplementation")}}. There is a property flag to allow subclass instantiations without the security check ({{jdk.corba.allowOutputStreamSubclass=true}}), but this system property is subject to removal in the future Java releases, according to my findings. At the moment, our IIOP code fails (can be seen in iiop tests of WildFly testsuite) when running with SM enabled. See the following stacktraces: {noformat} at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:271) at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) at org.omg.CORBA_2_3.portable.InputStream.checkPermission(InputStream.java:67) at org.omg.CORBA_2_3.portable.InputStream.<init>(InputStream.java:84) at com.sun.corba.se.impl.encoding.WrapperInputStream.<init>(WrapperInputStream.java:74) at com.sun.corba.se.impl.corba.TypeCodeImpl.read_value(TypeCodeImpl.java:1273) at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_any(CDRInputStream_1_0.java:695) at com.sun.corba.se.impl.encoding.CDRInputStream.read_any(CDRInputStream.java:238) at org.omg.CosTransactions.PropagationContextHelper.read(PropagationContextHelper.java:88) at com.arjuna.ArjunaOTS._ArjunaTransactionStub.get_txcontext(_ArjunaTransactionStub.java:387) at com.arjuna.ats.jts.orbspecific.javaidl.interceptors.interposition.InterpositionClientRequestInterceptorImpl.send_request(InterpositionClientRequestInterceptorImpl.java:223) at com.sun.corba.se.impl.interceptors.InterceptorInvoker.invokeClientInterceptorStartingPoint(InterceptorInvoker.java:245) at com.sun.corba.se.impl.interceptors.PIHandlerImpl.invokeClientPIStartingPoint(PIHandlerImpl.java:355) at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:293) at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:137) at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:449) at org.omg.CosTransactions._ResourceStub.commit_one_phase(_ResourceStub.java:94) at com.arjuna.ats.internal.jts.resources.ResourceRecord.topLevelOnePhaseCommit(ResourceRecord.java:537) at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2361) at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1495) - locked <0x360a> (a com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:375) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:244) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1313) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) at org.jboss.as.test.iiop.transaction.ClientEjb.testSynchronization(ClientEjb.java:65) {noformat} {noformat} at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:271) at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) at org.omg.CORBA_2_3.portable.InputStream.checkPermission(InputStream.java:67) at org.omg.CORBA_2_3.portable.InputStream.<init>(InputStream.java:84) at com.sun.corba.se.impl.encoding.WrapperInputStream.<init>(WrapperInputStream.java:74) at com.sun.corba.se.impl.corba.TypeCodeImpl.read_value(TypeCodeImpl.java:1273) at com.sun.corba.se.impl.corba.TypeCodeImpl.copy(TypeCodeImpl.java:2018) at com.sun.corba.se.impl.corba.TypeCodeImpl.copy(TypeCodeImpl.java:2054) at com.sun.corba.se.impl.corba.AnyImpl.write_value(AnyImpl.java:610) at com.sun.corba.se.impl.interceptors.CDREncapsCodec.encodeImpl(CDREncapsCodec.java:173) at com.sun.corba.se.impl.interceptors.CDREncapsCodec.encode_value(CDREncapsCodec.java:119) at com.arjuna.ats.jts.orbspecific.javaidl.interceptors.interposition.InterpositionClientRequestInterceptorImpl.send_request(InterpositionClientRequestInterceptorImpl.java:280) at com.sun.corba.se.impl.interceptors.InterceptorInvoker.invokeClientInterceptorStartingPoint(InterceptorInvoker.java:245) at com.sun.corba.se.impl.interceptors.PIHandlerImpl.invokeClientPIStartingPoint(PIHandlerImpl.java:355) at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:293) at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:137) at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:449) at com.arjuna.ArjunaOTS._ArjunaTransactionStub.is_top_level_transaction(_ArjunaTransactionStub.java:193) at com.arjuna.ats.jts.OTSManager.destroyControl(OTSManager.java:133) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.destroyAction(ArjunaTransactionImple.java:2201) at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.commit(ArjunaTransactionImple.java:392) at com.arjuna.ats.internal.jts.ControlWrapper.commit(ControlWrapper.java:244) at com.arjuna.ats.internal.jts.orbspecific.CurrentImple.commit(CurrentImple.java:247) at com.arjuna.ats.jts.extensions.AtomicTransaction.commit(AtomicTransaction.java:276) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.commitAndDisassociate(TransactionImple.java:1313) at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.commit(BaseTransaction.java:130) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) at org.jboss.as.test.iiop.transaction.ClientEjb.testSynchronization(ClientEjb.java:65) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2517: ----------------------------------- Git Pull Request: https://github.com/jbosstm/performance/pull/30 (was: https://github.com/jbosstm/performance/pull/29) > Update the Narayana Release Process doc to include performance figures > ---------------------------------------------------------------------- > > Key: JBTM-2517 > URL: https://issues.jboss.org/browse/JBTM-2517 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, Release Process > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2576) Fix build.bat to work with updated Maven

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2576?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2576: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix build.bat to work with updated Maven > ---------------------------------------- > > Key: JBTM-2576 > URL: https://issues.jboss.org/browse/JBTM-2576 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2576) Fix build.bat to work with updated Maven

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2576?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2576: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/956 > Fix build.bat to work with updated Maven > ---------------------------------------- > > Key: JBTM-2576 > URL: https://issues.jboss.org/browse/JBTM-2576 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2576) Fix build.bat to work with updated Maven

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2576: ------------------------------------- Summary: Fix build.bat to work with updated Maven Key: JBTM-2576 URL: https://issues.jboss.org/browse/JBTM-2576 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Critical Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2561) XTS code coverage failures

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.... ] Amos Feng edited comment on JBTM-2561 at 12/3/15 3:05 AM: ---------------------------------------------------------- It looks like that the maven your updated changes the tools/maven/bin/mvn.bat to mvn.cmd. This cause the build.bat does not work. I think it should be fixed by instead of "mvn.cmd" in build.bat see the failure windows build http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/... was (Author: zhfeng): It looks like that the maven your updated changes the tools/maven/bin/mvn.bat to mvn.cmd. This cause the build.bat does not work. I think it should be fixed by instead of "mvn.cmd" in build.bat > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2561) XTS code coverage failures

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2561: --------------------------------- It looks like that the maven your updated changes the tools/maven/bin/mvn.bat to mvn.cmd. This cause the build.bat does not work. I think it should be fixed by instead of "mvn.cmd" in build.bat > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2575) When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2575?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2575: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/955 > When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2575 > URL: https://issues.jboss.org/browse/JBTM-2575 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.31, 5.later > > > There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g. > a->b b->c > When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b". > This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2575) When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2575: ----------------------------------- Summary: When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back Key: JBTM-2575 URL: https://issues.jboss.org/browse/JBTM-2575 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Reporter: Tom Jenkinson Priority: Blocker Fix For: 4.17.31, 5.later There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g. a->b b->c When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b". This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2561) XTS code coverage failures

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2561: --------------------------------------- It possibly is, but I merged the fix after that failure. Lets see how will http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-codeCove... finish. > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2015