Announcement

Collapse
No announcement yet.

DB ConnectionLifecycle Fehler in der Log

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DB ConnectionLifecycle Fehler in der Log

    Hallo mal wieder,
    bei uns kommt es immer wieder in der Log zu Folgender Meldung, mit verschiedenen user-ids:

    Jan 21, 2013 12:39:58 PM com.openexchange.log.internal.LoggerTask call
    WARNING: Logged at: com.openexchange.database.internal.ConnectionLifec ycle.validate(ConnectionLifecycle.java:189)
    DBP-0012 Category=5 Message=Connection used for 2190 milliseconds. exceptionID=1678598872-58293
    com.openexchange.database.schema=oxdatabase_6
    com.openexchange.session.clientId=USM-JSON
    com.openexchange.session.contextId=1
    com.openexchange.session.userId=95
    Throwable occurred: DBP-0012 Category=5 Message=Connection used for 2190 milliseconds. exceptionID=1678598872-58293
    at com.openexchange.database.internal.DBPoolingExcept ionFactory.createException(DBPoolingExceptionFacto ry.java:76)
    at com.openexchange.database.internal.DBPoolingExcept ionFactory.createException(DBPoolingExceptionFacto ry.java:62)
    at com.openexchange.exceptions.Exceptions.create(Exce ptions.java:141)
    at com.openexchange.exceptions.Exceptions.create(Exce ptions.java:145)
    at com.openexchange.exceptions.Exceptions.create(Exce ptions.java:149)
    at com.openexchange.database.DBPoolingExceptionCodes. create(DBPoolingExceptionCodes.java:211)
    at com.openexchange.database.internal.ConnectionLifec ycle.validate(ConnectionLifecycle.java:186)
    at com.openexchange.pooling.ReentrantLockPool.back(Re entrantLockPool.java:179)
    at com.openexchange.pooling.ReentrantLockPool.back(Re entrantLockPool.java:147)
    at com.openexchange.database.internal.ReplicationMoni tor.backAndIncrementTransaction(ReplicationMonitor .java:238)
    at com.openexchange.database.internal.wrapping.JDBC3C onnectionReturner.close(JDBC3ConnectionReturner.ja va:105)
    at com.openexchange.database.internal.DatabaseService Impl.back(DatabaseServiceImpl.java:108)
    at com.openexchange.database.internal.DatabaseService Impl.backReadOnly(DatabaseServiceImpl.java:214)
    at com.openexchange.databaseold.Database.back(Databas e.java:178)
    at com.openexchange.server.impl.DBPool.closeReaderSil ent(DBPool.java:104)
    at com.openexchange.api2.RdbContactSQLImpl.getContact sInFolder(RdbContactSQLImpl.java:380)
    at com.openexchange.ajax.request.ContactRequest.actio nAll(ContactRequest.java:732)
    at com.openexchange.ajax.request.ContactRequest$7.per form(ContactRequest.java:224)
    at com.openexchange.ajax.request.ContactRequest.actio n(ContactRequest.java:299)
    at com.openexchange.ajax.Contact.doGet(Contact.java:1 56)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:707)
    at com.openexchange.ajax.AJAXServlet.service(AJAXServ let.java:434)
    at com.openexchange.ajax.SessionServlet.service(Sessi onServlet.java:259)
    at com.openexchange.ajax.PermissionServlet.service(Pe rmissionServlet.java:82)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.doServletService(AJPv13RequestHandlerImpl.java: 563)
    at com.openexchange.ajp13.AJPv13Request.response(AJPv 13Request.java:138)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.createResponse(AJPv13RequestHandlerImpl.java:36 5)
    at com.openexchange.ajp13.najp.AJPv13ConnectionImpl.c reateResponse(AJPv13ConnectionImpl.java:224)
    at com.openexchange.ajp13.najp.AJPv13Task.call(AJPv13 Task.java:398)
    at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.jav a:138)
    at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.runTask(CustomThreadPoolExecuto r.java:781)
    at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.run(CustomThreadPoolExecutor.ja va:807)
    at java.lang.Thread.run(Thread.java:736)


    Kennt das vieleicht schon jemand?

    Gruß,
    Victor

  • #2
    Hallo,

    das ist lediglich eine Warnmeldung die ausgegeben wird wenn eine Datenbankanfrage länger als 2 Sekunden dauert. Soweit nichts schlimmes, nur sollte man über eine flottere Datenbank nachdenken falls die Werte höher werden oder das häufig auftritt.

    Gruß
    Martin

    Comment

    Working...
    X