The SOAP monitor is now working fine in my Axis2 web service.
Many thanks to Robert Lazasrki for the assistance.
It turns out that the port error occurs only when running Tomcat 5.5 within
Eclipse. Also the messages referring to a null handler for the SOAP monitor
phase can be ignored.
One oth
It looks like the port binding error occurs only when starting Tomcat 5.5
within the Eclipse WTP. I don't see the error when deploying the WAR file
directly to Tomcat 5.5
However I see this message 12 times upon startup:
Handler null added to Phase soapmonitorPhase
Then when I invoke an operat
Search for 'Deploying module' - you may be doing it twice as that's
the only thing I can think of. Sure you only have one war with axis2 ?
When you shutdown tomcat, is java.exe still holding on to ports 5001,
3901 etc ?
BTW, I just tested the soapmonitor with the 1.3 branch nightly from
yesterday
Robert,
Setting the log4j level to DEBUG produced quite a lot of messages in the Tomcat
5.5 console within Eclipse upon startup.
There are a bunch of sax and Digester messages prior to the port error, but
nothing that looks related. The 2 messages immediately before the port error
are:
2007-0
I'm using Axis2 version 1.2.
I've already got a log4j.xml config. file in place. I'll set the debugging
level on oprg.apache to DEBUG and post back.
Thanks again for the help.
T
robert lazarski <[EMAIL PROTECTED]> wrote: What version are you using?
That's a pretty strange problem. There are p
What version are you using?
That's a pretty strange problem. There are people that use this tool
and I've never heard of an issue like this. We're about to do a
release soon - can you try these?
http://people.apache.org/dist/axis2/nightly/axis2-1.3-SNAPSHOT-bin.zip
http://people.apache.org/dist/a
Hi Robert,
Only the Java executable (javaw.exe) is using the port. It does not matter
what port I set in web.xml - it is always in use by the Java executable.
I thought I could find an open port, but it does not seem to matter which one I
use. It is *always* taken by javaw.exe.
It''s almost l
What is connected to 3901 ? There's 65,000 or so ports, so I'm sure
you should be able to find one of them open ;-) .
HTH,
Robert
On 7/26/07, Jack Sprat <[EMAIL PROTECTED]> wrote:
> Hi Robert.
>
> I used ActivePorts for Windows, as suggested earlier. This showed the port
> specified in web.xml a
Hi Robert.
I used ActivePorts for Windows, as suggested earlier. This showed the port
specified in web.xml as occupied by javaw.exe.
What could be the problem here?
Thanks again for trying to help.
T
robert lazarski <[EMAIL PROTECTED]> wrote: I'm not a windows user, but you do
have the nets
I'm not a windows user, but you do have the netstat command that can
help you track your occupied ports. On linux it'd be 'netstat -ancp |
grep 5001' .
You can engage the module in either services.xml or axis2.xml - but
not both. engaging in axis2.xml make the module available for all
services, wh
Hi Robert.
Thanks for trying to help. This has me quite confused.
The Tomcat console says that the server socket on the port specified in web.xml
cannot be opened. If I set port 3901 then the console says port 3901 cannot be
opened. Same for port 5001.
The ports show as used by the javaw.exe
---
> From: robert lazarski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 25, 2007 7:07 AM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] SOAPMonitorApplet port
>
>
> When you set the port to 3901, does it still say cannot connect to
> 5001? Can you try RC2? I
nt: Wednesday, July 25, 2007 7:07 AM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] SOAPMonitorApplet port
>
>
> When you set the port to 3901, does it still say cannot connect to
> 5001? Can you try RC2? I'll try to give this scenario a spin today.
>
> H
When you set the port to 3901, does it still say cannot connect to
5001? Can you try RC2? I'll try to give this scenario a spin today.
HTH,
Robert
On 7/24/07, Jack Sprat <[EMAIL PROTECTED]> wrote:
I've tried ports 3901, 5001 and 5050. All gave the same result.
robert lazarski <[EMAIL PROTECT
I've tried ports 3901, 5001 and 5050. All gave the same result.
robert lazarski <[EMAIL PROTECTED]> wrote: Have you tried changing to another
port in the web.xml?
HTH,
Robert
On 7/24/07, Jack Sprat wrote:
> I've followed the instructions for setting up the SOAP monitor applet here:
> http://
Have you tried changing to another port in the web.xml?
HTH,
Robert
On 7/24/07, Jack Sprat <[EMAIL PROTECTED]> wrote:
I've followed the instructions for setting up the SOAP monitor applet here:
http://ws.apache.org/axis2/1_2/soapmonitor-module.html
Whenever I start my server I get the followin
16 matches
Mail list logo
