Connection refused when connecting SMP 3 to ASE 16

[Former Member]

Hi all,

We're in the process of setting up an installation of SMP 3.0 with Sybase ASE 16 for one of our clients. The final goal is to run the SAP EHS Safety Issue mobile app.

When installing SMP 3.0 with Derby database, I'm able to start the system without any problems. However, when I try the installation configuring the Sybase ASE DB, the service gets stuck on a loop while starting up and doesn't react. I cannot stop it manually nor restart it. The only way to stop it is by restarting the system.

On the Sybase side of things, I can install the ASE without any issues. I have also done all the preliminary steps to create the user and smp3 DB for SMP. I've connected to the DB using this user and I'm able to see that the smp3 DB is created.

When looking at the logs, I can see an exception with the message: Connection refused. Here's an excerpt:

2014 07 28 15:01:10#0-500#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Timer-2,SAPDSMP-5000-smp3-smpserver:com.sap.mobile.platform.server.online.admin.backendconnections.cluster.ClusterBackends,SAPDSMP-4630###Failed creating JDBC connection for SMP_JDBC_PING java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect

  at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)

Any idea what may be causing this issue?

Kind regards,

Omar

[Former Member · Accepted solution]

I continued doing some research and found out that the connection.properties file was getting overwritten after installation with the parameters defined on the installer. The major difference between the parameters was that the password was getting encrypted.

I tested changing the parameters manually to the values that I've entered manually before installation, and the connection to DB succeeded!!!

However, the server didn't start... it got stuck trying to initialize the bundles. Here's the exception that I'm getting now:

2014 07 30 09:16:25#0-500#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Timer-3,SAPDSMP-5000-smp3-gomobile:com.sap.mobile.platform.server.online.admin.logsettings.cluster.ClusterLogSettings,SAPDSMP-32939###Error updating JDBC_PING table java.sql.SQLException: jgroupsping not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).

  at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybStatement.nextResult(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybStatement.nextResult(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybStatement.updateLoop(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybStatement.executeUpdate(Unknown Source)

  at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeUpdate(Unknown Source)

  at org.jgroups.protocols.JDBC_PING.delete(JDBC_PING.java:276)

  at org.jgroups.protocols.JDBC_PING.writeToFile(JDBC_PING.java:243)

  at org.jgroups.protocols.FILE_PING.fetchClusterMembers(FILE_PING.java:73)

  at org.jgroups.protocols.Discovery.sendDiscoveryRequest(Discovery.java:263)

  at org.jgroups.protocols.Discovery.findMembers(Discovery.java:227)

  at org.jgroups.protocols.Discovery.findAllViews(Discovery.java:214)

  at org.jgroups.protocols.Discovery.down(Discovery.java:551)

  at org.jgroups.protocols.FILE_PING.down(FILE_PING.java:101)

  at org.jgroups.protocols.MERGE2$FindSubgroupsTask.findAllViews(MERGE2.java:351)

  at org.jgroups.protocols.MERGE2$FindSubgroupsTask._findAndNotify(MERGE2.java:286)

  at org.jgroups.protocols.MERGE2$FindSubgroupsTask.findAndNotify(MERGE2.java:274)

  at org.jgroups.protocols.MERGE2$FindSubgroupsTask$1.run(MERGE2.java:247)

  at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:277)

  at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:308)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

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

|

[Former Member · Accepted solution]

Hi all,

Now I'm getting a different error when starting the server. 12 Bundles wouldn't start and the only thing I get is an arrow saying (<-- Issue).

Here's the OSGI log:

!ENTRY org.eclipse.osgi 4 0 2014-08-06 10:40:29.710

!MESSAGE SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.agentry.core <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.lcmservices.webapps.http <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.kapsel <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.notifications.http <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.notifications.blackberry <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.online.admin.common <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.proxy.connection.pooling <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.coreservices.appsettings.odata <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.notifications.handler <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.proxy.connectivity.onpremise <-- Issue

SMPServerStatusManager: 2014 08 06 10:40:29.710 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.proxy.core <-- Issue

Has anyone seen this before? We have another group that is facing the issue too...

[Former Member · Accepted solution]

For anyone interested, I found the issue.

For the "Connection refused" issue, it was a mistake on one of my configuration files. I had left the DBNAME without filling out.

For the not initialized bundles issue:

It was the DBMAINTAIN script. You have to run this script AFTER you install the SMP server. If you run it before installing SMP, you'll get this error.

I haven't executed the DBMAINTAIN script since it's optional (you only need to execute it if you want to support Mobiliser apps). So, maybe there's a bug?

Anyways, good luck!

[agentry_src · Accepted solution]

Hi Omar,

Thanks for posting the resolution to the issue!

Cheers, Mike

SAP Customer Experience Group - CEG

[Former Member · Accepted solution]

Hi Omar,

Regarding the mistake that you have mentioned in the configuration. Can you please let me know which config file do we need to mention the db name?

I am currently facing a similar issue:

"

(Oct 30, 2014 6:54:50 AM), , com.installshield.smpserver.event.dialog.swing.PanelDBConfiguration, dbg, Ping failed: 1
(Oct 30, 2014 6:54:50 AM), , com.installshield.smpserver.event.dialog.swing.PanelDBConfiguration, err, Cannot connect to database. Verify that the values entered are correct and that the database is running.
(Oct 30, 2014 6:54:50 AM), , com.installshield.smpserver.event.dialog.swing.PanelDBConfiguration, err, Refer to errors in installation log.
(Oct 30, 2014 6:54:50 AM), , com.installshield.smpserver.event.dialog.swing.PanelDBConfiguration, err, Failed to execute SQL script file Select CLUSTER_NAME, CLUSTER_VERSION, CLUSTER_KEY from SMP_CLUSTER . Error: java.sql.SQLException: SMP_CLUSTER not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).

