I've used the SOAPMonitor from the command line, not via the applet. It operates as a proxy like tcpmon where you'll need to point your client to an IP/port that the SOAPMonitor is listening to and configure SOAPMonitor to relay to the packets to the actual SOAP service IP/port. I'm assuming that the applet functions in the same way.
Note that you can change either the IP or the port - you don't have to change the port. So you could set your client to talk to a different IP - keeping the port number the same - and have SOAPMonitor listening on that IP/port. Many people forget that you have the whole 127.0.0.0/8 net available on your boxes. I've tried this on Win2K/XP/Linux. For example, the client could be configured to talk to 127.0.0.2/TCP:8080. The SOAPMonitor could be configure to listen on 127.0.0.2/TCP:8080 and talk to a server on 127.0.0.1/TCP:8080. Where the server actually lives on 127.0.0.1/TCP:8080. JBoss can be started with a "-b IP_ADDR" argument that will bind it's services to a specific IP rather than all host interfaces. e.g. "-b 127.0.0.3" will configure JBoss to bind to only IP 127.0.0.3. I noticed log messages about clustering when doing this, but I haven't cared about clustering yet. This gives you some creativity in seting up a testing scenario. r, Lance View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863017#3863017 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863017 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
