-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to deploy simple ear from command line on GlassFish 6 build #23080
Comments
Hi @scottkurz, I tried to reproduce the issue on GlassFish master and got a different issue on the deployment of the
After applying the ORB patch (eclipse-ee4j/orb#97), The ear deploys successfully and GreeterServlet is accessible via |
The Orb issue should be fixed in the latest master. |
I was still seeing the problem after pulling down the latest updates and doing a clean build. I then threw away all of the local maven repo jakarta artifacts and rebuilt, and now the deployment is working. Either some cached staging build or other local build was causing the problem. |
When attempting to deploy a simple Jakarta EE 9 based ear using asadmin, a 500 error is seen due to an internal org.glassfish.jersey.server.ContainerException: java.lang.NoClassDefFoundError: javax/xml/datatype/DatatypeConfigurationException error.
Environment Details
GlassFish Version: Eclipse GlassFish 6.0.0 (build starksm-private)
java version "1.8.0_251"
Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)
OSX 10.14.6
none
Problem Description
Attempting to deploy a simple ear containing a stateless EJB and simple Servlet from the command line fails with an internal error.
The server shows:
The full stack trace is attached:
full-strace.txt
Steps to reproduce
Using the attached test.ear.zip, copy it into /tmp/test.ear, and use the asadmin command from the glassfish6 build:
glassfish$ bin/asadmin deploy /tmp/test.ear
I/O Error: Server returned HTTP response code: 500 for URL: http://localhost:4848/command/deploy
Command deploy failed.
Impact of Issue
Unable to validate bean-validation TCK due to being unable to deploy test EARs.
The text was updated successfully, but these errors were encountered: