SAP WM 6.1 with SMP 3.0 SP04 not loading on ATE/device.

[razarizvi]

Hello All -

I am working on implementing SAP WM 6.1 with the SMP 3.0 SP 04 server. The application has been deployed & configured on the server. I can also get to the page for application test

https://host.fqdn.com:8082/SAPWM

where I get a response "I am here". I have downloaded & installed the smp_crt on the laptop before running the test.

When testing the application from the ATE 7.0.x the user is able to login to the app itself, however the loading and rebuilding index definitions just takes too long to finish and is stuck at this stage for hours before I have to kill the app. (See screen shot below).

The backed is IS-U EHP7 of ERP 6.0 and all the necessary config and data exist on the ECC. There are just a few records on the backend.

Any clues to resolve this is much appreciated.

Thanks

Raza.

[bill_froelich · Accepted solution]

If you are using SMP 3.0 SP04 or higher you need to make sure you are using a client from the SDK SP05 or later.  This would apply to the test environment as well.

Can you confirm what version of the client you are trying to use?

--Bill

[razarizvi]

Now I am getting the following error with a heap dump on the host

2014 11 25 17:58:25#0-500#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Timer-5,jdbc:derby:./db/derby/smp3:com.sap.mobile.platform.server.proxy.configuration.cluster.ClusterApplications,host-20775####null#null#null#error#Other#null#null#1791bce4-a0bc-403d-9b79-4924ef567d52#null#1416974305180#null#org.jgroups.protocols.SMP_JDBC_PING:getConnection#Failed creating JDBC connection for SMP_JDBC_PING Connection refused : java.lang.OutOfMemoryErrorjava.sql.SQLNonTransientConnectionException: Connection refused : java.lang.OutOfMemoryError

2014 11 25 17:58:25#0-500#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Timer-5,jdbc:derby:./db/derby/smp3:com.sap.mobile.platform.server.proxy.configuration.cluster.ClusterApplications,host-20775####null#null#null#error#Other#null#null#1791bce4-a0bc-403d-9b79-4924ef567d52#null#1416974305180#null#org.jgroups.protocols.SMP_JDBC_PING:getConnection#Failed creating JDBC connection for SMP_JDBC_PING Connection refused : java.lang.OutOfMemoryErrorjava.sql.SQLNonTransientConnectionException: Connection refused : java.lang.OutOfMemoryError

org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)

org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)

org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

org.apache.derby.impl.jdbc.EmbedConnection.<clinit>(Unknown Source)

org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)

org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)

org.eclipse.gemini.jpa.PlainDriverDataSource.getConnection(PlainDriverDataSource.java:53)

org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:132)

org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)

org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:330)

org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:295)

org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect(DatasourceAccessor.java:418)

org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection(ConnectionPool.java:216)

org.eclipse.persistence.sessions.server.ExternalConnectionPool.startUp(ExternalConnectionPool.java:146)

org.eclipse.persistence.sessions.server.ServerSession.connect(ServerSession.java:484)

org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:734)

org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:217)

org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:542)

org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:186)

org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getMetamodel(EntityManagerFactoryDelegate.java:602)

org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getMetamodel(EntityManagerFactoryImpl.java:516)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

java.lang.reflect.Method.invoke(Method.java:606)

org.eclipse.gemini.jpa.proxy.EMFServiceProxyHandler.invoke(EMFServiceProxyHandler.java:85)

com.sun.proxy.$Proxy5.getMetamodel(Unknown Source)

com.sap.espmprocessing.util.Activator.getOrCreateEMF(Activator.java:69)

com.sap.espmprocessing.util.Activator.start(Activator.java:41)

org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

java.security.AccessController.doPrivileged(Native Method)

org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)

org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)

org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)

org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)

org.eclipse.osgi.framework.internal.core.PackageAdminImpl.resumeBundles(PackageAdminImpl.java:312)

org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:556)

org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:251)

org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:174)

java.lang.Thread.run(Thread.java:791)

#null#497#null#1#null |

2014 11 25 17:58:25#0-500#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Timer-5,jdbc:derby:./db/derby/smp3:com.sap.mobile.platform.server.proxy.configuration.cluster.ClusterApplications,host-20775###Failed to store PingData in database |

-----------  H E A P   C H E C K  -----------"

Suspension of 374 threads failed.

79 Java thread local allocation buffers currently in use.

   1. TLAB: start=0x00000000f55668c0, top=0x00000000f55668e8, end=0x00000000f5567e78, thread=0x000000001d555800

   2. TLAB: start=0x00000000f57a54a0, top=0x00000000f57a54f0, end=0x00000000f57a5cc0, thread=0x0000000022a90000"