Justin Lee wrote:
> I have breakpoints set in ContainerMapper.map(), both Mapper.map()
> methods, and ProcessorTask.parseRequest()
Looks like your code doesn't match with the svn revision you are using
(at least for grizzly).
and it never stops... Where
> should I set a break point to watch the incoming requests? When
> watching the set up, I noticed that it uses the default algorithm of
> NoParsingAlgorithm. Could that be a problem?
No this is the strategy configured for v3. The ContainerMapper.map()
should break for sure as everything goes inside it. If not, then it
means GrizzyProxy is not invoked properly as this is the one that
initiate the Grizzly Http module creation.
A+
-- Jeanfrancois
>
>
>
> Justin Lee wrote:
>> I'm not *100%* sure but it all seems to work under the tests in
>> grizzly. Of course, those are known to be pretty shallow tests. I'll
>> dig into ContainerMapper, though. Thanks.
>>
>> Jeanfrancois Arcand wrote:
>>>
>>>
>>> Justin Lee wrote:
>>>> I sent this to another list earlier but haven't heard back yet so I
>>>> thought I'd cast my net wider.
>>>>
>>>> Well, the great news is that I finally have glassfish booting up on
>>>> top of the grizzly config changes. All the osgi and xml parsing
>>>> issues seem to be resolved. So that's awesome. What's *not* so
>>>> awesome, however, is that it appears that even though I see all
>>>> three network listener configurations being processed and log output
>>>> about listening to the different ports, if I hit 4848 or 8080 I
>>>> always just get the one web app. Either the "it works!" page or a
>>>> horribly broken login.jsf for the admin app. So it would appear
>>>> that some wires are crossed somewhere and I'm not exactly sure where
>>>> to look. I'm stepping through GrizzlyProxy and GrizzlyService this
>>>> morning hoping to see something but that's a lot of code in there.
>>>> Anyone have any suggestions to explore?
>>>
>>> Take a look at the ContainerMapper under the same directory. Make
>>> sure the mapped container is the one supposed to be retrieved, e.g.
>>> the AdminAdapter for admin call, the CoyoteAdapter for Servlet/Jsp,
>>> The GrizzlyStaticAdapter for statics resources. Also are you sure
>>> Grizzly is properly configured (stupid question, just to make sure).
>>>
>>> A+
>>>
>>> - jeanfrancois
>>>
>>>
>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>