Frequently Asked Questions and Its Solution
Can't start J2EE server
Named Directory Service Port Conflict Symptom: When you use -verbose to select Start J2EE Server, display the following information: J2EE Server Listen Port: 1050 runtimeException: Could Not Initialize Server........................................................... If the J2EE service has already run, you can stop this service by entering J2EE -STOP. If other programs use this port, you can change the default port (1050) by modifying the config / orb.properties file installed in your J2EE SDK. For more information on the default port number, see the configuration wizard provided simultaneously when downloading J2EE SDK.
Web service port conflict symptom: When you start J2EE service using the -verbose option: LifeCycleException: httpconnector [8000] .Open: java.net.bindexception: address in use.... Solution: Other programs use ports 8000. You can change the default port (8000) by modifying the config / orb.properties file installed by your J2EE SDK to change the default port (8000).
Wrong XML parsing Symptom: When you start J2EE service using the -verbose option, display the following information: Exception in thread "main" javax.xml.parsers.FactoryConfigurationerror: org.apache.xerces.jaxp.saxparserfactoryImpl at.. Solution : Remove the JRE / lib / jaxp.properties file from your J2SE installation directory.
Compile Error
Ant can't find the structure of the texture: When you enter Ant Converter, the following information is displayed: buildfile: build.xml does not exist! build failed. Solution: Before running Ant, go to the J2EETORIAL / EXAMPLES / SRC directory. If you want to run Ant in the current directory, you must specify a constructor in the command line. For example, in the window you need to enter the following command in the same row: Ant -BuildFile C: J2ETUTORIALEXAMPLESSRCUILD.XML CONVERTER
The compiler cannot resolve symbol symptoms: When you enter Ant Converter, the compiler reports many errors, including: Cannot Resolve Symbol... Build Faled.. Compile Failed, Messages Should Have Been Provided Solution: Make sure you are correct The J2EE_HOME environment variable is configured. For more information, see Check the environment variable.
After you run the client, Ant 1.4 does not compile example symptoms: Ant 1.4 Display the following error: The FileName, Directory Name, or Volume Label Syntax INCORRECT. Solution: Use the version 1.3 version of Ant. The JavaCMD environment variable is used for the 1.4 version, the ANT.BAT script and J2EE SDK scripts use. The SDK's RunClient.bat script may set up JavaCMD, which has caused Ant.bat issues.
Deployment error
In your classpath, the wrong XML parses: display the following error:.... [] Java.rmi.RemoteException: Error saving / openingDeployment error: Bad mapping of key {0} Class {1}, Not Found: COM. Sum.Enterprise.Deployment.xml.ApplicationNode Solution: Delete the JAXP.jar file from your J2SE installation directory. This JAR file contains an XML parser that is not compatible with the J2EE server. If you don't have a jaxp.jar file, your classpath may reference a Tomcat installed XML program. In this case, you need to delete this environment from your classpath.
The remote home interface is specified as a local HOME interface symptom: LocalHomeImpl Must Be Declared Abstract. It does not define javax.ejb.homehandle gethomeHandle () from interface javax.ejb.ebhome. Solution: Remove from the EAR file This Enterprise Bean (EditDelete) creates a new bean using the New Enterprise Bean wizard. In the General dialog box of the Wizard, select the Remote Home Interface and Remote Interface Combination box.
J2EE application client running error
The client throws a noclassdeffounderror symptom: client report the following exception: java.lang.noclassdeffounderror: Converter.converterHome solution: This error is that the client cannot find classes in the ConverterAppClient.jar file. Please carefully check if you are properly executed in accordance with the deployment of the J2EE application client.
The client cannot find Convertrapp.ear Symptoms: Client Report: IOException: Convertrapp.ear Does Not Exist Solution: Seriously check if the Convertrapp.ear file exists and specify -client options: Runclient -client Convertrapp.ear -Name ConverterClient For more information on creating a Convertrapp.ear file, see Creating a J2EE application and running a J2EE application client.
The client cannot find the symptoms of the ConverterClient component: The client displays the following information: No Application Client Descriptors Defined for:..................................... For more information on establishing a ConverterClient component, see Pack the J2EE application client.
Login failure Symptom: After logging in, display the following information: IncorRect login and / or password solution: After the login prompt, the username enters Guest, password input guest123.
J2EE application is not deployed: Client Report: NameNotFoundException. Root exception is org.omg.cosnaming....
JNDI Name Error Symptom: Client Report The following exception: NameNotFoundException. Root exception is org.omg.cosnaming... Re-specify the correct JNDI name and re-deploy the application. Web client running error
The Web's URL environment is incorrect: The browser report page is not found (HTTP 404). Workaround: Check if the Web's URL environment is specified in the Component General Properties dialog (see Packing the web client). Questions for special attention.
The J2EE application is not deployed: the browser report page is not found (HTTP 404). Solution: Deploy the app.
JNDI Name Error Symptom: When you click on the submit button on the web page, the browser reports a servlet Exception Has Occurred. Workaround: In the JNDI Name panel of the symbol for Convertrapp, check whether the JNDI naming of ConverterBean and whether the JNDI name of Converterwar is matched. Re-specify the correct JNDI name and re-deploy the application.
The error check tool (Verifier) found in the verification tool can discover the contradiction between deployment descriptions and method features. These contradictions often lead to errors in deploying and runtime. In DeployTool, you can run the GUI version of Verifier by selecting Toolsverifier. You can also run Verifier's GUI version or command line. For more information, please refer to Appendix B.
Most of your EAR file with our comparison for this example, in the downloaded file contains the J2EE application's EAR file, which is located in the J2Eetutorial / Examples / Ears directory.
Other errors If these recommendations do not solve the problem, you may need to reinstall the application and clear the storage content in the server by running the Cleanup script. You must also need to close and restart the server: J2EE -STOP CLEANUP J2EE -VERBOSE
