java.lang.NullPointerException when using stack trace feature from Fusion Reactor web UI

[Daniel Heighton]

On both of our FR instances, we are getting a null pointer exception when trying to stack trace running requests. I've attached a screenshot, and included the raw text.

I've restarted both the Coldfusion service, and the physical machine, and it hasn't changed it. I haven't yet tried to reinstall the service into the CF instance from FRAM, but will during maintenance this weekend.

I first noticed the behavior after we updated to 7.4.1, but can't be sure on timeline, as I don't stack trace everyday.

FR Version:

Revision: 7.4.1, Build: fusionreactor.40.79843.branches/FR-7.4.x-MAINT

Running on Windows Server 2016. 

Raw Text:

java.lang.NullPointerException

com.intergral.fusionreactor.plugin.ui.internal.pages.resources.TraceThreads.doSingle(TraceThreads.java:582)
com.intergral.fusionreactor.plugin.ui.internal.pages.resources.TraceThreads.doCommand(TraceThreads.java:165)
com.intergral.fusionreactor.plugin.ui.extendables.PageContributorImpl.doCommand(PageContributorImpl.java:238)
com.intergral.fusionreactor.filter.osgi.PageTracker.getResponseFromPageContributor(PageTracker.java:518)
com.intergral.fusionreactor.filter.osgi.PageTracker._getResponse(PageTracker.java:394)
com.intergral.fusionreactor.filter.osgi.PageTracker.getResponse(PageTracker.java:256)
com.intergral.fusionreactor.filter.osgi.FusionReactorOSGIServlet.service(FusionReactorOSGIServlet.java:61)
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044)
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372)
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978)
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
org.eclipse.jetty.server.Server.handle(Server.java:369)
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486)
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:933)
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:995)
org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
java.lang.Thread.run(Thread.java:748)

[charlie arehart]

Yep, that’s a sudden new bug, that the team knows about (I experienced this with a client who reported it, and that was the response). So assuming it came in 7.4.1, you could revert back to 7.4.0 if you had the installer (sadly there seems no means on the FR site to access prior installers, that I readily see).

An FR engineer may hop in here and let us know of a better solution (or whether a fix in a new update is pending). As you may know, they are based in Germany and it’s already evening, and now with the weekend, we may not see a solution until next week (if then, depending on how hard it is to solve), but hopefully someone will respond sooner.

/charlie

 

From: fusion...@googlegroups.com <fusion...@googlegroups.com> On Behalf Of Daniel Heighton
Sent: Friday, September 21, 2018 03:34 PM
To: FusionReactor <fusion...@googlegroups.com>
Subject: [fusionreactor] java.lang.NullPointerException when using stack trace feature from Fusion Reactor web UI

 

On both of our FR instances, we are getting a null pointer exception when trying to stack trace running requests. I've attached a screenshot, and included the raw text.

 

<snip>

[michael...@intergral.com]

Hi Daniel,

As Charlie mentioned this is a known bug with FusionReactor, we have developed a fix for this that should be released in the next few days.

As a workaround downgrading to a pre 7.4.0 instance should resolve this issue, alternatively If you can send your license key to sup...@fusion-reactor.com I can send you an ultimate edition license so you will no longer see this NPE.

Regards,

Michael Flewitt

FusionReactor SupportTeam

[Daniel Heighton]

I'll wait for the fix. We found a temp work around that covers our use cases so far. If you go to kill a thread, it shows the last 5 frames of the stack trace.

It's not a daily issue right now, just when you need it, you need it.

--Daniel Heighton
--VP of Technology
--435-586-1205 x120

--
You received this message because you are subscribed to a topic in the Google Groups "FusionReactor" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fusionreactor/gRitXg8EM9c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fusionreactor+unsubscribe@googlegroups.com.
To post to this group, send email to fusion...@googlegroups.com.
Visit this group at https://groups.google.com/group/fusionreactor.
For more options, visit https://groups.google.com/d/optout.

[charlie arehart]

The fix came out overnight: 7.4.2.

/charlie

 

From: fusion...@googlegroups.com <fusion...@googlegroups.com> On Behalf Of Daniel Heighton

Sent: Monday, September 24, 2018 05:38 PM
To: fusion...@googlegroups.com
Subject: Re: [fusionreactor] Re: java.lang.NullPointerException when using stack trace feature from Fusion Reactor web UI