SEVERE: selectorThread.stopException

[Alan Williamson]

I am still getting this exception and its very confusing.  But i think i
may have spotted what changed when i upgraded the production machines to 1.8

In the 1.6 i was including the following JAR files in my java startup

Old:
CP=$CP:lib/framework-1.6.1.jar
CP=$CP:lib/portunif-1.6.1.jar
CP=$CP:lib/rcm-1.6.1.jar
CP=$CP:lib/http-utils-1.6.1.jar
CP=$CP:lib/http-1.6-SNAPSHOT.jar



Now i am only using:

New:
CP=$CP:lib/grizzly-framework-1.8.0.jar
CP=$CP:lib/grizzly-http-webserver-1.8.0.jar



Am i missing something?

thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

Alan Williamson wrote:

> I am still getting this exception and its very confusing.  But i think i
> may have spotted what changed when i upgraded the production machines to
> 1.8
>
> In the 1.6 i was including the following JAR files in my java startup
>
> Old:
> CP=$CP:lib/framework-1.6.1.jar
> CP=$CP:lib/portunif-1.6.1.jar
> CP=$CP:lib/rcm-1.6.1.jar
> CP=$CP:lib/http-utils-1.6.1.jar
> CP=$CP:lib/http-1.6-SNAPSHOT.jar
>
>
>
> Now i am only using:
>
> New:
> CP=$CP:lib/grizzly-framework-1.8.0.jar
> CP=$CP:lib/grizzly-http-webserver-1.8.0.jar
>
>
> Am i missing something?

Can you remove the grizzly-framework jar to see if that makes a
difference? That jar is not needed as its contents are included with the
latter one. Those bundles (grizzly-XXX-webserver) have been added only
since 1.7.x


Thanks

-- Jeanfrancois


>
> thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

Thanks Jeanfrancois, tried that.  :(

no difference.

now here is something; i went back to Grizzly1.6, all is well.  No problems.

So something is definitely up with either the way i am handling 1.8.

i am running JDK1.6


SEVERE: selectorThread.stopException
java.lang.InternalError
         at
sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:752)
         at sun.misc.URLClassPath.getResource(URLClassPath.java:168)
         at java.net.URLClassLoader$1.run(URLClassLoader.java:192)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
         at
java.util.ResourceBundle$RBClassLoader.loadClass(ResourceBundle.java:445)
         at
java.util.ResourceBundle$Control.newBundle(ResourceBundle.java:2383)
         at java.util.ResourceBundle.loadBundle(ResourceBundle.java:1406)
         at java.util.ResourceBundle.findBundle(ResourceBundle.java:1365)
         at java.util.ResourceBundle.findBundle(ResourceBundle.java:1292)
         at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1234)
         at java.util.ResourceBundle.getBundle(ResourceBundle.java:715)
         at java.util.logging.Level.getLocalizedName(Level.java:223)
         at
java.util.logging.SimpleFormatter.format(SimpleFormatter.java:64)
         at java.util.logging.StreamHandler.publish(StreamHandler.java:179)
         at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88)
         at java.util.logging.Logger.log(Logger.java:472)
         at java.util.logging.Logger.doLog(Logger.java:494)
         at java.util.logging.Logger.log(Logger.java:583)
         at com.sun.grizzly.Controller.doSelect(Controller.java:498)
         at
com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:82)
         at
com.sun.grizzly.Controller.startSelectorHandlerRunner(Controller.java:1117)
         at com.sun.grizzly.Controller.start(Controller.java:924)
         at
com.sun.grizzly.http.SelectorThread.startListener(SelectorThread.java:1196)
         at
com.sun.grizzly.http.SelectorThread.run(SelectorThread.java:1063)
         at
com.sun.grizzly.http.SelectorThread.startEndpoint(SelectorThread.java:1128)
         at com.mediafed.net.HttpServer.<init>(HttpServer.java:109)
         at com.mediafed.HttpGateway.<init>(HttpGateway.java:55)
         at com.mediafed.HttpGateway.main(HttpGateway.java:47)
Caused by: java.util.zip.ZipException: error in opening zip file
         at java.util.zip.ZipFile.open(Native Method)
         at java.util.zip.ZipFile.<init>(ZipFile.java:114)
         at java.util.jar.JarFile.<init>(JarFile.java:133)
         at java.util.jar.JarFile.<init>(JarFile.java:70)
         at
