Regarding JDBC Connectivity

Hi,
Can I know if VB can use JDBC Connectivity to get connected to Mainframe DB2? Or is there any option of connecting from VB through ODBC Connectivity to Mainframe db2?

See if this link is useful:
http://database.sarang.net/database/db2/vb/db2-with-vb.html

Similar Messages

Need some tips about efficiency regarding jdbc connections

Hi there. I am a pre-novice to jsp, jdbc, etc. Anyways, I recently created a site for the purpose of learning jsp, servlets etc. and it has been going pretty decent. However, today I started thinking of whether my coding would be able to survive if many users were to use it.
Let me describe in brief what I am doing and then I will move on to my question(s).
I have a 'My Account' feature and users can register and then login their respective accounts. I ask the user to login and then I check if the login is correct with the saved data in my MySQL database. If its correct they can enter otherwise they get to try again. Simple enuf. I also create a session when they login and in it I put their username. I also use page response.sendRedirect() method to send people back to login page if they dont have a session created already and they try to access pages inside the 'My Account'. It seems to be working great for my purposes and all that but as I said today I started thinking. Right now, I believe my coding is in some matters pretty lousy. I have a bean whose one and only purpose is to connect to the database. But I noticed that almost all my pages in 'My Account' need to connect to the database to do one thing or another and I tend to be creating a new connection for each page using that bean. So I started thinking.. what is the best way to go about doing this???
Should I create ONE connection at the time of logging and then use that for rest of the pages (I remember reading something about scope=session for JSP usebean).. or should I keep doing what I am doing.. that is opening a new connection at each page and then closing it before going to the next page. Also, I wonder how good my site will stand if multiple people are trying to access same things etc etc. Please I looked around quite a bit but I havnt found a simple straightforward response. I would really appreciate if anyone here can share their wisdom or post some useful links. I wanna become a wise coder just like you :)

duh Looks like I posted this in the wrong forum by mistake
note to himself: To become a wise coder post in the right forums!

Error while creating a report that uses Oracle OCI JDBC connectivity

Please let me know why my CR and LF characters are removed from my forum posting *****
Hi,
I was trying to create a report that uses Oracle OCI JDBC connectivity. I am using Eclipse3.4 download from "cr4e-all-in-one-win_2.0.2.zip". I have successfully created a JDBC OCI connection.
The connection parameters are given below:
URL: jdbc:oracle:oci8:@xe
Database: xe
username: <userName>
password: <password>
I have tested the above connection in Data source Explorer and it works fine!!!
But I am getting the following error when I drag-and-drop a table from the list of tables. Not sure what I am missing here? Any help is highly appreciated.
com.businessobjects.reports.jdbinterface.common.DBException: InvalidURLOrClassName
 at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCConnection.Open(Unknown Source)
 at com.crystaldecisions.reports.queryengine.JDBConnectionWrapper.Open(SourceFile:123)
 at com.crystaldecisions.reports.queryengine.Connection.br(SourceFile:1771)
 at com.crystaldecisions.reports.queryengine.Connection.bs(SourceFile:491)
 at com.crystaldecisions.reports.queryengine.Connection.t1(SourceFile:2979)
 at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2408)
 at com.crystaldecisions.reports.dataengine.datafoundation.AddDatabaseTableCommand.new(SourceFile:529)
 at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
 at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
 at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)
 at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.byte(SourceFile:1079)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1163)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:657)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:163)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:525)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:523)
 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at com.businessobjects.crystalreports.designer.core.util.thread.ExecutorWithIdleProcessing$3.doWork(ExecutorWithIdleProcessing.java:182)
 at com.businessobjects.crystalreports.designer.core.util.thread.AbstractCancellableRunnable.run(AbstractCancellableRunnable.java:69)
 at com.businessobjects.crystalreports.designer.core.util.thread.PriorityTask.run(PriorityTask.java:75)
 at com.businessobjects.crystalreports.designer.core.util.thread.PriorityCompoundCancellableRunnable.runSubtask(PriorityCompoundCancellableRunnable.java:187)
 at com.businessobjects.crystalreports.designer.core.util.thread.PriorityProgressAwareRunnable.runSubtask(PriorityProgressAwareRunnable.java:90)
 at com.businessobjects.crystalreports.designer.core.util.thread.PriorityCompoundCancellableRunnable.doWork(PriorityCompoundCancellableRunnable.java:144)
 at com.businessobjects.crystalreports.designer.core.util.thread.AbstractCancellableRunnable.run(AbstractCancellableRunnable.java:69)
 at com.businessobjects.crystalreports.designer.core.util.thread.ExecutorWithIdleProcessing$IdleTask.run(ExecutorWithIdleProcessing.java:320)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Thanks
