Setting isolation level with JDriver for Oracle/XA
edocs (http://e-docs.bea.com/wls/docs70/oracle/trxjdbcx.html#1080746) states that,
if using jDriver for Oracle/XA you can not set the transaction isolation level
for a transaction and that 'Transactions use the transaction isolation level set
on the connection or the default transaction isolation level for the database'.
Does this mean that you shouldn't try to set it programatically (fair enough)
or that you can't set it in the weblogic deployment descriptor either? Also anybody
got any idea what the default is likely to be if you are using an Oracle 9iR2
database? Is this determined by some database setting?
IJ wrote:
edocs (http://e-docs.bea.com/wls/docs70/oracle/trxjdbcx.html#1080746) states that,
if using jDriver for Oracle/XA you can not set the transaction isolation level
for a transaction and that 'Transactions use the transaction isolation level set
on the connection or the default transaction isolation level for the database'.
Does this mean that you shouldn't try to set it programatically (fair enough)
or that you can't set it in the weblogic deployment descriptor either? Also anybody
got any idea what the default is likely to be if you are using an Oracle 9iR2
database? Is this determined by some database setting?The system should honor the setting defined in the deployment descriptor,
however, for oracle it may not be helpful to change it. Oracle provides two
isolation levels. The default is always READ_COMMITTED. The other
setting is SERIALIZABLE, but this hurts performance, and is also problematic
in the way oracle implements it. For instance, even if you set SERIALIZABLE,
oracle will not lock read data. It will allow other transactions to read and/or
alter data trhat another ongoing SERIALIZABLE transaction has read. The
only way to really lock read data in oracle is to issue oracle-specific SQL in
your select: "SELECT ..... FOR UPDATE".
All in all, you should collect a strong case for why you can't proceed with
READ_COMMITTED first. Then you should research oracle's recommendations
(and their problem record) with SERIALIZABLE.
Joe Weinstein at BEA
Similar Messages
-
C How to Set Isolation Level in the Connection String
How to Set Isolation Level in the Connection String using the "Microsoft OLE DB Provider for DB2 Version 4.0"?
We are trying to move from Crystal Reporting that run against a IBM DB2 database on a mainfram to SSRS reporting and we have downloaded the "Microsoft OLE DB Provider for DB2 Version 4.0" and then worked with the DB2 Administrator to create the
Packages. We only have access to use the "Read Uncommitted ("MSUR001") package. We were able to connect and pull data before he removed access to the other packages, but after setting access the Connection keeps trying to use
the 'Cursor Stability (MSCS001)" package. How do we change the Default to the "Read Uncommitted ("MSUR001") package??? Since it is keeps defaulting to the the other package
we can't connect to do it in the T-SQL query, it has to be set at the Connection String level.Hi Dannyboy1263,
According to your description, you want to set the Transaction Isolation Level in Connection String. Right?
In Reporting Services, the Connection String for OLE DB Connection can only contains Provider, Data Source and Initial Catalog. There's no property for setting Transaction Isolation Level in the Connection String. Based on my knowledge, we can
only set the Transaction Isolation Level at Query level or set it by using code (C#, VB, Java...) to call the property of Connection. So unfortunately your requirement can't be achieved currently.
Reference:
OLE DB Connection Type (SSRS)
Data Connections, Data Sources, and Connection Strings in Reporting Services
If you have any question, please feel free to ask.
Best Regards,
Simon Hou -
Cannot configure JDriver for Oracle
Following the instructions indicated in Setting JDriver for Oracle, I still get
the following errors :
1. Error dialog box : The procedure entry point OCILobLocatorAssign could not
be located in the dynamic link library OCI.dll.
Anyone can help to fix the problem.
Thanks.
Elton.Sashikiran Inuganti wrote:
We recently applied a client and server patches to our db and workstations to move to Oracle9i Enterprise Edition Release 9.2.0.6.0. We are using the OCI driver thru the weblogic Jdriver for oracle. when we print the meta data after the client upgrade the version of the driver is still showing as old. If we put the oracle classes12.jar in the weblogic classpath the driver version is printed correctly from the meta data. Can some oone answer why this happens.
Here is the out put with out the oracle classes12.jar in the class path:
<b>============= Database Product Name is ... Oracle
Database Product Version is Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.6.0 - Production
============= JDBC Driver Name is ........ Oracle JDBC driver
JDBC Driver Version is ..... 9.2.0.3.0
JDBC Driver Major Version is 9
JDBC Driver Minor Version is 2</b>
Driver version should show as 9.2.0.6.0 it is instead showing 9.2.0.3.0.
Thanks For your Help.We ship a version of the oracle driver, which you will find in the server\lib directory, and
unless you put a different version of the driver ahead of weblogic.jar, that's the version of
the driver WLS will use. You can definitely install a later version of the oracle driver in that
directory.
Joe -
Weblogic jDriver for Oracle 9.0.1.4
Hi,
We are using the Weblogic jDriver for Oracle oci901_8 to access the Oracle 9.0.1.
We are planning to upgrade the oracle to 9.0.1.4. Will there be any issues with
the Weblogic jDriver that is being currently used by us(oci901_8 ).
Is there Weblogic jDriver available for oracle 9.0.1.4?
Thanks in Advance,
Vidhyaa Shankar.SThe driver you have is ok to be used with oracle 9.0.1.4. Actually, you are getting
patch set for 901 database server. So, you dont need additional driver. The driver you
have is ok to work with it.
Mitesh
"Vidhyaa Shankar.S" wrote:
Hi,
We are using the Weblogic jDriver for Oracle oci901_8 to access the Oracle 9.0.1.
We are planning to upgrade the oracle to 9.0.1.4. Will there be any issues with
the Weblogic jDriver that is being currently used by us(oci901_8 ).
Is there Weblogic jDriver available for oracle 9.0.1.4?
Thanks in Advance,
Vidhyaa Shankar.S -
Configuring Weblogic's jDriver for Oracle to use in distributed transactions
Here is some errata to the instructions at "Configuring XA JDBC drivers" section of the online beta documentation:
http://www.weblogic.com/docs60/adminguide/managetx.html#1041268
The sample JDBC connection pool using Weblogic jDriver for Oracle should be:
<JDBCConnectionPool
Name="fundsXferAppPool"
Targets="myserver"
URL="jdbc:weblogic:oracle:localdb"
DriverName="weblogic.jdbc.oci.xa.XADataSource"
InitialCapacity="0"
MaxCapacity="5"
CapacityIncrement="1"
Properties="user=scott;password=tiger;server=localdb;rmid=0"
/>
<JDBCTxDataSource
Name="fundsXferDataSource"
Targets="myserver,server1"
JNDIName="myapp.fundsXfer"
PoolName="fundsXferAppPool"
/>
Here is an example of an additional XA connection pool for a second database instance:
<JDBCConnectionPool
Name="fundsXferAppPool2"
Targets="myserver"
URL="jdbc:weblogic:oracle:localdb2"
DriverName="weblogic.jdbc.oci.xa.XADataSource"
InitialCapacity="0"
MaxCapacity="5"
CapacityIncrement="1"
Properties="user=scott;password=tiger;server=localdb2;rmid=1"
/>
<JDBCTxDataSource
Name="fundsXferDataSource2"
Targets="myserver,server1"
JNDIName="myapp.fundsXfer2"
PoolName="fundsXferAppPool2"
/>
Please note the different "rmid" values for the 2 different database instances. Note also that the above sample only applies for Beta 1. Instructions may change in the future for Beta 2.
Also, all the names of the data source properties shown in "Table 8-2 Data Source Properties for WebLogic jDriver for Oracle" should start with lower case.
The Beta 1 online documentation will soon be updated to reflect the above. Our apologies for any inconvenience caused.
-- Priscilla Fung, BEA Systems, Inc.
Thanks
Mark
"Sree Bodapati" <[email protected]> wrote:
>Hi Mark,
>
>Yes you need 8.1.6 DB Server or higher for WebLogic's jDriver for Oracle/XA
>as well.
>
>/
>sree
>
>
>"Mark Cordobal" <[email protected]> wrote in message
>news:[email protected]..
>>
>> I read that XA features require version Oracle8i release 8.1.6 or later
>of
>the Oracle
>> server.
>> Does this apply only to Oracle JDBC drivers (which implement 2pc on top
>of
>JAVA_XA
>> package) or also to Weblogic's jDriver for Oracle/XA ?
>> I mean, if I have two Oracle 8.06 (or however < 8.1.6) jdbc Resource
>Manager, can
>> I implement (wlserver 6.1sp2) a distributed xa transaction using
>Weblogic's jDriver
>> for Oracle/XA ?
>> Or is it (jdriver) built also on top of JAVA_XA package, and so the db
>server XA
>> compliancy is a must ?
>>
>> Thanks in advance
>>
>> Mark
>
>
-
XA jDriver for Oracle problem : Getting native code exception
Hi,
I'm getting a native code exception which causes the Weblogic server to crash when
using XA drivers for transaction with two oracle databases. My application uses RMI
and threads.
I'm using BEA's jDriver for Oracle running under Weblogic server 6.1 sp1 talking
to Oracle 8.1.6. The OS is Solaris 2.8.
In middle of the program execution it's giving this problem. I'm using jdk131 in
solaris platform.
Any idea what's going on here ?
Thanks,
Nagoor Haja
Exception in the Log file:
===========================
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xff2414d8
Function name=madvise
Library=/usr/lib/libc.so.1
Current Java thread:
at weblogic.jdbc.oci.xa.XA.native_commit(Native Method)
at weblogic.jdbc.oci.xa.XA.commit(XA.java:136)
at weblogic.jdbc.oci.xa.XADataSource.commit(XADataSource.java:696)
at weblogic.jdbc.jta.DataSource.commit(DataSource.java:784)
at weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.java:1180)
at weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.java:419)
at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:233)
at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1397)
at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:1940)
at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:1886)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:221)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x10000 /opt/jdk131/jre/bin/../bin/sparc/native_threads/java
0xff350000 /usr/lib/libthread.so.1
0xff390000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
0xfe480000 /opt/jdk131/jre/lib/sparc/hotspot/libjvm.so
0xff2e0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff310000 /usr/lib/libw.so.1
0xff0b0000 /usr/lib/libmp.so.2
0xff080000 /opt/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000 /opt/jdk131/jre/lib/sparc/libverify.so
0xfe440000 /opt/jdk131/jre/lib/sparc/libjava.so
0xff020000 /opt/jdk131/jre/lib/sparc/libzip.so
0xfafb0000 /opt/jdk131/jre/lib/sparc/libnet.so
0xfadd0000 /usr/lib/nss_files.so.1
0xe1d00000 /opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so
0xe1400000 /opt/oracle/lib/libclntsh.so.8.0
0xfac90000 /usr/lib/libC.so.5
0xfadb0000 /opt/oracle/lib/libwtc8.so
0xfad90000 /usr/lib/libgen.so.1
0xfac70000 /usr/lib/libsched.so.1
0xfac40000 /usr/lib/libaio.so.1
0xfac20000 /opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoxa37.so
0xe8ad0000 /redis/tibco/rv6.6/lib/libtibrvj.so
0xe8ab0000 /redis/tibco/rv6.6/lib/libtibrvcmq.so
0xe89c0000 /redis/tibco/rv6.6/lib/libtibrvcm.so
0xe8990000 /redis/tibco/rv6.6/lib/libtibrvft.so
0xe8890000 /redis/tibco/rv6.6/lib/libtibrv.so
0xe8870000 /usr/lib/libpthread.so.1
0xe6fe0000 /opt/wlserver6.1/lib/solaris/libmuxer.so
0xe6fc0000 /opt/wlserver6.1/lib/solaris/libweblogicunix1.so
java Exception in the program due to the above reason:
======================================================
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.rmi.RemoteException: Message was not sent because transaction is not active.
Xid=0:a1ccd55d7f28edb9(795840),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 29 seconds
Xid=0:a1ccd55d7f28edb9(795840),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
since begin=29,seconds left=30,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
since begin=68,seconds left=1,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy1.process(Unknown Source)
at com.cme.clearing.jta.JThread.process(JThread.java:101)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.rmi.RemoteException: Message was not sent because transaction is not active.
Xid=1:a1ccd55d7f28edb9(6051803),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 29 seconds
Xid=1:a1ccd55d7f28edb9(6051803),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
since begin=29,seconds left=30,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
since begin=69,seconds left=0,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy1.process(Unknown Source)
at com.cme.clearing.jta.JThread.process(JThread.java:101)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.rmi.RemoteException: Message was not sent because transaction is not active.
Xid=2:a1ccd55d7f28edb9(4244097),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 33 seconds
Xid=2:a1ccd55d7f28edb9(4244097),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
since begin=68,seconds left=5,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy1.process(Unknown Source)
at com.cme.clearing.jta.JThread.process(JThread.java:101)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
javax.naming.CommunicationException. Root exception is java.rmi.ConnectException:
Unable to get direct or routed connection to: '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain:myserver'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:255)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
at com.cme.clearing.jta.JThread.run(JThread.java:81)
Exception null
javax.naming.CommunicationException. Root exception is java.rmi.ConnectException:
Unable to get direct or routed connection to: '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain:myserver'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:255)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
at javax.naming.InitialContext.lookup(InitialContext.java:350) Exception null
at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
at com.cme.clearing.jta.JThread.run(JThread.java:81)I see. Do you mean this code runs outside of the server? :
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
Regards,
Slava Imeshev
"Tim" <[email protected]> wrote in message
news:[email protected]...
>
Slava,
In my case, I'm not spawning any threads.
Regards,
Tim
"Slava Imeshev" <[email protected]> wrote:
That could be a trace of some threading issue. Note that EJB spec
prohibits
using threads within a container.
Regards,
Slava Imeshev
"Tim" <[email protected]> wrote in message
news:[email protected]...
Nagoor,
Did anybody respond? I'm getting the same exception with the sameenvironment configuration
but using WLS 6.1 SP2.
Tim
"Nagoor Haja" <[email protected]> wrote:
Hi,
I'm getting a native code exception which causes the Weblogic server
to
crash when
using XA drivers for transaction with two oracle databases. Myapplication
uses RMI
and threads.
I'm using BEA's jDriver for Oracle running under Weblogic server 6.1sp1
talking
to Oracle 8.1.6. The OS is Solaris 2.8.
In middle of the program execution it's giving this problem. I'm
using
jdk131 in
solaris platform.
Any idea what's going on here ?
Thanks,
Nagoor Haja
Exception in the Log file:
===========================
An unexpected exception has been detected in native code outside theVM.
Unexpected Signal : 11 occurred at PC=0xff2414d8
Function name=madvise
Library=/usr/lib/libc.so.1
Current Java thread:
at weblogic.jdbc.oci.xa.XA.native_commit(Native Method)
at weblogic.jdbc.oci.xa.XA.commit(XA.java:136)
atweblogic.jdbc.oci.xa.XADataSource.commit(XADataSource.java:696)
at weblogic.jdbc.jta.DataSource.commit(DataSource.java:784)
at
weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
ava:1180)
at
weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
ava:419)
at
weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:233
at
weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
ctionImpl.java:1397)
at
weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(Server
TransactionImpl.java:1940)
at
weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTrans
actionImpl.java:1886)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:221)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:190)
at
weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
atweblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Dynamic libraries:
0x10000 /opt/jdk131/jre/bin/../bin/sparc/native_threads/java
0xff350000 /usr/lib/libthread.so.1
0xff390000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
0xfe480000 /opt/jdk131/jre/lib/sparc/hotspot/libjvm.so
0xff2e0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff310000 /usr/lib/libw.so.1
0xff0b0000 /usr/lib/libmp.so.2
0xff080000 /opt/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000 /opt/jdk131/jre/lib/sparc/libverify.so
0xfe440000 /opt/jdk131/jre/lib/sparc/libjava.so
0xff020000 /opt/jdk131/jre/lib/sparc/libzip.so
0xfafb0000 /opt/jdk131/jre/lib/sparc/libnet.so
0xfadd0000 /usr/lib/nss_files.so.1
0xe1d00000/opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so
0xe1400000 /opt/oracle/lib/libclntsh.so.8.0
0xfac90000 /usr/lib/libC.so.5
0xfadb0000 /opt/oracle/lib/libwtc8.so
0xfad90000 /usr/lib/libgen.so.1
0xfac70000 /usr/lib/libsched.so.1
0xfac40000 /usr/lib/libaio.so.1
0xfac20000/opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoxa37.so
0xe8ad0000 /redis/tibco/rv6.6/lib/libtibrvj.so
0xe8ab0000 /redis/tibco/rv6.6/lib/libtibrvcmq.so
0xe89c0000 /redis/tibco/rv6.6/lib/libtibrvcm.so
0xe8990000 /redis/tibco/rv6.6/lib/libtibrvft.so
0xe8890000 /redis/tibco/rv6.6/lib/libtibrv.so
0xe8870000 /usr/lib/libpthread.so.1
0xe6fe0000 /opt/wlserver6.1/lib/solaris/libmuxer.so
0xe6fc0000 /opt/wlserver6.1/lib/solaris/libweblogicunix1.so
java Exception in the program due to the above reason:
======================================================
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at
weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
>>>>
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at
weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
>>>>
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at
weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
>>>>
at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
at com.cme.clearing.jta.JThread.process(JThread.java:100)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.rmi.RemoteException: Message was not sent because transaction isnot
active.
Xid=0:a1ccd55d7f28edb9(795840),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 29 seconds
Xid=0:a1ccd55d7f28edb9(795840),Status=Active,numRepliesOwedMe=1,numReplies
O
wedOthers=0,seconds
since begin=29,seconds
left=30,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myser
>
ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
>
atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
edOthers=0,seconds
since begin=68,seconds
left=1,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserv
>
er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
torURL=myserver+10.1.32.81:8001+mydomain+)
at
weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
ManagerImpl.java:1155)
at
weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
101)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
>>>>
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy1.process(Unknown Source)
at com.cme.clearing.jta.JThread.process(JThread.java:101)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.rmi.RemoteException: Message was not sent because transaction isnot
active.
Xid=1:a1ccd55d7f28edb9(6051803),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 29 seconds
Xid=1:a1ccd55d7f28edb9(6051803),Status=Active,numRepliesOwedMe=1,numReplie
s
OwedOthers=0,seconds
since begin=29,seconds
left=30,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myser
>
ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
>
atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
edOthers=0,seconds
since begin=69,seconds
left=0,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserv
>
er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
torURL=myserver+10.1.32.81:8001+mydomain+)
at
weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
ManagerImpl.java:1155)
at
weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
101)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
>>>>
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy1.process(Unknown Source)
at com.cme.clearing.jta.JThread.process(JThread.java:101)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
java.rmi.RemoteException: Message was not sent because transaction isnot
active.
Xid=2:a1ccd55d7f28edb9(4244097),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 33 seconds
Xid=2:a1ccd55d7f28edb9(4244097),Status=Active,numRepliesOwedMe=1,numReplie
s
OwedOthers=0,seconds
since begin=33,seconds
left=30,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myser
>
ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
>
atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
edOthers=0,seconds
since begin=68,seconds
left=5,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserv
>
er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
torURL=myserver+10.1.32.81:8001+mydomain+)
at
weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
ManagerImpl.java:1155)
at
weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
101)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
>>>>
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy1.process(Unknown Source)
at com.cme.clearing.jta.JThread.process(JThread.java:101)
at com.cme.clearing.jta.JThread.run(JThread.java:85)
javax.naming.CommunicationException. Root exception isjava.rmi.ConnectException:
Unable to get direct or routed connection to:
'-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain
:myserver'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:255)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at
weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
>>>>
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
at com.cme.clearing.jta.JThread.run(JThread.java:81)
Exception null
javax.naming.CommunicationException. Root exception isjava.rmi.ConnectException:
Unable to get direct or routed connection to:
'-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain
:myserver'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:255)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at
weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
>>>>
at javax.naming.InitialContext.lookup(InitialContext.java:350)Exception
null
at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
at com.cme.clearing.jta.JThread.run(JThread.java:81) -
Does Weblogic JDriver for Oracle support Oracle REFCURSOR?
"R. W. Stavros" wrote:
>
BUT BE FORWARNED ... IF YOUR CONNECTION IS FROM A CONNECTION POOL ...
YOU GET A WONDERFUL weblogic.jdbc.pool.ResultSet not a
java.sql.ResultSet .... BEA wants you to believe its a featureI'm still interested in your position that a weblogic.jdbc.pool.ResultSet
is not a java.sql.ResultSet. I get the impression you're very frustrated
and I know that can cause one to make mistakes one normally wouldn't...
Joe
>
Shiva Paranandi <[email protected]> wrote in message news:<[email protected]>...
Yes, you have to specify it as java.sql.Types.OTHER and use the
getObject() method to obtain it.
Shiva.
Chuan Li wrote:
Does Weblogic JDriver for Oracle support Oracle REFCURSOR?
Thanks.
-Chuan
PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advanced positions
for people who want to work with Java, XML, SOAP and E-Commerce infrastructure products.
We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San Jose CA.
Send resumes to [email protected] -
Set isolation level in EJB 2.0
how can i set isolation level to a transaction in EJB 2.0.
If anybody can give example code much appriciatedFor 5.1, look at:
http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#107261
7
http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_reference.html#1061916
"marshalli" <[email protected]> wrote in message
news:3a59546d$[email protected]..
>
> How to set the isolation level(Container Manager or Bean Manager) in EJB.
Thanks
>
>
-
How do I set-up on %ORACLE_HOME%\bin for Oracle client on Windows XP
How do I set-up on %ORACLE_HOME%\bin for Oracle client on Windows XP?
The Oracle bin directory is: C:\oracle\ora90\bin
Thank you!If you are asking how to setup the resolution of %ORACLE_HOME%\bin to C:\oracle\ora90\bin, you must create a system environment variable called ORACLE_HOME that is set to a value of C:\oracle\ora90.
Kind regards,
Russ -
JDK1.3 for "jDriver for Oracle"
Hi,
I'm developing for RMI/IIOP by using WLS5.1,JDK1.3 and Oracle8.
Is it possible to use JDK1.3 for "jDriver for Oracle"? And also, when it
will be added to Support Platform??I dunno about Oracle 8... ask Oracle... 1.3 is supported now.
Teru Yoshikoshi wrote:
Hi,
I'm developing for RMI/IIOP by using WLS5.1,JDK1.3 and Oracle8.
Is it possible to use JDK1.3 for "jDriver for Oracle"? And also, when it
will be added to Support Platform?? -
How to set a keyframe with setValueAtTime for only one axis?
Hi,
I´d like to set a keyframe for the layer´s scale, anchor point values but separately. Let´s say I want to add the following keyframes to a layer:
time: 0, value: 100, axis: X
time: 0.3, value: 10, axis: Y
time: 1, value: 110, axis: X
If I use setValueAtTime(time ,[x, y]) it always places a keyframe for both axis.
How can I set a keyframe with setValueAtTime for only one axis?
Regards,
ThomasDan, thanks for your fast reply. But the problem is a bit difficult to describe for a german like me
I´m try to convert given keyframes from another application. Let me visually show how it handles keyframes that are set on different axis at different times:
X: O---O---O
Y: ---O--O-O
You see when the user sets a keyframe and both axis were modified, both have a keyframe (see the last key). But if only one axis is transformed and the other not, there is only one keyframe. The problem that I try to solve is that AE is only able to set a keyframe for both axis at a given time. So if I set the 3 keyframes of the X axis first, the AE script will set keys on the Y axis simultaneously. That´s bad because it adds keyframe to the other axis where there is no value "cache". So if I would set all keyframes it would look like this:
X: O--•O-•-O
Y: •--O•-O-O
The small dots indicate those "forced" in-between keys.
So is there a "native" scripting way to separate the dimensions (like the position prop) for other props and add independent keyframes? -
How to set isolation level for BMP
Hi.
We're trying to avoid the ORA-08177 by setting the isolation level in the weblogic-ejb-jar.xml
to READ_COMMITED
Still (looking in the jdbc.log) it seems that weblogic set the transaction isolation
level to SERIALIZABLE
The xml :
<weblogic-enterprise-bean>
<ejb-name>Account</ejb-name>
<caching-descriptor>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>600</idle-timeout-seconds>
<cache-strategy>Read-Write</cache-strategy>
</caching-descriptor>
<persistence-descriptor>
<delay-updates-until-end-of-tx>true</delay-updates-until-end-of-tx>
<finders-call-ejbload>false</finders-call-ejbload>
</persistence-descriptor>
<clustering-descriptor>
<home-is-clusterable>false</home-is-clusterable>
<home-load-algorithm>round-robin</home-load-algorithm>
</clustering-descriptor>
<enable-call-by-reference>false</enable-call-by-reference>
<jndi-name>Account</jndi-name>
<transaction-isolation>
<isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
<method><ejb-name>Account</ejb-name><method-name>*</method-name></method>
</transaction-isolation>
</weblogic-enterprise-bean>
RegardsWhen I marked all the beans with READ_COMMITED it works.
-
(I posted this in ejb but didn't really get a solution that works)
I'm able to set the isolation level of a CMT using weblogic-ejb-jar.xml without
any problems. Below is a snipet which shows how that:
<transaction-isolation> <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
<method> <description><![CDATA[Transaction isolation for StateHandlerMessage]]></description>
<ejb-name>StateHandlerMessage</ejb-name> <method-name>*</method-name> </method>
</transaction-isolation>
That works perfectly for a CMT bean, however it does not seem to work for a BMT.
I'm using weblogic81 in development mode with an oracle jdriver and it seems my
BMT bean is getting an isolation level of TRANSACTION_SERIALIZABLE.
Is this a bug? If not how do I set the isolation level for a BMT bean? (I don't
think I can using Connection.setIsolationLevel since I don't have a connection
within my Session and Message Beans)
thanks!
lance
But weblogic.transaction.Transaction does have setProperty method and you should
be able to use :
weblogic.transaction.TxHelper.getTransaction().setProperty() to set that property.
"Lance" <[email protected]> wrote:
>
>Thanks for the reply, however javax.transaction.UserTransaction does
>not have a
>.setProperty method.
>
>Any ideas?
>
>lance
>
>"asafbu" <[email protected]> wrote:
>>
>>
>>
>>You set the isolation level for user transactions in the beans java
>code.
>>When
>>the application runs, the transaction is explicitly started.
>>
>>
>>User Transaction tx = (UserTransaction) ctx.lookup("javax.transaction.UserTransaction");
>>
>>tx.begin();
>>
>>tx.setProperty (TxConstants.ISOLATION_LEVEL, new Integer
>> (Connection.TRANSACTION_READ_COMMITED));
>>....
>>....
>>
>>
>>
>>
>>
>>"Lance" <[email protected]> wrote:
>>>
>>>(I posted this in ejb but didn't really get a solution that works)
>>>
>>>I'm able to set the isolation level of a CMT using weblogic-ejb-jar.xml
>>>without
>>>any problems. Below is a snipet which shows how that:
>>>
>>><transaction-isolation> <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
>>><method> <description><![CDATA[Transaction isolation for StateHandlerMessage]]></description>
>>><ejb-name>StateHandlerMessage</ejb-name> <method-name>*</method-name>
>>></method>
>>></transaction-isolation>
>>>
>>>That works perfectly for a CMT bean, however it does not seem to work
>>>for a BMT.
>>>I'm using weblogic81 in development mode with an oracle jdriver and
>>it
>>>seems my
>>>BMT bean is getting an isolation level of TRANSACTION_SERIALIZABLE.
>>
>>>
>>>Is this a bug? If not how do I set the isolation level for a BMT bean?
>>> (I don't
>>>think I can using Connection.setIsolationLevel since I don't have a
>>connection
>>>within my Session and Message Beans)
>>>
>>>thanks!
>>>
>>>lance
>>>
>>
>
-
Hi,
Im using Kodo 3.0.0 on Oracle 8.1.7.
I tried to define the isolation level in the kodo.properties:
e.g.: kodo.jdbc.TransactionIsolation: serializable
Unfortunately Oracle throws an exception which says, that "set
transaction" has to be the first statement called within a transaction. I
get this exception on almost every db access.
java.sql.SQLException: ORA-01453: SET TRANSACTION muss erste Anweisung der
Transaktion sein
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42)
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24)
at
kodo.jdbc.schema.LazySchemaFactory.findTable(LazySchemaFactory.java:1
50)
at
kodo.jdbc.meta.VerticalClassMapping.fromMappingInfo(VerticalClassMapp
ing.java:135)
at
kodo.jdbc.meta.RuntimeMappingProvider.getMapping(RuntimeMappingProvid
er.java:56)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:342)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:325)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappings(MappingRepository.java:2
72)
at
kodo.jdbc.meta.MappingRepository.getMetaDatas(MappingRepository.java:
256)
at kodo.query.AbstractQuery.internalCompile(AbstractQuery.java:538)
at kodo.query.AbstractQuery.compile(AbstractQuery.java:502)
at kodo.datacache.CacheAwareQuery.compile(CacheAwareQuery.java:265)
-- WolfgangMarc,
Here you go...
kodo.util.FatalDataStoreException: ORA-01453: SET TRANSACTION must be
first statement of transaction
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:897)
at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.initTestModel(AbstractConcurrentAction.java:290)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction$InitRunnable.run(AbstractConcurrentAction.java:212)
at
edu.sjsu.recon.util.ConcurrencyUtilities.executeSynchronized(ConcurrencyUtilities.java:20)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.setup(AbstractConcurrentAction.java:75)
at
edu.sjsu.recon.execution.ServerExecutor.beforeExecute(ServerExecutor.java:27)
at
edu.sjsu.recon.execution.AbstractExecutor.execute(AbstractExecutor.java:43)
at
edu.sjsu.recon.execution.DefaultExecutionCoordinator.executeAction(DefaultExecutionCoordinator.java:25)
at
edu.sjsu.recon.server.handler.ExecutionRequestHandler.handleRequest(ExecutionRequestHandler.java:63)
at edu.sjsu.recon.server.RequestProcessor.run(RequestProcessor.java:90)
NestedThrowablesStackTrace:
kodo.util.DataStoreException: ORA-01453: SET TRANSACTION must be first
statement of transaction
at
kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3004)
at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77)
at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43)
at kodo.jdbc.runtime.JDBCStoreManager.connect(JDBCStoreManager.java:871)
at
kodo.jdbc.runtime.JDBCStoreManager.retainConnection(JDBCStoreManager.java:189)
at kodo.jdbc.runtime.JDBCStoreManager.begin(JDBCStoreManager.java:114)
at
kodo.runtime.DelegatingStoreManager.begin(DelegatingStoreManager.java:95)
at
kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:1004)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:885)
at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.initTestModel(AbstractConcurrentAction.java:290)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction$InitRunnable.run(AbstractConcurrentAction.java:212)
at
edu.sjsu.recon.util.ConcurrencyUtilities.executeSynchronized(ConcurrencyUtilities.java:20)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.setup(AbstractConcurrentAction.java:75)
at
edu.sjsu.recon.execution.ServerExecutor.beforeExecute(ServerExecutor.java:27)
at
edu.sjsu.recon.execution.AbstractExecutor.execute(AbstractExecutor.java:43)
at
edu.sjsu.recon.execution.DefaultExecutionCoordinator.executeAction(DefaultExecutionCoordinator.java:25)
at
edu.sjsu.recon.server.handler.ExecutionRequestHandler.handleRequest(ExecutionRequestHandler.java:63)
at edu.sjsu.recon.server.RequestProcessor.run(RequestProcessor.java:90)
NestedThrowablesStackTrace:
java.sql.SQLException: ORA-01453: SET TRANSACTION must be first statement
of transaction
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:623)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:112)
at oracle.jdbc.driver.T4CStatement.execute_for_rows(T4CStatement.java:474)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1028)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1516)
at
oracle.jdbc.driver.PhysicalConnection.setTransactionIsolation(PhysicalConnection.java:1412)
at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
at
com.solarmetric.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
at
com.solarmetric.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:90)
at
com.solarmetric.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:82)
at
com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:131)
at
kodo.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:305)
at
kodo.jdbc.runtime.JDBCStoreManager.connectInternal(JDBCStoreManager.java:887)
at kodo.jdbc.runtime.JDBCStoreManager.connect(JDBCStoreManager.java:865)
at
kodo.jdbc.runtime.JDBCStoreManager.retainConnection(JDBCStoreManager.java:189)
at kodo.jdbc.runtime.JDBCStoreManager.begin(JDBCStoreManager.java:114)
at
kodo.runtime.DelegatingStoreManager.begin(DelegatingStoreManager.java:95)
at
kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:1004)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:885)
at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.initTestModel(AbstractConcurrentAction.java:290)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction$InitRunnable.run(AbstractConcurrentAction.java:212)
at
edu.sjsu.recon.util.ConcurrencyUtilities.executeSynchronized(ConcurrencyUtilities.java:20)
at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.setup(AbstractConcurrentAction.java:75)
at
edu.sjsu.recon.execution.ServerExecutor.beforeExecute(ServerExecutor.java:27)
at
edu.sjsu.recon.execution.AbstractExecutor.execute(AbstractExecutor.java:43)
at
edu.sjsu.recon.execution.DefaultExecutionCoordinator.executeAction(DefaultExecutionCoordinator.java:25)
at
edu.sjsu.recon.server.handler.ExecutionRequestHandler.handleRequest(ExecutionRequestHandler.java:63)
at edu.sjsu.recon.server.RequestProcessor.run(RequestProcessor.java:90)
Marc Prud'hommeaux wrote:
Cleo-
Can you post the complete stack (including all the nested stack traces)?
In article <[email protected]>, Cleo wrote:
Marc,
Here is the stack:
ORA-01453: SET TRANSACTION must be first statement of transaction
kodo.util.FatalDataStoreException
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:897)
at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
This is the code being executed:
Transaction initTransaction = initPersistenceManager.currentTransaction();
initTransaction.begin();
initPersistenceManager.makePersistentAll(model);
initTransaction.commit(); //EXCEPTION HERE
initPersistenceManager.close();
thx
Marc Prud'hommeaux wrote:
Cleo-
Can you post the complete stack trace from the exception? I expect it is
different from the one posted previously (which was with a much earlier
version of Kodo).
In article <[email protected]>, Cleo wrote:
Has anybody figured out how to solve this?
I am having the same problem with:
KODO 3.2
Oracle JDBC Dirver 10.1.0.3
thx
PS: (I am on a deadline for the end of this week)
Stephen Kim wrote:
First I would suggest using Kodo 3.0.1. Second I would suggest trying
to use 9.0.1 drivers which work very well with 8.1.7.
Wolfgang Hutya wrote:
Hi,
Im using Kodo 3.0.0 on Oracle 8.1.7.
I tried to define the isolation level in the kodo.properties:
e.g.: kodo.jdbc.TransactionIsolation: serializable
Unfortunately Oracle throws an exception which says, that "set
transaction" has to be the first statement called within a
transaction.
I
get this exception on almost every db access.
java.sql.SQLException: ORA-01453: SET TRANSACTION muss erste
Anweisung
der
Transaktion sein
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42)
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24)
at
kodo.jdbc.schema.LazySchemaFactory.findTable(LazySchemaFactory.java:1
50)
at
kodo.jdbc.meta.VerticalClassMapping.fromMappingInfo(VerticalClassMapp
ing.java:135)
at
kodo.jdbc.meta.RuntimeMappingProvider.getMapping(RuntimeMappingProvid
er.java:56)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:342)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:325)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappings(MappingRepository.java:2
72)
at
kodo.jdbc.meta.MappingRepository.getMetaDatas(MappingRepository.java:
256)
atkodo.query.AbstractQuery.internalCompile(AbstractQuery.java:538)
at kodo.query.AbstractQuery.compile(AbstractQuery.java:502)
atkodo.datacache.CacheAwareQuery.compile(CacheAwareQuery.java:265)
-- Wolfgang
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com
Marc Prud'hommeaux
SolarMetric Inc.
Marc Prud'hommeaux
SolarMetric Inc. -
Setting Isolation Level In A UserTransaction
We are having a problem where a class creates a UserTransaction from the InitialContext,
but does not see any database changes made by other EJBs even though they have
been committed. This "seems" like an isolation issue.
What is the default isolation level for UserTransaction? And since it appears
that it is not seeing committed data, what level should it be set to? (i.e. TRANSACTION_READ_COMMITTED
would be nice...)this is mirrored from the transaction newsgroup:
Joseph Weinstein <[email protected]> wrote:
>
>
Interesting, but it's not an isolation level issue. There is no DBMS
isolation level
that could cause a user not to see already-committed data.Well, we are using Oracle as our backend and it supports Read Uncommitted, Read
Committed and Serializable. The Serializable option would prevent a transaction
from seeing any committed data to a table (i.e. prevents unrepeatable reads).
The default isolation level of most DBMSes is READ_COMMITTED, and you
should
never have to change it, and you should be able to see already-committed
data.I agree, but that is not happening for us (and this gets somewhat complicated
with JMS). What is Weblogic 8.1's default isolation level for any transaction.
From the link below, I get the impression it is SERIALIZABLE which would explain
the behaviour I'm seeing. Athough the article seems to be talking about CMT (container
transation), I would suspect a BMT (bean managed transaction) be similar (just
manual).
If this only confuses things, please let me know the easiest way to communicate
this issue (code, etc..)
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.transaction&item=227&utag
(from the article)
Subject: Re: What is ths default transaction isolation level
Date: Mon, 12 Feb 2001 15:27:24 -0500
From: "Cameron Purdy" <[email protected]>
Organization: BEA SYSTEMS Inc
Newsgroup: weblogic.developer.interest.transaction
serializable
-- Cameron Purdy Tangosol, Inc. http://www.tangosol.com +1.617.623.5782 WebLogic
Consulting Available
"mrityunjay" <[email protected]> wrote in message news:3a86c781$[email protected]..
Hi , > If transaction isolation , for a EJB is not specified what is the > defaulttransaction isolation level > Thanks > Jay > >
Maybe you are looking for
-
Imac 27" bought Jan 2011 running 10.6.4
Having a back up of my valued files and programmes I decided to do a clean install on this mac (I was unhappy with my sims 3 game and wanted to start afresh) so inserted my install dvd which promptly got eaten by the superdrive with lots of grungy no
-
Installation trial failed on MS Visual C++
Hello, Can't install a trial of inDesign (also tried Photoshop and Illustrator). Get an error (see below). Installed Microsoft Visual C++ 2010 Redistritutable Package. Zie image. Restarted the computer. Tried again. Same issue. Adobe Photoshop 5 is p
-
Service tax Receivable and payable adjustment automatically
Dear GURU, Service Tax Receivable & Payable The Client wants to have a Service Tax Control Account that would be automatically populated for the particular bill / Invoice on the day of Vendor Payment and Customer Receipt. a. Example While Billing
-
@MOVAVG equivilent in Ver 11.1.1.3
Can anyone help me with the conversion of @MOVAVG to Essbase Ver 11.1.1.3 ? I want to convert: @MOVAVG(Sales,7) to the equivilent in Essabse Ver 11.1.1.3. Any help would be appreciated ! Thanks
-
Where should I put my code?
Where should I put my code, on the buttons and other items in question, or in a separate Layer, referencing the items I need...? Background : I'm REALLY new to Flash with Adobe. I've used SwishMax a little in the past, but nothing of recent. At work