sun.misc.URLClassPath$JarLoader.getJarFile(URLClassPath.java:643)
         at
sun.misc.URLClassPath$JarLoader.access$600(URLClassPath.java:538)
         at sun.misc.URLClassPath$JarLoader$1.run(URLClassPath.java:605)
         at java.security.AccessController.doPrivileged(Native Method)
         at
sun.misc.URLClassPath$JarLoader.ensureOpen(URLClassPath.java:597)
         at
sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:750)




Jeanfrancois Arcand wrote:

> Salut,
>
> Alan Williamson wrote:
>> I am still getting this exception and its very confusing.  But i think
>> i may have spotted what changed when i upgraded the production
>> machines to 1.8
>>
>> In the 1.6 i was including the following JAR files in my java startup
>>
>> Old:
>> CP=$CP:lib/framework-1.6.1.jar
>> CP=$CP:lib/portunif-1.6.1.jar
>> CP=$CP:lib/rcm-1.6.1.jar
>> CP=$CP:lib/http-utils-1.6.1.jar
>> CP=$CP:lib/http-1.6-SNAPSHOT.jar
>>
>>
>>
>> Now i am only using:
>>
>> New:
>> CP=$CP:lib/grizzly-framework-1.8.0.jar
>> CP=$CP:lib/grizzly-http-webserver-1.8.0.jar
>>
>>
>> Am i missing something?
>
> Can you remove the grizzly-framework jar to see if that makes a
> difference? That jar is not needed as its contents are included with the
> latter one. Those bundles (grizzly-XXX-webserver) have been added only
> since 1.7.x
>
>
> Thanks
>
> -- Jeanfrancois
>
>
>>
>> thanks
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

--
Alan Williamson

  Try our free registrationless email/sms reminder
    http://yourli.st/

  b: http://alan.blog-city.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

