List Icon
Mailing list Archive

2019 up to July 2022 | 20182017  |  2016  2015 2014 | 2013

The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter  


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[QF-Test] Problem with Swing lockup


  • Subject: [QF-Test] Problem with Swing lockup
  • From: STEPHENS Patrick <patrick.stephens@?.com>
  • Date: Thu, 24 Jan 2013 17:25:26 +0000

Hi all,
 
I thought I had modified my test application to use SwingUtilities.invokeAndWait() when creating its JFrame but I am still seeing a lockup when it is launched from QFTest.
 
 TestHCIMain(String[] args)
 {
  try {
   javax.swing.SwingUtilities.invokeAndWait( new Runnable() {
    public void run() {
     jFrame = getJFrame();
    }
   } );
  }
...
 public static void main(String[] args)
 {
  System.out.println("TestHCIMain started");
  
  for(int i = 0; i < args.length; ++i)
  {
   System.out.println(args[i]);
  }
  new TestHCIMain(args);
 }
...
 
This gives me a thread dump with the usual Swing thread safety culprit: java.awt.Component$AWTTreeLock
 
It looks like my invokeAndWait call has been triggered on a QFTest thread:
 
 at com.thalesgroup.sat.toolbar.test.TestHCIMain.getJFrame(TestHCIMain.java:122)
 at com.thalesgroup.sat.toolbar.test.TestHCIMain.access$100(TestHCIMain.java:45)
 at com.thalesgroup.sat.toolbar.test.TestHCIMain$1.run(TestHCIMain.java:67)
 at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at de.qfs.lib.gui.EventQueue.doDispatch(EventQueue.java:679)
 at de.qfs.apps.qftest.client.awt.dd.doDispatch(SourceFile:439)
 at de.qfs.lib.gui.EventQueue.dispatchEvent(EventQueue.java:592)
 at de.qfs.apps.qftest.client.awt.dd.a(SourceFile:350)
 at de.qfs.apps.qftest.client.awt.de.run(SourceFile:334)
 at java.security.AccessController.doPrivileged(Native Method)
 at de.qfs.apps.qftest.client.awt.dd.dispatchEvent(SourceFile:332)
 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)
 
Anyone seem anything obvious I've missed?
 
Regards,
Pat.

Patrick Stephens
Software Engineer

Thales UK
Dolphin House, Ashurst Drive
Cheadle Heath, Stockport SK3 OXB - UK
www.thales-naval.com

Tel: +44 (0)161 741 3860
e-mail: patrick.stephens@?.thalesgroup.com

 

Please consider the environment before printing a hard copy of this e-mail.

The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)1932 824800 and delete it and all copies from your system.

Thales Corporate Services Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 959962.  

Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273

 

Attachment: jstack_testhci.log
Description: jstack_testhci.log

Attachment: TestHCIMain.java
Description: TestHCIMain.java