Robbie Knight

I resolved it already, but thanks...

It wasn't quite the same error you were getting, but the 2 stack traces have the following line in common:

J2CA0030E: Method enlist caught javax.transaction.SystemException

We had migrated from a WAS 7.0.0.19 installation on a Linux box to a AIX (UNIX) machine. When our EJBs attempted to connect to Oracle 10g using the data source setup, we would get a stack trace as follows:

[1/9/12 11:22:03:427 SAST] 00000037 XATransaction E J2CA0030E: Method enlist caught javax.transaction.SystemException at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredResources.java:1089) at com.ibm.ws.tx.jta.TransactionImpl.enlistResource(TransactionImpl.java:2168) at com.ibm.ws.tx.jta.TranManagerSet.enlist(TranManagerSet.java:526) at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:715) at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(ConnectionManager.java:2206) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.lazyEnlist(WSRdbManagedConnectionImpl.java:2569) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java:714) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java:2745) at org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:166) ... at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604) Caused by: com.ibm.ws.recoverylog.spi.InternalLogException at com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverableUnit(MultiScopeRecoveryLog.java:1266) at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit(RecoveryLogImpl.java:168) at com.ibm.tx.jta.PartnerLogData.logData(PartnerLogData.java:220) at com.ibm.tx.jta.PartnerLogData.logRecoveryEntry(PartnerLogData.java:168) at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredResources.java:1078) ... 61 more while trying to enlist resources from DataSource jdbc/oracleDb with the Transaction Manager for the current transaction, and threw a ResourceException. 00000037 PartnerLogDat E WTRN0000E: An internal error occurred in method logData in class com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.spi.InternalLogException at com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverableUnit(MultiScopeRecoveryLog.java:1266) at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit(RecoveryLogImpl.java:168) at com.ibm.tx.jta.PartnerLogData.logData(PartnerLogData.java:220) at com.ibm.tx.jta.PartnerLogData.logRecoveryEntry(PartnerLogData.java:168) at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredResources.java:1078) at com.ibm.ws.tx.jta.TransactionImpl.enlistResource(TransactionImpl.java:2168) at com.ibm.ws.tx.jta.TranManagerSet.enlist(TranManagerSet.java:526) at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:715) at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(ConnectionManager.java:2206) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.lazyEnlist(WSRdbManagedConnectionImpl.java:2569) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java:714) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java:2745) at org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:166) ... at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

It turns out the Oracle driver (we were using ojdbc14.jar i.e. version 1.4 of the jar) wasn't compatible with the AIX/WAS7 installation. Once we upgraded the driver (to version 6 - ojdbc6_g.jar), the problem went away.

More symptoms were:

Doing a 'test' connection from the admin console does not throw an error

If the JDBC provider is set to Non XA, then the problem goes away

I hope this helps someone else

Hi svm muni,
Did you find a solution to the above? I'm getting a similar problem.

Incase, the title didn't give it away, here is my scenario:

I have a main html window that pops up a dialog box using the showModelessDialog method. This method is only available in IEs javascript implementation. That's OK because the business all use IE.

the popped up dialog box contains an applet. Method calls happen as follows. user clicks on button -> javscript method is invoked -> javascript method calls applet method -> applet method churns (processes) -> applet method calls javascript method (to update certain fields) -> applet method exits -> user is happy.

However, the last applet call into the javascript fails in IE. is this a bug? When I use window.open instead of window.showModelessDialog, then the bug is not apparent.

Any Ideas?

Here is a test setup that will reproduce the problem:

main window:
<html> <head> <script language="javascript"> function callAppletModeless() { window.showModelessDialog('popup.htm',window,'dialogHeight:500px;dialogWidth:500px;status:no; scroll:auto;center:yes;resizable:yes;help:no;minimize:yes;maximize:yes;'); } function callAppletPlain() { window.open('popup.htm','','height=500px,width=500px,fullscreen=0,location=0, menubar=0,resizable=1,scrollbars=1,status=0,toolbar=0'); } </script> </head> <body> <h1>This is the main window</h1> The dialog is called here. <p> you can call the dialog using showModelessDialog() here: <input type='button' value='call as a modeless' onKlick="callAppletModeless();" /> <p> or you can call the dialog as a plain window: <input type='button' value='call plain' onKlick="callAppletPlain();" /> </body> </html>

popup window

<html> <head> <script language="javascript"> function enterJavaScript() { alert('Hello applet friend'); } function reEntryTestStart() { myApplet.reEntryTest(); } function reEntryTestFinish() { alert('I am back in the JavaScript'); } function enterApplet() { myApplet.sayHello(); } </script> </head> <body> <h2>This is the popup</h2> <P> Three methods to test. <br> A.) A call from the javascript to the applet. <input type='button' value='javascript -> applet' onKlick="enterApplet();" /> <p> B.) A call from the applet to the javascript. <br> <applet id="myApplet" name="myApplet" code="MyApplet.class" height="100" width="500" MAYSCRIPT > <param name="debugMode" value="true" /> <PARAM NAME="MAYSCRIPT" VALUE="true"> </applet> <p> C.) A call from the script, into the applet, and then back again to the javascript. If you're using IE and you chose the showModeless, then your browser might crash. <br> <input type='button' value='javascript -> applet -> javascript' onKlick="reEntryTestStart();" /> <p> Why does this not work? </body> </html>

Applet. (you will need to have netscape's plugin.jar in your classpath in order to run - this should be available in your java jre's lib folder)

import java.awt.*; import java.awt.event.*; import java.applet.*; import netscape.javascript.*; public class MyApplet extends Applet implements ActionListener { private Button button; private TextField text; public void init() { button = new Button("applet -> javascript"); button.addActionListener(this); text = new TextField(30); setLayout(new FlowLayout()); add(button); add(text); } public void start() { } public void stop() { } public void destroy() { } public void actionPerformed(ActionEvent event){ calle_v_a_l("enterJavaScript();"); } public void sayHello() { text.setText("Hello my javascript friend"); } public void reEntryTest() { text.setText("In Applet, attempting to go back to javascript..."); calle_v_a_l("reEntryTestFinish();"); } private void calle_v_a_l(String e_v_a_lString) { try { JSObject win = netscape.javascript.JSObject.getWindow(this); win.e_v_a_l(e_v_a_lString); } catch (Throwable t) { System.out.println("Error calling javascript method!"); t.printStackTrace(); } } }
[ UD: added linebreaks to preserve layout ]
[ September 28, 2007: Message edited by: Ulf Dittmer ]