Managed VM Java - Start Error

[Rahul Tongia]

Hi,

I am using appengine managed vm for Java. I use priority order for setting the jars of my choice in appengine-web.xml

    <class-loader-config>

        <priority-specifier filename="activation-1.1.1.jar"/>

    </class-loader-config>   

Since this morning, I am getting the following error. Also suspisiously, the appengine version shown in console is 1.9.33 for which there was no Java release.:

Any one else facing this kind of issue. I have changed no code or anything else, but now Managed VM refuses to start.

Regards,

Rahul

2016-03-02 20:19:19.736:INFO:oejs.Server:main: jetty-9.2.10.v20150310

2016-03-02 20:19:19.766:INFO:oejs.AbstractNCSARequestLog:main: Opened /var/log/app_engine/request.2016_03_02.log

2016-03-02 20:19:19.770:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/vmagent/appengine-java-

vmruntime/contexts/] at interval 1

Mar 02, 2016 8:19:20 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml

SEVERE: Received exception processing /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF/appengine-web.xml

java.lang.NumberFormatException: empty String

        at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1020)

        at java.lang.Double.parseDouble(Double.java:540)

        at com.google.apphosting.utils.config.AppEngineWebXml$PrioritySpecifierEntry.setPriority(AppEngineWebXml.ja

va:2110)

        at com.google.apphosting.utils.config.AppEngineWebXmlProcessor.processClassPathPrioritySpecifier(AppEngineW

ebXmlProcessor.java:601)

        at com.google.apphosting.utils.config.AppEngineWebXmlProcessor.processClassLoaderConfig(AppEngineWebXmlProc

essor.java:594)

        at com.google.apphosting.utils.config.AppEngineWebXmlProcessor.processSecondLevelNode(AppEngineWebXmlProces

sor.java:209)

        at com.google.apphosting.utils.config.AppEngineWebXmlProcessor.processXml(AppEngineWebXmlProcessor.java:64)

        at com.google.apphosting.utils.config.AppEngineWebXmlReader.processXml(AppEngineWebXmlReader.java:132)

        at com.google.apphosting.utils.config.AppEngineWebXmlReader.readAppEngineWebXml(AppEngineWebXmlReader.java:

76)

        at com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.init(VmRuntimeWebAppContext.java:224)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:606)

        at org.eclipse.jetty.util.TypeUtil.call(TypeUtil.java:500)

        at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.call(XmlConfiguration.java:730)

        at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417)

        at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:354)

        at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:262)

        at org.eclipse.jetty.deploy.providers.WebAppProvider.createContextHandler(WebAppProvider.java:287)

[Nick (Cloud Platform Support)]

Hey Rahul,

This forum isn't the right place to post specific-issue technical support requests. These should be posted to either Stack Overflow or the App Engine Public Issue Tracker, depending on whether you believe the issue to be mostly based on your own misunderstanding or on an actual issue in the platform itself (and thus would require tracking in a public issue tracker). In those places, your post is far more likely to find its way to people who are willing and able to assist in debugging. 

Sincerely,

Nick
Cloud Platform Community Support