Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Concurrency TCK without remote EJB, javax.rmi.RemoteException

On 6/28/22 1:42 PM, Scott Stark wrote:
I have create a fork of the concurrency project and update the tck to only use local EJBs and even removed use of javax.rmi.RemoteException:

I have build the current glassfish repo and run theĀ appserver/tests/tck/concurrency project against a build of this version of the concurrency TCK. It is showing no errors when run with SE 17. The PR for this update is here:

I'll fork the Platform TCK CI Concurrency test job to run with + and see what that shows.


I'm not sure how to test this against a web profile configuration of glassfish. Can that be done from the appserver/tests/tck/concurrency project?

jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top