CODETOOLS-7902793: Fix IllegalMonitorStateException in JInternalFrameOperatorCloseTest

[shurymury]

What worked was to override setClosed(boolean) in JInternalFrame to not close the frame.

Also while inspecting the stack trace, I have discovered that the description is not passed down from JInternalFrameOperator.waitClosed()

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Referenced JBS issue must only be used for a single change
• Change must be properly reviewed

Issue

• CODETOOLS-7902793: Fix IllegalMonitorStateException in JInternalFrameOperatorCloseTest

Reviewers

• Abdul Kolarkunnu (@akolarkunnu - Committer)

Download

$ git fetch https://git.openjdk.java.net/jemmy-v2 pull/4/head:pull/4
$ git checkout pull/4

[shurymury]

@akolarkunnu @amresh-sahu, can you take a look?

[bridgekeeper]

👋 Welcome back shurailine! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@shurymury This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

7902793: Fix IllegalMonitorStateException in JInternalFrameOperatorCloseTest

Reviewed-by: akolarkunnu

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 02: Full - Incremental (e726335)
• 01: Full - Incremental (bc4a2b5)
• 00: Full (9d2c119)

[amresh-sahu]

Not able to run the test due to NPE.

When close event is triggered by calling internalFrameOper.close(); JInternalFrame.doDefaultCloseAction() is called(). This method fires close property change event. Because we are closing the internal frame so this frame is removed from the desktop pane and when it is removed then its parent also set to null in Container.remove() method call.

I tested JInternalFrame add/remove workflow with Oracle's InternalFrameDemo class and It seems me valid. NPE is not a part of Product Bug.

java.lang.NullPointerException
at org.netbeans.jemmy.ClassReference.(ClassReference.java:51)
at org.netbeans.jemmy.EventDispatcher.(EventDispatcher.java:87)
at org.netbeans.jemmy.operators.ComponentOperator.(ComponentOperator.java:195)
at org.netbeans.jemmy.operators.ContainerOperator.(ContainerOperator.java:71)
at org.netbeans.jemmy.operators.WindowOperator.(WindowOperator.java:70)
at org.netbeans.jemmy.util.DefaultVisualizer.makeVisible(DefaultVisualizer.java:211)
at org.netbeans.jemmy.operators.ComponentOperator.makeComponentVisible(ComponentOperator.java:887)
at org.netbeans.jemmy.operators.AbstractButtonOperator.push(AbstractButtonOperator.java:350)
at org.netbeans.jemmy.drivers.windows.DefaultInternalFrameDriver.requestClose(DefaultInternalFrameDriver.java:59)
at org.netbeans.jemmy.operators.JInternalFrameOperator.close(JInternalFrameOperator.java:581)
at org.netbeans.jemmy.operators.JInternalFrameOperatorCloseTest.testClose(JInternalFrameOperatorCloseTest.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:599)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:174)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)

[shurymury]

Thank you, @amresh-sahu, for the analysis. Like we discussed, I can not reproduce this problem locally. But I think I have enough to work on this.

[shurymury]

The exception was actually coming from the finally block where the test attempts to close an internal frame which acts absolutely normally (with field done been set to true). That, probably, means that there is something wrong in InternalFrameOperator.close(). Which is not related to this test, as this test is only supposed to test that waiting happens if the internal windows is not closing.
I have therefore removed internal frame closing at the end. It was unnecessary in the first place, as the test disposes the container window anyway.
The problem of the NPE coming from internal frame closing happening because the internal frame does not have a parent, should still be resolved. @amresh-sahu, can you be so kind file a separate bug on that with all the details you can provide? If you can create a standalone scenario for that, it would be great.

[shurymury]

@amresh-sahu , to make sure, can you run the test with the latest changes?

[shurymury]

As we have discovered with @amresh-sahu , it does not work in his environment.

[amresh-sahu]

Changes look fine and these are working as expected.

[akolarkunnu]

Looks good

[akolarkunnu]

Looks good

[shurymury]

/integrate

[openjdk]

@shurymury Pushed as commit 94612e2.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.