Java Exception when going to Webaccess Application running on on OES2015

  • 7017214
  • 02-Feb-2016
  • 17-Nov-2016


Novell GroupWise 2014 R2
Novell GroupWise 2014


When trying to log into WebAccess from browser, seeing error: HTTP Status 500 - Servlet execution threw an exception.

Installing the GroupWise Webaccess 2014 R2 or 2014 Application to an OES 2015 Server or SLES 12 Server will likely result in the following error being displayed on the browser when accessing the login page:

 java.lang.J9VMInternals.verifyImpl(Native Method)


GroupWise 2014 and 2014 R2 Webaccess likely will need to be manually configured to run with OES 2015 until GroupWise 2014 R2 SP1 is released.  Please follow these steps to manually configure:

From a terminal window do the following:

1.  Stop Tomcat process "rcnovell-tomcat6 stop"
2.  Create the following directories if they do not exist already and assign them the correct owner
mkdir -p /var/opt/novell/tomcat6/lib/
mkdir -p /var/opt/novell/tomcat6/common/endorsed
chown -R wwwrun:www /var/opt/novell/tomcat6/common
chown -R wwwrun:www /var/opt/novell/tomcat6/lib/
2.  Create symbolic links for the following 5 files
ln -s /opt/novell/groupwise/webaccess/metro/webservices-api.jar /var/opt/novell/tomcat6/common/endorsed/
ln -s /opt/novell/groupwise/webaccess/metro/webservices-extra-api.jar /var/opt/novell/tomcat6/lib/
ln -s /opt/novell/groupwise/webaccess/metro/webservices-extra.jar /var/opt/novell/tomcat6/lib/
ln -s /opt/novell/groupwise/webaccess/metro/webservices-rt.jar /var/opt/novell/tomcat6/lib/
ln -s /opt/novell/groupwise/webaccess/metro/webservices-tools.jar /var/opt/novell/tomcat6/lib/
3. Restart Tomcat
rcnovell-tomcat6 start


Since OES2015 shipped after GroupWise 2014 R2 and 2014, the installation routine for Webaccess did not take into account differences in the Tomcat binaries that shipped with OES2015.
Although, not officially supported until a future date, these changes should result in a working Webaccess server.


Reported to Engineering

Additional Information

This issue has been addressed by GroupWise Development.   It should not occur after applying builds after GroupWise 2014R2 HP1