ESB Management Console not responding
Submitted by chao2004.gmail.com on July 23, 2010 - 10:59
Hi,
I followed the deployment instruction to deploy the esb to tomcat. I was able to bring up the esb server successfully, however, I can't access the management console through https://localhost:8443/esb/carbon/. The server didn't respond to the request at all.
Anyone has an idea what is the problem?
I didn't modify the Axis2 transport port number. I can still access https://localhost:8243/esb/services/ to see all the deployed services.
Can someone explain how it works when the esb is deployed within tomcat as a web app? The OSGi runtime is running within tomcat servlet container. OSGi provides its own http(s) server components. How does tomcat servlet container interact with the OSGi services?
Thanks
Bookmark/Search this post with:
- Login or register to post comments
- 155 reads
- Printer-friendly version
- Send to friend
- PDF version
Post to twitter
The actual connection URL is
The actual connection URL is logged at the server startup. Can you try connecting that URL ? Is that same as https://localhost:8443/esb/carbon/ ? It seems that you have changed the port number to 8443, other wise it should be normally 9443.
Rajika
Help: ESB admin console URL
I didn't change the admin console port number.
The instruction on this site only said enable https for tomcat, which runs on port 8443. And the admin url displayed on the console is using 8443. Isn't that supposed to work like that?
However, I do notice there is mgmt-transports.xml file in the conf directory. Port 9443 is used in there for https. I tried to cahnge this too, but didn't work.
Should the admin console be accessed through Tomcat https port or the https service deployed in the OSGi framework?
Tomcat console log is below:
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Starting WSO2 Carbon...
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Operating System : Windows XP 5.1, x86
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Java Home : C:\apps\jdk1.6\jre
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Java Version : 1.6.0_10
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Java VM : Java HotSpot(TM) Client VM 11.0-b15,Sun Microsystems Inc.
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Carbon Home : C:/apps/data/esb
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator Java Temp Dir : C:\apps\tomcat-6.0.14\temp
2010-07-26 13:42:49,597 [-] [Start Level Event Dispatcher] INFO CarbonCoreActivator User : en-US, America/New_York
2010-07-26 13:42:51,801 [-] [Component Resolve Thread (Bundle 77)] INFO RuleServerManagerComponent There is no rule-server.xml... Using the default configuration
2010-07-26 13:42:51,847 [-] [Component Resolve Thread (Bundle 77)] INFO RuleServerConfigurationFactory A Rule provider has not been specified. Using default one : org.wso2.carbon.rule.engine.jsr94.JSR94BackendRuntimeFactory
2010-07-26 13:42:52,879 [-] [Start Level Event Dispatcher] INFO RegistryCoreServiceComponent Registry Mode : READ-WRITE
2010-07-26 13:42:54,926 [-] [Framework Event Dispatcher] INFO CarbonServerManager Starting Carbon initialization...
2010-07-26 13:42:55,097 [-] [Framework Event Dispatcher] INFO ClusterBuilder Clustering has been disabled
2010-07-26 13:42:55,238 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : relay-3.0
2010-07-26 13:42:55,269 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : wso2mex-3.0
2010-07-26 13:42:55,285 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : rampart-1.50-wso2v1
2010-07-26 13:42:55,316 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : sandesha2-3.0
2010-07-26 13:42:55,347 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : wso2caching-3.0
2010-07-26 13:42:55,379 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : wso2xfer-3.0
2010-07-26 13:42:55,379 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : rahas-1.50-wso2v1
2010-07-26 13:42:55,394 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : savan-1.10-wso2v1
2010-07-26 13:42:55,410 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : wso2throttle-3.0
2010-07-26 13:42:55,457 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 module : addressing-1.6-wso2v1
2010-07-26 13:42:55,597 [-] [Framework Event Dispatcher] INFO HttpCoreNIOSSLSender Loading Identity Keystore from : C:/apps/data/esb/resources/security/wso2carbon.jks
2010-07-26 13:42:55,613 [-] [Framework Event Dispatcher] INFO HttpCoreNIOSSLSender Loading Trust Keystore from : C:/apps/data/esb/resources/security/client-truststore.jks
2010-07-26 13:42:55,769 [-] [Framework Event Dispatcher] INFO HttpCoreNIOSender HTTPS Sender starting
2010-07-26 13:42:55,785 [-] [Framework Event Dispatcher] INFO HttpCoreNIOSender HTTP Sender starting
2010-07-26 13:42:55,879 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 service : echo
2010-07-26 13:42:56,176 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 service : version
2010-07-26 13:42:57,941 [-] [Framework Event Dispatcher] WARN DefaultSchemaGenerator We don't support method overloading. Ignoring [getLogs]
2010-07-26 13:42:59,269 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 service : wso2carbon-sts
2010-07-26 13:42:59,957 [-] [Framework Event Dispatcher] INFO DeploymentInterceptor Deploying Axis2 service : XKMS
2010-07-26 13:43:00,269 [-] [Framework Event Dispatcher] INFO CarbonServerManager Repository : C:/apps/data/esb/repository/deployment/server/
2010-07-26 13:43:00,332 [-] [Framework Event Dispatcher] INFO EmbeddedRegistryBasedSubscriptionManager Connection established with the registry
2010-07-26 13:43:00,379 [-] [Framework Event Dispatcher] INFO ServiceBusInitializer Starting ESB...
2010-07-26 13:43:00,441 [-] [Framework Event Dispatcher] INFO ServiceBusInitializer Initializing Apache Synapse...
2010-07-26 13:43:00,441 [-] [Framework Event Dispatcher] INFO SynapseControllerFactory Using Synapse home : C:\apps\tomcat-6.0.14\bin\.
2010-07-26 13:43:00,441 [-] [Framework Event Dispatcher] INFO SynapseControllerFactory Using synapse.xml location : C:\apps\data\esb\repository\conf\synapse-config
2010-07-26 13:43:00,441 [-] [Framework Event Dispatcher] INFO SynapseControllerFactory Using server name : localhost
2010-07-26 13:43:00,457 [-] [Framework Event Dispatcher] INFO SynapseControllerFactory The timeout handler will run every : 15s
2010-07-26 13:43:00,504 [-] [Framework Event Dispatcher] INFO Axis2SynapseController Initializing Synapse at : Mon Jul 26 13:43:00 EDT 2010
2010-07-26 13:43:00,504 [-] [Framework Event Dispatcher] INFO Axis2SynapseController Loading mediator extensions...
2010-07-26 13:43:00,504 [-] [Framework Event Dispatcher] INFO CarbonSynapseController Loading the mediation configuration from the file system
2010-07-26 13:43:00,519 [-] [Framework Event Dispatcher] INFO MultiXMLConfigurationBuilder Building synapse configuration from the synapse artifact repository at : C:/apps/data/esb/repository/conf/synapse-config
2010-07-26 13:43:00,519 [-] [Framework Event Dispatcher] INFO XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
2010-07-26 13:43:00,722 [-] [Framework Event Dispatcher] INFO SynapseConfigurationBuilder Loaded Synapse configuration from the artifact repository at : C:/apps/data/esb/repository/conf/synapse-config
2010-07-26 13:43:00,957 [-] [Framework Event Dispatcher] INFO Axis2SynapseController Deploying the Synapse service...
2010-07-26 13:43:00,972 [-] [Framework Event Dispatcher] INFO Axis2SynapseController Deploying Proxy services...
2010-07-26 13:43:00,972 [-] [Framework Event Dispatcher] INFO Axis2SynapseController Deploying EventSources...
2010-07-26 13:43:00,972 [-] [Framework Event Dispatcher] INFO ServerManager Server ready for processing...
2010-07-26 13:43:01,816 [-] [Framework Event Dispatcher] INFO HttpsTransportListener HTTPS port : 8443
2010-07-26 13:43:01,816 [-] [Framework Event Dispatcher] INFO HttpTransportListener HTTP port : 9090
2010-07-26 13:43:01,816 [-] [Framework Event Dispatcher] INFO RegistryEventingServiceComponent Successfully Initialized Eventing on Registry
2010-07-26 13:43:04,629 [-] [Framework Event Dispatcher] INFO CarbonUIServiceComponent Mgt Console URL : https://172.23.135.19:8443/esb/carbon/
2010-07-26 13:43:04,644 [-] [Framework Event Dispatcher] INFO StartupFinalizerServiceComponent Started Transport Listener Manager
2010-07-26 13:43:04,644 [-] [Framework Event Dispatcher] INFO StartupFinalizerServiceComponent Server : WSO2 ESB-3.0.0
2010-07-26 13:43:04,644 [-] [Framework Event Dispatcher] INFO StartupFinalizerServiceComponent WSO2 Carbon started in 20 sec
Anyone can help?
Does anyone have an idea what is wrong? Carbon osgi bridge problem?
Hi, Could you please check
Hi,
Could you please check whether you have done the following?
a) Add the following to the apache-tomcat-6.0.14/conf/server.xml of Tomcat
b) Replace this
https://${carbon.local.ip}:${carbon.management.port}${carbon.context}/services/
from this
https://localhost:8443/esb/services/
of the ESB_HOME/repository/conf/carbon.xml of your WSO2 ESB instance
Also could you please go through http://evanthika.blogspot.com/2009/02/deploying-wso2-esb-20-on-apache-tomcat.html once more and see what you have missed?
Thanks,
Evanthika