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

Inclusion of Soteria leads to warnings on module deployment #2266

Closed
jo-ka opened this issue Jan 15, 2018 · 7 comments
Closed

Inclusion of Soteria leads to warnings on module deployment #2266

jo-ka opened this issue Jan 15, 2018 · 7 comments
Labels
Type: Bug Label issue as a bug defect
Milestone

Comments

@jo-ka
Copy link

jo-ka commented Jan 15, 2018

Description


With the inclusion of Soteria in Payara 4.1.2.174, there are warning log messages concerning Soteria implementation classes on every module deployment.

Expected Outcome

There should be no warnings, especially as I didn't (mis-)configure anything related to Soteria but used a stock Payara installation.

Current Outcome

These two warnings appear (which look all the more menacing due to the coloured font of the "WARNING" in the middle of the line):

  • Warning: The following warnings have been detected: WARNING: Parameter interceptedBean of type javax.enterprise.inject.spi.Bean<?> from private javax.enterprise.inject.spi.Bean<?> org.glassfish.soteria.cdi.RememberMeInterceptor.interceptedBean is not resolvable to a concrete type.
  • Warning: The following warnings have been detected: WARNING: Parameter interceptedBean of type javax.enterprise.inject.spi.Bean<?> from private javax.enterprise.inject.spi.Bean<?> org.glassfish.soteria.cdi.LoginToContinueInterceptor.interceptedBean is not resolvable to a concrete type.

Steps to reproduce

Deploy any module.

Context

When searching for the log message, I found at least two different recent posts that exhibit the same behaviour: https://github.com/javaserverfaces/mojarra/issues/4264 and https://stackoverflow.com/questions/48074073/how-to-use-omnifaces-eager-annotation-with-primefaces.

As the potential consequences don't seem to be so dire from the log messages as long as one does not use Soteria in the first place, it would be fine if Soteria could just be completely disabled. The release notes say it's optional, so I assume this would be possible somehow, maybe someone could tell me how?

Environment

  • Payara Version: 4.1.2.174
  • Edition: Full
  • JDK Version: 8u131 OpenJDK
  • Operating System: Debian Linux
  • Database: PostgreSQL
@michaelranaldo michaelranaldo added Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect labels Jan 15, 2018
@michaelranaldo
Copy link
Contributor

Hi @jo-ka,

Thanks for reporting this, created internal issue PAYARA-2364.

@smillidge
Copy link
Contributor

Fixed by #2407

@fturizo fturizo removed the Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev label Feb 22, 2018
@HeinBloed
Copy link

Thanks guys!

@OndroMih OndroMih added this to the Payara 5.181 milestone Mar 20, 2018
@AllenConquest
Copy link

Is this fix available in Payara 4 ?

@smillidge
Copy link
Contributor

There are no more Payara 4 community releases. It will be backported into customer releases of 4.x which have a 10 year support lifecycle.

@AllenConquest
Copy link

I believe our company has a support contract with Payara, would that entitle us to customer releases?

@smillidge
Copy link
Contributor

smillidge commented Nov 9, 2018

Yes raise a ticket on support.payara.fish

Or you can download 4.x later releases and patch releases with your nexus account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Label issue as a bug defect
Projects
None yet
Development

No branches or pull requests

7 participants