Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » [SOLVED]Eclipselink crashing after throw a Database Excetion
[SOLVED]Eclipselink crashing after throw a Database Excetion [message #558443] Sun, 12 September 2010 21:23 Go to next message
Daniel Frank is currently offline Daniel Frank
Messages: 14
Registered: July 2010
Junior Member
Hi,
After a Datebase Exception all of my new transactions result in a NullpointerException.
Erro:
[EL Warning]: 2010-09-12 18:11:15.493--UnitOfWork(21069155)--Thread(Thread[http-8080-1,5,main])--java.lang.NullPointerException
	at org.eclipse.persistence.internal.sessions.AbstractRecord.get(AbstractRecord.java:270)
	at org.eclipse.persistence.descriptors.InheritancePolicy.classFromRow(InheritancePolicy.java:327)
	at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:473)
	at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:441)
	at org.eclipse.persistence.queries.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:635)
	at org.eclipse.persistence.queries.ReadAllQuery.registerResultInUnitOfWork(ReadAllQuery.java:838)
	at org.eclipse.persistence.queries.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:464)
	at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:997)
	at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:675)
	at org.eclipse.persistence.queries.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:958)
	at org.eclipse.persistence.queries.ReadAllQuery.execute(ReadAllQuery.java:432)
	at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:1021)
	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2863)
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1181)
	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:453)
	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.getResultList(EJBQueryImpl.java:669)
	at jpaeclipselink.service.ContatoService.teste(ContatoService.java:52)
	at jpaeclipselink.service.ContatoService.findAllContatos(ContatoService.java:30)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:421)
	at flex.messaging.services.RemotingService.serviceMessage(RemotingService.java:183)
	at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1495)
	at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:882)
	at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:121)
	at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158)
	at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:44)
	at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:67)
	at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:146)
	at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:278)
	at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:315)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at jpaeclipselink.filter.JPAFilter.doFilter(JPAFilter.java:23)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:619)


Anyone can help me?

[Updated on: Thu, 16 September 2010 15:43]

Report message to a moderator

Re: Eclipselink crashing after throw a Database Excetion [message #558636 is a reply to message #558443] Mon, 13 September 2010 18:40 Go to previous messageGo to next message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

What is the database exception?

Is the JDBC driver still able to function, or is it returning invalid data?



James : Wiki : Book : Blog : Twitter
Re: Eclipselink crashing after throw a Database Excetion [message #558684 is a reply to message #558443] Tue, 14 September 2010 00:16 Go to previous messageGo to next message
Daniel Frank is currently offline Daniel Frank
Messages: 14
Registered: July 2010
Junior Member
Anyone database exception like a NOT NULL verification.
I think the JDBC driver is correct. I can''t see any invalid data only the stacktrace that I showed before.

Additional information: It is a Web application running under tomcat.
Re: Eclipselink crashing after throw a Database Excetion [message #559416 is a reply to message #558443] Thu, 16 September 2010 14:58 Go to previous messageGo to next message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

I have never seen this, and can't see how it could possible occur.

What database/JDBC driver are you using?

It looks like the row being returned from the database is empty, which does not make much sense.

Please include the stack trace of the exception that occurred.


James : Wiki : Book : Blog : Twitter
Re: Eclipselink crashing after throw a Database Excetion [message #559442 is a reply to message #558443] Thu, 16 September 2010 15:43 Go to previous message
Daniel Frank is currently offline Daniel Frank
Messages: 14
Registered: July 2010
Junior Member
Hi James,
I found the root of the problem, it is related to serialization of BlazeDS (
http://www.parkplanet.net/blog/post.cfm/controlling-serializ ation-of-java-objects-in-lcds-or-blazeds ).
Solved using a Spring Exception Translator.
Regards,

Previous Topic:ValidationException while deployment on Tomcat with enabled TomcatSecurity
Next Topic:EclipseLink + OSGi
Goto Forum:
  


Current Time: Fri Oct 31 04:55:36 GMT 2014

Powered by FUDForum. Page generated in 0.03221 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software