Re: [glassfish-dev] GlassFish Fails with Arquillian

[Reza Rahman <reza_rahman@xxxxxxxx>]

Good idea. I’ll try that later today. Hopefully it’ll help uncover the root cause. I’ll post back my findings.

As a side note, could I switch to GlassFish embedded now? That’s what it was originally in the Sun/Oracle days before I had to switch to Payara. If not, no big deal. I’ll still try to get to the bottom of this either way.

---

From: glassfish-dev <glassfish-dev-bounces@xxxxxxxxxxx> on behalf of Ondro Mihályi via glassfish-dev <glassfish-dev@xxxxxxxxxxx>
Sent: Monday, March 24, 2025 8:51 AM
To: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Cc: Ondro Mihályi <mihalyi@xxxxxxxxxxx>; glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>; cargotracker developer discussions <cargotracker-dev@xxxxxxxxxxx>
Subject: Re: [glassfish-dev] GlassFish Fails with Arquillian

 

By the way, Reza, you should get the same error with Payara if you used the payara-managed container and not the Payara Micro container (arquillian-payara-micro-managed). 

The payara-managed container starts the server in exactly the same way as the OmniFish glassfish managed container - finds the path to the Java program from the Payara/GlassFish configuration or just runs "java" and expects it on the path. However, the Payara Micro container uses the same Java executable used by maven. This hints that maybe really the default Java is not properly configured on your system.

Ondro

On Mon, Mar 24, 2025 at 12:23 PM Ondro Mihályi <mihalyi@xxxxxxxxxxx> wrote:

Reza, is the "java" executable in the PATH?

When I remove it from PATH, then I get a similar CIRCULAR_REFERENCE exception with the JBoss Aruiallian connector:

Caused by: [CIRCULAR REFERENCE: org.jboss.arquillian.container.spi.client.container.LifecycleException: Unable to execute [java, -jar, /home/ondro/workspaces/OmniFish/sample-apps/cargotracker/target/glassfish7/glassfish/modules/admin-cli.jar, start-domain, -t]]
Caused by: java.io.IOException: Cannot run program "java": error=2, No such file or directory
        at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1170)
        at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1089)
        at org.jboss.arquillian.container.glassfish.managed_6.GlassFishServerControl.executeAdminCommand(GlassFishServerControl.java:154)
        ... 46 more
Caused by: java.io.IOException: error=2, No such file or directory
        at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
        at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:295)
        at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:225)
        at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1126)

On Mon, Mar 24, 2025 at 11:17 AM Arjan Tijms <arjan.tijms@xxxxxxxxxxx> wrote:

Hi,

It looks like a rather basic thing:

"org.jboss.arquillian.container.spi.client.container.LifecycleException: Unable to execute [C:\Program Files\Eclipse Adoptium\jdk-17.0.8.101-hotspot\bin\java.exe, -jar, C:\GitHub\cargotracker\target\glassfish7\glassfish\modules\admin-cli.jar, start-domain, -t]"

Can you double check if the JDK is indeed at that location?

Kind regards,

Arjan Tijms

On Mon, 24 Mar 2025 at 09:22, Ondro Mihályi via glassfish-dev <glassfish-dev@xxxxxxxxxxx> wrote:

Can you try if it also happens on Linux/Mac? When I run the BookingServiceTest test with "maven test -Pglassfish" on master branch on Linux, it works.

I suspect that the problem is only on Windows, can you confirm it, Reza?

Ondro

On Mon, Mar 24, 2025 at 12:05 AM Reza Rahman via glassfish-dev <glassfish-dev@xxxxxxxxxxx> wrote:

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.

---

From: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Sent: Sunday, March 23, 2025 6:10 PM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Cc: Reza Rahman <reza_rahman@xxxxxxxx>; cargotracker developer discussions <cargotracker-dev@xxxxxxxxxxx>
Subject: Re: [glassfish-dev] GlassFish Fails with Arquillian

 

Hi,

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:

 <dependency>
          <groupId>org.jboss.arquillian.container</groupId>
          <artifactId>arquillian-glassfish-managed-6</artifactId>
          <version>1.0.0.Alpha1</version>
          <scope>test</scope>
</dependency>

Maybe that could explain some?

You could try with:

<dependency>
            <groupId>org.omnifaces.arquillian</groupId>
            <artifactId>arquillian-glassfish-server-managed</artifactId>
            <version>1.7</version>
            <scope>test</scope>
</dependency>

Kind regards,

Arjan Tijms

On Sun, 23 Mar 2025 at 20:47, Reza Rahman via glassfish-dev <glassfish-dev@xxxxxxxxxxx> wrote:

Hello,

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.

Thanks,

Reza
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev

_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev

_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev