JDBC Connections not being returned to pool

Greetings All.
I really need some help here to find out where my connections are being held.
I have a transactional connection pool that runs out of connections on average three times a day. I've read all the threads in the newsgroups for connection leaks and how to always release connections in the finally block.
1.
I can confirm that it's definitely not a connection leak, I confirmed this by using the jar for tracing connection leaks and none was displayed.
2.
I've looked at all our code and all code that uses jdbc connections destroys jdbc resources in the finally clause.
3.
I'm new to the department and therefore cannot tell you what new code was put in that caused this problem to occur.
4.
We're using WL 8.1.3 AND JDK 1.4.2_06
5.
I've tried JMX to view what the connections are doing when this problem occurs, and hence enabled statement cache which revealed nothing of interest to me. I just wish somehow I could get to trace which threads reserved the connections and do a stack trace on them.
The most frequent error in my jdbc logs is :
java.sql.SQLException: ORA-01401: inserted value too large for column
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
     at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
     at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:656)
     at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:70)
     at net.cellc.sal.ejb.saldataaccess.TransactionDAO.updateRecordStatus(TransactionDAO.java:76)
     at net.cellc.sol.ejb.sol.SOLBean.updateRecord(SOLBean.java:312)
     at net.cellc.sol.ejb.sol.SOLBean.processMessage(SOLBean.java:170)
     at net.cellc.sol.ejb.sol.SOL_ytyu34_EOImpl.processMessage(SOL_ytyu34_EOImpl.java:46)
     at net.cellc.sal.ejb.sal.SALBean.callSOL(SALBean.java:339)
     at net.cellc.sal.ejb.sal.SALBean.process(SALBean.java:201)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl.process(SAL_ki83rk_EOImpl.java:100)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
SQLException: SQLState(23000) vendor code(1401)
Your help would be really appreciated.
Regards
Ze Casperian

Hi. Show us your pool definition. You should turn off refresh test minutes.
Set it to 9999999.
Joe
Mncedisi Kasper wrote:
Greetings All.
I really need some help here to find out where my connections are being held.
I have a transactional connection pool that runs out of connections on average three times a day. I've read all the threads in the newsgroups for connection leaks and how to always release connections in the finally block.
1.
I can confirm that it's definitely not a connection leak, I confirmed this by using the jar for tracing connection leaks and none was displayed.
2.
I've looked at all our code and all code that uses jdbc connections destroys jdbc resources in the finally clause.
3.
I'm new to the department and therefore cannot tell you what new code was put in that caused this problem to occur.
4.
We're using WL 8.1.3 AND JDK 1.4.2_06
5.
I've tried JMX to view what the connections are doing when this problem occurs, and hence enabled statement cache which revealed nothing of interest to me. I just wish somehow I could get to trace which threads reserved the connections and do a stack trace on them.
The most frequent error in my jdbc logs is :
java.sql.SQLException: ORA-01401: inserted value too large for column
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
     at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
     at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:656)
     at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:70)
     at net.cellc.sal.ejb.saldataaccess.TransactionDAO.updateRecordStatus(TransactionDAO.java:76)
     at net.cellc.sol.ejb.sol.SOLBean.updateRecord(SOLBean.java:312)
     at net.cellc.sol.ejb.sol.SOLBean.processMessage(SOLBean.java:170)
     at net.cellc.sol.ejb.sol.SOL_ytyu34_EOImpl.processMessage(SOL_ytyu34_EOImpl.java:46)
     at net.cellc.sal.ejb.sal.SALBean.callSOL(SALBean.java:339)
     at net.cellc.sal.ejb.sal.SALBean.process(SALBean.java:201)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl.process(SAL_ki83rk_EOImpl.java:100)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
SQLException: SQLState(23000) vendor code(1401)
Your help would be really appreciated.
Regards
Ze Casperian

Similar Messages

Connections not being released from pool with Weblogic 5.1 sp 8

I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin
jdbc driver as shown in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com