Karthik
Edited by: KARTHIK1 on Oct 14, 2009 9:38 PM

Hi Ted,
Thanks for the feedback. I was able to create a report in Creystal Reports Designer 2008 using OCI. It is not allowing only in the Eclipse plugin. In our environment we are not allowed to user Oracle thin connections and ONLY OCI is allowed.
1) Can you please let me know if there is a way to do this?
2) Will it allow data sources using native database driver?
3) If so, can I use JRC to create these reports from a desktop java program?
Thanks & Regards
Karthik
Edited by: KARTHIK1 on Oct 15, 2009 4:38 PM

JDBC connection pool failures when used by JMS stores

 We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
 a JMS Store.
 <JDBCConnectionPool Name="sybaseJMSPool"
 Targets="cluster00"
 InitialCapacity="2"
 MaxCapacity="10"
 DriverName="com.sybase.jdbc2.jdbc.SybDriver"
 Properties="[email protected]@;[email protected]@;charset=utf8"
 URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
 (note that the @xxx@ string are replaced by actual values).
 We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
 We deployed this configuration on a number of environments (testing, staging,
 ..). The actual hardware and network configuration is different for the different
 system, but the WebLogic domain stays the same regarding this issue.
 On the test system we frequently get the following exceptions:
 <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
 <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
 <JMSServer "JMSServer00", store failure while writing message for topic
 OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
 <sybaseJMSPool>, prefix = <JMS00>: write failed
 java.sql.SQLException: JZ006: Caught IOException:
 com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
 closed.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
 (ErrorMessage.java:715)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
 at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
 (SybStatement.java:1625)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
 (SybPreparedStatement.java:91)
 at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
 (P6LogPreparedStatement.java:179)
 at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 .>
 java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
 = <JMS00>: write failed
 java.sql.SQLException: JZ006: Caught IOException:
 com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
 closed.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
 (ErrorMessage.java:715)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
 at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
 (SybStatement.java:1625)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
 (SybPreparedStatement.java:91)
 at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
 (P6LogPreparedStatement.java:179)
 at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 at weblogic.jms.store.JDBCIOStream.throwIOException
 (JDBCIOStream.java:1213)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 Before that this message appeared:
 <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
 <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
 <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
 received a message over an uninitialized connection: 'JVMMessage from: 'null'
 to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
 1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
 invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
 offset: '34'''>
 This problem did not occur on another system which was used during a 2 day stress
 testing session.
 It seems that the problem occurs after a period in which no user request where
 made. The user requests trigger EJB's that start sending JMS messages.
 When the problem occurs, the JMS messaging systems seems to lock up as no messages
 are received anymore by the different listeners (MDBs).
 Undeploying and redeploying the JBDC connection pool solves the problem. This
 solution is unacceptable in case of a production system.
 A similarly defined connection pool, which is used by the EJBs to make database
 connection, does not manifest this problem.
 <JDBCConnectionPool Name="sybasePool"
 Targets="cluster00"
 InitialCapacity="10"
 CapacityIncrement="5"
 MaxCapacity="50"
 PreparedStatementCacheSize="150"
 DriverName="com.sybase.jdbc2.jdbc.SybDriver"
 Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
 URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
 The JDBC connection pool is used as follows by the JDBC store
 <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
 <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
 <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
 <JMSTopic JNDIName="ADIS.Status"
 Name="StatusTopic" RedeliveryDelayOverride="300000"/>
 <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
 Name="OrderChangeTopic" RedeliveryLimit="3"/>
 </JMSServer>
 Turning on the "Test Reserved Connection" with a appropriate test table does not
 help.
 Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
 can be related to network problems. Nevertheless the connection pool should be
 able to cope with this.
 Can you provide any solution for this ? Or give us hints what can cause the problem


Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe

