You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am curious if anyone can point me to a solution for an issue we are facing after upgrading from 1.8.12 to 1.8.13. With no other changes, our application no longer deploys to WebSphere 9 with Java 8. Running as a Spring Boot application still works fine. The error that I see in the WebSphere logs indicates the following issues:
The org.springframework.web.SpringServletContainerInitializer@ ServletContainerInitializer, located in the following application , produced the following error while invoking the onStartup method: java.servlet.ServletException: Failed to instantiate WebApplicationInitializer class
Spring context lookup failed, skipping spring component provider initialization
As a result of Spring setup issues, FF4jApiApplicationJersey2x ApiConfig is null, causing a NullPointerException on line 74 of FF4jApiApplicationJersey2x.
Unfortunately, I can't post any code. We are using a combination of web.xml and annotation configuration.
Due to the minor version update, I wasn't expecting any issues. We are hoping to move to 1.9 to resolve some of the security issues.
Thank you in advance for any help you can provide!
The text was updated successfully, but these errors were encountered:
I am curious if anyone can point me to a solution for an issue we are facing after upgrading from 1.8.12 to 1.8.13. With no other changes, our application no longer deploys to WebSphere 9 with Java 8. Running as a Spring Boot application still works fine. The error that I see in the WebSphere logs indicates the following issues:
As a result of Spring setup issues, FF4jApiApplicationJersey2x ApiConfig is null, causing a NullPointerException on line 74 of FF4jApiApplicationJersey2x.
Unfortunately, I can't post any code. We are using a combination of web.xml and annotation configuration.
Due to the minor version update, I wasn't expecting any issues. We are hoping to move to 1.9 to resolve some of the security issues.
Thank you in advance for any help you can provide!
The text was updated successfully, but these errors were encountered: