Connectiing to a local ADDE server with a recent build of 1.7beta1 issues the error message below. 1.6 works fine.
HP
java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:209) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.net.SocketInputStream.read(SocketInputStream.java:223) at java.io.DataInputStream.readInt(DataInputStream.java:387) at edu.wisc.ssec.mcidas.adde.AddeURLConnection.connect(AddeURLConnection.java:759) at edu.wisc.ssec.mcidas.adde.AddeURLConnection.getInputStream(AddeURLConnection.java:819) at edu.wisc.ssec.mcidasv.chooser.adde.AddeChooser.checkIfServerIsOk(AddeChooser.java:1320) at edu.wisc.ssec.mcidasv.chooser.adde.AddeChooser.canAccessServer(AddeChooser.java:1381) at edu.wisc.ssec.mcidasv.chooser.adde.AddeChooser.connectToServer(AddeChooser.java:1420) at edu.wisc.ssec.mcidasv.chooser.adde.AddeChooser.handleConnect(AddeChooser.java:821) at ucar.unidata.idv.chooser.adde.AddeChooser.handleConnectFromThread(AddeChooser.java:600) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at ucar.unidata.util.Misc$2.run(Misc.java:1215) at ucar.unidata.util.Misc$3.run(Misc.java:1243)
Thanks for reporting this, I'm replicating the problem on my Windows 7 machine. This problem of local servers not working in the nightly should only be an issue on Windows machines. I sent a message to the programmer to see if we can get the local servers working again in the nightly build, but this might not be done until next week. I'll respond to this forum when local servers are working again on Windows.
FYI the inquiry for updating the local servers on Windows is Inquiry 2322.
I quick checked a local AREA dataset on a Windows 7 laptop this morning and I'm able to connect to the local server. If you give this a try and run into any further problems, please let me know.
I am having similar trouble with the standard ADDE servers in the latest McIDAS nightly build. They open fine in the IDV. In the latest McIDAS they act as if they are loading, but they never finish, on some they return the bad data error. I tried the same servers and data in the IDV and they open almost immediately. Thanks for the continued support.
Sorry that you are having trouble with the ADDE servers in McIDAS-V. I picked up today's McIDAS-V 1.7beta1 nightly on Windows and OS X and a couple remote imagery servers I tested (adde.ucar.edu and atm.ucar.edu) look to be working fine on our end. Can you please give me more specifics by answering the following questions?
Can you please let me know what platform you are on, as well as the date of the build you are using? You can get the date information by going to Help>About McIDAS-V from the Main Display window. The 'Build-date' will be listed in the McIDAS-V tab of the About McIDAS-V window (for example, 2016-10-03 09:30).
You are talking about the remote ADDE servers/datasets included with McIDAS-V and not the local ADDE servers, correct? The IDV does not have local ADDE functionality so I'm assuming this is the case.
Assuming #1 above is true, then are you seeing this problem with all remote servers/datasets, or just a few particular ones?
Can you please let me know where along the process of trying to display the data you are seeing the error? For example, do you see the error when hitting the Connect button or when selecting an Image Type?
Can you please post the text of the error message you are seeing along with the stack trace? The stack trace is visible by clicking the Show Details button in the Error window. You can copy/paste this text.
I'm on the "Version: 1.7beta1 Build-date: 2016-10-02 09:30" running on Windows 7 32 bit. The problem has been prevalent with all the satellite data I have tried. I was planning on using the data with Hurricane Matthew as it's the first Cat. 4 storm I have had a decent chance to interrogate. Here is one of the common errors I am getting on all the servers:
There was an error loading the data: Data load failed for edu.wisc.ssec.mcidasv.data.adde.AddeImageParameterDataSource
ucar.unidata.data.BadDataException: Data load failed for edu.wisc.ssec.mcidasv.data.adde.AddeImageParameterDataSource at ucar.unidata.data.DataManager.createDataSource(DataManager.java:1585) at ucar.unidata.idv.IntegratedDataViewer.createDataSource(IntegratedDataViewer.java:1978) at ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataViewer.java:1895) at ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataViewer.java:1829) at ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataViewer.java:1802) at ucar.unidata.idv.chooser.IdvChooser.makeDataSource(IdvChooser.java:943) at edu.wisc.ssec.mcidasv.chooser.adde.AddeImageChooser.doLoadInThread(AddeImageChooser.java:2783) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at ucar.unidata.util.Misc$2.run(Misc.java:1215) at ucar.unidata.util.Misc$3.run(Misc.java:1243)
I hope that this helps with the problem. Thanks for your help Bob
Thanks for the information. I found a forum user a while back (in 2011) had a similar problem that was reported in the creating local ADDE server forum. This user had the 'ADDE via port 80' plugin installed that was causing the problem. Can you check if you have this plugin installed? Here is how you would do that:
From the Main Display window, go to Tools>Plugins>Manage
At the top of the Plugin Manager, under Installed Plugins, see if a plugin called 'ADDE via port 80' is installed. If it is, click the Uninstall Plugin button next to it:
uninstallPlugin.jpg (1.11 KiB) Viewed 4962 times
Restart McIDAS-V and see if things work better
If you don't have this plugin installed, can you please let me know how long you have been seeing this problem?