Opened 5 months ago
Closed 5 months ago
#1599 closed defect (fixed)
NullPointerException when starting ASCAT jobs
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | Reggie v5.0.2 |
Component: | net.sf.basedb.reggie | Keywords: | |
Cc: |
Description
This is the stacktrace:
java.lang.NullPointerException: Cannot invoke "net.sf.basedb.core.File.getName()" because "normalBam" is null at net.sf.basedb.reggie.grid.AscatJobCreator.createAscatJobs(AscatJobCreator.java:257) at net.sf.basedb.reggie.servlet.AscatServlet.doPost(AscatServlet.java:411) at javax.servlet.http.HttpServlet.service(HttpServlet.java:528) at javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
When checking the list of items that are displayed in the "Start ASCAT" wizard it seems like tumor alignments are matched against normal alignments that are still waiting in the job queue for being aligned. The error will go away once all alignments have been completed, but the code should of course be updated so that only completed alignments are selected.
There is probably a similar problem in the "Start variant calling" wizard.
Note:
See TracTickets
for help on using tickets.
In 7765: