Thanks a lot for your explanation.
The thing that puzzled me was that the HTTP 503 error generated when the
ear file was deployed to Weblogic 14 server. If the error and warning can
be ignored, why did we encounter this HTTP 503 error? What is the best way
to figure out what caused this server error?
Currently, I'm working on installing WebLogic server 14 my in Eclipse for
local deployment, however, I'm not sure if this is a better way for our
local development as I don't have much experience with Weblogic server. The
production WebLogic server on Linux is maintained by another group.
Would Jetty or Tomcat server be a better choice in terms of easy
configuration etc.? If so, we should install the latest version, right?
Your help is much appreciated,
Jenny
On Friday, June 25, 2021 at 5:01:19 AM UTC-5 Jens wrote:
>
>> The code server is ready at http://127.0.0.1:9876/
>> Code server started in 4.878 s ms
>> *[ERROR] jreLeakPrevention.gcDaemonFail*
>> *java.lang.ClassNotFoundException: sun.misc.GC*
>>
>
> This can be ignored. GWT's class JettyLauncher tries to fix a class loader
> memory leak within sun.misc.GC but this class does not exist in that
> package in Java 11. The exception is catched and logged as error, but code
> will continue.
>
>
> java.lang.RuntimeException: Error scanning entry module-info.class from
>> jar
>> file:/C:/Users/jiny/gitTestUpgrade/aries/war/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar
>> at
>> org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)
>> at
>> org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
>> at
>> org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
>> at
>> org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
>> at
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
>> at
>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
>> at java.base/java.lang.Thread.run(Thread.java:834)
>> Caused by: java.lang.UnsupportedOperationException: This feature requires
>> ASM6
>> at org.objectweb.asm.ClassVisitor.visitModule(ClassVisitor.java:130)
>> at
>> org.objectweb.asm.ClassReader.readModuleAttributes(ClassReader.java:724)
>> at org.objectweb.asm.ClassReader.accept(ClassReader.java:544)
>> at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)
>> at
>> org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)
>> at
>> org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)
>> at
>> org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)
>> ... 6 more
>>
>
>
> The embedded Jetty provided by GWT's DevMode class is too old to handle
> module-info.class files correctly during class file scanning. It basically
> requires newer ASM version.
>
> The recommend approach for anything other than a small demo app is to not
> use the embedded Jetty provided by GWT DevMode. Instead use your own Jetty
> installation or a Jetty plugin for Gradle/Maven to deploy the server side
> part of your app. Or even better use the same application server that you
> are also using in production to minimize development/production
> differences. Once you do that you can also directly use GWT's CodeServer
> class without going through DevMode class. This will also remove the error
> log regarding sun.misc.GC.
>
> There is also a discussion in
> https://groups.google.com/g/google-web-toolkit-contributors/c/iU9hckIab2o
> to gather feedback wether or not GWT should remove embedded Jetty support.
> It makes configuring a server more complex but you also don't run into a
> situation where everything seems to look right, but still it does not work,
> as in your case.
>
> -- J.
>
>
>
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/beefbaf2-c7f9-4399-acd6-392380d378a4n%40googlegroups.com.
