Dear All,

 

We deploy web application on application server. Users accessing content
server(Documentum) through application server. But we are getting
following error after 3 hours. So our unable to access Document
Management System(DMS).Temporary solution for this restart application
server then user able to access DMS.

 

We are getting DM_API_E_NO_SESSION error.Please find attached file for
error.

 

2007-05-14 14:31:08 StandardWrapperValve[SessionTimeoutControl]:
Servlet.service() for servlet SessionTimeoutControl threw exception

DfAuthenticationException:: THREAD: http-8080-Processor24; MSG:
[DM_API_E_NO_SESSION]error:  "There are no more available sessions."

; ERRORCODE: 1905; NEXT: null

            at
com.documentum.fc.client.DfSessionManager.newManualSession(DfSessionMana
ger.java:751)

            at
com.documentum.fc.client.DfSessionManager.createSessionHelper(DfSessionM
anager.java:599)

            at
com.documentum.fc.client.DfSessionManager.getSession(DfSessionManager.ja
va:531)

            at
com.documentum.fc.client.DfSessionManager.getSession(DfSessionManager.ja
va:334)

            at
com.documentum.web.formext.privilege.UserPrivilegeModel.getUserPrivilege
(UserPrivilegeModel.java:188)

            at
com.documentum.web.formext.privilege.PrivilegeService.getUserPrivilege(P
rivilegeService.java:57)

            at
com.documentum.web.formext.config.PrivilegeQualifier.getScopeValue(Privi
legeQualifier.java:72)

            at
com.documentum.web.formext.config.ScopeKey.<init>(ScopeKey.java:58)

            at
com.documentum.web.formext.config.ConfigService.makeScopeKey(ConfigServi
ce.java:1036)

            at
com.documentum.web.formext.config.ConfigService.lookupElement(ConfigServ
ice.java:334)

            at
com.documentum.web.formext.config.ConfigService.lookupInteger(ConfigServ
ice.java:504)

            at
com.documentum.web.servlet.SessionTimeoutControl.getShortTimeout(Session
TimeoutControl.java:258)

            at
com.documentum.web.servlet.SessionTimeoutControl.service(SessionTimeoutC
ontrol.java:159)

            at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

            at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:237)

            at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:157)

            at
com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilter.
java:113)

            at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:186)

            at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:157)

            at
com.documentum.web.env.WDKController.processRequest(WDKController.java:9
4)

            at
com.documentum.web.env.WDKController.doFilter(WDKController.java:82)

            at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:186)

            at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:157)

            at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:214)

            at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo
ntext.java:104)

            at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5
20)

            at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCon
textValve.java:198)

            at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:152)

            at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo
ntext.java:104)

            at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5
20)

            at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:137)

            at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo
ntext.java:104)

            at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:118)

            at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo
ntext.java:102)

            at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5
20)

            at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)

            at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo
ntext.java:104)

            at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5
20)

            at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)

            at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)

            at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:79
9)

            at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:705)

            at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:57
7)

            at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:683)

            at java.lang.Thread.run(Thread.java:534)

Caused by: DfException:: THREAD: http-8080-Processor24; MSG:
[DM_API_E_NO_SESSION]error:  "There are no more available sessions."

; ERRORCODE: 100; NEXT: null

 

For this I have change attribute in dmcl.ini file in application
server.(max_collection_count=1000 and max_session_count=1000)

 

We appreciate support to resolve this problem.

 

 

 

Regards,
Piyush Chordiya.
Email: [EMAIL PROTECTED]



 


======================================
i-choose online store at www.tataindicom.com
Your Comfort.Your Convenience.YourChoice.
====================================== 

DISCLAIMER:
The information contained in this message (including any attachments) is 
confidential and may be privileged. If you have received it by mistake please 
notify the sender by return e-mail and permanently delete this message and any 
attachments from your system. Any dissemination, use, review, distribution, 
printing or copying of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change.TATATELESERVICES LTD. 
(including its group companies) shall not be liable for the improper or 
incomplete transmission of the information contained in this communication nor 
for any delay in its receipt or damage to your system. TATA TELESERVICES LTD. 
(or its group companies) does not guarantee that the integrity of this 
communication has been maintained nor that this communication is free of 
viruses, interceptions or interference.

Reply via email to