Java Application Window Crashing issue

[Akshay_MMC]

Hi Everyone,

I am currently working on a Java application to automate one of our processes. We are using Java spy mode with JAB enabled to identify elements. While the highlighting of elements functions correctly, the Java window unexpectedly crashes during the process execution.

I am seeking assistance from the community to help resolve this issue. We are working with Blue Prism version 7.1.1, and I would be happy to discuss this matter in more detail with anyone who can assist.

Thank you!
@devneetmohanty07, could you please help with this?

#javaapplicationcrashing #javacrash #blueprism

[steven.boggs]

Hi Akshay,

What is the error message thrown when Java/the Java window crashes? Have you reviewed the Event Viewer logs from around the time of the error to determine if this could be related to an OOM event, or something else? Also, can you provide more details about the Java application you're attempting to automate and the version of Java in use in the environment?

[Akshay_MMC]

Hi Steven,

Thank you for your reply regarding the Java application crash.

To address your questions:

1. Error Message: There isn't a specific error message generated when Java crashes. The error we observed in the logs is actually from the subsequent stage of the code, specifically during the navigation and reading process. It states, "No elements match with query terms," which appears to be a straightforward error that occurs when the Java window is not present.

2. Event Viewer Logs: I have reviewed the Event Viewer logs from around the time of the crash. There are no indications of an Out of Memory (OOM) event, which could suggest that the application is consuming more memory than is available. However, I will need to analyze the logs in more detail to confirm this and check for any other potential issues.

3. Application Details: The Java application I am working to automate is related to insurance, where it records entries and manages data concerning claims, renewals, settlements, and more. We are currently using Java version 1.8.431 (Runtime Environment 8.0.4310.31-R1) along with Blue Prism version 7.1.1 in our environment.

4. I observed that Java crashes immediately after the dynamic wait stage, where I am checking the state of the checkbox using the "Checked" parameter with the "Check Attribute" action. However, when I substitute this wait stage with a Read and Decision stage, everything works as expected. I will keep testing additional cases to confirm the results.

Please let me know if you need any more information or if there are specific areas you would like me to focus on.

[rabbanir]

Hi Akshay,

Are you using Match Index on your elements by any chance? when we were on 6.10 we were also getting intermittent crashes, turns out it was an issue with match index causing it. Luckily we upgraded to 7.1.2 which resolved the issue; you can see here in the 'application modeler' section:
Blue Prism 7.1.2: December 2022

If this is the case for you then your best bet is to upgrade to a later version if you can, otherwise you will have to disable the match index attribute on all your java elements which significantly increases the time taken to highlight the element.

[Akshay_MMC]

@steven.boggs 
Hi Steven, 
Please refer below event log, Looks like dll cousing this issue..

Log Name: Application
Source: Application Error
Date: 3/4/2025 9:54:45 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: IEDBLMVDIX00427.emea.mrshmc.com
Description:
Faulting application name: javaw.exe, version: 8.0.4310.31, time stamp: 0x66fab3f8
Faulting module name: jvm.dll, version: 8.0.4310.31, time stamp: 0x66fab2a9
Exception code: 0xc0000005
Fault offset: 0x0016edb1
Faulting process id: 0x2858
Faulting application start time: 0x01db8ceaaaefc8bb
Faulting application path: C:\Program Files (x86)\Java\jre1.8.0_431\bin\javaw.exe
Faulting module path: C:\Program Files (x86)\Java\jre1.8.0_431\bin\client\jvm.dll
Report Id: 02d63d39-6b14-44a8-a927-ea6e980a8998
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2025-03-04T09:54:45.1427726Z" />
<EventRecordID>153663</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>IEDBLMVDIX00427.emea.mrshmc.com</Computer>
<Security />
</System>
<EventData>
<Data>javaw.exe</Data>
<Data>8.0.4310.31</Data>
<Data>66fab3f8</Data>
<Data>jvm.dll</Data>
<Data>8.0.4310.31</Data>
<Data>66fab2a9</Data>
<Data>c0000005</Data>
<Data>0016edb1</Data>
<Data>2858</Data>
<Data>01db8ceaaaefc8bb</Data>
<Data>C:\Program Files (x86)\Java\jre1.8.0_431\bin\javaw.exe</Data>
<Data>C:\Program Files (x86)\Java\jre1.8.0_431\bin\client\jvm.dll</Data>
<Data>02d63d39-6b14-44a8-a927-ea6e980a8998</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[steven.boggs]

Further to what @rabbanir mentioned above, your version of BPE (v7.1.1) is included in those affected by [BPE] BP-10711 - Java applications crash intermittently during automation. I'd suggest testing this with a newer version of BPE (i.e. spin up a test environment with BPE v7.1.2 or later) where the fix to this known issue exists to determine if this is indeed the source of the problem. Alternately, try implementing the stated workaround in the BP-10711 documentation related to match index and/or region mode for this portion of the Process.

[Akshay_MMC]

Hi Team,
Thank you for your valuable suggestions.
I’m happy to share that we have successfully resolved the issue for now. The solution involved removing the match index attribute, which was causing complications. Additionally, we implemented some static wait times to ensure smoother processing and replaced the dynamic wait stage with a more effective read and decision stage. This adjustment has significantly improved the overall functionality. Thank you for your support!