head	1.8;
access;
symbols;
locks
	nobody:1.8; strict;
comment	@# @;


1.8
date	99.07.30.05.48.57;	author nobody;	state Exp;
branches;
next	1.7;

1.7
date	99.04.21.18.43.14;	author nobody;	state Exp;
branches;
next	1.6;

1.6
date	99.04.01.18.10.44;	author nobody;	state Exp;
branches;
next	1.5;

1.5
date	99.03.31.03.16.07;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.03.29.20.13.10;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.03.26.19.38.10;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.03.26.19.36.42;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.03.26.19.36.21;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.8
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 2
IDependOn-Set: 7
IDependOn-Set: 76
IDependOn-Set: 79
IDependOn-Set: 80
LastModifiedSecs: 933313736
Parent: 7
SequenceNumber: 6
Title: ERROR: java.net.BindException: Address already in use
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 922477080
Type: monospaced
Lines: 11
Apache JServ: Exception creating the server socket: java.net.BindException: 
Address already in use

If you are getting the above error, it is most likely that you have another 
copy of the JVM running. On a unix machine, type:

ps -uax | grep java
or
ps -ef | grep java

If you see a JVM running you must kill it.
EndPart: 0
Part: 1
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 922738380
Type: monospaced
Lines: 20

----------
From: Pierpaolo Fumagalli <p_fumagalli@@fumagalli.org>
To: Java Apache Users <java-apache-users@@list.working-dogs.com>
Subject: Re: Me too java.net.BindException error
Date: Mon, Mar 29, 1999, 7:38 AM


Jonathan Buschmann wrote:
> 
> For the record I've got Apache/1.3.4, java 1.1.6, Apache-JServ-1.0b2 as
> a DSO on Solaris 2.7.
> (P.S Because I like DSOs).
> 
I think there's something buggy in JDK 1.1.6 on the ServerSocket. I can
remember it from a discussion ran here some months ago... I'd suggest
you to upgrade to the LATEST JVM for Solaris... (1.1.7 or 1.2 should
work)...

        Pier
EndPart: 1
Part: 2
Author-Set: dking@@opentable.com
HideAttributions: 1
LastModifiedSecs: 933313736
Type: monospaced
Lines: 1
I get this error when I restart the server too soon after stopping it. Apparently you just have to let it die gracefully, then restart, otherwise to socket hasn't freed up yet.
EndPart: 2
@


1.7
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 924720194
d9 1
a9 1
SequenceNumber: 5
d56 8
@


1.6
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 922990244
d9 1
a9 1
SequenceNumber: 4
a55 10
Part: 2
Author-Set: anonymous
HideAttributions: 1
Type: directory
Lines: 4
Subcategories:


Answers in this category:
EndPart: 2
@


1.5
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 922738390
d9 1
a9 1
SequenceNumber: 3
d56 10
@


1.4
log
@null
@
text
@a30 1
DateOfPart: 1999-Mar-29 12:13pm
d32 1
@


1.3
log
@null
@
text
@d6 2
a7 1
LastModifiedSecs: 922477090
d9 1
a9 1
SequenceNumber: 2
a12 1
DateOfPart: 1999-Mar-26 11:38am
d14 1
d29 27
@


1.2
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 922477002
d8 1
a8 1
SequenceNumber: 1
d10 18
@


1.1
log
@null
@
text
@d4 1
d6 1
a6 1
LastModifiedSecs: 922476980
d8 2
a9 2
SequenceNumber: 0
Title: New Item
@
