NullPointerException after logging in to admin console.
This happens if the number of open files allowed is low.
Update the limit in /etc/security/limits.conf and restart. I used 16384, works fine now.
June 19, 2012
org.hibernate.hql.ast.QuerySyntaxException
Description: org.hibernate.hql.ast.QuerySyntaxException: Tablename is not mapped [SELECT id
FROM Tablename] when trying to run NamedQuery in JPA.
Reason/Solution: Put simply, you are using the table name instead of the Entity class name mapped in persistence.xml.
So if table USERS is mapped to entity class User, your query will need User and not USERS.
FROM Tablename] when trying to run NamedQuery in JPA.
Reason/Solution: Put simply, you are using the table name instead of the Entity class name mapped in persistence.xml.
So if table USERS is mapped to entity class User, your query will need User and not USERS.
June 18, 2012
WTP metadata
Description: This project needs to migrate WTP Metadata.
Solution: At times, just a QuickFix from the Problems view might work. If not, try renaming the project temporarily , and then naming it back followed by a full build or clean. HTH.
Errors occurred during wsimport.
Description: Errors occurred during wsimport.
[failed to localize] wsimport.ParsingWSDL()
[failed to localize] wsimport.ErrorMessage(A class/interface with the same name "mypackage.MyClass" is already in use. Use a class customization to resolve this conflict.)
[failed to localize]
Reason:This is an error generated by the XJC that comes with JDK 1.6.
Solution: While there are parameters you can pass to the tool from command line etc, the simplest explanation is that there are multiple types of the same name in your WSDL/XSD. Resolve the duplicate names and you will be good to go.
The MyClass is the XSD type you are looking for! HTH!
[failed to localize] wsimport.ParsingWSDL()
[failed to localize] wsimport.ErrorMessage(A class/interface with the same name "mypackage.MyClass" is already in use. Use a class customization to resolve this conflict.)
[failed to localize]
Reason:This is an error generated by the XJC that comes with JDK 1.6.
Solution: While there are parameters you can pass to the tool from command line etc, the simplest explanation is that there are multiple types of the same name in your WSDL/XSD. Resolve the duplicate names and you will be good to go.
The MyClass is the XSD type you are looking for! HTH!
November 06, 2007
RAD does not start
Description: RAD does not startup. I came across the problem with RAD 7.0. You get a popup screen showing something like this.
Reason: Not sure. Might be with initialisation.
Solution: Open the eclipse.ini file located in the RAD installation directory. just delete all the contents of the file. Save the file and try to open RAD again.
WARNING: Keep a backup of the eclipse.ini file. [Just in case my fix fails :D]
-vmC:\RAD70SDP\jdk\jre\bin\javaw.exe
-vmargs
-Xquickstart
-Xms40m
-Xmx768m
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:singleJVM,keep
-Xnolinenumbers
-XX:MaxPermSize=512M
Reason: Not sure. Might be with initialisation.
Solution: Open the eclipse.ini file located in the RAD installation directory. just delete all the contents of the file. Save the file and try to open RAD again.
WARNING: Keep a backup of the eclipse.ini file. [Just in case my fix fails :D]
November 05, 2007
CREATE_LISTENER_FAILED_4
Description: This is often encountered when you try to start your server (WAS). It is typically seen with RAD6.0. I never came across the problem with RAD 7.0.
Reason: Occurs when the server process related to a particular server instance is not terminated and you try to start the same server. So the applications running on the ports give a problem because the port is already occupied.
Solution: Go to task manager, and end the process in the name java.exe.
WARNING: If you have multiple servers running, you might risk ending some other server process.
Reason: Occurs when the server process related to a particular server instance is not terminated and you try to start the same server. So the applications running on the ports give a problem because the port is already occupied.
Solution: Go to task manager, and end the process in the name java.exe.
WARNING: If you have multiple servers running, you might risk ending some other server process.
Subscribe to:
Posts (Atom)