Errors Found Glassfish Eclipse Web Service

  • June 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Errors Found Glassfish Eclipse Web Service as PDF for free.

More details

  • Words: 459
  • Pages: 2
Error 1: Buildfile: D:\Glassfish eclipse\Workspace\.metadata\.plugins\org.eclipse.jst.server.generic.core\serverdef \sunappsrv-ant.xml deploy.j2ee.web: resourcesfile.check: tools: addresources: tools: deploydir: [exec] CLI171 Command deploydir failed : Deploying application in domain failed; Error loading deployment descriptors for module [SimpleTest] -UnsupportedClassVersionError: Class test.TestService has unsupported major or minor version numbers, which are greater than those found in the Java Runtime Environment version 1.5.0_10 [echo] Application dir Deployed at: http://localhost:8082/SimpleTest BUILD SUCCESSFUL Total time: 1 second Remedy: If you check the top of the server log it's starting with 1.5.0_11 which is the JRE that MyEclipse ships with for the "All in One" installer. Are you saying after you posted that last message you change the connector to use a 1.6 JDK to launch Glassfish and it's worknig better except for some *other* error, or you are still getting that same ZipException? Here are the steps that we can try to get things working: 1. Make sure you are running Glassfish with 1.6.0_02 or later JDK (not just a JRE). Edit asenv.bat under glassfish\conf set AS_HOME=jdk fully qualified path\jre/.. 2. Step 1 will get rid of that Class version exception for the timer bean during startup. 3. After that, shut down the app server and remove any and all deployments and then re-create them *while the server is stopped* 4. Start the server back up, make sure the deployments are loaded correctly.

Error 2: "Waiting For Virtual Machine To Exit" in eclipse Remedy : When you have "Waiting For Virtual Machine To Exit" message and did not change any progress , you might install "Axis2 Code Generator" in Eclipse. In order to solve this problem, you should change ANT home setting in eclipse. Because when you install "Axis2 Code Generator" in eclipse , it change the ANT HOME setting. So please go to "Window > Preference > Ant > Runtime". There will be "Ant Home Entires" part. You can confirm the jar files are from Axis2 plugin directory. This is causing the problem so please click "Ant Home" button on the right side and setting up ant home such as "D:\java\ant\apache-ant-1.7.0" directory and click OK.

Error 3 : While running Glassfish in Eclipse you got Invalid username or password error Remedy : Double click on the GlassFish entry in Servers view. Change the Username and Password according to GlassFish (default password is adminadmin for GlassFish)

Error 4: While trying to run Web Service it gives 404 error. Remedy : Here problem is with GlassFish plugin. Try to get latest plugin for eclipse. Also check for AS_HOME in glassfish\conf\asenv.bat file. It should be pointing to JDK 1.6 Error 5: org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Any type element type has not been given Remedy : We should not return any Collection object in the method. Try to return object which doesn’t belongs to Collection package.

Related Documents

Glassfish
November 2019 14
Glassfish
November 2019 12
Web Service
October 2019 18
Eclipse
November 2019 48