Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display a warning when Hazelcast configuration does not contain Jetty session serializer #6118

Closed
olamy opened this issue Mar 30, 2021 · 0 comments · Fixed by #6321
Closed
Assignees

Comments

@olamy
Copy link
Member

olamy commented Mar 30, 2021

It's possible to configure Hazelcast Session Manager with a single hazelcast.xml file but the Jetty session manager needs to have the serializer configured as is:

  <serialization>
    <serializers>
      <serializer type-class="org.eclipse.jetty.server.session.SessionData"
                  class-name="org.eclipse.jetty.hazelcast.session.SessionDataSerializer" />
    </serializers>
  </serialization> 

If it's not configured we should display a warning in the logs telling the user the Hazelcast Jetty session integration will not work

@olamy olamy self-assigned this Mar 30, 2021
janbartel added a commit that referenced this issue May 25, 2021
Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel added a commit that referenced this issue May 28, 2021
janbartel added a commit that referenced this issue Jun 2, 2021
…er (#6321)

* Issue #6118 Warn if hazelcast cfg file is missing SessionDataSerializer

Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel added a commit that referenced this issue Jun 2, 2021
…er (#6321)

* Issue #6118 Warn if hazelcast cfg file is missing SessionDataSerializer

Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel added a commit that referenced this issue Jun 3, 2021
…er (#6321) (#6345)

* Issue #6118 Warn if hazelcast cfg file is missing SessionDataSerializer

Signed-off-by: Jan Bartel <janb@webtide.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@olamy and others