argh , Im working on a test case now, I think I have another one actually, where it loads the last servlet adapter and overwrites the previous ones loaded... frustrated :( Let me get my notes together and Ill post the test here.
--Richard
----- Original Message ----
From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
To: users_at_grizzly.dev.java.net
Sent: Tuesday, February 24, 2009 12:46:59 PM
Subject: Re: The issue I posted yesterday (459), still present but identified
Richard Corsale wrote:
> well this one is pretty simple,
> this.Server.setMaxThreads(harnessConfig.getMaxThreads());
> this.Server.addAsyncFilter(new CometAsyncFilter());
>
> if I do this, the servlet adapter wont register with the server. if I comment out the setMaxThreads all works fine. It (setMaxThreads) does work in 1.9.5 so, I'm fairly sure this is a bug.
Are you seeing exception?
>
>
> I found another one also :) I dont know.. try this one out as well. in 1.9.5 I could add a rootFolder like this "/path/to/anywhere/" this wont work in the new release, it also appears to load everything properly and never throws an error. in the later versions > 1.9.6 you cant end this path with a / (forward slash) I think we need to either A. detect and remove the trailing slash or B. throw some kind of an error when loading the servlet adapters setRootFolder
>
OK can you produce test case for both of the issues? We need to fix this asap if they exist :-)
A+
-- Jeanfrancois
>
> --Richard
>
>
>
> ----- Original Message ----
> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
> To: users_at_grizzly.dev.java.net
> Sent: Tuesday, February 24, 2009 12:04:19 PM
> Subject: Re: The issue I posted yesterday (459), still present but identified
>
> Salut,
>
> Richard Corsale wrote:
>> Hi all,
>>
>> I found that the issue that I posted yesterday (459) remains after the tickets update, I have isolated the problem however. The servlet adapter fails to load when I specify the max threads, if I omit this parameter all is fine. So I don't know if this is a new bug or an update to an existing one. I found this in the last upload of 1.9.6 as well as the latest 1.9.7
>
> I think this is a different issue. Can you share a test case? The issue yesterday was caused a missing resources. What you explain here seems to be different.
>
> Thanks!
>
> -- Jeanfrancois
>
>> Note: The issue has already been flaged as FIXED?
>>
>> --Richard
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
For additional commands, e-mail: users-help_at_grizzly.dev.java.net