portal down

[Former Member]

Hello colleagues,

My SAP is down, in the log show this error,

#1.#0017A4773418012D0000000400000C4A0004A531544E9630#1307531194462#com.sap.engine.services.dbpool##com.sap.engine.services.dbpool#16062488R#48#SAP J2EE Engine JTA Transaction : [6ffffff8cffffffb616025772]#n/a##b4d91e2790f511e0b5750000068cb616#Thread[Agent Heartbeat,5,Agent]##0#0#Error#1#/System/Server#Java#dbpool_0300##ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.#3#ResourceException#ConnectionFactoryImpl.getConnection()#com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.#

#1.#0017A4773418012D0000000500000C4A0004A531544EA28B#1307531194465#com.sap.engine.services.dbpool##com.sap.engine.services.dbpool#16062488R#48#SAP J2EE Engine JTA Transaction : [6ffffff8cffffffb616025772]#n/a##b4d91e2790f511e0b5750000068cb616#Thread[Agent Heartbeat,5,Agent]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)

at com.sap.security.core.persistence.datasource.imp.J2EEConnectionPool.getConnection(J2EEConnectionPool.java:244)

at com.sap.security.core.persistence.datasource.imp.J2EEConnectionPool.getConnection(J2EEConnectionPool.java:188)

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.getConnection(DataBasePersistence.java:3212)

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.populatePrincipalDatabag(DataBasePersistence.java:2098)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.getPrincipalDatabag(PrincipalDatabagFactoryInstance.java:2431)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.getPrincipalDatabags(PrincipalDatabagFactoryInstance.java:3698)

at com.sap.security.core.imp.GroupFactory.getReadonlyGroups(GroupFactory.java:451)

at com.sap.security.core.imp.GroupFactory.getReadonlyGroups(GroupFactory.java:381)

at com.sap.security.core.imp.PrincipalFactory.getReadonlyPrincipals(PrincipalFactory.java:1534)

at com.sap.security.core.imp.PrincipalFactory.getReadonlyPrincipals(PrincipalFactory.java:1765)

at com.sap.security.core.imp.AbstractPrincipal.getParentsOfType(AbstractPrincipal.java:1027)

at com.sap.security.core.imp.AbstractPrincipal.getRoles(AbstractPrincipal.java:844)

at com.sap.security.core.imp.AbstractPrincipal.getRoles(AbstractPrincipal.java:835)

at com.sap.security.core.imp.User.calculatePermissions(User.java:1202)

at com.sap.security.core.imp.User.getPermissionsData(User.java:1166)

at com.sap.security.core.imp.User.hasPermission(User.java:842)

at com.sap.security.core.imp.UserWrapper.hasPermission(UserWrapper.java:203)

at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:73)

at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)

at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:233)

at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

at com.wily.introscope.agent.jmx.AJMXDataView.IJMXDataView_update(AJMXDataView.java:110)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor.pollViews(IntroscopeProtocolAdaptor.java:617)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor.findServersAndPollViews(IntroscopeProtocolAdaptor.java:518)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor.access$200(IntroscopeProtocolAdaptor.java:52)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor$FindServersAndPollViewsAction.run(IntroscopeProtocolAdaptor.java:450)

at java.security.AccessController.doPrivileged(Native Method)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor.setContextAndPoll(IntroscopeProtocolAdaptor.java:405)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor.access$1200(IntroscopeProtocolAdaptor.java:52)

at com.wily.introscope.agent.jmx.IntroscopeProtocolAdaptor$IntroscopeProtocolAdaptorHeartbeatBehavior.ITimestampedRunnable_execute(IntroscopeProtocolAdaptor.java:1247)

at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:944)

at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:489)

at com.wily.util.heartbeat.IntervalHeartbeat.access$300(IntervalHeartbeat.java:28)

at com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:665)

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

Regards

[markus_doehr2 · Accepted solution]

> #1.#0017A4773418012D0000000400000C4A0004A531544E9630#1307531194462#com.sap.engine.services.dbpool##com.sap.engine.services.dbpool#16062488R#48#SAP J2EE Engine JTA Transaction : [6ffffff8cffffffb616025772]#n/a##b4d91e2790f511e0b5750000068cb616#Thread[Agent Heartbeat,5,Agent]##0#0#Error#1#/System/Server#Java#dbpool_0300##ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system

What happened prior to this problem? Patch installations? JDK upgrades? Reboot?

Is your database up and running?

Markus

[Former Member · Accepted solution]

What happened prior to this problem?

The instance is working suddenly the instance JC10 stop.

Patch installations?

We have not installed patches.

JDK upgrades?

We have not installed JDK.

Reboot?

The system HP-UX is impossible reboot

Is your database up and running?

My database is up and runing

[benjamin_houttuin · Accepted solution]

Hi Victor,

Did you already tried one of the hints (or maybe all of them):

1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine),

2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or

3) The specified time to wait for connection is not enough according to the pool size and current load of the system

Another thing you could try is to temporary remove the Wily Introscope parameters from the j2ee engine start parameters.

And check if the system wants to start then. (so you can isolate the issue)

Cheers,

B