Bug 777981 (SOA-510) - FATAL [DatasourceConnectionProvider] Could not find datasource: java:/JbpmDS - seen on server startup - intermittent - timing issue?
Summary: FATAL [DatasourceConnectionProvider] Could not find datasource: java:/JbpmDS ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-510
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Standalone Server
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP02
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
: SOA-505 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-09 16:08 UTC by Len DiMaggio
Modified: 2008-06-10 09:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
/opt/CP01/soa-4.2.0.GA_CP01.CR3.zip /opt/CP01/standalone-soa-4.2.0.GA_CP01.CR3.zip
Last Closed: 2008-06-10 09:03:59 UTC
Type: Bug

Attachments (Terms of Use)
NameNotFoundException.txt (59.70 KB, text/plain)
2008-04-09 16:13 UTC, Len DiMaggio 		no flags Details
server.log.gz (399.10 KB, application/x-gzip)
2008-04-09 19:16 UTC, Len DiMaggio 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-510 0 None None None Never

Description Len DiMaggio 2008-04-09 16:08:36 UTC 
Date of First Response: 2008-04-14 06:50:56
project_key: SOA

This is an intermittent problem - probably a timing issue - I've seen this one in 10 tries today - with CP01_CR3 - on startup of the standalone/default server:

11:32:49,464 FATAL [DatasourceConnectionProvider] Could not find datasource: java:/JbpmDS
javax.naming.NameNotFoundException: JbpmDS not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)

Maybe the Job Exceutor thread is running before DS deployment/after undeployment?
Comment 1 Len DiMaggio 2008-04-09 16:13:19 UTC 
The server.log was overwritten - here is stdout from the standalone server startup/shutdown.
Comment 2 Len DiMaggio 2008-04-09 16:13:19 UTC 
Attachment: Added: NameNotFoundException.txt
Comment 4 Len DiMaggio 2008-04-09 16:23:44 UTC 
The system was:

 cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : Intel(R) Pentium(R) M processor 1.70GHz
stepping        : 6
cpu MHz         : 600.000
cache size      : 2048 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2
bogomips        : 1199.41
Comment 5 Len DiMaggio 2008-04-09 16:24:59 UTC 
Note: soa-510 and soa-511 did not happen at the same time. This was all on the same system - but on different startup sessions.
Comment 6 Len DiMaggio 2008-04-09 19:16:22 UTC 
This error:

2008-04-09 14:56:10,954 INFO  [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{}
2008-04-09 14:56:10,956 FATAL [org.hibernate.connection.DatasourceConnectionProvider] Could not find datasource: java:/JbpmDS
javax.naming.NameNotFoundException: JbpmDS not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:543)

Is not a regression in CP01 - it's also in the GA bits - see attached server log
Comment 7 Len DiMaggio 2008-04-09 19:16:22 UTC 
Attachment: Added: server.log.gz
Comment 8 Kevin Conner 2008-04-14 10:50:56 UTC 
This is a missing dependency from one of the MBean definitions
Comment 9 Kevin Conner 2008-04-14 10:50:56 UTC 
Link: Added: This issue depends JBESB-1635
Comment 10 Len DiMaggio 2008-04-15 19:49:31 UTC 
Attachment: Added: server.log.gz
Comment 11 Len DiMaggio 2008-04-15 19:57:07 UTC 
Attachment: Removed: server.log.gz
Comment 12 Kevin Conner 2008-04-16 09:09:49 UTC 
This is a race caused by the missing dependency on the MBean, see linked JBESB issue.  It has existed in GA.

The workaround is to add the following to the JbpmService within jbpm-service.xml

<depends>jboss.esb:service=JBPMDatabaseInitializer</depends>
Comment 13 Marek Novotny 2008-04-22 13:32:42 UTC 
Link: Added: This issue is duplicated by SOA-505
Comment 14 Jiri Pechanec 2008-06-10 09:03:59 UTC 
Verified in CR1, config file modified
Note You need to log in before you can comment on or make changes to this bug.