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

Bug Report: Seems Payara Micro 6.2024.6 (but not Server) is broken (to be investigated where exactly) comparing to Payara Micro 6.2024.5/FISH-9110 #6779

Open
AndrewG10i opened this issue Jun 21, 2024 · 7 comments
Assignees
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev

Comments

@AndrewG10i
Copy link

Brief Summary

After upgrading Payara Micro 6.2024.5 to 6.2024.6 our app gets some weird behavior. We currently do not have reproducer, as no specific error is logged in the error log at the moment error occurs. Just after 4th of 5th open page app stops responding properly to page navigation and the shown below error start appearing.

It seems to me that something is happening with User Session, as user gets logged out or not able to navigate to other pages or navigate to the home page.

Reverting back to Payara Micro 6.2024.5 resolves the issue. Also app works fine on Payara Server (full) 6.2024.6, issue only appears when deployed on Payara Micro 6.2024.6.

At this moment reporting this issues as is, I will try to provide more details in case we are able to get minimal reproducer, but cannot promise that it will be quick due to tough schedule.

Expected Outcome

No error.

Current Outcome

After navigating over few pages user may get logged out or pages are not open and error log start reporting some weird errors like:

[2024-06-21 17:14:40] [WARNING] [com.sun.faces.lifecycle.InvokeApplicationPhase execute]
 Cannot invoke "java.util.Map.put(Object, Object)" because "this.innerMap" is null
java.lang.NullPointerException: Cannot invoke "java.util.Map.put(Object, Object)" because "this.innerMap" is null
	at com.sun.faces.context.flash.ELFlash$PreviousNextFlashInfoManager.initializeBaseCase(ELFlash.java:1226)
	at com.sun.faces.context.flash.ELFlash.getCurrentFlashManager(ELFlash.java:1117)
	at com.sun.faces.context.flash.ELFlash.loggingGetPhaseMapForWriting(ELFlash.java:802)
	at com.sun.faces.context.flash.ELFlash.setKeepMessages(ELFlash.java:318)
	at com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:235)
	at com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:200)
	at com.sun.faces.application.ActionListenerImpl.invokeNavigationHandling(ActionListenerImpl.java:93)
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:62)
	at jakarta.faces.component.UIViewAction.broadcast(UIViewAction.java:506)
	at jakarta.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:858)
	at jakarta.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1332)
	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:56)
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:72)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:159)
	at jakarta.faces.webapp.FacesServlet.executeLifecyle(FacesServlet.java:691)
	at jakarta.faces.webapp.FacesServlet.service(FacesServlet.java:449)
	at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1554)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:331)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211)
	at org.glassfish.tyrus.servlet.TyrusServletFilter.doFilter(TyrusServletFilter.java:83)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:253)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211
        ...

Reproducer

Not availbale at this moment - we will try to provide reproducer once have more time for troubleshooting.

Operating System

Windows and Linux - same behaviour

JDK Version

Zulu JDK 17 - latest version availbale

Payara Distribution

Payara Micro

@AndrewG10i AndrewG10i added Status: Open Issue has been triaged by the front-line engineers and is being worked on verification Type: Bug Label issue as a bug defect labels Jun 21, 2024
@felixif
Copy link

felixif commented Jun 26, 2024

Hello @AndrewG10i,

Thank you for your bug report! Unfortunately, without a minimal reproducer, I cannot verify that the issue occurs and escalate it to be solved. If you have time to provide a reproducer, I would be happy to assist.

Best regards,
Felix

@MeroRai MeroRai added Status: Pending Waiting on the issue requester to give more details or share a reproducer and removed Status: Open Issue has been triaged by the front-line engineers and is being worked on verification labels Jul 17, 2024
@AndrewG10i
Copy link
Author

The same issue repeats with Payara Micro 6.2024.7 as well (but still Payara Micro 6.2024.5 works fine). I am planning to work on reproducer during next 2-3 weeks. Thanks!

@github-actions github-actions bot added Status: Abandoned User has not supplied reproducers for bug report, soon to be closed if user doesn’t come back and removed Type: Bug Label issue as a bug defect Status: Pending Waiting on the issue requester to give more details or share a reproducer labels Jul 24, 2024
Copy link

Greetings,
It's been more than 5 days since we requested more information or an update from you on the details of this issue. Could you provide an update soon, please?
We're afraid that if we do not receive an update, we'll have to close this issue due to inactivity.

@AndrewG10i
Copy link
Author

AndrewG10i commented Jul 24, 2024

Hello!

Reproducer was published here:
https://github.com/AndrewG10i/jakartaFacesTestApp/

Steps to reproduce the issue:

  1. Click on any of the availbale records
  2. On the new page click the Delete button
  3. You can see errors appearing in console (see the video recording demonstrating the issue. Particularly at the timing 1:43 - the exception posted in the initial post is shown)

NOTE: Issue reproduces only on the Payara Micro 6.2024.6 and 6.2024.7. Payara Micro 6.2024.5 and below, and Payara Server 6.2024.5,6,7 - all work fine.

@felixif felixif added Status: Open Issue has been triaged by the front-line engineers and is being worked on verification and removed Status: Abandoned User has not supplied reproducers for bug report, soon to be closed if user doesn’t come back labels Jul 29, 2024
@felixif
Copy link

felixif commented Jul 29, 2024

Hello @AndrewG10i,

Thank you very much for the excellent reproducer! I was able to quickly see the problem after testing across the three versions that you mentioned above. I have raised an internal issue, codename FISH-9110, and our Platform Development team will analyse and fix the bug.

Thank you very much for your report!

Best regards,
Felix

@felixif felixif added Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev and removed Status: Open Issue has been triaged by the front-line engineers and is being worked on verification labels Jul 29, 2024
@felixif felixif changed the title Bug Report: Seems Payara Micro 6.2024.6 (but not Server) is broken (to be investigated where exactly) comparing to Payara Micro 6.2024.5 Bug Report: Seems Payara Micro 6.2024.6 (but not Server) is broken (to be investigated where exactly) comparing to Payara Micro 6.2024.5/FISH-9110 Jul 30, 2024
@AndrewG10i
Copy link
Author

AndrewG10i commented Oct 10, 2024

Hello Payara team! Seem this issue is still present even in the recently released version 6.2024.10. Any chances to have it fixed soon as well? As we still forced to stay with 6.2024.5 as result not able to try & test your latest releases and help with stabilizing Enterprise version. ;) Thanks in advance!

@AndrewG10i
Copy link
Author

Hello Payara team! Any updates here? Can you pls provide any insights so we try to collaborate on the fix for this issue? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev
Projects
None yet
Development

No branches or pull requests

3 participants