February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1062) Deployments from the domain/data/content folder goes missing after few minutes if the Host controller is started with --backup option.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1062?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1062: ------------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1265170|https://bugzilla.redhat.com/show_bug.cgi?id=1265170] from POST to MODIFIED > Deployments from the domain/data/content folder goes missing after few minutes if the Host controller is started with --backup option. > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1062 > URL: https://issues.jboss.org/browse/WFCORE-1062 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR7 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 2.0.0.CR8 > > > Host controller started with --backup option deletes the deployments from the domain/data/content folder after approximately 10 mins. > The deployment is restored or recreated if the HostController is started. > Version-Release number of selected component (if applicable): 6.4.x > How reproducible: > Steps to Reproduce: > > 1. Setup domaincontroller > 2. Setup hostcontroller > 3. Start domaincontroller > 4. Start hostcontroller with --backup option. > 5. deploy an application using cli or admin console > ./jboss-cli.sh --connect --controller=x.x.x.x:9999 --command='deploy /PathToApp/App.war --server-groups=main-server-group' > 6. deployments are available under $JBOSS_HOME/domain/data/content > 7. Wait for approximately 10 minutes > 8. Cached deployments are deleted on hostcontroller (domain/data/content is empty). Following is the logging seen on the console : > ++++++++++++++ > [Host Controller] 14:20:40,439 INFO [org.jboss.as.repository] (Host Controller Service Threads - 4) JBAS014903: Content /NotBackedUp/JAR-Folder/EAPs/EAP6/jboss-eap-6.4.3-Patched/domain/data/content/47/1108a27fa1b82e6a92fb56ee25bc76f2625249 is obsolete and will be removed > [Host Controller] 14:20:40,440 INFO [org.jboss.as.repository] (Host Controller Service Threads - 4) JBAS014901: Content removed from location /NotBackedUp/JAR-Folder/EAPs/EAP6/jboss-eap-6.4.3-Patched/domain/data/content/47/1108a27fa1b82e6a92fb56ee25bc76f2625249/content > ++++++++++++++ > 9. After restarting the Host Controller, the deployment is restored and the cached deployment can now be seen under the Host Controller's domain/data/content folder. > Actual results: Deployment folder form domain/data/content folder gets deleted after approx 10 mins and are restored if the Host Controller is restarted > Expected results: The cached deplpyments folder should never be removed from the HostController's domain/data/content folder. > Additional info: This does not affect the availability of the application since the applications are also availbale with the assigned server's under their data/content folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6264) ClassNotFoundException: org.wildfly.clustering.service.Builder when creating singleton service via SingletonPolicy

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6264?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6264: ------------------------------- Description: This is because the org.wildfly.clustering.singleton.SingletonPolicy interface references org.wildfly.clustering.service.Builder from the org.wildfly.clustering.service module, but this module is not exported to deployments. {noformat} &amp#27;[0m&amp#27;[31m13:22:08,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."singleton.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."singleton.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "singleton.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) 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) Caused by: java.lang.NoClassDefFoundError: org/wildfly/clustering/service/Builder at org.jboss.as.test.clustering.cluster.singleton.service.AbstractServiceActivator.install(AbstractServiceActivator.java:59) at org.jboss.as.test.clustering.cluster.singleton.service.MyServiceActivator.activate(MyServiceActivator.java:38) at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:74) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more Caused by: java.lang.ClassNotFoundException: org.wildfly.clustering.service.Builder from [Module "deployment.singleton.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) ... 9 more {noformat} was:This is because the org.wildfly.clustering.singleton.SingletonPolicy interface references org.wildfly.clustering.service.Builder from the org.wildfly.clustering.service module, but this module is not exported to deployments. > ClassNotFoundException: org.wildfly.clustering.service.Builder when creating singleton service via SingletonPolicy > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6264 > URL: https://issues.jboss.org/browse/WFLY-6264 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.1.0.Final > > > This is because the org.wildfly.clustering.singleton.SingletonPolicy interface references org.wildfly.clustering.service.Builder from the org.wildfly.clustering.service module, but this module is not exported to deployments. > {noformat} > &amp#27;[0m&amp#27;[31m13:22:08,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."singleton.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."singleton.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "singleton.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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) > Caused by: java.lang.NoClassDefFoundError: org/wildfly/clustering/service/Builder > at org.jboss.as.test.clustering.cluster.singleton.service.AbstractServiceActivator.install(AbstractServiceActivator.java:59) > at org.jboss.as.test.clustering.cluster.singleton.service.MyServiceActivator.activate(MyServiceActivator.java:38) > at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:74) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > Caused by: java.lang.ClassNotFoundException: org.wildfly.clustering.service.Builder from [Module "deployment.singleton.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) > ... 9 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6264) ClassNotFoundException: org.wildfly.clustering.service.Builder when creating singleton service via SingletonPolicy

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-6264: ---------------------------------- Summary: ClassNotFoundException: org.wildfly.clustering.service.Builder when creating singleton service via SingletonPolicy Key: WFLY-6264 URL: https://issues.jboss.org/browse/WFLY-6264 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 10.1.0.Final This is because the org.wildfly.clustering.singleton.SingletonPolicy interface references org.wildfly.clustering.service.Builder from the org.wildfly.clustering.service module, but this module is not exported to deployments. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Display MetaspaceSize & MaxMetaspaceSize as jvm attributes

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills closed WFCORE-1402. ----------------------------- Fix Version/s: (was: 3.0.0.Alpha1) Resolution: Rejected Closing, as not needed. > Display MetaspaceSize & MaxMetaspaceSize as jvm attributes > ---------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > > This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Display MetaspaceSize & MaxMetaspaceSize as jvm attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1402: ------------------------------------------ I'm fine with closing it. :) > Display MetaspaceSize & MaxMetaspaceSize as jvm attributes > ---------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-421) IBM JDK uses a slightly different stack for property permission checking

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-421?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-421: --------------------------------- Fix Version/s: 1.0.3.CR1 1.1.0.Beta4 (was: 1.1.0.Beta5) > IBM JDK uses a slightly different stack for property permission checking > ------------------------------------------------------------------------ > > Key: ELY-421 > URL: https://issues.jboss.org/browse/ELY-421 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta4, 1.0.3.CR1 > > > On some IBM JDKs, System.getProperty delegates to other System methods. The security manager does not account for that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-421) IBM JDK uses a slightly different stack for property permission checking

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-421?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-421. ---------------------------------- Resolution: Done > IBM JDK uses a slightly different stack for property permission checking > ------------------------------------------------------------------------ > > Key: ELY-421 > URL: https://issues.jboss.org/browse/ELY-421 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.3.CR1, 1.1.0.Beta4 > > > On some IBM JDKs, System.getProperty delegates to other System methods. The security manager does not account for that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Display MetaspaceSize & MaxMetaspaceSize as jvm attributes

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills edited comment on WFCORE-1402 at 2/23/16 1:50 PM: ------------------------------------------------------------ Thanks for the clarification, I thought we'd be treating it like permgen going forward. I've edited the title and description to be more accurate. So based on that, we'd either just want to leave it available in its generic form under jvm-options, or we could parse it out for display. Do you think there's any value in that? If not, I'll close this and file under "mistake." :) was (Author: luck3y): Thanks for the clarification, I thought we'd be treating it like permgen going forward. I've edited the title and description to be more accurate. So based on that, we'd either just want to leave it available in its generic form under jvm-options, or we could parse it out for display. Do you think there's any value in that? If not, I'll close this an file under "mistake." :) > Display MetaspaceSize & MaxMetaspaceSize as jvm attributes > ---------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Display MetaspaceSize & MaxMetaspaceSize as jvm attributes

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills edited comment on WFCORE-1402 at 2/23/16 1:49 PM: ------------------------------------------------------------ Thanks for the clarification, I thought we'd be treating it like permgen going forward. I've edited the title and description to be more accurate. So based on that, we'd either just want to leave it available in its generic form under jvm-options, or we could parse it out for display. Do you think there's any value in that? If not, I'll close this an file under "mistake." :) was (Author: luck3y): Thanks for the clarification, I thought we'd be treating it like permgen going forward. So based on that, we'd either just want to leave it available in its generic form under jvm-options, or we could parse it out for display. Do you think there's any value in that? If not, I'll close this an file under "mistake." :) > Display MetaspaceSize & MaxMetaspaceSize as jvm attributes > ---------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Display MetaspaceSize & MaxMetaspaceSize as jvm attributes

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-1402: ------------------------------ Summary: Display MetaspaceSize & MaxMetaspaceSize as jvm attributes (was: Add support for metaspacesize to jvm options and remove permgen) > Display MetaspaceSize & MaxMetaspaceSize as jvm attributes > ---------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016