Re: [glassfish-dev] GlassFish Fails with Arquillian

[Arjan Tijms <arjan.tijms@xxxxxxxxxxx>]

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