org.drools.RuntimeDroolsException: unable to determine Value

[jjarkko]

Just found this on the server log. Anyone seen this before?

org.drools.RuntimeDroolsException: unable to determine ValueType for Class [class org.jboss.internal.soa.esb.message.format.xml.MessageImpl]
at org.drools.base.ValueType.determineValueType(ValueType.java:222)
at org.drools.base.ClassObjectType.(ClassObjectType.java:56)
at org.drools.reteoo.Rete$ClassObjectTypeConf.(Rete.java:442)
at org.drools.reteoo.Rete.assertObject(Rete.java:152)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:192)
at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:900)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:883)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:684)
at org.drools.reteoo.ReteooStatelessSession.execute(ReteooStatelessSession.java:160)
at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRules(DroolsRuleService.java:584)
at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRules(DroolsRuleService.java:126)
at org.jboss.internal.soa.esb.services.rules.RuleServiceCallHelper.executeRulesService(RuleServiceCallHelper.java:126)
at org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route(JBossRulesRouter.java:123)
at org.jboss.soa.esb.actions.ContentBasedWiretap.executeRules(ContentBasedWiretap.java:168)
at org.jboss.soa.esb.actions.ContentBasedWiretap.process(ContentBasedWiretap.java:140)
at org.jboss.soa.esb.actions.ContentBasedRouter.process(ContentBasedRouter.java:58)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:896)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:735)

[marklittle]

What has this to do with the Design of ESB? Moving to User Forums. Please post these kinds of queries there.

[jjarkko]

Yes, sorry that was my mistake but I couldn't move it afterwards. I just googled "jboss esb forum" and posted a message, previously google had forwarded me to to the user forum.

This seems to be some kind of class loader issue I presume, but I'm not sure. This exception occurs if I define " -Djboss.messaging.groupname=FESB_MessagingPostOffice" which I tought would help some of the clustering / lost JMS replies issues we're having.

We've two ESB clusters A and B, with two nodes on each cluster (totalling 4 nodes).

They share the same UDDI. This itself seems to be a little problematic.

Cluster A hosts services which are used through webservice from a portal layer.

Cluster B hosts services which are used through JMS (ServiceInvoker) from cluster A.

Now, sometimes reply from a service in Cluster B does not come back to cluster A --> the web services times out. And this is what I'm investigating.

[jjarkko]

This only occurs when running on IBM JDK 6R3.