Dialog queue Standstill - Error while connecting to DB [Task Limit]

[former_member583013]

Hi,

My XI system, which has been successfully running for the past 2 months suddently broke yesterday.

It is a double stack (ABAP+Java) system, running XI/PI 7.0. Using Windows 2003 (64 bit) with MaxDB.

MMC process list:

- Message server is Green

- Dispatcher is: Running but Dialog Queue standstill, J2EE: Some processes running.

-

---

Following is the snapshot from defaultTrace.3.trc file...

#1.5 #001A64C1A27A0000000000140000559000045FBE51647030#1231170920796#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Error while connecting to DB.

=======================================================

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerFactoryImpl.<init>(ConfigurationHandlerFactoryImpl.java:30)

at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:189)

at com.sap.engine.core.configuration.AbstractConfigurationManagerImpl.init(AbstractConfigurationManagerImpl.java:169)

at com.sap.engine.core.Framework.loadSingleManager(Framework.java:577)

at com.sap.engine.core.Framework.loadManagers(Framework.java:255)

at com.sap.engine.core.Framework.start(Framework.java:189)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)

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

Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: Cannot connect to jdbc:sapdb://AYANS02IBMW/DN1 [Task limit].

at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:237)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

... 15 more

-

---

server.0.log file snapshot is here:

#1.5 #001A64C1A27A001E000000140000123400045FCBCFFD9A9E#1231228879348#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_104##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service dbpool started. (1047 ms).#

#1.5 #001A64C1A27A001F000000000000123400045FCBCFFDB5E0#1231228879348#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_97##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service UT started. (0 ms).#

#1.5 #001A64C1A27A0020000000000000123400045FCBCFFE47C7#1231228879395#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service caf_eugp_mailcf started. (31 ms).#

#1.5 #001A64C1A27A00210000000C0000123400045FCBD00ADD42#1231228880223#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR connection to partner '127.0.0.1:sapgw00' broken

TIME Tue Jan 06 13:31:20 2009

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -6

MODULE gwxx.c

LINE 391

DETAIL NiIWrite

SYSTEM CALL NiWrite

ERRNO 10054

ERRNO TEXT WSAECONNRESET: Connection reset by peer

COUNTER 1

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR connection to partner '127.0.0.1:sapgw00' broken

TIME Tue Jan 06 13:31:20 2009

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -6

MODULE gwxx.c

LINE 391

DETAIL NiIWrite

SYSTEM CALL NiWrite

ERRNO 10054

ERRNO TEXT WSAECONNRESET: Connection reset by peer

COUNTER 1

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:445)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)

... 6 more

-

---

Other than the above 2 log/trace files, I couldn't find errors in any other logs.

I went thru all SDN posts related to 'Dialog Standstill' and '[Task Limit]'.

I increased the MAXUSERTASKS parameter in MaxDB from 50 to 120. But that didn't solve the problem.

Any help will be greatly appreciated.

Thanks,

Venky.

[p330068]

Hi Venky,

I think the error J2EE: Some processes running and Error while connecting to DB MaxDB.

First thing you need to do that is :

1. check the Java version if it is correct for your installed XI server, then you need to add system variable in the Enviroment variable(My Computer>properties>Advance Tab>here you see Enviroment variable button)

2. you need to check the services in you computer(Control Panel>Administrative tool>Services), check the MaxDB in the list and change thier properties 'automatic' for starting. And also start manually here.

Then after doing above steps, please try to start your server.

Hope this will helps you.

Thanks

Arun

[Former Member]

Hi,

Suggest checking if your MAXDB log files are full.

I had the same issue and changed the log file settings to 'overwrite' (see command below).

To check, use the DBM Command line tool that is installed with MAXDB on your server.

Log into your host and db, then run the following command:

INFO LOG

This will then show you the size of your log files, if they are at 100% you have likely found your error.

To get around this, you can set your logs to overwrite themselves (which means your will not be able to do a log recovery).

The command to do this (again from DBM command line tool is):

db_execute SET LOG AUTO OVERWRITE ON

Regards, W

[former_member583013]

Some additional info...

'server0' is stopped (in MMC -> J2EE process tables).

Following is the Developer Trace for this process:

-

---

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [server0]

**********************************************************************

[Thr 9176] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 9176] Tue Jan 06 14:13:33 2009

[Thr 9176] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 9176] JLaunchISetClusterId: set cluster id 3943150

