Hi Jan,
On 9/10/14 11:29 AM, Jan Berg wrote:
> Hi!
>
> So i've been having problems with migrating from glassfish 2 to
> glassfish 4. The migration has been progressing a bit, and currently i
> have only one problem, which is with webservice tester. The thing is,
> that the tester itself prints some error, but there's no sign of the
> complete error details in the server logs.
Actually it may be complete error showing that there seems to be
something wrong in the tester itself and it looks like a bug. The best
would be file it through
https://java.net/jira/secure/CreateIssue!default.jspa - project
GlassFish, component web_services. Do not forget to describe the service
you're trying to test (ie special setup, protocol etc) and paste the
stack trace there
thanks,
--lukas
>
> javax.servlet.ServletException: java.lang.NullPointerException at
> org.glassfish.webservices.monitoring.WebServiceTesterServlet.doPost(WebServiceTesterServlet.java:336)
> at
> org.glassfish.webservices.monitoring.WebServiceTesterServlet.invoke(WebServiceTesterServlet.java:106)
> at
> org.glassfish.webservices.JAXWSServlet.doPost(JAXWSServlet.java:157)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:318)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673)
> at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99) at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)
> at
> org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:357)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:260)
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:188)
> at
> org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191)
> at
> org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168)
> at
> org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189)
> at
> org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114)
> at
> org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
> at
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838)
> at
> org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113)
> at
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115)
> at
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55)
> at
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135)
> at
> org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564)
> at
> org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544)
> at java.lang.Thread.run(Thread.java:745) Caused by:
> java.lang.NullPointerException at
> org.glassfish.webservices.monitoring.WebServiceTesterServlet.doPost(WebServiceTesterServlet.java:307)
> ... 31 more
>
> Thats the error which is printed. Is there any way for me to get the
> full error (can't see the "31 more" part anywhere) so probably end up
> missing a bit of information here. I tried to fiddle a bit with the
> logger config in glassfish admin panel, but no luck whatsoever. Of
> course if there is some possible problem, which you could see from the
> error message as it is right now, i would be glad to have some tips on
> what the cause could possibly be. The same exact webservice tester
> does work on the glassfish 2. However the ear package used on
> glassfish 4 is slightly different from the old package (few jars in
> different places as before). Also other webservices does seem to work
> ok, the application itself runs with no errors.
>
> Any help will be greatly appreciated!
>
>