I agree with Sree. We had same kind of problem before but I attribute this mostly
to the application handling of the connections rather than container in managing
pools. Most often programmers tend to disregard to explicitly claim the resources(close
them in case of db con.s) in case of exceptions. Though they keep a finally block
at the end of every business method , my experience says, more safer it is to close
them in exception catch block too. I dont know if some JVMs defer the execution of
finally blocks/containers override the behavior.
comments?
-Chandra
"Sree Bodapati" <[email protected]> wrote:
Hello Anish,
There are two things here:
1. Make sure connections are closed (in a finally block). If objects are
not
at the method level, the application code may
be overwriting and losing references to the connection. So watchout for
that.
2. Never try to get a connection in an infinite loop in the application,
that will take all the available execute threads on the server when you
have
enough number of clients and can cause this issue.
One other config change that I would suggest is,
make refreshtestMinutes=99999, testConnsOnReserve should be sufficient to
ensure application gets a good connection.
hth
sree
"Anish Srivastava" <[email protected]> wrote in message
news:[email protected]...
I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin
jdbc driver as shown in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com

Generic JDBC connection not setting up.

Hey ..
I am trying to make a Generic JDBC connection in DB adapter. For the steps I am refering to this blog: https://blogs.oracle.com/middleware/entry/configuring_mssql_with_soa_suite
so I went as follows: step 3 of 4 of adapter configuration > create new connection > Driver class: new > Library: Browse
chose the driver source .jar, put the correct URL & tested the connection.
The Error that came said:
"Test failed: Driver class not found.
Verify the Driver location"
I tried same thing with sqljdbc.jar - the file used in the blog ... Same error was there.
What's the mistake? What should I try to do?

The problem got solved ..
Actually the path was correct but the driver class name was wrong ..
Perhaps it tries to find the driver class with the specific name in specified .jar
I thought we are CREATING new thing ..
Thanks anyways for your help

CR4E only support JDBC connections not support exterior datasource?

The current vision only support JDBC connections?when I organized the datasource or datalist in the application, if this datasource or datalist can connect the data connection? Thank you!jessica

 Hi JessicaYes, the JRC only works with JDBC connections. You can also pass it POJOs at runtime. Rob Horne <a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a>

Jdbc Connections not closed on OC4J 9.0.4 - BUG VERSION?

Hi, I migrate my applications from 9ias 9.0.3 to OAS 10g with OC4J 9.0.4.
After migration, the jdbc connections provide by Data Source Names don't be closed in Oracle Database 8.1.7, stay INACTIVE state, and in few time of access, the Oracle Database exceded limit of sessions.
The OC4J 9.0.4.1 resolve this problem ? Where i can download this release ?
Any body have any idea ?
thanks,
Danilo

Hi
did you find any solution for this problem? I'm having the same problem...
thanks in advanced
Vitor

Connections not being released from jdbc pool on WLS 5.1 sp8

I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin jdbc driver as shown in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com

