jBPM Message Service not starting up

[sachin_garg]

I'm unable to start the jbpm message service. This is what the jpbm.cfg.xml looks like:

<jbpm-configuration>

<jbpm-context>





</jbpm-context>

<!-- configuration resource files pointing to default configuration files in jbpm-{version}.jar -->

<!-- -->












</jbpm-configuration>

I'm getting the following exception when signal is called for an async node:

org.jbpm.svc.JbpmServiceException: service 'message' unavailable

Is there anything else I'm missing that needs to be done to start the message service?

[sachin_garg]

Just realized it probably has to do with the single quote instead of double. Let me try that and get back to the group.

[sachin_garg]

Double quotes didn't help, still very much the same error. Do let me know what I'm missing. The configuration file is not appearing correctly in the previous post. I'm just trying to use the default factory:

org.jbpm.msg.db.DbMessageServiceFactory

Is there anything else I need to do?

[mshotton]

I have the same problem; I receive the error:

org.jbpm.svc.JbpmServiceException: service 'message' unavailable
at org.jbpm.svc.Services.getCurrentService(Services.java:86)

when I try to execute a process instance with a node that is marked as async=true

Is there a known solution for this?

[sachin_garg]

I think the solution lies in starting up the messaging services separately by creating a new instance using the factory. Unlike other services, there doesn't seem to be a default implementation of the messaging "server" if you may. I don't think I'll get a chance to try this in the next few days. If someone does, please share the results.

[egeek]

Realize that this is an old thread, but never-the-less, this was one of the few places I came across that referenced "service message unavailable". I had the same issue unit testing my processes with a HSQL db and the DbMessageServiceFactory.

Turns out you have to create a JbpmContext to get the message broker to work, i.e. add this

JbpmConfiguration.getInstance().createJbpmContext();

before the message broker is invoked.

If you want persistence to work then its probably a good idea to add:

JbpmConfiguration.getInstance().createSchema();

prior to this as well. This will tell hibernate to create the DB schemas and enable persistence.