payara/Payara

Bug Report: Deployment Groups dont apply changes to jndi jdbc not correct

Closed this issue · 1 comments

nikogillen commented

Brief Summary

We have a clustered environment with 1 master and 4 nodes.
All nodes are ssh type.
Each node has 4 instances. All instances are referencing a master configuration.
These are managed in deployment groups the following way:

  1. master_dg
    • dg01
      • node01_instance01
      • node02_instance01
      • node03_instance01
      • node04_instance01
    • dg02
      • node01_instance02
      • node02_instance02
      • node03_instance02
      • node04_instance02
    • dg03
      • node01_instance03
      • node02_instance03
      • node03_instance03
      • node04_instance03
    • dg04
      • node01_instance04
      • node02_instance04
      • node03_instance04
      • node04_instance04

These deployment groups are selected as the target for deployed applications, jdbc and jndi resources.

We expect that changes are taking effect to all slaves of a group.
Instances are not marked to restart, either does a restart have any effect.
The only way to solve this problem is to remove all target and to reassign them.

This behavior is very annoying, as there is no indication that the configuration is out of sync again.
Affected versions are at least 5.61.0 and 6.16.0

Expected Outcome

Changes of properties should be synced to all targets.

Current Outcome

Changes of properties are not synced to targets either does a restart fix this issue. The only workaround that works is to reassign the targets.

Reproducer

Operating System

Oracle Linux 8/9

JDK Version

OracleJDK11, OpenJDK17, Oracle GraalVM21, Payara 5.61.0, 6.16.0

Payara Distribution

Payara Server Full Profile

artur-mal commented

Greetings @nikogillen

We’re sorry, but the release you have reported this issue from is an official Payara Enterprise build, and its support is covered through an active Payara Enterprise subscription.

Can you confirm that you either:

  • Belong to an organization that has an active Payara Enterprise subscription? If so, please contact one of the account holders of your subscription to raise this request via the official support channels.
  • Received the build through an organization that has an active Payara Enterprise subscription that re-distributes the build to you? If so, please contact them to receive support since all requests must come from companies that hold active accounts.

If none of the above applies to your case, I’m afraid that you’re in violation of the Enterprise EULA, and I must request that you stop using this binary immediately and instead use the latest Payara Community release 6.2024.8.

After this, you are free to verify if this issue is present on the Community build so that we can proceed with investigating your report as usual. If this is the case, please raise a new issue with these details.

We’ll proceed to close this issue.