Java Web Server 6.1 & Pooled SQL Server 2000 JDBC Connections

If anyone can shed some light on this problem I would greatly appreciate it.
I am unsuccessfully trying to use a database connnection retrieved from a pool configured using Java System Web Server 6.1 with the SQL Server 2000 JDBC Driver.
The background:
1. I have downloaded the SQL Server 2000 JDBC Driver and installed it on the web server.
2. I used the Administration GUI to add the .jars(namely msbase.jar, msutil.jar, and mssqlserver.jar), to the classpath.
3. Upon creating a simply JSP to access connection metadata using the direct connect method, ie.,
Class.forName( com.microsoft.jdbc.sqlserver.SQLServerDriver);
Connection con = DriverManager.getConnection( "jdbc:microsoft:sqlserver:// ....
I am shown a successful output of...
JDBC Test
Registering JDBC Driver
driverClass: com.microsoft.jdbc.sqlserver.SQLServerDriver loaded and registered.
Driver Information
Driver Name: SQLServer
Driver Version: 2.2.0037
Database Information
Database Name: Microsoft SQL Server
Database Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: )
Avalilable Catalogs
catalog: master
catalog: msdb
catalog: Northwind
catalog: pubs
catalog: tempdb
4. This tells me that the web server has access to the files necessary and the classpath is configured correctly.
Now the fun begins...
In order to set up the JDBC Connection Pool I have done the following...
1. I have created a web.xml file for the web-app which contains the JSP and includes the following entry
<resource-ref>
<res-ref-name>jdbc/devjwscp</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
2. I have used the "JDBC Connection Pools" link under the "Java" tab in the Administration GUI to create a connection pool.
"Pool Name:" is "devjwscp"
"DataSource Classname" is set to "com.microsoft.jdbcx.sqlserver.SQLServerDataSource". All other properties have been left alone.
3. I have used the "JDBC Resources" link under the "Java" tab in the Administration GUI to create a JNDI resource.
"JNDI Name" is set to "jdbc/devjwscp"
"Status" is "true"
"Pool Name" is "devjwscp"
The web-app JSP comes back with the following exception.
JDBC Test
Exception Thrown
Cannot create resource instance
javax.naming.NamingException: Cannot create resource instanceorg.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:167)
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
org.apache.naming.NamingContext.lookup(NamingContext.java:834)
org.apache.naming.NamingContext.lookup(NamingContext.java:181)
org.apache.naming.NamingContext.lookup(NamingContext.java:822)
org.apache.naming.NamingContext.lookup(NamingContext.java:181)
org.apache.naming.NamingContext.lookup(NamingContext.java:822)
org.apache.naming.NamingContext.lookup(NamingContext.java:181)
org.apache.naming.NamingContext.lookup(NamingContext.java:822)
org.apache.naming.NamingContext.lookup(NamingContext.java:194)
org.apache.naming.SelectorContext.lookup(SelectorContext.java:183)
javax.naming.InitialContext.lookup(InitialContext.java:347)
_jsps._jdbctest_jsp._jspService(_jdbctest_jsp.java:236)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:667)
com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:447)
com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:363)
javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:161)
com.iplanet.ias.web.WebContainer.service(WebContainer.java:586)
4. FYI my server.xml <RESOURCE> entry looks as is shown below
<RESOURCES>
<JDBCCONNECTIONPOOL name="devjwscp" datasourceclassname="com.microsoft.jdbcx.sqlserver.SQLServerDataSource" steadypoolsize="8" maxpoolsize="32" poolresizequantity="2" idletimeout="300" maxwaittime="60000" connectionvalidationrequired="off" connectionvalidationmethod="auto-commit" validationtablename="" failallconnections="off" transactionisolationlevel="read-uncommitted" isolationlevelguaranteed="off">
<PROPERTY name="serverName" value="secret"/>
<PROPERTY name="portNumber" value="1433"/>
<PROPERTY name="User" value="secret"/>
<PROPERTY name="Password" value="secret"/>
</JDBCCONNECTIONPOOL>
<JDBCRESOURCE jndiname="jdbc/devjwscp" poolname="devjwscp" enabled="on"/>
</RESOURCES>
What gives? Do I need to add anything else to the server.xml? I know the server.xml for JWS differs from Apache. I have done an exhaustive search of the web. Many other individuals have had the same thing happen, buy none of them offered any explaination or remedy.
Thanks in advance.

