[JBoss JIRA] (WFLY-11518) war deployment in 10.1.0 Final is failing itself after its successful deployment
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11518?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11518:
-------------------------------
Description:
Setup -- Wildfly Clustered ha with pacemaker
pcs resource enable REST
This will internally call custom bash scripts as below.
APP_NAME = myproject-plf-core-fm-rest-api.war
cd $MYPROJECT_DEPLOYMENT_DIR
$MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
batch
deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
run-batch
exit
war is switching with deploy/undeploy as below without the success deployment. This leading to failure of other jars deployment in the cluster.
2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
name: dacPersistenceUnit
...]
2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
Let me know incase require any more information.
was:
Setup -- Wildfly Clustered ha with pacemaker
pcs resource enable REST
This will internally call custom bash scripts as below.
APP_NAME = myproject-plf-core-fm-rest-api.war
cd $MYPROJECT_DEPLOYMENT_DIR
$MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
batch
deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
run-batch
exit
war is switching with deploy/undeploy as below without the success deployment. This leading to failure of other jars deployment.
2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
name: dacPersistenceUnit
...]
2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
Let me know incase require any more information.
> war deployment in 10.1.0 Final is failing itself after its successful deployment
> --------------------------------------------------------------------------------
>
> Key: WFLY-11518
> URL: https://issues.jboss.org/browse/WFLY-11518
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Major
> Labels: highavailability
>
> Setup -- Wildfly Clustered ha with pacemaker
> pcs resource enable REST
> This will internally call custom bash scripts as below.
> APP_NAME = myproject-plf-core-fm-rest-api.war
> cd $MYPROJECT_DEPLOYMENT_DIR
> $MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
> batch
> deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
> run-batch
> exit
> war is switching with deploy/undeploy as below without the success deployment. This leading to failure of other jars deployment in the cluster.
> 2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
> 2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
> 2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
> name: dacPersistenceUnit
> ...]
> 2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
> 2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
> 2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
> 2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
> 2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
> 2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> Let me know incase require any more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (WFLY-11518) war deployment in 10.1.0 Final is failing itself after its successful deployment
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11518?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11518:
-------------------------------
Labels: highavailability (was: )
> war deployment in 10.1.0 Final is failing itself after its successful deployment
> --------------------------------------------------------------------------------
>
> Key: WFLY-11518
> URL: https://issues.jboss.org/browse/WFLY-11518
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Major
> Labels: highavailability
>
> Setup -- Wildfly Clustered ha with pacemaker
> pcs resource enable REST
> This will internally call custom bash scripts as below.
> APP_NAME = myproject-plf-core-fm-rest-api.war
> cd $MYPROJECT_DEPLOYMENT_DIR
> $MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
> batch
> deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
> run-batch
> exit
> war is switching with deploy/undeploy as below --
> 2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
> 2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
> 2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
> name: dacPersistenceUnit
> ...]
> 2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
> 2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
> 2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
> 2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
> 2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
> 2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> Let me know incase require any more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (WFLY-11518) war deployment in 10.1.0 Final is failing itself after its successful deployment
by Srinivas ev (Jira)
Srinivas ev created WFLY-11518:
----------------------------------
Summary: war deployment in 10.1.0 Final is failing itself after its successful deployment
Key: WFLY-11518
URL: https://issues.jboss.org/browse/WFLY-11518
Project: WildFly
Issue Type: Bug
Reporter: Srinivas ev
Assignee: Jason Greene
Setup -- Wildfly Clustered ha with pacemaker
pcs resource enable REST
This will internally call custom bash scripts as below.
APP_NAME = myproject-plf-core-fm-rest-api.war
cd $MYPROJECT_DEPLOYMENT_DIR
$MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
batch
deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
run-batch
exit
war is switching with deploy/undeploy as below --
2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
name: dacPersistenceUnit
...]
2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
Let me know incase require any more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (WFLY-11518) war deployment in 10.1.0 Final is failing itself after its successful deployment
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11518?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11518:
-------------------------------
Affects Version/s: 10.1.0.Final
> war deployment in 10.1.0 Final is failing itself after its successful deployment
> --------------------------------------------------------------------------------
>
> Key: WFLY-11518
> URL: https://issues.jboss.org/browse/WFLY-11518
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Major
>
> Setup -- Wildfly Clustered ha with pacemaker
> pcs resource enable REST
> This will internally call custom bash scripts as below.
> APP_NAME = myproject-plf-core-fm-rest-api.war
> cd $MYPROJECT_DEPLOYMENT_DIR
> $MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
> batch
> deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
> run-batch
> exit
> war is switching with deploy/undeploy as below --
> 2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
> 2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
> 2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
> name: dacPersistenceUnit
> ...]
> 2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
> 2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
> 2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
> 2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
> 2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
> 2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> Let me know incase require any more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (WFLY-11518) war deployment in 10.1.0 Final is failing itself after its successful deployment
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11518?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11518:
-------------------------------
Component/s: Clustering
> war deployment in 10.1.0 Final is failing itself after its successful deployment
> --------------------------------------------------------------------------------
>
> Key: WFLY-11518
> URL: https://issues.jboss.org/browse/WFLY-11518
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Major
>
> Setup -- Wildfly Clustered ha with pacemaker
> pcs resource enable REST
> This will internally call custom bash scripts as below.
> APP_NAME = myproject-plf-core-fm-rest-api.war
> cd $MYPROJECT_DEPLOYMENT_DIR
> $MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
> batch
> deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
> run-batch
> exit
> war is switching with deploy/undeploy as below --
> 2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
> 2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
> 2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
> name: dacPersistenceUnit
> ...]
> 2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
> 2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
> 2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
> 2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
> 2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
> 2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> Let me know incase require any more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt edited comment on DROOLS-3412 at 12/14/18 7:40 AM:
-----------------------------------------------------------------------
Hi, I am still in the tests. One additional thought which came up: For operations it would be good if we could get the size of a KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session leaks. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
was (Author: christianl):
Hi, I am still in the tests. One additional thought which came up: For operations it would be good if we could get the size of a KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session likes. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt edited comment on DROOLS-3412 at 12/14/18 7:40 AM:
-----------------------------------------------------------------------
Hi, I am still in the tests. One additional thought which came up: For operations it would be good if we could get the size of an KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session likes. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
was (Author: christianl):
Hi, I am still in the tests. One additional thought which came up: For operation it would be good if we could get the size of an KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session likes. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt edited comment on DROOLS-3412 at 12/14/18 7:40 AM:
-----------------------------------------------------------------------
Hi, I am still in the tests. One additional thought which came up: For operations it would be good if we could get the size of a KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session likes. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
was (Author: christianl):
Hi, I am still in the tests. One additional thought which came up: For operations it would be good if we could get the size of an KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session likes. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt commented on DROOLS-3412:
---------------------------------------------
Hi, I am still in the tests. One additional thought which came up: For operation it would be good if we could get the size of an KieSessionsPool. This way operations could monitor the number of open sessions and react to issues like session likes. I think the change for that would be quite simple too. So something like this should be sufficient:
{code:java}
diff --git a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
index 26068a6477..ee3bee8916 100644
--- a/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
+++ b/drools-core/src/main/java/org/drools/core/impl/AbstractKieSessionsPool.java
@@ -62,4 +62,8 @@ public abstract class AbstractKieSessionsPool implements KieSessionsPool {
protected abstract StatefulSessionPool createStatefulSessionPool( String kSessionName, KieSessionConfiguration conf, boolean stateless );
protected abstract String getKey(String kSessionName, KieSessionConfiguration conf, boolean stateless);
+
+ public int size() {
+ return pools.size();
+ }
}
{code}
Would this be something you would want to add?
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0
[JBoss JIRA] (JGRP-2319) MULTI_PING doesn't work anymore
by Bela Ban (Jira)
Bela Ban created JGRP-2319:
------------------------------
Summary: MULTI_PING doesn't work anymore
Key: JGRP-2319
URL: https://issues.jboss.org/browse/JGRP-2319
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0.16
In JGRP-2317, parameter {{timeout}} was added to {{Discovery.findMembers()}}. This caused the overridden method in MULTI_PING not to be called any longer.
Effect: MULTI_PING is not used.
Todo: add {{@Override@}} and {{timeout}} parameter
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
- 1
- 0