How to configure JDBC connection in oracle BI publisher with teradata datab

Hi,
I am going to use Oracle BI publisher to create report.
Our database is Teradata.
How to create database connection for Teradata in BI publisher.
How to create JDBC connection.
What should be the Database Driver Class?
What should be the connection string format?
Please provide me the suggetion.
Thanks,
Santanu Manna

Hi;
I suggest please refer below which could be helpful on your issue:
How To Generate XML Output (Excel, HTML, PDF) for FSG Reports [ID 804913.1]
E-XMLP: BI Publisher Report RTF Template to Excel output is not same as PDF,RTF or HTML format.[Article ID 1515711.1]
BI Publisher Enterprise Excel Output File Size is Too Large [ID 1271544.1]
Regard
Helios

ADF: Gracefully handling JDBC connection errors?

Hi gang
We've a use case to display a specific web page when the JDBC connection drops out on our ADF application, specifically the following error:
oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
I've been researching solutions to this and came up with a near solution of placing the following entry in the application's web.xml file:
<error-page>
<exception-type>oracle.jbo.DMLException</exception-type>
<location>/MyErrorPage.jsp</location>
</error-page>This works okay but is a blunt mechanism as it captures all DMLExceptions which includes insert/update/delete failures, as well as the JDBC connection drop out.
Has anybody come up with a better solution for handling JDBC connection drop outs?
Thanks & regards,
CM.
PS. (JDev 11g build 5188, ADF BC + ADF Faces RC)