Scratch that -- its just done it with 1.6! :(

Can i disable the logging some how?

Jeanfrancois Arcand wrote:

> Salut,
>
> Alan Williamson wrote:
>> I am still getting this exception and its very confusing.  But i think
>> i may have spotted what changed when i upgraded the production
>> machines to 1.8
>>
>> In the 1.6 i was including the following JAR files in my java startup
>>
>> Old:
>> CP=$CP:lib/framework-1.6.1.jar
>> CP=$CP:lib/portunif-1.6.1.jar
>> CP=$CP:lib/rcm-1.6.1.jar
>> CP=$CP:lib/http-utils-1.6.1.jar
>> CP=$CP:lib/http-1.6-SNAPSHOT.jar
>>
>>
>>
>> Now i am only using:
>>
>> New:
>> CP=$CP:lib/grizzly-framework-1.8.0.jar
>> CP=$CP:lib/grizzly-http-webserver-1.8.0.jar
>>
>>
>> Am i missing something?
>
> Can you remove the grizzly-framework jar to see if that makes a
> difference? That jar is not needed as its contents are included with the
> latter one. Those bundles (grizzly-XXX-webserver) have been added only
> since 1.7.x
>
>
> Thanks
>
> -- Jeanfrancois
>
>
>>
>> thanks
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

--
Alan Williamson

  Try our free registrationless email/sms reminder
    http://yourli.st/

  b: http://alan.blog-city.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Alan Williamson wrote:
> Scratch that -- its just done it with 1.6! :(
>
> Can i disable the logging some how?

Give me 15 minutes and I will send you a patch that avoid logging and
just print on the screen the exception (before the log).

A+

-- Jeanfrancois

>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> Alan Williamson wrote:
>>> I am still getting this exception and its very confusing.  But i
>>> think i may have spotted what changed when i upgraded the production
>>> machines to 1.8
>>>
>>> In the 1.6 i was including the following JAR files in my java startup
>>>
>>> Old:
>>> CP=$CP:lib/framework-1.6.1.jar
>>> CP=$CP:lib/portunif-1.6.1.jar
>>> CP=$CP:lib/rcm-1.6.1.jar
>>> CP=$CP:lib/http-utils-1.6.1.jar
>>> CP=$CP:lib/http-1.6-SNAPSHOT.jar
>>>
>>>
>>>
>>> Now i am only using:
>>>
>>> New:
>>> CP=$CP:lib/grizzly-framework-1.8.0.jar
>>> CP=$CP:lib/grizzly-http-webserver-1.8.0.jar
>>>
>>>
>>> Am i missing something?
>>
>> Can you remove the grizzly-framework jar to see if that makes a
>> difference? That jar is not needed as its contents are included with
>> the latter one. Those bundles (grizzly-XXX-webserver) have been added
>> only since 1.7.x
>>
>>
>> Thanks
>>
>> -- Jeanfrancois
>>
>>
>>>
>>> thanks
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

THANK YOU -- really appreciate it.

am also interested in WHY its being thrown in the first place, so it
will get at two problems.

Jeanfrancois Arcand wrote:

>
>
> Alan Williamson wrote:
>> Scratch that -- its just done it with 1.6! :(
>>
>> Can i disable the logging some how?
>
> Give me 15 minutes and I will send you a patch that avoid logging and
> just print on the screen the exception (before the log).
>
> A+

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

can you run with that patch. The exception will be printed on screen. I
will file an issue agains us because the server should never go down in
the case of a bad logger.

A+

-- Jeanfrancois

Jeanfrancois Arcand wrote:

>
>
> Alan Williamson wrote:
>> Scratch that -- its just done it with 1.6! :(
>>
>> Can i disable the logging some how?
>
> Give me 15 minutes and I will send you a patch that avoid logging and
> just print on the screen the exception (before the log).
>
> A+
>
> -- Jeanfrancois
>
>
>>
>> Jeanfrancois Arcand wrote:
>>> Salut,
>>>
>>> Alan Williamson wrote:
>>>> I am still getting this exception and its very confusing.  But i
>>>> think i may have spotted what changed when i upgraded the production
>>>> machines to 1.8
>>>>
>>>> In the 1.6 i was including the following JAR files in my java startup
>>>>
>>>> Old:
>>>> CP=$CP:lib/framework-1.6.1.jar
>>>> CP=$CP:lib/portunif-1.6.1.jar
>>>> CP=$CP:lib/rcm-1.6.1.jar
>>>> CP=$CP:lib/http-utils-1.6.1.jar
>>>> CP=$CP:lib/http-1.6-SNAPSHOT.jar
>>>>
>>>>
>>>>
>>>> Now i am only using:
>>>>
>>>> New:
>>>> CP=$CP:lib/grizzly-framework-1.8.0.jar
>>>> CP=$CP:lib/grizzly-http-webserver-1.8.0.jar
>>>>
>>>>
>>>> Am i missing something?
>>>
>>> Can you remove the grizzly-framework jar to see if that makes a
>>> difference? That jar is not needed as its contents are included with
>>> the latter one. Those bundles (grizzly-XXX-webserver) have been added
>>> only since 1.7.x
>>>
>>>
>>> Thanks
>>>
>>> -- Jeanfrancois
>>>
>>>
>>>>
>>>> thanks
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>> For additional commands, e-mail: users-help@...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

fantastic ... thank you.

it is now running, and i will let you know the results.

Jeanfrancois Arcand wrote:
> Salut,
>
> can you run with that patch. The exception will be printed on screen. I
> will file an issue agains us because the server should never go down in
> the case of a bad logger.
>
> A+

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Alan Williamson wrote:
> fantastic ... thank you.
>
> it is now running, and i will let you know the results.

You are welcome. I've filled:

https://grizzly.dev.java.net/issues/show_bug.cgi?id=164

and at least shielded the Controller to die after such unexpected exception.

A+

-- Jeanfrancois

>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> can you run with that patch. The exception will be printed on screen.
>> I will file an issue agains us because the server should never go down
>> in the case of a bad logger.
>>
>> A+
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Oleksiy Stashok]

Alan, if one day you'll find out what caused such a problem with  
logging - please let us know :))

Thank you.

WBR,
Alexey.

On Jun 19, 2008, at 17:58 , Jeanfrancois Arcand wrote:

>
>
> Alan Williamson wrote:
>> fantastic ... thank you.
>> it is now running, and i will let you know the results.
>
> You are welcome. I've filled:
>
> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>
> and at least shielded the Controller to die after such unexpected  
> exception.
>
> A+
>
> -- Jeanfrancois
>
>
>> Jeanfrancois Arcand wrote:
>>> Salut,
>>>
>>> can you run with that patch. The exception will be printed on  
>>> screen. I will file an issue agains us because the server should  
>>> never go down in the case of a bad logger.
>>>
>>> A+
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

Alexey, i *think* the issue maybe related to "too many files" open.

I am running some tests at the moment that will confirm this one way or
another.   But its always the way, as soon as you get a new spanking JAR
file, nothing crashes!!!

I will update this bug thread as soon as i know more concrete information.

   https://grizzly.dev.java.net/issues/show_bug.cgi?id=164

thanks again for all your efforts.

Oleksiy Stashok wrote:

> Alan, if one day you'll find out what caused such a problem with logging
> - please let us know :))
>
> Thank you.
>
> WBR,
> Alexey.
>
> On Jun 19, 2008, at 17:58 , Jeanfrancois Arcand wrote:
>
>>
>>
>> Alan Williamson wrote:
>>> fantastic ... thank you.
>>> it is now running, and i will let you know the results.
>>
>> You are welcome. I've filled:
>>
>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

