June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1577) After a full-replace-deployment operation a server on a hosts subsystem model is empty

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1577?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1577: ------------------------------------- Priority: Blocker (was: Major) > After a full-replace-deployment operation a server on a hosts subsystem model is empty > -------------------------------------------------------------------------------------- > > Key: WFCORE-1577 > URL: https://issues.jboss.org/browse/WFCORE-1577 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Priority: Blocker > Attachments: WFCORE-1577-test-case.patch > > > Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1577) After a full-replace-deployment operation a server on a hosts subsystem model is empty

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1577?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1577: ------------------------------------------ The param to the server-group/deployment add op and the full-replace-deployment op is "enabled" not "enable". Fix that in your test and it passes. That doesn't mean there isn't a bug here, but it may fix your plugin if that's where you are hitting this. > After a full-replace-deployment operation a server on a hosts subsystem model is empty > -------------------------------------------------------------------------------------- > > Key: WFCORE-1577 > URL: https://issues.jboss.org/browse/WFCORE-1577 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Attachments: WFCORE-1577-test-case.patch > > > Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1577) After a full-replace-deployment operation a server on a hosts subsystem model is empty

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1577?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1577: ---------------------------------- Steps to Reproduce: Use the test from https://github.com/jamezp/wildfly-core/tree/WFCORE-1577 or the attached patch and execute with: {code} cd testsuite/domain mvn clean test -Dtest=DeploymentTestCase {code} was: Use the test from https://github.com/jamezp/wildfly-core/tree/WFCORE-1577 or the attached patch and execute with: {code} mvn clean test -Dtest=DeploymentTestCase {code} > After a full-replace-deployment operation a server on a hosts subsystem model is empty > -------------------------------------------------------------------------------------- > > Key: WFCORE-1577 > URL: https://issues.jboss.org/browse/WFCORE-1577 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Attachments: WFCORE-1577-test-case.patch > > > Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1577) After a full-replace-deployment operation a server on a hosts subsystem model is empty

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1577?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1577: ---------------------------------- Steps to Reproduce: Use the test from https://github.com/jamezp/wildfly-core/tree/WFCORE-1577 or the attached patch and execute with: {code} mvn clean test -Dtest=DeploymentTestCase {code} was: Use the test from https://issues.jboss.org/browse/WFCORE-1577 or the attached patch and execute with: {code} mvn clean test -Dtest=DeploymentTestCase {code} > After a full-replace-deployment operation a server on a hosts subsystem model is empty > -------------------------------------------------------------------------------------- > > Key: WFCORE-1577 > URL: https://issues.jboss.org/browse/WFCORE-1577 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Attachments: WFCORE-1577-test-case.patch > > > Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1577) After a full-replace-deployment operation a server on a hosts subsystem model is empty

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1577?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1577: ---------------------------------- Steps to Reproduce: Use the test from https://issues.jboss.org/browse/WFCORE-1577 or the attached patch and execute with: {code} mvn clean test -Dtest=DeploymentTestCase {code} Attachment: WFCORE-1577-test-case.patch > After a full-replace-deployment operation a server on a hosts subsystem model is empty > -------------------------------------------------------------------------------------- > > Key: WFCORE-1577 > URL: https://issues.jboss.org/browse/WFCORE-1577 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Attachments: WFCORE-1577-test-case.patch > > > Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1577) After a full-replace-deployment operation a server on a hosts subsystem model is empty

by James Perkins (JIRA)

