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

Jcontrol dies with exitcode = 66

Hi,

After applying java kernel & SP patches using JSPM, got a error message that deployment was successful but unable to start J2EE engine..

Tried starting manually but jcontrol died with exit hook called rc=66

SAPCRM2007/SQLSERVER2K5/WIN2K3

Attaching here logs of jcontrol,jcmon,bootstrap,server0..

Please let me know your thoughts..

dev_jcontrol....

-


trc file: "E:\usr\sap\QAS\JC00\work\dev_jcontrol", trc level: 1, release: "700"

-


node name : jcontrol

pid : 2792

system name : QAS

system nr. : 00

started at : Wed Oct 08 12:50:38 2008

arguments :

arg[00] : E:\usr\sap\QAS\JC00\exe\jcontrol.EXE

arg[01] : pf=E:\usr\sap\QAS\SYS\profile\QAS_JC00_sap-xp-q01

[Thr 3008] Wed Oct 08 12:50:38 2008

[Thr 3008] *** WARNING => INFO: Unknown property [instance.box.number=QASJC00sap-xp-q01] [jstartxx.c 841]

[Thr 3008] *** WARNING => INFO: Unknown property [instance.en.host=sap-xp-q01] [jstartxx.c 841]

[Thr 3008] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]

[Thr 3008] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

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

JStartupReadInstanceProperties: read instance properties [E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties;E:\usr\sap\QAS\JC00\SDM\program\config\sdm_jstartup.properties]

-> ms host : sap-xp-q01

-> ms port : 3901

-> OS libs : E:\usr\sap\QAS\JC00\j2ee\os_libs

-> Admin URL :

-> run mode : normal

-> run action : NONE

-> enabled : yes

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

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

Used property files

-> files [00] : E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

-> files [01] : E:\usr\sap\QAS\JC00\SDM\program\config\sdm_jstartup.properties

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

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

Instance properties

-> ms host : sap-xp-q01

-> ms port : 3901

-> os libs : E:\usr\sap\QAS\JC00\j2ee\os_libs

-> admin URL :

-> run mode : normal

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

-> [00] bootstrap : E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

-> [01] bootstrap_ID3561900 : E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

-> [02] bootstrap_ID3561950 : E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

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

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

Worker nodes

-> [00] ID3561900 : E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

-> [01] ID3561950 : E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

-> [02] sdm : E:\usr\sap\QAS\JC00\SDM\program\config\sdm_jstartup.properties

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

[Thr 3008] JControlExecuteBootstrap: execute bootstrap process [bootstrap]

[Thr 3008] [Node: bootstrap] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_16-x64

[Thr 3008] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\QAS\JC00\exe\jvmx.jar

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

JStartupIReadSection: read node properties [bootstrap]

-> node name : bootstrap

-> node type : bootstrap

-> node execute : yes

-> java path : C:\j2sdk1.4.2_16-x64

-> java parameters : -Djco.jarm=1

-> java vm version : 1.4.2_16-b05

-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : amd64

-> heap size : 256M

-> root path : E:\usr\sap\QAS\JC00\j2ee\cluster

-> class path : .\bootstrap\launcher.jar

-> OS libs path : E:\usr\sap\QAS\JC00\j2ee\os_libs

-> main class : com.sap.engine.offline.OfflineToolStart

-> framework class : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path : E:\usr\sap\QAS\JC00\exe\jstartup.jar;E:\usr\sap\QAS\JC00\exe\jvmx.jar

-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0035619

-> debuggable : yes

-> debug mode : no

-> debug port : 60000

-> shutdown timeout : 120000

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

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

JControlStartJLaunch: program = E:\usr\sap\QAS\JC00\exe\jlaunch.exe

-> arg[00] = E:\usr\sap\QAS\JC00\exe\jlaunch.exe

-> arg[01] = pf=E:\usr\sap\QAS\SYS\profile\QAS_JC00_sap-xp-q01

-> arg[02] = -DSAPINFO=QAS_00_bootstrap

