Opened 12 years ago
Closed 12 years ago
#240 closed defect (invalid)
Bug in HazardCurveServer
Reported by: | anonymous | Owned by: | Peter Powers |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | sha | Version: | |
Keywords: | Cc: |
Description
Steps to reproduce: (PLEASE FILL IN)
Other info: (PLEASE FILL IN)
Application: HazardCurveServer?
Version: 1.1.3
Bulid Type: dist
Metadata:
Problem occured during initialization the ERF's. All parameters are set to default.
Exception:
java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method# at sun.reflect.NativeConstructorAccessorImpl.newInstance#Unknown Source# at sun.reflect.DelegatingConstructorAccessorImpl.newInstance#Unknown Source# at java.lang.reflect.Constructor.newInstance#Unknown Source# at org.opensha.sha.gui.beans.ERF_GuiBean.createERFClassInstance#ERF_GuiBean.java:139# at org.opensha.sha.gui.beans.ERF_GuiBean.init_erf_IndParamListAndEditor#ERF_GuiBean.java:246# at org.opensha.sha.gui.beans.ERF_GuiBean.<init>#ERF_GuiBean.java:118# at org.opensha.sha.gui.HazardCurveServerModeApplication.initERF_GuiBean#HazardCurveServerModeApplication.java:1888# at org.opensha.sha.gui.HazardCurveServerModeApplication.init#HazardCurveServerModeApplication.java:382# at org.opensha.sha.gui.HazardCurveServerModeApplication.main#HazardCurveServerModeApplication.java:789# Caused by: java.rmi.ConnectException: Connection refused to host: opensha.usc.edu; nested exception is: java.net.ConnectException: Connection timed out: connect at sun.rmi.transport.tcp.TCPEndpoint.newSocket#Unknown Source# at sun.rmi.transport.tcp.TCPChannel.createConnection#Unknown Source# at sun.rmi.transport.tcp.TCPChannel.newConnection#Unknown Source# at sun.rmi.server.UnicastRef.newCall#Unknown Source# at sun.rmi.registry.RegistryImpl_Stub.lookup#Unknown Source# at org.opensha.sha.earthquake.rupForecastImpl.remote.RemoteERF_Client.getRemoteERF#RemoteERF_Client.java:66) at
Note: See
TracTickets for help on using
tickets.
Firewall or server down issue, not a bug. Better error reporting should be included with #141