"

Any inputs around this will be very much  valuable.

Many Thanks in advance!

Regards,

Kartik

[rakshit_doshi]

Dear Omar,

can you check the below

1. If ASE services are running on the host machine on which SMP is installed

2. Can you share the username and password configured in the .DLL file

3. The DLL file after editing

4. Also you can stop the services forcibly by going to services.msc and clicking the SAPSMP3Service. Double click on it and get the name of the service. Go to command prompt(launch as Administrator) nd use the command

sc queryex smpservicename

record the PID number and then run the below command

taskkill /f /pid PIDNO

then go to the SMP3 server installation directory from cmd

cd //installationpath/SAP/Mobile3/Server

and then hit the go command

your service might not appear in the start mode but u can use all the features

p.n before running the go.bat command delete the log folder, work folder under Server folder and the .state folder within the pickup folder

hope this should help

thanks

[Former Member]

Hi Rakshit,

1. Yes, they're running on the same machine.

2. Yesterday I used a different user / pwd combination, but today I'm using the suggested default (gomobile/secret). I'm still getting the same error. I'm attaching the log files and scripts.

3. Attached.

4. Right now the service is stopped, but I'll try starting it using the go command.

Regards,

Omar

SAPDSMP-smp-server.log.zip

001_SMP3_drop_and_create_user.DDL.txt.zip

[Former Member]

I tried using the go.bat to start the server and got the same error. Here's the output:

Using SMP_BASE:    "D:\SAP\MobilePlatform3\Server"

Using SMP_HOME:    "D:\SAP\MobilePlatform3\Server"

Using SMP_OPTS:    " "-Dlog4j.logfiles.path=D:\SAP\MobilePlatform3\Server\log" "

-Dwicket.configuration=development" "-Dmobiliser.home=D:\SAP\MobilePlatform3\Ser

ver" "-DMOBILISER_PROTOCOL=http" "-DMOBILISER_HOSTNAME=localhost" "-DMOBILISER_P

ORT=8080" "-DMOBILISER_HOST=http://localhost:8080" "-Dtracker.defaultHost=localh

ost" "-Dtracker.defaultPort=8080" "-Dtracker.defaultServlet=/mobiliser" "-Dcom.s

ap.mobile.platform.server.home=D:\SAP\MobilePlatform3\Server" "-DPREFS_PROTOCOL=

prefs""

Using JAVA_HOME:   "D:\SAP\MobilePlatform3\sapjvm_7"

"Updating SMP3 Server P2 Repository Locations to: D:\SAP\MobilePlatform3\Server/

p2"

        1 file(s) moved.

        1 file(s) moved.

"Updating server log name to reflect the hostname"

        1 file(s) moved.

java version "1.7.0_25"

Java(TM) SE Runtime Environment (build 7.1.012)

SAP Java Server VM (build 7.1.012 23.5-b11, Aug  8 2013 23:45:34 - 71_REL - optU

- windows amd64 - 6 - bas2:201691 (mixed mode))

D:\SAP\MobilePlatform3\Server>"D:\SAP\MobilePlatform3\sapjvm_7\bin\java.exe" -se

rver  -XtraceFile=log/vm_@PID_trace.log   "-Dlog4j.logfiles.path=D:\SAP\MobilePl

atform3\Server\log" "-Dwicket.configuration=development" "-Dmobiliser.home=D:\SA

P\MobilePlatform3\Server" "-DMOBILISER_PROTOCOL=http" "-DMOBILISER_HOSTNAME=loca

lhost" "-DMOBILISER_PORT=8080" "-DMOBILISER_HOST=http://localhost:8080" "-Dtrack

er.defaultHost=localhost" "-Dtracker.defaultPort=8080" "-Dtracker.defaultServlet