-> arg[03] = -nodeId=-1

-> arg[04] = -file=E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties

-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2792

-> arg[06] = -nodeName=bootstrap

-> arg[07] = -jvmOutFile=E:\usr\sap\QAS\JC00\work\jvm_bootstrap.out

-> arg[08] = -stdOutFile=E:\usr\sap\QAS\JC00\work\std_bootstrap.out

-> arg[09] = -locOutFile=E:\usr\sap\QAS\JC00\work\dev_bootstrap

-> arg[10] = -mode=BOOTSTRAP

-> arg[11] = pf=E:\usr\sap\QAS\SYS\profile\QAS_JC00_sap-xp-q01

-> lib path = PATH=C:\j2sdk1.4.2_16-x64\jre\bin\server;C:\j2sdk1.4.2_16-x64\jre\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_16-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;E:\usr\sap\QAS\SYS\exe\uc\NTAMD64;E:\usr\sap\QAS\SYS\exe\uc\NTAMD64

-> exe path = PATH=C:\j2sdk1.4.2_16-x64\bin;E:\usr\sap\QAS\JC00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_16-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;E:\usr\sap\QAS\SYS\exe\uc\NTAMD64;E:\usr\sap\QAS\SYS\exe\uc\NTAMD64

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

[Thr 3008] Wed Oct 08 12:50:59 2008

[Thr 3008] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642]

[Thr 3008] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)

[Thr 3008] JControlCloseProgram: started (exitcode = 66)

[Thr 3008] JControlCloseProgram: good bye... (exitcode = 66)

BOOTSTRAP....

[Oct 8, 2008 12:07:00 PM ] [Bootstrap module]> Problem occurred while performing synchronization.

[Oct 8, 2008 12:50:41 PM ] -


[Oct 8, 2008 12:50:41 PM ] Bootstrap MODE:

[Oct 8, 2008 12:50:41 PM ] <INSTANCE GLOBALS>

[Oct 8, 2008 12:50:41 PM ] determined by parameter [ID0035619].

[Oct 8, 2008 12:50:41 PM ] -


[Oct 8, 2008 12:50:45 PM ] Instance [ID35619] will run in [normal] mode, performing action [NONE]

[Oct 8, 2008 12:50:45 PM ] Discovered property [instance.en.port] with value [3201] !

[Oct 8, 2008 12:50:45 PM ] Discovered property [instance.en.host] with value [sap-xp-q01] !

[Oct 8, 2008 12:50:45 PM ] Synchronizing file [.\.hotspot_compiler].

[Oct 8, 2008 12:50:45 PM ] ...Synched ok!

[Oct 8, 2008 12:50:45 PM ] Synchronizing file [..\..\SDM\program\.hotspot_compiler].

[Oct 8, 2008 12:50:45 PM ] ...Synched ok!

[Oct 8, 2008 12:50:45 PM ] * Synchronizing native files...

[Oct 8, 2008 12:50:45 PM ] Synchronizing file [.\..\os_libs\FontManagerService_native.zip].

[Oct 8, 2008 12:50:54 PM ] Error synchronizing file [.\..\os_libs\FontManagerService_native.zip].

com.sap.engine.frame.core.configuration.InvalidPersistentDataStreamException: Could not get file from DB.

at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:84)

at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)

at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)

at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)

at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)

at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:708)

at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:200)

at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:993)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:972)

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.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by:

com.microsoft.sqlserver.jdbc.SQLServerException: The system is out of memory. Use server side cursors for large result sets:null. Result set size:112,526,773. JVM total memory size:259,522,560.

at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)

at com.microsoft.sqlserver.jdbc.DBComms.receive(Unknown Source)

at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)

at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedStatementExecutionRequest.executeStatement(Unknown Source)

at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)

at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(Unknown Source)

at com.microsoft.sqlserver.jdbc.SQLServerStatement.doCursorFetch(Unknown Source)

