[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-12718:
-------------------------------------
As we discussed a number of times, there is something wrong with your MOD_JK configuration. Until this is fixed, it's not worth running, as it obfuscates the issue.
This log:
{noformat}
2019-11-04 11:24:52,121 ERROR o.j.e.c.j.ClusteringHTTPRequestSampler: Invalid serial: Expected 122, received 2 (previous: JSessionId{sessionId='bc844XEHEsfXWP4rcLnxVcIyr9TDcx4S-ULHzef9', jvmRoutes=[wildfly3]} current: JSessionId{sessionId='bc844XEHEsfXWP4rcLnxVcIyr9TDcx4S-ULHzef9', jvmRoutes=[wildfly1]})
samples sequence:
{noformat}
This suggests that the session state was lost in the previous request - are there log messages that indicate why?
> Clustering: replicated-cache sampling errors
> --------------------------------------------
>
> Key: WFLY-12718
> URL: https://issues.jboss.org/browse/WFLY-12718
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 18.0.0.Final
> Reporter: Tommasso Borgato
> Assignee: Paul Ferraro
> Priority: Blocker
>
> The issue is about replicated-cache in fail-over tests.
> WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add()
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add()
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl)
> {noformat}
> The test is run with wildfly-18.0.0.Final.zip;
> The same tests run with version wildfly-17.0.1.Final.zip do not have any problem;
> hence this looks like a regression;
> As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error;
> Here are the runs that exhibit this issue:
> - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...]
> We also repeated the tests to make sure it can be reproduced:
> - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JGRP-2393) JmxConfigurator creates an invalid object name when fixing duplicates
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2393?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2393.
----------------------------
Resolution: Done
> JmxConfigurator creates an invalid object name when fixing duplicates
> ---------------------------------------------------------------------
>
> Key: JGRP-2393
> URL: https://issues.jboss.org/browse/JGRP-2393
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.6
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.1.8
>
>
> {noformat}
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:559) ~[?:?]
> at javax.management.ObjectName.<init>(ObjectName.java:1406) ~[?:?]
> at org.jgroups.jmx.JmxConfigurator.getObjectName(JmxConfigurator.java:206) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.internalRegister(JmxConfigurator.java:173) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.register(JmxConfigurator.java:121) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:62) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:520) ~[classes/:?]
> {noformat}
> The generated object name is {{ClusteredCLITest:type=channel,cluster="org.infinispan.cli.interpreter.ClusteredCLITest"duplicate-52510}}, which is not valid because {{duplicate-52510}} is not part of any key=value pair.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-12689) WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
by Romain Pelisse (Jira)
[ https://issues.jboss.org/browse/WFLY-12689?page=com.atlassian.jira.plugin... ]
Romain Pelisse updated WFLY-12689:
----------------------------------
Labels: downstream_dependency (was: )
> WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
> ---------------------------------------------------------------------------------
>
> Key: WFLY-12689
> URL: https://issues.jboss.org/browse/WFLY-12689
> Project: WildFly
> Issue Type: Bug
> Components: JMX, JPA / Hibernate, Server
> Affects Versions: 18.0.0.Final
> Reporter: Masafumi Miura
> Assignee: Masafumi Miura
> Priority: Major
> Labels: downstream_dependency
> Fix For: 19.0.0.Beta1
>
>
> When a web application contains both MBean (jboss-service.xml) and persistence-unit (persistence.xml), the WAR deployment fails due to the following NullPointerException:
> {code}
> 11:51:03,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-mbean-webapp.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.service.MBeanServices.<init>(MBeanServices.java:107)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:124)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:109)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> ...(snip)...
> 11:51:03,687 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "helloworld-mbean-webapp.war")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-mbean-webapp.war\"
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService",
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService, jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]"
> ]
> }
> {code}
> This NPE happens because [WebNonTxEmCloserAction#dependencies()|https://github.com/wildfly/wildfly/...] returns null. It should return Collections.emptySet() instead of null.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JGRP-2393) JmxConfigurator creates an invalid object name when fixing duplicates
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2393?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2393:
---------------------------
Fix Version/s: 4.1.8
Priority: Minor (was: Major)
> JmxConfigurator creates an invalid object name when fixing duplicates
> ---------------------------------------------------------------------
>
> Key: JGRP-2393
> URL: https://issues.jboss.org/browse/JGRP-2393
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.6
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.1.8
>
>
> {noformat}
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:559) ~[?:?]
> at javax.management.ObjectName.<init>(ObjectName.java:1406) ~[?:?]
> at org.jgroups.jmx.JmxConfigurator.getObjectName(JmxConfigurator.java:206) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.internalRegister(JmxConfigurator.java:173) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.register(JmxConfigurator.java:121) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:62) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:520) ~[classes/:?]
> {noformat}
> The generated object name is {{ClusteredCLITest:type=channel,cluster="org.infinispan.cli.interpreter.ClusteredCLITest"duplicate-52510}}, which is not valid because {{duplicate-52510}} is not part of any key=value pair.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JGRP-2393) JmxConfigurator creates an invalid object name when fixing duplicates
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/JGRP-2393?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated JGRP-2393:
-------------------------------
Description:
{noformat}
javax.management.MalformedObjectNameException: Unterminated key property part
at javax.management.ObjectName.construct(ObjectName.java:559) ~[?:?]
at javax.management.ObjectName.<init>(ObjectName.java:1406) ~[?:?]
at org.jgroups.jmx.JmxConfigurator.getObjectName(JmxConfigurator.java:206) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.internalRegister(JmxConfigurator.java:173) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.register(JmxConfigurator.java:121) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:62) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:520) ~[classes/:?]
{noformat}
The generated object name is {{ClusteredCLITest:type=channel,cluster="org.infinispan.cli.interpreter.ClusteredCLITest"duplicate-52510}}, which is not valid because {{duplicate-52510}} is not part of any key=value pair.
was:
{noformat}
javax.management.MalformedObjectNameException: Unterminated key property part
at javax.management.ObjectName.construct(ObjectName.java:559) ~[?:?]
at javax.management.ObjectName.<init>(ObjectName.java:1406) ~[?:?]
at org.jgroups.jmx.JmxConfigurator.getObjectName(JmxConfigurator.java:206) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.internalRegister(JmxConfigurator.java:173) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.register(JmxConfigurator.java:121) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:62) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:520) ~[classes/:?]
{noformat}
The generated object name is `ClusteredCLITest:type=channel,cluster="org.infinispan.cli.interpreter.ClusteredCLITest"duplicate-52510`, which is not valid because `duplicate-52510` is not part of any `key=value` pair.
> JmxConfigurator creates an invalid object name when fixing duplicates
> ---------------------------------------------------------------------
>
> Key: JGRP-2393
> URL: https://issues.jboss.org/browse/JGRP-2393
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.6
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Priority: Major
>
> {noformat}
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:559) ~[?:?]
> at javax.management.ObjectName.<init>(ObjectName.java:1406) ~[?:?]
> at org.jgroups.jmx.JmxConfigurator.getObjectName(JmxConfigurator.java:206) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.internalRegister(JmxConfigurator.java:173) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.register(JmxConfigurator.java:121) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:62) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:520) ~[classes/:?]
> {noformat}
> The generated object name is {{ClusteredCLITest:type=channel,cluster="org.infinispan.cli.interpreter.ClusteredCLITest"duplicate-52510}}, which is not valid because {{duplicate-52510}} is not part of any key=value pair.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JGRP-2393) JmxConfigurator creates an invalid object name when fixing duplicates
by Dan Berindei (Jira)
Dan Berindei created JGRP-2393:
----------------------------------
Summary: JmxConfigurator creates an invalid object name when fixing duplicates
Key: JGRP-2393
URL: https://issues.jboss.org/browse/JGRP-2393
Project: JGroups
Issue Type: Bug
Affects Versions: 4.1.6
Reporter: Dan Berindei
Assignee: Bela Ban
{noformat}
javax.management.MalformedObjectNameException: Unterminated key property part
at javax.management.ObjectName.construct(ObjectName.java:559) ~[?:?]
at javax.management.ObjectName.<init>(ObjectName.java:1406) ~[?:?]
at org.jgroups.jmx.JmxConfigurator.getObjectName(JmxConfigurator.java:206) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.internalRegister(JmxConfigurator.java:173) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.register(JmxConfigurator.java:121) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:62) ~[jgroups-4.1.6.Final.jar:4.1.6.Final]
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:520) ~[classes/:?]
{noformat}
The generated object name is `ClusteredCLITest:type=channel,cluster="org.infinispan.cli.interpreter.ClusteredCLITest"duplicate-52510`, which is not valid because `duplicate-52510` is not part of any `key=value` pair.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4475) jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module
by Romain Pelisse (Jira)
[ https://issues.jboss.org/browse/WFCORE-4475?page=com.atlassian.jira.plugi... ]
Romain Pelisse updated WFCORE-4475:
-----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3779
> jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module
> ---------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4475
> URL: https://issues.jboss.org/browse/WFCORE-4475
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Bartosz Spyrko
> Assignee: Bartosz Spyrko
> Priority: Major
> Labels: downstream_dependency
>
> Follow up to JBEAP-13094 and JBEAP-14310
> annotations=true on a sub deployment module reference fails to deploy.
> This is the same test app from JBEAP-13094, the only change is the api jar is listed as a module in application.xml and then the j-d-s.xml depends on its deployment module.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <sub-deployment name="application-exception-ejb.jar">
> <dependencies>
> <module name="deployment.application-exception-api.jar" annotations="true" meta-inf="export"/>
> </dependencies>
> </sub-deployment>
> <sub-deployment name="application-exception-client-singleton.jar">
> <dependencies>
> <module name="deployment.application-exception-api.jar" annotations="true" meta-inf="export"/>
> </dependencies>
> </sub-deployment>
> </jboss-deployment-structure>
> {code}
> {code}
> 23:28:46,235 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main]",
> "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main]"
> ]
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months