CachedRowSetImpl.acceptchanges(con) don't release the connection

Hi all,
i've have this problem using the CachedRowSetImpl tecnology.
this is my code:
CachedRowSet TargetTableCursor= new CachedRowSetImpl();
...I populate the cursor...
...I update the cursor
...I retrieve the connection con accros a poolconnection object
...I update to the Database with the following istructions
TargetTableCursor.acceptChanges(con);
con.close();
at this point, the object con (the connection) it does not come destroyed.
someone has an idea about this?
thanks
Emiliano

Hi,
It looks like you have some "wrong" concepts.
First you say that:
Now in WS1, there is no schema
later on you are telling
have then check the command
select * from SAPBOS.SVERS and it worked.
So, do you have a schema or don't you?
Let me try to understand what you have done, for your description
1) you have a system called BOS. On this system you have a schema called SAPBOS.
2) you did a system copy from BOS to W1S. Guessing -> You did a restore from a BOS
Now your SAPW1S has "dissapeared"
am I understandin it properly?
If so, you should think a little.
You have restored a backup from BOS ( DB name BOS, SCHEMA BOS, tablespace names PSAPBOS ) into W1S
Restoring a backup will not change the schema name ( AFAIK, there is no simple way of doing so )
Restoring a backup will not change the tablespaces names ( in Oracle 10g you can do this, but has to be done manually )
Restoring the backup will not change the DB name. The System copy procedure ask you to create a script that will perform this last change.
So, at the end of the process you have a DB called W1S, with a schema called SAPBOS and tablespaces called PSAPBOS.
As mentioned before there is no simple way of changing the schema name.
If you need/want/desire to do so then you cannot use BACKUP/RESTORE for system copies. You must use the R3Load method ( take all data out of the DB and then take all the data in on the new system )

Similar Messages

Oci_close does not release the connection when using DRCP

