Title: "You are not getting the semantics you expect" warning
ditto.  i get the same thing.  i remember david jencks saying it was due to not having an xa compliant driver.  i'm using oracle 8i, which i thought was an xa database, but i have the "free" version, so maybe you have to pay money for the xa version???
 

"You are using a local transaction adapter, probably a non xa database, in a

transaction with more than one resource adapter (jms message + database

work most likely). This does not give you ACID transactions. If something

crashes in the middle of commit you will have unrecoverable state. To

avoid this use xa resource adapters only (probably an xa driver to your

db).

david jencks"

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Burns, Jamie
Sent: Thursday, July 11, 2002 5:07 AM
To: '[EMAIL PROTECTED]'
Subject: [JBoss-user] "You are not getting the semantics you expect" warning

I am getting this warning in my log file . The full log entry is

2002-07-11 09:33:52,748 WARN  [org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener] prepare called on a local tx. You are not getting the semantics you expect!

I think it is occurring in ejbStore() of a BMP entity bean.

Does anybody know what it means and/or what steps l should take to fix it?

Thanks

********************************************************************************
  This electronic mail system is used for information purposes and is
  not intended to form any legal contract or binding agreement.
  The content is confidential and may be legally privileged. Access
  by anyone other than the addressee(s) is unauthorised and any
  disclosure, copying, distribution or any other action taken in
  reliance on it is prohibited and maybe unlawful

  All incoming and outgoing e-mail communications and attachments
  are scanned automatically by software designed to detect and remove
  any material containing viruses or other unauthorised content.  While
  we undertake best endeavours to ensure that this content checking
  software is up to date, recipients should take steps to assure themselves
  that e-mails received are secure.
********************************************************************************

Reply via email to