Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

2 phase commit

 
sateesh lg
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am getting the below error in a 2 phase commit transaction. I am using Websphere MQ 5.3 and DB2 Connect 7.2. Can someone please help? Are there any specific settings required for 2 phase commit. My datasource is JTA enabled, EJB is container managed and the transaction type is required
ERORR:
--------
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2] SQL30090N Operation invalid for application execution environment. Reason code = "1". SQLSTATE=25000
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What version of WebSphere Application Server are you running?
Kyle
 
sateesh lg
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Kyle,
Thanks for the response. I am using Websphere Application Studio Developer 4.0.3, DB2 connect 7.2. The database resides on OS/390. Is there any specific setting that needs to be done for Db2 connect to support 2 phase commit? I am using a DB2XADatasource class to get the connection and it is JTS enabled. Is there any need of transaction processing monitor to be installed either on the workstation or the database (OS/390 - DB2)
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by sateesh lg:
Hi Kyle,
Thanks for the response. I am using Websphere Application Studio Developer 4.0.3, DB2 connect 7.2. The database resides on OS/390. Is there any specific setting that needs to be done for Db2 connect to support 2 phase commit? I am using a DB2XADatasource class to get the connection and it is JTS enabled. Is there any need of transaction processing monitor to be installed either on the workstation or the database (OS/390 - DB2)

This sounds like something on the DB2 (OS/390) side is not configured correctly. Take the following URL to you DBA and ask them to look at this.
WebSphere IS a TP Monitor. It sounds like DB2 on the mainframe is at fault in this case.
Kyle
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic