Skip to Content
author's profile photo Former Member
Former Member

DTRServlet - 500 Internal Server Error is returned for HTTP request

Hi everybody,

I've got a Problem with my DTR.

Recently we've set up the new CE 7.2 System.

The DTR has run until about 3 hours ago.

I don't know what I've done that this error occurs, but I'm nearly shure that I haven't done anything that depends on the dtr.

I went through the set up wizzard of "Connect Design Time for Visual Composer with NWDI" again, but nothing changed.

Can you please help me with this issue?!

Thank you and best regards

julian

_________________________________________________________________________________________________

This is the text from the application log:

_________________________________________________________________________________________________

#2.0 #2010 08 20 15:02:47:398#+0200#Info#/Applications/DTR/Lifecycle#

lifecycle.startApplicationInitialisation#BC-CTS-DTR-SRV#sap.com/tcdtrenterpriseapp#005056BA56AE050000000000000010D8#1694250000000004#sap.com/tcdtrenter

priseapp#com.tssap.dtr.server.servlet.WebdavServlet#Guest#0##F30581C3AC5A11DFCAED00000019DA2A#f30581c3ac5

a11dfcaed00000019da2a#f30581c3ac5a11dfcaed00000019da2a#0#Thread[HTTP Worker [@1902689675],5,Dedicated_Application_Thread]#Plain#com.tssap.dtr.server.deltav.resources.log_messages#

Starting initialisation of DTR application.#

#2.0 #2010 08 20 15:02:47:405#+0200#Fatal#/Applications/DTR/Lifecycle#

com.sap.DI.dtr.090009#BC-CTS-DTR-SRV#sap.com/tcdtrenterpriseapp#005056BA56AE050000000001000010D8#1694250000000004#sap.com/tcdtrente

rpriseapp#com.tssap.dtr.server.servlet.WebdavServlet#Guest#0##F30581C3AC5A11DFCAED00000019DA2A#f30581c3ac5

a11dfcaed00000019da2a#f30581c3ac5a11dfcaed00000019da2a#0#Thread[HTTP Worker [@1902689675],5,Dedicated_Application_Thread]#Plain#com.tssap.dtr.server.deltav.resources.log_messages#

Initialisation of DTR application failed. Please refer to SAP note 774339 for more details on how to analyze the error condition.#

_________________________________________________________________________________________________

And this is the message from the Default Trace: (not all, that didn't fit in this thread)

_________________________________________________________________________________________________

#2.0 #2010 08 20 15:13:49:744#+0200#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

com.sap.ASJ.web.000137#BC-CTS-DTR-SRV#sap.com/tcdtrenterpriseapp#005056BA56AE05D600000002000010D8#1694250000000004#sap.com/tcdtrent

erpriseapp#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##7F3F3C0AAC5A11DF869E00000019D

A2A#7db05704ac5c11dfa28500000019da2a#7db05704ac5c11dfa28500000019da2a#0#Thread[HTTP Worker [@236433360],5,Dedicated_Application_Thread]#Plain##

Cannot process an HTTP request to servlet [DTRServlet] in [dtr] web application.

[EXCEPTION]

javax.servlet.ServletException: WebdavServlet.init() failed : com.tssap.dtr.pvc.basics.cluster.TaskFailedException: Connection is invalid.

at com.tssap.dtr.server.servlet.WebdavServlet.init(WebdavServlet.java:471)

at javax.servlet.GenericServlet.init(GenericServlet.java:270)

at com.sap.engine.services.servlets_jsp.server.application.WebComponents.getServlet(WebComponents.java:864)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:326)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

..............

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: com.tssap.dtr.pvc.basics.cluster.TaskFailedException: Connection is invalid.

at com.tssap.dtr.pvc.basics.cluster.ClusterExclusiveTaskRunner.start(ClusterExclusiveTaskRunner.java:54)

at com.tssap.dtr.server.deltav.impl.Repository.initialize(Repository.java:643)

at com.tssap.dtr.server.deltav.impl.Repository.initialize(Repository.java:613)

at com.tssap.dtr.server.servlet.WebdavServlet.initializeDeltaV(WebdavServlet.java:556)

at com.tssap.dtr.server.servlet.WebdavServlet.init(WebdavServlet.java:462)

... 36 more

Caused by: com.tssap.dtr.pvc.util.sql.SQLRuntimeException: Connection is invalid.

at com.tssap.dtr.pvc.util.sql.GenericStatementProvider.prepareStatement(GenericStatementProvider.java:75)

at com.tssap.dtr.pvc.util.sql.GenericStatementProvider._getPreparedStatement(GenericStatementProvider.java:62)

at com.tssap.dtr.pvc.util.sql.GenericStatementProvider.getPreparedStatement(GenericStatementProvider.java:44)

at com.tssap.dtr.pvc.basics.persistence.PersistentClass.getPreparedStatement(PersistentClass.java:148)

at com.tssap.dtr.pvc.repository.TaggedValuePersistentClass.loadTaggedValue(TaggedValuePersistentClass.java:113)

at com.tssap.dtr.pvc.repository.TaggedValueTransientClass.loadTaggedValue(TaggedValueTransientClass.java:51)

at com.tssap.dtr.pvc.repository.RepositoryManager._checkDbInitialization(RepositoryManager.java:288)

at com.tssap.dtr.pvc.repository.RepositoryManager.isDbInitialized(RepositoryManager.java:1128)

at com.tssap.dtr.server.deltav.impl.Repository.initializeDeltaV(Repository.java:558)

at com.tssap.dtr.server.deltav.impl.Repository$1.run(Repository.java:645)

at com.tssap.dtr.pvc.basics.cluster.ClusterExclusiveTaskRunner.startTask(ClusterExclusiveTaskRunner.java:65)

at com.tssap.dtr.pvc.basics.cluster.ClusterExclusiveTaskRunner.start(ClusterExclusiveTaskRunner.java:51)

... 40 more

Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: Connection is invalid.

at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfInvalid(ConnectionHandle.java:652)

at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfValid(ConnectionHandle.java:639)

at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:113)

at com.tssap.dtr.pvc.basics.transaction.SharedConnection.prepareStatement(SharedConnection.java:131)

at com.tssap.dtr.pvc.util.sql.GenericStatementProvider.prepareStatement(GenericStatementProvider.java:73)

... 51 more

#

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Sep 08, 2010 at 03:54 PM

    I know someone who just discovered a similar issue like this recently. I let him know.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 08, 2010 at 04:49 PM

    Hello Julian

    This is a known problem.

    Cause

    - A user may have been added to a group in another ldap tree with a name, that is already existing.

    - When DTR retrieves the group from UME, we get 2 similar group names, but the groups may be different.

    - DTR cannot handle this and throws "Internal Server error"

    Resolution

    If you change parameter "ume.ldap.unigue_grup_attribute" to 'uid', DTR doesn't use the groupname,

    but the group-uid, therefore the group is unique.

    1. open Visual Administrator

    2. choose Services

    3. choose UME Provider

    4. Reset "ume.ldap.unigue_grup_attribute" with 'uid'

    5. restart the system

    Thanks

    Kenny.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 09, 2010 at 11:32 AM

    Hi,

    now there's a KBA released about it:

    http://service.sap.com/sap/support/notes/1506882

    Regards,

    Ervin

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.