CarbonServerManager Carbon initialization is delayed due to the following unsatisfied items - wso2

Hi I am doing following steps from http://wso2.com/library/articles/2014/02/cloud-to-rdbms-using-wso2-esb/
the following issue happens after installation of Data Service Hosting 4.2.0 and restarted the ESB.
[2017-03-15 11:58:30,385] WARN - CarbonServerManager Carbon initialization is delayed due to the following unsatisfied items:
[2017-03-15 11:58:30,385] WARN - CarbonServerManager Waiting for required OSGiAxis2Service: org.wso2.carbon.dataservices.task-4.4.0
how can I fix or revert it.

What is the ESB version you are using?
If you want to revert you can select it from installed features list and click uninstall

Related

org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.capp.monitor

I am using WSO2 Integration Studio 8.1.0 to develop an API on my machine, and when trying to run on Micro Integrator, I get the following error :
ERROR {Framework} - FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.capp.monitor [170]
Unresolved requirement: Import-Package: org.wso2.carbon.application.deployer
at org.eclipse.osgi.container.Module.start(Module.java:457)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$1.run(ModuleContainer.java:1820)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1813)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1770)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1735)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1661)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
But after the error appears in the console the application runs fine.
Any ideas why I get this error and how to avoid it ?
This issue is happening due to a bug[1] in the Integration Studio. Due to this bug, the Studio was using the configuration of the older MI version to run/debug CApps. To fix this you will need to update the Integration Studio and manually remove some configurations as follows,
Remove the server configurations under ESB Mediation Debugger and Generic Server in Debug Configurations,
If the org.wso2.carbon.capp.monitor-3.0.0 jar is already present in IntegrationStudio/runtime/microesb/dropins folder remove it as well.
Restart the Integration Studio to load the new configurations shipped with the latest updates.
Please refer Get the latest updates to install the latest updates to Integration Studio.
[1] - https://github.com/wso2/api-manager/issues/772
The components of the MI product are activated as OSGI bundles at the kernel level during the server startup process. In this case, the OSGI bundle related to org.wso2.carbon.capp.monitor module is not activated because the org.wso2.carbon.application.deployer module is not available at the time when the OSGI bundle related to org.wso2.carbon.capp.monitor module is activated. As a result, the bundle activation issue will be visible during the initial server startup process.
However, once the bundle related to org.wso2.carbon.application.deployer is successfully activated, the OSGI bundle related to org.wso2.carbon.capp.monitor module will also be successfully re-activated, even if the bundling exception occurred during the initial bundle activation process.
We can check whether the OSGI bundle related to the org.wso2.carbon.capp.monitor module was successfully activated by looking for the org.wso2.carbon.capp.monitor-3.0.0.jar file in the <Integration_STUDIO_INSTALLED_LOCATION>/runtime/microesb/dropins directory after starting the MI server; additionally, the CAR application will not be deployed successfully if the OSGI bundle was not properly activated during the server startup process.
You can also validate it by redeploying the CAR application into the MI server. You will not notice the issue during the CAR application redeployment process because it occurs due to the order in the bundle activation process during the server startup.
This issue has been reported:
https://github.com/wso2/api-manager/issues/772
Please take the latest update by following the official guide:
https://apim.docs.wso2.com/en/latest/integrate/develop/installing-wso2-integration-studio/#get-the-latest-updates
Cheers!
Nadun.

WSO2 waiting for required OSGI services during startup

I'm running WSO2 AM 1.10.0 in cluster node on two virtual machines on my PC (one acting as manager node the other is a worker node). Recently I had to re-install my PC from scratch with Windows 10, and occasionally after restart I receive the following warning messages repeating again and again:
WARN {org.wso2.carbon.application.deployer.internal.AppDeployerServiceComponent}
Waiting for required OSGi services:
org.wso2.carbon.application.deployer.synapse.service.SynapseAppDeployerService,
org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,
WARN {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent}
Waiting for required OSGi services:
org.wso2.carbon.application.deployer.service.CappDeploymentService,
org.wso2.carbon.server.admin.common.IServerAdmin,
org.wso2.carbon.throttling.agent.ThrottlingAgen,
It does not happen each time, but when it happens it does not allow WSO2 to start for a long time. Any possible reason why it happens?
Turns out the visual SVN server I am using (Visual SVN on the host of the virtual boxes) sometimes not runs correctly after restart, and requires manual restart.

issue in installing DSS feature on wso2 ESB 5.0

