Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] My problem with getting the Jetty 8.1.7 WebSocket client to connect to a Tomcat server


The technique that most of the jetty core developers use is Wireshark. ( )
Course, its important to capture non-SSL traffic in this case.
The captured traffic should identify where the problem may lay.

Another choice is to file the bug at bugzilla with a small example project demonstrating the behavior you are experiencing, along with some instructions on how to build (if needed) and run the project.

Joakim Erdfelt <joakim@xxxxxxxxxxx>

On Thu, Oct 25, 2012 at 4:54 AM, Tomas Normark <tomas@xxxxxxxxx> wrote:
Hi Joakim,

I sent a message to the Jetty mailing list last Friday telling about my problems
to connect a Jetty 8.1.7 WebSocket Java client to a Tomcat 7.0.30 server.
You answered and asked me to file a bug report at along
with a capture of the network traffic.

I would now like to ask you about how that capture can be most easily done.
I have tried using Fiddler but it does not seem to give me anything even if
I try the standard tricks for getting it to show traffic on localhost.

Can you give short instructions for what software I should use to perform the
logging and how to do it or send me a link to some web page where it is
described how the logging can be done?

I can also tell you that since the last testing I have been testing a
Jetty 8.1.7 server as well. To the Jetty server I can connect using a client
in .NET, _javascript_ or using the Jetty 8.1.7 client from Java.

If I use a Tomcat 7.0.30 server I can also connect using a .NET or _javascript_
client but the Jetty 8.1.7 Java client times out during the initial handshake.

For now we need to use the Tomcat 7.0.30 server so I hope you can help me
forward in trouble shooting what might be the problem with using the
Jetty client with the Tomcat server.

I hope it is OK to mail you directly like this. I thought it would be easier
than posting to the mailing list.

Best regards,

Tomas Normark

Back to the top