Anonymous_User Absent Member.
Absent Member.
3662 views

Java error when starting IManager after upgrading to SP5

After upgrading to NW65SP5, I can no longer get into IManager. I realized
that tomcat was not loading on the server. When I tried to load it the I
received this error:

Module PERL.NLM load status OK
Using CATALINA_BASE: sys:/tomcat/4
Using CATALINA_HOME: sys:/tomcat/4
Using CATALINA_TMPDIR: sys:/tomcat/4/temp
Using JAVA_HOME: SYS:\java
Doing a stop
Error occurred during initialization of VM
Could not reserve enough space for object heap
java: Class org.apache.catalina.startup.Bootstrap exited with status -9

tccheck: LDAP is not up yet; waiting
LDAP connectivity not found on ldap://localhost:636
Please load NLDAP and then manually execute command: sys:/tomcat/4/bin/
startup

If your server host certificates have change recently, executing
sys:/system/tckeygen.ncf may be needed to restore secure LDAP
connectivity
Java: Class com.novell.application.tomcat.util.tccheck.LDAPVerifier
exited successfully

I resolved this issue by rebooting the server and using the -u300000000
switch, as suggested by TID#10093274. However, when I tried to start tomcat
again, I received an error "Could not initialize Netware Java runtime."
There was no information on the knowledgebase about this error. We tried
reinstalling SP5, but it didn't clear up the error. I tried reinstalling
Java, but of course it installed an older version of Java. This seemed to
mess things up even more. Now when tomcat tries to start this message comes up:

Java: page fault processor exception occured while executing class
com.novell.application.tomcat.util.tccheck.LDAPVerifier

State of Registers at Processor Exception:
EIP=8816B200, EFLAGS=210202, EAX=2, ECX=9EFCE8E4, EDX=68,
EBX=9EFCE8F9, ESP=9EFCE6D8, EBP=9EFCEB1C, ESI=883B9B60, EDI=200,

The exception occurred while executing code in: JAVA.NLM (8814e000)
The exception occurred while running thread: Java_717 Main (93C08080)

Anybody have any ideas what to do next?
Labels (2)
0 Likes
11 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

jlines,

> After upgrading to NW65SP5, I can no longer get into IManager. I realized
> that tomcat was not loading on the server. When I tried to load it the I
> received this error:
>
> Module PERL.NLM load status OK
> Using CATALINA_BASE: sys:/tomcat/4
> Using CATALINA_HOME: sys:/tomcat/4
> Using CATALINA_TMPDIR: sys:/tomcat/4/temp
> Using JAVA_HOME: SYS:\java
> Doing a stop
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> java: Class org.apache.catalina.startup.Bootstrap exited with status -9
>
> tccheck: LDAP is not up yet; waiting
> LDAP connectivity not found on ldap://localhost:636
> Please load NLDAP and then manually execute command: sys:/tomcat/4/bin/
> startup
>
> If your server host certificates have change recently, executing
> sys:/system/tckeygen.ncf may be needed to restore secure LDAP
> connectivity
> Java: Class com.novell.application.tomcat.util.tccheck.LDAPVerifier
> exited successfully
>
> I resolved this issue by rebooting the server and using the -u300000000
> switch, as suggested by TID#10093274. However, when I tried to start tomcat
> again, I received an error "Could not initialize Netware Java runtime."


Totally remove the -u switch for now, or significantly increase it.
Tomcat will have issues with -u less than around 550000000


--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

jlines@statenationalbank.com wrote:

> After upgrading to NW65SP5, I can no longer get into IManager. I
> realized that tomcat was not loading on the server. When I tried to
> load it the I received this error:
>
> Module PERL.NLM load status OK
> Using CATALINA_BASE: sys:/tomcat/4
> Using CATALINA_HOME: sys:/tomcat/4
> Using CATALINA_TMPDIR: sys:/tomcat/4/temp
> Using JAVA_HOME: SYS:\java
> Doing a stop
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> java: Class org.apache.catalina.startup.Bootstrap exited with
> status -9
> tccheck: LDAP is not up yet; waiting
> LDAP connectivity not found on ldap://localhost:636
> Please load NLDAP and then manually execute command:
> sys:/tomcat/4/bin/ startup
>
> If your server host certificates have change recently, executing
> sys:/system/tckeygen.ncf may be needed to restore secure LDAP
> connectivity
> Java: Class
> com.novell.application.tomcat.util.tccheck.LDAPVerifier exited
> successfully
>
> I resolved this issue by rebooting the server and using the
> -u300000000 switch, as suggested by TID#10093274. However, when I



Err...i don't really believe that to be honest. Tomcat is trying to
connect to port 636 of your LDAP server and as it says in the logger
screen it is failing because there is no activity.

Check with TCPCON if there is actually something listening on port 636.
Check in ConsoleOne if the LDAP Server object has a valid certificate
associated. Check with pkidiag if your certs are still valid.

Once you are sure that all points above are correct run tckeygen.ncf


--
Cheers,
Edward
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

> jlines@statenationalbank.com wrote:
>
> > After upgrading to NW65SP5, I can no longer get into IManager. I
> > realized that tomcat was not loading on the server. When I tried to
> > load it the I received this error:
> >
> > Module PERL.NLM load status OK
> > Using CATALINA_BASE: sys:/tomcat/4
> > Using CATALINA_HOME: sys:/tomcat/4
> > Using CATALINA_TMPDIR: sys:/tomcat/4/temp
> > Using JAVA_HOME: SYS:\java
> > Doing a stop
> > Error occurred during initialization of VM
> > Could not reserve enough space for object heap
> > java: Class org.apache.catalina.startup.Bootstrap exited with
> > status -9
> > tccheck: LDAP is not up yet; waiting
> > LDAP connectivity not found on ldap://localhost:636
> > Please load NLDAP and then manually execute command:
> > sys:/tomcat/4/bin/ startup
> >
> > If your server host certificates have change recently, executing
> > sys:/system/tckeygen.ncf may be needed to restore secure LDAP
> > connectivity
> > Java: Class
> > com.novell.application.tomcat.util.tccheck.LDAPVerifier exited
> > successfully
> >
> > I resolved this issue by rebooting the server and using the
> > -u300000000 switch, as suggested by TID#10093274. However, when I

>
>
> Err...i don't really believe that to be honest. Tomcat is trying to
> connect to port 636 of your LDAP server and as it says in the logger
> screen it is failing because there is no activity.
>
> Check with TCPCON if there is actually something listening on port 636.
> Check in ConsoleOne if the LDAP Server object has a valid certificate
> associated. Check with pkidiag if your certs are still valid.
>
> Once you are sure that all points above are correct run tckeygen.ncf
>
>
> --
> Cheers,
> Edward



Thanks for the info. I have looked at all of this: TCPCON verifies that
port 636 has something listening on it. ConsoleOne verifies that the LDAP
Server Object has a valid certificate associated with it. And pkidiag runs
with no errors. However, when I try to run tckeygen.ncf the following error
shows on the logger screen:

java: Page fault processor exception occurred while executing class
com.novell.application.tomcat.util.EdirectoryIntegrator

State of Registers at Processor Exception:
EIP=85D4C200, EFLAGS=210202, EAX=2, ECX=9487A184, EDX=68,
EBX=9487A199, ESP=94879F78, EBP=9784A3BC, ESI=856E9C60, EDI=200

The exception occurred while executing code in: JAVA.NLM (85d2f000)
The exception occurred while running thread: Java_1624 Main (93B4E0A0)

Java: An exception occurred while cleaning up
com.novell.application.tomcat.util.EdirectoryIntegrator. The JVM running
this class is permanently suspended and its resources are unrecoverable.

This is a similar error to what I was getting in my first post after
reinstalling Java and then trying to start Tomcat. Any ideas on how to get
past this. SP5 has already been reinstalled to no avail. Thanks in advance.

James
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

jlines@statenationalbank.com wrote:

> This is a similar error to what I was getting in my first post after
> reinstalling Java and then trying to start Tomcat. Any ideas on how
> to get past this. SP5 has already been reinstalled to no avail.
> Thanks in advance.


