You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Alex O'Ree <sp...@gmail.com> on 2013/08/25 13:38:59 UTC
Re:
Start tomcat first, then soapui. Soapui likes to tie up a number of
ports. It may be conflicting with tomcat
On Sat, Aug 24, 2013 at 10:35 PM, Saibabu Vallurupalli
<sa...@gmail.com> wrote:
> Hi,
>
> The jUDDI server errors out after and an hour always and I need to restart
> then it works fine. How can I avoid restarting server every time. Below is
> the error:
>
> <faultstring>The last packet successfully received from the server was
> 256,592,402 milliseconds ago. The last packet sent successfully to the
> server was 256,592,402 milliseconds ago. is longer than the server
> configured value of 'wait_timeout'. You should consider either expiring
> and/or testing connection validity before use in your application,
> increasing the server configured values for client timeouts, or using the
> Connector/J connection property 'autoReconnect=true' to avoid this
> problem.</faultstring>
>
> I used this server several days before and now I am trying to access a
> service and it throws the error above.
>
> Thank you,
> Sai
Re:
Posted by Saibabu Vallurupalli <sa...@gmail.com>.
Hi Kurt/Alex,
Yes, this is DB Configuration issue. I did some research and found MySQL
has a global variable wait_timeout which has a value set by default to time
out after certain idle wait time set.
I am researching on how to disable this.
Thank you,
Sai
On Sun, Aug 25, 2013 at 8:34 AM, Kurt Stam <ku...@gmail.com> wrote:
> Sounds like a db connection misconfiguration to me.
>
> On Aug 25, 2013, at 7:38, "Alex O'Ree" <sp...@gmail.com> wrote:
>
> > Start tomcat first, then soapui. Soapui likes to tie up a number of
> > ports. It may be conflicting with tomcat
> >
> > On Sat, Aug 24, 2013 at 10:35 PM, Saibabu Vallurupalli
> > <sa...@gmail.com> wrote:
> >> Hi,
> >>
> >> The jUDDI server errors out after and an hour always and I need to
> restart
> >> then it works fine. How can I avoid restarting server every time. Below
> is
> >> the error:
> >>
> >> <faultstring>The last packet successfully received from the server was
> >> 256,592,402 milliseconds ago. The last packet sent successfully to the
> >> server was 256,592,402 milliseconds ago. is longer than the server
> >> configured value of 'wait_timeout'. You should consider either expiring
> >> and/or testing connection validity before use in your application,
> >> increasing the server configured values for client timeouts, or using
> the
> >> Connector/J connection property 'autoReconnect=true' to avoid this
> >> problem.</faultstring>
> >>
> >> I used this server several days before and now I am trying to access a
> >> service and it throws the error above.
> >>
> >> Thank you,
> >> Sai
>
Re:
Posted by Kurt Stam <ku...@gmail.com>.
Sounds like a db connection misconfiguration to me.
On Aug 25, 2013, at 7:38, "Alex O'Ree" <sp...@gmail.com> wrote:
> Start tomcat first, then soapui. Soapui likes to tie up a number of
> ports. It may be conflicting with tomcat
>
> On Sat, Aug 24, 2013 at 10:35 PM, Saibabu Vallurupalli
> <sa...@gmail.com> wrote:
>> Hi,
>>
>> The jUDDI server errors out after and an hour always and I need to restart
>> then it works fine. How can I avoid restarting server every time. Below is
>> the error:
>>
>> <faultstring>The last packet successfully received from the server was
>> 256,592,402 milliseconds ago. The last packet sent successfully to the
>> server was 256,592,402 milliseconds ago. is longer than the server
>> configured value of 'wait_timeout'. You should consider either expiring
>> and/or testing connection validity before use in your application,
>> increasing the server configured values for client timeouts, or using the
>> Connector/J connection property 'autoReconnect=true' to avoid this
>> problem.</faultstring>
>>
>> I used this server several days before and now I am trying to access a
>> service and it throws the error above.
>>
>> Thank you,
>> Sai