It should work, but in general 3.0.1 is more stable, that's why IMO it
could make sense to try it.
Thanks.
Alexey.
On Aug 31, 2010, at 16:21 , Martin, Ray wrote:
> Okay - I will make the switch to a newer version ASAP.
>
> BUT - to get me back up and running, could I not set the other
> variable???
>
>
> The link that you provided says:
> Additional comments
> "We misinterpret thread-pool configuration elements in domain.xml, we
> use thread-pool->idle-thread-
> timeout-seconds to set transaction timeout and http->timeout-seconds
> to
> set thread's idle-timeout."
>
>
> So, if I knew the syntax, I could set
> thread-pool-idle-thread-timeout-seconds
> Just for enough to get me going - I am in a really bad position at the
> moment.
>
> -----Original Message-----
> From: Oleksiy.Stashok_at_Sun.COM [mailto:Oleksiy.Stashok_at_Sun.COM]
> Sent: Tuesday, August 31, 2010 9:58 AM
> To: users_at_glassfish.dev.java.net
> Subject: Re: Interrupted idle thread
>
> Now I see, most probably you're using GF v3, where we had issue [1].
> Can you pls. switch to GF v3.0.1?
>
> I don't remember exactly if NB 6.8 supports GF v3 server out of the
> box, or you need additional plugin to be installed, but with NB 6.9.1
> you can use GF 3.0.1 (AFAIR it's one you have out of the box), which
> should have that issue resolved.
>
> Thanks.
>
> WBR,
> Alexey.
>
> [1] https://glassfish.dev.java.net/issues/show_bug.cgi?id=11490
>
>
> On Aug 31, 2010, at 14:21 , Martin, Ray wrote:
>
>> I am using netbeans6.8 and whatever glassfish comes with it.
>>
>> At the glassfish admin console, I press the version button, I get v3
>> (no
>> numbers)
>>
>> I am very sorry to say, that I cannot get the descriptor onto the
>> Internet.
>>
>> -----Original Message-----
>> From: Oleksiy.Stashok_at_Sun.COM [mailto:Oleksiy.Stashok_at_Sun.COM]
>> Sent: Tuesday, August 31, 2010 7:35 AM
>> To: users_at_glassfish.dev.java.net
>> Subject: Re: Interrupted idle thread
>>
>> Martin,
>>
>> just to make sure, are you using the Glassfish 3.0.1 release?
>> Can you pls. share the domain.xml descriptor?
>>
>> Thanks.
>>
>> Alexey.
>>
>> On Aug 31, 2010, at 13:28 , Martin, Ray wrote:
>>
>>> Mr. Lubke,
>>>
>>> I did the following:
>>> ...
>>> <http request-timeout-seconds="-1" ...
>>> ...
>>>
>>> I assume that -1 means to disable.
>>>
>>> After restarting glassfish and deploying the EJBModule in an
>>> Enterprise
>>> app (so it will see the third party jars) - still got the
>>> "interrupting
>>> idle thread.."
>>>
>>> But, worse than that is the fact that something causes the SOAP
>>> message
>>> to be repeated - then my process is not protected against that
>>> repeat
>>> SOAP message again kicks off and stomps all over the database
>>> records
>>> that it just wrote before the timeout.
>>>
>>> I am going to try an asynchronous client to see if that will take
>>> care
>>> of the problem.
>>>
>>> Thanx for your help.
>>>
>>>
>>> -----Original Message-----
>>> From: Ryan Lubke [mailto:ryan.lubke_at_oracle.com]
>>> Sent: Monday, August 30, 2010 8:51 PM
>>> To: Martin, Ray
>>> Cc: users_at_glassfish.dev.java.net
>>> Subject: RE: Interrupted idle thread
>>>
>>> Hello Martin,
>>>
>>> I believe you'll be able to resolve this issue by either increasing
>>> the
>>> request-timeout-seconds property or disabling
>>> the feature altogether.
>>>
>>> This can be done by backing up your
>>> GF_HOME/domains/domain1/config/domain.xml and then modify the http
>>> element
>>> associated with the protocol your listener is using.
>>>
>>> For example, if you're using the out-of-the-box configuration, you
>>> can
>>> change the timeout for requests made to port 8080 like
>>> so:
>>>
>>>
>>> <protocol name="http-listener-1">
>>> <http request-timeout-seconds="60" default-virtual-server="server"
>>> max-connections="250" />
>>> </protocol>
>>>
>>> It doesn't appear that this value can currently be set to -1 via
>>> asadmin
>>>
>>> command line, so I'll be looking into resolving
>>> that shortly.
>>>
>>> Could you please try updating the domain.xml using the above xml
>>> snippet
>>>
>>> as a guide and let us know if it resolves your problem?
>>>
>>> Thanks,
>>> -rl
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>