Preventing timeout when loading data

[Tommy Marullo]

Is there a way to extend the timeout when changing the history to a
much larger value? I currently have a test with about 30 channels
with a few XY graphs and when I use RDV to have a time history of more
than 1 hour it will load the data for a few moments then pop up a
message saying that it failed to retrieve the data and then RDV is
useless. It will not play or go to realtime. I have a feeling that
it is still getting the data but just times out.

I've tried using the Resample Plugin for RBNB so it doesn't retrieve
as many points but it still times out. Are there any suggestions for
preventing it from timing out so easily?

[Paul Hubbard]

Hmm. This is determined by the arguments to Sink.Fetch; see the
JavaDocs for details.

is this the message you're seeing?

"Stopping real time. Failed to load data from the server. Please try
again later."

that's from monitorData, in RBNBController.java.

From grepping the source, it looks like it tries twice to get the
data (see monitorData(boolean retry))

and dumps to error messages. So can you run it from the command line
and let us know what errors it's reporting?

Cheers,
paul

[Tommy Marullo]

It says "Failed to load data from the server. Please try again
later". It happens when I have a data turbine running and I try to
change the time history to a larger value like 1.0h. It is already in
a real-time running state. The good thing is that it goes back to
running in a real-time state and collects data. Older versions just
pretty much went into a dead state. See the image:
http://groups.google.com/group/rdv-users/web/rdvtimeout.png

Tommy

[Paul Hubbard]

I'm sorry, I wasn't clear. Do you have RDV downloaded as source code?
I need to see the messages that the process is printing to its console.

Are you using a jarfile or a JNLP to run it?

If a jarfile, please try

java -jar rdv.jar

from a command line and send the output from that. If jnlp, then try

javaws {filename}

Cheers,
Paul

[Thomas Marullo]

Here is the console log from when I change the time to 1 hour:

INFO: Updating channel listing at 2008-09-29 09:21:38.421 EDT
Sep 29, 2008 9:21:41 AM org.rdv.rbnb.RBNBController processTimeScaleUpdate
INFO: Setting time scale to 3600.0.
Sep 29, 2008 9:21:41 AM org.rdv.rbnb.RBNBController changeStateSafe
INFO: Transitioned from state stopped to loading.
Sep 29, 2008 9:21:48 AM org.rdv.rbnb.MetadataManager updateMetadata
INFO: Updating channel listing at 2008-09-29 09:21:48.718 EDT
Sep 29, 2008 9:22:12 AM org.rdv.rbnb.RBNBController updateDataMonitoring
SEVERE: Failed to fetch data.

--
Thomas M. Marullo
Research Scientist II & RTMD IT Manager
ATLSS Engineering Research Center
Lehigh University
117 ATLSS Drive
Bethlehem, PA 18015
(610) 758-6683

Normal people believe that if it ain't broke, don't fix it. Engineers believe that if it ain't broke, it doesn't have enough features yet.

[Paul Hubbard]

Nothing else?

You might try changing line 817 of RBNBController.java from

timeout = 500;

to something larger and see what effect that has. I'm a bit at sea in
the RDV code, so I'm hoping Jason can chime in here.

Cheers,
-Paul

> /Normal people believe that if it ain't broke, don't fix it. Engineers
> believe that if it ain't broke, it doesn't have enough features yet./
>
>
> >

[Thomas Marullo]

Yeah, that is all that prints to console.  I will try changing the timeout in my build.

Thanks,
Tommy