[ openjms-Bugs-756237 ] telnet-ing directly to tcp connector/jndi yields OutOfMemory

"SourceForge.net" <[email protected]>
Newsgroups gmane.comp.java.openjms.devel
Message-ID <[email protected]>
Bugs item #756237, was opened at 2003-06-18 07:17
Message generated for change (Comment added) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=756237&group_id=54559

Category: server
Group: None
Status: Open
>Resolution: Later
Priority: 5
Submitted By: John Evans (lgas)
>Assigned to: Tim Anderson (tanderson)
Summary: telnet-ing directly to tcp connector/jndi yields OutOfMemory

Initial Comment:
If you start the OpenJMS server with the 
tcp_jms_full.xml configuration and telnet to either the 
port 3030 (the tcp connector) or port 3035 (the jndi 
connector) and hit return several times, you will see an 
OutOfMemoryError in the output from the server.

Obviously the server is not expecting people to telnet to 
it, but in "the wild" this will happen all the time, so this 
is a denial-of-service problem.

----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2003-06-24 20:54

Message:
Logged In: YES 
user_id=557161

I'm a bit reluctant to spend any time fixing this as the tcp 
connector is going to be replaced in the near future.

In any case, it won't fix all DOS issues - a client could 
hammer the server with new connections and cause the same 
problem.

The tcps connector should be able to avoid the problem you 
describe.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=756237&group_id=54559
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.