Re: Using Eclipse / TCP monitor
Hi, Sorry I couldn't get back to you earlier... Are you using the SOAP/TCp monitor that comes supplied with Axis or eclipse have one? On 5/9/05, Plorks mail <[EMAIL PROTECTED]> wrote: > > > Can anyyone help me out > > I've created a web service using eclipse and I have a client.java file that > calls a method in the web service. > > I'm trying to run my client.java file so that i can see the SOAP > response/request > > I right-click the file select Run As - Run, click the Args tab put the > progrram args in the Program args box, then click apply and Run > > However, i'm not seeing any movement in the TCP- monitor. I know my > client.java methd is being called as i've got the syste,.out.println in the > output but can't see anything hapening in the tcp monitor > > Can anyone help me to get this to work > > Many Thanks > > _ > Be the first to hear what's new at MSN - sign up to our free newsletters! > http://www.msn.co.uk/newsletters > > -- Classic Family Guy. "Yes, but no sprinkles. For every sprinkle i find, i shall KILL you." - Stewie "And Joe, I've had new neighbors before, but none of them were half the man you are. Since you're half a man already, that splits them into some kind of fraction I can't even measure." - Peter "Hello, 911? It's Quagmire. Yeah, it's caught in the window this time." Quagmire "I got an idea, an idea so smart my head would explode if I even began to know what I was talking about." - Peter
Using Eclipse / TCP monitor
Can anyyone help me out I've created a web service using eclipse and I have a client.java file that calls a method in the web service. I'm trying to run my client.java file so that i can see the SOAP response/request I right-click the file select Run As - Run, click the Args tab put the progrram args in the Program args box, then click apply and Run However, i'm not seeing any movement in the TCP- monitor. I know my client.java methd is being called as i've got the syste,.out.println in the output but can't see anything hapening in the tcp monitor Can anyone help me to get this to work Many Thanks _ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters
Re: TCP Monitor
Are you using TCPMonitor from Axis 1.2RC3? I tried it and it bombed on me so I continues using the Axis 1.1 version. BTW, TCPMonitor is entirely independent of Axis. It simple redirects TCP traffic while logging requests and responses. Do you have a publicly accessible URL for your web service that I could try? Jeff - Original Message - From: James Chiu To: axis-user@ws.apache.org Sent: Wednesday, April 27, 2005 5:10 PM Subject: RE: TCP Monitor The server side is hosted by IIS only and does not involve with Tomcat/Axis. The sample WS Url is like http://servername/ReportServer/ReportService.asmx. Does TCP Monitor work with IIS directly? Any other suggestions? After entering the data as described in the previous emails, I received the following error while clicking the Add button from TCP Monitor: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at org.apache.axis.utils.tcpmon$8.valueChanged(tcpmon.java:1426) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSel ectionModel.java:187) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSel ectionModel.java:167) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSel ectionModel.java:214) at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSele ctionModel.java:408) at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSele ctionModel.java:417) at javax.swing.DefaultListSelectionModel.removeSelectionIntervalImpl(Def aultListSelectionModel.java:510) at javax.swing.DefaultListSelectionModel.removeSelectionInterval(Default ListSelectionModel.java:482) at javax.swing.JTable.checkLeadAnchor(JTable.java:2965) at javax.swing.JTable.tableRowsInserted(JTable.java:3081) at javax.swing.JTable.tableChanged(JTable.java:3015) at javax.swing.table.AbstractTableModel.fireTableChanged(AbstractTableMo del.java:280) at javax.swing.table.AbstractTableModel.fireTableRowsInserted(AbstractTa bleModel.java:215) at javax.swing.table.DefaultTableModel.insertRow(DefaultTableModel.java: 349) at javax.swing.table.DefaultTableModel.addRow(DefaultTableModel.java:323 ) at javax.swing.table.DefaultTableModel.addRow(DefaultTableModel.java:334 ) at org.apache.axis.utils.tcpmon$Listener.(tcpmon.java:1474) at org.apache.axis.utils.tcpmon$5.actionPerformed(tcpmon.java:431) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:18 49) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav a:2169) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel .java:420) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258 ) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL istener.java:234) at java.awt.Component.processMouseEvent(Component.java:5488) at javax.swing.JComponent.processMouseEvent(JComponent.java:3093) at java.awt.Component.processEvent(Component.java:5253) at java.awt.Container.processEvent(Container.java:1966) at java.awt.Component.dispatchEventImpl(Component.java:3955) at java.awt.Container.dispatchEventImpl(Container.java:2024) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212 ) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822) at java.awt.Container.dispatchEventImpl(Container.java:2010) at java.awt.Window.dispatchEventImpl(Window.java:1766) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.EventQueue.dispatchEvent(EventQueue.java:463) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchTh read.java:234) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre ad.java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) James From: Jeff [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 8:55 PMTo: axis-user@ws.apache.orgSubject: Re: TCP Monitor
RE: TCP Monitor
The server side is hosted by IIS only and does not involve with Tomcat/Axis. The sample WS Url is like “http://servername/ReportServer/ReportService.asmx. Does TCP Monitor work with IIS directly? Any other suggestions? After entering the data as described in the previous emails, I received the following error while clicking the “Add” button from TCP Monitor: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at org.apache.axis.utils.tcpmon$8.valueChanged(tcpmon.java:1426) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSel ectionModel.java:187) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSel ectionModel.java:167) at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSel ectionModel.java:214) at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSele ctionModel.java:408) at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSele ctionModel.java:417) at javax.swing.DefaultListSelectionModel.removeSelectionIntervalImpl(Def aultListSelectionModel.java:510) at javax.swing.DefaultListSelectionModel.removeSelectionInterval(Default ListSelectionModel.java:482) at javax.swing.JTable.checkLeadAnchor(JTable.java:2965) at javax.swing.JTable.tableRowsInserted(JTable.java:3081) at javax.swing.JTable.tableChanged(JTable.java:3015) at javax.swing.table.AbstractTableModel.fireTableChanged(AbstractTableMo del.java:280) at javax.swing.table.AbstractTableModel.fireTableRowsInserted(AbstractTa bleModel.java:215) at javax.swing.table.DefaultTableModel.insertRow(DefaultTableModel.java: 349) at javax.swing.table.DefaultTableModel.addRow(DefaultTableModel.java:323 ) at javax.swing.table.DefaultTableModel.addRow(DefaultTableModel.java:334 ) at org.apache.axis.utils.tcpmon$Listener.(tcpmon.java:1474) at org.apache.axis.utils.tcpmon$5.actionPerformed(tcpmon.java:431) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:18 49) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav a:2169) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel .java:420) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258 ) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL istener.java:234) at java.awt.Component.processMouseEvent(Component.java:5488) at javax.swing.JComponent.processMouseEvent(JComponent.java:3093) at java.awt.Component.processEvent(Component.java:5253) at java.awt.Container.processEvent(Container.java:1966) at java.awt.Component.dispatchEventImpl(Component.java:3955) at java.awt.Container.dispatchEventImpl(Container.java:2024) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212 ) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822) at java.awt.Container.dispatchEventImpl(Container.java:2010) at java.awt.Window.dispatchEventImpl(Window.java:1766) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.EventQueue.dispatchEvent(EventQueue.java:463) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchTh read.java:234) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre ad.java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) James From: Jeff [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 8:55 PM To: axis-user@ws.apache.org Subject: Re: TCP Monitor BTW, I had assumed that you had a valid web service URL. The IIS server might be running independently of Tomcat/Axis and the web service may not even be hosted by Tomcat/Axis. You need to consult the web service documentation. IIS could be redirecting to Tomcat/Axis or some other web service hosting software and may or may not be doing that via port 80. If IIS is not redirecting then you need to connect directly to the listening port of the web service. In the case of Tomcat/Axis the default port is 8080, of course. Anyone setting up a web service on a port other than port 80 needs to ensure that if external clients are expected to connect from outside a firewall then the firewall is configured to permit access through that port. Jeff - Original Message - From: Jeff To: axis-user@ws.
Re: TCP Monitor
BTW, I had assumed that you had a valid web service
URL. The IIS server might be running independently of Tomcat/Axis and the web
service may not even be hosted by Tomcat/Axis. You need to consult the web
service documentation. IIS could be redirecting to Tomcat/Axis or some other web
service hosting software and may or may not be doing that via port 80. If IIS is
not redirecting then you need to connect directly to the listening port of the
web service. In the case of Tomcat/Axis the default port is 8080, of course.
Anyone setting up a web service on a port other than port 80 needs to ensure
that if external clients are expected to connect from outside a firewall then
the firewall is configured to permit access through that port.
Jeff
- Original Message -
From:
Jeff
To: axis-user@ws.apache.org
Sent: Tuesday, April 26, 2005 11:43
PM
Subject: Re: TCP Monitor
James,
TCPMonitor listens for connections at the
specified port on the machine on which it is running. This port is any free
port you know of or guess at, e.g. is unlikely to be in use. The
client-side software must be configured to use the TCPMonitor by replacing the
target host name and port (which could just be the default port 80). Here's
what to do, assuming that TCPMonitor will be running on the same computer as
the client software (if it isn't then change 127.0.0.1 that appears below for
the host name or IP address of the machine running TCPMonitor):
- Pick a port number for
TCPMonitor to listen on, let's suppose it's .
- Make a note of the target
host name (or IP address) plus the port number of the target web
service.
E.g.
for http://services.xmethods.net/soap/servlet/rpcrouter
the host name is services.xmethods.net and the port number is 80.
E.g.
for http://10.0.0.12:8080/axis/services/ScsServiceSoap
the IP address is 10.0.0.12 and the port number is 8080.
- Now change the target web
service URL in the client-side code to point to TCPMonitor.
E.g.
http://services.xmethods.net/soap/servlet/rpcrouter
becomes http://127.0.0.1:/soap/servlet/rpcrouter
E.g.
http://10.0.0.12:8080/axis/services/ScsServiceSoap becomes
http://127.0.0.1:/axis/services/ScsServiceSoap
- Recompile the client-side
code.
- Start TCPMonitor and enter
the Listen Port # as . Enter the appropriate Target Hostname and the
Target Port # as noted in the second step
E.g.
for http://services.xmethods.net/soap/servlet/rpcrouter
Target Hostname is services.xmethods.net and the Target Port #
is 80
E.g.
for http://10.0.0.12:8080/axis/services/ScsServiceSoap Target
Hostname is 10.0.0.12 and the Target Port # is
8080
- After entering the correct data, start TCPMonitor
listening by clicking the Add button.
- Run the client software and watch TCPMonitor for
activity.
Jeff
- Original Message -
From:
James
Chiu
To: axis-user@ws.apache.org
Sent: Tuesday, April 26, 2005 7:06
PM
Subject: TCP Monitor
Hi,
I like to use tcpmon to see
outgoing messages and incoming messages of my java WS client. The server
side is hosted by Microsoft IIS.
I am not sure the exact
arguments (listenPort
targetHost targetPort) in this case.
What is the listen
port?
I assume the targetHost is the
machine of the server side.
I think the targetPort is 80 by
default in IIS.
Thanks for your
help,
James
Re: TCP Monitor
James, TCPMonitor listens for connections at the specified port on the machine on which it is running. This port is any free port you know of or guess at, e.g. is unlikely to be in use. The client-side software must be configured to use the TCPMonitor by replacing the target host name and port (which could just be the default port 80). Here's what to do, assuming that TCPMonitor will be running on the same computer as the client software (if it isn't then change 127.0.0.1 that appears below for the host name or IP address of the machine running TCPMonitor): - Pick a port number for TCPMonitor to listen on, let's suppose it's . - Make a note of the target host name (or IP address) plus the port number of the target web service. E.g. for http://services.xmethods.net/soap/servlet/rpcrouter the host name is services.xmethods.net and the port number is 80. E.g. for http://10.0.0.12:8080/axis/services/ScsServiceSoap the IP address is 10.0.0.12 and the port number is 8080. - Now change the target web service URL in the client-side code to point to TCPMonitor. E.g. http://services.xmethods.net/soap/servlet/rpcrouter becomes http://127.0.0.1:/soap/servlet/rpcrouter E.g. http://10.0.0.12:8080/axis/services/ScsServiceSoap becomes http://127.0.0.1:/axis/services/ScsServiceSoap - Recompile the client-side code. - Start TCPMonitor and enter the Listen Port # as . Enter the appropriate Target Hostname and the Target Port # as noted in the second step E.g. for http://services.xmethods.net/soap/servlet/rpcrouter Target Hostname is services.xmethods.net and the Target Port # is 80 E.g. for http://10.0.0.12:8080/axis/services/ScsServiceSoap Target Hostname is 10.0.0.12 and the Target Port # is 8080 - After entering the correct data, start TCPMonitor listening by clicking the Add button. - Run the client software and watch TCPMonitor for activity. Jeff - Original Message - From: James Chiu To: axis-user@ws.apache.org Sent: Tuesday, April 26, 2005 7:06 PM Subject: TCP Monitor Hi, I like to use tcpmon to see outgoing messages and incoming messages of my java WS client. The server side is hosted by Microsoft IIS. I am not sure the exact arguments (listenPort targetHost targetPort) in this case. What is the listen port? I assume the targetHost is the machine of the server side. I think the targetPort is 80 by default in IIS. Thanks for your help, James
TCP Monitor
Hi, I like to use tcpmon to see outgoing messages and incoming messages of my java WS client. The server side is hosted by Microsoft IIS. I am not sure the exact arguments (listenPort targetHost targetPort) in this case. What is the listen port? I assume the targetHost is the machine of the server side. I think the targetPort is 80 by default in IIS. Thanks for your help, James