at com.microsoft.sqlserver.jdbc.ServerFetchBuffer.doServerFetch(Unknown Source)

at com.microsoft.sqlserver.jdbc.ServerFetchBuffer.forward(Unknown Source)

at com.microsoft.sqlserver.jdbc.ServerFetchBuffer.relative(Unknown Source)

at com.microsoft.sqlserver.jdbc.PositionedCursor.positionedRelative(Unknown Source)

at com.microsoft.sqlserver.jdbc.PositionedCursor.next(Unknown Source)

at com.microsoft.sqlserver.jdbc.ForwardOnlyDynamicServerCursor.next(Unknown Source)

at com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(Unknown Source)

at com.sap.sql.jdbc.basic.BasicResultSet.next(BasicResultSet.java:61)

at com.sap.sql.jdbc.direct.DirectResultSet.next(DirectResultSet.java:132)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessMSSQL.getFileEntry(DBAccessMSSQL.java:68)

at com.sap.engine.core.configuration.impl.persistence.rdbms.FileLoader.getInputStream(FileLoader.java:33)

at com.sap.engine.core.configuration.impl.PersistentDataInputStream.getStream(PersistentDataInputStream.java:81)

at com.sap.engine.core.configuration.impl.PersistentDataInputStream.read(PersistentDataInputStream.java:135)

at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:245)

at com.sap.engine.bootstrap.Synchronizer.getFile(Synchronizer.java:216)

at com.sap.engine.bootstrap.Synchronizer.synchronizeFile(Synchronizer.java:151)

at com.sap.engine.bootstrap.Bootstrap.getOSDependentFiles(Bootstrap.java:708)

at com.sap.engine.bootstrap.Bootstrap.synchInstanceGlobals(Bootstrap.java:200)

at com.sap.engine.bootstrap.Bootstrap.makeUpdate(Bootstrap.java:993)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:972)

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.offline.OfflineToolStart.main(OfflineToolStart.java:81)

SERVER0 LOG.....

#

#1.5 #000C29701B8A0082000001AA000004E8000458C1FD95AA83#1223490112316#/System/Server##com.sap.engine.services.connector#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.connector#Java#connector_0501#com.sap.engine.services.connector.ConnectorResourceBundle#"" is closed. Possible reasons: 1) connector "" is stopped or not started, 2) Connector service is stopped or has not been started.#2#ConnectionManager#SAPQASDB# #1.5 #000C29701B8A0082000001AD000004E8000458C1FD95AD10#1223490112316#/System/Server##com.sap.engine.services.dbpool#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.dbpool#Java#dbpool_0300#com.sap.engine.services.dbpool.DBPoolResourceBundle# in method : #3#ResourceException#ConnectionFactoryImpl.getConnection()#com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started.# #1.5 #000C29701B8A0082000001B1000004E8000458C1FD95B13F#1223490112316#/System/Server##com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor#Plain###ERROR_ACQUIRE_CONNECTION com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92) at com.sap.caf.eu.gp.base.db.TransactionController.openTransaction(TransactionController.java:159) at com.sap.caf.eu.gp.model.queue.QueueFactory.readQueueItemIdentifier(QueueFactory.java:1744) at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueFactory.getNextQueueItemID(NotificationQueueFactory.java:335) at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor.run(NotificationQueueProcessor.java:135) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59) at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89) ... 8 more Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started. at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51) ... 9 more # #1.5 #000C29701B8A0082000001B2000004E8000458C1FD95B303#1223490112316#/System/Server##com.sap.engine.services.connector#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.connector#Java#connector_0501#com.sap.engine.services.connector.ConnectorResourceBundle#"" is closed. Possible reasons: 1) connector "" is stopped or not started, 2) Connector service is stopped or has not been started.#2#ConnectionManager#SAPQASDB#

