You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/06/11 18:16:09 UTC
[jira] Created: (AXIS-1389) Ability to Suspend and Resume Specific Services
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1389
Summary: Ability to Suspend and Resume Specific Services
Type: New Feature
Status: Unassigned
Priority: Major
Project: Axis
Components:
Deployment / Registries
Versions:
1.1
Assignee:
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Fri, 11 Jun 2004 9:14 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Brian Dillon
Created: Mon, 14 Jun 2004 6:28 AM
Body:
Hi,
Thats fine. I will give you a shout once I have it done.
Thanks,
Brian
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36142
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Mon, 14 Jun 2004 6:28 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Brian Dillon
Created: Tue, 15 Jun 2004 9:21 AM
Body:
Dims,
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 AdminServlet).
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.
Thanks,
Brian.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36184
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Tue, 15 Jun 2004 9:21 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
Message:
The following issue has been re-assigned.
Assignee: Davanum Srinivas (mailto:dims@yahoo.com)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1389
Summary: Ability to Suspend and Resume Specific Services
Type: New Feature
Status: Open
Priority: Major
Project: Axis
Components:
Deployment / Registries
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Fri, 11 Jun 2004 9:38 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Mon, 14 Jun 2004 5:38 AM
Body:
NO!!! :) Am not asking you to use AdminServlet from your JMX. Am asking you to look at the code in AdminServlet and do the same from your JMX thingy.
thanks,
dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36140
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Mon, 14 Jun 2004 5:38 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Fri, 11 Jun 2004 12:18 PM
Fixed.
Notes:
- you need to switch on axis.development.system flag either in AdminServlet's init-param or in server-config.wsdd
- Updated the AdminServlet page to display list of current services and links to suspend/resume.
Please open up a new request (or drop me a note) when you have the JMX piece ready :)
Thanks,
dims
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Fri, 11 Jun 2004 12:18 PM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Brian Dillon
Created: Mon, 14 Jun 2004 3:35 AM
Body:
Dims,
I downloaded the latest nightly build but can't seem to see what changes you have made.
Can you let me know what you have changed ?
Thanks,
Brian.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36137
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Mon, 14 Jun 2004 3:35 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Mon, 14 Jun 2004 3:40 AM
Body:
- enable adminservlet in your web.xml.
- add an init-param to your adminservlet named axis.development.system and set it to true
- start tomcat and browse to http://localhost:8080/axis/servlet/AdminServlet
-- dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36138
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Mon, 14 Jun 2004 3:40 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Fri, 11 Jun 2004 9:41 AM
Body:
Brian,
If i help with this....Would you be able to help implement a small JMX layer to do the following? :) :)
- start/stop the axis server (see admin servlet)
- enumerate services
- suspend/resume specific service
Thanks,
dims
PS: take a look at the code in org\apache\axis\management\Registrar that can help with this effort
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36040
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1389
Summary: Ability to Suspend and Resume Specific Services
Type: New Feature
Status: Open
Priority: Major
Project: Axis
Components:
Deployment / Registries
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Fri, 11 Jun 2004 9:41 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Brian Dillon
Created: Mon, 14 Jun 2004 4:44 AM
Body:
Dims,
Thanks. So the suspend and resume must be called through the AdminServlet ? What I had originally envisaged was that if AxisEngine was made into a singleton (or some other Admin object) then it would be possible to get a reference to SOAPService without the use of servlets (thus providing a neat hookin for JMX).
Anyway, in the meantime I will take a look to see what would be involved now. The JMX utility would need to be able to do a http post or something similar or just simply maintain it's own reference to an AxisEngine.
Brian.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36139
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
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
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Mon, 14 Jun 2004 4:44 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Brian Dillon
Created: Fri, 11 Jun 2004 9:51 AM
Body:
Dims,
Yep, I can take a look at the JMX layer. It is something I would be looking at for our own services anyway so it probably make sense to see if it can be made generic and added here.
Thanks,
Brian.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36041
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1389
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1389
Summary: Ability to Suspend and Resume Specific Services
Type: New Feature
Status: Open
Priority: Major
Project: Axis
Components:
Deployment / Registries
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Brian Dillon
Created: Fri, 11 Jun 2004 9:14 AM
Updated: Fri, 11 Jun 2004 9:51 AM
Description:
Hi,
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;
handlers.soap.SOAPService.enableTransport(HTTP)
handlers.soap.SOAPService.disableTransport(HTTP)
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.
Thanks,
Brian Dillon
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira