PM02899: EGL0505E Cannot connect to jdbc/db when debugging EGL Web transa ction using JNDI

APAR status

• Closed as program error.

Error description

• Environment:
  
   - Product name (Build ID or version/patch level): IBM Rational
  Business Developer v7.5.1.4
  Reproducible Y/N: Y
  
  Description of problem:
  
  When trying to debug a j2ee-enabled Web transaction with only a
  jndi name specified the following error is raised at the first d
  atabase operation:
  
  EGL0150E An error occurred calling the printdata program.
  Error: EGL0505E Cannot connect to jdbc/db:
  
  A JNDI operation on a 'java:' name cannot be completed because t
  he server runtime
  is not able to associate the operation's thread with any J2EE ap
  plication component.
  This condition can occur when the JNDI client using the 'java:'
  name is not executed on
  the thread of a server application request. Make sure that a J2E
  E application does not
  execute JNDI operations on 'java:' names within static code bloc
  ks or in threads
  created by that J2EE application. Such code does not necessarily
   run on the
  thread of a server application request and therefore is not supp
  orted by
  JNDI operations on 'java:' names.
  

Local fix

Problem summary

• JNDI lookups in the debugger for web transactions were being
  done in the wrong thread, resulting in the error.
  

Problem conclusion

• JNDI lookups are now done in the appropriate thread.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL BUS DEV

• Fixed component ID

  5724S5000

Applicable component levels

• R751 PSN

     UP