[ 
https://wso2.org/jira/browse/ESBJAVA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24475#action_24475
 ] 

Prabath Siriwardena commented on ESBJAVA-590:
---------------------------------------------

Hi Marc;

Suggested change being done in the trunk as per [1].

Thanks
- Prabath

[1]:https://wso2.org/jira/browse/CARBON-3178

> Carbon UI fails to start on Windows after enabling FIX transport
> ----------------------------------------------------------------
>
>                 Key: ESBJAVA-590
>                 URL: https://wso2.org/jira/browse/ESBJAVA-590
>             Project: WSO2 ESB
>          Issue Type: Bug
>    Affects Versions: NIGHTLY
>         Environment: Windows Vista x64; jdk1.6.0_12
>            Reporter: Marc Hodgins
>            Assignee: Ruwan Linton
>
> Started server via wso2server.bat; signed on to the web UI, clicked 
> transports and to enable FIX transport.  Shut down server.  Restarted via 
> wso2server.bat.  Carbon UI will not restart.   The result is the same, 
> whether using the current release version 1.7 or using the nightly snapshot 
> as of Feb 11 2009:
> C:\wso2esb-SNAPSHOT\bin>wso2server.bat
> [WARNING] CARBON has not been fully tested on JDK 1.6
> Feb 12, 2009 11:42:07 AM org.wso2.carbon.server.Main main
> INFO: Starting WSO2 Carbon...
> Feb 12, 2009 11:42:08 AM org.wso2.carbon.server.Main main
> INFO: Using Java Home        : c:\program files\java\jdk1.6.0_12\jre
> Feb 12, 2009 11:42:08 AM org.wso2.carbon.server.Main main
> INFO: Using Java Version     : 1.6.0_12
> Feb 12, 2009 11:42:08 AM org.wso2.carbon.server.Main main
> INFO: Using Carbon Home      : C:\WSO2ES~1\bin\..
> Feb 12, 2009 11:42:09 AM org.apache.catalina.startup.Embedded start
> INFO: Starting tomcat server
> Feb 12, 2009 11:42:09 AM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> Feb 12, 2009 11:42:10 AM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> Feb 12, 2009 11:42:10 AM org.apache.coyote.http11.Http11BaseProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-9763
> Feb 12, 2009 11:42:10 AM org.apache.coyote.http11.Http11BaseProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-9763
> Feb 12, 2009 11:42:12 AM org.apache.coyote.http11.Http11BaseProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-9443
> Feb 12, 2009 11:42:12 AM org.apache.coyote.http11.Http11BaseProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-9443
> 2009-02-12 11:42:46,696 [-] [Start Level Event Dispatcher]  INFO Activator 
> Using
>  embedded Registry
> 2009-02-12 11:42:46,717 [-] [Start Level Event Dispatcher]  INFO Activator 
> Regis
> try is used in READ-WRITE mode
> 2009-02-12 11:42:52,083 [-] [Start Level Event Dispatcher]  INFO 
> SynapseInitiali
> zationModule Initializing Synapse at : Thu Feb 12 11:42:52 CST 2009
> 2009-02-12 11:42:52,087 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseInitializationModule Loading mediator extensions...
> 2009-02-12 11:42:52,581 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseInitializationModule Initializing the Synapse configuration ...
> 2009-02-12 11:42:52,676 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> XMLConfigurationBuilder Generating the Synapse configuration model by parsing 
> th
> e XML configuration
> 2009-02-12 11:42:52,807 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseConfigurationBuilder Loaded Synapse configuration from : 
> conf/synapse.xml
> 2009-02-12 11:42:52,837 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseInitializationModule Deploying the Synapse service..
> 2009-02-12 11:42:52,895 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseInitializationModule Synapse server name : localhost
> 2009-02-12 11:42:52,895 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseInitializationModule Deploying Proxy services...
> 2009-02-12 11:42:52,896 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> SynapseInitializationModule Synapse initialized successfully...!
> 2009-02-12 11:42:52,897 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOSSLSender Loading Identity Keystore from : 
> resources/security/wso2car
> bon.jks
> 2009-02-12 11:42:52,989 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOSSLSender Loading Trust Keystore from : 
> resources/security/client-tru
> ststore.jks
> 2009-02-12 11:42:52,991 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOSender HTTPS Sender starting
> 2009-02-12 11:42:53,001 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOSender HTTP Sender starting
> 2009-02-12 11:42:53,005 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> JMSSender JMS Sender started
> 2009-02-12 11:42:53,005 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> VFSTransportSender VFS Sender started
> 2009-02-12 11:42:55,399 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> DefaultServerInitializer Repository             : C:\WSO2ES~1\bin\../reposi
> tory/
> 2009-02-12 11:42:56,290 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOSSLListener Loading Identity Keystore from : 
> resources/security/wso2c
> arbon.jks
> 2009-02-12 11:42:56,291 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOSSLListener Loading Trust Keystore from : 
> resources/security/client-t
> ruststore.jks
> 2009-02-12 11:42:56,293 [192.168.0.102-PC] [Start Level Event Dispatcher]  
> INFO
> HttpCoreNIOListener HTTPS Listener starting on port : 8243
> 2009-02-12 11:42:56,466 [192.168.0.102-PC] [Start Level Event Dispatcher] 
> ERROR
> Activator Failed to start Carbon UI
> java.lang.Exception: ConfigurationContext Service is not available
>         at org.wso2.carbon.ui.internal.Activator.start(Activator.java:108)
>         at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(Bund
> leContextImpl.java:999)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
> ator(BundleContextImpl.java:993)
>         at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
> leContextImpl.java:974)
>         at 
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
> eHost.java:346)
>         at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(Abstra
> ctBundle.java:350)
>         at 
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Frame
> work.java:1118)
>         at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBund
> les(StartLevelManager.java:634)
>         at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(St
> artLevelManager.java:508)
>         at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStart
> Level(StartLevelManager.java:282)
>         at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEv
> ent(StartLevelManager.java:468)
>         at 
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventM
> anager.java:195)
>         at 
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(Even
> tManager.java:297)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
Esb-java-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to