How did you reinstall java ?
Not sure if you can use any other version then the one that comes with
the service pack. Maybe somebody else can confirm that ?

--
Cheers,
Edward
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

jlines@statenationalbank.com wrote:

>tccheck: LDAP is not up yet; waiting
>LDAP connectivity not found on ldap://localhost:636
>Please load NLDAP and then manually execute command: sys:/tomcat/4/bin/
>startup


check sys:\etc\hosts and be sure that there is a definition for localhost
- sometimes it "disappears" and tomcat stops working because in it's XML
files, it connects to LDAP on localhost

--
Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

> jlines@statenationalbank.com wrote:
>
> >tccheck: LDAP is not up yet; waiting
> >LDAP connectivity not found on ldap://localhost:636
> >Please load NLDAP and then manually execute command: sys:/tomcat/4/bin/
> >startup

>
> check sys:\etc\hosts and be sure that there is a definition for localhost
> - sometimes it "disappears" and tomcat stops working because in it's XML
> files, it connects to LDAP on localhost
>
> --
> Joe Moore
> Novell Support Forums SysOp
> http://just.fdisk-it.com
> http://www.caledonia.net/jmdns.html
> http://www.caledonia.net/nesadmin.html
> http://www.caledonia.net/jmttb.html


There is a definition of "127.0.0.1 loopback lb localhost # normal loopback
address". Is this the correct one, or should there be a different one?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

127.0.0.1 is the standard loopback address.

--


Peter
eDirectory Rules!
(Site P is here!! http://www.DreamLAN.com/site_p.htm)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

jlines@statenationalbank.com wrote:

>Is this the correct one, or should there be a different one?


that is the correct one

--
Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

> jlines@statenationalbank.com wrote:
>
> >Is this the correct one, or should there be a different one?

>
> that is the correct one
>
> --
> Joe Moore
> Novell Support Forums SysOp
> http://just.fdisk-it.com
> http://www.caledonia.net/jmdns.html
> http://www.caledonia.net/nesadmin.html
> http://www.caledonia.net/jmttb.html


OK. I have managed to get the version of Java that comes with SP5 installed
back on to the server, so the Java exception errors are gone. I am now
receiving the following error when trying to start Tomcat--"Error occurred
during initialization of VM. Could not reserve enough space for code cache.
java: Class com.novell.application.tomcat.util.tccheck.LDAPVerifier exited
with status -9". Any further ideas? Thanks in advance.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

jlines,

> OK. I have managed to get the version of Java that comes with SP5 installed
> back on to the server, so the Java exception errors are gone. I am now
> receiving the following error when trying to start Tomcat--"Error occurred
> during initialization of VM. Could not reserve enough space for code cache.


Do you have a -u switchon the server.exe line in autoexec.bat? If so,
remove it and reboot the server.


--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Java error when starting IManager after upgrading to SP5

> jlines,
>
> > OK. I have managed to get the version of Java that comes with SP5 installed
> > back on to the server, so the Java exception errors are gone. I am now
> > receiving the following error when trying to start Tomcat--"Error occurred
> > during initialization of VM. Could not reserve enough space for code cache.

>
> Do you have a -u switchon the server.exe line in autoexec.bat? If so,
> remove it and reboot the server.
>
>
> --
> Hamish Speirs
> Novell Support Forums Volunteer Sysop.
>
> http://haitch.net
>
> (Please, no email unless requested. Unsolicited support emails will
> probably be ignored)



So far I've received this error without a -u switch (see first post) and
with a higher -u switch of 550000000 at your suggestion (see your first
post). It doesn't seem that anything is keeping the error from coming up. I
can't reinstall Java because it installs a lower version than comes with
SP5 and that messes up more things. Reinstalling SP5 hasn't helped. Are the
messages "Error occurred during initialization of VM. Could not reserve
enough space for object heap." related to the messages "Java: Class
org.apache.catalina.startup.Bootstrap exited with status -9 and Java: Class
com.novell.application.tomcat.util.tccheck.LDAPVerifier exited
successfully."? Or are they dealing with two completely different problems?
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.