#1.5 #000C29701B8A0082000001B5000004E8000458C1FD95B767#1223490112316#/System/Server##com.sap.engine.services.dbpool#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.dbpool#Java#dbpool_0300#com.sap.engine.services.dbpool.DBPoolResourceBundle# in method : #3#ResourceException#ConnectionFactoryImpl.getConnection()#com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started.# #1.5 #000C29701B8A0082000001B9000004E8000458C1FD95BE19#1223490112316#/System/Server##com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor#Plain###ERROR_ACQUIRE_CONNECTION com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92) at com.sap.caf.eu.gp.base.db.TransactionController.openTransaction(TransactionController.java:159) at com.sap.caf.eu.gp.model.queue.QueueFactory.readQueueItemIdentifier(QueueFactory.java:1744) at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueFactory.getNextQueueItemID(NotificationQueueFactory.java:335) at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor.run(NotificationQueueProcessor.java:135) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59) at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89) ... 8 more Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started. at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51) ... 9 more # #1.5 #000C29701B8A0082000001BA000004E8000458C1FD95C0A6#1223490112316#/System/Server##com.sap.engine.services.connector#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.connector#Java#connector_0501#com.sap.engine.services.connector.ConnectorResourceBundle#"" is closed. Possible reasons: 1) connector "" is stopped or not started, 2) Connector service is stopped or has not been started.#2#ConnectionManager#SAPQASDB# #1.5 #000C29701B8A0082000001BD000004E8000458C1FD95C58A#1223490112316#/System/Server##com.sap.engine.services.dbpool#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.dbpool#Java#dbpool_0300#com.sap.engine.services.dbpool.DBPoolResourceBundle# in method : #3#ResourceException#ConnectionFactoryImpl.getConnection()#com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started.# #1.5 #000C29701B8A0082000001C1000004E8000458C1FD95CEA7#1223490112331#/System/Server##com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor#Plain###ERROR_ACQUIRE_CONNECTION com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92) at com.sap.caf.eu.gp.base.db.TransactionController.openTransaction(TransactionController.java:159) at com.sap.caf.eu.gp.model.queue.QueueFactory.readQueueItemIdentifier(QueueFactory.java:1744) at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueFactory.getNextQueueItemID(NotificationQueueFactory.java:335) at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueProcessor.run(NotificationQueueProcessor.java:135) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59) at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89) ... 8 more Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started. at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51) ... 9 more # #1.5 #000C29701B8A0082000001C2000004E8000458C1FD978B66#1223490112425#/System/Server##com.sap.engine.services.connector#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.connector#Java#connector_0501#com.sap.engine.services.connector.ConnectorResourceBundle#"" is closed. Possible reasons: 1) connector "" is stopped or not started, 2) Connector service is stopped or has not been started.#2#ConnectionManager#SAPQASDB# #1.5 #000C29701B8A0082000001C5000004E8000458C1FD984BCE#1223490112488#/System/Server##com.sap.engine.services.dbpool#J2EE_GST_QAS#0#####SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#com.sap.engine.services.dbpool#Java#dbpool_0300#com.sap.engine.services.dbpool.DBPoolResourceBundle# in method : #3#ResourceException#ConnectionFactoryImpl.getConnection()#com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQASDB" is stopped or not started, 2) Connector service is stopped or has not been started.#

#1.5 #000C29701B8A007F0000005B000004E8000458C1FD986124#1223490112488#/System/Server##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GST_QAS#0#####Thread[Thread-226,5,main]##0#0#Info#1#com.sap.engine.core.thread.impl3.ThreadManagerImpl#Plain###ThreadManager stopped.#

JCMON..

-


trc file: "E:\usr\sap\QAS\JC00\work\dev_jcmon", trc level: 1, release: "700"

-


node name : jcmon

pid : 4820

system name : QAS

system nr. : 00

started at : Wed Oct 08 11:27:09 2008

arguments :

arg[00] : E:\usr\sap\QAS\JC00\exe\jcmon.exe

arg[01] : pf=E:/usr/sap/QAS/SYS/profile/QAS_JC00_sap-xp-q01

[Thr 4968] Wed Oct 08 11:27:09 2008

