| Re: [glassfish-dev] GlassFish Fails with Arquillian |
_______________________________________________So by sheer amount of random trial and error I was able to reduce the instances of this happening: https://github.com/eclipse-ee4j/cargotracker/commit/733884ef435290113a70958fd7922d34a2b83362. It is still happening intermittently. It looks like some kind of low level file locking and/or permissions issue. I'll keep trying but honestly I could use some real help.
I would still be very keen on moving to GlassFish Embedded in a way that's proper for an Eclipse Foundation project if that's possible instead. This problem can be someone else's headache to solve.
On 3/24/2025 11:08 AM, Reza Rahman wrote:
Also tried the following, it works fine:
& "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
I did notice that if GlassFish was not shut down completely, I get this:
Waiting finished after 60,001 ms.
No response from the Domain Administration Server (domain1) after 60 seconds.
The command is either taking too long to complete or the server has failed.
Please see the server log files for command status.
Please start with the --verbose option in order to see early messages. No response from the Domain Administration Server (domain1) after 60 seconds.
The command is either taking too long to complete or the server has failed.
Please see the server log files for command status.
Please start with the --verbose option in order to see early messages.I'll try to pin down under what exact conditions this happens. It's not easy to reproduce. This is easier to reproduce manually:
There is a process already using the admin port 4,848 -- it probably is another instance of a GlassFish server.
On 3/24/2025 10:44 AM, Reza Rahman wrote:
This is what I did:
C:\GitHub\cargotracker> cd "C:\Program Files\Eclipse Adoptium\jdk-17.0.8.101-hotspot\bin\"
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
This is the output I get:
Waiting finished after 48,817 ms.
Successfully started the domain : domain1
domain Location: C:\GitHub\cargotracker\target\glassfish7\glassfish\domains\domain1
Log File: C:\GitHub\cargotracker\target\glassfish7\glassfish\domains\domain1\logs\server.log
Admin Port: 4,848This still could be an issue, but at least the above works.
On 3/24/2025 6:17 AM, Arjan Tijms via glassfish-dev 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 ArquillianHi,
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
_______________________________________________ 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