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

Upgrade from 1.8.12 to 1.8.13 Breaks Deployment of War to WebSphere #718

Open
willweyant opened this issue Sep 26, 2023 · 0 comments
Open
Assignees

Comments

@willweyant
Copy link

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!

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

No branches or pull requests

2 participants