Leaking Connection Handles

We are running a cluster configuration of 4 data-enabled nodes plus 4 Proxy data-disabled nodes that are dedicated to servicing TCP-Extend clients.
We have seen today an issue where Connection Handles are being leaked by one of the Coherence Proxy Processes. I know that a similar issue has been raised by a colleague with respect to a .NET issue which would be fixed in 3.4. However we are using Java for our clients, and our limit of 1024 handles is being breached by Socket Connections that are not being closed.
Sample trace from the logs which results in a "Request was cancelled" on the client:-
2008-04-28 15:47:57,929 ERROR: [Logger@9257955 3.3/387] [] Coherence - 2008-04-28 15:47:57.929 Oracle Coherence GE 3.3/387 <Error> (thread=TcpProcessor, member=10): Error accepting a Socket connection: java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:145)
at com.tangosol.coherence.component.comm.connectionManager.acceptor.TcpAcceptor$TcpProcessor.onAccept(TcpAcceptor.CDB:18)
at com.tangosol.coherence.component.comm.connectionManager.acceptor.TcpAcceptor$TcpProcessor.onSelect(TcpAcceptor.CDB:21)
at com.tangosol.coherence.component.comm.connectionManager.acceptor.TcpAcceptor$TcpProcessor.onNotify(TcpAcceptor.CDB:15)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:35)
at java.lang.Thread.run(Thread.java:595)
This is a very worrying issue for us - can anyone explain why this might be happening? Should the Java client code be explicitly trying to close the connection in certain circumstances.
We are using version 3.3.
Regards,
Simon Martin

Hi Jason
I have already opened a service request via METALINK for this issue so hopefully you should receive more details shortly.
The MBean was reporting only 6 active connections at the time - yet there were over 1000 socket connections for the process within the /proc/$pid$/fd directory indicating the leaking was definitely from that process.
Definitely no custom connection management at this point in time or with the process that exhibited this behaviour.
Fyi we are using v3.3b387.
Rgds,
Simon

Similar Messages

Creative Cloud Leaks Thread Handles

I have Creative Cloud version 1.8.0.447 running on windows 7, and I notice that it leaks a Thread Handle, about 4 times, or so, per minute. Since I leave my computer on most of the time, after a few days, the number of leaked Thread Handles is up in the tens of thousands.
I can see the thread handles leaking using Process Explorer.
Generally when a thread ends, its handle needs to be closed, or else the handle will stay active forever, or until the process ends. It looks like the programming team is not closing these handles after the threads end.
Please, adobe, fix this problem in a future release of creative cloud.
-Todd

Some 10.9.x links
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-and https://forums.adobe.com/thread/1507936
or
A chat session where an agent may remotely look inside your computer may help
Creative Cloud chat support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html

New error with upgrade jboss/tomcat: "Connection handle has been closed and is unusable"

Hi,
This error suddenly appeared when we upgraded from jboss3/tomcat5.0 to jboss4.2/tomcat5.5.
here's the usecase:
1) User clicks on report link
2) Crystal reports web componnent displays screen to fill in report parameters.
3) user enters parameters and clicks submit
4) System throws Exception
The same reports worked fine with jboss 3.2.6/tomcat 5.0. We haven't touched anything in this realm.
Log Excerpt:
09:42:18,842 INFO [datasource] Openning rowset
09:42:18,904 ERROR [reportdefinition] com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: Connection handle has been closed and is unusable
09:42:18,905 ERROR [datasource] Failed to open rowset: the query failed to open rowset
com.crystaldecisions.reports.reportdefinition.datainterface.g: JDBC Error: Connection handle has been closed and is unusable
 at com.crystaldecisions.reports.reportdefinition.datainterface.d.a(Unknown Source)
To try to narrow down the problem, I've updated the jdbc configuration to
 <track-statements>true</track-statements>