Alan Williamson wrote:

> Alexey, i *think* the issue maybe related to "too many files" open.
>
> I am running some tests at the moment that will confirm this one way or
> another.   But its always the way, as soon as you get a new spanking JAR
> file, nothing crashes!!!
>
> I will update this bug thread as soon as i know more concrete information.
>
>   https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>
> thanks again for all your efforts.

OK I will right now look if connection are properly closed on our side.
Hopefully they are :-)

A+

-- Jeanfrancois

>
> Oleksiy Stashok wrote:
>> Alan, if one day you'll find out what caused such a problem with
>> logging - please let us know :))
>>
>> Thank you.
>>
>> WBR,
>> Alexey.
>>
>> On Jun 19, 2008, at 17:58 , Jeanfrancois Arcand wrote:
>>
>>>
>>>
>>> Alan Williamson wrote:
>>>> fantastic ... thank you.
>>>> it is now running, and i will let you know the results.
>>>
>>> You are welcome. I've filled:
>>>
>>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Oleksiy Stashok]

Hi Alan,


> Alexey, i *think* the issue maybe related to "too many files" open.
>
> I am running some tests at the moment that will confirm this one way  
> or another.   But its always the way, as soon as you get a new  
> spanking JAR file, nothing crashes!!!
>
> I will update this bug thread as soon as i know more concrete  
> information.
This is very possible!!! Because recently I ran some tests on my local  
machine on "maximum allowed client connections" and ran in to the same  
issue :) So, looks like it is really the cause.

Thanks.

WBR,
Alexey.

>
>
>  https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>
> thanks again for all your efforts.
>
> Oleksiy Stashok wrote:
>> Alan, if one day you'll find out what caused such a problem with  
>> logging - please let us know :))
>> Thank you.
>> WBR,
>> Alexey.
>> On Jun 19, 2008, at 17:58 , Jeanfrancois Arcand wrote:
>>>
>>>
>>> Alan Williamson wrote:
>>>> fantastic ... thank you.
>>>> it is now running, and i will let you know the results.
>>>
>>> You are welcome. I've filled:
>>>
>>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

Oleksiy Stashok wrote:

> Hi Alan,
>
>
>> Alexey, i *think* the issue maybe related to "too many files" open.
>>
>> I am running some tests at the moment that will confirm this one way
>> or another.   But its always the way, as soon as you get a new
>> spanking JAR file, nothing crashes!!!
>>
>> I will update this bug thread as soon as i know more concrete
>> information.
> This is very possible!!! Because recently I ran some tests on my local
> machine on "maximum allowed client connections" and ran in to the same
> issue :) So, looks like it is really the cause.

but I don't think this message is the same. The "maximum allowed client
connections" message is from the pipeline queue. A file descriptor leak
is different IMO :-)

A+

-- Jeanfrancois

