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.
Related
Go-agent and go-server same version - v18.8.0. Server and agent are installed in different machines. In go-server/agents , the agent is not listed. The agent configuration file in /etc/default/go-agent is updated with hostname of go server.
Please help.
As mentioned in my question - the /etc/default/go-agent file is updated with the remote go-server url. After making this change, restarting the agent did not solve the problem. So, I went to restart the entire machine and now the remote go-agent gets listed in the go-server/agents.
Anytime the server (go-server) goes down, it should be ensured that every machine/runtime running go-agent is restarted.
FYI - This is with go-version#18.8.0 and go-agent#18.8.0
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.
I am trying to profile Mule ESB apps deployed on a mule container(CE v3.4) using Jprofiler but have been unsuccessful this far.
My Mule server is running remotely on a linux 64 bit server and the jprofiler is running on my local windows machine. I am trying to remotely connect the jprofiler running on my local windows machine to the Mule server running remotely on a linux server, but till now I have failed to connect the local running jprofiler to the remotely running Mule server.
Has somebody done this before? What are the steps to be followed to connect my jprofiler running locally to Mule server running remotely on some different server?
Thanks and Regards
Jai
Add these lines to conf/wrapper.conf:
wrapper.java.additional.4=-Dcom.sun.management.jmxremote.port=9999
wrapper.java.additional.5=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.6=-Dcom.sun.management.jmxremote.ssl=false
and connect your profiler to port 9999
Can any one tell me how to run wso2 governance registry 4.5.3 in web app mode rather running it in stand alone mode ? I have successfully built the source code and I want to know exactly how I can run in web app mode so that I can debug it in the eclipse ??
If what you want is to debug the source code all you have to do is start the WSO2 Governance registry with debug enabled when starting the server this can be done by starting the server with the following command.
sh wso2server.sh debug 8000
And you can remotely debug the server through an IDE like eclipse or Idea with port 8000 or some other port number you wish to use.
EDIT: Regarding running WSO2 governance registry in web app mode take a look at this blog post which explains how WSO2 carbon can be run as a web app might help you
[1]http://pradeepfernando.blogspot.com/2012/09/running-wso2-carbon-as-web-app-apache.html
First you have to setup debug configurations in your IDE which is can be learn using this wso2 article
Then start the BPS server script with debug option as follows.
<bps_home>/bin/wso2server.sh -debug 5005
After you start the server you will get this message:
Listening for transport dt_socket at address: 5005
Then start debugging from your IDE!
This is the debug configuration I used:
I'm trying to setup some OSS builds in Cloudbees and one of them requires a redis server for the tests performed during the build.
Is this supported in some way by the Jenkins build process under Cloudbees, or will I have to find another way to set that one up?
You can launch a redis-server as your build starts.
redis-server &
The current version of redis installed can be found (it's a packaged Redis, so the version of the cli and server typically match up) using
redis-cli -v
This information is also now available on the CloudBees developer site - http://developer.cloudbees.com/bin/view/DEV/Redis