[JBoss JIRA] Created: (JBREM-1289) CLONE [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker
by Ron Sigal (JIRA)
CLONE [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker
------------------------------------------------------------------------------------------
Key: JBREM-1289
URL: https://issues.jboss.org/browse/JBREM-1289
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.5.4.SP1, 2.2.4
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.4.SP2, 2.2.4.SP1
When the org.jboss.remoting.Client method
public Object invoke(InputStream inputStream, Object param) throws Throwable;
or one of its variants is called, it calls new StreamServer(inputStream), which creates an org.jboss.remoting.transport.Connector to serve the contents of the InputStream. To determine the transport to be used, StreamServer looks for a system property "remoting.stream.transport", and, if it doesn't exist, it uses "socket" by default. However, if the InputStream is being sent to a server in the same JVM, the "local" transport should be used.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBREM-1285) Callback Connector for in-jvm connection should create a LocalServerInvoker
by Ron Sigal (JIRA)
Callback Connector for in-jvm connection should create a LocalServerInvoker
---------------------------------------------------------------------------
Key: JBREM-1285
URL: https://issues.jboss.org/browse/JBREM-1285
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.5.4.SP1, 2.2.4
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.4.SP2, 2.2.4.SP1
When the org.jboss.remoting.Client method
public void addListener(InvokerCallbackHandler callbackhandler, Map metadata) throws Throwable;
or one of its variants is called, it checks if the ClientInvoker is an instance of BidirectionalClientInvoker as part of its determination of whether to set up push or pull callbacks. If the server is in the same jvm, and the parameter "force_remote" is not set to true, then the ClientInvoker will be an instance of LocalClientInvoker, which implements BidirectionalClientInvoker, so that push callbacks will be configured. That means that a callback Connector will be created, whose transport, if not configured in the metadata map, will be derived from the server's InvokerLocator. If, for instance, the transport in the InvokerLocator is "http", the callback Connector will create an instance of CoyoteInvoker. But CoyoteInvoker will create a ServerSocket, which is completely useless since callback invocations will be made by reference.
Client.addListener() should check that its ClientInvoker is a LocalClientInvoker, in which case it should use the "local" transport, before deriving the transport from the servers InvokerLocator.
Shout out to Justin Bertram for tracking down this problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBAS-9385) JBOSS 6.1 - HORNETQ Integration
by Subha Krishnan (JIRA)
JBOSS 6.1 - HORNETQ Integration
-------------------------------
Key: JBAS-9385
URL: https://issues.jboss.org/browse/JBAS-9385
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Subha Krishnan
Hi,
I downloaded JBOSS 6.1 because of Hornetq problem [JBAS - 7950]. When the application tries to deliver a message to a JMS topic, I get the following error message:
javax.jms.JMSException: Failed to create session factory
at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:605)
at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:143)
at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:138)
at jx.util.ejb.JMSPublisher.publishTopic(JMSPublisher.java:103)
at jx.util.ejb.JMSPublisher.publishInternalDocument(JMSPublisher.java:67)
at jx.visionTek.VisionTekConnection.publish(VisionTekConnection.java:78)
at jx.visionTek.VisionTekConnection.update(VisionTekConnection.java:117)
at java.util.Observable.notifyObservers(Observable.java:142)
at jx.io.AsyncReader.messageRecieved(AsyncReader.java:99)
at jx.visionTek.VisionTekReader.read(VisionTekReader.java:42)
at jx.io.AsyncReader.run(AsyncReader.java:72)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: Error instantiating connector factory "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory"
at org.hornetq.core.client.impl.ClientSessionFactoryImpl$1.run(ClientSessionFactoryImpl.java:1145)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl$1.run(ClientSessionFactoryImpl.java:1134)
at java.security.AccessController.doPrivileged(Native Method)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.instantiateConnectorFactory(ClientSessionFactoryImpl.java:1133)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:175)
at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:590)
at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:601)
... 11 more
Caused by: java.lang.ClassNotFoundException: Class not found org.hornetq.core.remoting.impl.netty.NettyConnectorFactory
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:897)
at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:505)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:450)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl$1.run(ClientSessionFactoryImpl.java:1140)
... 17 more
Caused by: java.lang.IllegalStateException: BaseClassLoader@de0ae6{vfs:///C:/JBoss/jboss-6.1.0-SNAPSHOT/server/all/deploy/vcms_visiontek.jar} classLoader is not connected to a domain (probably undeployed?) for class org.hornetq.core.remoting.impl.netty.NettyConnectorFactory
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:881)
... 21 more
Help would be greatly appreciated!
Subha
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (JBRULES-2957) Error "Unexpected exception executing action org.drools.reteoo.PropagationQueuingNode$PropagateAction@631b86c7" with two after-clauses
by Armin Steudte (JIRA)
Error "Unexpected exception executing action org.drools.reteoo.PropagationQueuingNode$PropagateAction@631b86c7" with two after-clauses
---------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-2957
URL: https://issues.jboss.org/browse/JBRULES-2957
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.1.1.FINAL
Environment: macosx snowleopard jdk 1.6.x
Reporter: Armin Steudte
Assignee: Mark Proctor
I'm getting the following Error "Unexpected exception executing action org.drools.reteoo.PropagationQueuingNode$PropagateAction@631b86c7" with one off my rules in my project.
The problem is linked with the use of two after statements in one rule.
If I delete one of them everything works like a charm.
The rule looks like this:
// Regeln
rule "Vergessene Herdplatte"
when
// Platte wurde eingeschaltet und es steht kein Topf auf ihr
$platte: HerdplatteEingeschaltet( plateOccupied == false ) from entry-point events
// und in den nächsten 20 sek wird die gleiche Platte nicht ausgeschaltet
not( HerdplatteAusgeschaltet( this.nummer == $platte.nummer, this after[0s,20s] $platte ) from entry-point events )
// oder es wird in den nächsten 20 sek kein Topf auf die Platte gestellt
not( TopfAufHerdplatte( this.nummer == $platte.nummer, this after[0s,20s] $platte ) from entry-point events )
then
System.out.println("Vergessene Herdplatte erkannt!");
end
If I comment one of the not-clause out, it works.
I created an unit-test which reproduces the exception.
And here the Failure Trace:
org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.PropagationQueuingNode$PropagateAction@631b86c7
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1473)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:182)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:145)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:96)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:44)
at com.sample.FusionTest.testRule(FusionTest.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: java.lang.NullPointerException
at org.drools.time.impl.CompositeMaxDurationTimer.createTrigger(CompositeMaxDurationTimer.java:58)
at org.drools.common.Scheduler.scheduleAgendaItem(Scheduler.java:55)
at org.drools.common.DefaultAgenda.scheduleItem(DefaultAgenda.java:314)
at org.drools.reteoo.RuleTerminalNode.assertLeftTuple(RuleTerminalNode.java:185)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:189)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:78)
at org.drools.reteoo.NotNode.assertLeftTuple(NotNode.java:101)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:189)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:78)
at org.drools.reteoo.NotNode.assertLeftTuple(NotNode.java:101)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:189)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateAssertLeftTuple(SingleLeftTupleSinkAdapter.java:64)
at org.drools.reteoo.JoinNode.assertObject(JoinNode.java:128)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59)
at org.drools.reteoo.PropagationQueuingNode$AssertAction.execute(PropagationQueuingNode.java:347)
at org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:229)
at org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:443)
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1471)
... 29 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months