Opened 16 years ago
Closed 16 years ago
#494 closed defect (fixed)
Unexpected Error on JSP for Experiment Overview
Reported by: | base | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.2.2 |
Component: | core | Version: | 2.2.1 |
Keywords: | Experiment Overview JSP | Cc: |
Description
I have loaded 2 experiments, one gives me the following problem
stack trace:
Experiment Options… Unexpected error java.lang.NullPointerException? on page /nutribase221/views/experiments/overview/index.jsp Version BASE 2.3.0pre (build #3130; schema #29) Web server Apache Tomcat/5.5.15 Database Dialect org.hibernate.dialect.MySQLInnoDBDialect JDBC Driver com.mysql.jdbc.Driver (version 5.0) Java runtime Java(TM) 2 Runtime Environment, Standard Edition (1.5.0_06-b05), Sun Microsystems Inc. Operating system Windows XP x86 5.1 Memory Total: 31.5 MB Free: 9.9 MB Max: 254.1 MB Browser Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Error message Stack trace
...at net.sf.basedb.util.overview.ExperimentOverview?.addRawBioAssay(ExperimentOverview?.java:621) ...at net.sf.basedb.util.overview.ExperimentOverview?.addRawBioAssays(ExperimentOverview?.java:573) ...at net.sf.basedb.util.overview.ExperimentOverview?.generateOverview(ExperimentOverview?.java:309) ...at net.sf.basedb.util.overview.ExperimentOverview?.(ExperimentOverview?.java:256) ...at net.sf.basedb.util.overview.ExperimentOverview?.getOverview(ExperimentOverview?.java:187) ...at org.apache.jsp.views.experiments.overview.index_jsp._jspService(org.apache.jsp.views.experiments.overview.index_jsp:87) ...at org.apache.jasper.runtime.HttpJspBase?.service(HttpJspBase?.java:97) ...at javax.servlet.http.HttpServlet?.service(HttpServlet?.java:802)
...at org.apache.jasper.servlet.JspServletWrapper?.service(JspServletWrapper?.java:332) ...at org.apache.jasper.servlet.JspServlet?.serviceJspFile(JspServlet?.java:314) ...at org.apache.jasper.servlet.JspServlet?.service(JspServlet?.java:264) ...at javax.servlet.http.HttpServlet?.service(HttpServlet?.java:802) ...at org.apache.catalina.core.ApplicationFilterChain?.internalDoFilter(ApplicationFilterChain?.java:252) ...at org.apache.catalina.core.ApplicationFilterChain?.doFilter(ApplicationFilterChain?.java:173) ...at net.sf.basedb.clients.web.servlet.CharacterEncodingFilter?.doFilter(CharacterEncodingFilter?.java:71) ...at org.apache.catalina.core.ApplicationFilterChain?.internalDoFilter(ApplicationFilterChain?.java:202) ...at org.apache.catalina.core.ApplicationFilterChain?.doFilter(ApplicationFilterChain?.java:173) ...at org.apache.catalina.core.StandardWrapperValve?.invoke(StandardWrapperValve?.java:213) ...at org.apache.catalina.core.StandardContextValve?.invoke(StandardContextValve?.java:178) ...at org.apache.catalina.core.StandardHostValve?.invoke(StandardHostValve?.java:126) ...at org.apache.catalina.valves.ErrorReportValve?.invoke(ErrorReportValve?.java:105) ...at org.apache.catalina.core.StandardEngineValve?.invoke(StandardEngineValve?.java:107) ...at org.apache.catalina.connector.CoyoteAdapter?.service(CoyoteAdapter?.java:148) ...at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) ...at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) ...at org.apache.tomcat.util.net.PoolTcpEndpoint?.processSocket(PoolTcpEndpoint?.java:527) ...at org.apache.tomcat.util.net.LeaderFollowerWorkerThread?.runIt(LeaderFollowerWorkerThread?.java:80) ...at org.apache.tomcat.util.threads.ThreadPool?$ControlRunnable?.run(ThreadPool?.java:684) ...at java.lang.Thread.run(Thread.java:595)
cheers
Philippe
Change History (2)
comment:1 Changed 16 years ago by
Component: | web → core |
---|---|
Milestone: | → BASE 2.2.2 |
Owner: | changed from Johan Enell to Nicklas Nordborg |
comment:2 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think this happens if there is a raw bioassay without annotations. It should be easy to fix by checking 'annotationsNode' for null on line 621. Note, that the failure on the following lines should still be generated in this case.