JVM abort in IWS 4.0sp4

[Dean Nguyen]

Harmony,

Have you been able to find a solution to this problem. I'm experiencing the
same problem and have not found a work around for it.

Thanks,
Dean

Harmony Wong wrote:

> Hi,
>
> After the application port started, the following errors occurs.
>
> [18/Feb/2000:20:43:31] info (28123): successful server startup
> [18/Feb/2000:20:43:31] info (28123): Netscape-Enterprise/4.0 SP4
> BB1-02/07/100 2
> 0:53
> [18/Feb/2000:20:43:44] info (28123): Aborting JVM
> [18/Feb/2000:20:43:44] info (28123): Exiting JVM due to: jvm_abort () and
> jvm.ex
> itOnAbort > 0
> [18/Feb/2000:20:43:57] info (28125): Aborting JVM
> [18/Feb/2000:20:43:57] info (28125): Exiting JVM due to: jvm_abort () and
> jvm.ex
> itOnAbort > 0
>
> However, when I remove the complied file nmain.web and start the
> webserver. Although the following file not file errors occurs, the other
> application in the same port works fine.
>
> [root@ERB.4]/usr/local/nes4/https-proxy>./start
> Netscape-Enterprise/4.0 SP4 BB1-02/07/100 20:53
> startup: listening to http://proxy.erb.org, port 100 as nobody
> [root@ERB.4]/usr/local/nes4/https-proxy>JavaScript initialize The
> application fi
> le /opt/erb/website/nmain.web could not be opened.
> JavaScript initialize Cannot load application /opt/erb/website/nmain.web.
>
> Finally, a work around is found:
> 1. rename the complied final.web file to tmp.web
> 2. start the application port
> 3. rename back the tmp.web to final.web
> 4. start the application in the appmgr
>
> Does anybody has the same problem?
>
> Regards,
> Harmony
>
> P.S. the work around script is attached.
>
> #### cut here ####
> /usr/local/nes4/https-uat/stop
> sleep 1
> echo "Rename ./nmain.web ./tmp.web"
> mv ./nmain.web ./tmp.web
> /usr/local/nes4/https-uat/start
> sleep 5
> echo "Rename tmp.web to nmain.web"
> mv ./tmp.web ./nmain.web
> echo "Restarting application main..."
> lynx -auth=admin:AdminPassword -source
> "http://localhost/appmgr/control.html?na
> me=main&cmd=restart"