Weblogic jDriver for oracle/xa thin driver configuration
Hi,
I try to configure an XA thin connection pool to oracle.
Using the configuration from page 16-11 of adminguide.pdf,
the start is with the error "No suitable driver".
The driver is configured like that:
DriverClassname=oracle.jdbc.xa.client.OracleXADataSource
Also, with the classes12.zip for oracle 8.1.7 for jdk1.2 taken from oracle site,
before weblogic.jar in classpath, same error:(.
The error:
<Jan 14, 2001 2:22:01 PM EET> <Error> <JDBC> <Cannot startup connection pool "OracleJDBCTxConnectionPool"
weblogic.common.ResourceException: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:537)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:88)
at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:68)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:194)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy41.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy34.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
at weblogic.management.Admin.finish(Admin.java:520)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:203)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy41.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy34.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
at weblogic.management.Admin.finish(Admin.java:520)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
Thank you in advance.
kind regards, adrian
Hi,
it works :) !
Thank you,
Adrian
"John Harby" <[email protected]> wrote:
>
>Mine seems to work ok but I have classes12.zip after weblogic.jar.
>
>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.C:\oracle\ora81\jdbc\l
>ib\classes12.zip;.\config\examples\serverclasses
>
>
>"adrian balaban" <[email protected]> wrote:
>>
>>Hi,
>>
>>I try to configure an XA thin connection pool to oracle.
>>
>>Using the configuration from page 16-11 of adminguide.pdf,
>>the start is with the error "No suitable driver".
>>
>>The driver is configured like that:
>>DriverClassname=oracle.jdbc.xa.client.OracleXADataSource
>>
>>Also, with the classes12.zip for oracle 8.1.7 for jdk1.2 taken from
>oracle
>>site,
>>before weblogic.jar in classpath, same error:(.
>>
>>The error:
>>
>><Jan 14, 2001 2:22:01 PM EET> <Error> <JDBC> <Cannot startup connection
>>pool "OracleJDBCTxConnectionPool"
>>weblogic.common.ResourceException: java.sql.SQLException: No suitable
>>driver
>> at java.sql.DriverManager.getConnection(DriverManager.java:537)
>> at java.sql.DriverManager.getConnection(DriverManager.java:177)
>> at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
>> at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:88)
>> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:68)
>> at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:194)
>> at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
>> at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
>> at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
>> at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
>> at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
>> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
>> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
>> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
>> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
>> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
>> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
>> at $Proxy41.updateDeployments(Unknown Source)
>> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
>> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
>> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
>> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
>> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
>> at $Proxy34.start(Unknown Source)
>> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
>> at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
>> at weblogic.management.Admin.finish(Admin.java:520)
>> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
>> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
>> at weblogic.Server.main(Server.java:35)
>>
>> at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:203)
>> at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
>> at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
>> at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
>> at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
>> at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
>> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
>> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
>> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
>> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
>> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
>> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
>> at $Proxy41.updateDeployments(Unknown Source)
>> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
>> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
>> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
>> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
>> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
>> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
>> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
>> at $Proxy34.start(Unknown Source)
>> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
>> at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
>> at weblogic.management.Admin.finish(Admin.java:520)
>> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
>> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
>> at weblogic.Server.main(Server.java:35)
>>>
>>
>>Thank you in advance.
>>
>>kind regards, adrian
>
Similar Messages
-
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 -
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] -
How to use a custom KeyManager for Oracles JCBD thin driver
I am trying to create a java application that uses PKI for authentication. I need to be able to retrieve a certificate from the Microsoft Certificate Store MCS) and pass it along to an Oracle database (11.2). I am connecting using the jdbc:oracle:thin driver. After spending some time googlling it appears that I have to create a custom KeyManager and a custom TrustManager to accomplish this. I am not sure if this is even the correct way to approach the problem, but assuming it is; how do I force the jdbc:oracle:thin driver to use my KeyManager and TrustManager? Also, as stated above the client certificates will be stored in the MCS while the Oracle database will be using a wallet. The database could be running on just about any OS that supports Oracles database which is why I will not be setting up Oracle to use MCS.
Thanks for the help!I am trying to create a java application that uses PKI for authentication. I need to be able to retrieve a certificate from the Microsoft Certificate Store MCS) and pass it along to an Oracle database (11.2). I am connecting using the jdbc:oracle:thin driver. After spending some time googlling it appears that I have to create a custom KeyManager and a custom TrustManager to accomplish this. I am not sure if this is even the correct way to approach the problem, but assuming it is; how do I force the jdbc:oracle:thin driver to use my KeyManager and TrustManager? Also, as stated above the client certificates will be stored in the MCS while the Oracle database will be using a wallet. The database could be running on just about any OS that supports Oracles database which is why I will not be setting up Oracle to use MCS.
Thanks for the help! -
Problem installing weblogic jdriver for oracle
Hi ,
I have installed WLS510 and Oracle8i Personal Edition on windows98. I have
put the c:\weblogic\bin\oci815_8 directory in the system path and
c:\oracle\ora81\jdbc\lib\classes102.zip in the CLASSPATH
Now when I try to test the connection using the following command:
$ java utils.t3dbping URL user password DB driver_class driver_URL
I get error :
Connecting to WebLogic with the WebLogic JDBC Driver
Can't connect with the WebLogic JDBC driver:
System.loadLibrary threw java.lang.UnsatisfiedLinkError
with the message 'no weblogicoci36 in java.library.path'.
Server StackTrace:
<not available>]
Could anyone please tell me what java.library.path is and where should I
find
weblogicoci36.
Thanks
Vishwajeet Lohakareyjava.library.path is Java System variable for seting directories where will java look out for native library modules (DLLs on NT). It is normally unset because DLLs are serached by standard NT algorithm (PATH variable, System dir) too.
weblogicoci36 is native module name of WL JDBC driver for Oracle that Java&NT couldn't find. Coresponding DLL file is in your c:\weblogic\bin\oci815_8 directory.
Problem could be in that if WL is started as NT Service,
a) PATH variable must be set for System not for User and
b) this setting don't take effect until NT restart.
VZ
"Vishwajeet Lohakarey" <[email protected]> wrote:
Hi ,
I have installed WLS510 and Oracle8i Personal Edition on windows98. I have
put the c:\weblogic\bin\oci815_8 directory in the system path and
c:\oracle\ora81\jdbc\lib\classes102.zip in the CLASSPATH
Now when I try to test the connection using the following command:
$ java utils.t3dbping URL user password DB driver_class driver_URL
I get error :
Connecting to WebLogic with the WebLogic JDBC Driver
Can't connect with the WebLogic JDBC driver:
System.loadLibrary threw java.lang.UnsatisfiedLinkError
with the message 'no weblogicoci36 in java.library.path'.
Server StackTrace:
<not available>]
Could anyone please tell me what java.library.path is and where should I
find
weblogicoci36.
Thanks
Vishwajeet Lohakarey -
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
>
>
-
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 -
Oracle JDBC Thin Driver for oracle 9.2.0.4
Hi,
It would be nice if someone please guide me to the download of Oracle JDBC Thin Driver for oracle 9.2.0.4.
Thanks in anticipationuser566773,
As far as I know, all Oracle JDBC drivers are meant to be backward compatible.
According to the table on the following Web page, the latest Oracle JDBC driver can be used with Oracle 9.2.0.x DBMS.
http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
Good Luck,
Avi. -
Sql_trace does not work for Java app using Oracle JDBC thin driver
Hi,
I'm using Oracle 8.1.7. I enabled sql trace at instance level by setting sql_trace and timed_statistics to true in init.ora. I restarted the db instance. I wrote a stand-alone java application which used Oracle JDBC thin driver(classes12.zip) to make a connection to my db instance, do some select statements, and close the connection. There were no trace files generated in the folder specified by udump_dest variable. However, if I used sqlplus or dba studio, I saw trace files generated. Has anyone got Oracle sql trace work for JDBC calls from java apps.
Thanks in advance!Hi,
I'm using Oracle 8.1.7. I enabled sql trace at instance level by setting sql_trace and timed_statistics to true in init.ora. I restarted the db instance. I wrote a stand-alone java application which used Oracle JDBC thin driver(classes12.zip) to make a connection to my db instance, do some select statements, and close the connection. There were no trace files generated in the folder specified by udump_dest variable. However, if I used sqlplus or dba studio, I saw trace files generated. Has anyone got Oracle sql trace work for JDBC calls from java apps.
Thanks in advance! -
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) -
Bug in Oracle JDBC thin driver (parameter order)
[ I'd preferably send this to some Oracle support email but I
can't find any on both www.oracle.com and www.technet.com. ]
The following program illustrates bug I found in JDBC Oracle thin
driver.
* Synopsis:
The parameters of prepared statement (I tested SELECT's and
UPDATE's) are bound in the reverse order.
If one do:
PreparedStatement p = connection.prepareStatement(
"SELECT field FROM table WHERE first = ? and second = ?");
and then bind parameter 1 to "a" and parameter to "b":
p.setString(1, "a");
p.setString(2, "b");
then executing p yields the same results as executing
SELECT field FROM table WHERE first = "b" and second = "a"
although it should be equivalent to
SELECT field FROM table WHERE first = "a" and second = "b"
The bug is present only in "thin" Oracle JDBC driver. Changing
driver to "oci8" solves the problem.
* Version and platform info:
I detected the bug using Oracle 8.0.5 server for Linux.
According to $ORACLE_HOME/jdbc/README.doc that is
Oracle JDBC Drivers release 8.0.5.0.0 (Production Release)
* The program below:
The program below illustrates the bug by creating dummy two
column table, inserting the row into it and then selecting
the contents using prepared statement. Those operations
are performed on both good (oci8) and bad (thin) connections,
the results can be compared.
You may need to change SID, listener port and account data
in getConnecton calls.
Sample program output:
$ javac ShowBug.java; java ShowBug
Output for both connections should be the same
--------------- thin Driver ---------------
[ Non parametrized query: ]
aaa
[ The same - parametrized (should give one row): ]
[ The same - with buggy reversed order (should give no answers):
aaa
--------------- oci8 driver ---------------
[ Non parametrized query: ]
aaa
[ The same - parametrized (should give one row): ]
aaa
[ The same - with buggy reversed order (should give no answers):
--------------- The end ---------------
* The program itself
import java.sql.*;
class ShowBug
public static void main (String args [])
throws SQLException
// Load the Oracle JDBC driver
DriverManager.registerDriver(new
oracle.jdbc.driver.OracleDriver());
System.out.println("Output for both connections should be the
same");
Connection buggyConnection
= DriverManager.getConnection
("jdbc:oracle:thin:@localhost:1521:ORACLE",
"scott", "tiger");
process("thin Driver", buggyConnection);
Connection goodConnection
= DriverManager.getConnection ("jdbc:oracle:oci8:",
"scott", "tiger");
process("oci8 driver", goodConnection);
System.out.println("--------------- The end ---------------");
public static void process(String title, Connection conn)
throws SQLException
System.out.println("--------------- " + title + "
Statement stmt = conn.createStatement ();
stmt.execute(
"CREATE TABLE bug (id VARCHAR(10), val VARCHAR(10))");
stmt.executeUpdate(
"INSERT INTO bug VALUES('aaa', 'bbb')");
System.out.println("[ Non parametrized query: ]");
ResultSet rset = stmt.executeQuery(
"select id from bug where id = 'aaa' and val = 'bbb'");
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println("[ The same - parametrized (should give one
row): ]");
PreparedStatement prep = conn.prepareStatement(
"select id from bug where id = ? and val = ?");
prep.setString(1, "aaa");
prep.setString(2, "bbb");
rset = prep.executeQuery();
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println("[ The same - with buggy reversed order
(should give no answers): ]");
prep = conn.prepareStatement(
"select id from bug where id = ? and val = ?");
prep.setString(1, "bbb");
prep.setString(2, "aaa");
rset = prep.executeQuery();
while (rset.next ())
System.out.println (rset.getString (1));
stmt.execute("DROP TABLE bug");
nullHorea
In the ejb-jar.xml, in the method a cursor is closed, set <trans-attribute>
to "Never".
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name></ejb-name>
<method-name></method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
</assembly-descriptor>
Deepak
Horea Raducan wrote:
Is there a known bug in Oracle JDBC thin driver version 8.1.6 that would
prevent it from closing the open cursors ?
Thank you,
Horea -
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 -
Oracle JDBC Thin Driver and Firewall Problem
Hi!
We have Oracle 8.1.5 and Websphere App Server. There is a
firewall between the two. A servlet creates a connection pool
(not that of Wesphere's). The frontend is JSP/HTML (no applets).
The servlet uses the Oracle JDBC Thin Driver for DB Connections.
The problem is - Once the connection is freed, the connection
pool is not being able to retrieve it and hence it created
another one, thus reaching the max. # of connections and the
system hangs. Restarting the DB service flushes the connection
and the application starts running again...
There was a similar problem discussed in this forums long ago. I
have not yet tried mentioning the firwall port and IP in the
connection string. But apart from that, is there any other
setting I need to do (on firewall or for the connectionstring)
to deal with this problem?
Someone had suggested to punch a hole in the firewall for the DB
port - but we can not really do that in the current scenario...
I would appreciate if anyone could share their experience
regarding how they resolved this issue.
Thanks in advance,
Vijaya.One more question -
Can we use Oracle JDBC OCI driver? We do not have any appletes...
Does it have firewall issues too? Is there any other driver that
we can use?
Thanks,
Vijaya. -
Change expired password using oracle jdbc thin driver
Hello,
I have a java program that uses the oracle jdbc thin driver (ojdbc6 - version 11.2.0.3) for database connection. My question is if I have any possibility to change an expired password (java.sql.SQLException: ORA-28001: the password has expired) using the thin driver - NOT OCI?No - the thin driver doesn't have any password management features.
-
BEA WebLogic jDriver for Microsoft SQL Server
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
Thank you for your attention regarding this matter.Actually, this driver is already documented as deprecated. We intended to remove it from a future
release (most likely, the release after WLS 8.1).
The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
for features, quality, and performance. We are pushing very hard to have this replacement
driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
ship in July). The most likely candidate is already in testing both at the WLS level and
with the layered products. It also did quite well in an internal performance comparison.
"Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
>
>
Peter Foskaris wrote:
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
product development direction.
>>
Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
our next major release (8), but may not be in future ones.
Joe Weinstein at BEA
Maybe you are looking for
-
hie guys I had initially posted a similar post in ABAP-General forum but was advised to post one here because this is the most appropriate forum. I have customized the balance confirmation letter however i am failing to find the field with the vendor
-
I just can't fix my iPhone4, it requests restore more than 8 times
-
OAS: Building a HA environment with OAS
Hi all, we have tio scale up our OFM capacity asap. Because migration to WLS in a short time is not possible, we have to prepare OAS Cluster + SOA 10g environment. We are working at this moment in a single node environment. I'd like to know about bes
-
It seems that there are new classes with LR6: LrDevelopController LrApplicationView LrSelection LrSlideshow LrSounds LrTether LrUndo For my purposes, LrDevelopController sounds promising Jarno
-
Is there a way to just change the theme (background) on a website already created?