StartNode cannot be cast to org.jbpm.workflow.core.node.SubProcessNode

[nehajo...@gmail.com]

I m getting below error :

[Contaire:Process:9,933 - ?:7] -- org.jbpm.workflow.core.node.StartNode cannot be cast to org.jbpm.workflow.core.node.SubProcessNode

Can anyone help me with this error.

[waytoultim...@gmail.com]

Hi Neha,

Have you re-deployed the process by changing the process diagram?

Regards,

Sudhish Nair

[Neha joshi]

Hey there, 

Yes I have changed the process and also update the version of. Project from 1.0.0 snapshot to 1.0.1 snapshot. Does that will create an issue? 

--
You received this message because you are subscribed to a topic in the Google Groups "jBPM Usage" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jbpm-usage/zcNEOiPqePM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jbpm-usage+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/b5f82222-de5e-416f-8a3a-bc9d77230c98n%40googlegroups.com.

[Amit Nijhawan]

Please try to check if you have active processes and abort them. actually the Exception that you are getting may occur if you change the version of your deployment while you still have an active process instance or an active Task (check both and abort if you found one of them active). that's all I can help with.

You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/CAMS-hCysu0ggGpnzPW31wMOYgbrWk9t0ANQunhZ072%3DyynLrtA%40mail.gmail.com.

[waytoultim...@gmail.com]

Hi Neha,

Yes, If you may have running process instances started with an old process definition.  So you will have to either abort the active process instances before upgrading versions or deploy both processes as separate deployment so that both works separately.

Another option would be migrating the active process instances from one version to another. You can refer to documentation [1] to learn more about it.

[1] https://docs.jboss.org/jbpm/release/7.46.0.Final/jbpm-docs/html_single/#service-migration-con_jbpm-doc

Regards,

Sudhish

[nehajo...@gmail.com]

Hello Sudhish/Anij,

Thanks for you reply.

But  i have two separate deploymens showin in sample-server :i.e.1.0.0 snapshopt and 1.0.1 snapshot.

will it not work ? 

actually i have 9000+ process instance running in 1.0.0 snapshot on dev , do i have to abort or migrate  all of them ???? 

[waytoultim...@gmail.com]

Hi Neha,

If you have two separate deployments then ideally it should work.

When exactly are you getting the error? While working with process instances created with the new version or working with old process instances created with old versions?

Regards,

Sudhish Nair

[nehajo...@gmail.com]

Thanks Everyone for quick response.

Issue got resolved.

I was hitting wrong url to create process that was creating issue. :) 

Once again Thanks Everyonce.

[nehajo...@gmail.com]

Hello Everyone , 

Above one was of the reason of getting error..But i am also getting this error sometimes. .

Could not commit session: java.lang.ClassCastException: org.jbpm.workflow.core.node.Join cannot be cast to org.jbpm.workflow.core.node.HumanTaskNode

How do i identify what is causing the error ? 

I have two separate deployments. (FYI).