James Perkins created WFCORE-1577: ------------------------------------- Summary: After a full-replace-deployment operation a server on a hosts subsystem model is empty Key: WFCORE-1577 URL: https://issues.jboss.org/browse/WFCORE-1577 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: Brian Stansberry Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1532) Upgrade VFS to 3.2.12.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1532?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1532: ------------------------------------------ Can you release Version 3.2.11 and 3.2.12 in JIRA? > Upgrade VFS to 3.2.12.Final > --------------------------- > > Key: WFCORE-1532 > URL: https://issues.jboss.org/browse/WFCORE-1532 > Project: WildFly Core > Issue Type: Component Upgrade > Components: VFS > Affects Versions: 2.1.0.Final > Reporter: Ivo Studensky > Assignee: Tomaz Cerar > > Upgrade VFS to address JBVFS-204. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6554) Cache configuration are not eagerly defined in Cache Container

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/WFLY-6554?page=com.atlassian.jira.plugin.... ] Mathieu Lachance commented on WFLY-6554: ---------------------------------------- Good to know, I'll pull out the latest ci build and test this tomorrow. I'll open a new issue, if necessary. Thanks again ! > Cache configuration are not eagerly defined in Cache Container > -------------------------------------------------------------- > > Key: WFLY-6554 > URL: https://issues.jboss.org/browse/WFLY-6554 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Mathieu Lachance > Assignee: Paul Ferraro > > In WF8 we used the cache configuration start="EAGER" to force the initialization of the cache configuration. > In my scenario, we especially used that trick to define all cache configuration (i.e. entity / timestamps / local-query) in the hibernate cache container before any of our war was deployed. Doing so, when wiring the EntityManager programatically (in our application), we were able to depend on the JNDIRegionFactory without getting any NullPointerException/etc. > This trick has only one bad side effect, which was the creation of unecessary caches. > Now in WF10, the eager feature is gone and it seems that even if the cache container is available at startup (as discussed in: https://developer.jboss.org/thread/259151) the defined caches are not. > I do not know if this is a bug or this is by design but this seems wrong to me. > If we define caches within standalone.xml, I would definitly like to have them defined at the container level. I think it's fair to assume that when pulling the CacheManager all defined caches should have been there. > I would suggest that when reading all the infinispan subsystem, each cache contained in each cache container be eagerly defined to avoid any issue (and I really meant "defined" and not "started"). > Doing so this would resolve our EntityManager second level cache bootstraping without relying on our application to define the missing cache configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6554) Cache configuration are not eagerly defined in Cache Container

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6554?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6554: ------------------------------------ I believe you are running into WFLY-6674 - a fix for which was just merged into master. The description of WFLY-6674 is a bit deceiving - essentially, cache configurations specified in the Infinispan subsystem were not being defined eagerly, but lazily when the appropriate dependencies are established. > Cache configuration are not eagerly defined in Cache Container > -------------------------------------------------------------- > > Key: WFLY-6554 > URL: https://issues.jboss.org/browse/WFLY-6554 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Mathieu Lachance > Assignee: Paul Ferraro > > In WF8 we used the cache configuration start="EAGER" to force the initialization of the cache configuration. > In my scenario, we especially used that trick to define all cache configuration (i.e. entity / timestamps / local-query) in the hibernate cache container before any of our war was deployed. Doing so, when wiring the EntityManager programatically (in our application), we were able to depend on the JNDIRegionFactory without getting any NullPointerException/etc. > This trick has only one bad side effect, which was the creation of unecessary caches. > Now in WF10, the eager feature is gone and it seems that even if the cache container is available at startup (as discussed in: https://developer.jboss.org/thread/259151) the defined caches are not. > I do not know if this is a bug or this is by design but this seems wrong to me. > If we define caches within standalone.xml, I would definitly like to have them defined at the container level. I think it's fair to assume that when pulling the CacheManager all defined caches should have been there. > I would suggest that when reading all the infinispan subsystem, each cache contained in each cache container be eagerly defined to avoid any issue (and I really meant "defined" and not "started"). > Doing so this would resolve our EntityManager second level cache bootstraping without relying on our application to define the missing cache configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9579) ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to localhost/127.0.0.1:80, configuration will be reset: null

by Sivahari Upputholla (JIRA)

Sivahari Upputholla created JBAS-9579: ----------------------------------------- Summary: ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to localhost/127.0.0.1:80, configuration will be reset: null Key: JBAS-9579 URL: https://issues.jboss.org/browse/JBAS-9579 Project: Application Server 3 4 5 and 6 Issue Type: Task Components: Clustering Affects Versions: 6.1.0 Reporter: Sivahari Upputholla Assignee: Paul Ferraro Priority: Minor Fix For: Open To Community Hi Friends, An error occured while i'm integrating Jboss AppServer (domain mode)with Apache. Can anyone suggest me the fix for it..... ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to localhost/127.0.0.1:80, configuration will be reset: null Thanks...! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2016