From: Phil B. <pbu...@ib...> - 2007-04-09 17:40:14
|
Tim Anderson <tma@...> writes: > > You're absolutely right. There should be a call to > Socket.setTcpNoDelay(true) in the socket creation code. > > -Tim > > Steve Condas wrote: > > All, > > > > This is my final message for the night. I said that the performance > > problem happened for both the TCP and RMI connectors, but in fact, it > > does not happen with the RMI connector. I had a configuration error > > where I was using RMI for JNDI, but TCP/IP for the actual data. With > > RMI correctly configured I am now getting more than 700 messages per > > second. > > > > Steve I am having the same problem with messages not being sent fast enough on my Linux machine. The program works fine on my Windows machine. I am running the JMS server locally on both the Windows and Linux machines. I have tried using both TCP and RMI but both seem to have the same problem. When debugging the program, I can see that there is still a connection on port 3035, even when I am using RMI (which is supposed to be on port 1099). How did you correctly configure RMI for both JNDI and the data? Thanks, Phil |