>
> Thanks.
>
> WBR,
> Alexey.
>
>>
>>
>>  https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>
>> thanks again for all your efforts.
>>
>> Oleksiy Stashok wrote:
>>> Alan, if one day you'll find out what caused such a problem with
>>> logging - please let us know :))
>>> Thank you.
>>> WBR,
>>> Alexey.
>>> On Jun 19, 2008, at 17:58 , Jeanfrancois Arcand wrote:
>>>>
>>>>
>>>> Alan Williamson wrote:
>>>>> fantastic ... thank you.
>>>>> it is now running, and i will let you know the results.
>>>>
>>>> You are welcome. I've filled:
>>>>
>>>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

but under Linux, isn't the "too many files" handles apply to sockets as
well as files? i am sure i read that on the t'internet!

Jeanfrancois Arcand wrote:

> Salut,
>
> Oleksiy Stashok wrote:
>> Hi Alan,
>>
>>
>>> Alexey, i *think* the issue maybe related to "too many files" open.
>>>
>>> I am running some tests at the moment that will confirm this one way
>>> or another.   But its always the way, as soon as you get a new
>>> spanking JAR file, nothing crashes!!!
>>>
>>> I will update this bug thread as soon as i know more concrete
>>> information.
>> This is very possible!!! Because recently I ran some tests on my local
>> machine on "maximum allowed client connections" and ran in to the same
>> issue :) So, looks like it is really the cause.
>
> but I don't think this message is the same. The "maximum allowed client
> connections" message is from the pipeline queue. A file descriptor leak
> is different IMO :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Alan Williamson wrote:
> but under Linux, isn't the "too many files" handles apply to sockets as
> well as files? i am sure i read that on the t'internet!

Yes. Can you do a netstat -an | grep <<port>> when that happens? Which
JDK are you using? Those issues are sometimes created by the JDK...

A+

-- Jeanfrancois

>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> Oleksiy Stashok wrote:
>>> Hi Alan,
>>>
>>>
>>>> Alexey, i *think* the issue maybe related to "too many files" open.
>>>>
>>>> I am running some tests at the moment that will confirm this one way
>>>> or another.   But its always the way, as soon as you get a new
>>>> spanking JAR file, nothing crashes!!!
>>>>
>>>> I will update this bug thread as soon as i know more concrete
>>>> information.
>>> This is very possible!!! Because recently I ran some tests on my
>>> local machine on "maximum allowed client connections" and ran in to
>>> the same issue :) So, looks like it is really the cause.
>>
>> but I don't think this message is the same. The "maximum allowed
>> client connections" message is from the pipeline queue. A file
>> descriptor leak is different IMO :-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

its not under load YET, but so far:

[root@munich]# netstat -an | grep 80 | wc -l
199

[root@munich]# /usr/java/default/bin/java -version
java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)


Jeanfrancois Arcand wrote:
> Alan Williamson wrote:
>> but under Linux, isn't the "too many files" handles apply to sockets
>> as well as files? i am sure i read that on the t'internet!
>
> Yes. Can you do a netstat -an | grep <<port>> when that happens? Which
> JDK are you using? Those issues are sometimes created by the JDK...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Alan Williamson wrote:
> its not under load YET, but so far:
>
> [root@munich]# netstat -an | grep 80 | wc -l
> 199
>

In what state are they? CLOSE_WAIT ? Hopefully not as this is the leak
cause.

A+

-- Jeanfrancois

> [root@munich]# /usr/java/default/bin/java -version
> java version "1.6.0_04"
> Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
> Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
>
>
> Jeanfrancois Arcand wrote:
>> Alan Williamson wrote:
>>> but under Linux, isn't the "too many files" handles apply to sockets
>>> as well as files? i am sure i read that on the t'internet!
>>
>> Yes. Can you do a netstat -an | grep <<port>> when that happens? Which
>> JDK are you using? Those issues are sometimes created by the JDK...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Alan Williamson]

>> [root@munich]# netstat -an | grep 80 | wc -l
>> 199
>>
>
> In what state are they? CLOSE_WAIT ? Hopefully not as this is the leak
> cause.

vast majority in TIME_WAIT

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Alan Williamson wrote:
>>> [root@munich]# netstat -an | grep 80 | wc -l
>>> 199
>>>
>>
>> In what state are they? CLOSE_WAIT ? Hopefully not as this is the leak
>> cause.
>
> vast majority in TIME_WAIT

So far this is good. It means there is no socket leaks. So there is
probably files that aren't closed properly (like you guessed)...

A+

-- jeanfrancois

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...