[JBoss JIRA] (WFLY-9098) Infinispan & Wildfly
by Majid Mostafavi (JIRA)
Majid Mostafavi created WFLY-9098:
-------------------------------------
Summary: Infinispan & Wildfly
Key: WFLY-9098
URL: https://issues.jboss.org/browse/WFLY-9098
Project: WildFly
Issue Type: Bug
Reporter: Majid Mostafavi
Assignee: Jason Greene
22:03:39,026 INFO [io.undertow.servlet] (ServerService Thread Pool -- 73) Initializing Shiro environment 22:03:39,027 INFO [org.apache.shiro.web.env.EnvironmentLoader] (ServerService Thread Pool -- 73) Starting Shiro environment initialization. 22:03:39,947 INFO [org.apache.shiro.config.IniSecurityManagerFactory] (ServerService Thread Pool -- 73) Realms have been explicitly set on the SecurityManager instance - auto-setting of realms will not occur. 22:03:40,010 INFO [org.apache.shiro.web.env.EnvironmentLoader] (ServerService Thread Pool -- 73) Shiro environment initialized in 977 ms. 22:03:40,162 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 73) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/nejat' 22:03:43,737 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'deploy' at address '[("deployment" => "nejat")]' 22:03:43,746 ERROR [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0021: Deploy of deployment "nejat.war" was rolled back with the following failure message: "WFLYCTL0344: Operation timed out awaiting service container stability" 22:03:44,227 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = nejat.war_oracle.jdbc.OracleDriver_11_2 22:03:44,327 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = nejat.war_org.postgresql.Driver_9_4 22:03:48,755 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0190: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$1@5454e920 for operation {"operation" => "deploy","address" => [("deployment" => "nejat")],"operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"}} at address [("deployment" => "nejat")] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:498) at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1369) at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328) at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1301) at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185) at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) 22:03:53,761 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0349: Timeout after [5] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'deploy' at address '[("deployment" => "nejat")]' [2017-07-18 10:03:54,181] Artifact nejat:war exploded: Error during artifact deployment. See server log for details. [2017-07-18 10:03:54,181] Artifact nejat:war exploded: java.lang.Exception: WFLYCTL0344: Operation timed out awaiting service container stability
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9097) Remove unused cache configurations from default config files
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9097?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-12195 to WFLY-9097:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9097 (was: JBEAP-12195)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.ER2)
> Remove unused cache configurations from default config files
> ------------------------------------------------------------
>
> Key: WFLY-9097
> URL: https://issues.jboss.org/browse/WFLY-9097
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 11.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> Based on discussion in JBEAP-12141 - some Infinispan cache configurations are not used by default.
> bq. These were added to serve as configuration examples in response to the number of users requesting the same types of configuration.
> This jira's purpose is to reach a decision whether we will remove them or not, simplyfing the configuration and possibly saving some memory at runtime.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ]
Jan Kalina moved JBEAP-12194 to WFLY-9096:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9096 (was: JBEAP-12194)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
Security
(was: JMS)
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.ER1)
> JMS client fails to connect with SSL on IBM JDK 8
> -------------------------------------------------
>
> Key: WFLY-9096
> URL: https://issues.jboss.org/browse/WFLY-9096
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 11.0.0.Alpha1
> Environment: IBM JDK 8:
> {code}
> $ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled)
> J9VM - R28_20170314_2309_B340265
> JIT - tr.r14.java.green_20170314_134138
> GC - R28_20170314_2309_B340265
> J9CL - 20170314_340265)
> JCL - 20170318_01 based on Oracle jdk8u121-b13
> {code}
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Labels: eap7.1-risks-mitigation
>
> If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with:
> {code}
> ERROR: AMQ214016: Failed to create netty connection
> java.nio.channels.ClosedChannelException
> at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source)
> Producer got exception and ended:javax.jms.JMSException: Failed to create session factory
> javax.jms.JMSException: Failed to create session factory
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260)
> at ProducerTransSession.run(ProducerTransSession.java:75)
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755)
> ... 3 more
> {code}
> If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully.
> Issue is under investigation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9095) AS TS module manualmode has a wrong configuration of surefire plugin in pom.xml
by Josef Cacek (JIRA)
Josef Cacek created WFLY-9095:
---------------------------------
Summary: AS TS module manualmode has a wrong configuration of surefire plugin in pom.xml
Key: WFLY-9095
URL: https://issues.jboss.org/browse/WFLY-9095
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Josef Cacek
The {{pom.xml}} in manualmode module contains in its surefire plugin configuration part:
{code:xml}
<includes>
<include>org/jboss/as/test/manualmode/**/*TestCase.java</include>
</includes>
<runOrder>alphabetical</runOrder>
{code}
These config items should be removed
* the includes set defined here isn't complete
* test run order should not be predefined..
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3072) CapabilityRegistry.suggest-capabilities issue on Windows
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3072?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3072:
----------------------------------------------
[~brian.stansberry], I just linked the PR: https://github.com/wildfly/wildfly-core/pull/2620
> CapabilityRegistry.suggest-capabilities issue on Windows
> --------------------------------------------------------
>
> Key: WFCORE-3072
> URL: https://issues.jboss.org/browse/WFCORE-3072
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
>
> The test added by WFLY-8990 highlight a problem on windows.
> A path containing a ':' makes Paths.get to fail. (Eg: profile/clone-profile-test-case-default/subsystem/mail/mail-session/java:jboss/mail/Default)
> [Host Controller] 12:00:52,091 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("suggest-capabilities") failed - address: ([
> [Host Controller] ("host" => "master"),
> [Host Controller] ("core-service" => "capability-registry")
> [Host Controller] ]): java.nio.file.InvalidPathException: Illegal char <:> at index 73: /profile/clone-profile-test-case-default/subsystem/mail/mail-session/java:jboss/mail/Default
> [Host Controller] at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> [Host Controller] at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> [Host Controller] at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> [Host Controller] at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
> [Host Controller] at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
> [Host Controller] at java.nio.file.Paths.get(Paths.java:84)
> [Host Controller] at org.jboss.as.controller.CapabilityRegistry.lambda$null$4(CapabilityRegistry.java:952)
> [Host Controller] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> [Host Controller] at java.util.Iterator.forEachRemaining(Iterator.java:116)
> [Host Controller] at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3072) CapabilityRegistry.suggest-capabilities issue on Windows
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3072?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-3072:
--------------------------------------------
Assignee: Jean-Francois Denise (was: Brian Stansberry)
> CapabilityRegistry.suggest-capabilities issue on Windows
> --------------------------------------------------------
>
> Key: WFCORE-3072
> URL: https://issues.jboss.org/browse/WFCORE-3072
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
>
> The test added by WFLY-8990 highlight a problem on windows.
> A path containing a ':' makes Paths.get to fail. (Eg: profile/clone-profile-test-case-default/subsystem/mail/mail-session/java:jboss/mail/Default)
> [Host Controller] 12:00:52,091 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("suggest-capabilities") failed - address: ([
> [Host Controller] ("host" => "master"),
> [Host Controller] ("core-service" => "capability-registry")
> [Host Controller] ]): java.nio.file.InvalidPathException: Illegal char <:> at index 73: /profile/clone-profile-test-case-default/subsystem/mail/mail-session/java:jboss/mail/Default
> [Host Controller] at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> [Host Controller] at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> [Host Controller] at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> [Host Controller] at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
> [Host Controller] at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
> [Host Controller] at java.nio.file.Paths.get(Paths.java:84)
> [Host Controller] at org.jboss.as.controller.CapabilityRegistry.lambda$null$4(CapabilityRegistry.java:952)
> [Host Controller] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> [Host Controller] at java.util.Iterator.forEachRemaining(Iterator.java:116)
> [Host Controller] at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9069) EJBClientContext could not initialize class org.jboss.ejb.client.DeploymentNodeSelector when building with JDK-9
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9069?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-9069.
-------------------------------
Fix Version/s: 11.0.0.Beta1
Resolution: Done
This was fixed in ejb-client, https://github.com/wildfly/jboss-ejb-client/pull/287
and will be part of CR6 release.
> EJBClientContext could not initialize class org.jboss.ejb.client.DeploymentNodeSelector when building with JDK-9
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9069
> URL: https://issues.jboss.org/browse/WFLY-9069
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Amos Feng
> Assignee: Tomaz Cerar
> Fix For: 11.0.0.Beta1
>
>
> {noformat}
> testRejectionsEAP620(org.jboss.as.ejb3.subsystem.Ejb3TransformersTestCase) Time elapsed: 2.786 sec <<< ERROR!
> java.lang.IncompatibleClassChangeError: Inconsistent constant pool data in classfile for class org/jboss/ejb/client/DeploymentNodeSelector. Method lambda$static$1([Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String; at index 109 is CONSTANT_MethodRef and should be CONSTANT_InterfaceMethodRef
> at org.jboss.ejb.client.DeploymentNodeSelector.<clinit>(DeploymentNodeSelector.java:83)
> at org.jboss.ejb.client.EJBClientContext$Builder.<init>(EJBClientContext.java:538)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem50Parser.parseProfile(EJB3Subsystem50Parser.java:218)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem30Parser.parseProfiles(EJB3Subsystem30Parser.java:215)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem40Parser.parseRemote(EJB3Subsystem40Parser.java:116)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:135)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem13Parser.readElement(EJB3Subsystem13Parser.java:66)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem14Parser.readElement(EJB3Subsystem14Parser.java:58)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem20Parser.readElement(EJB3Subsystem20Parser.java:69)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem30Parser.readElement(EJB3Subsystem30Parser.java:77)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem50Parser.readElement(EJB3Subsystem50Parser.java:88)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:104)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:71)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> at org.jboss.as.subsystem.test.TestParser.readElement(TestParser.java:103)
> at org.jboss.as.subsystem.test.TestParser.readElement(TestParser.java:51)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.subsystem.test.SubsystemTestDelegate.parse(SubsystemTestDelegate.java:223)
> at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.parse(SubsystemTestDelegate.java:611)
> at org.jboss.as.model.test.ModelTestBootOperationsBuilder.internalSetSubsystemXml(ModelTestBootOperationsBuilder.java:76)
> at org.jboss.as.model.test.ModelTestBootOperationsBuilder.setXmlResource(ModelTestBootOperationsBuilder.java:55)
> at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.parseXmlResource(SubsystemTestDelegate.java:624)
> at org.jboss.as.ejb3.subsystem.Ejb3TransformersTestCase.testRejections(Ejb3TransformersTestCase.java:174)
> at org.jboss.as.ejb3.subsystem.Ejb3TransformersTestCase.testRejectionsEAP620(Ejb3TransformersTestCase.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9094) Trivial fixes in appclient.sh and jdr.sh
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9094?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-9094:
---------------------------------
Assignee: Jan Stourac (was: Tomaz Cerar)
> Trivial fixes in appclient.sh and jdr.sh
> ----------------------------------------
>
> Key: WFLY-9094
> URL: https://issues.jboss.org/browse/WFLY-9094
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Stourac
> Assignee: Jan Stourac
> Priority: Trivial
>
> Minor changes in bin/appclient.sh and bin/jdr.sh:
> * appclient:
> ** fix of HAS_OPENJDK variable name
> ** use || instead of -o as it is better defined
> * jdr:
> ** used simplier syntax for if statement condition
> ** fix of assignment statement "cygwin = true" -> "cygwin=true"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months