cancel
Showing results for 
Search instead for 
Did you mean: 

NPE on browse after failed login

unknown-user
Champ on-the-rise
Champ on-the-rise
Just started testing the latest OWD 3.1.0.0 sprint 8 (CI) with IBM's P8 CMIS tip build and had an issue after a failed login.   Pressed the browse button and I see this exception:    Posting per your suggestion.   Thx.

java.lang.NullPointerException
at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.getResource(OwCMISNetwork.java:967)
at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.getObjectFromPath(OwCMISNetwork.java:922)
at com.wewebu.ow.server.app.OwEcmUtil.createObjectFromString(OwEcmUtil.java:290)
at com.wewebu.ow.server.plug.owrecord.OwRecordView.init(OwRecordView.java:358)
at com.wewebu.ow.server.ui.OwEventTarget.attach(OwEventTarget.java:44)
at com.wewebu.ow.server.ui.OwNavigationView.addView(OwNavigationView.java:89)
at com.wewebu.ow.server.app.OwMainNavigationView.addPluginView(OwMainNavigationView.java:170)
at com.wewebu.ow.server.app.OwMainLayout.addMasterPlugins(OwMainLayout.java:125)
at com.wewebu.ow.server.app.OwMainLayout.init(OwMainLayout.java:188)
at com.wewebu.ow.server.ui.OwEventTarget.attach(OwEventTarget.java:44)
at com.wewebu.ow.server.ui.OwWebApplication.handleRequest(OwWebApplication.java:370)
at org.apache.jsp.default20_jsp._jspService(default20_jsp.java:76)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:417)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:391)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:383)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:188)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:166)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:288)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
1 REPLY 1

d_evil
Champ in-the-making
Champ in-the-making
Hello Jay,

unfortunatelly we cannot reproduce the problem.

But the good news is that our final release of OWD 3.1.0.0 is out now,
please try it out http://sourceforge.net/projects/owd/.

If you should still have problems, provided us the stacktrace with the new error and we will help you as much as we can.

Regards,
D.evil