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_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
>>
>