Hi,
Were you able to get it working.
I am using
Sun ONE Web Server 6.1SP2 B04/07/2004 18:47
I am still getiing the same error. I also suspect that there is something wrong with thr DTD too. It gives me the following when the server comes up.
Sun ONE Web Server 6.1SP2 B04/07/2004 18:47
Listening for transport dt_socket at address: 1699
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_04] from [Sun M
icrosystems Inc.]
info: WEB0100: Loading web module in virtual server [https-AW-NYNY-D609628.nna.
wdpr.disy.com] at [acsanet]
info: WEB0100: Loading web module in virtual server [https-AW-NYNY-D609628.nna.
wdpr.disy.com] at [testing]
failure: WEB0120: XML error parsing deployment descriptor [C:/Sun/WebServer6.1/h
ttps-AW-NYNY-D609628.nna.wdpr.disy.com/webapps/https-AW-NYNY-D609628.nna.wdp
r.disy.com/testing/WEB-INF/sun-web.xml]
Failed to create the XML-DOM Document. Check your XML to make sure it is correc
t.org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8
character beginning with 0xa0" (line number may be too low).
at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(Input
Entity.java:914)
at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl
.java:185)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(Grap
hManager.java:711)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:
2075)
at com.iplanet.ias.web.WebContainer.loadWebModule(WebContainer.java:695)
at com.iplanet.ias.web.WebContainer.loadStandaloneWebModule(WebContainer
.java:626)
at com.iplanet.ias.web.WebContainer.loadWebModules(WebContainer.java:600)
at com.iplanet.ias.web.WebContainer.createVS(WebContainer.java:374)
at com.iplanet.ias.server.J2EERunner.createVS(J2EERunner.java:223)
info: WEB0100: Loading web module in virtual server [https-AW-NYNY-D609628.nna.wdpr.disy.com] at [search]
config: HTTP4292: flex-init: Log file C:/Sun/WebServer6.1/https-AW-NYNY-D609628.
nna.wdpr.disy.com/logs/access should be removed before changing its format
info: HTTP3072: [LS ls1] http://AW-NYNY-D609628.nna.wdpr.disy.com:80 ready to
accept requests
startup: server started successfully
info: CORE3274: successful server startup
the sun-web.xml is as below:
<?xml�version="1.0"�encoding="UTF-8"?>
<!--
     Copyright 2002 Sun Microsystems, Inc. All rights reserved.
-->
<!DOCTYPE�sun-web-app�PUBLIC�"-//Sun�Microsystems,�Inc.//DTD�Application�Server�8.0�Servlet�2.4//EN"�"http://www.sun.com/software/appserver/dtds/sun-web-app_2_4-0.dtd">
<sun-web-app>
     <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc/oraclePool</jndi-name>
     </resource-ref>
</sun-web-app>
Am I using the right DTD ?
Please let me know.
Thank you.
-- Martin Louis

