Found it.
It was coming from jax-ws RI. Theres some debugging code in there...
I wasnt sure if it was glassfish or not because the messages were
prefixed with httpWorker thread id's...
[#|2006-09-28T10:45:28.103-0400|INFO|sun-appserver-pe9.0|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=httpWorkerThread-8080-0;|fiber1
created|#]
/s
Jan Luehe wrote:
>
>
> Sameer Tyagi wrote On 09/28/06 07:59,:
>
>> While running a webapp, I see the following messages in server.log
>> and the server seems to go in a wierd loop.
>> Has anyone seen thie before ? Trying to see if this is coming from
>> Glassfish or the app....
>
>
>
> I'm sorry, but you need to provide a little more detail.
>
> All the "fiberxxx" messages seem to be coming from your webapp.
> (I've never seen those before.)
>
> From the output below, it is not clear to me where the loop occurs,
> but if there is any loop, it is your webapp that is causing it.
>
>
> Jan
>
>
>>
>> /s
>>
>>
>> [#|2006-09-28T10:44:17.576-0400|INFO|sun-appserver-pe9.0|javax.enterprise.resource.webservices.jaxws.servlet.http|_ThreadID=15;_ThreadName=httpWorkerThread-4848-1;|WSSERVLET14:
>> JAX-WS servlet initializing|#]
>>
>> [#|2006-09-28T10:45:28.103-0400|INFO|sun-appserver-pe9.0|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=httpWorkerThread-8080-0;|fiber1
>> created|#]
>>
>> [#|2006-09-28T10:45:28.108-0400|INFO|sun-appserver-pe9.0|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=httpWorkerThread-8080-0;|
>>
>> fiber1 running by httpWorkerThread-8080-0|#]
>>
>> [#|2006-09-28T10:45:28.125-0400|INFO|sun-appserver-pe9.0|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=httpWorkerThread-8080-0;|
>>
>> fiber1 running by httpWorkerThread-8080-0|#]
>>
>> [#|2006-09-28T10:45:28.132-0400|INFO|sun-appserver-pe9.0|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=httpWorkerThread-8080-0;|
>>
>> fiber1 completed
>> |#]
>