Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via harmony-alerts by nomail@intel.com, 1 year ago
expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=61,y=17]>
via harmony-alerts by nomail@intel.com, 1 year ago
expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=61,y=17]>
via harmony-alerts by nomail@intel.com, 1 year ago
expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=760,y=542]>
via harmony-alerts by nomail@intel.com, 1 year ago
expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=760,y=542]>
via harmony-alerts by nomail@intel.com, 1 year ago
expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=760,y=542]>
via harmony-alerts by nomail@intel.com, 1 year ago
expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=760,y=542]>
java.awt.WindowTestjunit.framework.AssertionFailedError: expected:<java.awt.Point[x=699,y=525]> but was:<java.awt.Point[x=61,y=17]> at java.awt.WindowTest.testSetLocationRelativeTo(WindowTest.java:82) at java.lang.reflect.VMReflection.invokeMethod(Native Method)