axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Date Tue, 15 Jun 2004 16:23:10 GMT
The following comment has been added to this issue:

     Author: Brian Dillon
    Created: Tue, 15 Jun 2004 9:21 AM

I am trying to develop the non-servlet version. The issue that I have come across is that
when I list the services the only services that can be seen are the AdminService and Version,
non of the application specific services are viewable (even though I can see them using the

So basically my problem is trying to create a new AxisServer which shares the current configuration
with what is already there (similar to AdminServlet);

Currently what I have is;

     * Get the singleton engine for this management object 
     * @return
     * @throws AxisFault
    static public AxisServer getEngine() throws AxisFault {
        if (axisServer == null) {
            axisServer = new AxisServer(EngineConfigurationFactoryFinder.newFactory().getServerEngineConfig()
        return axisServer;

Is there some other way of creating the AxisServer (I have tried new AxisServer() ) which
is capable of sharing the configuration with the AxisServlet and the AdminServlet ?

If it helps you can mail me directly and I will send on the full class I am using.


View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1389
    Summary: Ability to Suspend and Resume Specific Services
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
             Deployment / Registries
   Fix Fors:
             current (nightly)

   Assignee: Davanum Srinivas
   Reporter: Brian Dillon

    Created: Fri, 11 Jun 2004 9:14 AM
    Updated: Tue, 15 Jun 2004 9:21 AM


If a Service is deployed on Axis there currently seems to be no way of suspending and resuming
the service (without undeploying and redeploying).

I understand from looking through the API that there are calls;

So my issue is how to get a reference to this SOAPService handler since we don't have direct
access to the running AxisServer ? There seems to be now way to get access to either the AxisServer
or the SOAPService handler from outside of Axis.

The reason for not going down the route of deploy and undeploy is because of the need for
wsdd files. If the ability to suspend and resume the service was allowed then we could present
a JMX interface to list and control (stop/suspend and restart/resume) the services as required.


Brian Dillon

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message