WSO2 API Manager 1.6.0 - Distributed environment blocks each other on start

Question

Update #2 to reflect the comments.... I have tried correcting for this issue launching the services varous ways...

#./wso2server.sh start

#./wso2server.sh -Dprofile=api-key-manager

#nohup ./wso2server.sh -Dprofile=api-key-manager &

Unfortuneately the errors have started occurring regardless.

Earlier post below...

Please note this is an edit...didn't want to post yet another question... So now I'm really confused. After upgrading WSO2 AM (API Manager) 1.6.0 and the problem persisting I decided to split up the services into Key Manager, Gateway, Store, and Publisher. So now I have: I have one server running the store and publisher on different ports. I have another server running the gateway and keymanager on different ports.

The first service I started was Key Manager... which failed to start with:

2014-01-22 18:09:41,786 [-] [Timer-2]  WARN CarbonServerManager Carbon initialization is delayed due to the following unsatisfied items:
2014-01-22 18:09:41,788 [-] [Timer-2]  WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.mediation.configadmin-4.2.0
2014-01-22 18:09:41,789 [-] [Timer-2]  WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.apimgt.gateway-1.2.1
2014-01-22 18:09:41,789 [-] [Timer-2]  WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.proxyadmin-4.2.1
2014-01-22 18:09:41,790 [-] [Timer-2]  WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.localentry-4.2.0

Which is confusing to me since the Key Manager should not rely on the other components in AM. It only connects to the APIMGT_DB which I've added in api-manager.xml jdbc/WSO2AM_DB

Any advice?

Usually this issue happens due to lack of performance in terms of memory and network. Can you please try a fresh pack of api manager on the same node (without any configuration changes) and update the question with the results? — DarRay
@DarRay Same issue after installing and config of AM 1.6: 2014-01-22 14:15:50,097 [-] [Timer-2] WARN CarbonServerManager Carbon initialization is delayed due to the following unsatisfied items: WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.mediation.configadmin-4.2.0 WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.apimgt.gateway-1.2.1 WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.proxyadmin-4.2.1 WARN CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.localentry-4.2.0 — Gammonster
When you say split up, did you remove any features from the API Manager. — Kasun Gajasinghe
@KasunBG I did not remove any features. I copied the API Manager zip extraction into different folders (one for gateway, one for key manager). I configured each, and then started using the -Dprofile setting. -Dprofile=api-key-manager — Gammonster
@Gammonster Got it. It starts fine for me with -Dprofile=api-key-manager in AM 1.5. Didn't check the 1.6 yet. I guess you can start the server without specifying the profile for now to continue with the development. — Kasun Gajasinghe

Kasun Gajasinghe Kasun Gajasinghe · Accepted Answer · 2014-02-01T10:25:58

Here is a wild suggestion that you can tryout. I re-produced your issue frequently in APIM 1.6 server start-up, and after this modification I haven't seen this error anymore. So, may be this would work for you too.

Open the jar file, synapse-core_2.1.2.wso2v3.jar, at APIM_HOME/repository/components/plugins/. You can use a archive openers like file-roller.
Open the file at META-INF/MANIFEST.MF.
Search for the text, javax.xml.soap;version="0.0.0" . Replace it with - javax.xml.soap;version="1.0.0" . (The difference is in the version)
Save the file, and restart the server.

WSO2 API Manager 1.6.0 - Distributed environment blocks each other on start

2 Answers