[Mashup-dev] [jira] Resolved: (MASHUP-1036) Adding a new transport after shutting down the server causes issues

Keith Godwin Chapman (JIRA) jira at wso2.org
Thu Jul 31 10:08:53 PDT 2008


     [ https://wso2.org/jira/browse/MASHUP-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Godwin Chapman resolved MASHUP-1036.
------------------------------------------

    Resolution: Fixed

> Adding a new transport after shutting down the server causes issues
> -------------------------------------------------------------------
>
>                 Key: MASHUP-1036
>                 URL: https://wso2.org/jira/browse/MASHUP-1036
>             Project: WSO2 Mashup Server
>          Issue Type: Bug
>            Reporter: Keith Godwin Chapman
>            Assignee: Keith Godwin Chapman
>             Fix For: 1.5.1
>
>
> Adding new transports before the server has started works fine (clean database). But adding transports after the server has been used causes deployment issues with the following error. This is due to a BUG in WSAS
> ERROR [2008-07-30 21:47:14,384]  Could not handle initialization of existing service [samples-CSVSample]
> java.lang.NullPointerException
> 	at org.wso2.wsas.persistence.PersistenceManager.handleExistingServiceInit(PersistenceManager.java:1095)
> 	at org.wso2.wsas.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:237)
> 	at org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:510)
> 	at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:355)
> 	at org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:500)
> 	at org.wso2.mashup.deployers.DBDeployer.deploy(DBDeployer.java:96)
> 	at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> 	at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
> 	at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> 	at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
> 	at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
> 	at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:324)
> 	at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
> 	at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
> 	at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:83)
> 	at java.util.TimerThread.mainLoop(Timer.java:512)
> 	at java.util.TimerThread.run(Timer.java:462)

-- 
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

        



More information about the Mashup-dev mailing list