Weather Module issue (WRS)

[silentmonolith]

Recently my WRS module stopped functioning: it gives me the following message: "Failed to load the WRS java classess". I have removed Java and reinstalled version 1.5.0_06 but I'm getting the same error message. Any help would be appreciated!

[salsbst]

Did you reinstall the WRS java classes?

[silentmonolith]

Originally Posted by salsbst

Did you reinstall the WRS java classes?

Do you mean those few files that have to be copied manually into /../program files/java/.../ext/lib? Initially I did and still the same error, then I downoaded the entire java package.

[salsbst]

It's entirely possible that it's not compatible with Java 1.5. I haven't upgraded to 1.5 yet, myself, and I'm ashamed to admit I also haven't installed WRS since upgrading from Sage v2... maybe someone else out there can confirm or deny compatibility?

[silentmonolith]

Originally Posted by salsbst

It's entirely possible that it's not compatible with Java 1.5. I haven't upgraded to 1.5 yet, myself, and I'm ashamed to admit I also haven't installed WRS since upgrading from Sage v2... maybe someone else out there can confirm or deny compatibility?

I did not recopy the WRS java files after installing the new java version. So, now, I recopied them and I got my module back , working 100%. Thanks!

[srothwell]

Originally Posted by silentmonolith

I did not recopy the WRS java files after installing the new java version. So, now, I recopied them and I got my module back , working 100%. Thanks!

Salsbst,

I had the exact same thing happen to me the last few days. I was out of town and my wife was upset that Sage was stuttering and extremely slow. I had her shut down Sage and bring it back up (no reboot) and everything was fine.

I looked at the log files today and the following was everywhere in 28MB of log files:

