There is a simple way to solve this issue. Inside your DS component class,
put the following code segment.
try {
Utils.registerDeployerServices(bundleContext);
} catch (Exception e) {
String msg = Failed to register Axis1Deployer as an OSGi
service.;
Hello,
Were setting up a gadget server cluster with two nodes on Amazon. Were
having problems with the clustering and load balance, we got a Amazon load
balancer: balancer.mydomain.com
This balance between gs1.mydomain.com and gs2.mydomain.com, both server are
configures on carbon.xml
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/home/stratos/build/carbon/components/localentry/org.wso2.carbon.localentry/src/main/java/org/wso2/carbon/localentry/service/LocalEntryAdmin.java:[185,80]
cannot find
Please configure your load balancer to use HTTP sticky sessions. We haven't
implemented HTTP session replication yet. For hostname server URL entries,
use the name/IP of the load balancer.
Azeez
On Thu, Jul 29, 2010 at 8:52 PM, Daniel Callejas Albalate
d...@nextret.netwrote:
Hello,
We’re
You can keep a habit of running svn stat to avoid that mistake before
committing code.
Lahiru
On Thu, Jul 29, 2010 at 8:16 AM, Amani Soysa am...@wso2.com wrote:
Hi,
Sorry I forgot to commit a file it's fixed now.
Regards,
Amani
On Thu, Jul 29, 2010 at 5:03 AM, Samisa Abeysinghe
Why is the original request/reponse wrapped by these classes? Some JavaDocs
explaining the usage of these classes would have helped.
Azeez
--
Afkham Azeez
Senior Software Architect Senior Manager; WSO2, Inc.; http://wso2.com,
Lean . Enterprise . Middleware
Member; Apache Software Foundation;
I'm a bit concerned about the multiple layers that wrap the original HTTP
servlet request/response. We have the Equinox wrapper, then the Carbon
wrapper, and now metering wrapper. Is the metering wrapper needed? Can't we
use the existing Carbon wrapped request/responses?
Azeez
On Fri, Jul 30,
