Error in jbpm 3.2.3?

[xigua]

I few errors I noticed. When I started the websale sample server, I got a few errors:
09:52:46,875 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml
09:52:46,890 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
09:52:46,906 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
09:52:46,921 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
09:52:46,921 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
09:52:46,968 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
09:52:47,000 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
09:52:47,015 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
09:52:47,031 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
09:52:47,046 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
09:52:47,062 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
09:52:47,078 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
09:52:47,125 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
09:52:47,140 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
09:52:47,156 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
09:52:47,171 ERROR [STDERR] Jul 14, 2008 9:52:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/
tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml

I can still connect to http://localhost:8080/jbpm-console though. But when I signle the process to enter the "fork", I am getting the following exceptioN:

exception

javax.servlet.ServletException: Servlet execution threw an exception
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)


root cause

java.lang.UnsupportedClassVersionError: Bad version number in .class file
java.lang.ClassLoader.defineClass1(Native Method)
java.lang.ClassLoader.defineClass(ClassLoader.java:620)
java.lang.ClassLoader.defineClass(ClassLoader.java:465)
org.jbpm.instantiation.ProcessClassLoader.findClass(ProcessClassLoader.java:111)
java.lang.ClassLoader.loadClass(ClassLoader.java:306)
java.lang.ClassLoader.loadClass(ClassLoader.java:251)
org.jbpm.instantiation.Delegation.instantiate(Delegation.java:140)
org.jbpm.instantiation.Delegation.getInstance(Delegation.java:125)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
org.jbpm.instantiation.Delegation_$$_javassist_4.getInstance(Delegation_$$_javassist_4.java)
org.jbpm.graph.def.Action.execute(Action.java:121)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
org.jbpm.graph.def.Action_$$_javassist_63.execute(Action_$$_javassist_63.java)
org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:259)
org.jbpm.graph.def.Node.execute(Node.java:338)
org.jbpm.graph.def.Node.enter(Node.java:318)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
org.jbpm.graph.def.Node_$$_javassist_49.enter(Node_$$_javassist_49.java)
org.jbpm.graph.def.Transition.take(Transition.java:151)
org.jbpm.graph.def.Node.leave(Node.java:393)
org.jbpm.graph.def.Node.leave(Node.java:368)
org.jbpm.graph.node.Fork.execute(Fork.java:140)
org.jbpm.graph.def.Node.enter(Node.java:318)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
org.jbpm.graph.def.Node_$$_javassist_49.enter(Node_$$_javassist_49.java)
org.jbpm.graph.def.Transition.take(Transition.java:151)
org.jbpm.graph.def.Node.leave(Node.java:393)
org.jbpm.graph.node.TaskNode.leave(TaskNode.java:209)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
org.jbpm.graph.def.Node_$$_javassist_49.leave(Node_$$_javassist_49.java)
org.jbpm.graph.exe.Token.signal(Token.java:192)
org.jbpm.graph.exe.Token.signal(Token.java:155)
org.jbpm.jsf.core.action.SignalActionListener.handleAction(SignalActionListener.java:56)
org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82)
javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:746)
javax.faces.component.UICommand.broadcast(UICommand.java:368)
javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447)
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)


note The full stack trace of the root cause is available in the JBossWeb/2.0.1.GA logs.

I am using jdk1.5.0_12, which version should I use? I though jbpm supports 1.4 and 1.5.

Thanks

[kukeltje]

2 things (and I do not want to sound rude, but going to say it anyway)

1: STFF, Google is your friend
2: Learn java (or use 1)

[villatore]

Ronald, I appreciate your time, to respond all our messages, but this kind of answers, does not help us to resolve our problems. Some persons does not have your level of technical knowledge, still that seems trivial the doubt. We are trying to learn your tool, but we can chose your tool or other. Try not be rude.

____________
Xigua try to use, a newest java version, like 6, it most run on it, if it done, try with one more old, and on and on, you can discover, until the JDK is supported.

[kukeltje]

I know, but most people know how to use google... some small searches with basic terms from the 'errors' yields lots of results... lots....

The thing is that these errors have *nothing* to do with jBPM. The first one is just a plain jdk-logging/log4j logging thing, the second one is because classes are compiled with a newer jdk then the one they run on without code compatibility.... see... *nothing* to do with jBPM

[xigua]

First of all, I should have pointed out that I tried both jbpm 3.2.2 and 3.2.3 and the example websale app worked out of box on 3.2.2 but not 3.2.3 on me. My apologies on that.

Secondly, Ronald, yes, you are rude to have this kind of tone toward people seeking help. It's not helping.

I did search on google before posting the questions and I think the first one is more or less an INFO but rather an ERROR. "09:52:46,875 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml"

For the second one, I know what it means and that's why I put my java version number in there. However, I do not want to try different java version to figure out which one is appropriate. This issue might not be in the jbpm core library, might be some 3rd party jars included. However, it's not mentioned in the release note and the sample application of 3.2.2 worked but not 3.2.3.

Anyway, I think jBPM as a product (not just the core library) and I am evaluating it to see whether it's a good solid product. In my opinion, jbpm 3.2.3 includes a sample application, which should run out of the box, but it doesn't. I am raising these two issues I observed here if people already know the answer, which I could not find in google.

-xigua

[kukeltje]

