[
https://wso2.org/jira/browse/ESBJAVA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evanthika Amarasiri closed ESBJAVA-441.
---------------------------------------
Tested on wso2esb-1.7. A proper error message is given when an invalid WSDL is
used by the configuration. The issue will be closed
> NullPointerException thrown when trying to invoke a WSDL of a service which
> does not exist
> ------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-441
> URL: https://wso2.org/jira/browse/ESBJAVA-441
> Project: WSO2 ESB
> Issue Type: Bug
> Affects Versions: 1.6
> Environment: Ubuntu7.04, JDK1.5.0_14, Firefox 2.0.0.12
> Reporter: Evanthika Amarasiri
> Assignee: Ruwan Linton
> Fix For: 1.7
>
>
> Was trying to start the ESB server with a configuration which has link to a
> WSDL of a service which does not exist.
> The following exception was thrown on the ESB console.
> **************************************************************************************************************************************************************
> 2008-02-19 09:35:22,570 [10.100.1.97-testc-ubuntu] [main] INFO ProxyService
> Building Axis service for Proxy service : adding_jms_proxy
> java.lang.NullPointerException
> at
> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:250)
> at
> org.apache.synapse.core.axis2.SynapseInitializationModule.init(SynapseInitializationModule.java:142)
> at
> org.apache.axis2.context.ConfigurationContextFactory.initModules(ConfigurationContextFactory.java:222)
> at
> org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:200)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:76)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180)
> at org.apache.synapse.ServerManager.start(ServerManager.java:86)
> at
> org.wso2.esb.ServiceBusManager.startListeners(ServiceBusManager.java:147)
> at
> org.wso2.esb.transport.tomcat.StartUpServlet.init(StartUpServlet.java:81)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
> at org.apache.catalina.startup.Embedded.start(Embedded.java:821)
> at
> org.wso2.esb.transport.tomcat.TomcatServer.start(TomcatServer.java:120)
> at org.wso2.esb.ServiceBusManager.start(ServiceBusManager.java:118)
> at org.wso2.esb.ServiceBus.start(ServiceBus.java:135)
> at org.wso2.esb.ServiceBus.main(ServiceBus.java:69)
> 2008-02-19 09:35:23,221 [10.100.1.97-testc-ubuntu] [main] FATAL ServerManager
> Startup failed...
--
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]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
