[JBoss JIRA] (WFLY-11522) Race condition in InfinispanRouteLocator logic can cause missing route
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-11522:
-----------------------------------
Summary: Race condition in InfinispanRouteLocator logic can cause missing route
Key: WFLY-11522
URL: https://issues.jboss.org/browse/WFLY-11522
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 15.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
If the determination of the primary owner of a given session immediately precedes a topology change, the returned address might no longer exist in the registry and thus the call to locate(...) can return null.
This causes the route to be omitted from the response.
In this situation, we should return the registry entry of the local node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11520) [GSS](7.2.z) SFSB not sticky on a single cluster node when clustering of the bean is disabled
by Jörg Bäsner (Jira)
Jörg Bäsner created WFLY-11520:
----------------------------------
Summary: [GSS](7.2.z) SFSB not sticky on a single cluster node when clustering of the bean is disabled
Key: WFLY-11520
URL: https://issues.jboss.org/browse/WFLY-11520
Project: WildFly
Issue Type: Bug
Components: Clustering, Remoting
Affects Versions: 15.0.0.Final
Environment: A clustered environment with 2 nodes. Both nodes started with an unmodified {{standalone-ha.xml}} configuration (see _Steps to Reproduce_)
This issue happens on 15.0.0.Final and was tested as well as on current head (sha: 372697282dccefd0b9df48e6aa4dcb69e1c4b40f).
Reporter: Jörg Bäsner
Assignee: Richard Achmatowicz
Attachments: reproducer.zip
In case a stateful session bean is annotated with:
{{@Stateful(passivationCapable=false)}}
then the serialization is *disabled* and thus the bean is only available on a single cluster node.
When a client now calls two different methods on this stateful bean it intermittently ends up on different cluster nodes, resulting in the following Exception:
{code}
ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component TestSessionEJB for method public abstract void test.ITestSession.method2(java.lang.String,java.lang.String) throws javax.ejb.EJBException,java.rmi.RemoteException: javax.ejb.NoSuchEJBException: WFLYEJB0168: Could not find EJB with id UUIDSessionID [4b0f4a27-40ba-411b-8852-0108a5ec64f4]
at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:55)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81)
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618)
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
at org.wildfly.security.auth.server.SecurityIdentity.runAsFunctionEx(SecurityIdentity.java:406)
at org.jboss.as.ejb3.remote.AssociationImpl.invokeWithIdentity(AssociationImpl.java:565)
at org.jboss.as.ejb3.remote.AssociationImpl.invokeMethod(AssociationImpl.java:546)
at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:197)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11521) Race condition in InfinispanRouteLocator logic can cause missing route
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-11521:
-----------------------------------
Summary: Race condition in InfinispanRouteLocator logic can cause missing route
Key: WFLY-11521
URL: https://issues.jboss.org/browse/WFLY-11521
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 15.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
If the determination of the primary owner of a given session immediately precedes a topology change, the returned address might no longer exist in the registry and thus the call to locate(...) can return null.
This causes the route to be omitted from the response.
In this situation, we should return the registry entry of the local node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Tibor Zimányi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Tibor Zimányi commented on DROOLS-3412:
---------------------------------------
Hi, great to hear that the performance is fixed. Regarding the size method, I wouldn't mind having it, however [~mfusco] is the main Drools master here :) Mario what do you think about it?
> 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
[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:
---------------------------------------------
[~tzimanyi], I've completed all tests. Performance seems to be fine now. Thanks for the fix. Let me know what you think about the idea in my previous comment.
> 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
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3406:
----------------------------------------
Great [~roger600] that helped a lot :-)
My next questions (sorry for doing on JIRA but our paths don't seem to be aligning at the moment!), now I have a _custom_ shape for {{DecisionService}} using some code like the following (it uses the base SVG shape from UX and adds a {{Line}} to it):
{code}
view = new SVGShapeViewImpl(name, primitiveShape, width, height, resizable);
final Line primitive = new com.ait.lienzo.client.core.shape.Line(0, height / 2, width, height / 2)......
final SVGPrimitiveShape divider = SVGPrimitiveFactory.newSVGPrimitiveShape(primitive, false, null);
view.addChild(divider);
{code}
I cannot use "scalable" as a {{Line}} has zero height (according to Lienzo) and causes an "Infinity" error in some JSON internal to Lienzo and {{WiresScalableContainer.scaleTo(..)}}. So I resize the width of the {{Line}} by adding a {{view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)}} which works OK.. now.. I want to (a) add a Control Point to the line to support moving it up and down (it'd be nice to have a drag constraint too); when released I'd like a Command to execute, (b) resizing the {{DecisionService}} from the Properties Panel does not lead to the {{Line}} being resized (no surprise really, as it's not invoking the {{ResizeHandler}}.. any ideas about this one? I see it also affects _core_ Stunner too (select a node so it's Control Points/Toolbox are visible) and resize it using the Properties Panel. The ControlPoints and Toolbox do not follow the resize from the Properties Panel.. anyway... suggestions as always welcomed :-)
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11519) Time-based metrics do not specify measurement unit
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-11519:
----------------------------------
Summary: Time-based metrics do not specify measurement unit
Key: WFLY-11519
URL: https://issues.jboss.org/browse/WFLY-11519
Project: WildFly
Issue Type: Bug
Components: JCA, Web (Undertow)
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Identifed metrics:
* Undertow:
* session-avg-alive-time
* session-max-alive-time
* max_processing_time
* processing_time
* Transactions
* transactions_average_commit_time
* Datasources
* average_blocking_time{data_source="ExampleDS",}
* average_creation_time{data_source="ExampleDS",}
* average_get_time{data_source="ExampleDS",}
* max_creation_time{data_source="ExampleDS",}
* max_pool_time{data_source="ExampleDS",}
* total_blocking_time{data_source="ExampleDS",}
* total_creation_time{data_source="ExampleDS",}
* total_get_time{data_source="ExampleDS",}
* max_wait_time{data_source="ExampleDS",}
* total_creation_time{data_source="ExampleDS",}
* average_pool_time{data_source="ExampleDS",}
* average_usage_time{data_source="ExampleDS",}
* max_usage_time{data_source="ExampleDS",}
* total_pool_time{data_source="ExampleDS",}
* total_usage_time{data_source="ExampleDS",}
* xacommit_average_time{data_source="ExampleDS",}
* xacommit_max_time{data_source="ExampleDS",}
* xacommit_total_time{data_source="ExampleDS",}
* xaend_average_time{data_source="ExampleDS",}
* xaend_max_time{data_source="ExampleDS",}
* xaend_total_time{data_source="ExampleDS",}
* xaforget_average_time{data_source="ExampleDS",}
* xaforget_max_time{data_source="ExampleDS",}
* xaforget_total_time{data_source="ExampleDS",}
* xaprepare_average_time{data_source="ExampleDS",}
* xaprepare_max_time{data_source="ExampleDS",}
* xaprepare_total_time{data_source="ExampleDS",}
* xarecover_average_time{data_source="ExampleDS",}
* xarecover_max_time{data_source="ExampleDS",}
* xarecover_total_time{data_source="ExampleDS",}
* xarollback_average_time{data_source="ExampleDS",}
* xarollback_max_time{data_source="ExampleDS",}
* xarollback_total_time{data_source="ExampleDS",}
* xastart_average_time{data_source="ExampleDS",}
* xastart_max_time{data_source="ExampleDS",}
* xastart_total_time{data_source="ExampleDS",}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[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:
-------------------------------
Summary: WAR deployment in 10.1.0 Final is failing itself after its successful deployment (was: war deployment in 10.1.0 Final is failing itself after its successful deployment)
> 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
[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.
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 --
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.
> 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