wso2 / wso2/testgrid

Dashboard crashes after a day of operation

Open
#1,237 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
60
Forks
78
PR merge metrics
No merged PRs in 30d

Description

Description:
The dashboard keeps crashing after a day of operation. Following error log was observed in logs. We need to upgrade eclipselink jpa library.

05:26:21.444 [https-jsse-nio-8443-exec-6] ERROR org.wso2.testgrid.web.api.ProductService - Error occurred while fetching the Product statuses 
org.wso2.testgrid.dao.TestGridDAOException: Error occurred when searching for entity.
	at org.wso2.testgrid.dao.repository.AbstractRepository.findAll(AbstractRepository.java:165) ~[org.wso2.testgrid.dao-1.0.5-SNAPSHOT.jar:1.0.5-SNAPSHOT]
	at org.wso2.testgrid.dao.repository.ProductRepository.findAll(ProductRepository.java:104) ~[org.wso2.testgrid.dao-1.0.5-SNAPSHOT.jar:1.0.5-SNAPSHOT]
	at org.wso2.testgrid.dao.uow.ProductUOW.getProducts(ProductUOW.java:82) ~[org.wso2.testgrid.dao-1.0.5-SNAPSHOT.jar:1.0.5-SNAPSHOT]
	at org.wso2.testgrid.web.api.ProductService.getAllProductStatuses(ProductService.java:125) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_151]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_151]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_151]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_151]
	at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) [jersey-server-2.22.2.jar:?]
....
Caused by: java.lang.NullPointerException
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeDeferredEvents(AbstractSession.java:1189) ~[org.eclipse.persistence.core-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2843) ~[org.eclipse.persistence.core-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1521) ~[org.eclipse.persistence.core-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1503) ~[org.eclipse.persistence.core-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1477) ~[org.eclipse.persistence.core-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:484) ~[org.eclipse.persistence.jpa-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.getResultList(EJBQueryImpl.java:741) ~[org.eclipse.persistence.jpa-2.2.0.jar:2.2.0.v20110202-r8913]
	at org.wso2.testgrid.dao.repository.AbstractRepository.findAll(AbstractRepository.java:163) ~[org.wso2.testgrid.dao-1.0.5-SNAPSHOT.jar:1.0.5-SNAPSHOT]
	... 54 more

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with AbstractRepository.findAll at line 163 and ProductRepository.findAll at line 104, following the stack trace into ProductUOW.getProducts and ProductService.getAllProductStatuses. Check how the EclipseLink JPA version is declared and whether the deferred-event NullPointerException can be reproduced after prolonged operation. Done means the dashboard remains available after a day without this exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.