I did search on google before posting the questions and I think the first one is more or less an INFO but rather an ERROR. "09:52:46,875 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml"

So why not mention that....

note The full stack trace of the root cause is available in the JBossWeb/2.0.1.GA logs.

So why did you not post this? and only the 'screenshot' part

For the second one, I know what it means and that's why I put my java version number in there.

I think you partly do or you give to little info again. The error means a class which is compiled with a newer JDK tries to be run by an older JDK/JRE. So just mentioning one jdk (which one is that btw, the one running jBPM or the one used to compile your actionhandler?) is not enough.

For these kinds of reasons I (sometimes) give short, maybe that not politically correct anwsers on these kinds of questions.

jBPM itself is running on 1.4, 1.5 and 1.6 but your classes might not

HTH

[xigua]

"kukeltje" wrote:

I did search on google before posting the questions and I think the first one is more or less an INFO but rather an ERROR. "09:52:46,875 ERROR [STDERR] Jul 14, 2008 9:52:46 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/tools/jbpm-jpdl-3.2.3/server/server/jbpm/tmp/deploy/tmp14048jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml"

So why not mention that....

note The full stack trace of the root cause is available in the JBossWeb/2.0.1.GA logs.

So why did you not post this? and only the 'screenshot' part

For the second one, I know what it means and that's why I put my java version number in there.

I think you partly do or you give to little info again. The error means a class which is compiled with a newer JDK tries to be run by an older JDK/JRE. So just mentioning one jdk (which one is that btw, the one running jBPM or the one used to compile your actionhandler?) is not enough.

For these kinds of reasons I (sometimes) give short, maybe that not politically correct anwsers on these kinds of questions.

jBPM itself is running on 1.4, 1.5 and 1.6 but your classes might not

HTH

I tried to run the websale example by directly executing jbpm-jpdl-3.2.3/server/start.bat
none of my code involved.

[kukeltje]

now that is good information..... So 3.2.2 out of the box runs with jdk 1.5 of some JBoss AS server, but 3.2.3 does not. The log4j logging could show in what stage the process is in when it is signalled. 'The fork' is the fork in the websale example? Then the error only can be in org.jbpm.websale.ShipItem. Can you tell me
- what the version number in that class is?
- how you deployed this process or was it in the preconfigured database?
- what happens if you run with jdk6?

[xigua]

"kukeltje" wrote:
now that is good information..... So 3.2.2 out of the box runs with jdk 1.5 of some JBoss AS server, but 3.2.3 does not. The log4j logging could show in what stage the process is in when it is signalled. 'The fork' is the fork in the websale example? Then the error only can be in org.jbpm.websale.ShipItem. Can you tell me
- what the version number in that class is?
- how you deployed this process or was it in the preconfigured database?
- what happens if you run with jdk6?

At the very beginning of my question, I said "When I started the websale sample server", maybe that's not clear enough to you.
1. I have no idea in which jar I can find the class. The attached source code has the following private static final long serialVersionUID = 1L; but the class file in the jar may not be the same.
2. I didn't deploy. As I said, I just run the command without any modification, which means it running with the embedded hsqldb
3. It works fine on jdk1.6.0_07 but not 1.5.0_12

[kukeltje]

websale sample server for me was the same as websale sample process... ;-). The sample server is the jBPM suite therefor I was set of on the wrong foot

2: ok... clear
1: that is not to be found if you did not do 2
3: hmm... In the worst case, the official release has been build with jdk6 which I do not hope it was. I'll check. btw, is it the

[kukeltje]

btw, what happens if you just start a process and do nothing? within 20 seconds there a reminder should be send which might cause the same error. If not, the problem gets even stranger.

[johnhurtchan]

I have the exact same problem as this person. I'm running the jbpm suite 3.2.3 out of the box. On the websale app. Same error. Just prior to the 1st fork. Get that version error in 2 cases. (1) when the websale app Exits the "Evaluate Web Order" Task just prior to a fork. Get that error on webpage (2) Also when the reminder timer kicks off, get same message but in the console log.

I'm running j2se 1.5.0_16. I didnt compile anything, running default suite server and default websale app. Help!

[robro99]

I had this exact same problem when I tried to get things working with JDK5, JBoss 4.2.3, and jBPM 3.3.1. I could not run the Websale example that comes pre-installed.

I cleaned all this off the box. I installed JDK6. I installed the JBoss 4.2.3 that comes prepped for JDK6. I then installed jBPM 3.3.1 again. Now the Websale example works.

[kukeltje]

did you realy not deploy the websale example from eclipse? In that case the installer might be compiled with the wrong jdk.

[robro99]

I cannot seem to get deploy from eclipse working with the basic install, so no I did not deploy anything. I was just using what comes when you run the basic install.

for reference this is what I used to setup my env.

jdk-6u12-windows-i586-p.exe
jboss-4.2.3.GA-jdk6.zip
jbpm-installer-3.3.1.GA.jar
eclipse-jee-ganymede-SR2-win32.zip

Aside from the fact that I cannot deploy from eclipse, this seems to work for me.

Previously I had tried to set things up with

jdk-1_5_0_17-windows-i586-p.exe
jboss-4.2.3.GA.zip
jbpm-installer-3.3.1.GA.jar
eclipse-jee-ganymede-SR2-win32.zip

This setup had the same symptoms as described the original poster when I tried to run the websale demo that comes pre-installed.