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 Aaoz Gul <aa...@northbaysolutions.net> on 2011/09/27 08:50:27 UTC
Re: Axis2 | Soap Monitor unable to communicate with server
On Tue, Sep 27, 2011 at 11:48 AM, Aaoz Gul
<aa...@northbaysolutions.net>wrote:
> Below is the description of my problem. I'm new with Axis2. I 've deployed
> .war file in tomcate and make change to run the SoapMonitor which
> are explained below links
> http://axis.apache.org/axis2/java/core/docs/installationguide.html
> http://axis.apache.org/axis2/java/core/docs/soapmonitor-module.html
>
> when i hit the soap Link. It will open the UI but a message show that
>
> "The SOAP Monitor is unable to communicate with the server". I'm using
> Linux . I've also set the environment variable following path
> AXIS2_HOME=/etc/axis2-1.6.1-bin/axis2-1.6.1
> JAVA_HOME=/usr/java/jdk
>
> PATH=/usr/java/jdk/bin:/usr/java/jdk/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
>
>
>
> but Soap Monitor couldn't connect with server. Is there is thing missing.
> I'm also new with Linux
>
> I'll be very thankful to you
> regards
> Aaoz
>
Re: Axis2 | Soap Monitor unable to communicate with server
Posted by robert lazarski <ro...@gmail.com>.
On Tue, Sep 27, 2011 at 3:50 AM, Aaoz Gul
<aa...@northbaysolutions.net> wrote:
>
>
> On Tue, Sep 27, 2011 at 11:48 AM, Aaoz Gul <aa...@northbaysolutions.net>
> wrote:
>>
>> Below is the description of my problem. I'm new with Axis2. I 've deployed
>> .war file in tomcate and make change to run the SoapMonitor which
>> are explained below links
>> http://axis.apache.org/axis2/java/core/docs/installationguide.html
>> http://axis.apache.org/axis2/java/core/docs/soapmonitor-module.html
>> when i hit the soap Link. It will open the UI but a message show that
>> "The SOAP Monitor is unable to communicate with the server". I'm using
>> Linux . I've also set the environment variable following path
>> AXIS2_HOME=/etc/axis2-1.6.1-bin/axis2-1.6.1
>> JAVA_HOME=/usr/java/jdk
>>
>> PATH=/usr/java/jdk/bin:/usr/java/jdk/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
>>
>>
>> but Soap Monitor couldn't connect with server. Is there is thing missing.
>> I'm also new with Linux
>> I'll be very thankful to you
>> regards
>> Aaoz
>
You may be having a problem with port 5001, you can tweak that via the
web.xml file. If you still have problems and its not network related,
showing the stacktrace could help explain the cause.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
RE: Jar file dependencies, specifically for
geronimo-stax-api_1.0_spec-1.0.1.jar
Posted by William Walsh <WW...@curamsoftware.com>.
Andreas,
Thanks for the detailed response. I will check in our environments.
All the best,
William
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Wednesday, September 28, 2011 12:08 PM
To: java-dev@axis.apache.org
Subject: Re: Jar file dependencies, specifically for geronimo-stax-api_1.0_spec-1.0.1.jar
Removing geronimo-stax-api_1.0_spec-1.0.1.jar is safe, but you should
double check that after removing that JAR, Axis2 is still using the
Woodstox StAX implementation and not the one provided by the server
runtime (WebSphere's XLXP parser is supported, but less well tested
than Woodstox, and WebLogic's StAX implementation is currently not
supported).
Regarding the dependencies: the page from the Rampart Web site is
generated from the Maven metadata. This is feasible for Rampart
because Rampart only has a single set of dependencies. For Axis2 it is
not realistic to publish that information because the project is split
into multiple Maven modules and each Maven module can have specific
dependencies.
Andreas
On Tue, Sep 27, 2011 at 14:27, William Walsh <WW...@curamsoftware.com> wrote:
> Hi,
>
> We are deploying Axis2 web services in WebSphere and WebLogic and are seeing an application conflict (JVMVRFY013 class loading constraint violated) with geronimo-stax-api_1.0_spec-1.0.1.jar and are trying to determine the impact, if any, of removing this jar. As far as I can tell both WebSphere and WebLogic provide their own implementations of these classes (in xml.jar and wlfullclient.jar, respectively). But, am wondering if there might be future impacts if we remove this jar. In researching what the dependencies are I see that Rampart does a very good job of defining its dependencies (see http://axis.apache.org/axis2/java/rampart/dependencies.html), but I haven't been able to find anything for Axis2 in general. Our testing hasn't revealed any issues so far. Does anyone have any experience or knowledge in this area of geronimo-stax-api_1.0_spec-1.0.1.jar usage and/or dependencies that they could share?
>
> Thanks,
> William
>
>
>
>
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. If you are not the intended
> addressee please contact the sender and dispose of this e-mail. Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Jar file dependencies, specifically for geronimo-stax-api_1.0_spec-1.0.1.jar
Posted by Andreas Veithen <an...@gmail.com>.
Removing geronimo-stax-api_1.0_spec-1.0.1.jar is safe, but you should
double check that after removing that JAR, Axis2 is still using the
Woodstox StAX implementation and not the one provided by the server
runtime (WebSphere's XLXP parser is supported, but less well tested
than Woodstox, and WebLogic's StAX implementation is currently not
supported).
Regarding the dependencies: the page from the Rampart Web site is
generated from the Maven metadata. This is feasible for Rampart
because Rampart only has a single set of dependencies. For Axis2 it is
not realistic to publish that information because the project is split
into multiple Maven modules and each Maven module can have specific
dependencies.
Andreas
On Tue, Sep 27, 2011 at 14:27, William Walsh <WW...@curamsoftware.com> wrote:
> Hi,
>
> We are deploying Axis2 web services in WebSphere and WebLogic and are seeing an application conflict (JVMVRFY013 class loading constraint violated) with geronimo-stax-api_1.0_spec-1.0.1.jar and are trying to determine the impact, if any, of removing this jar. As far as I can tell both WebSphere and WebLogic provide their own implementations of these classes (in xml.jar and wlfullclient.jar, respectively). But, am wondering if there might be future impacts if we remove this jar. In researching what the dependencies are I see that Rampart does a very good job of defining its dependencies (see http://axis.apache.org/axis2/java/rampart/dependencies.html), but I haven't been able to find anything for Axis2 in general. Our testing hasn't revealed any issues so far. Does anyone have any experience or knowledge in this area of geronimo-stax-api_1.0_spec-1.0.1.jar usage and/or dependencies that they could share?
>
> Thanks,
> William
>
>
>
>
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. If you are not the intended
> addressee please contact the sender and dispose of this e-mail. Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Jar file dependencies, specifically for
geronimo-stax-api_1.0_spec-1.0.1.jar
Posted by William Walsh <WW...@curamsoftware.com>.
Hi,
We are deploying Axis2 web services in WebSphere and WebLogic and are seeing an application conflict (JVMVRFY013 class loading constraint violated) with geronimo-stax-api_1.0_spec-1.0.1.jar and are trying to determine the impact, if any, of removing this jar. As far as I can tell both WebSphere and WebLogic provide their own implementations of these classes (in xml.jar and wlfullclient.jar, respectively). But, am wondering if there might be future impacts if we remove this jar. In researching what the dependencies are I see that Rampart does a very good job of defining its dependencies (see http://axis.apache.org/axis2/java/rampart/dependencies.html), but I haven't been able to find anything for Axis2 in general. Our testing hasn't revealed any issues so far. Does anyone have any experience or knowledge in this area of geronimo-stax-api_1.0_spec-1.0.1.jar usage and/or dependencies that they could share?
Thanks,
William
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org