[JBoss jBPM] - JBPM and JMSMQ
by curatiotech
I am trying to hook up my spring application with JBPM and JMS for asynchronous communications, I am getting a JNDI classcast exception when I deploy JmsMessageFactoryImpl as the message factory.
I was wondering if any one else has come across this problem,my understanding is that JBoss is providing a JMSConnectionFactoryImpl instead of the ConnectionFactory specified in web.xml resource-ref and expected by the JmsMessageFactoryImpl.
Please see stack below, I would appreciate any help.
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
aused by: java.lang.ClassCastException: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl cannot be cast to javax.jms.ConnectionFactory
tionFactory
at org.jbpm.msg.jms.JmsMessageServiceFactoryImpl.(JmsMessageServiceFactoryImpl.java:74)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.jbpm.configuration.BeanInfo.createObject(BeanInfo.java:86)
... 153 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172154#4172154
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172154
17 years, 8 months
[JBoss Cache: Core Edition] - Re: Eviction node event queue warning
by em161100
Hello,
The problem came back again even after setting the queue size to 500,000.
I can't just ignore this problem because it just takes too much cpu.
I have a question regarding the way the eviction work. I thought that the problem happens maybe because of the way I evict my objects and for some reason the cache thinks that the object was revisited and therefor adds it again to the cache. This is what I do in my eviction listener :
public void logNodeEvent(NodeEvent ne) {
Fqn fqnActionFather = ...
// handling evicition of nodes according to the object type
if (ne.getType().name().equals("NODE_EVICTED")) {
if (ne.getFqn().size() > 0) {
if (ne.getFqn().isChildOf(fqnActionFather )) { String id= (String) ne.getFqn().getLastElement();
Node node = ne.getCache().getNode(ne.getFqn());
if (node != null) {
Action action = (Action) node.get(id);
// handle eviction
}
.
.
.
.
Thanks for the help,
Elad.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172135#4172135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172135
17 years, 8 months