Salut,
Richard Corsale wrote:
> let me clarify that a bit :)
>
> "No Im saying that when I include multiple servletAdapters with contexts that contain 2 levels
> ex: /level1/level2 the second servletAdapter seems to replace the first and the first
> acts as if it was never registered. if there were three adapters the third is the only one that gets loaded and so on. The other servlet adapters are not
> answering the request of the last, their just not present. "
>
> Sorry for the obscurity , its been a long day :)
Thanks! It should be simple to fix. Can you file a new issue? Sorry for
keep asking :-)
Thanks!!!
-- Jeanfrancois
>
>
> --Richard
>
>
>
> ----- Original Message ----
> From: Richard Corsale <igf1_at_yahoo.com>
> To: users_at_grizzly.dev.java.net
> Sent: Tuesday, February 24, 2009 3:05:44 PM
> Subject: Re: The issue I posted yesterday (459), still present but identified
>
> No Im saying that when I include a contexts with 2 levels /level1/level2 the second one seems to replace the first and the first acts as if it was never registered. The first servlet adapter is not answering the request of the second, its just not present.
>
>
> See before I realized this was the issue I mistook some of the anomalies for this. At this time this is the only bug I have positivly identified, and I suspect that everything else will fall into place once this one is fixed.
>
>
> --Richard
>
>
>
> ----- Original Message ----
> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
> To: users_at_grizzly.dev.java.net
> Sent: Tuesday, February 24, 2009 2:50:36 PM
> Subject: Re: The issue I posted yesterday (459), still present but identified
>
> Salut
>
> Richard Corsale wrote:
>> Ok, I'm attaching GrizzlyHarness , the front wrapper for controlling the Grizzly server, this is the netbeans project (I know how much you love NetBeans :) )
>>
>>
>> Ok test case one:
>>
>> in the file localTest take a look at the startServer Method, here I load the servlets to contexts :
>> ssa.addServlet("/OortCloud/debug", new testServlet());
>> ssa.addServlet("/OortCloud/test", new testServlet_1());
>> now run this and head over to these contexts you see that the test context works and the debug will not. Now if you remove the /OortCloud part of the context and set it to just /test and /debug both work. I'm pretty sure I get a cookie for this one :)
>
> Just curious, before we were having a mapping issue and I'm not surprised it worked...but now you are saying that testServlet_1 is never invoked, but instead all requests goes to testServlet?
>
> Thanks
>
> -- jeanfrancois
>
>>
>> Once I identified this, It seems to have resolved the mistakenly associated MaxThread issue as well as the trailing / issue :-) as it turns out there all the same issue :)
>>
>> 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
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> 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
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>