Joram, when there are persisted running process instances shouldn't the process
definitions used by the running instances be in the repository already even
after a Tomcat restart?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4264540#4264540
Reply to the post
I'm going to try this. Also see my e-mail, please.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4264507#4264507
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4264507
___
The error usually meant that there was something wrong with the process xml -
but I've never seen it being thrown at runtime.
Regarding java activities, there are no limitations for the constructor (as
long it is the default constructor).
It sure sounds like a strange problem. i'm curious to
This is the only error I see:
| INFO: exception while executing command
org.jbpm.pvm.internal.cmd.startprocessinstanceinlatest...@5ad89e02
| java.lang.ClassCastException:
org.jbpm.jpdl.internal.model.JpdlProcessDefinition cannot be cast to
java.util.List
| at
So if I see it correctly, the error happens when starting a new process
instance, the process definition isn't found in the repositorycache, which
actually triggers the deployment again.
So far this is acceptable. Could you post your process?
View the original post :
I think this is hardly possible since it is splattered all over with
implementation details. I'll have to check back after consultation. Maybe
instead of posting I could supply it to you by e-mail.
I already raised log levels. Is there no way to see more?
View the original post :
Normally, the real cause should be shown somewhere down in the stacktrace (but
as you stated, this is missing)?
Have you tried the process against the 4.3 trunk?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263953#4263953
Reply to the post :
Hello Joram,
I will try to provide the stacktrace tomorrow.
The situation is the following. I've got a process definition with a couple of
automated activities, a bunch of java classes mainly used to invoke Axis2
webservices and 2 tasks for users. The process definition is deployed with no
Forgot to mention that if I use a different process definition to be started
like this it works fine. So it must be something with the definition or the
implementation classes??
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263849#4263849
Reply to the post :
It seems this Exception is haunting me. I am able to deploy my process
definition and there is no exception thrown when viewing the list of process
definitions but as soon as I want to start an instance of the process. I tried
to follow bwestrich's advice and searched for the actual cause but I
Starting a new instance of this process succeeds but throws an exception. Could
there be anything wrong with the process definition which is not detected
during deployment but just during run time?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263473#4263473
@Sebastian: can you provide the stacktrace when starting a new instance?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263551#4263551
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4263551
I'll double check this to see if I can trust me. I was facing too many
different problems on the same time today. So it's difficult to distinguish and
to reproduce theme. If I'll face the same problem I'll provide the stacktrace.
Seems that this happened to me when I was testing for the right
I managed to get rid of the problem. There was a classpath / buildpath problem
and a wrong spelled package name when referencing a class in the process
definition. I'm glad about the change to a more meaningful error message
because I basically had 2 different problems but this wasn't clear to
awesome! Thanks for the heads up on this upcoming improvement.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263188#4263188
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4263188
I am facing a similiar problem but I can't identify the cause. I am trying to
deploy a process definition and the exception is thrown. The prior exception
identified is
| deploy.seminar:
| [jbpm-deploy] java.util.zip.ZipException: error in opening zip file
| [jbpm-deploy] at
could be that the zip is being copied there and opened before it is finished
copying
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263224#4263224
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4263224
https://jira.jboss.org/jira/browse/JBPM-2281
It's basically the same problem as stated in the new comment here.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263229#4263229
Reply to the post :
I have created a unit test and I am facing the same problem when trying to
deploy so it's not the ant task's fault.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263251#4263251
Reply to the post :
@bwestrich: indeed, that's a good analysis :-)
We've changed the error message in 4.2 into something more meaningful, because
we also had trouble interpreting it ;-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262922#4262922
Reply to the post :
How does the process definition look like? For me this is somehow not enough
information to help you. I encountered this problem already when browsing
process definitions with the console and I had java classes referenced in the
process definition which were missing in the classpath.
View the
Usually when I've gotten this error I can resolve it by deleting all the
process definitions that are in my database, then redeploying the process
definition. Possibly I had an old process definition in my database that
refers to a Java class that no longer exists?
Not that this fix is
Actually, I ran into one of these errors just now
(java.lang.ClassCastException:
org.jbpm.jpdl.internal.model.JpdlProcessDefinition cannot be cast to j
ava.util.List) and clearing the database didn't solve it.
Digging a little deeper, it looks like (at least when a model is deployed in a
23 matches
Mail list logo
