java.lang.NullPointerException

This exception has no message.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web123839

  • via Terracotta by unnutz, 11 months ago
    This exception has no message.
  • This exception has no message.
  • This exception has no message.
  • Stack trace

    • java.lang.NullPointerException at com.gargoylesoftware.htmlunit.html.HtmlPage.loadFrames(HtmlPage.java:1786) at com.gargoylesoftware.htmlunit.html.HtmlPage.initialize(HtmlPage.java:169) at com.gargoylesoftware.htmlunit.WebClient.loadWebResponseInto(WebClient.java:456) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:332) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:389) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:374) at org.jvnet.hudson.test.HudsonTestCase$WebClient.getPage(HudsonTestCase.java:1519) at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:297) at org.jvnet.hudson.test.HudsonTestCase.runBare(HudsonTestCase.java:226) at com.sun.maven.junit.LocalTestCaseRunner.runTests(LocalTestCaseRunner.java:113) at com.sun.maven.junit.LocalTestCaseRunner.runTestCase(LocalTestCaseRunner.java:56) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:274) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:255) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:104) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:250) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.