C:\GitHub\cargotracker> cd "C:\Program Files\Eclipse
Adoptium\jdk-17.0.8.101-hotspot\bin\"
I wonder if it would help to copy the jdk-17.0.8.101-hotspot folder to c:\ in case the spaces in the path are causing trouble. And set the environment/path to point to new (no spaces) Java location.
When I try with the OmniFish plugin, I get a slightly
different error with the same overall symptoms. The
stack trace is attached.
On 3/23/2025 6:36 PM, Reza Rahman wrote:
Thanks very much for taking a look. I
can try the OmniFish plugin as a test.
However, I cannot use it in the project
in relation to GlassFish. I must use something in
the GlassFish or Arquillian domain instead. I’ve
already checked with the EMO on this. My hope would
be that either the Arquillian plugin is properly
maintained or a plugin is created within the
GlassFish project. Alternatively, I would not mind
adding support for an OmniFish branded runtime.
That’s also something that the EMO has suggested.
I haven't tried anything yet, but from
a cursory glance at master the first thing that
stands out is that for GlassFish an alpha version of
the unmaintained JBoss Arquillian connector is used,
that was only suited for GlassFish 6:
The Cargo Tracker project (https://github.com/eclipse-ee4j/cargotracker)
has tried to support GlassFish but once again I am
running into seeming
stability issues. While running tests with
Arquillian, the attached
issue now suddenly crops up. I have absolutely no
idea what is going on.
Honestly, this sort of thing never happens with
Payara or Liberty, which
are the two other runtimes Cargo Tracker supports.
Is there someone here that can help? Otherwise I
will remove GlassFish
support from Cargo Tracker for now.