Hi Caren,
Weblogic doesn't close connections on "time-out". There are some reasons
for this. The most important one is that even if you have such a
functionality,
in case of a connection leak all the available connections can be trashed in
a matter of milliseconds, so it wouldn't help at all. Though, weblogic does
close leaked connection when they are garbage collected, but it's easy to
see
that it doesn't help a lot, too.
So you need to make sure that all the JDBC objects are closed properly,
for example like in this code:
try {
} finally {
try {resultSet.close();} catch (SQLException se) {}
try {preparedStatement.close();} catch (SQLException se) {}
try {connection.close();} catch (SQLException se) {}
Also it's possible that you simply don't have enough connection.
You could try to increase size of the pool.
Regards,
Slava Imeshev
"Karen Law" <[email protected]> wrote in message
news:[email protected]...
Closing the DB connections is important. But is there any parameters to be
set in the WebLogic configuration in order to release the connection whenit
hasn't been closed for a long time? Say, setting the connection timeout?
Many thx!
Karen
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Do you close the DB connections in a finally block after you've finished
using them?
If not your application is leaking the connections and sometimes GC is
not able or does not free those in a timely manner.
--dejan
Anish Srivastava wrote:
I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin jdbc driver as
shown
in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com

DB Connections not being released when using Weblogic Datasource

I am using Kodo-JDO 2.5.3 and Weblogic 8.1.
I have JDO running as a JCA connector and I have a simple stateless session
bean persisting a simple object. My problem is that every time I call my
session bean to persist an object it grabs a connection from the Weblogic
connection pool and never returns it. So if I have configured a maximum of
50 connections in the pool, on my 51st call to the session bean I will get
an error saying it cannot acquire a connection from the pool. (error pasted
below)
I have configured my JDO parameters as follows:
ConnectionRetainMode=persistence-manager (also tried 'transaction')
TransactionMode=xa
ConnectionFactoryName=ERDataSource
ConnectionFactory2Name=NonXADataSource
At the end of every call to the SessionBean I perform a
persistenceManager.close(); and a persistenceManager=null;
Any ideas why connections are not getting re-used?
Exception I am receiving:
java.sql.SQLException: Internal error: Cannot obtain XAConnection
weblogic.common.resourcepool.ResourceLimitException: No resources currently
available in pool MyJDBC Connection Pool-1 to allocate to applications,
please increase the size of the pool and retry..
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwDataStore(SQLExcep
tions.java:64)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getSQLExecutionManag
er(JDBCStoreManager.java:722)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.setPersistenceManage
r(JDBCStoreManager.java:133)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.initialize(PersistenceMa
nagerImpl.java:173)
at
com.solarmetric.kodo.ee.EEPersistenceManager.initialize(EEPersistenceManager
..java:50)
at
com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory.newPersistence
Manager(EEPersistenceManagerFactory.java:107)
at
com.solarmetric.kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceMan
ager(PersistenceManagerFactoryImpl.java:204)
at
com.solarmetric.kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceMan
ager(PersistenceManagerFactoryImpl.java:136)
at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory.getPersistenceManager
(JDOConnectionFactory.java:161)
at
com.mslv.osa.infrastructure.ossj.app.JVTSessionBean.getPersistenceManager(JV
TSessionBean.java:308)
at
com.mslv.osa.infrastructure.system.app.SystemJVTSessionBean.createSystemProp
erty(SystemJVTSessionBean.java:882)
at
com.mslv.osa.infrastructure.system.app.SystemJVTSessionBean_toe7tm_EOImpl.cr
eateSystemProperty(SystemJVTSessionBean_toe7tm_EOImpl.java:1536)
at
com.mslv.osa.infrastructure.system.app.SystemJVTSessionBean_toe7tm_EOImpl_WL
Skel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:407)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:108)
at
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:356)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:353)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:123)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:351)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
0)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
Glen

A couple of suggestions that might do the trick:
1. Upgrade to 2.5.4
2. Leave the ConnectionRetainMode to its default value (on-demand).
3. Make sure you always close your Query results and Extent iterators.

LDAP connections not being closed

