[JBoss JIRA] (AS7-3902) NPE in JGroups on shutting down the server
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3902:
-----------------------------------
Summary: NPE in JGroups on shutting down the server
Key: AS7-3902
URL: https://issues.jboss.org/browse/AS7-3902
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.1.1.Final
Ran into while manually playing around.
1/ 2 server
2/ client requesting session on #1
3/ #2 is shut down >
Preceeding this log is AS7-3180.
{noformat}
17:23:39,763 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher
17:23:40,086 SEVERE [org.jgroups.JChannel] failed destroying the protocol stack: java.lang.NullPointerException
at org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:174) [jboss-as-clustering-jgroups-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at org.jgroups.stack.DiagnosticsHandler.stop(DiagnosticsHandler.java:76) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.protocols.TP.stop(TP.java:1010) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.protocols.UDP.stop(UDP.java:248) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:996) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.stopStack(JChannel.java:923) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.disconnect(JChannel.java:380) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel._close(JChannel.java:909) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.close(JChannel.java:389) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.stop(ChannelService.java:61) [jboss-as-clustering-jgroups-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at org.jboss.as.clustering.msc.AsynchronousService$2.run(AsynchronousService.java:84) [jboss-as-clustering-common-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
17:23:40,090 SEVERE [org.jgroups.JChannel] failed destroying the protocol stack: java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:922) [rt.jar:1.6.0_29]
at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:980) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.stopStack(JChannel.java:923) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel._close(JChannel.java:910) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.close(JChannel.java:389) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.stop(ChannelService.java:61) [jboss-as-clustering-jgroups-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at org.jboss.as.clustering.msc.AsynchronousService$2.run(AsynchronousService.java:84) [jboss-as-clustering-common-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (AS7-3796) Remote EJB client seems to be leaking messages MAX_OUTBOUND_MESSAGES (ChannelBusyException: Too many open outbound writes)
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3796:
-----------------------------------
Summary: Remote EJB client seems to be leaking messages MAX_OUTBOUND_MESSAGES (ChannelBusyException: Too many open outbound writes)
Key: AS7-3796
URL: https://issues.jboss.org/browse/AS7-3796
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB, Remoting
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: David Lloyd
Priority: Critical
Fix For: 7.1.1.Final
David and Jaikiran,
lets revisit this topic. I still think were are leaking messages in remoting3. Badly. Even though I set MAX_O_Ms to 100K it still results in:
{noformat}
2012/02/16 08:34:48:728 EST [WARN ][Runner - 227] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 227.>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 227.
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:79)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
... 3 more
Caused by: org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111)
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:235)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:193)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
... 5 more
{noformat}
Here is a snip from the client properties:
{noformat}
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=perf18,perf19,perf20,perf21
remote.connection.perf18.host=perf18
remote.connection.perf18.port=4447
remote.connection.perf18.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.perf18.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (AS7-5728) ClusteredSingleSignOn doesn't remove ssoId from sso cluster on Request.logout
by Stian Thorgersen (JIRA)
Stian Thorgersen created AS7-5728:
-------------------------------------
Summary: ClusteredSingleSignOn doesn't remove ssoId from sso cluster on Request.logout
Key: AS7-5728
URL: https://issues.jboss.org/browse/AS7-5728
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.3.Final (EAP)
Reporter: Stian Thorgersen
Logging out a user with Request.logout doesn't work with clustered SSO. This is caused by ClusteredSingleSignOn.deregister(String) not remove the ssoId from the SSO cluster. The ClusteredSingleSignOn.sessionEvent removes it from both the local cache and the SSO cluster, so a workaround is to call Session.invalidate() prior to calling Request.logout().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (JBRULES-3279) Error message when using 2 patterns inside a single accumulate is not clear: Parser returned a null Package
by Geoffrey De Smet (Created) (JIRA)
Error message when using 2 patterns inside a single accumulate is not clear: Parser returned a null Package
-----------------------------------------------------------------------------------------------------------
Key: JBRULES-3279
URL: https://issues.jboss.org/browse/JBRULES-3279
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.3.0.Final
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
I am trying to parse this rule:
{code}
rule "machineUsage"
when
$machineCapacity : MrMachineCapacity($machine : machine, $resource : resource)
$usageTotal : Number() from accumulate(
MrProcessRequirement(resource == $resource, $process : process, $usage : usage)
MrProcessAssignment(machine == $machine, process == $process),
sum($usage)
)
then
...
end
{code}
And I get this error message:
{code}
Exception in thread "main" java.lang.IllegalStateException: There are errors in the scoreDrl's:[47,77]: [ERR 102] Line 47:77 mismatched input ',' in rule "machineUsage"
[0,0]: Parser returned a null Package
{code}
For this line:
{code}
MrProcessAssignment(machine == $machine, process == $process),
{code}
It clear that it's because I can't use 2 patterns inside a single accumulate, but the error message seems wrong?
When I try this instead:
{code}
rule "machineUsage"
when
$machineCapacity : MrMachineCapacity($machine : machine, $resource : resource)
$usageTotal : Number() from accumulate(
(MrProcessRequirement(resource == $resource, $process : process, $usage : usage)
and MrProcessAssignment(machine == $machine, process == $process)),
sum($usage)
)
then
...
end
{code}
I get:
{code}
Exception in thread "main" org.drools.RuntimeDroolsException: BUG: Can't build a rete network with an inner OR group element
{code}
Don't really see the OR in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (AS7-5823) Create class hierarchy
by Harald Pehl (JIRA)
Harald Pehl created AS7-5823:
--------------------------------
Summary: Create class hierarchy
Key: AS7-5823
URL: https://issues.jboss.org/browse/AS7-5823
Project: Application Server 7
Issue Type: Sub-task
Reporter: Harald Pehl
Seperate classes into two distinct packages:
* org.jboss.mbui.aui: Contains classes for the abstract ui layer
* org.jboss.mbui.cui: Contains classes for the concrete ui layer
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months