[JBoss JIRA] (DROOLS-1013) Error jitting a compareTo constraint
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1013?page=com.atlassian.jira.plugi... ]
Mario Fusco closed DROOLS-1013.
-------------------------------
Fix Version/s: 6.4.x
Resolution: Done
Fixed by https://github.com/droolsjbpm/drools/commit/a01c0f684
> Error jitting a compareTo constraint
> ------------------------------------
>
> Key: DROOLS-1013
> URL: https://issues.jboss.org/browse/DROOLS-1013
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
>
> When the implementation of the Comparable interface is not directly declared by a Class, but the Class implements another interface that transitively extends Comparable the jitting of a constraint doing a compareTo on that class fails with the following exception:
> {code}
> Exception in thread "Thread-0" java.lang.NoSuchMethodError: java.time.LocalDateTime.compareTo(Ljava/time/LocalDateTimeI
> at ConditionEvaluator8566b06b2be943a7ba50f1700fa7b033.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:248)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (SECURITY-930) A security-domain can only load login-modules from a single JBoss module
by Derek Horton (JIRA)
Derek Horton created SECURITY-930:
-------------------------------------
Summary: A security-domain can only load login-modules from a single JBoss module
Key: SECURITY-930
URL: https://issues.jboss.org/browse/SECURITY-930
Project: PicketBox
Issue Type: Bug
Components: JBossSX, Security-SPI
Reporter: Derek Horton
Assignee: Stefan Guilhen
A security-domain can only load login-modules from a single JBoss module. Even though the security-domain configuration will allow each login module defined within a single security-domain to have a "module" attribute, the only module that is used to load the login-modules is the last "module" attribute that the parsing system locates.
For example, with the following configuration, it looks like "org.jboss.example.CustomLoginModule" should be loaded from the "org.jboss.example" jboss-module and "org.jboss.example.CustomBaseCertLoginModule" should be loaded from the "org.jboss.another.example" jboss-module:
<security-domain name="jmx-console" cache-type="default">
<authentication>
<login-module code="org.jboss.example.CustomLoginModule" module="org.jboss.example" flag="required">
<module-option name="usersProperties" value="${jboss.server.config.dir}/users.properties"/>
<module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/>
</login-module>
<login-module code="org.jboss.example.CustomBaseCertLoginModule" module="org.jboss.another.example" flag="required">
<module-option name="usersProperties" value="${jboss.server.config.dir}/users.properties"/>
<module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/>
</login-module>
</authentication>
</security-domain>
Unfortunately, it does not work like this. Only the "org.jboss.another.example" jboss-module is used to load the custom login modules.
There seems to be two issues. 1) The security subsystem code only "remembers" the last module that is defined within a single security domain. 2) I think issue #1 is happening because the JBoss authentication code (org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate()) defers to the JVM's login module handling code. The JVM appears to treat the login modules as one atomic until and so a single classloader is set and then the JVM login module code is invoked to handle the authentication requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1239) Embedded API is confusing re process types
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1239?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1239:
-------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1320
> Embedded API is confusing re process types
> ------------------------------------------
>
> Key: WFCORE-1239
> URL: https://issues.jboss.org/browse/WFCORE-1239
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.4.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.0.5.Final
>
>
> The embedded API has gotten a bit confusing with respect to names and types, primarily the use of the word "server" in a number of placing where the relevant thing could either be an embedded standalone server or an embedded host controller.
> Originally I saw this module as just being an internal implementation detail for the CLI, used by the offline CLI feature, but now we've opened it up for use by things like Arquillian's WildFly integration, so I want to clean this API up a bit.
> I see two minor breaking changes needed:
> 1) The HostController interface has an odd "public HostController getHostController()" method that logically would only return 'this'. I could keep this but it's not needed and I'd rather get rid of it.
> 2) The HostController interface's start() method does not throw a checked exception, while the equivalent start() on StandaloneServer does. To do anything coherent I need to unify the exception handling. HostController is extremely unlikely to be used outside wf core, while StandaloneServer is used, and removing a checked exception from StandaloneServer would be a breaking change or any user that catches it, so instead I will add the exception to HostController.start().
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-1012) kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1012?page=com.atlassian.jira.plugi... ]
Mario Fusco closed DROOLS-1012.
-------------------------------
Fix Version/s: 6.4.x
Resolution: Done
Fixed by https://github.com/droolsjbpm/drools/commit/e48ee1730
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1012
> URL: https://issues.jboss.org/browse/DROOLS-1012
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
> Attachments: brms-fuse-integration-master.tgz
>
>
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry. This implies that when the KieContainer is created in a OSGi environment it is not able to get an instance of the MavenClassLoaderResolver and then cannot create a ClassLoader including all the transitive dependencies of the kjar to be compiled.
> The attached project reproduces this issue. In order to run it, it's enough to do a mvn clean install of the project and issue the following commands in fuse:
> features:addurl mvn:com.redhat/brms-fuse-integration-features/0.0.1-SNAPSHOT/xml/features
> features:install brms-integration-bundle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-1013) Error jitting a compareTo constraint
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-1013:
-----------------------------------
Summary: Error jitting a compareTo constraint
Key: DROOLS-1013
URL: https://issues.jboss.org/browse/DROOLS-1013
Project: Drools
Issue Type: Bug
Reporter: Mario Fusco
Assignee: Mario Fusco
When the implementation of the Comparable interface is not directly declared by a Class, but the Class implements another interface that transitively extends Comparable the jitting of a constraint doing a compareTo on that class fails with the following exception:
{code}
Exception in thread "Thread-0" java.lang.NoSuchMethodError: java.time.LocalDateTime.compareTo(Ljava/time/LocalDateTimeI
at ConditionEvaluator8566b06b2be943a7ba50f1700fa7b033.evaluate(Unknown Source)
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:248)
at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5889) Add journal-pool-files attribute
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-5889:
---------------------------------
Summary: Add journal-pool-files attribute
Key: WFLY-5889
URL: https://issues.jboss.org/browse/WFLY-5889
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 10.0.0.CR5
Artemis 1.1.0.wildfly-010 has a new attribute journal-pool-files that must be added to the server resource definition
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-965) "Writes closed" when deploying application in domain
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-965?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFCORE-965.
-------------------------------------
Resolution: Rejected
Turns out this was an environmental issue in the test lab; see recent comments on JBEAP-1042.
> "Writes closed" when deploying application in domain
> ----------------------------------------------------
>
> Key: WFCORE-965
> URL: https://issues.jboss.org/browse/WFCORE-965
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.Beta6
> Environment: domain
> profile=default
> 1x domain controller without servers
> 3x slave, 10 servers each
> Reporter: Martin Simka
> Assignee: Brian Stansberry
>
> Some of our tests for large domain sometimes fail with error: "Writes closed". It happens only with some higher number of servers per host.
> {noformat}
> Failed response:
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-3" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {
> "server-group-A" => {"host" => {
> "perf31" => {
> "perf31-server-3" => "Writes closed",
> "perf31-server-5" => "Writes closed"
> },
> "perf33" => {"perf33-server-3" => "Writes closed"}
> }},
> "server-group-B" => {"host" => {"perf32" => {
> "perf32-server-2" => "Writes closed",
> "perf32-server-6" => "Writes closed"
> }}}
> }}},
> "rolled-back" => true,
> "server-groups" => {
> "server-group-A" => {"host" => {
> "perf31" => {
> "perf31-server-1" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf31-server-3" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "Writes closed",
> "rolled-back" => true
> }},
> "perf31-server-5" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "Writes closed",
> "rolled-back" => true
> }},
> "perf31-server-7" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf31-server-9" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }}
> },
> "perf32" => {
> "perf32-server-1" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf32-server-3" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => undefined,
> "rolled-back" => true
> }},
> "perf32-server-5" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf32-server-7" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf32-server-9" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }}
> },
> "perf33" => {
> "perf33-server-1" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-3" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "Writes closed",
> "rolled-back" => true
> }},
> "perf33-server-5" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-7" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-9" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }}
> }
> }},
> "server-group-B" => {"host" => {
> "perf31" => {
> "perf31-server-10" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf31-server-2" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => undefined,
> "rolled-back" => true
> }},
> "perf31-server-4" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => undefined,
> "rolled-back" => true
> }},
> "perf31-server-6" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf31-server-8" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }}
> },
> "perf32" => {
> "perf32-server-10" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf32-server-2" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "Writes closed",
> "rolled-back" => true
> }},
> "perf32-server-4" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => undefined,
> "rolled-back" => true
> }},
> "perf32-server-6" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "Writes closed",
> "rolled-back" => true
> }},
> "perf32-server-8" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }}
> },
> "perf33" => {
> "perf33-server-10" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-2" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-4" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-6" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }},
> "perf33-server-8" => {"response" => {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> }},
> "failure-description" => "WFLYCTL0063: Composite operation was rolled back",
> "rolled-back" => true
> }}
> }
> }}
> }
> }
> {noformat}
> I know this isn't detailed bug report, I didn't find easy way to reproduce it, other than running large domain tests. Tests are modified tests from https://github.com/wildfly/wildfly/blob/master/testsuite/domain/src/test/... .
> I can provide other logs, outputs ...., just let me know which log categories would help.
> Also I tried to play a bit with remoting's HEARTBEAT interval (through subsystem configuration), but that doesn't help.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5543) Can't recover transaction started by MDB on WSMQ when RAR is deployed as an archive
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFLY-5543?page=com.atlassian.jira.plugin.... ]
Amos Feng reopened WFLY-5543:
-----------------------------
The similar errors is still shown for JTS
> Can't recover transaction started by MDB on WSMQ when RAR is deployed as an archive
> -----------------------------------------------------------------------------------
>
> Key: WFLY-5543
> URL: https://issues.jboss.org/browse/WFLY-5543
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Transactions
> Affects Versions: 10.0.0.CR2
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Fix For: 10.0.0.CR5
>
> Attachments: standalone-full.wmq.xml, tx-object-store.zip
>
>
> There is a problem with recovering transaction started by MDB pointing to a WSMQ JMS resource.
> If I do so then the recovery process fails with [1]
> {code}WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016043: Exception on attempting to restore XAResource: java.lang.ClassNotFoundException: com.ibm.mq.connector.xa.XARWrapper from [Module "org.jboss.jts:main" from local module loader @707f7052 (finder: local module finder @11028347 (roots: /home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/modules,/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:626)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.restore_state(XAResourceRecord.java:969)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.restore_state(BasicAction.java:1118)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:488)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:451)
> at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.<init>(RecoverAtomicAction.java:50)
> at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecoveryModule.java:149)
> at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.processTransactionsStatus(AtomicActionRecoveryModule.java:253)
> at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.periodicWorkSecondPass(AtomicActionRecoveryModule.java:109)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012154: RecoverAtomicAction: transaction 0:ffff0a28048f:-470895ed:5624c495:34 not activated, unable to replay phase 2 commit. Check state has not already been completed.
> InputObjectState Type : /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> InputObjectState Size : 7204
> InputObjectState Buffer: )
> WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012379: ExpiredTransactionScanner - 0:ffff0a28048f:-470895ed:5624c495:34 is assumed complete and will be moved.
> {code}
> This means that instead of commiting the unfinished transaction the txn log is put to expired part of txn object store and the transaction on wsmq broker side is left in-doubt.
> I'm attaching my configuration file.
> [1] trace level on transaction manager log category
> {code}
> WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016043: Exception on attempting to restore XAResource: java.lang.ClassNotFoundException: com.ibm.mq.connector.xa.XARWrapper from [Module "org.jboss.jts:main" from local module loader @707f7052 (finder: local module finder @11028347 (roots: /home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/modules,/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:626)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.restore_state(XAResourceRecord.java:969)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.restore_state(BasicAction.java:1118)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:488)
> at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:451)
> at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.<init>(RecoverAtomicAction.java:50)
> at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecoveryModule.java:149)
> at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.processTransactionsStatus(AtomicActionRecoveryModule.java:253)
> at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.periodicWorkSecondPass(AtomicActionRecoveryModule.java:109)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) RecoverAtomicAction.replayPhase2 recovering 0:ffff0a28048f:-470895ed:5624c495:34 ActionStatus is ActionStatus.COMMITTED
> WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012154: RecoverAtomicAction: transaction 0:ffff0a28048f:-470895ed:5624c495:34 not activated, unable to replay phase 2 commit. Check state has not already been completed.
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) StateManager::StateManager( 2, 0 )
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) BasicAction::BasicAction()
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.read_committed(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.read_state(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_SHADOW)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, 10)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, 11)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.currentState(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction) - returning StateStatus.OS_COMMITTED
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, 11)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.openAndLock(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a28048f_-470895ed_5624c495_34, FileLock.F_RDLCK, false)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) InputObjectState::InputObjectState(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.closeAndUnlock(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a28048f_-470895ed_5624c495_34, java.io.FileInputStream@13c3edbd, null)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) OutputObjectState::OutputObjectState(InputObjectState Uid : 0:ffff0a28048f:-470895ed:5624c495:34
> InputObjectState Type : /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> InputObjectState Size : 7204
> InputObjectState Buffer: )
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.write_committed(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.write_state(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired, 11)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.openAndLock(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired/0_ffff0a28048f_-470895ed_5624c495_34, FileLock.F_WRLCK, true)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.createHierarchy(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired/0_ffff0a28048f_-470895ed_5624c495_34)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.closeAndUnlock(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired/0_ffff0a28048f_-470895ed_5624c495_34, null, java.io.FileOutputStream@322aab6a)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.remove_committed(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.remove_state(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_SHADOW)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, 10)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, 11)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.currentState(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction) - returning StateStatus.OS_COMMITTED
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) ShadowingStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, StateType.OS_ORIGINAL)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.genPathName(0:ffff0a28048f:-470895ed:5624c495:34, /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction, 11)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.openAndLock(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a28048f_-470895ed_5624c495_34, FileLock.F_WRLCK, false)
> TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) FileSystemStore.closeAndUnlock(/home/ochaloup/jboss/jboss-eap-7.0.0.DR11-wsmq2/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a28048f_-470895ed_5624c495_34, null, null)
> WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012379: ExpiredTransactionScanner - 0:ffff0a28048f:-470895ed:5624c495:34 is assumed complete and will be moved.
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
> DEBUG [com.arjuna.ats.txoj] (Periodic Recovery) TORecoveryModule - second pass
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) XARecoveryModule state change BETWEEN_PASSES->SECOND_PASS
> DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Local XARecoveryModule - second pass
> DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Local XARecoveryModule.transactionInitiatedRecovery completed
> DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Local XARecoveryModule.resourceInitiatedRecovery completed
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) XARecoveryModule state change SECOND_PASS->IDLE
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread Status <== INACTIVE
> DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread backing off
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months