[Thr 9176] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 9176] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

Tue Jan 06 14:13:35 2009

3.514: [GC 3.514: [DefNew: 87534K->6375K(131328K), 0.0309929 secs] 87534K->6375K(1004800K), 0.0310657 secs]

Tue Jan 06 14:13:37 2009

5.792: [GC 5.792: [DefNew: 93927K->11251K(131328K), 0.0354697 secs] 93927K->11251K(1004800K), 0.0355330 secs]

Tue Jan 06 14:13:39 2009

7.136: [GC 7.136: [DefNew: 98794K->17269K(131328K), 0.0487054 secs] 98794K->17269K(1004800K), 0.0487685 secs]

Tue Jan 06 14:13:40 2009

8.121: [GC 8.121: [DefNew: 104821K->20022K(131328K), 0.0441809 secs] 104821K->20022K(1004800K), 0.0442446 secs]

8.878: [GC 8.878: [DefNew

Tue Jan 06 14:13:41 2009

: 107574K->21552K(131328K), 0.0453561 secs] 107574K->21552K(1004800K), 0.0454087 secs]

9.542: [GC 9.542: [DefNew: 109104K->23560K(131328K), 0.0462656 secs] 109104K->23560K(1004800K), 0.0463198 secs]

9.859: [GC 9.859: [DefNew

Tue Jan 06 14:13:42 2009

: 111112K->23219K(131328K), 0.0430789 secs] 111112K->23219K(1004800K), 0.0431349 secs]

Tue Jan 06 14:13:43 2009

10.942: [GC 10.942: [DefNew: 110771K->26099K(131328K), 0.0471753 secs] 110771K->26099K(1004800K), 0.0472303 secs]

Tue Jan 06 14:13:44 2009

12.188: [GC 12.189: [DefNew: 113651K->28887K(131328K), 0.0584381 secs] 113651K->28887K(1004800K), 0.0584915 secs]

Tue Jan 06 14:13:45 2009

12.977: [GC 12.977: [DefNew: 116439K->29498K(131328K), 0.0583486 secs] 116439K->29498K(1004800K), 0.0584911 secs]

Tue Jan 06 14:13:46 2009

14.835: [GC 14.835: [DefNew

Tue Jan 06 14:13:47 2009

: 117013K->31990K(131328K), 0.0712612 secs] 117013K->31990K(1004800K), 0.0713232 secs]

[Thr 2552] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 2552] ***LOG Q0I=> NiIWrite: WSASend (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 3948]

[Thr 2552] *** ERROR => NiIWrite: SiSendV failed for hdl 0 / sock 6708

(SI_ECONN_BROKEN/10053; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3948]

[Thr 2552] *** ERROR => GwIConnect: GwWrite to localhost / sapgw00 failed, rc: NIECONN_BROKEN [gwxx.c 401]

[Thr 2552] ***LOG S90=> SAP_STINIT3, GwIConnect ( 224) [r3cpic.c 2006]

[Thr 2552]

*****************************************************************************

*

[Thr 2552] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 2552] * ERROR connection to partner '127.0.0.1:sapgw00' broken

[Thr 2552] *

• TIME Tue Jan 06 14:13:47 2009

[Thr 2552] * RELEASE 700

[Thr 2552] * COMPONENT NI (network interface)

[Thr 2552] * VERSION 38

[Thr 2552] * RC -6

[Thr 2552] * MODULE gwxx.c

[Thr 2552] * LINE 391

[Thr 2552] * DETAIL NiIWrite

[Thr 2552] * SYSTEM CALL NiWrite

[Thr 2552] * ERRNO 10053

[Thr 2552] * ERRNO TEXT WSAECONNABORTED: Software caused connection abort

[Thr 2552] * COUNTER 1

[Thr 2552] *

[Thr 2552] *****************************************************************************

[Thr 5960] Tue Jan 06 14:13:48 2009

[Thr 5960] JLaunchIExitJava: exit hook is called (rc = -11113)

*[Thr 5960] ***********************************************************************

ERROR => The Java VM terminated with a non-zero exit code.

Please see SAP Note 943602 , section 'J2EE Engine exit codes'

for additional information and trouble shooting.

[Thr 5960] JLaunchCloseProgram: good bye (exitcode = -11113)

-

---

[Former Member]

Hi, are you trying to check Note 958378 - XI 3.0 J2EE AE: JDBCDriverException with SAP DB

Regards.