Hello everyone,
we are currently testing the deplyment of DRCP with 11g. I have the whole thing setup (correctly to my best knowledge), but I am facing an issue. The call to oci_close does not seem to release the connection to the pool as I would expect and therefore we see similar behavior like we were getting without using the DRCP.
Our setup is using two RAC instances running 11.1.0.6.0, I am using PHP 5.1.6 with PECL installed oci8 1.3.4. The DRCP pool is configured and started, each with 100 max servers.
When the webserver is idle it looks, well, idle.
SQL> SELECT INST_ID,NUM_BUSY_SERVERS FROM GV$CPOOL_STATS;
INST_ID NUM_BUSY_SERVERS
1 0
2 0
The script is as simple as it gets:
<?php
$c = oci_pconnect('scott','tiger','IWPPOOLED');
$s = oci_parse($c, 'select * from emp');
$r = oci_execute($s, OCI_DEFAULT);
oci_close($c);
sleep(30);
?>
What I would expect is that the script would connect to the pool, do the work for a tiny moment and then release the connection for usage by other script.
But after I point the browser to the script, I get a 30 second loading time (as expected) but the server is busy all the time, like this:
SQL> SELECT INST_ID,NUM_BUSY_SERVERS FROM GV$CPOOL_STATS;
INST_ID NUM_BUSY_SERVERS
1 0
2 1
After the 30 second sleep, it is released and busy servers are back to 0.
If I load the server with ab using 256 connections:
ab -n 1000000 -c 256 -k http://mywebserver/ocitest.php
the pool is maxed out and the connects are stalling:
SQL> SELECT INST_ID,NUM_BUSY_SERVERS FROM GV$CPOOL_STATS;
INST_ID NUM_BUSY_SERVERS
1 95
2 95
My network config for this service is following:
IWPPOOLED =
(DESCRIPTION =
(LOAD_BALANCE=ON)
(FAILOVER=ON)
(ADDRESS = (PROTOCOL = tcp)(HOST = 10.1.16.33)(PORT = 1521))
(ADDRESS = (PROTOCOL = tcp)(HOST = 10.1.16.34)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = IWP)
(SERVER=POOLED)
(FAILOVER_MODE=
(TYPE=SELECT)
(METHOD=BASIC)
(RETRIES=5)
(DELAY=3)
The phpinfo() look like this:
OCI8 Support enabled
Version 1.3.4
Revision $Revision: 1.269.2.16.2.38.2.20 $
Active Persistent Connections 1
Active Connections 1
Oracle Instant Client Version 11.1
Temporary Lob support enabled
Collections support enabled
Directive Local Value Master Value
oci8.connection_class IWPAPP IWPAPP
oci8.default_prefetch 100 100
oci8.events On On
oci8.max_persistent -1 -1
oci8.old_oci_close_semantics Off Off
oci8.persistent_timeout -1 -1
oci8.ping_interval -1 -1
oci8.privileged_connect Off Off
oci8.statement_cache_size 20 20
I am using the instant client for 11g
Any ideas?
Thanks!
Michal

Don't forget to use oci_free_statement($s); See "Closing Oracle Connections" in The Underground PHP and Oracle Manual. (I was just simplifying this example today for the next release of the manual).
You may also see the "dedicated optimization", where a pooled server in a non- maxed-out pool is retained (unless needed by another PHP process) under the assumption that the initial PHP process might become active again. See http://www.oracle.com/technology/tech/php/pdf/php-scalability-ha-twp.pdf
Feel free to email me offline (see my profile) if there are questions/data you don't want to post.
cj
Edited by: cj2 on Oct 16, 2008 8:12 AM

Release the connection in JMS Adapter

Hi,
I’m sending the message to JMS queue (queue is running in weblogic server) using JMS Adapter in BPEL. My question is how to release the weblogic connection once the message produced to queue. It is happen automatically or we have to release the connection explicitly. If it explicit handle means how to do it?
It would very helpful for me if you send any reference doc or url about this.
Thanks in Advance.
Thanks
Chandramohan

The JMS adapater of SOA will handle this for you. You do not have to do anything with closing connections.
Marc

Does transaction manager also releases the connections ?

Hi All,
I've a doubt regarding release of connection in transaction handling scenarios in EJB.
Let us assume I have an EJB method associated with a transaction attribute as Requires New (i.e. the ejb method is associated with container managed transaction).
Within that method two diffreent databasess are accessed, connections are created, databases are updated but connections are not realeased.
The code goes similar to the one given below -
public void beanMethod1()
InitialContext cntx = new InitialContext();
javax.sql.DataSource ds1 = cntx.lookup("dataSourceName1");
javax.sql.DataSource ds2 = cntx.lookup("dataSourceName2");
java.sql.Connection conn1 = ds1.getConnection();
ds1.setAutoCommit(false);
PreparedStatement pst1 = ds1.prepareStatement("Qyery1");
pst1.executeUpdate();
java.sql.Connection conn2 = ds2.getConnection();
ds2.setAutoCommit(false);
PreparedStatement pst2 = ds2.prepareStatement("Qyery2");
pst2.executeUpdate();
Now in this context my doubt is - will the transaction manager, along with handling commit/rollback, release the connections also (once commit/rollback is over) ? Or releasing of connections need to be handled in the bean method ?
If releasing connections has to be handled in the bean method, then how does transaction manager execute a commit/rollback on a released connection ?
The same doubt can be extended to bean managed transaction also where transaction boundarry is demarcated using javax.transaction.UserTransaction object's begin(), commit() and rollback() methods.
It will be a real help if anyone please throw some light on this doubt.
Thanks in advance,
Sourav

Hi,
Your code needs to release (i.e., close) the connections it uses; this is outside the TM responsibility scope.
The commit or rollback is not a problem, because the corresponding XAResource (which is the
transaction manager's handle to your connection) can be used even after your connection
has been closed in the application code. That is the catch about XA, and it allows the whole
mechanism of connection pooling and DataSources to work properly.
Hope that helps,
Guy

EJB3 : suspend JTA transaction does not release the connection in the XA DS

Hi all,
I did a test and after suspending a JTA transaction I note that in the xa datasource the activeconnection = 1.
So is it normal because I was thinking that when I suspend the transaction the teh connection is released and then after a transaction resume I could continue the transaction with another connection of the xa datasource ?
Thank you for all..
Christophe.

It's a long time ago, but did you ever solve this problem?
I'm having the same issue with OSB writing to a WLS8.1 JMS queue.
I have a development OSB server which works fine.
Pete

CUCM unexpectedly release the connect

Can anyboydy give a hint ?
I have an Avaya - Cisco 2901 -CUCM H323 connection.
If i ring from outside to local phone then call dropped after 5 sec. In the h225 log i see following sequence :
(VG -> CUCM) SETUP
(VG -> CUCM) CALL_PROC
(VG <- CUCM) ALERTING
(VG <- CUCM) NOTIFY
(VG <- CUCM) CONNECT
(VG <- CUCM) NOTIFY
(5 sec wait)
(VG <- CUCM) RELEASE
If I call from local to outside then connection established and called party picks up the phone, but calling party doesn't get any sign of that.
What can cause the problem ?

Can anyboydy give a hint ?
I have an Avaya - Cisco 2901 -CUCM H323 connection.
If i ring from outside to local phone then call dropped after 5 sec. In the h225 log i see following sequence :
(VG -> CUCM) SETUP
(VG -> CUCM) CALL_PROC
(VG <- CUCM) ALERTING
(VG <- CUCM) NOTIFY
(VG <- CUCM) CONNECT
(VG <- CUCM) NOTIFY
(5 sec wait)
(VG <- CUCM) RELEASE
If I call from local to outside then connection established and called party picks up the phone, but calling party doesn't get any sign of that.
What can cause the problem ?

LMS 4.2 is not releasing SSH connections of the devices

Hello!
We have LMS opens SSH sessions to Nexus 5000 devices as part of some jobs.
These SSH connections are not being released by LMS as soon as jobs are completed, which leads the N5K devices to hang without any way of managing them remotely.
We see these connections as idle on the nexus devices (which also should kill these sessions, but this is not the issue).
We have found a known bug:
CSCty90928
LMS Pari jobs are not releasing SSH,telnet connections of the devices
Symptom:
Telnet/SSH connections are not released by LMS
Conditions:
Pari collections jobs are not releasing the connections after the Job completed
Workaround:
None
This bug is categorized as "2 – severe" and is in "Open (Postponed)" status.
I have a few questions, if anyone can assist:
1.) What is the ETA to fix this bug?
2.) Are there any other known bugs matching what we see (documented public bugs, with bug ID's, internal bugs or even undocumented bugs).
3.) Is there any released or unreleased (even yet to be tested by TAC) patch we can use that should fix the issue?
4.) Is there any way to adjust LMS idle timeout of SSH/Telnet sessions (I couldn't find it in the GUI, but maybe there is a way to change this parameter using a perl script or modifying one of LMS properties files)?
Thanking in advance, Udi Dahan.

Hello Ehud
From N5k side we have submitted bug CSCty00044
Currently there is no fix for it and our debelopment team is catively working on it and investigating the issue in the lab.
To get ETA for the release I would suggest you reach your account team and check with them how fast fixed release will be available.
HTH,
Alex

Difference between closing the connection before and after committing user transaction?

          I was wondering what's the difference between closing the connection before committing
          the transaction versus closing the connection after committing the transaction?...
          for e.g....
          Scenario 1.........
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          conn.close();
          usertran.commit()
          Scenario 2...
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          usertran.commit()
          conn.close();
          thanks....
          Srini


Hi. As long as you're sure there's a transaction going on, and the connection
is a transaction-aware object (from a TxDataSource), either will be fine.
In the first scenario the actual semantics of the close() call are less than
normal, because we really don't close the connection or return it to the
pool until the actual transaction commits, and in the second case, we have
already taken the connection out of your service as of the commit().
The second scenario is the usual coding style. If there's ever a chance your
code will get non-transaction-aware connections, it is crucial to close
connections, and I always recommend putting the close() in a finally block
so it's guaranteed to happen.
Joe
srinivas wrote:
I was wondering what's the difference between closing the connection before committing
the transaction versus closing the connection after committing the transaction?...
for e.g....
Scenario 1......... UserTransaction useretran; usertran.begin(); Connection con =
datasource.getCOnnection(); // do bunch of stuff... conn.close(); usertran.commit()
Scenario 2... UserTransaction useretran; usertran.begin(); Connection con = datasource.getCOnnection();
// do bunch of stuff... usertran.commit() conn.close();
thanks....
Srini

MAX don't release LAN connction while communicating with Agilent 86122A

Dear guys,
Yesterday I met a communication issue while talking to Agilent 86122A via LAN.
It showed I cannot run MAX before launching LabVIEW; otherwise I'd have trouble in send commands in LabVIEW.
I doubt if MAX MAX don't release LAN connection while communicating with Agilent 86122A?
Please advise,thanks.
I debugged as below:
1, Ping the IP of Agilent 86122A shows internet is OK.
2, I restarted the instrument, LabVIEW reported the same error code.
3, I restarted PC, launched LabVIEW first and run the code (*IDN?), everything is OK!!!
4, Again, I send *IDN? With MAX, and it seemed to be OK.
5, hit x to close MAX and then run the same and simple code (*IDN?) in LabVIEW, but it reports error code -1073807346.

Caglar,
The documents you mention ahould include the proper prcedure for using this hardware in LabVIEW. Here are my recommendations:
The version of NI-VISA you mentioned is not valid. The most recent version is 4.6.2. I would recommend ugrading if you do not have this version. After the upgrade,ensure that tulip is enabled as well as the other settings and see if this helps.
When talking about the instrument, the biggest concern that usually is relevant with 488.1 is that it will not respond to *IDN?. In your case, it looks like it does, and should work as 488.2 is backwards compatible. It seems to me, the issue is still with the 82357A, and we have not yet reached the voltmeter.
In order for NI-VISA to work with your device, NI-VISA must be the primary visa driver.
Hope this helps, let us know how the upgrade turns out. If you continue to have issues, take some screenshots of the preferences in MAX and upload them on the forum.
Regards,
Peter Flores
Applications Engineer

Release jms connection doesn?t release.

 Hi All,
 Environment: WLS 7.0sp2, JMS: weblogic JMS JMSJDBCStore, database oracle9
 We invoke the following sendEvent code from a worker thread invoked by a scheduler
 that was started in a servlet init method (this worker thread code is wrapped
 with a user tx).
 The topic’s MDB is getting the message OK, however the number of connection in
 the monitor (mydomain> JMS Servers> NomJMSServer> Active JMS Servers) keep growing.
 As you can see we are releasing the connection in a finally block. Can anybody
 explain it.?
 Second question: Should we cache the jms session? If the answer is yes, can they
 expire (close), how do we check if they are still valid?
 Thanks
 public String sendEvent(SyncOutput event)
 String retval = null;
 try
 init();
 topicPublisher.publish( formatMessage(event) );
 catch (Exception e)
 logger().debug("cannot send event", e);
 }finally{
 release();
 return retval;
 private Message formatMessage(SyncOutput output)
 throws JMSException, IOException
 BytesMessage message = topicSession.createBytesMessage();
 GZIPOutputStream gzip = new GZIPOutputStream(new BytesMessageOutputStream(message));
 output.flush(new OutputStreamWriter(gzip));
 gzip.close();
 return message;
 private void init()
 throws Exception
 InitialContext context = new InitialContext();
 TopicConnectionFactory conFactory =
 (TopicConnectionFactory) context.lookup(JMSConfig.get(JMSConfig.FACTORY));
 topicConnection = conFactory.createTopicConnection();
 topicSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
 Topic topic = (Topic) context.lookup( this.jndiName );
 topicPublisher = topicSession.createPublisher(topic);
 topicPublisher.setDeliveryMode( DeliveryMode.PERSISTENT );
 private void release()
 try{
 if (topicPublisher != null){
 topicPublisher.close();
 topicPublisher = null;
 if (topicSession != null){
 topicSession.close();
 topicSession = null;
 if (topicConnection != null) {
 topicConnection.close();
 topicConnection = null;
 System.gc();
 }catch(Exception ignore){
 ignore.printStackTrace();


 We found the problem, it was a bug in our code. Thanks for your help.
 Tom Barnes <[email protected]> wrote:
 >Its possible the monitor has a bug, but in your case, since
 >you now only create one connection how could the
 >connection count keep growing?
 >
 >Perhaps the MDB app or MDB container is failing in some
 >unexpected way and not
 >closing its connection before attempting to create a new one?
 >Check your log for warnings and error messages, and
 >consider encapsulating your onMessage() code with a
 >try { /* all onMessage code */ }
 >catch (Throwable t) { t.printStackTrace(); rethrow}
 >
 >Meir wrote:
 >> Is it possible that the monitor has a bug? I changed my code to cache
 >the topic
 >> session and topic publisher, so I always use the same one (they are
 >static members
 >> of the class) but this didn't change the result that I'm seeing in
 >the monitor
 >> - the number of connections still keep growing.
 >> Could it be TX related weirdness (note we set the factory "User Transactions
 >Enabled"
 >> attribute to true)?
 >>
 >>
 >> "Meir" <[email protected]> wrote:
 >>
 >>>Thanks for your quick response.
 >>>I cahnged the code to catch throwable (both the open and close connection
 >>>are
 >>>in the try/catch block) and I don't see any problems.
 >>>Do you have any other suggestions? Do you need more data?
 >>>
 >>>
 >>>Tom Barnes <[email protected]> wrote:
 >>>
 >>>>
 >>>>Meir wrote:
 >>>>
 >>>>
 >>>>>Hi All,
 >>>>>
 >>>>>Environment: WLS 7.0sp2, JMS: weblogic JMS JMSJDBCStore, database
 >>>>
 >>>>oracle9
 >>>>
 >>>>>We invoke the following sendEvent code from a worker thread invoked
 >>>>
 >>>>by a scheduler
 >>>>
 >>>>>that was started in a servlet init method (this worker thread code
 >>>>
 >>>>is wrapped
 >>>>
 >>>>>with a user tx).
 >>>>>The topic’s MDB is getting the message OK, however the number of
 >connection
 >>>>
 >>>>in
 >>>>
 >>>>>the monitor (mydomain> JMS Servers> NomJMSServer> Active JMS Servers)
 >>>>
 >>>>keep growing.
 >>>>
 >>>>>As you can see we are releasing the connection in a finally block.
 >>>>
 >>>>Can anybody
 >>>>
 >>>>>explain it.?
 >>>>
 >>>>Perhaps you are throwing a RuntimeException or Error without
 >>>>catching it. Put trace statements before the connection
 >>>>create and right before and after the "connection.close()" to
 >>>>verify.
 >>>>
 >>>>Note that since you are closing the connection, there is no need
 >>>>to close the publisher or session.
 >>>>
 >>>>
 >>>>>Second question: Should we cache the jms session?
 >>>>
 >>>>For performance reasons, yes. But if your performance
 >>>>is fine, you don't need to. Since you are doing
 >>>>a "zip" per message, which is expensive in terms of CPU,
 >>>>the overhead of creating a session per
 >>>>message may be negligable in comparison.
 >>>>
 >>>>
 >>>>>If the answer is yes, can they
 >>>>>expire (close),
 >>>>
 >>>>If the host JMS server is adminstratively shutdown
 >>>>or the host JVM for the JMS server crashes...
 >>>>
 >>>>
 >>>>>how do we check if they are still valid?
 >>>>
 >>>>If it fails when you use it, it ain't valid. ;-)
 >>>>
 >>>>You can detect failures pro-actively by registering
 >>>>a connection onException listerner
 >>>>and a session onException listener.
 >>>>
 >>>>Note that WL 8.1 has built in connection/session
 >>>>pooling, and the JMS Performance Guide white-paper's
 >>>>appendix has sample code for writing your own pool for
 >>>>previous WL versions. There is a linke to
 >>>>the white-paper here:
 >>>>
 >>>>http://dev2dev.bea.com/technologies/jms/index.jsp
 >>>>
 >>>>
 >>>>>Thanks
 >>>>>
 >>>>>
 >>>>> public String sendEvent(SyncOutput event)
 >>>>> {
 >>>>> String retval = null;
 >>>>> try
 >>>>> {
 >>>>> init();
 >>>>> topicPublisher.publish( formatMessage(event) );
 >>>>> }
 >>>>> catch (Exception e)
 >>>>> {
 >>>>> logger().debug("cannot send event", e);
 >>>>> }finally{
 >>>>> release();
 >>>>> }
 >>>>> return retval;
 >>>>> }
 >>>>>
 >>>>> private Message formatMessage(SyncOutput output)
 >>>>> throws JMSException, IOException
 >>>>> {
 >>>>> BytesMessage message = topicSession.createBytesMessage();
 >>>>> GZIPOutputStream gzip = new GZIPOutputStream(new BytesMessageOutputStream(message));
 >>>>> output.flush(new OutputStreamWriter(gzip));
 >>>>> gzip.close();
 >>>>> return message;
 >>>>> }
 >>>>>
 >>>>> private void init()
 >>>>> throws Exception
 >>>>> {
 >>>>> InitialContext context = new InitialContext();
 >>>>> TopicConnectionFactory conFactory =
 >>>>> (TopicConnectionFactory) context.lookup(JMSConfig.get(JMSConfig.FACTORY));
 >>>>> topicConnection = conFactory.createTopicConnection();
 >>>>> topicSession = topicConnection.createTopicSession(false,
 >Session.AUTO_ACKNOWLEDGE);
 >>>>>
 >>>>> Topic topic = (Topic) context.lookup( this.jndiName );
 >>>>> topicPublisher = topicSession.createPublisher(topic);
 >>>>> topicPublisher.setDeliveryMode( DeliveryMode.PERSISTENT );
 >>>>> }
 >>>>>
 >>>>> private void release()
 >>>>> {
 >>>>> try{
 >>>>> if (topicPublisher != null){
 >>>>> topicPublisher.close();
 >>>>> topicPublisher = null;
 >>>>> }
 >>>>>
 >>>>> if (topicSession != null){
 >>>>> topicSession.close();
 >>>>> topicSession = null;
 >>>>> }
 >>>>>
 >>>>> if (topicConnection != null) {
 >>>>> topicConnection.close();
 >>>>> topicConnection = null;
 >>>>> }
 >>>>>
 >>>>> System.gc();
 >>>>> }catch(Exception ignore){
 >>>>> ignore.printStackTrace();
 >>>>> }
 >>>>> }
 >>>>>
 >>>>
 >>
 >

Forgot the passcode to my ipad. When I went to restore it, it asked me if I wanted to update the software so I said yes. It then went into recovery mode, I'm guessing, with the connect to iTunes showing on the screen. Now iTunes will not recognize it??

Forgot the passcode to my ipad. When I went to restore it, it asked me if I wanted to update the software so I said yes. It then went into recovery mode, I'm guessing, with the connect to iTunes showing on the screen. Now iTunes will not recognize it so I have no idea how to get it back! Help!!

Then you will need to try restoring it once more:
Placing your device into recovery (DFU) mode:
Follow these steps to place your iOS device into recovery mode. If your iOS device is already in recovery mode, you can proceed immediately to step 6.
   1. Disconnect the USB cable from the iPhone, iPad, or iPod touch, but leave the
       other end of the cable connected to your computer's USB port.
   2. Turn off the device: Press and hold the Sleep/Wake button for a few seconds
       until the red slider appears, then slide the slider. Wait for the device to turn off.
              * If you cannot turn off the device using the slider, press and hold the
                Sleep/Wake and Home buttons at the same time. When the device turns off,
                release the Sleep/Wake and Home buttons.
3. While pressing and holding the Home button, reconnect the USB cable to the
       device. The device should turn on. Note: If you see the battery charge warning,
       let the device charge for at least ten minutes to ensure that the battery has some
       charge, and then start with step 2 again.
4. Continue holding the Home button until you see the "Connect to iTunes" screen.
       When this screen appears you can release the Home button:
5. If necessary, open iTunes. You should see the following "recovery mode" alert:
6. Use iTunes to restore the device.
If you don't see the "Connect to iTunes" screen, try these steps again. If you see the "Connect to iTunes" screen but the device does not appear in iTunes, see this article and its related links.
Additional Information:
If you have a problem getting into recovery mode then try: RecBoot: Easy Way to Put iPhone into Recovery Mode.
Note: When using recovery mode, you can only restore the device. All user content on the device will be erased, but if you had previously synced with iTunes on this computer, you can restore from a previous backup. See this article for more information.

In the ReportDocument.Load method it tries to connect using the using the connection information embedded in the Report File

Post Author: bhaveshbusa
CA Forum: Crystal Reports
In the ReportDocument.Load method it tries to connect using the using the connection information embedded in the Report File. When the application calls ReportDocument.Load(reportFileName). This
tries to connect to the database using the connection information embedded in
the "reportFileName". This was only realised on checking the ODBC Trace
Log. The connection itself is not a problem. The problem is that the embedded
connection information is related to OLD production system. And failed
connections had raised some concerns.
Note: I am using
SetDataSource to populate the data for the report. So I don't need the
connection.
Is there any way I
can disable this auto-connect?
Thanks and
regards,
Bhavesh

960738 wrote:
I need a help in answering one of the issue encountered last week.
I have created a database link and tried to access the information from a table using the program written in another language. The password provided was incorrect for that user while creating database link. So we expected that,while retrieving the data, Database connection has to be errored out as password provided is incorrrect.
But unfortunately, user account was locked out. When i checked with DBAs they mentioned that it tries to connect 16 ports with in a min of time.we were shocked as it STOPS another scheduled jobs with that user. and affects production badly.
As per the program, it has to connect only one time and yesterday we tried to execute the program in DBAs observation and it errored out as expected. Didn't tried for multiple ports.
Now the question is, WHY the database connection established 16 times last week and caused user account locked. DBAs are unable to answer it. Any EXPERTs opinion on this would greatly appreciated.
I have verified managing ports in oracle documentation, it was mentioned that if one port is busy it will try to connect to another port in the range of ports mentioned during the installtion. DBAs verified ports related file and it was blank. and they are not agreeing with this reason. Please HELP me in finding the correct REASON for this.
is it a NETWORK issue or issue with DATABASE SERVER only?
Thanks
SSP
Edited by: 960738 on Sep 22, 2012 9:13 PMDBLINK is 100% oblivious to the fact any port exists.
DBLINK only contains username, password & TNS Alias.
can you post actual SQL & results?

WLS5.1 - How to configure WLS5.1 to release "unclosed" connections?

 Hi all,
 is there any feature or detector element in WLS5.1 to release connections back
 to the pool if they were not closed properly by the application? If not, is there
 any alternative to overcome the problem?
 Please advice! Thanks!
 Best Regards,
 Winnie


 "Winnie Ngiam" <[email protected]> wrote:
 >
 >Hi all,
 >
 >is there any feature or detector element in WLS5.1 to release connections
 >back
 >to the pool if they were not closed properly by the application? If not,
 >is there
 >any alternative to overcome the problem?
 >
 >Please advice! Thanks!
 >
 >Best Regards,
 >Winnie
 Hi WInnie,
 you can set timeouts for releasing the connection pool if the connection
 is not properly closed by using
 the following way for a T3CLient like :
 t3.setSoftDisconnectTimeoutMins(2);
 for further calrifications let me know.
 http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#startupconnpool
 rgds
 SureshKumar

Delay in the release of connections to pool after closing.

Hi,
I'm using typical jdbc code to close the Connections got through ConnectionPool created on Weblogic 8.1. When the data access / update code is completed execution, I could observe couple of connections still open in the weblogic console connections monitor screen.
These open connections are getting released after 15 minutes approximately, provided if I'm not accessing any DB access/update code till then.
I'm using the following code for closing all the jdbc resources.
public static void closeAllResources(){
         try{
             if (rSet != null){
                rSet.close();
                rSet = null;
             if (rSet2 != null){
                  rSet2.close();
                 rSet2 = null;
             if (preStatement != null){
                 preStatement.close();
                 preStatement = null;
             if (callStatement != null){
                callStatement.close();
                callStatement = null;
             if (conn != null){
                 conn.close();
                 conn = null;
         catch (SQLException e){
}I'm closing the jdbc resources as follows in finally block...
public static boolean saveXXX(String userid, ArrayList list) throws SQLException{
     BaseDAO baseDAO = null;
         String scode= null;
          try {
          baseDAO = new BaseDAO();
              conn = baseDAO.getConnection();                  callStatement = baseDAO.prepareCallableStatement("call pkg_1.pr_add_XXX(?,?)");
                             callStatement.setObject(1, userid);
             callStatement.setObject(2, scode);
     int saveResult = callStatement.executeUpdate();
     finally {
     closeAllResources();
     return true;
}Both the above methods are present in the same java class.
Can sombody help me in resolving the issue immediately?
Regards
Sudarsan

Do you understand what a connection pool is and how it works at all?
It is a pool of open connections. It therefore perfectly fine and appropriate for their to be open connections from your pool to your database once you have returned them to the pool. These connections will be kept alive for a period of time (in your case apparently 15 minutes) to serve the next request for a connection from the pool.
This is really the whole point of using a connection pool. Reuse.

Hello Simple problem - don,t know how to solve it. With Premiere CC when I try to do a selection (click... drag... release the click) very often it stop way before the end of the move I'm swinging the Magic Mouse. I taught that the mouse clicking was de

Hello
Simple problem - don,t know how to solve it.
With Premiere CC when I try to do a selection (click... drag... release the click) very often it stop way before the end of the move I'm swinging the Magic Mouse. I taught that the mouse clicking was defective and went to get a new Magic Mouse after lots of frustration. Today, I have an edit to do it it does the SAME thing !!
I was like ????#$%?&*(???
Opened all the lights and taught I've trow the new mouse to the garbage and was using the defective mouse again... no !! - ??
Actually, the bran new mouse is doing the same thing. What I understand after investigating on the motion and watching carefully my fingers !! - is that when I click I have to keep my finger at the EXACT same place on the mouse... drag and release and it's fine. If I click by pushing on the mouse and my finder is moving of a 1/32th of a millimeter, it will release and my selection will be to redo. You can understand my frustration ! - 75$ later... same problem, but I know that if I click with about 5 pounds of pressure and trying to pass my finger through the plastic of the mouse, it you stay steady and make it !
The problem is that scrolling is enable while clicking and it bugs.
How to disable it ??
Simple question - can't find the answer !

Helllooo !?
sorry but the Magic Mouse is just useless with the new Adobe Premiere CC and since I'm not the only one but can't find answer this is really disappointing. This mouse is just fantastic and now I have to swap from a USB mouse to the Magic Mouse every times I do some editing. My USB mouse if hurting my hand somehow and I want to got back to the Magic Mouse asap. Please - for sure there is a simple solution !
Thanks !!

CachedRowSetImpl.acceptchanges(con) don't release the connection

Similar Messages

Maybe you are looking for