[JBoss jBPM] - JBPM Oracle connection Issue
by Kodee
Hi,
We are new to Jbpm and we are trying to change default hsqldb to oracledb.
When we try to connect with Oracle database with jbpm, while deploying my processdefinition.xml, it displays the following error.
Please do the needful
Warm Regards,
Kodee
Error Message in Console
10:45:10,118 DEBUG [LogFilter] request http://localhost:8080/jbpm/upload
10:45:10,118 DEBUG [JbpmContextInfo] creating jbpm context with service factories '[message, schedul
er, authentication, persistence, logging]'
10:45:10,118 DEBUG [JbpmContext] creating JbpmContext
10:45:10,165 DEBUG [NodeTypes] node 'page' will not be available. class 'org.jboss.seam.pageflow.Pag
e' couldn't be loaded
10:45:10,165 DEBUG [NodeTypes] node 'start-page' will not be available. class 'org.jboss.seam.pagefl
ow.Page' couldn't be loaded
10:45:10,165 DEBUG [FileDefinition] preparing file 'processimage.jpg' for storage in the database
10:45:10,165 DEBUG [FileDefinition] preparing file 'forms.xml' for storage in the database
10:45:10,165 DEBUG [FileDefinition] preparing file 'processdefinition.xml' for storage in the databa
se
10:45:10,165 DEBUG [FileDefinition] preparing file 'gpd.xml' for storage in the database
10:45:10,165 DEBUG [FileDefinition] preparing file 'Deal Entry.xhtml' for storage in the database
10:45:10,165 DEBUG [UploadServlet] Created a processdefinition : SampleJBPM
10:45:10,165 DEBUG [DbPersistenceServiceFactory] creating persistence service
10:45:10,165 DEBUG [DbPersistenceService] creating hibernate session
10:45:10,165 DEBUG [DbPersistenceService] beginning hibernate transaction
10:45:10,165 WARN [JDBCExceptionReporter] SQL Error: 923, SQLState: 42000
10:45:10,165 ERROR [JDBCExceptionReporter] ORA-00923: FROM keyword not found where expected
10:45:10,368 INFO [STDOUT] org.hibernate.exception.SQLGrammarException: could not execute query
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.loader.Loader.doList(Loader.java:2150)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2026)
at org.hibernate.loader.Loader.list(Loader.java:2021)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:298)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1020)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74)
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:650)
at org.jbpm.db.GraphSession.findLatestProcessDefinition(GraphSession.java:153)
at org.jbpm.db.GraphSession.deployProcessDefinition(GraphSession.java:67)
at org.jbpm.JbpmContext.deployProcessDefinition(JbpmContext.java:173)
at org.jbpm.webapp.servlet.UploadServlet.doDeployment(UploadServlet.java:94)
at org.jbpm.webapp.servlet.UploadServlet.handleRequest(UploadServlet.java:81)
at org.jbpm.webapp.servlet.UploadServlet.service(UploadServlet.java:50)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188976#4188976
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188976
17 years, 4 months
[JBoss jBPM] - Re: jBPM 4 Design Question: Stateful Process Instance
by benhu
"kukeltje" wrote : how do you mean stateless? Is that the same as no persistence to you? 95% of current jBPM usage is with persistance, Can you point me to the wiki page and tell me what you think this statefull means?
The wiki page is here:
http://www.jboss.org/community/docs/DOC-12855
My understanding for current jBPM is, the state of a process instance (during the execution, where the token points) is persistent in the database. Thus suppose I have a service to call jBPM to execute a process, I can make this service stateless because this service does not need to carry the state of current process (the state is in the persistence). This service does not need to wait for jBPM and keep its state. It simply call jBPM, signal the token and return. Next time when the service access this process instance again, it will know the state from the persistence. Otherwise, I have to make my service stateful which from my perspective may affect scalability of my system.
I am not sure if this is what jBPM team means by stateless process instance or statefull process instance.
I am just concerned whether or not I can still keep my service stateless.
BTW, in existing code base, jbpm enterprise has a stateless EJB implemenation. That is why I think I can have a stateless service in my system to interact with jBPM.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188955#4188955
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188955
17 years, 4 months