[JBoss JIRA] (AS7-6770) Recovery manager service may not always use the correct orphan filters
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-6770?page=com.atlassian.jira.plugin.s... ]
jaikiran pai reassigned AS7-6770:
---------------------------------
Assignee: jaikiran pai (was: Jason Greene)
> Recovery manager service may not always use the correct orphan filters
> ----------------------------------------------------------------------
>
> Key: AS7-6770
> URL: https://issues.jboss.org/browse/AS7-6770
> Project: Application Server 7
> Issue Type: Bug
> Components: Transactions
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: jaikiran pai
> Assignee: jaikiran pai
>
> I've been looking into certain transaction recovery use cases (with EJB remote beans involved) and while investigating the issues, I noticed that the orphan filters being set in the JTAEnvironmentBean might not be available to the Recovery manager service. That's because the MSC service which sets up the transaction recovery manager service runs before the JTAEnvironmentBean is setup with the orphan filters, which actually happens in a separate MSC service (Arjuna tx manager service) which starts *after* the recovery manager MSC service.
> (Sorry, don't have the code in front of me, else would have added the exact class names - will do so later).
--
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
12 years, 6 months
[JBoss JIRA] (AS7-6828) Cannot add empty messaging subsystem using CLI
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-6828:
--------------------------------
Summary: Cannot add empty messaging subsystem using CLI
Key: AS7-6828
URL: https://issues.jboss.org/browse/AS7-6828
Project: Application Server 7
Issue Type: Feature Request
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.Alpha1
It's not possible to add empty messaging subsystem using CLI:
[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=backup:add()
{
"outcome" => "failed",
"failure-description" => "JBAS011679: No connectors definition present.",
"rolled-back" => true
}
--
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
12 years, 6 months
[JBoss JIRA] (DROOLS-92) NPE when removing a rule using a Java object with Drools annotations
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-92?page=com.atlassian.jira.plugin.... ]
Mario Fusco resolved DROOLS-92.
-------------------------------
Fix Version/s: (was: 6.0.0.Alpha1)
Resolution: Done
I fixed it on the 5.6. It was already ok on the master because of the changes in the rewiring process.
> NPE when removing a rule using a Java object with Drools annotations
> --------------------------------------------------------------------
>
> Key: DROOLS-92
> URL: https://issues.jboss.org/browse/DROOLS-92
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Reporter: Davide Sottara
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 5.6
>
>
> - Drools 5.5.x still has Accessors : field readers and writers. They are created consistently (reader+writer) for declared types, but in case of non-declared types (java objects), only readers are created, and only when
> a field is involved in a constraint.
> - when a rule is added (dynamically) during an incremental construction process, the packagebuilder creates "redeclarations" (TypeDeclarations with
> NATURE == DECLARATION) of involved classes, in order to process annotations
> such as @Position or @Modifies.
> - if a rule triggers the removal/update of a rule in its own KB, AbstractRuleBase.executeQueuedActions() is called, which tries to rewire the accessors
> Problem: if the modified rule's package contains a TypeDeclaration for
> an annotated java object, only the reader will exist and the rewiring
> process will throw a NPE as it tries to rewire the writer.
> Possible solutions?
> a) make the rewiring process check that an accessor exists before trying to rewire it
> OR
> b) change AbstractRuleBase.executeQueuedActions() - the code seems to have
> been removed in 6.x (master)
> OR
> c) limit the rewiring to TypeDeclarations with Nature == DEFINITION
> OR
> d) always create the writer together with the reader
--
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
12 years, 6 months
[JBoss JIRA] (AS7-5937) UndeclaredThrowableException if EJB invocation fails with IOException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-5937?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-5937:
----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 901006|https://bugzilla.redhat.com/show_bug.cgi?id=901006]
Never seen this anymore. The exceptions that I refer to in my comment from 2013-02-07 are likely a manifestation of bug 900520 or 900999.
> UndeclaredThrowableException if EJB invocation fails with IOException
> ---------------------------------------------------------------------
>
> Key: AS7-5937
> URL: https://issues.jboss.org/browse/AS7-5937
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Richard Janík
> Assignee: Stuart Douglas
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
>
>
> UndeclaredThrowableExceptions were seen at failover testing through server crashes. Scenarios: jvmkill-dist-async, jvmkill-repl-async, jvmkill-repl-sync. Stack traces:
> {code}
> 2012/09/27 09:10:22:331 EDT [ERROR][Runner - 1533] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.io.IOException: Broken pipe
> at sun.nio.ch.FileDispatcher.write0(Native Method)
> at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:69)
> at sun.nio.ch.IOUtil.write(IOUtil.java:40)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
> at org.xnio.nio.AbstractNioStreamChannel.write(AbstractNioStreamChannel.java:303)
> at org.xnio.channels.FramedMessageChannel.doFlushBuffer(FramedMessageChannel.java:295)
> at org.xnio.channels.FramedMessageChannel.doFlush(FramedMessageChannel.java:309)
> at org.xnio.channels.FramedMessageChannel.send(FramedMessageChannel.java:236)
> at org.xnio.channels.Channels.sendBlocking(Channels.java:200)
> at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:109)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:126)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:114)
> at org.xnio.streams.BufferPipeOutputStream.flush(BufferPipeOutputStream.java:143)
> at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:161)
> at org.jboss.remoting3.remote.OutboundMessage.close(OutboundMessage.java:193)
> at org.jboss.ejb.client.remoting.ChannelAssociation.releaseChannelMessageOutputStream(ChannelAssociation.java:266)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:203)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> 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
> {code}
> {code}
> 2012/09/27 09:10:22:344 EDT [ERROR][Runner - 114] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.remoting3.NotOpenException: Writes closed
> at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:107)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
> at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:249)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:196)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> 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
> {code}
> {code}
> 2012/09/27 09:14:37:914 EDT [ERROR][Runner - 335] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.io.IOException: Channel Channel ID 9d26983d (outbound) of Remoting connection 12dfbabd to null has been closed
> at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:115)
> at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:107)
> at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:517)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:382)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:103)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:78)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> {code}
> These exceptions were numerous and were seen by clients (ejb remote calls) after node crash. This is the client call of the bean:
> {code}
> myBean = (RemoteStatefulSB) context.lookup("ejb:" + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "!" + viewClassName + "?stateful");
> {code}
> Links to hudson jobs:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
--
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
12 years, 6 months
[JBoss JIRA] (AS7-5937) UndeclaredThrowableException if EJB invocation fails with IOException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-5937?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-5937:
----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 901006|https://bugzilla.redhat.com/show_bug.cgi?id=901006] from ON_QA to VERIFIED
> UndeclaredThrowableException if EJB invocation fails with IOException
> ---------------------------------------------------------------------
>
> Key: AS7-5937
> URL: https://issues.jboss.org/browse/AS7-5937
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Richard Janík
> Assignee: Stuart Douglas
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
>
>
> UndeclaredThrowableExceptions were seen at failover testing through server crashes. Scenarios: jvmkill-dist-async, jvmkill-repl-async, jvmkill-repl-sync. Stack traces:
> {code}
> 2012/09/27 09:10:22:331 EDT [ERROR][Runner - 1533] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.io.IOException: Broken pipe
> at sun.nio.ch.FileDispatcher.write0(Native Method)
> at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:69)
> at sun.nio.ch.IOUtil.write(IOUtil.java:40)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
> at org.xnio.nio.AbstractNioStreamChannel.write(AbstractNioStreamChannel.java:303)
> at org.xnio.channels.FramedMessageChannel.doFlushBuffer(FramedMessageChannel.java:295)
> at org.xnio.channels.FramedMessageChannel.doFlush(FramedMessageChannel.java:309)
> at org.xnio.channels.FramedMessageChannel.send(FramedMessageChannel.java:236)
> at org.xnio.channels.Channels.sendBlocking(Channels.java:200)
> at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:109)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:126)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:114)
> at org.xnio.streams.BufferPipeOutputStream.flush(BufferPipeOutputStream.java:143)
> at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:161)
> at org.jboss.remoting3.remote.OutboundMessage.close(OutboundMessage.java:193)
> at org.jboss.ejb.client.remoting.ChannelAssociation.releaseChannelMessageOutputStream(ChannelAssociation.java:266)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:203)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> 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
> {code}
> {code}
> 2012/09/27 09:10:22:344 EDT [ERROR][Runner - 114] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.remoting3.NotOpenException: Writes closed
> at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:107)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
> at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:249)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:196)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
> 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
> {code}
> {code}
> 2012/09/27 09:14:37:914 EDT [ERROR][Runner - 335] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy0.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:75)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.io.IOException: Channel Channel ID 9d26983d (outbound) of Remoting connection 12dfbabd to null has been closed
> at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:115)
> at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:107)
> at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:517)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:382)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:103)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:78)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> {code}
> These exceptions were numerous and were seen by clients (ejb remote calls) after node crash. This is the client call of the bean:
> {code}
> myBean = (RemoteStatefulSB) context.lookup("ejb:" + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "!" + viewClassName + "?stateful");
> {code}
> Links to hudson jobs:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Fail...
--
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
12 years, 6 months
[JBoss JIRA] (DROOLS-92) NPE when removing a rule using a Java object with Drools annotations
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-92?page=com.atlassian.jira.plugin.... ]
Mario Fusco reassigned DROOLS-92:
---------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> NPE when removing a rule using a Java object with Drools annotations
> --------------------------------------------------------------------
>
> Key: DROOLS-92
> URL: https://issues.jboss.org/browse/DROOLS-92
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Reporter: Davide Sottara
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 5.6, 6.0.0.Alpha1
>
>
> - Drools 5.5.x still has Accessors : field readers and writers. They are created consistently (reader+writer) for declared types, but in case of non-declared types (java objects), only readers are created, and only when
> a field is involved in a constraint.
> - when a rule is added (dynamically) during an incremental construction process, the packagebuilder creates "redeclarations" (TypeDeclarations with
> NATURE == DECLARATION) of involved classes, in order to process annotations
> such as @Position or @Modifies.
> - if a rule triggers the removal/update of a rule in its own KB, AbstractRuleBase.executeQueuedActions() is called, which tries to rewire the accessors
> Problem: if the modified rule's package contains a TypeDeclaration for
> an annotated java object, only the reader will exist and the rewiring
> process will throw a NPE as it tries to rewire the writer.
> Possible solutions?
> a) make the rewiring process check that an accessor exists before trying to rewire it
> OR
> b) change AbstractRuleBase.executeQueuedActions() - the code seems to have
> been removed in 6.x (master)
> OR
> c) limit the rewiring to TypeDeclarations with Nature == DEFINITION
> OR
> d) always create the writer together with the reader
--
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
12 years, 6 months