Wed 6/14 18:53:15.507 com.stusals.wrs.Location: java.io.IOException: trying with http://xoap.weather.com/weather/local/32751?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
java.io.IOException: trying with http://xoap.weather.com/weather/local/32751?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
Wed 6/14 18:53:15.507 	at com.stusals.wrs.data.WeatherDotCom.getXmlDoc(WeatherDotCom.java:281)
Wed 6/14 18:53:15.508 	at com.stusals.wrs.data.WeatherDotCom.<init>(WeatherDotCom.java:72)
Wed 6/14 18:53:15.508 	at sun.reflect.GeneratedConstructorAccessor523.newInstance(Unknown Source)
Wed 6/14 18:53:15.508 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Wed 6/14 18:53:15.508 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
Wed 6/14 18:53:15.508 	at com.stusals.wrs.Location.retrieve(Location.java:57)
Wed 6/14 18:53:15.508 	at com.stusals.bgupdate.BGUpdateable.update(BGUpdateable.java:73)
Wed 6/14 18:53:15.508 	at com.stusals.bgupdate.Updater.update(Updater.java:12)
Wed 6/14 18:53:15.508 	at com.stusals.bgupdate.UpdateThread.run(UpdateThread.java:23)
Wed 6/14 18:53:15.508 com.stusals.wrs.Location: updated data for Orlando
Wed 6/14 18:53:25.513 com.stusals.wrs.Location: Problem retrieving data
Wed 6/14 18:53:25.513 com.stusals.wrs.Location: Failed to create class com.stusals.wrs.data.WeatherDotCom: InvocationTargetException
Wed 6/14 18:53:25.513 com.stusals.wrs.Location: java.io.IOException: trying with http://xoap.weather.com/weather/local/USVA0797?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
java.io.IOException: trying with http://xoap.weather.com/weather/local/USVA0797?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
Wed 6/14 18:53:25.513 	at com.stusals.wrs.data.WeatherDotCom.getXmlDoc(WeatherDotCom.java:281)
Wed 6/14 18:53:25.513 	at com.stusals.wrs.data.WeatherDotCom.<init>(WeatherDotCom.java:72)
Wed 6/14 18:53:25.513 	at sun.reflect.GeneratedConstructorAccessor523.newInstance(Unknown Source)
Wed 6/14 18:53:25.513 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Wed 6/14 18:53:25.513 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
Wed 6/14 18:53:25.513 	at com.stusals.wrs.Location.retrieve(Location.java:57)
Wed 6/14 18:53:25.513 	at com.stusals.bgupdate.BGUpdateable.update(BGUpdateable.java:73)
Wed 6/14 18:53:25.514 	at com.stusals.bgupdate.Updater.update(Updater.java:12)
Wed 6/14 18:53:25.514 	at com.stusals.bgupdate.UpdateThread.run(UpdateThread.java:23)
Wed 6/14 18:53:25.514 com.stusals.wrs.Location: updated data for Virginia Beach
Wed 6/14 18:53:27.748 Ministry is waiting for 180 sec
Wed 6/14 18:53:35.416 Carny waiting for awhile...
Wed 6/14 18:53:35.522 com.stusals.wrs.Location: Problem retrieving data
Wed 6/14 18:53:35.523 com.stusals.wrs.Location: Failed to create class com.stusals.wrs.data.WeatherDotCom: InvocationTargetException
Wed 6/14 18:53:35.523 com.stusals.wrs.Location: java.io.IOException: trying with http://xoap.weather.com/weather/local/USDC0001?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
java.io.IOException: trying with http://xoap.weather.com/weather/local/USDC0001?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
Wed 6/14 18:53:35.523 	at com.stusals.wrs.data.WeatherDotCom.getXmlDoc(WeatherDotCom.java:281)
Wed 6/14 18:53:35.523 	at com.stusals.wrs.data.WeatherDotCom.<init>(WeatherDotCom.java:72)
Wed 6/14 18:53:35.523 	at sun.reflect.GeneratedConstructorAccessor523.newInstance(Unknown Source)
Wed 6/14 18:53:35.523 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Wed 6/14 18:53:35.523 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
Wed 6/14 18:53:35.523 	at com.stusals.wrs.Location.retrieve(Location.java:57)
Wed 6/14 18:53:35.523 	at com.stusals.bgupdate.BGUpdateable.update(BGUpdateable.java:73)
Wed 6/14 18:53:35.523 	at com.stusals.bgupdate.Updater.update(Updater.java:12)
Wed 6/14 18:53:35.523 	at com.stusals.bgupdate.UpdateThread.run(UpdateThread.java:23)
Wed 6/14 18:53:35.523 com.stusals.wrs.Location: updated data for DC
Wed 6/14 18:53:45.538 com.stusals.wrs.Location: Problem retrieving data
Wed 6/14 18:53:45.538 com.stusals.wrs.Location: Failed to create class com.stusals.wrs.data.WeatherDotCom: InvocationTargetException
Wed 6/14 18:53:45.538 com.stusals.wrs.Location: java.io.IOException: trying with http://xoap.weather.com/weather/local/23236?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
java.io.IOException: trying with http://xoap.weather.com/weather/local/23236?par=&key=&cc=*&dayf=10&prod=xoap&link=xoap&unit=s -- org.apache.commons.httpclient.HttpConnection$ConnectionTimeoutException
Wed 6/14 18:53:45.538 	at com.stusals.wrs.data.WeatherDotCom.getXmlDoc(WeatherDotCom.java:281)
Wed 6/14 18:53:45.538 	at com.stusals.wrs.data.WeatherDotCom.<init>(WeatherDotCom.java:72)
Wed 6/14 18:53:45.538 	at sun.reflect.GeneratedConstructorAccessor523.newInstance(Unknown Source)
Wed 6/14 18:53:45.539 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Wed 6/14 18:53:45.539 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
Wed 6/14 18:53:45.539 	at com.stusals.wrs.Location.retrieve(Location.java:57)
Wed 6/14 18:53:45.539 	at com.stusals.bgupdate.BGUpdateable.update(BGUpdateable.java:73)
Wed 6/14 18:53:45.539 	at com.stusals.bgupdate.Updater.update(Updater.java:12)
Wed 6/14 18:53:45.539 	at com.stusals.bgupdate.UpdateThread.run(UpdateThread.java:23)

This happened over and over and over..... After restarting Sage, it doesn't have the problem any more. Also I have been on Java 1.5 since it came out, and have been using WRS well, since it came out and this is the first real problem I've had.

Any ideas?

[salsbst]

Not sure what caused it, but obviously the download of the weather data from weather.com was not working.

Perhaps weather.com was down?

You say restarting the Sage process fixed it? I wonder if a thread managed to get loose and tie up your network stack. WRS makes significant use of multithreading and background processing in order to try to stay out of the way of Sage's main business while still keeping the weather data up to date. I haven't heard of recent problems with this.

Perhaps a future version of WRS should track failures and quit at some point so that it doesn't go bonkers in these cases?