[
https://issues.apache.org/jira/browse/PIVOT-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808866#comment-13808866
]
Sandro Martini commented on PIVOT-927:
--------------------------------------
Ok so the maven jars is not a real problem, good :-) .
The problem with maven exec is due to a change (made many time ago) to ensure
that code will be run from the right thread, and this is a good feature ... but
the problem is for example in the run from Maven. Note that there is a
workaround, or fork a process instead of an inline run.
I'm not sure if we can solve this (targeting only Maven users) in a simple way,
but if you want, add a new issue so we can try to look ... maybe creating a
dedicated class where this restriction doesn't apply, but maybe add it to a
dedicated subproject (someone remember our old subproject tools ?) for
developers-only.
Finally, to resolve this issue we wait your tests with updated jars (fix by
Roger), ok ?
Thanks for now.
> Unexpected NPE
> --------------
>
> Key: PIVOT-927
> URL: https://issues.apache.org/jira/browse/PIVOT-927
> Project: Pivot
> Issue Type: Question
> Affects Versions: 2.0.3
> Reporter: Łukasz Hanusiak
> Assignee: Roger Whitcomb
> Fix For: 2.0.4, 2.1
>
>
> After upgrading to pivot 2.0.3 my application randomly becomes unresponsive
> after throwing NPE with following trace:
> java.lang.NullPointerException
> at
> org.apache.pivot.wtk.ApplicationContext$DisplayHost.processMouseMotionEvent(ApplicationContext.java:1132)
>
> at java.awt.Component.processEvent(Unknown Source)
> at
> org.apache.pivot.wtk.ApplicationContext$DisplayHost.processEvent(ApplicationContext.java:793)
>
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> After mentioned exception occurs user is unable to use any element of UI.
> Only application restart helps solve this problem. Even more confusing is
> fact that problem sometimes occurs after few minutes and sometimes after few
> hours or even days.
> Can anybody give me some pointers how to workaround / fix this situation?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
