[JBoss jBPM] - Re: Problems with jbpm 3.3.1 GA and JBoss AS 5.0.0 GA
by the_fredo
1) is solved by adding a patch I found in the JIRA (a few .xhtml files)
2) the pb remains even with JBoss AS 4.2.3, so it's a pb with jbpm, not with AS.
It's impossible to deploy a process through the deployment' tab of GPD, even with jbpm 3.2.5. The and task does not work either. The only working solution is to save locally a process archive and then upload it through the web console (it works even with the gwt console)
3) I can now login (with manager/manager) in the gwt console but it crashes as long as it requires Birt : could not create connection : user JBPMTEST not found:
17:41:52,236 WARN [Parameters] Parameters: Invalid chunk ignored.
| 17:41:52,453 INFO [ReportFacade] BIRT home: /Developer/Archives/jboss-5.0.0.GA/server/jbpm/data/birt/ReportEngine
| 17:41:52,456 INFO [ReportFacade] Output dir: /Developer/Archives/jboss-5.0.0.GA/server/jbpm/data/birt/output/
| 17:41:52,456 INFO [ReportFacade] Report dir: /Developer/Archives/jboss-5.0.0.GA/server/jbpm/data/birt/
| 17:41:52,760 INFO [ReportFacade] BIRT home: /Developer/Archives/jboss-5.0.0.GA/server/jbpm/data/birt/ReportEngine
| 17:41:52,765 INFO [ReportFacade] Output dir: /Developer/Archives/jboss-5.0.0.GA/server/jbpm/data/birt/output/
| 17:41:52,765 INFO [ReportFacade] Report dir: /Developer/Archives/jboss-5.0.0.GA/server/jbpm/data/birt/
| 17:41:57,067 INFO [BirtService] Service created: org.eclipse.birt.report.engine.api.impl.ReportEngine@f8a1a13
| 17:41:57,069 INFO [BirtService] Service created: org.eclipse.birt.report.engine.api.impl.ReportEngine@5573d88b
| 17:42:04,539 WARN [JBossManagedConnectionPool] Destroying connection that could not be successfully matched: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@5d8a64f3[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@f4681fb handles=0 lastUse=1232469714936 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@5dff8d92 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@34a79c74 xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@5ae8300f txSync=null]
| 17:42:04,544 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
| org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: User not found: JBPMTEST)
| at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)
| at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:611)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:257)
| at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:607)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
| at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:104)
| at org.eclipse.birt.report.data.oda.jdbc.JndiDataSource.getDataSourceConnection(JndiDataSource.java:159)
| at org.eclipse.birt.report.data.oda.jdbc.JndiDataSource.getConnection(JndiDataSource.java:133)
| at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getJndiDSConnection(JDBCDriverManager.java:227)
| at
| ...
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:637)
| Caused by: java.sql.SQLException: User not found: JBPMTEST
| at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
| at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
| at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
| at org.hsqldb.jdbcDriver.connect(Unknown Source)
| at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:207)
| ... 92 more
Fred
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203354#4203354
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203354
17 years, 2 months
[JBoss jBPM] - Re: EJB Timer Lookup problem in BPEL
by dhanushgopinath
Ok. I did some more research, added in web.xml of my application this snippet <ejb-local-ref>
| <ejb-ref-name>ejb/LocalTimerEntityBean</ejb-ref-name>
| <ejb-ref-type>Entity</ejb-ref-type>
| <local-home>org.jbpm.ejb.LocalTimerEntityHome</local-home>
| <local>org.jbpm.ejb.LocalTimerEntity</local>
| <ejb-link>TimerEntityBean</ejb-link>
| </ejb-local-ref>
and then added in the jboss-web.xml <ejb-local-ref>
| <ejb-ref-name>ejb/LocalTimerEntityBean</ejb-ref-name>
| <local-jndi-name>java:ejb/TimerEntityBean</local-jndi-name>
| </ejb-local-ref>
Then I ran my application and when the process ends ejb timer lookup problem is now gone. But its throwing a class cast exception.
Caused by: java.lang.ClassCastException: $Proxy63
| at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.getTimerEntityHome(EntitySchedulerServiceFactory.java:41)
| at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.openService(EntitySchedulerServiceFactory.java:50)
| at org.jbpm.svc.Services.getService(Services.java:150)
| at org.jbpm.svc.Services.getCurrentService(Services.java:94)
| at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
The same $Proxy63 class is getting created after looking up in the case of Process Ending while running the process with a SOAP-UI. But no exception is thrown in that case.
Please let me know if you have any info on this.
Thanks
Dhanush
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203326#4203326
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203326
17 years, 2 months