[JBoss JIRA] (WFLY-5457) org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped during server shutdown
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-5457?page=com.atlassian.jira.plugin.... ]
Romain Pelisse commented on WFLY-5457:
--------------------------------------
I took a look at this issue, and I agree with Paul. Those messages are harmless and there is no simple way to "make them go". Thus, I'll close this issue as WON'T FIX.
> org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped during server shutdown
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5457
> URL: https://issues.jboss.org/browse/WFLY-5457
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR2
> Reporter: Michal Vinkler
> Assignee: Romain Pelisse
> Priority: Minor
>
> EAP 7.0.0.DR11
> Scenario: failover-http-session-shutdown-repl-sync, using graceful shutdown
> During server shutdown, perf19 logged this single-line error message few times:
> {code}
> ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-18,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> {code}
> Right after that the server stopped, see the log:
> {code}
> [JBossINF] [0m[0m06:40:01,917 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Undertow 1.3.0.CR2 stopping
> [JBossINF] [0m[0m06:40:01,917 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-passivating.war) in 10472ms
> [JBossINF] [0m[31m06:40:01,916 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-18,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,921 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-10,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-20,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-17,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-13,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-1,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,922 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-8,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,922 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-12,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[0m06:40:01,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 10476ms
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-19,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[0m06:40:01,970 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR5) stopped in 10521ms
> [JBossINF] [0m
> 2015/10/02 06:40:02:479 EDT [DEBUG][RMI TCP Connection(12)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Server is down.
> {code}
> Server log
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5457) org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped during server shutdown
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-5457?page=com.atlassian.jira.plugin.... ]
Romain Pelisse closed WFLY-5457.
--------------------------------
Resolution: Won't Fix
> org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped during server shutdown
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5457
> URL: https://issues.jboss.org/browse/WFLY-5457
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR2
> Reporter: Michal Vinkler
> Assignee: Romain Pelisse
> Priority: Minor
>
> EAP 7.0.0.DR11
> Scenario: failover-http-session-shutdown-repl-sync, using graceful shutdown
> During server shutdown, perf19 logged this single-line error message few times:
> {code}
> ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-18,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> {code}
> Right after that the server stopped, see the log:
> {code}
> [JBossINF] [0m[0m06:40:01,917 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Undertow 1.3.0.CR2 stopping
> [JBossINF] [0m[0m06:40:01,917 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-passivating.war) in 10472ms
> [JBossINF] [0m[31m06:40:01,916 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-18,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,921 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-10,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-20,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-17,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-13,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-1,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,922 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-8,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[31m06:40:01,922 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-12,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[0m06:40:01,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 10476ms
> [JBossINF] [0m[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-19,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
> [JBossINF] [0m[0m06:40:01,970 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR5) stopped in 10521ms
> [JBossINF] [0m
> 2015/10/02 06:40:02:479 EDT [DEBUG][RMI TCP Connection(12)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Server is down.
> {code}
> Server log
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-981) when I update the stateful rule, the rule is not be actived
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-981?page=com.atlassian.jira.plugin... ]
Mario Fusco closed DROOLS-981.
------------------------------
Resolution: Rejected
The fixed you suggested for DROOLS-978 was not correct. I believe that the fix I pushed should solve also this second problem.
> when I update the stateful rule, the rule is not be actived
> -----------------------------------------------------------
>
> Key: DROOLS-981
> URL: https://issues.jboss.org/browse/DROOLS-981
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: bing yang
> Assignee: Mario Fusco
> Labels: jboss, statefule
>
> this issue is due to[ https://issues.jboss.org/browse/DROOLS-978]. I modified the source(NodeTypeEnums.java:Line 88):add if node is null, then return false.
> there is no NPE, but I find that the updated rule is not be actived by adding the listener on the session.
> So, I want to know whether my test case is not correct? or the drools does not support the stateful rule's update? or this is the drools's bug?
> but If i modify the org.drools.core.reteoo.TimerNode like this:
> public void setNodePosMaskBit(long segmentPos) {
> // this.nodePosMaskBit = segmentPos;
> this.nodePosMaskBit = 1;
> }
> then the rule will be actived, but i dont know whether this can cause other questions.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-152) ServiceRegistry race condition
by Karl von Randow (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-152?page=com.atlassian.jira.plu... ]
Karl von Randow commented on HIBERNATE-152:
-------------------------------------------
I believe I have just encountered this issue, but with DatasourceConnectionProviderImpl and specifically a race to complete {{configure(Map)}} and calling {{getConnection()}}.
I have two threads that both start at the same time, immediately after the {{SessionFactory}} has been created. It appears that the first thread creates the {{ConnectionProvider}} service and then configures it, while the second thread gets the unconfigured {{ConnectionProvider}} service instance and tries to use it, calling {{getConnection}} and failing because it is not configured.
I can reproduce this quite reliably (although not every time, by nature of the race condition) in my development environment. I am happy to test a solution.
> ServiceRegistry race condition
> ------------------------------
>
> Key: HIBERNATE-152
> URL: https://issues.jboss.org/browse/HIBERNATE-152
> Project: Hibernate Integration
> Issue Type: Bug
> Reporter: rob moffat
> Assignee: Steve Ebersole
> Priority: Minor
>
> If I have multiple threads, all trying to use StatementPreparer, then what happens is that they all get a RefCursorSupport from the service registry, and start using it.
> The problem is, the initialisation process is: 1) create the instance of RefCursorSupport, 2) add it to the service registry, 3) then initialise the fields on it (specifically, jdbcServices).
> However, because the object is available from the service registry after creation, but before initialisation, the other threads can pull this back and start using it without jdbcServices initialised.
> This is a pervasive problem for all the objects in the service registry which have injected services that they depend on, I would think. I'm very surprised this hasn't been spotted sooner and fixed.
> cheers,
> Rob
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5596) MessageDrivenComponent startDelivery/stopDelivery is not thread safe
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5596?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-5596:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1282661
Bugzilla Update: Perform
> MessageDrivenComponent startDelivery/stopDelivery is not thread safe
> --------------------------------------------------------------------
>
> Key: WFLY-5596
> URL: https://issues.jboss.org/browse/WFLY-5596
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JMS
> Affects Versions: 10.0.0.CR4
> Reporter: James Livingston
> Assignee: Jeff Mesnil
>
> WFLY-4470 made a change to prevent MDBs being activated or deactivated multiple times, but it is not thread safe. A volatile boolean is used for the flag, but there is no protection against multiple threads invoking the methods simultaneously.
> Possible effects include:
> * activating the endpoint twice, with (probably) only one deactivation later, leading to not de-registering XA resources from the recovery manager properly
> * activate() and deactivate() running in the wrong order if done by separate threads
> Several simple solutions probably will not work correctly. Using an AtomicBoolean would stop multiple activations/deactivations from concurrent calls, but would mean that startDelivery() could return before the activation was one. Using a synchronized block or other exclusive lock would work, however since it involves invoking non-container code (the resource adapter), there could potentially be a deadlock risk if that invoked some related container functionality.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5684) Injection of ArquillianResource URL fails in Wildfly 10 CR4
by John Ament (JIRA)
[ https://issues.jboss.org/browse/WFLY-5684?page=com.atlassian.jira.plugin.... ]
John Ament commented on WFLY-5684:
----------------------------------
Ok, finally figured out the CLI commands. Had to do
{code}
cd /socket-binding-group=
cd standard-sockets
:read-resource
{code}
And the output is
{code}
{
"outcome" => "success",
"result" => {
"default-interface" => "public",
"name" => "standard-sockets",
"port-offset" => expression "${jboss.socket.binding.port-offset:0}",
"local-destination-outbound-socket-binding" => undefined,
"remote-destination-outbound-socket-binding" => {"mail-smtp" => undefined},
"socket-binding" => {
"management-http" => undefined,
"management-https" => undefined,
"ajp" => undefined,
"http" => undefined,
"https" => undefined,
"txn-recovery-environment" => undefined,
"txn-status-manager" => undefined
}
}
}
{code}
This is against a completely vanilla running instance.
> Injection of ArquillianResource URL fails in Wildfly 10 CR4
> -----------------------------------------------------------
>
> Key: WFLY-5684
> URL: https://issues.jboss.org/browse/WFLY-5684
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR4
> Reporter: John Ament
> Assignee: Jason Greene
>
> I recently added injection of an ArquillianResource URL to a test. I also just tried upgrading from WF9 to WF10.CR4. In CR4, it seems that this injection is working a bit weird.
> My injection is very simple
> {code}
> @ArquillianResource
> private URL url;
> {code}
> However, I see this output when running (note that my HTTP listener is on 8082)
> {code}
> 11:37:40,922 INFO [org.apache.http.impl.client.DefaultHttpClient] (default task-46) I/O exception (java.net.SocketException) caught when connecting to {}->http://[::]:8082: Network is unreachable
> 11:37:40,922 INFO [org.apache.http.impl.client.DefaultHttpClient] (default task-46) Retrying connect to {}->http://[::]:8082
> 11:37:47,069 INFO [org.apache.http.impl.client.DefaultHttpClient] (default task-46) I/O exception (java.net.SocketException) caught when connecting to {}->http://[::]:8082: Network is unreachable
> 11:37:47,069 INFO [org.apache.http.impl.client.DefaultHttpClient] (default task-46) Retrying connect to {}->http://[::]:8082 11:37:54,163 INFO [org.apache.http.impl.client.DefaultHttpClient] (default task-46) I/O exception (java.net.SocketException) caught when connecting to {}->http://[::]:8082: Network is unreachable
> 11:37:54,163 INFO [org.apache.http.impl.client.DefaultHttpClient] (default task-46) Retrying connect to {}->http://[::]:8082
> {code}
> It would appear that the host portion of the URL is being lost.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months