=/mobiliser" "-Dcom.sap.mobile.platform.server.home=D:\SAP\MobilePlatform3\Serve

r" "-DPREFS_PROTOCOL=prefs" -XX:ErrorFile="D:\SAP\MobilePlatform3\Server\log\err

or.log" -XX:HeapDumpPath="D:\SAP\MobilePlatform3\Server\log\heap_dump.hprof" "-X

X:+HeapDumpOnOutOfMemoryError" "-XX:+DisableExplicitGC" "-Xms1024m" "-Xmx2048m"

"-XX:PermSize=256M" "-XX:MaxPermSize=512M" "-Dosgi.requiredJavaVersion=1.6" "-Du

seNaming=osgi" "-Dosgi.install.area=." "-Djava.io.tmpdir=./work/tmp" "-Djava.end

orsed.dirs=lib/endorsed" "-Dorg.eclipse.equinox.simpleconfigurator.exclusiveInst

allation=false" "-Dcom.sap.core.process=ljs_node" "-Declipse.ignoreApp=true" "-D

http.proxyHost=" "-Dhttp.proxyPort=" "-Dhttps.proxyHost=" "-Dhttps.proxyPort=" "

-Dorg.eclipse.net.core.enableProxyService=false" "-Dosgi.noShutdown=true" "-Dosg

i.framework.activeThreadType=normal" "-Dosgi.embedded.cleanupOnSave=true" "-Dosg

i.usesLimit=30" "-Djava.awt.headless=true" "-Dtc.active=true" "-Dmail.mime.encod

eparameters=true" "-Dnet.sf.ehcache.skipUpdateCheck=true" "-Dorg.eclipse.gemini.

blueprint.extender.internal.boot.ChainActivator.disableBlueprint=true" "-Dcom.sy

base365.mobiliser.util.tools.springextender.threadpool.size=20" "-Dcom.sybase365

.mobiliser.util.tools.springextender.shutdown.wait.time=35000" "-Dwicket.configu

ration=deployment" "-DlicenseAccepted=true" "-Dorg.apache.tomcat.util.buf.UDecod

er.ALLOW_ENCODED_SLASH=true" "-Dcom.sybase365.mobiliser.framework.service.config

.MobiliserServiceBeanDefinitionParser.serviceAdviceConfig=audit,security,caller-

audit,responseCode,traceableRequest,responseCode,filterExternal,sessionManagemen

t,txn" "-Dcom.sybase365.mobiliser.framework.service.config.MobiliserServiceBeanD

efinitionParser.internalServiceAdviceConfig=security,responseCode,validation,res

ponseCode,filterInternal,sessionManagement,txn" "-Dcom.sybase365.mobiliser.frame

work.service.config.MobiliserInternalServiceBeanDefinitionParser.responseCodeTyp

e=responseCode" "-Dcom.sybase365.mobiliser.framework.service.config.MobiliserInt

ernalServiceBeanDefinitionParser.auditType=audit" "-Dcom.sybase365.mobiliser.mon

ey.persistence.hibernate.dao.transaction.AuthorisationCodeDaoHbnImpl.max=200" "-

Dcom.sybase365.mobiliser.money.persistence.hibernate.dao.transaction.Authorisati

onCodeDaoHbnImpl.table=SEQ_AUTH_CODES" "-Dcom.sybase365.mobiliser.money.persiste

nce.hibernate.dao.transaction.AuthorisationCodeDaoHbnImpl.column=ID_SEQUENCE" "-

Dcom.sybase365.mobiliser.framework.persistence.hibernate.dialect.useTableBasedSe

quences=true" "-Dcom.sybase365.mobiliser.framework.persistence.hibernate.dialect

.useSequenceNameForTableSequences=true" "-Dcom.sybase365.mobiliser.framework.per

sistence.hibernate.dialect.sequenceTableName=SEQ_TABLE_HILO" "-Dcom.sybase365.mo

biliser.framework.persistence.hibernate.dialect.sequenceTableSequenceNameColumnN

ame=STR_SEQUENCE_NAME" "-Dcom.sybase365.mobiliser.framework.persistence.hibernat

e.dialect.sequenceTableSequenceValueColumnName=ID_SEQUENCE_NEXT_HI_VALUE" "-Dcom

.sybase365.mobiliser.framework.persistence.jdbc.bonecp.pool.lazy=true" "-Dcom.sa

p.mobile.platform.server.notifications.baseurl=https://SAPDSMP.corp.local:8081/"

"-Dcom.sap.mobile.platform.online.proxy.maxresponsesize=-1" "-Dcom.sap.mobile.p

latform.server.connection.pool.idletimeout=600" "-Dcom.sap.mobile.platform.serve

r.connection.timeout=60000" "-Dcom.sap.mobile.platform.server.connection.sotimeo

