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!

Similar Messages

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.

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

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.

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

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.

RMI - connection handling and parallelity

Hello everybody!
I have some questions about RMI that I was not able to clarify clearly enough through the documentation - maybe due to my poor english that hinders me to understand long technical documents ;-)
Assumed I have a program that allows several users at the same time to connect to a server via RMI:
- Will RMI be able to keep the different users apart? (So that a user will not get something that is determined for another)
- Will RMI create Threads for the different tasks the different users want to execute? How does RMI handle threads?
- What happens if 2 users want to acces the same object at the same time? Will RMI handle that or do I have to declare those methods/fields synchronized or something like that?
Thank you in advance for your answers!

- Will RMI be able to keep the different users apart? (So that a user will not get something that is determined for another)Yes.
- Will RMI create Threads for the different tasks the different users want to execute? How does RMI handle threads?A new thread per connection. Connections are pooled at the client, so this doesn't imply a new thread per call.
- What happens if 2 users want to acces the same object at the same time? Will RMI handle that or do I have to declare those methods/fields synchronized or something like that?It's up to you.

WSA S160 Support for Terminal Servers (How are terminal server connections handled?)

We have a terminal server environment with a mixture of computers and laptops. Currently we have multiple proxy servers and would like to considate down to one. Our current solution does not work well in a terminal server environment. We are looking for a way to integrate all equipment with one soluton and I was curious as to how the S160 handled users connecting via a terminal server.

Edadios thanks for the response. I was reading over this document (see attached), and it looks to me like the connection would be tracked via a cookie surrogate. My bigger concern is that we are looking to be able to track usage per user even though they are on a terminal server. Our current solution (Barracuda) is not able to perform this function. I am hoping to have a S160 on site this week to do some testing but was hoping to gather some intel in the forums prior to implementation.
The response helps clear up what protocols are in use but I am still wondering how terminal server connections are handled by the WSA and if they are truly handled and tracked per user instead of by the device they are connecing to.

J9 wlan connection handling - help needed

I wrote an application which is running on phone and communicates with a server. I can open sockets, and communicate with the server (read/write data on chanel), but after ferw minutes/hours(depend on trafic) the wlan connection between the client and server breakes. The problem is, that after an exception is thrown, I close th connection and try to open a new connection, but can't. It seems, that somewhere in the phone's operatin system the connection is not closed.
My question is , that is there anybody who meet this problem? The second question is that kind of workaround can be used to reconnect to the server?

hi,
have you found a solution? I have nearly the same problem now...
My application runs on windows mobile 6.1 with IBM j9. Connecting to the WLAN inclusive VPN works well on the device, browsing with internet explorer is no problem and if necessary the WLAN and VPN connections are established automatically if needed.
But when I try to invoke a webservice-request from within my java-application the connection isn't established. (Doing the webservice-request while a there is an existing connection everything works fine, e.g. when starting the application right after browsing in internet explorer).
Probably I have to tell the connection manager on wm6 to connect - but how do I implement that?
For .Net I found the following:
- http://msdn.microsoft.com/en-us/library/bb840031.aspx
- http://msdn.microsoft.com/en-us/library/ms849587.aspx
Can anybody give me a hint, please?
regards, blackfox86

Connection Handling

In my Web application, I use a SQL database to store some data. I currently don't use a connection pool. Every time I access database, I do the following:
try {
// Get connection to database
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
DataSource ds = (DataSource) envCtx.lookup("jdbc/mydata");
Connection con = ds.getConnection();
java.sql.Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery(querySQL);
while (rs.next()) {
rs.close();
stmt.close();
con.close();
catch(SQLException ex) {
if (log.isErrorEnabled()) {
log.error("\nERROR: ----- SQLException -----\n");
while (ex != null) {
log.error("Message: " + ex.getMessage());
log.error("SQLState: " + ex.getSQLState());
log.error("ErrorCode: " + ex.getErrorCode());
ex = ex.getNextException();
catch(Exception e) {
e.printStackTrace();
The issue I run into is that if there is an exception, the connection does not get closed and the application can't access the database anymore. I hesitate to put a finally block where I would call:
rs.close(); stmt.close(); con.close();
because the exception might occur while the connection is being opened in which case all these close calls might cause problems. Is this right? What is standard practice to make sure the connection is released even in case of exception?
Also, I am not using a pool. Performance is not an issue in my application (it is a low transaction application), so I should be able to get away without a pool. I fear that using a pool, I may run out of connections if there are too many session active at the same time (even if user log out, the session may be around for a while). Any suggestions in this area?
Martin

What is standard
practice to make sure the connection is released even
in case of exception?A finally block:Connection con = null;
Statement st = null;
ResultSet rs = null;
try {
con = datasource.getConnection();
st = con.createStatement();
//etc etc
catch (Exception e) {
//some code
finally {
if (rs != null) {
    try {
      rs.close();
    catch (SQLException sqle) {}
if (st != null) {
    try {
      st.close();
    catch (SQLException sqle) {}
if (con != null) {
    try {
      con.close();
    catch (SQLException sqle) {}
}You can put that tedious jdbc clean up code in a helper class.

As set up a certain number of users per connection handled by a WLC AP

HELLO community need an access point configured in the user minimum because I was looking and some had up to 49 LAP connections at the same time. I have a WLC 4402VERSION 7.0.98

You can't set a max user on a given AP unless you are running 7.2. The 4400 can't do that. Also its up to the client to decide what ap it will try to associate to. So depending in your ap locations and density of user and devices, all that can factor into why you see more clients on a AP and not on others.
Thanks,
Scott Fella
Sent from my iPhone

SSLM optimistic connection handling?

Similar Messages

Maybe you are looking for