[JBoss JIRA] (WFLY-10834) Load provider settings is not taken into account in mod_cluster subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10834?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10834:
----------------------------------
Fix Version/s: 14.0.0.CR1
> Load provider settings is not taken into account in mod_cluster subsystem
> -------------------------------------------------------------------------
>
> Key: WFLY-10834
> URL: https://issues.jboss.org/browse/WFLY-10834
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: No Release
> Environment: Latest nightly from ci.wildfly.org
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 14.0.0.CR1
>
>
> Everything works in version with old subsytem with this settings (load is properly reported to balancer):
> {code:xml}
> <subsystem
> xmlns="urn:jboss:domain:modcluster:3.0">
> <mod-cluster-config advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp">
> <dynamic-load-provider>
> <load-metric type="cpu"/>
> </dynamic-load-provider>
> </mod-cluster-config>
> </subsystem>
> {code}
> Same configuration for latest snapshot doesn't work (load remains at 1):
> {code:xml}
> <subsystem
> xmlns="urn:jboss:domain:modcluster:4.0">
> <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp">
> <dynamic-load-provider>
> <load-metric type="cpu" weight="1"/>
> </dynamic-load-provider>
> </proxy>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10834) Load provider settings is not taken into account in mod_cluster subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10834?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10834:
----------------------------------
Priority: Blocker (was: Critical)
> Load provider settings is not taken into account in mod_cluster subsystem
> -------------------------------------------------------------------------
>
> Key: WFLY-10834
> URL: https://issues.jboss.org/browse/WFLY-10834
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: No Release
> Environment: Latest nightly from ci.wildfly.org
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> Everything works in version with old subsytem with this settings (load is properly reported to balancer):
> {code:xml}
> <subsystem
> xmlns="urn:jboss:domain:modcluster:3.0">
> <mod-cluster-config advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp">
> <dynamic-load-provider>
> <load-metric type="cpu"/>
> </dynamic-load-provider>
> </mod-cluster-config>
> </subsystem>
> {code}
> Same configuration for latest snapshot doesn't work (load remains at 1):
> {code:xml}
> <subsystem
> xmlns="urn:jboss:domain:modcluster:4.0">
> <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp">
> <dynamic-load-provider>
> <load-metric type="cpu" weight="1"/>
> </dynamic-load-provider>
> </proxy>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-83) [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
by Martyn Taylor (JIRA)
[ https://issues.jboss.org/browse/WFWIP-83?page=com.atlassian.jira.plugin.s... ]
Martyn Taylor edited comment on WFWIP-83 at 8/14/18 4:36 AM:
-------------------------------------------------------------
I've added a configuration option to enable the old support. Jeff you will need to enable this option in the ConnectionFactoryConfiguration objects
See: https://github.com/mtaylor/wildfly/commit/87decdde58da98aff59b51b503c77ad...
Artemis PR: https://github.com/apache/activemq-artemis/pull/2246
was (Author: martyn-taylor):
https://github.com/apache/activemq-artemis/pull/2246
> [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-83
> URL: https://issues.jboss.org/browse/WFWIP-83
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> There is regression TCK 7 when running WF/EAP with Artemis 2.x resource adapter against AMQ 7.2.0.GA. WF/EAP with Artemis 2.x is last build from [2018-08-06]:
> https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
> There are approximately 200 failures with exception:
> {code}
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) 08-03-2018 09:55:10: SVR-ERROR: javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.validateClientID(ActiveMQConnection.java:266)
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:681)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:849)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXATopicConnection(ActiveMQConnectionFactory.java:387)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:745)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.<init>(ActiveMQRAManagedConnection.java:161)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(Semaphor
> eConcurrentLinkedDequeManagedConnectionPool.java:1326)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinke
> dDequeManagedConnectionPool.java:499)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
> [javatest.batch] ESC[0mESC[0m09:55:10,606 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.allocateConnection(ActiveMQRASessionFactoryImpl.java:872)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:531)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:746)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:751)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.validateUser(ActiveMQRAConnectionFactoryImpl.java:475)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.createTopicConnection(ActiveMQRAConnectionFactoryImpl.java:217)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.testInitForT(TransactionTests.java:354)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.Test06(TransactionTests.java:634)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at java.lang.reflect.Method.invoke(Method.java:498)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.EETest.run(EETest.java:550)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:113)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.tests.common.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:70)
> {code}
> Note that TCK 7 is passing when trying with current Wildfly master (Artemis 1.5.5.012).
> Link to TCK 7 job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-third-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10836) mod_cluster uses wrong password for credential stores (regression after removing lambdas)
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10836?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10836:
----------------------------------
Fix Version/s: 14.0.0.CR1
> mod_cluster uses wrong password for credential stores (regression after removing lambdas)
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10836
> URL: https://issues.jboss.org/browse/WFLY-10836
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 12.0.0.Final, 13.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> Uncovered by [~jkasik].
> Credential stores are opened with wrong password. Regression caused by WFLY-9613 [1].
> {code}
> 09:43:29,686 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.IllegalStateException: java.io.IOException: Keystore was tampered with, or password was incorrect
> at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:113)
> at org.wildfly.extension.mod_cluster.ProxyConfigurationServiceConfigurator.configure(ProxyConfigurationServiceConfigurator.java:315)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.installServices(ModClusterSubsystemServiceHandler.java:79)
> at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:179)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:338)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:780)
> at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:56)
> at sun.security.provider.KeyStoreDelegator.engineLoad(KeyStoreDelegator.java:224)
> at sun.security.provider.JavaKeyStore$DualFormatJKS.engineLoad(JavaKeyStore.java:70)
> at java.security.KeyStore.load(KeyStore.java:1445)
> at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getStore(JSSESocketFactory.java:230)
> at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeystore(JSSESocketFactory.java:179)
> at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:251)
> at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:98)
> ... 15 more
> Caused by: java.security.UnrecoverableKeyException: Password verification failed
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:778)
> ... 23 more
> {code}
> [1] https://github.com/wildfly/wildfly/pull/10708/files#diff-fabeb2ec71da4fca...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-83) [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
by Martyn Taylor (JIRA)
[ https://issues.jboss.org/browse/WFWIP-83?page=com.atlassian.jira.plugin.s... ]
Martyn Taylor commented on WFWIP-83:
------------------------------------
https://github.com/apache/activemq-artemis/pull/2246
> [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-83
> URL: https://issues.jboss.org/browse/WFWIP-83
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> There is regression TCK 7 when running WF/EAP with Artemis 2.x resource adapter against AMQ 7.2.0.GA. WF/EAP with Artemis 2.x is last build from [2018-08-06]:
> https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
> There are approximately 200 failures with exception:
> {code}
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) 08-03-2018 09:55:10: SVR-ERROR: javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.validateClientID(ActiveMQConnection.java:266)
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:681)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:849)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXATopicConnection(ActiveMQConnectionFactory.java:387)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:745)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.<init>(ActiveMQRAManagedConnection.java:161)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(Semaphor
> eConcurrentLinkedDequeManagedConnectionPool.java:1326)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinke
> dDequeManagedConnectionPool.java:499)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
> [javatest.batch] ESC[0mESC[0m09:55:10,606 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.allocateConnection(ActiveMQRASessionFactoryImpl.java:872)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:531)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:746)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:751)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.validateUser(ActiveMQRAConnectionFactoryImpl.java:475)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.createTopicConnection(ActiveMQRAConnectionFactoryImpl.java:217)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.testInitForT(TransactionTests.java:354)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.Test06(TransactionTests.java:634)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at java.lang.reflect.Method.invoke(Method.java:498)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.EETest.run(EETest.java:550)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:113)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.tests.common.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:70)
> {code}
> Note that TCK 7 is passing when trying with current Wildfly master (Artemis 1.5.5.012).
> Link to TCK 7 job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-third-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10836) mod_cluster uses wrong password for credential stores (regression after removing lambdas)
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-10836:
-------------------------------------
Summary: mod_cluster uses wrong password for credential stores (regression after removing lambdas)
Key: WFLY-10836
URL: https://issues.jboss.org/browse/WFLY-10836
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 13.0.0.Final, 12.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Blocker
Uncovered by [~jkasik].
Credential stores are opened with wrong password. Regression caused by WFLY-9613 [1].
{code}
09:43:29,686 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.IllegalStateException: java.io.IOException: Keystore was tampered with, or password was incorrect
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:113)
at org.wildfly.extension.mod_cluster.ProxyConfigurationServiceConfigurator.configure(ProxyConfigurationServiceConfigurator.java:315)
at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.installServices(ModClusterSubsystemServiceHandler.java:79)
at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:179)
at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:338)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:780)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:56)
at sun.security.provider.KeyStoreDelegator.engineLoad(KeyStoreDelegator.java:224)
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineLoad(JavaKeyStore.java:70)
at java.security.KeyStore.load(KeyStore.java:1445)
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getStore(JSSESocketFactory.java:230)
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeystore(JSSESocketFactory.java:179)
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:251)
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:98)
... 15 more
Caused by: java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:778)
... 23 more
{code}
[1] https://github.com/wildfly/wildfly/pull/10708/files#diff-fabeb2ec71da4fca...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10835) Connection factory with discovery-group doesn't work
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFLY-10835?page=com.atlassian.jira.plugin... ]
Martin Styk updated WFLY-10835:
-------------------------------
Attachment: server-trace.log
> Connection factory with discovery-group doesn't work
> ----------------------------------------------------
>
> Key: WFLY-10835
> URL: https://issues.jboss.org/browse/WFLY-10835
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: server-trace.log, standalone-full-ha.xml
>
>
> Jms client can not use remote connection factory defined as follows
> {noformat}
> <discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" discovery-group="dg-group1" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
> {noformat}
> Following exception is thrown on client
> {noformat}
> Exception in thread "main" java.lang.RuntimeException: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at client.ProducerJms11.sendMessages(ProducerJms11.java:67)
> at client.Producer.run(Producer.java:34)
> at client.Producer.sendAllSync(Producer.java:25)
> at client.ProducerJms11.main(ProducerJms11.java:14)
> Caused by: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:261)
> at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
> at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
> at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
> at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at client.ProducerJms11.sendMessages(ProducerJms11.java:43)
> ... 3 more
> Caused by: java.io.EOFException: Read past end of file
> at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUnsignedByte(BlockUnmarshaller.java:258)
> at org.jboss.marshalling.river.BlockUnmarshaller.readInt(BlockUnmarshaller.java:296)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUTF(BlockUnmarshaller.java:326)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.readExternal(ActiveMQConnectionFactory.java:186)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1414)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
> ... 15 more
> Caused by: an exception which occurred:
> in object of type org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
> {noformat}
> It fails on attempt to look up RemoteCF
> {noformat}
> ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(ClientDefaults.CONNECTION_FACTORY);
> {noformat}
> Same scenario with connector works well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10835) Connection factory with discovery-group doesn't work
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFLY-10835?page=com.atlassian.jira.plugin... ]
Martin Styk updated WFLY-10835:
-------------------------------
Attachment: standalone-full-ha.xml
> Connection factory with discovery-group doesn't work
> ----------------------------------------------------
>
> Key: WFLY-10835
> URL: https://issues.jboss.org/browse/WFLY-10835
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: server-trace.log, standalone-full-ha.xml
>
>
> Jms client can not use remote connection factory defined as follows
> {noformat}
> <discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" discovery-group="dg-group1" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
> {noformat}
> Following exception is thrown on client
> {noformat}
> Exception in thread "main" java.lang.RuntimeException: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at client.ProducerJms11.sendMessages(ProducerJms11.java:67)
> at client.Producer.run(Producer.java:34)
> at client.Producer.sendAllSync(Producer.java:25)
> at client.ProducerJms11.main(ProducerJms11.java:14)
> Caused by: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:261)
> at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
> at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
> at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
> at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at client.ProducerJms11.sendMessages(ProducerJms11.java:43)
> ... 3 more
> Caused by: java.io.EOFException: Read past end of file
> at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUnsignedByte(BlockUnmarshaller.java:258)
> at org.jboss.marshalling.river.BlockUnmarshaller.readInt(BlockUnmarshaller.java:296)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUTF(BlockUnmarshaller.java:326)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.readExternal(ActiveMQConnectionFactory.java:186)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1414)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
> ... 15 more
> Caused by: an exception which occurred:
> in object of type org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
> {noformat}
> It fails on attempt to look up RemoteCF
> {noformat}
> ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(ClientDefaults.CONNECTION_FACTORY);
> {noformat}
> Same scenario with connector works well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10812) Some security tests fail on closed channel exception
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10812?page=com.atlassian.jira.plugin... ]
Jan Kalina edited comment on WFLY-10812 at 8/14/18 4:29 AM:
------------------------------------------------------------
WSTrustTestCase:
* in GenerateWSKeyStores need to use CN=localhost and add alternative name 127.0.0.1
* still investigating "SSLHandshakeException: Invalid ECDH ServerKeyExchange signature": it looks {{testPicketLink}} breaks {{testHolderOfKey}} - probably incorrect clean up
{code}
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin/:$PATH mvn test -Dsurefire.runOrder=alphabetical -Dtest=WSTrustTestCase#testPicketLink+testHolderOfKey
{code}
was (Author: honza889):
WSTrustTestCase:
* in GenerateWSKeyStores need to use CN=localhost and add alternative name 127.0.0.1
* still investigating "SSLHandshakeException: Invalid ECDH ServerKeyExchange signature"
> Some security tests fail on closed channel exception
> ----------------------------------------------------
>
> Key: WFLY-10812
> URL: https://issues.jboss.org/browse/WFLY-10812
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Richard Opalka
> Assignee: Jan Kalina
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> With latest JDK11 (build 11-ea+25) the following tests fail due to closed channel exception: modified:
> * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/loginmodules/LdapExtLikeAdvancedLdapLMTestCase.java
> * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/loginmodules/LdapExtLoginModuleTestCase.java
> * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/loginmodules/LdapLoginModuleTestCase.java
> * testsuite/integration/elytron/src/test/java/org/wildfly/test/integration/elytron/ssl/UndertowTwoWaySslNeedClientAuthTestCase.java
> * testsuite/integration/iiop/src/test/java/org/jboss/as/test/iiopssl/basic/IIOPSslInvocationTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/security/OutboundLdapConnectionClientCertTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/security/OutboundLdapConnectionTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/CertificateRolesLoginModuleTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/DatabaseCertLoginModuleTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/HTTPSWebConnectorTestCase.java
> * testsuite/integration/ws/src/test/java/org/jboss/as/test/integration/ws/wsse/trust/WSTrustTestCase.java
> Is there a known SSL issue in JDK11? Could somebody from our security team investigate this issue?
> When these tests will start passing WF test suite will be passing 100% of tests on JDK11.
> Potential investigator from our security team may want to include this PR:
> https://github.com/wildfly/wildfly/pull/11499
> to fix known JDK11 issues.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10835) Connection factory with discovery-group doesn't work
by Martin Styk (JIRA)
Martin Styk created WFLY-10835:
----------------------------------
Summary: Connection factory with discovery-group doesn't work
Key: WFLY-10835
URL: https://issues.jboss.org/browse/WFLY-10835
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 13.0.0.Final
Reporter: Martin Styk
Assignee: Jeff Mesnil
Priority: Critical
Jms client can not use remote connection factory defined as follows
{noformat}
<discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" discovery-group="dg-group1" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
{noformat}
Following exception is thrown on client
{noformat}
Exception in thread "main" java.lang.RuntimeException: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
at client.ProducerJms11.sendMessages(ProducerJms11.java:67)
at client.Producer.run(Producer.java:34)
at client.Producer.sendAllSync(Producer.java:25)
at client.ProducerJms11.main(ProducerJms11.java:14)
Caused by: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:261)
at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at client.ProducerJms11.sendMessages(ProducerJms11.java:43)
... 3 more
Caused by: java.io.EOFException: Read past end of file
at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
at org.jboss.marshalling.river.BlockUnmarshaller.readUnsignedByte(BlockUnmarshaller.java:258)
at org.jboss.marshalling.river.BlockUnmarshaller.readInt(BlockUnmarshaller.java:296)
at org.jboss.marshalling.river.BlockUnmarshaller.readUTF(BlockUnmarshaller.java:326)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.readExternal(ActiveMQConnectionFactory.java:186)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1414)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
... 15 more
Caused by: an exception which occurred:
in object of type org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
{noformat}
It fails on attempt to look up RemoteCF
{noformat}
ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(ClientDefaults.CONNECTION_FACTORY);
{noformat}
Same scenario with connector works well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months