here's a recap:
This Boolean element specifies whether to check for unclosed statements when a connection is returned to the pool. If it is true, a warning message is issued for each unclosed statement. If the log4j category org.jboss.resource.adapter.jdbc.WrappedConnection has trace level enabled, a stack trace of the connection close call is logged as well. This is a debug feature that can be turned off in production.
Interestingly enough, this error appears slightly upstream:
(CachedConnectionManager.java:526) - Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@c76003
java.lang.Throwable: STACKTRACE
 at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
 at com.crystaldecisions.reports.queryengine.driverImpl.k.a(Unknown Source)
 at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.new(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.byte(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.j.a(Unknown Source)
 at com.crystaldecisions.reports.dataengine.ba.try(Unknown Source)
 at com.crystaldecisions.reports.common.av.a(Unknown Source)
 at com.crystaldecisions.reports.common.ag.a(Unknown Source)
 at com.businessobjects.reports.sdk.b.e.a(Unknown Source)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown
So the question arises:
1) Is the jboss datasource overly/aggressively closing result sets?
2) or is there a coding error in CRXIR2?
thanks,
bill
Full stack trace:
[2008-03-13 17:26:18,905] [INFO ] org.jboss.resource.connectionmanager.CachedConnectionManager (CachedConnectionManager.java:526) - Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@c76003
java.lang.Throwable: STACKTRACE
 at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290)
 at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417)
 at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
 at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
 at com.crystaldecisions.reports.queryengine.driverImpl.k.a(Unknown Source)
 at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.new(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.byte(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.j.a(Unknown Source)
 at com.crystaldecisions.reports.dataengine.ba.try(Unknown Source)
 at com.crystaldecisions.reports.common.av.a(Unknown Source)
 at com.crystaldecisions.reports.common.ag.a(Unknown Source)
 at com.businessobjects.reports.sdk.b.e.a(Unknown Source)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.y.a(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.r.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.cf.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.z.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.ak.if(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.ad.int(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.bk.for(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.v.a(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.v.if(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(Unknown Source)
 at com.crystaldecisions.reports.sdk.DatabaseController.setTableLocation(Unknown Source)
 at org.apache.jsp.reports.processreport_jsp.switchTables(processreport_jsp.java:131)
 at org.apache.jsp.reports.processreport_jsp.loadReport(processreport_jsp.java:68)
 at org.apache.jsp.reports.processreport_jsp._jspService(processreport_jsp.java:227)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
 at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.shared.pagecache.client.PageCacheFilter.doFilter(PageCacheFilter.java:760)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.util.servlet.ExpiredPasswordFilter.doFilter(ExpiredPasswordFilter.java:92)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.pe.channels.client.servlet.ChannelUrlFilter.processUrl(ChannelUrlFilter.java:168)
 at com.participate.pe.channels.client.servlet.ChannelUrlFilter.doFilter(ChannelUrlFilter.java:100)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.util.servlet.BlockIpAddressFilter.doFilter(BlockIpAddressFilter.java:224)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.outstart.multiapp.filters.KeepOtherSessionsAliveFilter.doFilter(KeepOtherSessionsAliveFilter.java:88)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.util.servlet.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:151)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
 at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
 at java.lang.Thread.run(Thread.java:619)


OK. I found the problem along with a workaround.


The problem:


a programming practice clashes with a new jboss 'safety check'.


Programming practice:


crystal reports gets a database connection in one jsp page, then tries to use it on another jsp/servlet


Jboss safety check:
Jboss/tomcat new comes configured out-of-the-box with a 'cached connection
manager', which


"Check[s] for unclosed connections and transaction terminated checks in servlets/jsps."


 Summary


In short, if a servlet/jsp ends and it leaves a database connection open, Jboss will automatically close it.




Workaround: 
Comment out two entries in these two files:


1) conf/jboss4/pe/deploy/jboss-web.deployer/server.xml


2) conf/jboss4/pe/deploy/jboss-web.deployer/META-INF/jboss-service.xml


The two entries:




1)


 <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve" 
 cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager" 
 transactionManagerObjectName="jboss:service=TransactionManager" /> 


2)


 <depends>jboss.jca:service=CachedConnectionManager</depends> 




Comments on the workaround


The 'cached connection manager' basically makes sure that the application cleans up after bad programmers. It seems most helpful in development, load testing, or trouble shooting.


In production, you can likely comment them out with minimal
impact on the application.

Getting leaked connection issues in ADF 11g - Urgent

Hi,
I am using Jdev 11.1.1.2.0 with ADF 11g.
I am facing severe and recurring issues of leaked connections and JBO 29000. I have tried many ways but in vain.
I observed that say on my own bowser if I do few login-logouts say 3-4 login logouts I start getting the error.
Initially I thought that I can do away with this by increaing my initial connection pool size. It helped but then it was just so that I deferred the exception by few logouts.
So I seriously doubt if my logout is releasing all resources. Here is what I am doing
1. I send an audit record to DB for the logged in user
2. I do commit/rollback
3. I remove the session attributes associated to the logged user
How and where do I get the session invalidate method. Is there something a miss?
Kindly help.

You can all an action and use code like
public void logout(ActionEvent actionEvent) {
try {
ExternalContext ectx = FacesContext.getCurrentInstance().getExternalContext();
HttpServletResponse response = (HttpServletResponse)ectx.getResponse();
HttpSession session = (HttpSession)ectx.getSession(false);
session.invalidate();
response.sendRedirect("Login.jsp");
} catch (Exception e) {
e.printStackTrace();
}The important part is the session.invalidate()!
Timo

A stale Connection Factory or Connection Handle may be used in SOA 11g

Hi all,
I am working on a outbound process from oracle apps to BPEL. I am using SOA 11.1.1.3 version. I have created connection pool in admin server.
But BPEL does not pick the messages from ecx_outqueue present in apps.
Also when i update the Aqadapter in the admin server i get the following message
Selected Deployments were updated.
You must also activate the pending changes to commit this, and other updates, to the active system.
The soa diagonostic log is provided below
[2011-02-14T02:29:21.248-07:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ohsadmin] [ecid: 004b3eilKBAE4UVQu2q2TH0006H0000Fay,1:30378] [APP: soa-infra] [dcid: 49c8ed318246db94:41013faa:12d7ab8287f:-7fff-0000000000002a49] [URI: /em/faces/ai/soa/composite] JCABinding=> Invoice_OracleApps *Error while performing endpoint Activation: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/AQ/ExtEBizConn_Factory from JNDI and get a new Connection Handle.*
[2011-02-14T02:29:21.248-07:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ohsadmin] [ecid: 004b3eilKBAE4UVQu2q2TH0006H0000Fay,1:30378] [APP: soa-infra] [dcid: 49c8ed318246db94:41013faa:12d7ab8287f:-7fff-0000000000002a49] [URI: /em/faces/ai/soa/composite] JCABinding=> Invoice_OracleApps [[
javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/AQ/ExtEBizConn_Factory from JNDI and get a new Connection Handle.
Can anyone provide some inputs on this?

Hi Anuj,
I have followed the following steps mentioned in the metalink ID 1235943.1 but still it is throwing the same error.
1.Log on to your Admin console and navigate to Domain -> Deployments -> <adapter name> -> Configuration Tab -> Outbound Connection Pools Tab -> Under Groups and Instances expand the javax.resource.cci.ConnectionFactory
2.Locate and select the adapter JNDI and click on the Connection Pool Tab.
3.Please check to see if Shrinking is enabled. If not, please enable it.
4.Please check the value for Shrink Frequency Seconds. The default for some connection pools is as high as 900 seconds. Please reset this to 120 seconds or less.
5.Activate your changes.
6.If this does not improve the situation, please also try increasing the max size of your connection pool.
Please advice if any other solution is there.
Thanks,
Dhiraj Mishra

GUI connection error MAXIMUM NUMBER OF CONNECTION HANDLES REACHED

Dear Experts
while logging on to GUI7.10 I am getting following error
MAXIMUM NUMBER OF CONNECTION HANDLES REACHED'
'MAXIMUM NUMBER OF HANDLES REACHED'. 'NO MORE MEMORY IS AVAILABLE'.
'DO YOU WANT TO SEE DETAILED ERROR DESCRIPTION?'
When i click on yes to the question above, i get the following:
'COMPONENT = DPTM'
'RELEASE = 7.10'
'VERSION = 10'
'RETURN CODE= -16'
'Counter = 3
This error is not allowing me work.
Does anyone have a solution?

Hi,
I am having the same issue. Did you resolve the issue.
Please let me know
Regards

LDAP Proxy fails to assign custom connection handler

Hi,
I've setup some custom connection handlers, and my proxy server is behaving randomly.
I mean that sometimes it assigns the new handler sometimes not. This randomness occurs
if I delete the handler and create it again with the same configuration options.
I tried restarting the server as well as upgrading to 6.3.1 (Linux/Centos) without any luck.
Now the server does not assign the high priority custom handler when I connect on the SSL port (1636)
but it does assign it if i connect on the NON-SSL port (1389)
This is is my configuration:
dpconf list-connection-handlers -v -p 1636
anonymous true 5
domain2.example.com true 3
default connection handler true 100
directory services administrators true 1
domain1.example.com true 1
schema false 6
dpconf get-connection-handler-prop domain1.example.com
aci-source : none
allowed-auth-methods : simple
allowed-ldap-ports : ldap
allowed-ldap-ports : ldaps
bind-dn-filters : uid=(.*),cn=(.*),ou=People,dc=domain1,dc=example,dc=com
bind-dn-filters : uid=(.*),ou=(.*),ou=People,dc=subdomain,dc=domain1,dc=example,dc=com
data-view-routing-custom-list : DOMAIN1
data-view-routing-policy : custom
description :
domain-name-filters : any
enable-data-view-affinity : false
ip-address-filters : any
is-enabled : true
is-ssl-mandatory : false
priority : 1
request-filtering-policy : Read and Modify
resource-limits-policy : no-limits
schema-check-enabled : false
user-filter : any
ldapsearch -x -b dc=example,dc=com -H ldaps://proxy.example.com:1636 -W -D "uid=user,cn=admin,ou=People,dc=domain1,dc=example,dc=com" '(uid=user)' dn
[07/Apr/2009:19:44:10 +0300] - CONNECT - INFO - conn=33 client=10.0.0.1:40795 server=proxy.example.com:1636 proto
col=LDAPS
[07/Apr/2009:19:44:10 +0300] - PROFILE - INFO - conn=33 assigned to connection handler cn=default connection handler,
cn=connection handlers, cn=config
[07/Apr/2009:19:44:10 +0300] - OPERATION - INFO - conn=33 op=0 BIND dn="uid=user,cn=admin,ou=People,dc=domain1,dc=example,dc=com" method="SIMPLE" version=3
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=0 BIND dn="uid=user,cn=admin,ou=People,dc=domain1,dc=example,dc=com" method="SIMPLE"" version=3 s_msgid=18 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=0 BIND RESPONSE err=0 msg="" s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - OPERATION - INFO - conn=33 op=0 BIND RESPONSE err=0 msg="" etime=0
[07/Apr/2009:19:44:10 +0300] - OPERATION - INFO - conn=33 op=1 msgid=2 SEARCH base="dc=example,dc=com" scope=2 filter="(uid=user)" attrs="dn "
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=1 SEARCH base="dc=domain1,dc=example,dc=com" scope=2 filter="(uid=user)" attrs="dn " s_msgid=19 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=1 SEARCH RESPONSE err=0 msg="" nentries=2 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=1 SEARCH base="dc=example,dc=com" scope=2 filter="(uid=user)"
attrs="dn " s_msgid=20 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=1 SEARCH RESPONSE err=32 msg="" nentries=0 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=1 SEARCH base="dc=domain2,dc=example,dc=com" scope=2 filter="(ui
d=user)" attrs="dn " s_msgid=21 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - SERVER_OP - INFO - conn=33 op=1 SEARCH RESPONSE err=0 msg="" nentries=2 s_conn=dna:1
[07/Apr/2009:19:44:10 +0300] - OPERATION - INFO - conn=33 op=1 SEARCH RESPONSE err=0 msg="" nentries=4 etime=0
As you see the connection is routed through default connection handler.
This happens sometimes even If I put the client IP in the criteria, without the bind criteria.
I'm a bit comfused. I've also tried to change the priorities but no luck again.
The funny thing is that If I connect through the NON-SSL port on the proxy the connection
is routed through the domain1.example.com connection handler...
[07/Apr/2009:19:51:32 +0300] - PROFILE - INFO - conn=37 assigned to connection handler cn=domain1.example.com,cn=connection handlers,cn=config
any comment on this would be appreciated
regards,
Giannis

Talking about randomness, I've deleted the connection handlers,
deleted the default data views, deleted the default data pool, enabled manual routing.
recreated the connection handlers and now it works.
The handlers are the same as before. Same criteria...
Don't get it but there must be something fishy going on there...
any way, what I'm trying to do is a setup like
"Data Views That Route Requests When a List of Subtrees Is Stored on Multiple, Data-Equivalent Data Sources"
http://docs.sun.com/app/docs/doc/820-2763/gbwva?a=view
where requests with the parent domain as base would work as well.
domain1.example.com
domain2.example.com
example.com (includes both)
if I have something new I will post
Giannis

Connection handle of this Interaction has already been closed

Dear All,
We are facing problem in Portal application and the portal screen shows
"WARNING : DOMG:0001 : EN: Applicatie Foutcould not create JCOClientconnection for logical system: WD_MODELDATA_DEST - Model..." When i checked the JCO and it seems to be working fine.
This error message occurs not all the time but it happens very often nowdays in our production system.
The trace file has the below info ....
#1.5 #005056917DFC0065000001700000148000048ACD4C7672EF#1278514262577
#com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel#sap.com/tcwddispwda#
com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.JcoClientManagementWDP#m.
vanginhoven#10799##n/a##0fee4bb889d711dfa9cc005056917dfc#SAPEngine_Application
Thread[impl:3]74ID\#(J2EE3880500)ID0960469550DB02703921047067447299End.
WID1278484862289##0#0#Error##Plain###Could not create JCOClientConnection for
logical System: *'WD_MODELDATA_DEST' *- Model: 'class com.nl.cv.pr.productlijst.
Zorg_Arrangementproduct_Lijst_Model'. #
#1.5 #005056917DFC002A000009B40000148000048ACD4F560780#1278514310781
#System.err#phobos/phobos~dcrlcear#System.err#Guest#0##as-careview1_EPP_3880550##2a53432b89d711dfbb8a005056917dfc#SAPEngine_
Application_Thread[impl:3]_38##0#0#Error##Plain###Connection handle of this
Interaction has already been closed#
#1.5 #005056917DFC002A000009B50000148000048ACD4F560987#1278514310781
#System.err#phobos/phobos~dcrlcear#System.err#Guest#0##as-careview1_EPP_3880550##2a53432b89d711dfbb8a005056917dfc#SAPEngine_
Application_Thread[impl:3]_38##0#0#Error##Plain###Connection is already closed
and no longer associated with a managed connection#
Do anyone have any idea on this issue? Please help me out to fix this problem
Regards
Raj

Hi,
The error message "Could not create JCOClientConnection for logical System" is only triggered when the WebDynpro application is requesting more JCO connections than the number of JCOs allocated for this application.
I suggest to carefully go through the documents below in order to properly configure your JCOs. If necessary, remove them and recreate in the correct way:
JCo Quick Summary
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
How to Configure the JCo Destination Settings
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3103eb90-0201-0010-71af-be6f4a6f61d1
You will have to calculate the maximum number of JCo connections to each application based on Models and users.
Br,
Javier

Own connection handling class

hi all,
In the jdbcpds.conf file, it is mentioned that we can write our own connection handling class which extends the provided JDBCConnectionHandling class
What i tried after looking at the methods of connection handler is something like this
class myJDBCConnectionHandling extends JDBCConnectionHandling
protected void parseConnectInfo(String s, JDBCConnectDialog jdbcconnectdialog, Plugin plugin)
throws Exception
String dbUrl = null;
dbUrl = "<user>/<pwd>@<remotedatabase>";
super.parseConnectInfo(dbUrl, jdbcconnectdialog, plugin);
Is there anything else that needs to be done
because this is throwing an error
JDBCPDS-62008 : Failed to connect to the datasource null
Invalid arguments in the call
Can anybody correct me
Of course my main purpose of trying this is to have something like a logical name given to the P_JDBCPDS parameter which can be mapped to the actual database url using JNDI lookup.
what i was expecting was, the string when passed to the connection handler, i can add the code to lookup the name in my own connection handler and leave the rest to the provided JDBCConnectionHandling class
Am i going in right direction or not
Or if anybody has any other solution you are welcome to suggest
Any sort of help is greatly appreciated
Thanks in advance
Ramakrishna

hi,
One more thing i forgot to mention was that i am not too concerned about this lookup in reports builder
I need when this is running on the server
thanks & regards
ramakrishna

Leaked connection problem

Hi,
I was getting the below error in BPEL server console, while trying to read data from oracle database:
06/03/20 11:28:33 OrionCMTConnection not closed, check your code!
06/03/20 11:28:33 Logical connection not closed, check your code!
06/03/20 11:28:33 (Use -Djdbc.connection.debug=true to find out where the leaked
connection was created)
Can any please, let me know how to fix this problem?
Thanks & Regards
RN

RN,
Did you ever get this solved? I am having the same problem...
Thx,
Smalls

SSLM optimistic connection handling?

Hi,
If this is posted in the wrong place please let me know.
The behaviour seen in the CSM/SSLM setup we're using indicates that the SSLM is being optimistic about the authentication process and initiating the clear connection before it's completed the certificate authentication.
Is there a way to disable this connection handling so that it only initiates the clear connection when it has successfully completed the SSL authentication?
Thanks!

Hi,
If this is posted in the wrong place please let me know.
The behaviour seen in the CSM/SSLM setup we're using indicates that the SSLM is being optimistic about the authentication process and initiating the clear connection before it's completed the certificate authentication.
Is there a way to disable this connection handling so that it only initiates the clear connection when it has successfully completed the SSL authentication?
Thanks!

DB connection handling with many adfbc AM

Hi Gurus,
Currently in my application we have some many AM (around 30). Initially it AM was created for each complex usecase for ease of separation. Down the line we realized the too many AM is not good and created a RootAM and nested the other AM inside the RootAM. We could manage to migrate most of the bindings to use the RootAM, however we left some of them due to the complexity.
Now we end up with around 6 AM (including the RootAM). In the application AM required a DB connection and the application is taking around 6 DB connection per user (incase of 50 concurrent user 50 * 6 = 300). is there any way that we can specify/configure to use the same DB connection for these 6 AM (one DB connection per user)?
Also i tried the following scenario in the browser, login into my application (i can be able see the no of connection in the weblogic console) after that close the browser, then check out the no of connection( it is same). In this case i guess the AM is still alive, so will the connection only release after the AM timeout or do we need to do any specific code to force release the connection on browser close ? How about the user logout (we destroy the session on logout click)
Looking forward to hear from the gurus opinion on this

Hi Philippe,
The only way to most of it is using a debugger, like
OptimizeIt. Weblogic 6.1 provides an ability to track
connection leaks. Set console message level to
warnings and you'll get notifications about leaked
connections along with stack traces showing where
leaked connection was created.
Regards,
Slava Imeshev
<Philippe Lantin plantin_AT_cobaltgroup.com> wrote in message
news:3bbc9fce$[email protected]..
>
>
Hello,
I would like to be able to track the usage of our db connection pools indetail.
I need to know which beans or servlets are currently using pooledconnections,
how long they have been using them, and how long the connections has beenidle.
>
Is this wishful thinking, or is there an easy way to find this out? Theinformation
from the console tool is not detailed enough for our needs. I am trying totrack
down a problem with unreleased db connections.
I am using weblogic v.6.1 with oracle's type4 driver.
-thanks-

DPS6.3 modify default connection handler?

While making some changes in a dps through the dscc I edited the default connection handler and added two connection policies. I have now lost access to the dps through the dscc possibly because of the policies added.How do I fix the default connection handler? Is there a dpconf command to read it, and delete the policies?
Edited by: Xoth on Jun 11, 2009 12:38 PM
FIXED. I figured it out. Looking at reference manual instead of admin where the dpconf commands are.
dpconf get-connection-handler-prop -h host -p port "default connection handler"
dpconf set-connection-handler-prop -h host -p port "default connection handler" request-filtering-policy:no-filtering
dpconf set-connection-handler-prop -h host -p port "default connection handler" resource-limits-policy:no-limits

Dummy post to increase the reply count. Sorry for the noise.

Adobe Reader X leaks GDI handles in quick search box

Just installed Adobe Reader X a couple of days ago (Windows 7, x64). I used it for numerous online documents (in Firefox), while searching for some specific terms in each document. After a while the reader presented a strange picture, not properly painting itself anymore. Then, the reader became unresponsive, and Firefox too, and I had to kill the task.
This happened a few times on different pdf documents.
In my programming career things like these have happened more often so, when the behavior happened again, I went checking the process using Windows Task Manager, adding a few extra columns (Handles, User Objects, GDI Objects) and found that the number of GDI objects was nearly 10000, the absolute limit that Windows imposes on any single process.
I went on checking the reader, now standalone and without Firefox, to see if the problem would persist. Opened a few pdfs and scrolled back and forth. No problems -
tried the same in Firefox to see if the plugin was OK - still no problem.
Then started using the quick search box (Ctrl-F) and repeatedly looked for something trivial (e.g. just a single letter A) - Bingo! Now the GDI handle count starts rising seriously, and does not come back to the original level.
This is definitely a leak, and it needs to be fixed.

We don't process bug reports via these forums - please post any details of unexpected behaviors to the official reporting form.

Connection-handling of ports

I want to make all connections through a proxy. I need to run the traffic through my proxy to be able to simulate some WAN-traffic + count the traffic. I know I can specify the proxy in the connection-string and the connection is then established.
But obviously the connection via the proxy is only to negotiate the port resp. address for the data-transfer. Cause the data-transfer is not handled via the proxy-config, but directly.
e.g. Proxy: localhost:9101 ==> connection is established via localhost, 9101; But no data is transferred on these, but on some other port, e.g. 3745, on my machine.
Is there a way to specify the callback-port resp. callback-machine? The best would be to specify it in the connection-string.
Thx
LeO

This is part of the Oracle Net protocol: during a connection attempt the server may ask the client to connect to a different port. If you want to use a network proxy then it has to understand this protocol.
Cyclops for example is an Oracle network proxy. You can find it here: http://lavarene.blogspot.com/2010/05/cyclops-oracle-net-proxy-and-replay.html
Regards.

Leaking Connection Handles

Similar Messages

Maybe you are looking for