[
https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518333
]
Charitha Kankanamge commented on AXIS2-3099:
--------------------------------------------
I observed following when investigating the issue further.
- If you have reference in axis2.xml for a non-existing module (Module which is
not available in WEB-INF\modules directory), you get an internal server error
when accessing listservices page in axis2 admin console. I removed rampart
reference (Which was not available in modules directory) from axis2.xml and
added <module ref="soapmonitor"/>. Then the happyaxis page did not throw an
error and available services were shown in listservices page. So, the current
behavior is, when you have a reference for a non-existing module, you get
internal server error in axis2 admin console.
- We replaced default axis2.xml with the axis2.xml file provided by Jorge.
First, we got the same error what Jorge had observed. Then we opened Jorge's
axis2.xml from a windows notepad editor and found out that there were some
invalid end of line characters in it. We removed those invalid characters and
restarted tomcat. Then we did not get such error.
The file opened and edited by notepad is attached here with. Copy it to your
conf directory and check again. Please let us know if you encounter this issue
again.
> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
> ----------------------------------------------------------------------------
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
> Reporter: Jorge Fernández
> Priority: Blocker
> Attachments: axis2.xml, excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not
> available or some thing has gone wrong. But this does not mean system is not
> working ! Try to upload some other service and check to see whether it is
> working.
> For stoping that problem I have to backup and restore the original axis2.xml
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated,
> apparently with no changes but is modified on disk and the same happens with
> axis2.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