ut=60000" "-Dcom.sap.mobile.platform.server.enable.statistics=true" "-Dcom.sap.m

obile.platform.server.maximum.clientlogfiles=10" "-Dcom.sap.mobile.platform.serv

er.maximum.connectionPoolSize=5000" "-Dcom.sap.mobile.platform.server.maximum.gz

ipPoolSize=5000" "-Dcom.sybase.security.FactoryRetriever=com.sybase.security.int

egration.tomcat7.TomcatFactoryRetriever" "-Dcom.sap.mobile.platform.server.gener

al.status.SMPServerStatusLogging=false" "-DsecretKey=7hZK9zP3cH" "-DsecretKeylen

gth=128" "-DapnsSocksProxyHost=" "-DapnsSocksProxyPort=" "-Dorg.apache.catalina.

authenticator.Constants.SSO_SESSION_COOKIE_NAME=X-SMP-SESSIDSSO" "-Dosgi.logfile

=./log/osgi.log" "-Djava.net.preferIPv4Stack=true" -classpath "D:\SAP\MobilePlat

form3\Server\lib\org.eclipse.virgo.nano.authentication_3.6.2.RELEASE.jar;D:\SAP\

MobilePlatform3\Server\lib\org.eclipse.virgo.nano.shutdown_3.6.2.RELEASE.jar;D:\

SAP\MobilePlatform3\Server\lib\org.eclipse.virgo.util.env_3.6.2.RELEASE.jar;D:\S

AP\MobilePlatform3\Server\plugins\org.eclipse.equinox.launcher_1.3.0.v20120308-1

358.jar;D:\SAP\MobilePlatform3\Server\plugins\com.sap.db.jdbc_1.0.31.362930.jar;

D:\SAP\MobilePlatform3\Server\plugins\jconnect-osgi_7.0.7.ESD5-1.jar;D:\SAP\Mobi

lePlatform3\Server\plugins\com.sybase365.com.ibm.db2jcc4_9.7.4.jar;D:\SAP\Mobile

Platform3\Server\plugins\oracle-jdbc-osgi_11.2.0.x_3.0.0.M1.jar;D:\SAP\MobilePla

tform3\Server\plugins\com.springsource.org.apache.commons.codec_1.4.0.jar;D:\SAP

\MobilePlatform3\Server\plugins\com.springsource.org.apache.commons.codec_1.6.0.

jar;D:\SAP\MobilePlatform3\Server\plugins\com.springsource.org.apache.commons.la

ng_2.5.0.jar" org.eclipse.equinox.launcher.Main -console localhost:2401

Checking DB...

Failed to connect to the database on startup:java.sql.SQLException: JZ006: Caugh

t IOException: java.net.ConnectException: Connection refused: connect

Checking DB...

Failed to connect to the database on startup:java.sql.SQLException: JZ006: Caugh

t IOException: java.net.ConnectException: Connection refused: connect

[Jitendra_Kansal]

After running go.bat command you should see successful message as per below screenshot:

Can you restart SMP server machine and then try?

[rakshit_doshi]

Dear Omar,

Even i was facing the same error earlier,

This is how i resolved it.

Reinstalled ASE Database and in the DLL file changed the default parameters of go mobile and secret with my username and password.

And also while restarting the services with go.bat command you need to delete these folders prior to running the command

the log folder and the work folder (under server folder) and the .state folder under pickup folder

While deleting the log folder you might face a warning that its in use.

Go to Taskmanager and check all the processes for all the user.

For smp3ServiceUser terminate the java.exe process and then try deleting the log folder

Hope this helps,

Thanks,

Regards,

Rakshit Doshi

[Former Member]

Hi Jitendra,

Thanks for your reply.

I've already restarted the SMP server machine and the SMP Windows Service multiple times and I'm getting the same error. I've also done the installation a couple of times, one with the default user for the DB and one with a user account I created. Still the same error.

I'm wondering if it has to do with the version of ASE. Currently I'm using version 16, but I've seen on many threads that people are using 15.7. Could this be the issue?

Regards,

Omar

[Former Member]

Hi Rakshit,

I've done as you suggested previously (deleting the folders and using the go.bat command) and I'm still getting the same error.

One question, which version of ASE are you using? Is it 15.7 or 16?

Regards,

Omar

[rakshit_doshi]

Dear Omar,

I am using ASE 16 with SMP 3.0.3

While Installation of SMP Server were you able to communicate to the ASE where you enter the ASE Database properties.

I hope you first installed the ASE Database and then Installed SMP.

What i understand is that you changed the ASE User parameters but the SMP Server is still using the old parameters to communicate.

Hence the ping is failing.

What i can advice is do a fresh installation of both (ASE and SMP)

Hope this helps,

Thanks,

Best Regards,

Rakshit Doshi