Thanks John, that's the solution. For some reason I'd forgotten that DCErrorHandlerImpl exists in the controller layer, not the model layer, so it makes perfect sense to override it and do the redirect.
Here's what I came up with:
@Override
public void reportException(DCBindingContainer dCBindingContainer,
 Exception exception) {
 try {
 String message = exception.getMessage();
 if (message.indexOf("JBO-26061") >= 0) {
 FacesContext.getCurrentInstance().getExternalContext().redirect("faces/ErrorPageJDBCFailure.jspx");
 } else
 super.reportException(dCBindingContainer, exception);
 } catch (IOException e) {
}The following OTN post shows some other methods to do the redirect: JSF forward Vs redirect
Cheers!
CM.

JDBC Connection in ISA 7.0

Hi,
Where can we set JDBC connection for local SAP-J2EE DB for ISA 7.0.
Please provide some information.
Regards,
Devender V

The default connections are preconfigured for Web Channel applications.
The actual resource references are made in web.xml
 
 <resource-ref>
 <res-ref-name>SAP/CRM/b2b</res-ref-name>
 <res-type>javax.sql.DataSource</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 
 <resource-ref>
 <res-ref-name>jdo/defaultPMF</res-ref-name>
 <res-type>javax.resource.cci.ConnectionFactory</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
This res-ref-name> is the alias of the JDBC Datasource.
You can find the JDBC connection / aliases either using Visual Admin or NWA Hope you know how to lausch them. I will explain this in Visual Admin.
After launching Visual Admin, go to Server -> Services -> JDBC Connector of the Cluster in the navigator panel. After that in the working panel, expand Data Sources in Resources. You will find the default data source SAP<instance>DB . If you select this Data source, the details are shown.
When you install the J2EE engine, the passwords of the JDBC data source SAP<instance>DB is requested and stored in the and can be managed using the Config Tool. Here you can change the default user, password, connection-string (URL) and the driver.
You can create a new alias if you want in the J2EE engine, but you have to diligently integrate it to your web application resource to use it in the application.
Easwar Ram
http://www.parxlns.com

APEX fails with Java stored procedure that creates a JDBC connection

Hello!
We are facing a strange problem since we have upgraded from Oracle 10g and Apache to Oracle 11g with Embedded Gateway.
Here is what we do:
** APEXX calls a PL/SQL package function "OPEN_CONNECTION" that wraps a Java stored procedure called "openConnection".*
FILE_READER_REMOTE_API.openConnection(user, password, host, port, service);
** The Java stored procedures "openConnection" opens a JDBC connection to an other database:*
public class FileReaderRemote {
private static Connection conn = null;
private static DefaultContext remoteContext = null;
public static void openConnection(String user, String password, String host, String port, String service) throws SQLException {
// Load the Oracle JDBC driver
DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
java.util.Properties props = new java.util.Properties();
props.put ("user", user);
props.put ("password", password);
//props.put ("database", "//" + host + ":" + port + "/" + service);
props.put ("database", host + ":" + port + ":" + service);
props.put("v$session.program", "FileReaderRemote2");
// Connect to the database
remoteContext = Oracle.getConnection("jdbc:oracle:thin:", props);
This procedure used to work fine before the upgrade, but now we see the following:
* It still works when called directly from TOAD or SQL*Plus, even under the user ANONYMOUS.
* When called from APEX and the target database is Oracle 11g, it still works.
* When called from APEX and the target database is Oracle 10g, it takes several minutes and we receive this error:
*"Socket read timed out"*
We have tested the following workaround:
We have created a database link to our own database and called the stored procedure through that database link.
FILE_READER_REMOTE_API.openConnection*@loopback*(user, password, host, port, service);
This works, but is not really an option.
I hope some one of you can explain this strange behaviour to me.
Best regards,
Matthias

You wrote
"Java stored procedures -- by definition - are stored in the 8i rdbms. !!"
From the Oracle8i Java Stored Procedures Developer's Guide
Release 8.1.5
A64686-01
"If you create Java class files on the client side, you can use loadjava to upload them into the RDBMS. Alternatively, you can upload Java source files and let the Aurora JVM compile them. In most cases, it is best to compile and debug programs on the client side, then upload the class files for final testing within the RDBMS"
This means that you can create shared classes that are used on both the client and server side. The source does not need to reside within the server (according to their documentation). Please also note the following from the Oracle8i JDBC Developer's Guide and Reference Release 8.1.5 A64685-01 for using the getConnection() method on the server:
"If you connect to the database with the DriverManager.getConnection() method, then use the connect string jdbc:oracle:kprb:. For example:
DriverManager.getConnection("jdbc:oracle:kprb:");
Note that you could include a user name and password in the string, but because you are connecting from the server, they would be ignored."
So if you're coding a shared class that is to run on both the client and server side, you might do something like this:
Connection conn =
DriverManager.getConnection(
System.getProperty("oracle.server.version") == null
? "jdbc:oracle:thin:@hostname:1521:ORCL"
: "jdbc:oracle:kprb:"),
"youruserid","yourpassword");
As stated earlier, the userid and password are supposedly ignored for server connections retrieved in this manner. I haven't tried this yet, but it is documented by Oracle.
Regards,
Steve
null

Interrupt method + JDBC connections

Hi all
 
Obviously I have a problem with the above :)
Briefly:
 
- I have a thread that does some things (long operations) and writes results into database
 
- The main thread has an option to cancel (using interrupt method) the thread on user's request
 
but when I invoke that interrupt method it obviously stops the thread, stops the statement running, takes me to the catch block shown below, but when I try to create a new JDBC connection in that block, I get the exception:
 
Io exception: The Network Adapter could not establish the connection 
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180) 
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222) 
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:335) 
 at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:361) 
 at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:442) 
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:321) 
 at java.sql.DriverManager.getConnection(DriverManager.java:525) 
 at java.sql.DriverManager.getConnection(DriverManager.java:171) 
 
