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 and it can use other ports like 3901 just fine. I'll improve the debugging a little to indicate what port its going to bind to. A suggestion is to use the 1.3 branch war as I mentioned last post - it'll be final shortly and as I said with that code I can't reproduce your problem. Also, sure, send me the logs off list and maybe I'll see something. HTH, Robert On 7/27/07, Jack Sprat <[EMAIL PROTECTED]> wrote: > 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-07-27 11:16:46,687 DEBUG [/Eclipse_project_name] - Sending application > start events > 2007-07-27 11:16:46,687 DEBUG [/Eclipse_project_name] - Starting filters > > Is there anything in particular I should be looking for? > I could send all the messages to you off-list. > > Thanks, > T > > > robert lazarski <[EMAIL PROTECTED]> wrote: > 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/axis2/nightly/axis2-1.3-SNAPSHOT-war.zip > > I can't think of anything off hand on windows that could track down > what class loaded by java.exe is using the port. Can you put > WEB-INF/classes/log4j.properties in DEBUG, along with a > log4j.jar in > WEB-INF/lib . That should create a bunch of axis2 content on > catalina.out. If you could send that to this list, we might be able > to track it down. > > Robert > > On 7/26/07, Jack Sprat wrote: > > 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 like Axis2 is reserving the port and then trying to use it > > again, causing the bind error. > > > > Thanks, > > T > > > > > > robert lazarski wrote: > > 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 wrote: > > > 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 wrote: > > > 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, whereas alternatively engaging in the services,xml makes to > > > module available to just that service. > > > > > > If all else fails, you could use tcpmon as an alternative. > > > > > > HTH, > > > Robert > > > > > > On 7/25/07, Jack Sprat wrote: > > > > 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 process. > > > > > > > > My only other question on the SOAP monitor applet is where to set the > > > module > > > > ref. I have this set in the services.xml file. This is the same as the > > > > logging module, with the instructions here: > > > > http://ws.apache.org/axis2/1_1/modules.html > > > > But the SOAP monitor page says to set the module reference in the > > > axis2.xml > > > > file. Which is right? > > > > > > > > Axis2 with Tomcat 5.5 > > > > > > > > Thanks, > > > > T > > > > > > > > > > > > robert lazarski wrote: > > > > 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 wrote: > > > > > I've tried ports 3901, 5001 and 5050. All gave the same result. > > > > > > > > > > > > > > > robert lazarski 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://ws.apache.org/axis2/1_2/soapmonitor-module.html > > > > > > > > > > > > Whenever I start my server I get the following errors: > > > > > > > > > > > > 2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open > > > server > > > > > > socket using port: 5001 > > > > > > 2007-07-24 18:18:20,484 ERROR SOAPMonitorService - Address already > > in > > > > use: > > > > > > JVM_Bind > > > > > > > > > > > > It does not seem to matter what port is used. > > > > > > > > > > > > What am I doing wrong? > > > > > > > > > > > > Thanks, > > > > > > T > > > > > > > > > > ________________________________ > Got a little couch potato? > Check out fun summer activities for kids. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
