SAP Knowledge Base Article - Preview

2223173 - DB transaction logs growing up due to Java Mail Socket timeout


The db transaction logs are slowly growing up and it is observed that there are threads active for a long time using the db transaction logs.

 If we create a db application snapshot we identify the application which is consuming more resources.



If we check the thread activity (by creating a thread dump) at this moment, we can see that the application thread looks similar to this:

"at;[BIII)I(Native Method)
 - locked<0x749e4a150> (a
 at com.sun.mail.util.LineInputStream.readLine()Ljava.lang.String;(
 at com.sun.mail.smtp.SMTPTransport.readServerResponse()I(
 at com.sun.mail.smtp.SMTPTransport.openServer(Ljava.lang.String;I)V(
 at com.sun.mail.smtp.SMTPTransport.protocolConnect(Ljava.lang.String;ILjava.lang.String;Ljava.lang.String;)Z(
 at javax.mail.Service.connect(Ljava.lang.String;ILjava.lang.String;Ljava.lang.String;)V(
 - locked<0x730cd3b78> (a com.sun.mail.smtp.SMTPTransport)
 at javax.mail.Service.connect(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(
 at javax.mail.Service.connect()V(



SAP NetWeaver BPM


Transaction logs, Java Mail Socket timeout, GLX_RRH_TEXTS , KBA , BC-BMT-BPM-SRV , Process Server , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.