Sounds like a db connection misconfiguration to me. On Aug 25, 2013, at 7:38, "Alex O'Ree" <[email protected]> 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 > <[email protected]> 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