In other words I am not able to rollback what has been done so far!
 
I just have to also say that I am using connection pooling and the "long operation" consists of many smaller ones. They all use database. It is a one tree-like process and I can't use just one connection for the whole thing to make it more simple.
 
<code>
run() 
{ 
try 
{ 
//long operation/transaction here 
... 
} 
catch (Exception e) 
{ 
//do some rollback operations corresponding to 
//the above transaction's progress 
} 
} 
</code>
 
So, can anyone tell me please, what am I doing wrong or is there any workaround for that?
 
Regards 
Thomas
 
Message was edited by: 
hrabiatc
Message was edited by:
hrabiatc

Good descriptions at:
http://www.java.sun.com/products/jdbc/driverdesc.html

Open/total jdbc connections

With Oracle9iR2 AS installed, I notice that there are always open JDBC connections. I explicitly close them from all my JSP files (and the statement and the resultset objects as well). Actually, the total JDBC connections are always 2 times the open JDBC connections.
The DataSource class I use is com.evermind.sql.DriverManagerDataSource. Is this a problem? Will this be corrected in any future release?
Thanx

Interesting thread. Have also had problems with the connection pool (903 standalone).
One problem in particular is that if min-connections is used, then those pool-connections are really never closed "physically". This means that a lot of open cursors are never released in the db (even though the "connections" used by the code from the pool are closed). Not so good under heavy load.
Posting a snippet from a connection pool entry we have. Maybe it will help some of you guys.
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="SomeDS"
location="jdbc/SomeDBCoreDS"
xa-location="jdbc/xa/SomeDBXADS"
ejb-location="SomeDB"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="user"
password="pwd"
url="jdbc:oracle:thin:@127.0.0.1:1521:SOMESID"
inactivity-timeout="300" <-- Will close connections after 300 sec of inactivity
min-connections="0"
max-connections="20" <-- Larger on prod machine of course
stmt-cache-size="100"
/>
I have experimented wildly with these settings and this is the most stable. Sure, it's nice to always have connections ready in the pool. But as I said. Open cursors WILL accumulate in your db if you use the min-connections set to a positive number (check your v$). This is our experience anyway. These settings have stopped us from getting db errors such as maximum open cursors exceeded and too many connections open using 903.
Regards,
Jonas

JDBC connection pool getting killed in Managed Server

I am running a managed server in a Windows2000 SP2,WebLogic 6.0 SP2, JDK 1.3.1_01
environment
When I start the managed server I get the following error:
Attempting to create Connection Pool for the Pool Registry Entry : perfectFitPool
<Nov 24, 2001 9:03:15 PM EST> <Error> <JDBC Connection Pool> <The pool 'perfectFitPool
was created successfully. But it must be killed because of: creating Admin MBean
on a managed server>
weblogic.common.ResourceException: creating Admin MBean on a managed server
at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:540)
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:766)
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:754)
at ConnectionPoolStartupWl6.createDynamicConnectionPool(ConnectionPoolStartupWl6.java:64)
at ConnectionPoolStartupWl6.startup(ConnectionPoolStartupWl6.java:45)
at weblogic.t3.srvr.StartupClassRunner.invokeStartup(StartupClassRunner.java:112)
at weblogic.t3.srvr.StartupClassRunner.invokeClass(StartupClassRunner.java:93)
at weblogic.t3.srvr.StartupClassRunner.run(StartupClassRunner.java:61)
at java.lang.Thread.run(Thread.java:484)
<Nov 24, 2001 9:03:15 PM EST> <Critical> <WebLogicServer> <Failed to invoke startup
class
"ConnectionPoolStartupWl6", weblogic.common.ResourceException: creating Admin
MBean on a managed server>
<Nov 24, 2001 9:03:15 PM EST> <Notice> <WebLogicServer> <WebLogic Server started>
Any idea on what could be wrong.
Thanks in advance,
Adarsh Ronald