For a new project I'd like to setup the new ESB 5.0 adding the dss feature as well. I was about to do it from the wilkes repository (http://product-dist.wso2.com/p2/carbon/releases/wilkes/), but during installation it shows following error:
Cannot complete the install because of a conflicting dependency. Software being installed: Data Service Hosting Feature 4.3.4
(org.wso2.carbon.dataservices.feature.group 4.3.4) Software currently installed: WSO2 Carbon - Transaction Manager Feature 4.5.4
(org.wso2.carbon.transaction.manager.feature.group 4.5.4) Only one of the following can be installed at once: WSO2 Carbon - Transaction Manager Feature 4.4.7 (org.wso2.carbon.transaction.manager.feature.jar 4.4.7) WSO2 Carbon -
Transaction Manager Feature 4.5.4 (org.wso2.carbon.transaction.manager.feature.jar 4.5.4) Cannot satisfy dependency: From: Data Service Hosting Feature 4.3.4 (org.wso2.carbon.dataservices.feature.group 4.3.4) To: org.wso2.carbon.dataservices.server.feature.group [4.3.4] Cannot satisfy dependency: From: Data Service Hosting Feature 4.3.4 (org.wso2.carbon.dataservices.server.feature.group 4.3.4) To: org.wso2.carbon.transaction.manager.feature.group [4.4.0,4.5.0) Cannot satisfy dependency: From: WSO2 Carbon - Transaction Manager Feature 4.4.7 (org.wso2.carbon.transaction.manager.feature.group 4.4.7) To: org.wso2.carbon.transaction.manager.feature.jar [4.4.7] Cannot satisfy dependency: From: WSO2 Carbon - Transaction Manager Feature 4.5.4 (org.wso2.carbon.transaction.manager.feature.group 4.5.4) To: org.wso2.carbon.transaction.manager.feature.jar [4.5.4]
How can this be solved? the same procedure using ESB 4.9.0 works as expected. Is it something that still to be updated in the new ESB 5.0?
In that case what are the alternatives you suggest?
This seems like a bug. I have raised a Jira (https://wso2.org/jira/browse/DS-1249) to track this. This will be fixed in the next release.
Thanks.

Stratos waiting forever

Following the guide for WSO2 Private PaaS, when running ./boot.sh, after the
Starting WSO2 Private PaaS server as ubuntu user...
There would be nothing going on.
Stratos version: Apache Stratos v4.0.0-wso2v1
In private-paas /install/apache-stratos-default/repository/logs directory:
the wso2carbon.log giving repeat message as:
[2015-05-06 10:27:38,573] WARN {org.wso2.carbon.core.init.CarbonServerManager} - Carbon initialization is delayed due to the following unsatisfied items:
[2015-05-06 10:27:38,574] WARN {org.wso2.carbon.core.init.CarbonServerManager} - Waiting for required OSGiAxis2Service: org.wso2.carbon.identity.provider-4.2.1
[2015-05-06 10:28:38,574] WARN {org.wso2.carbon.core.init.CarbonServerManager} - Carbon initialization is delayed due to the following unsatisfied items:
What does this mean? Any suggestions?
Apache Stratos is based on WSO2 Carbon which itself is an OSGI based framework. From the WARN messages it seems to be waiting for the identity provider OSGI bundle to be loaded. Check if the stated Jar file is available in <STRATOS_HOME>/repository/components/plugin path during server start. If there is one, check if its md5sum is the same as the one that is distributed with Private PaaS. There is a possibility that the jar file is corrupted and could not be loaded as a bundle.

WSO2 ESB 4.0.3 not working

I downloaded binary version for WSO2 ESB 4.0.3
Now when i run wso2server.bat , it simply executes for 2-3 seconds and quits with followin output:
>wso2server.bat
JAVA_HOME environment variable is set to D:\Java\jdk1.6.0_24
CARBON_HOME environment variable is set to D:\iprint\WSO2ES~1.3\bin\..
[2012-11-08 10:02:12,250] INFO - Main Initializing system...
[2012-11-08 10:02:12,375] INFO - HttpTransport Created Connector [HTTP_11_NIO:/
/*:9763]
[2012-11-08 10:02:12,390] INFO - HttpTransport Created Connector [HTTPS_11_NIO:
//*:9443]
[2012-11-08 10:02:12,453] INFO - TomcatCarbonWebappDeployer Deployed Carbon web
app: StandardEngine[Tomcat].StandardHost[defaulthost].StandardContext[/]
[2012-11-08 10:02:12,593] INFO - TransactionFactory Starting Atomikos Transacti
on Manager 3.7.0
>
I can not find anything in the logs as well.
The documentation also seems to be poor for 4.0.3 on wso2.org site as there is no step on how to configure DB for the ESB.
Thanks
deepak
WSO2 ESB documentation clearly specifies these information. As you are working with 4.0.3 version, this is the doc location. http://docs.wso2.org/wiki/display/ESB403
And please follow up; http://docs.wso2.org/wiki/display/ESB403/Installing+ESB+on+Windows+from+Binary+Distribution to run the ESB on windows.
Adding a db:
http://docs.wso2.org/wiki/display/ESB403/Adding+a+Database
FYI: Latest WSO2 ESB can be downloaded from http://wso2.com/products/enterprise-service-bus/
ESB 4.5.1 doc: http://docs.wso2.org/wiki/display/ESB451/Enterprise+Service+Bus+Documentation
Thanks
Thilini