January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5923) Add HA immutable-entity cache container entry for the Hibernate second level cache

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5923?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-5923. ------------------------------ > Add HA immutable-entity cache container entry for the Hibernate second level cache > ---------------------------------------------------------------------------------- > > Key: WFLY-5923 > URL: https://issues.jboss.org/browse/WFLY-5923 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5928) Intermittent NPE registering a slave HC in mixed-domain test suite

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5928?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5928: ---------------------------------------- Here's another one: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=83272&buildTyp... > Intermittent NPE registering a slave HC in mixed-domain test suite > ------------------------------------------------------------------ > > Key: WFLY-5928 > URL: https://issues.jboss.org/browse/WFLY-5928 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 10.0.0.CR4 > Reporter: Brian Stansberry > Assignee: Kabir Khan > > I've occasionally seen test failures in the mixed domain tests when a testsuite cannot start because the slave HC can't register due to an NPE on the master: > For example: > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=82653&tab=buil... > Critical log details: > {code}&amp#27;[0m16:16:15,252 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1 > &amp#27;[0m&amp#27;[0m16:16:15,363 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' > &amp#27;[0m[Host Controller] &amp#27;[0m16:16:15,871 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[0m16:16:16,015 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[0m16:16:16,068 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[0m16:16:16,625 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.10.GA-redhat-1&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[0m16:16:16,629 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.10.GA-redhat-1&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[0m16:16:16,657 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version (unknown)&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[0m16:16:16,705 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on [::1]:19999&amp#27;[0m > INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=server-one, host=slave, server-group=other-server-group} status is starting > [Host Controller] &amp#27;[0m&amp#27;[31m16:16:17,913 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 50) WFLYCTL0013: Operation ("read-master-domain-model") failed - address: ([]): java.lang.NullPointerException&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.registry.OperationTransformerRegistry$1.getResourceTransformer(OperationTransformerRegistry.java:83)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.resolveTransformer(ResourceTransformationContextImpl.java:235)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:285)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.description.TransformingDescription$3.invokeNext(TransformingDescription.java:161)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.description.AttributeTransformationRule.transformResource(AttributeTransformationRule.java:103)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.description.TransformingDescription.transformResource(TransformingDescription.java:167)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:289)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.transform.TransformersImpl.transformRootResource(TransformersImpl.java:115)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.domain.controller.operations.ReadMasterDomainModelUtil.readMasterDomainResourcesForInitialConnect(ReadMasterDomainModelUtil.java:88)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.domain.controller.operations.ReadDomainModelHandler.execute(ReadDomainModelHandler.java:51)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1343)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:408)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.host.controller.DomainModelControllerService.access$900(DomainModelControllerService.java:175)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:1229)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.processRegistration(HostControllerRegistrationHandler.java:424)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.access$400(HostControllerRegistrationHandler.java:334)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$InitiateRegistrationHandler$1.execute(HostControllerRegistrationHandler.java:230)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:465)&amp#27;[0m > [Host Controller] &amp#27;[31m at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)&amp#27;[0m > [Host Controller] &amp#27;[31m at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)&amp#27;[0m > [Host Controller] &amp#27;[31m at java.lang.Thread.run(Thread.java:745)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.threads.JBossThread.run(JBossThread.java:320)&amp#27;[0m > [Host Controller] &amp#27;[31m&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[33m16:16:17,935 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010900: Could not connect to remote domain controller at remote://[::1]:9999 -- 1-$-WFLYCTL0158: Operation handler failed: java.lang.NullPointerException&amp#27;[0m > [Host Controller] &amp#27;[33m&amp#27;[0m&amp#27;[33m16:16:17,936 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS016581: No domain controller discovery options remain.&amp#27;[0m > [Host Controller] &amp#27;[33m&amp#27;[0m&amp#27;[31m16:16:17,939 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS016519: Tried all domain controller discovery option(s) but unable to connect&amp#27;[0m > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5938) Upgrade Narayana to 5.2.12.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5938?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5938: -------------------------------- Description: Release notes: https://issues.jboss.org/browse/JBTM/fixforversion/12329351/?selectedTab=... > Upgrade Narayana to 5.2.12.Final > -------------------------------- > > Key: WFLY-5938 > URL: https://issues.jboss.org/browse/WFLY-5938 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.0.0.Final > > > Release notes: https://issues.jboss.org/browse/JBTM/fixforversion/12329351/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5938) Upgrade Narayana to 5.2.12.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5938?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-5938: ------------------------------------- Blocker issue linked in. > Upgrade Narayana to 5.2.12.Final > -------------------------------- > > Key: WFLY-5938 > URL: https://issues.jboss.org/browse/WFLY-5938 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.0.0.Final > > > Release notes: https://issues.jboss.org/browse/JBTM/fixforversion/12329351/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5938) Upgrade Narayana to 5.2.12.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5938?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5938: -------------------------------- Priority: Blocker (was: Major) > Upgrade Narayana to 5.2.12.Final > -------------------------------- > > Key: WFLY-5938 > URL: https://issues.jboss.org/browse/WFLY-5938 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 10.0.0.Final > > > Release notes: https://issues.jboss.org/browse/JBTM/fixforversion/12329351/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5938) Upgrade Narayana to 5.2.12.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5938?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5938: -------------------------------- Fix Version/s: 10.0.0.Final > Upgrade Narayana to 5.2.12.Final > -------------------------------- > > Key: WFLY-5938 > URL: https://issues.jboss.org/browse/WFLY-5938 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3573: --------------------------------- Fix Version/s: (was: 10.0.0.Final) > Adding incorrect JGroups protocol should provide better error description than CNFE > ----------------------------------------------------------------------------------- > > Key: WFLY-3573 > URL: https://issues.jboss.org/browse/WFLY-3573 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: ux > > As reported by the community user: > {noformat} > [standalone@localhost:9990 / #] list-batch > #1 /subsystem=jgroups/stack=test:add() > #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp) > #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd) > [standalone@localhost:9990 / #] run-batch > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}} > [standalone@localhost:9990 / #] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3573: --------------------------------- Issue Type: Enhancement (was: Feature Request) > Adding incorrect JGroups protocol should provide better error description than CNFE > ----------------------------------------------------------------------------------- > > Key: WFLY-3573 > URL: https://issues.jboss.org/browse/WFLY-3573 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: ux > > As reported by the community user: > {noformat} > [standalone@localhost:9990 / #] list-batch > #1 /subsystem=jgroups/stack=test:add() > #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp) > #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd) > [standalone@localhost:9990 / #] run-batch > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}} > [standalone@localhost:9990 / #] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1226: ------------------------------------- you marked that this is issue in WFCORE 2.0.4, aka currently latest, but description about reproducing is on EAP 6.4.4 which is much older code. Can you confirm that problem exists in both versions? > undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-1226 > URL: https://issues.jboss.org/browse/WFCORE-1226 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.4.Final > Reporter: Chao Wang > Assignee: Chao Wang > Attachments: WFCORE-1226-wildflytest.patch, WFCORE-1226.patch > > > {noformat} > 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command: > ~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war > ~~~ > 2. Deploy next version of application in "disabled" state with same "runtime-name" > ~~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war > ~~~ > 3. Now use replace-deployment command to access latest version of application: > ~~~ > [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war) > ~~~ > its working fine,laest version of application is accessable. > 4. Now try to undeploy old version of application > ~~~ > /server-group=main-server-group/deployment=WebApp-1.war:undeploy() > ~~~ > After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it. > Same steps are working fine in Standalone mode. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1268) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1268: ---------------------------------------- Summary: undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler Key: WFCORE-1268 URL: https://issues.jboss.org/browse/WFCORE-1268 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.0.4.Final Reporter: Chao Wang Assignee: Chao Wang {noformat} 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command: ~~ [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war ~~~ 2. Deploy next version of application in "disabled" state with same "runtime-name" ~~~ [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war ~~~ 3. Now use replace-deployment command to access latest version of application: ~~~ [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war) ~~~ its working fine,laest version of application is accessable. 4. Now try to undeploy old version of application ~~~ /server-group=main-server-group/deployment=WebApp-1.war:undeploy() ~~~ After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it. Same steps are working fine in Standalone mode. {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016