Hi Adarsh,
You can not create Admin MBean on managed server. Managed server can
have only cached copies of Admin MBeans with type ConfigMBean.
Could you show us what you do @ ConnectionPoolStartupWl6?
Regards,
Slava Imeshev
"Adarsh Ronald" <[email protected]> wrote in message
news:3c0054eb$[email protected]..
>
I am running a managed server in a Windows2000 SP2,WebLogic 6.0 SP2, JDK1.3.1_01
environment
When I start the managed server I get the following error:
Attempting to create Connection Pool for the Pool Registry Entry :perfectFitPool
<Nov 24, 2001 9:03:15 PM EST> <Error> <JDBC Connection Pool> <The pool'perfectFitPool
was created successfully. But it must be killed because of: creating AdminMBean
on a managed server>
weblogic.common.ResourceException: creating Admin MBean on a managedserver
atweblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java
:540)
atweblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:
766)
atweblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:
754)
atConnectionPoolStartupWl6.createDynamicConnectionPool(ConnectionPoolStartupWl
6.java:64)
at ConnectionPoolStartupWl6.startup(ConnectionPoolStartupWl6.java:45)
atweblogic.t3.srvr.StartupClassRunner.invokeStartup(StartupClassRunner.java:11
2)
atweblogic.t3.srvr.StartupClassRunner.invokeClass(StartupClassRunner.java:93)
at weblogic.t3.srvr.StartupClassRunner.run(StartupClassRunner.java:61)
at java.lang.Thread.run(Thread.java:484)
<Nov 24, 2001 9:03:15 PM EST> <Critical> <WebLogicServer> <Failed toinvoke startup
class
"ConnectionPoolStartupWl6", weblogic.common.ResourceException: creatingAdmin
MBean on a managed server>
<Nov 24, 2001 9:03:15 PM EST> <Notice> <WebLogicServer> <WebLogic Serverstarted>
>
Any idea on what could be wrong.
Thanks in advance,
Adarsh Ronald

Weblogic 8.1 SP 3 JDBC Connections

Hi,
We have configured JDBC connection pool size with initial 1, increment 1 and max is 15. We are experiencing slow performance with app sometimes. Some select and update operations taking more than 60 secs which usually takes about 15 secs.
I monitered the app during slowness and there were 3 users using the app that time. And application lost the connection with exchange server. The number of active connections in weblogic console were 4 and 5 sometimes. But when I checked with SQL Server DBA he saw 8 connections coming from application. Is there any possibility that the connections established before were not cleaned causing for this slowness.
When we bounce weblogic server it starts working fine as normal.
Does anyone experienced similar problem? I appreciate if anyone can help me in this.
Thanks,
Mahesh

Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
Regards.

Two jdbc connections in one transaction

Hi 
 
 In a method of a container managed ejb session bean I have two jdbc connections. I've expected, that they will be in the same transaction, so results of any actions performed with first connection will be visible for the second connection, but it is not. 
 I've checked, that there are two sessions at the database, so it seams that there are simply separate transactions. Is it a problem with a ejb-jar.xml (will paste it later), datasource (driver - Oracle Thin non-XA; 1PC selected) or such behaviour can not be achieved in WLS ? 
 
 regards
 
 <?xml version="1.0" encoding="UTF-8"?>
 
 <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
 
 <ejb-jar >
 
 <description><![CDATA[No Description.]]></description>
 <display-name>ConnectionTest1</display-name>
 
 <enterprise-beans>
 <session >
 <description><![CDATA[]]></description>
 
 <ejb-name>ConnectionTest1</ejb-name>
 
 <home>pl.axit.test.ConnectionTest1Home</home>
 <remote>pl.axit.test.ConnectionTest1</remote>
 <ejb-class>pl.axit.test.ConnectionTest1Bean</ejb-class>
 <session-type>Stateless</session-type>
 <transaction-type>Container</transaction-type>
 
 <resource-ref >
 <res-ref-name>jdbc/wowrite</res-ref-name>
 <res-type>javax.sql.DataSource</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 </session>
 </enterprise-beans>
 
 <assembly-descriptor>
 <container-transaction>
 <description/>
 <method>
 <description/>
 <ejb-name>ConnectionTest1</ejb-name>
 <method-name>*</method-name>
 </method>
 <trans-attribute>Required</trans-attribute>
 </container-transaction>
 
 </assembly-descriptor>
 </ejb-jar>

