setting up jbpm in jboss manually - db and setup-sql issue?
hannes Jul 28, 2005 12:22 PMHi there,
I am quite unexperienced in j2ee/jboss & jbpm, so I have to handle a couple of problems.
I am trying to setup jbpm in a fresh jboss (4.0.2):
1. jbpm.sar (copied from the jbpm-starters-kit-3.0)
2. start jboss
then a couple of errors:
17:07:29,146 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
....
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=Hypersonic,database=localDB
State: NOTYETINSTALLED
Depends On Me:
jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
....
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=Hypersonic,database=localDB
State: NOTYETINSTALLED
Depends On Me:
jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
using the tcp-mbean in the hsqldb.xml (case I)
<mbean code="org.jboss.jdbc.HypersonicDatabase" name="jboss:service=Hypersonic"> <attribute name="Port">1701</attribute> <attribute name="Silent">true</attribute> <attribute name="Database">default</attribute> <attribute name="Trace">false</attribute> <attribute name="No_system_exit">true</attribute> </mbean>
weird thing - if I use the other mbean in the hsqldb.xml (case II)
<mbean code="org.jboss.jdbc.HypersonicDatabase" name="jboss:service=Hypersonic,database=localDB"> <attribute name="Database">localDB</attribute> <attribute name="InProcessMode">true</attribute> </mbean>
The startup is quite different (a lot of [HbmBinder] output), but without errors.
Ok, going on with case II
2. deploying websale-project (copied jbpm.war from the starters-kit and renaming it in websale.war)
hmm, everything works fine - except that I cannot log in, because there are no user in the db. Thats typically - I wanted actually report an error ;)
Back to case I
2. deploying websale:
17:41:21,836 ERROR [[/websale]] StandardWrapper.Throwable
java.lang.ExceptionInInitializerError
at org.jbpm.scheduler.impl.Scheduler.start(Scheduler.java:20)
at org.jbpm.scheduler.impl.SchedulerServlet.init(SchedulerServlet.java:66)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
....
java.lang.ExceptionInInitializerError
at org.jbpm.scheduler.impl.Scheduler.start(Scheduler.java:20)
at org.jbpm.scheduler.impl.SchedulerServlet.init(SchedulerServlet.java:66)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
....
and
17:41:21,876 ERROR [[/websale]] Servlet /websale threw load() exception
java.lang.ExceptionInInitializerError
at org.jbpm.scheduler.impl.Scheduler.start(Scheduler.java:20)
at org.jbpm.scheduler.impl.SchedulerServlet.init(SchedulerServlet.java:66)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
....
java.lang.ExceptionInInitializerError
at org.jbpm.scheduler.impl.Scheduler.start(Scheduler.java:20)
at org.jbpm.scheduler.impl.SchedulerServlet.init(SchedulerServlet.java:66)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
....
then trying out localhost:8080/websale/index.jsp
Hm, strange. It seems to be fine. You know the thing, that you want to show an error and then you dont find it? :)
Ok, still some questions. What does these errors in caseI mean? This mbean is standalone-version of the db for extern process access, isn' it? I think I wont need it.
What tables does the jbpm-service exactly need? in the "\jbpm-starters-kit-3.0\jbpm-server\server\jbpm\data\hypersonic\default.script" there are a lot of sql-statements. I tried to commit all of them with an ant-skript (org.hsqldb.util.ScriptTool) and there are new values/tables in the db, but I want no patchwork solution. And the radiolist in the login-screen is still empty..
-> How do I package the setup-statements that are neccessary for the jbpm-service that they are executed one time at the deployment?
and
-> How do I package the setup-statements that are neccessary for the websale (in general for an app) that they are executed one time at the deployment?
Should I bundle the jbpm-related db-stuff in a seperate DB? How can I manage this? (I am a bit confused with the db-configuring)
Am sorry for my bad english und dizzy posting, but I would be happy if you can help me getting more familiar with this stuff :D