Hi,
I am trying to authenticate against a Netscape LDAP server and it works fine for 2 out of the 3 cases I am testing against.
The first case is authenticating with the correct username and correct password. In this case the user is authenticated and the connection is closed.
In the second case, I try to authenticate with the correct username and a wrong password. The authentication fails and an AuthenticationException is thrown. The connection is closed.
In the third case, where I have the PROBLEM is if I provide a wrong username, AuthenticationException is thrown indicating that such an username does not exist. But the CONNECTION IS NOT CLOSED.
Following is the code :
     private boolean authenticate(String userName, String password) throws Exception {
          Hashtable env = new Hashtable(11);
          env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
          env.put("com.sun.jndi.ldap.connect.pool", "false");
          env.put(Context.SECURITY_AUTHENTICATION, "simple");
          env.put(Context.SECURITY_PROTOCOL, "ssl");
          env.put(Context.SECURITY_PRINCIPAL, getSecurityPrincipal(userName));
          env.put(Context.SECURITY_CREDENTIALS, password);
          env.put(Context.PROVIDER_URL,"ldap://ldap05.nike.com:11003");
          DirContext ctx = null;
          try {
               // Create initial context
               ctx = new InitialDirContext(env);
               return true;
          } catch (AuthenticationException e) {
               log.error(e.getMessage());
          } catch (NamingException e) {
               log.error("The user could not be validated on LDAP server due to :" + e.getMessage());
          } finally {
               if (ctx != null) {
                    ctx.close();
          return false;
     }Any help is appreciated.
Thanks in Advance.

I did run the NETSTAT command and found some interesting things.
I ran it for the three cases. The first case is running netstat immediately after authenticating the user with VALID credentials. The status of the connection is TIME_WAIT which is the desired behaviour.
In the second case, when trying to authenticate with CORRECT username but a wrong password, an AuthenticationException is thrown. When I run the netstat command, the connection is in TIME_WAIT state which is the desired one.
In the third case, when I provide a wrong username, an AuthenticationException is thrown. When I run the netstat command, the connection is in ESTABLISHED state, which it should not be in.
An authenticationException is thrown for wrong username and also for wrong password. But the connection is closed for wrong password, but not for wrong username.This is what seems to me as a weird behaviour.
I was under the impression that in the CODE I mentioned at the begining of this topic, the INITIALDIRCONTEXT had the responsibility of closing the connection when authentication fails as we don't have a handle to close it. It is doing so in the case of ERROR 49 which is wrong password, but not in the case of ERROR 32 which is wrong username. Correct me if I am wrong, but doesn't it seem to be a bug with the INITIALDIRCONTEXT class.
Thanks.

Username and Password Required for Wifi Connection, Not Being Asked for Username

I just updated my iphone 4s to ios 8 and attempted to join my school's wireless network, which requires both a username and a password. i am being asked for a password but not a username.
my question here is how to have the username be requested as well.
thank you in advance for answering.

Hi, did you ever find a solution to this? I see your post is old, but the exact same thing has happened to me and I can't figure out what the generic username and password would be. Any insight you have would be most helpful. Thanks!

ORA-00936 not being returned.

I by accident ran across a syntactical error that SQL Developer is not reporting. Run this select query is both SQL Plus and SQL Developer....
select table_name, upper(substr(table_name,1,instr(table_name,'\')- 1)),
upper(substr(table_name, instr(table_name,'\') ,444)),
from all_tables;
Notice that SQL-Plus will return "ORA-00936: missing expression" because there is an extra comma just before "from all_tables". However, SQL Developer does not do this properly and states "All rows fetched: 0".
My versions...
SQL Developer 1.5.4
Oracle 10.2.0.4

Srinivas,
Yes, yes, and yes
A little more background... we're attempting to move the process to a new SAP box which uses AIX. The SAP RFC toolkit was installed and the C program was compiled successfully. The only things changed were the directories where the program resides.
I think you're correct in saying something in the code probably does not work properly with AIX, but I was hoping for hints as to what it might be (since it compiled in AIX).
...guess I need to track down a C/AIX/RFC expert...
Rob,
I double-checked, no short dumps are occurring. The RFC appears successful, but the data is not returned.
Thanks again.

JDBC Connections not closed

Hi,
we work on a Jdevelopper intranet application and an Oc4j application server.
recently, we have reached the maximum number of connections to an Oracle DB.
apparently, we have a lot of old connections that are not closed!!
is there any action to do on Oc4j configuration or Jdevelopper application to avoid this problem ??
thank you for help.
Cordialy

Hi
did you find any solution for this problem? I'm having the same problem...
thanks in advanced
Vitor

Oracle SOA Suite - SOAP Fault content not being returned

It starts with a fairly standard scenario: from within a BPEL process in Oracle SOA Suite, I’m making a call to an external web service. The not-so-standard part: the owner of the external web service has decided to return all errors in the form of a SOAP fault. Unfortunately, this error schema is not included in the WSDL. If we call the external web service directly (via SOAPUI, for example), we get the following, including a nice explanation of why it errored out:
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:err="error.xml.common">
<faultcode>soapenv:Server</faultcode>
<faultstring>Undefined</faultstring>
<detail>
<err:ErrorList>
<err:Error>
<err:Application>CIA</err:Application>
<err:Code>1031</err:Code>
<err:Description>Field value is invalid Credit Card Number V failed mod10 check</err:Description>
<err:ServerTime>2010-02-25T17:37:38.472-05:00</err:ServerTime>
</err:Error>
<err:StackTrace>subscription.memberservices.common.exception.ServiceInvocationException: 1031~Field value is invalid Credit Card Number V failed mod10 check
at subscription.memberservices.common.client.http.CiaHttpClient.checkForErrors(CiaHttpClient.java:120)
at subscription.memberservices.common.client.http.CiaHttpClient.enroll(CiaHttpClient.java:50)
at subscription.memberservices.na.processes.enroll.EnrollProcess.callCiaEnroll(EnrollProcess.jpd:1003)
at subscription.memberservices.na.processes.enroll.EnrollProcess_wf$ImplControlSend14.invoke(EnrollProcess_wf.java:145)
at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
... 38 more</err:StackTrace>
</err:ErrorList>
</detail>
</soapenv:Fault>
No matter what I try, however, I can’t fetch the information in the “detail” element above. When examining the audit trail in SOA Suite, I can only see this:
<fault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Undefined</summary>
</part>
<part name="detail">
<detail>javax.xml.ws.soap.SOAPFaultException: Undefined</detail>
</part>
<part name="code">
<code>null</code>
</part>
</remoteFault>
</fault>
It seems SOA Suite is “protecting” my service from the other SOAP fault elements instead of passing everything back, only passing the faultstring element. I even tried adding an ErrorList schema to match theirs but to no avail. Anyone out there have any experience, luck or ideas with this problem?
Thanks for the assistance,
Rob

Re: Oracle SOA suite server does not startBut I can see that server has got started -
<21-Jul-2010 12:04:47 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>em application gets deployed on admin server and not on SOA server. You may access em console on - http://<hostName>:<admin_server_port>/em
By default admin server port is 7001.
Regards,
Anuj

Hdmi connection not being detected on tv

So when I plug the hdmi into my computer through the adapter, it is no longer showing up on my TV, saying 'no signal'. It was working earlier today but now its not.
When I plug it it, the screen flashes like usual, but nothing happens. When I look in the displays part of system preferences, it knows its attached, but it still doesn't do anything.
So far I have tried taking it out and plugging it in again, restarting the computer, restarting the NVRAM because thats what another support thread said but none of them have worked.
I'm not sure if this is a problem with my computer, my TV, or my cable, but if anyone could tell me whats wrong, I would greatly appreciate it.

Your problem may be as simple as an HDMI cable that has gone bad, or.
Your television may have had its HDCP (High-bandwidth Digital Content Protection) credentials removed.
Sometimes a display can be HDCP certified and then later be removed from the certified list. So purchasing a new display (TV) may not be a permanent solution.
Your display may not be on the "approved" list, or was removed from it.
The Hollywood demanded technology is called High-bandwidth Digital Content Protection (HDCP) and aims to prevent copying of digital audio and video content as it travels across a variety of display connectors, even if such copying is not in violation of fair use laws.
I have occasionally offer methods for fixing this but my post gets deleted. Suggest you search elsewhere on the Internet for advice or purchase another television.

Wireless Internet Connection Not Being Shared

I'm having a bizarre problem that I cannot get my head around. I have just setup my Airport Extreme and it works fine wirelessly with my G4 Powerbook, whereas other devices can connect to the network but cannot access the internet. I am using the following settings:
Country: United States
Radio Mode: 802.11n (802.11b/g compatible)
Security: WPA2 Personal
I do you connect to the Internet: I use a DSL or cable modem with a static IP or DHCP
Configure IPv4: Using DHCP
Wireless Network Mode: Create a wireless network
My wife's MacBook can connect to the wireless network, but it just can't get on the internet.
I've tried turning stuff on and off. I've tried connecting the ethernet cable from my ComCast modem to the WAN socket in the back of the AX and using 'Bridge Mode'. But I've now connected it in the LAN sockets.
Any help would be greatly appreciated.
Thanks,
Ben

Bob Timmons wrote:
The WDS procedure that Tesserax posted recently should provide better guidance.
http://discussions.apple.com/thread.jspa?threadID=2287950&tstart=0
Thanks, I had a look at the thread; those instructions are from 'DesigningAirPort_Networks10.5-Windows.pdf', which I had downloaded earlier today. After reading through it there didn't seem to be anything that I missed in the WDS set-up. I re-did the set-up and got the same result.
For no particular reason, I tried setting up the WDS yet again, and now the network and internet access are functioning correctly, no problems. This time I had both AXs in the Main's room, then moved the Remote to its location after set-up. I don't know how this might make a difference, as this was how I did the set-up originally, and it didn't work then.
So, the problem was a phantom and the solution was magic — with a bit of helpful advice, of course — thanks

Database Connections Not Closing

I'm using iBatis for PostgreSQL database access and frequently have problems with connections not being closed. Here is a copy of my sqlMapConfig file:
============================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE sqlMapConfig
PUBLIC "-//iBATIS.com//DTD SQL Map Config 2.0//EN"
"http://www.ibatis.com/dtd/sql-map-config-2.dtd">
<sqlMapConfig>
<properties resource="ibatis.properties" />
<settings
lazyLoadingEnabled="true"
cacheModelsEnabled="true"
enhancementEnabled="false"
useStatementNamespaces="false"
/>
<transactionManager type="JDBC" commitRequired="true">
<dataSource type="DBCP">
<property name="driverClassName" value="${driver}" />
<property name="url" value="${url}" />
<property name="username" value="${username}" />
<property name="password" value="${password}" />
<property name="maxActive" value="10"/>
<property name="maxIdle" value="5"/>
<property name="maxWait" value="5000"/>
<property name="logAbandoned" value="true"/>
<property name="removeAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="1"/>
<property name="Driver.logUnclosedConnections" value="true"/>
</dataSource>
</transactionManager>
<sqlMap resource="job-sqlMap.xml" />
</sqlMapConfig>
============================
Due to the logAbandoned and removeAbandoned settings, I get a report in my log file whenever there is a connection that was not properly closed. Here is one of those log entries:
23:22:51.483 (10) Finalizing a Connection that was never closed:
java.lang.Throwable: Connection was created at this point:
at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:175)
at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:84)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.init(JdbcTransaction.java:48)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:89)
at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeQueryForList(MappedStatement.java:139)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:567)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:541)
at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(SqlMapSessionImpl.java:118)
at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.queryForList(SqlMapClientImpl.java:94)
at edu.calpoly.lib.multimedia.big.db.AutomaticPeriodUpdateIBatisImplDBHandler.getGamesWithAutomaticUpdatePolicy(AutomaticPeriodUpdateIBatisImplDBHandler.java:154)
at edu.calpoly.lib.multimedia.big.game.AutoUpdateThread.run(AutoUpdateThread.java:155)
The file: AutomaticPeriodUpdateIBatisImplDBHandler.java contains an iBatis call on line # 154:
--> list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
from the map file:
<select id="getGamesWithAutoPolicy" resultClass="java.util.HashMap">
<![CDATA[
SELECT gameid, policy
FROM update_policy
]]>
</select>
Here is the code for the entire method that uses this transaction:
============================
public List getGamesWithAutomaticUpdatePolicy() throws BIGDatabaseFacadeException
List list = new ArrayList();
try
sqlMap.startTransaction();
list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
sqlMap.commitTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
finally
try
sqlMap.endTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
return list;
============================
I know that this should be handled as an automatic transaction, but I tried adding the start, commit and end transaction commands in my desperate attempt to fix this problem (but it still didn't help).
Here is my code for creation of sqlMap -
--> sqlMap = SqlMapClientBuilder.buildSqlMapClient(Resources.getResourceAsReader("sqlMaps.xml"));
Except for the fact that occasionally connections are not closed, overall my database access using iBatis works very well.
In the course of trying to fix this problem I've worked to update all my lib files to the latest versions, and here is current status:
My iBatis lib file: ibatis-2.3.4.726.jar
My JDBC driver: postgresql-8.4-701.jdbc3.jar
Required commons files:
commons-dbcp-1.2.2.jar
commons-pool-1.5.3.jar
Note that I tried adding --> commitRequired="true" to the transactionManager in sqlMaps.xml, hoping it might help, but no joy.
Please help me figure out why my database connections often do not close. Thank you very much!

I'm sorry, but I don't understand what you mean by "close the session." I believe iBatis is supposed to take care of all that automatically. My understanding is that all the user does is create the sqlMapClient and then use it along with various map files to query and update the database. iBatis does the rest.

JDBC Connections not being returned to pool

Similar Messages

Maybe you are looking for