[Thr 4968] *** WARNING => INFO: Unknown property [instance.box.number=QASJC00sap-xp-q01] [jstartxx.c 841]

[Thr 4968] *** WARNING => INFO: Unknown property [instance.en.host=sap-xp-q01] [jstartxx.c 841]

[Thr 4968] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]

[Thr 4968] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

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

JStartupReadInstanceProperties: read instance properties [E:\usr\sap\QAS\JC00\j2ee\cluster\instance.properties;E:\usr\sap\QAS\JC00\SDM\program\config\sdm_jstartup.properties]

-> ms host : sap-xp-q01

-> ms port : 3901

-> OS libs : E:\usr\sap\QAS\JC00\j2ee\os_libs

-> Admin URL :

-> run mode : normal

-> run action : NONE

-> enabled : yes

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

[Thr 4968] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx.c 228]

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 09, 2008 at 12:52 PM

    Hi Dinakar,

    The problem is bootstrap process in not being able to synchronize the particular file from DB,

    Oct 8, 2008 12:50:54 PM  Error synchronizing file http://...os_libsFontManagerService_native.zip.
    
    com.sap.engine.frame.core.configuration.InvalidPersistentDataStreamException: Could not get file from DB.

    Check the below thread, it might help

    cannot-start-j2ee-engine-after-ads-installation

    Regards,

    Debasis.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 09, 2008 at 01:26 PM

    Hi Dinakar,

    Also check if these below files have been generated at the time of java startup or not. if generated, please check carefully, that will give you the exact problem. (go to the work directory, sort them by modified date and check)

    dev_bootstrap*

    jvm_bootstrap*

    log_bootstrap*

    For troubleshooting, bootstrap issues, you should follow this note

    https://service.sap.com/sap/support/notes/997510

    Regards,

    Debasis.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 09, 2008 at 03:58 PM

    Hi Debasis,

    Thank you very much for your fast reply...

    I checked the dev_bootstrap,jvm_bootstrap, log_bootstrap..

    I checked for Fontmangerservice_native.zip in oslibs folder..

    It was 0 KB in size, i went thru the notes 1143584 & 710146..

    and changed the heap values thru config tool and bounced the sap..but no luck..

    Infact I checked for the same file in DEV box it was 110 MB approx...

    also the folder adssap in QAS is much lower in size compared to DEV box..

    AS Java synchronizes these files from database @ file system level..

    So it could be a permission issue or am I missing any patch for Adobe services..? (ADSSAP SP from 12 to 15 was deployed successfully..)

    Please let me know your inputs..

    Regards,

    Dinakar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 17, 2008 at 01:19 PM

    Hi Dinakar

    Got the exakt same problem when patching to SPS 6 in CRM 2007, SQL server, W2k3. Have changed heap size, turned off safe mode in configtool but so far nothing works.

    I do not now where to change the parameter WAREHOUS;SelectMethod=cursor.

    Have you had any luck with this?

    regards

    Magnus

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 20, 2008 at 10:11 AM

    The solution to my problem: Note 1109274 - New JDBC driver for NetWeaver 7.0 and higher.

    regards

    Magnus

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 20, 2008 at 07:11 PM

    Hi Dinakar,

    Caused by:

    com.microsoft.sqlserver.jdbc.SQLServerException: The system is out of memory. Use server side cursors for large result sets:null. Result set size:112,526,773. JVM total memory size:259,522,560.

    You need to check the above in details. this is where your problem is.

    you need to reduce your heap memory and according please check the other Paramater for JVM.

    Apart from this also check for any latest updates to the JDBC driver if any.

    Please do let me know if this solved you problem.!!!

    Regards,

    Premkishan Chourasia

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 21, 2008 at 03:49 AM

    Guys,

    Increasing the bootstrap memory for dispatcher & server nodes did the trick...

    Debasis, Sergo thanks for your inputs.. 10 o 10 for both of you... 😊

    Regards,

    Dinakar

    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.