Hi,
 are you using XA transactions? Two separate JDBC Connections treated
 within one transactional context will require two phase commit (via
 Emulation or an XA database driver) Please check the connections
 settings within your datasources.
 Rgds,
 Axel van Lil (LMIS.de)
 Lukas Uruski schrieb:
 > I forgot to add, that in administration console in server_name > Monitoring > JTA parameter "Transactions Total Count" increases by one each time method from previous post is invoked.

Configuring RAC-aware JDBC connection in Oracle SQL Developer?

How can Oracle SQL Developer be configured to properly connect to an [Oracle RAC|http://en.wikipedia.org/wiki/Oracle_RAC] environment, I.E., not just setup to always connect to one of the individual nodes?
[http://programmersjournal.blogspot.com/2008/08/jdbc-connection-string-for-oracle-rac.html] has an example of a classic and the equivalent RAC-aware version of a JDBC connection string. I've already been using a RAC connection string of the same format from within custom Java applications without issue. I thought the same should be configurable in Oracle SQL Developer by setting the "Connection Type" drop-down to "Advanced", then entering the RAC-aware JDBC connection string as the "Custom JDBC URL". However, upon testing the connection, the following error is displayed at the bottom of the dialog:
Status : Failure -Test failed: Io exception: NL Exception was generated
There is no additional information shown on the "Logging Page" view. Using Oracle SQL Developer 1.5.5.
Thanks!

Thanks, Barry. Just F.Y.I., it is working for me now that I upgraded to the 2.1 EA as -K- suggested. I had marked his reply as "Correct", but probably should have left a response indicating my success as well.
Now, if there's anything you could do regarding the [issues around the display performance of CLOBs, etc., in the Query Result view|http://forums.oracle.com/forums/message.jspa?messageID=3906571] , it'd be very appreciated!

Cannot commit or rollback a JDBC Connection from CAF project

Hi Everybody,
I'm working in CE 7.10. I have a CAF Project that gets a JDBC connection from a Custom Datasource to an external Database.
Here is the code:
try
    Context ctx = new InitialContext();
    DataSource ds = (DataSource) ctx.lookup("jdbc/MYDATABASE");
    con = ds.getConnection();
    con.setAutoCommit(false);
    Statement statement = con.createStatement();
    String updateStatement = "UPDATE TABLE...";
    statement.executeUpdate(updateStatement);
    con.commit();
    catch(SQLException sqle){
         con.rollback();
I got the following exception on line "con.setAutoCommit(false);": --> "Cannot begin JDBC transaction from this connection of "MYDATABASE" DataSource. JTA transaction has already started."
and the following on line "con.commit() / con.rollback()" : --> "Cannot commit JDBC transaction from this connection of "MYDATABASE" DataSource. This resource participates in a JTA transaction."
If I run the same code from a webDynpro or a J2EE project it works ok, but not from a CAF Application Service. I tried to do it in a simple Class in the CAF Project and call this clas from the Application service, but I get the same error.
Any Ideas??
Thanks a lot!
Regards.

Solved with   "SessionContext.setRollbackOnly()" instruccion.
Regards.

Regarding JDBC Connectivity

Similar Messages

Maybe you are looking for