Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [messaging-dev] [openmq-dev] Releasing Messaging 3.1
  • From: Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>
  • Date: Wed, 2 Mar 2022 15:34:54 +0000
  • Accept-language: en-GB, sk-SK, en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=f7bC7Ejj4BygMgwmLXGDt35sqvz7ZFc2H2YFA9o3F+w=; b=Ux2m+VRvHUfyBT8sy+pjStdHaQ2vYa1Tqh+5eBlxJ7qlzCwYu6j1HybNufuJKyA3f4zgl/O2Kmk2i1EX49j5dQ8AtYy1iPoKgyY135fTk2BxZQyfjmO+7iSWoFExl2GcX5YUP/PqvwH4ljAXoKxvpsmyvFpXRCTVRAHivvA22i3Hdv6E3QEizFJDE5sj+fBbd0QvWuiYps1a2d17jiHs0vAtjucaK5dxpC9nx+MdDT3BfG/s0sq4FUCqWmSugmbEdASSkizL2JIynAezk4EZkxOs3PjGqkKD8gqH7G2MT5Xgyp+BpOgtTQ8LprXa5NKoCuvFuhGJg+5F96hh6bn7hw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=RosS8bt0p/slAjmgDjor32XVQO8PEgh7/U6smXAFYONAI08rHfz8nwX+T20w0JWs3GwqN05N+TdfP/6tuHnmk+J1mMjgoC7UmRvk6aF4WKfIItSGGcfGitQ/EtQI+RXupeblIkUWc71ULmACRbY3p+KI98rwbAEnAR++K9GNu/Io/3DZgCQ2zLLmlZKkxjyP1JtPa/+MwagujDYAEdaWWYA9XMeN9Zq+ThCGpogPbEOYpU2YwA/+MEh0MvDI0q19AZh0dS07Bd0IdlGJiOsXCdqZ1CtE2nvt/YMI6VqM2bTEIUmF1VK6CwH87OCIMtlAFirnI8o4yJ0Tfx4VQgUW5g==
  • Delivered-to: messaging-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Suggested_attachment_session_id: 23746ef5-d9bc-2bd9-b215-820914407e81
  • Thread-index: AQHYLh1fDIVSyk9nxkSdHB8Bk1a6tqyr/neAgAAyYICAAAAjZQ==
  • Thread-topic: [messaging-dev] [openmq-dev] Releasing Messaging 3.1

Hi, Piotrek, thank you very much for your update (and corrections to my email).

I see that the staged TCK has been updated and OpenMQ 6.3.0-M3 now passes the TCK with the latest Jenkins job run

Once the RC is out, do you want to submit a certification request issue against the Messaging repo? Similar to what I did for GlassFish:

In order to pass the standalone Messaging certification, it's enough to run the standalone Messaging TCK against it, which only contains Java SE tests. The EE portion of the tests are still executed within the Jakarta Platform TCK as the Messaging tests haven't been moved to the Messaging project yet. They will be executed against Jakarta EE 10 CI (e.g. GlassFish 7).

Kind regards,

Ondrej Mihályi

Senior Payara Service Engineer
Payara - Supported Enterprise Software for Jakarta EE and MicroProfile Applications
US: +1 415 523 0175 | UK: +44 207 754 0481


Payara is a proud recipient of the prestigious Queen's Award for Enterprise: International Trade 2021

Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal

VAT: PT 515158674 | | info@xxxxxxxxxxx | @Payara_Fish

---------- Forwarded message ---------
From: Piotr Żygieło
Date: st 2. 3. 2022 o 13:02
Subject: Re: [messaging-dev] [openmq-dev] Releasing Messaging 3.1
To: openmq developer discussions <openmq-dev@xxxxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>, EE4J Messaging project developer discussions <messaging-dev@xxxxxxxxxxx>

On Wed, 2 Mar 2022 at 12:09, Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote:
> OpenMQ
> Upgraded Messaging to 3.1 (
> this should pass the signature tests
> I think that the JMS metadata still needs to be updated for ConnectionMetaData (I think in the ConnectionMetaDataAdapter)

It was updated in above PR 1398, and is included in M3 build.

> this should then pass all the metadata tests

It does indeed:
the only failure was for signatures, as the TCK used:

*** Name:
*** Bundle Copied to URL:
*** Date and size: date: 2022-03-01 04:25:22.000000000 +0000, size(b):
14166201        ***
*** SHA256SUM: 0f3fc1ac079b495e06e56a68df377f1d91274dcb33bf4239e3abd9163d1dd73d

had no signatures updated yet.

> A new version of OpenMQ should be released to act as a CI for Messaging

I plan to do RC shortly. I suppose it will be almost identical to the
M3, but at this moment I'm not sure.

> Currently, the only role of GlassFish is to act as the CI because I think that the TCK Jenkins job runs against the OpenMQ bundled in GlassFish. If we can pass the TCK with plain OpenMQ, then we don't need GlassFish for releasing Messaging 3.1

I think for OpenMQ to be tested for CI - it's fine to pass 904 standalone tests.
I don't know if that's ok for Messaging Spec to have 2k+ EE tests
skipped. Maybe it is.

> Needs to upgrade OpenMQ after a new OpenMQ version is released

The latest OpenMQ with Messaging 3.1 has been integrated into GF

messaging-dev mailing list
To unsubscribe from this list, visit

Back to the top