on 04-07-2014 6:35 PM
Hello,
After a successful installation of SMP 3.0 on Linux Suse Server 11 I tried to start the SMP server using via the command prompt: ./daemon.sh start
All the initialization steps goes well expect the last one:
SMPServerStatusManager: 49 of 50 tracked bundles have initialized.
In the log there is the following error:
2014 04 07 12:58:10#0-400#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager:49 of 50 tracked bundles have initialized.|
2014 04 07 12:58:11#0-400#ERROR#org.osgi.service.log.LogService##anonymous#org.eclipse.virgo.medic.log.osgi.OSGiLogServiceListener@78a7f540###Bundle
org.eclipse.osgi_3.8.1.v20120830-144521, SMPServerStatusManager: 2014
0407 12:58:11.053 Bundles (and their services) not yet initialized:
com.sap.mobile.platform.server.agentry.core <-- Issue
Any idea?
After checking the whole log file, I notice there is lot of error regarding the agentry components....
Cheers
Fouad
Message was edited by: Michael Appleby
I deployed SMP 3.0 in Suse 11 SP3 and everything is working fine now.
Cheers,
Fouad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have exact the same error using a local development installation of SMP 3.0 SP04 PL1 on Windows 7.
My SMP was working initially and I was using it for a while without any problems. At the moment I get the same error Fouad pasted in his question.
Can someone describe the cause of this error and how to avoid it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.