Johan I have only one DataSource. The Problem might be that the Second session bean is trying to create another instance of the same DataSource which is used by the first Session Bean.
What reason(s) can be attributed to this? regards Salil Malhotra -----Original Message----- From: Johan Eltes [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2003 1:40 AM To: [EMAIL PROTECTED] Subject: Re: Illegal use of 1PC resource in transaction I have a distant memory of having seen the message when one tries to include/enlist a second managed transactional resource (like a jdbc connection) within the same jta transaction as a none-xa managed resource is already enlisted (used for DML operations). WebSphere performs local (1PC) connection optimization as long as there is only one managed transactional (none-xa) resource used in the scope of the jta transaction, but throws an exception as soon as the second managed transactional resource shows up (DML operation issued). /Johan Den 2003-03-31 17.57, skrev "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > I am getting the following problem while using only Session Beans Connecting > to an Oracle Database using Oracle thin Driver > I am using WSAD 4.0.3. I have not used in Entity beans and directly updating a > row through a DAO. > > "Illegal use of 1PC resource in transaction". > > Is it a problem of some patch for the same ? > > regards > Salil Malhotra > > > > > > > > DISCLAIMER: > This message contains privileged and confidential information and is intended > only for the individual named.If you are not the intended recipient you should > not disseminate,distribute,store,print, copy or deliver this message.Please > notify the sender immediately by e-mail if you have received this e-mail by > mistake and delete this e-mail from your system.E-mail transmission cannot be > guaranteed to be secure or error-free as information could be > intercepted,corrupted,lost,destroyed,arrive late or incomplete or contain > viruses.The sender therefore does not accept liability for any errors or > omissions in the contents of this message which arise as a result of e-mail > transmission. If verification is required please request a hard-copy version. > > ==========================================================================To > unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". DISCLAIMER: This message contains privileged and confidential information and is intended only for the individual named.If you are not the intended recipient you should not disseminate,distribute,store,print, copy or deliver this message.Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted,corrupted,lost,destroyed,arrive late or incomplete or contain viruses.The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
