Hi everyone,
We have an on-prem aka private cloud instance of apigee edge 4.15.04.00 (NOT the websockets version) and we just installed the .03 patch. After doing so, the Management Server UI will not start. In the /apigee-root/var/log/ui/start.out file, i see the following error every time the UI attempts to be started:
nohup: ignoring input Starting Apigee UI: Success Play server process ID is 18183 Oops, cannot start the server. @6nij2ble6: Cannot init the Global object at play.api.WithDefaultGlobal$$anonfun$play$api$WithDefaultGlobal$$globalInstance$1.apply(Application.scala:59) at play.api.WithDefaultGlobal$$anonfun$play$api$WithDefaultGlobal$$globalInstance$1.apply(Application.scala:53) at play.utils.Threads$.withContextClassLoader(Threads.scala:21) at play.api.WithDefaultGlobal$class.play$api$WithDefaultGlobal$$globalInstance(Application.scala:52) at play.api.DefaultApplication.play$api$WithDefaultGlobal$$globalInstance$lzycompute(Application.scala:402) at play.api.DefaultApplication.play$api$WithDefaultGlobal$$globalInstance(Application.scala:402) at play.api.WithDefaultGlobal$class.global(Application.scala:68) at play.api.DefaultApplication.global(Application.scala:402) at play.api.WithDefaultConfiguration$class.play$api$WithDefaultConfiguration$$fullConfiguration(Application.scala:82) at play.api.DefaultApplication.play$api$WithDefaultConfiguration$$fullConfiguration$lzycompute(Application.scala:402) at play.api.DefaultApplication.play$api$WithDefaultConfiguration$$fullConfiguration(Application.scala:402) at play.api.WithDefaultConfiguration$class.configuration(Application.scala:84) at play.api.DefaultApplication.configuration(Application.scala:402) at play.api.Application$class.$init$(Application.scala:274) at play.api.DefaultApplication.<init>(Application.scala:406) at play.core.StaticApplication.<init>(ApplicationProvider.scala:53) at play.core.server.NettyServer$.createServer(NettyServer.scala:244) at play.core.server.NettyServer$$anonfun$main$3.apply(NettyServer.scala:280) at play.core.server.NettyServer$$anonfun$main$3.apply(NettyServer.scala:275) at scala.Option.map(Option.scala:145) at play.core.server.NettyServer$.main(NettyServer.scala:275) at play.core.server.NettyServer.main(NettyServer.scala) Caused by: java.lang.UnsupportedClassVersionError: Global : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at play.api.WithDefaultGlobal$class.play$api$WithDefaultGlobal$$javaGlobal(Application.scala:31) at play.api.DefaultApplication.play$api$WithDefaultGlobal$$javaGlobal$lzycompute(Application.scala:402) at play.api.DefaultApplication.play$api$WithDefaultGlobal$$javaGlobal(Application.scala:402) at play.api.WithDefaultGlobal$$anonfun$play$api$WithDefaultGlobal$$globalInstance$1.apply(Application.scala:54) ... 21 more Failed
Any ideas why this would happen? Any insight would be very much appreciated!
Best, Chris
@Chris Covney I see this in the logs you posted
Caused by: java.lang.UnsupportedClassVersionError: Global : Unsupported major.minor version 51.0
Looks like its complaining about the java version here. Can you confirm the java version you are running on the UI server. Also could you please check if the management server is up ?
@Chris Covney We have a known issue with 1504.03 patch release whereby UI doesn't work with java version 1.6. This is because the UI source was build using Java 1.7 and the execution environment is below that version. We already have a fix for this, but unfortunately the patch is not yet released since its still going through the regular testing cycle as we speak.
The workaround at the moment is to upgrade the instance running the UI server to Java 1.7 and that should let you start the UI. The UI should work perfectly fine with Java 1.7 both SunJDK as well as OpenJDK. Let me know if you would be comfortable trying to upgrade to Java 1.7 while we work on making the patch available for our on-premise customers.
User | Count |
---|---|
5 | |
2 | |
2 | |
1 | |
1 |