Similar Messages

  • M trying to open a java web site its not opening and server goes to java website...??

    m trying to open a java web site its not opening and server goes to java web sites ...........???

    Java is not available for iOS devices, so the site you are trying to access won't work.

  • 2008 R2 Express Web Upgrade Failed: The selected SQL Server instance does not meet upgrade matrix requirements.

    HI
    I want to upgrade a SQL 2008 R2 Express install to 2008 R2 Web Edition.
    when I click view detailed report I get the below.
    How do I fix this?

    Hello,
    As per below link upgrade of SQL Server 2008 express to SQL server 2008 r2 web is not supported.So i guess this message.I have never tried upgrading unsupported edition so not too much sure about error message.But i am sure not meets requirement is because
    of unsupported upgrade you are doing
    http://technet.microsoft.com/en-us/library/ms143393(v=sql.105).aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Web logic cann't load Sql Server jdbc driver

    Web logic cann't load Sql Server jdbc driver. I've got an exception:
    NoClassDefFoundError: com/microsoft/sqlserver/jdbc/ISQLServerConnection
    but sqljdbc.jar is in weblogic's library directory.

    Hi,
    You can find Oracle Support id 1503650.1 (https://support.oracle.com) with the solution.
    Arik

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

  • Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

    I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
    "fix after" status.
    First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
    Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService.  That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list.  I tried
    setting the service account to a local account as  well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
    Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

    Hi Bob,
    Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
    Regards,
    Sofiya Li
    If you have any feedback on our support, please click here.
    Sofiya Li
    TechNet Community Support

  • How to restore SQL Server 2008 database to SQL Server Express 2012

    How to restore SQL Server 2008 database to SQL Server Express 2012.
    I BACKED UP a SQL Server 2008 database from work, which runs the enterprise version of 2008, and I tried to RESTORE it to my new 64-Bit home PC which is running the new SQL Server Express 2012 64-Bit (Advanced Edition).
    But if fails. I get the following message text.
    Can anyone help me please. I thought restoring a 2008 database to the later version 2012 would be possible.
    Here is the error message. Thanks.
    TITLE: Microsoft SQL Server Management Studio
    Restore of database failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
    ADDITIONAL INFORMATION:
    System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the backup, or use a
    backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)

    ADDITIONAL INFORMATION:
    System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the
    backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
    Are you sure your database is SQL server 2008 from error message it seems your SQL server version is 2000.I guess you have multiple versions of SQL server.
    AFAIK you cannot restore backup of SQL server 2000 to 2012 directly .Restore it first to SQL 2008/2008R2 or 2005 then take backup again of new database created and then you would be able to restore it on 2012.Its kind of intermediate way
    Also make sure your DB size is less than 10 G as max DB size supported by Express edition is 10 G and if your DB size is more than 10 G restore will fail.
    You are also trying to restore enterprise DB backup on express edition so you will loose enterprise features on express edition
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • [Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

    Hi,
    We have exadata x3-2. I am seeing this error in alert log file frequently.
    The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
    Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
    ORA-01017: invalid username/password; logon denied
    [Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
    ORA-02063: preceding 2 lines from HIS_CUST
    The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
    Contains many repeated lines like below
    *** 2015-01-21 06:34:40.209
    ERROR, tran=21.24.51311, session#=1, ose=0:
    ORA-01017: invalid username/password; logon denied
    [Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
    ORA-02063: preceding 2 lines from HIS_CUST
    Could any please help why is this happening.
    Thanks

    Hi,
       You have customers who are running distributed transactions using a gateway which need to be rolled back.  However, the gateway has not been correctly configured for distributed transactions.  To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter  HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
    I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
    If you have access to My Oracle Support have a look at this note -
    How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
    Otherwise, check the Gateway documentation.
    Regards,
    Mike

  • Upgrade from sql Server 9.0 to sql Server 12.0

    I am currently running SQLEXPRESS (SQL Server 9.0)  It appears that there is a limit to the size of the database which I have exceeded.  I want to restore a backup of my customers DB and am not allowed to do so.  Appears to be a size issue,
    the customer DB is over 5 GB.
    Will I eliminate this size restriction using sql Server 12.0?
    I don't see any references to upgrading sql Server 9.0 to sql Server 12.0, only references to a new installation.  Can it be upgraded and how do I do that?

    Hello,
    Please read the following article.
    http://www.mssqltips.com/sqlservertip/2941/upgrading-to-sql-server-2012-express
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Upgrading SQL Server 7.0 to SQL Server 2000

    Hello,
    We want to upgrade Microsoft SQL Server 7.0 to SQL Server 2000 to implement Mobile scenario in CRM .If anyone has any utility  implementation guide or good information regarding it ,kindly please forward it to my mail id  [email protected]
    Thanks and Regards,
    Saumya Maheshwari

    Hello Saumya,
    I have sent you a Upgrade note. Hope that will be of help. However, I like to tell you that there is no migration procedure, per se. But you could follow the steps in the document and it should be a straight forward approach to 2000.
    In case,the authentification of the SQL Server 7.0 is set to "Windows NT only";While upgrading, the user chooses "The SQL Server system administrator login information (SQL Server authentication)" in the "Connect to Server" step and enters the password for the system administrator (sa).
    In the next step, the upgrade program checks if the user can log on to SQL Server. First, the Windows authentification of the logged on user is checked, which is successful. The 'sa' user and the relevant password are not verified. However, later in the upgrade process, the program tries to execute the scripts with the 'sa' user; this fails due to the "Windows NT only" authentification for SQL Server. The error ("Error running script: upgrade.sql(1)") message is written to the log file (upgrade.out) of the script (upgrade.sql):
    Login failed for user 'sa'. Reason: Not associated with a trusted SQL
    Solution - The upgrade program of SQL Server 2000 saves the settings of the upgrade in the registry. You can change the authentification mode there. Start the registry editor and go to the following entry in the left panel:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup\Resume\
    Locate the "DO-NT" value in the right panel. Change this value from "0" (SQL Server authentification) to "1" (NT authentification). You can then restart the upgrade; the program now logs on to SQL Server via the Windows authenification and also executes the scripts under this authentification.
    Please award points in case you find the solution of help to you.
    Thanks
    Sumit

  • How to find out sql server administrator account in sql server 2008 R2

    how to find out sql server administrator account in sql server 2008 R2
    adil

    there is any way to find out actual administrator
    because i forget that user i used to logon to server and installed sqlserver
    adil
    Hi adilahmed,
    According to your description, you forgot the account which was used to install SQL Server. SQL Server service account information is stored in Windows Registry database. You can get this information from Services Console or SQL Server Configuration.
    For example, to get account information from Services Console.
    1. Go to Start > Run > Services.msc
    2. Right Click on SQL Server Service, i.e. “SQL Server (InstanceName)” and go to properties
    3. The account information is available under Log On tab.
    Or you can get the information by using DMV and so on.
    SELECT servicename, service_account FROM   sys.dm_server_servicesGO
    If you now log in SQL Server by using sysadmin account, you can check all login names in security and find the original account to login.
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SQL Server Express 2014 and SQL Server Agent

    Any chance SQL Server Express 2014 supports SQL Server Agent. I have a home weather database and I have to import Data every 30 seconds.

    Any chance SQL Server Express 2014 supports SQL Server Agent. I have a home weather database and I have to import Data every 30 seconds.
    SQL server 2014 express does not have SQL Server agent.You can take help from creating batch files and running them thorugh CMD.windows scheduler will let you schedule it.
    How to schedule and automate backup in SQL Express
    Free job scheduling toll for SQL Express
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Retrieve available server names for MS SQL server

    hello
    Can somebody tell me how I can retrieve available server names for MS SQL server.
    When MS SQL server loads it asks for server name to connect but on the same time has a combobox with the available server names(instace+database name). How can I provide the same functionality in my application?
    Thank you in advance.

    It isn't going to be as simple as just the name.
    There are also different ways to connect and probably other parameters as well.
    SQL Server Enterprise Manager probably uses a discovery protocol. It probably sends one or more messages requesting information and those servers that want to respond.
    Note that none of that has anything to do with JDBC and discovering how it does that probably isn't easy. A packet sniffer might help.

  • Migrating SAP products from a non-SQL Server platform to a SQL Server 2005

    Hi,
    I have another question too.
    Can someone pls provide me the Considerations for Migrating SAP products from a non-SQL Server platform to a SQL Server 2005 platform?
    More specifically from Oracle to SQL 2005.
    Regards
    Abhi

    Hello
    You need to perform an OSDB migration.
    This will involve exporting your SAP system into a DB neutral format and then reloading this into an SQL 2005 SAP system.
    Please review http://service.sap.com/osdbmigration
    I recommend you review the homo/heterogeneous system copy guide for your SAP release.
    Thanks
    N.P.C

  • Caused by java.sql.SQLException: No JDBC connection can be made

    Hi,
    I am using OSB11g (with soa db adapter ) to select data from DB2 Database. I am trying to just fetch like 100 records(very less).
    I get this Exception once in 4-5 tests I do . I am not sure if I have to modify any configurations, in case its timing out .
    I see something like *"To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml)."*
    I don't see the tables when I try to perform SELECT operation in db adapter. In JDev worksheet I can see the tables and records when queried.
    BEA-380002: Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/SampleOSBEMEA/WSDL/DBOut [ DBOut_ptt::DBOut(DBOutInput_msg,DBOutOutputCollection) ] - WSIF JCA Execute of operation 'DBOut' failed due to: Pure SQL Exception.
    Pure SQL Execute of SELECT Column1, Column2 ..........Column216 from Table.
    Caused by java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Rolledback.
    ; nested exception is:
    BINDING.JCA-11633
    Pure SQL Exception.
    Caused by java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Rolledback.
    The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. This exception is considered retriable, likely due to a communication failure. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).
    The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. This exception is considered retriable, likely due to a communication failure. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).
    at oracle.tip.adapter.db.exceptions.DBResourceException.createXARetriableException(DBResourceException.java:670)
    at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:642)
    at oracle.tip.adapter.db.exceptions.DBResourceException.pureSQLException(DBResourceException.java:711)
    at oracle.tip.adapter.db.puresql.PureSQLInteraction.executePureSQL(PureSQLInteraction.java:625)
    at oracle.tip.adapter.db.DBInteraction.executePureSQL(DBInteraction.java:1146)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:254)
    at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:529)
    ... 63 more
    Caused by: java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Rolledback
    at weblogic.jdbc.jts.Driver.newConnection(Driver.java:949)
    at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:327)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:173)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:126)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94)
    at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:327)
    at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:291)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.reconnect(DatasourceAccessor.java:558)
    at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1433)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.incrementCallCount(DatasourceAccessor.java:302)
    at oracle.tip.adapter.db.DBConnection.getTopLinkSQLConnection(DBConnection.java:333)
    at oracle.tip.adapter.db.transaction.DBTransaction.beginInternal(DBTransaction.java:126)
    at oracle.tip.adapter.db.puresql.PureSQLInteraction.executePureSQL(PureSQLInteraction.java:171)
    ... 66 more
    Should I increase the time interval in weblogicra.xml (DEV/wls1034/middleware/Oracle_OSB1/lib/external/adapters/META-INF)
    for <wls:connection-reserve-timeout-seconds>5</wls:connection-reserve-timeout-seconds>
    Thanks
    Edited by: soauser on Jul 6, 2011 10:02 AM

    Looks like either database is too slow or data-source is not functioning properly. Make sure to test data source and see if it is in running state and it has sufficient number of connections (you may increase max connections value). Actually transaction is getting rolled back because it could not get connection in specified time period (may be JTA/statement timeout).
    Cross post in Weblogic JDBC forum as well for expert's advice -
    WebLogic Server - JDBC
    You may consider raising a case with support as well.
    Regards,
    Anuj

Maybe you are looking for