Ok , I can't really wait for that to come out :( Any tips on using maybe JNI
to set that sockopt? (SO_REUSEADDR)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
First I must say thanks all for the help!
In this problem, I really would like to re-use the connections. Is it
possible to set SO_REUSEADDR for a server socket in Java?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Kevin,
I just remembered that I run into the same problem when using Sun JDK1.2.2_006.
Switching to JDK 1.3 fixed the problem. Apperently 1.2.2_006 was not
closing the underlying Linux sockets correctly.
Alexander
--
To
> 1. I'm assuming you are "NULL"ing the used sockets, so they get garbage
> collected?
You should not rely on garbage collection for scarce resources such
as file and socket handles. Make sure you invoke socket.close() when
you're done.
Since you're worki
Thanks a lot for the help.
I'm wondering what is the downside of setting fd_max to some huge number...
Is there one?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
Kevin,
You probably need to use the Socket.setSoLinger() call.
Nathan
On Fri, Apr 27, 2001 at 09:59:57AM -0400, kevin1 wrote:
> Hello all,
> I am somewhat new to java, and I am having a problem with a server app that
>I w
> rote.
> What is happening is that for each connection to th
happening fast enough, and as more requests come
> in, more ports are unuseable until the box will not accept any more
> connections.
>
> How does one get the ServerSocket to re-use ports instead of opening new
> ones?
1. I'm assuming you are "NULL"ing the use
On Fri, Apr 27, 2001 at 08:27:23AM -0500, Joi Ellis wrote:
> I wrote off the IBM JVM last year after living with swing bugs and
> a broken debugger that dumped core every time I tried to use it. I
> deleted it off my machine after I spent a day crafting a reproducible
> test case for the debugge
Hello all,
I am somewhat new to java, and I am having a problem with a server app that I w
rote.
What is happening is that for each connection to the server, it returns a Socket and co
ntinues the conversation. This is fine. The socket does some simple tasks and then I
close it. That
dear all
I am using tomcat on linux. My servlet is in a classes subforder under
my home. When servlet run, I don't see the output from System.out.println
printed to the screen. What should I do in order to see the output. (Before
I was using NT, the output would be printed to the Dos windo
On Thu, 26 Apr 2001, Vladimir G Ivanovic wrote:
> Why don't you try IBM's JDK? The Volano test results show it to be a
> powerful performer, and coupled with jikes, it makes pretty nifty
> development environment. Seems like an all-around winner to me.
>
> But that may not solve your problem. I
e very **nasty bugs**.
Two of them which I have recently run onto (present in SR6):
- You cannot create two multicast sockets in the same process (some
confusion with the kernel interfaces, works with 2.2.x kernels but not with
2.4.x)
- Interrupting threads that do reads in native code does not res
se green threads, or a
JE> classic JVM, the tests fail.
JE> The tests are braindead simple. Open a udp listen socket, open a
JE> send socket, send a packet, close the send socket, close the
JE> listen socket. The point of the tests isn't to test the sockets,
JE> it
send
socket, send a packet, close the send socket, close the listen socket.
The point of the tests isn't to test the sockets, it's to test other
code's ability to decipher the received udp packet's payload properly.
The send socket is part of the text fixture, ultimately the listen
I opened what I think is the last bug holding back the VolanoMark
network scalability tests under Blackdown JDK 1.2.2:
Bug Id 1604, "Segmentation violation with 1020 timeout sockets"
http://www.blackdown.org/cgi-bin/jdk/incoming?id=1604
I guess we report these bugs to Sun a
Dimitris Terzis wrote:
> Do you think there would be any interest in releasing this as open source to
> the community? If yes, I could persuade the folks over here to allow me
> doing so and will send over the current code as an alpha version, which we
> could then play with and improve (and/or us
Hi guys...
As part of my (Nortel Networks-funded) PhD work, I have spent a considerable
amount of time for more than a year now playing with Java support for ATM.
Because I haven't been able to find anything standard, I ended up creating
my own implementation of Java sockets for Linux ATM
> Check your /etc/route.conf file. The multicast route must be set to
> something like this if you want to use multicast on eth0:
> 224.0.0.00.0.0.0240.0.0.0eth0
>
this was the problem. i used "route add -net 224.0.0.0 netmask 240.0.0.0
dev eth0" to add the route to the routing
0.0240.0.0.0eth0
If all of this is ok it should work.
Rudi
-Original Message-
From: Wright Robert B Civ 96 CG/SCWDE <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Date: Friday, September 10, 1999 6:37 AM
Subject: mutlicast sockets
>i
Ted Neward wrote:
>
> Somebody made mention, in the JavaSpaces list, that if you want to do
> JavaSpaces (which uses Multicast sockets, as I understand it), that you have
> to have multicast support compiled into the kernel.
>
> It's hearsay and rumor, but maybe it'
CG/SCWDE; [EMAIL PROTECTED]
> Subject: Re: mutlicast sockets
>
>
> Somebody made mention, in the JavaSpaces list, that if you want to do
> JavaSpaces (which uses Multicast sockets, as I understand
> it), that you have
> to have multicast support compiled into the kernel.
Somebody made mention, in the JavaSpaces list, that if you want to do
JavaSpaces (which uses Multicast sockets, as I understand it), that you have
to have multicast support compiled into the kernel.
It's hearsay and rumor, but maybe it'll help?
Ted Neward
Patterns/C++/Java/CORBA/EJ
i'm getting a "java.net.SocketException: No such device" when executing this
code:
MulticastSocket socket = new MulticastSocket();
InetAddress address = InetAddress.getByName("230.0.0.1");
socket.joinGroup(address);
through jdb i discovered that the joinGroup method is throwing the
exceptio
;;
PrintWriter writer = new PrintWriter(socket.getOutputStream());
writer.write(command);
writer.write(CRLF);
writer.flush(); // flush the buffer!
-Gary
Greg Walker wrote:
>
> I am having a problem with a server written in java that uses sockets.
> The server runs fine; the prob
You should be able to track if there's any exception occured to the sockets
in question, of course that's assuming that you're performing
IO on them, such as attempting to read or write on the sockets. One thing you
should keep watch for is the variable that keeps track o
I am having a problem with a server written in java that uses sockets.
The server runs fine; the problem arises when I try to access it. The
client is simply telnet and after making a connection, and receiving a
handful of bytes, the client hangs as if the server is not responding.
Yet the server
... (mail header stuff deleted) ...
> From: "Jauvane Cavalcante de Oliveira" <[EMAIL PROTECTED]>
> ... (mail header stuff deleted) ...
> To: Bill Paladino <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: sockets; data transfer limits
> ... (mail heade
> Has anyone come across a limit on the size of a transfer thru a Java socket?
Yes, I had this problem under Solaris. In my case packets greater than 1500
bytes was tryncated into 1500, most likely because of the ethernet packet size.
I submitted such behaviour to Javasoft in their Bug Parade sec
Has anyone come across a limit on the size of a transfer thru a Java socket?
I'm using JDK116 (can't be certain of the version; downloaded it ~10/1/98).
3,541 bytes doesn't seem like much but anything larger than that gets lost.
This is NOT a problem on Windows-95 which I'd rather not use.
Topi Maenpaa writes:
> I have been observing your java port effort for a long time, and I'm
> happy noticing that it seems pretty much ready now...
>
> You may already know this, but it might help you to know that the
> multicast socket bug in Linux kernel is corrected in 2.2.1 (may be in
>
I have been observing your java port effort for a long time, and I'm
happy noticing that it seems pretty much ready now...
You may already know this, but it might help you to know that the
multicast socket bug in Linux kernel is corrected in 2.2.1 (may be in
2.2.0 also).
Good luck
-Topi-
<< htt
Hi,
I am trying to write a server program that accepts a large number of
socket connection. However, when the number of sockets goes over about
250, the accept call either blocks, or throws an
InvalidArgumentException.
I did wonder if this is related to the maximum number of open file
On 30-Jun-98 Charles Forsythe wrote:
> I have a simple client/sever benchmark (code below) designed to see how
> many simultanious open sockets I can sustain. The answer seems to be
> about 250. This is really sad because the crufty HP-UX JDK 1.1.3
> managed to make it t
maybe i should have more clearly stated, thats for java/vm/linux. the "C"
interface to the os has been "enhanced" to work with linux et al. That
limit need not be there, i guess its just another ti=hing to look at
gat
Charles Forsythe wrote:
> > I suspect at this time it is a hard coded limit in
> I suspect at this time it is a hard coded limit in java/vm.
Hmmm... possible, but why is it different for HP and Linux? Why is it,
for that matter, *worse* in JDK 1.1.6 on Linux than 1.1.3 on HP-UX?
-- Charles
Charles Forsythe wrote:
>
> Fellow Java Linux users:
>
> I have a simple client/sever benchmark (code below) designed to see how
> many simultanious open sockets I can sustain. The answer seems to be
> about 250. This is really sad because the crufty HP-UX JDK 1.1.3
>
I suspect at this time it is a hard coded limit in java/vm. Not just for
sockets in particular, but for the sum of all opened channels
gat
Charles Forsythe wrote:
> Fellow Java Linux users:
>
> I have a simple client/sever benchmark (code below) designed to see how
> many simul
Fellow Java Linux users:
I have a simple client/sever benchmark (code below) designed to see how
many simultanious open sockets I can sustain. The answer seems to be
about 250. This is really sad because the crufty HP-UX JDK 1.1.3
managed to make it to 1200. The exception is weird, too
Hi All,
I am having a client server application. The client opens a socket
connection to
the server. On the server side I create InputStream and OutputStream to
Communicate
with the client.
I am doing inputstream.available() to check if there are any bytes to be read.
Now the problem is if the
39 matches
Mail list logo
