During the migration process from JBoss EAP 6.4 to JBoss EAP 7.0 we stumbled in a SSO authentication issue, in the previous version we used the class: org.jboss.as.web.security.GenericHeaderAuthenticator class
However, we can't use that in JBoss EAP 7.0, what's the solution to replace that?
Related
We are upgrading a Spring Boot App deployed on Wildfly from Spring Boot 2.5.6 to 2.6.2. The majority of the app is working fine. However, we see the following stack trace on several URL's. One example is the CXF page listing web services which worked fine on Spring Boot 2.5.6.
2022-01-12 08:02:08,130 ERROR [org.springframework.boot.web.servlet.support.ErrorPageFilter] (default task-2) Forwarding to error page from request [/webservices] due to exception [HandlerMapping exception not suppressed]: java.lang.IllegalStateException: HandlerMapping exception not suppressed
at org.springframework.web.servlet.handler.HandlerMappingIntrospector.doWithMatchingMappingIgnoringException(HandlerMappingIntrospector.java:220)
at org.springframework.web.servlet.handler.HandlerMappingIntrospector.getCorsConfiguration(HandlerMappingIntrospector.java:161)
at org.springframework.web.filter.CorsFilter.doFilterInternal(CorsFilter.java:86)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
....
Caused by: java.lang.NullPointerException
at io.undertow.servlet#2.0.27.Final//io.undertow.servlet.spec.HttpServletRequestImpl.getHttpServletMapping(HttpServletRequestImpl.java:250)
I set the CXF libraries to be the same at the previous version. I was wondering if people were seeing similar issues and what is the source of the difference.
UPDATE #1
I researched further and found what appears to be come incompatibility between Spring web classes and the implementation within Undertow packaged with Wildfly. I tried several Wildfly version with the following results:
Wildfly 18.0.1 : NullPointerException shown above
Wildfly 23.0.2 : NullPointerException shown above
Wildfly 24.0.1 : no issues
Wildfly 26.0.0 : no issues
Redhat EAP 7.4 : NullPointerException shown above
I further researched by exchanging the Undertow versions under the modules folder.
Wildfly 18.0.1 / Undertow 2.0.27.Final : NullPointerException
Wildfly 23.0.2 / Undertow 2.2.5.Final : NullPointerException
Wildfly 24.0.1 / Undertow 2.2.8.Final : no issues
Wildfly 26.0.0 / Undertow 2.2.14.Final : no issues
Redhat EAP 7.4 / Undertow 2.2.5.Final-redhat-00001 : NullPointerException
If I move undertow files under /modules folder for Wildfly 24.0.1 to Wildfly 23.0.2 or Redhat EAP 7.4, the system deploys and runs with no issues when I access the url.So it appears the issue was addressed in Undertow between 2.2.5 and 2.2.8.
So it appears that our clients are limited on upgrading their systems. Especially our clients who utilize Redhat EAP version, they will have to wait for an update.
UPDATE #2
After looking at the release notes for Undertow, the problem appears to be https://issues.redhat.com/browse/UNDERTOW-1866
I develop a spring boot app (version 2.1.4) but when i tried to deploy on weblogic 12.1.3 i have this error:
I deployed it on a wildfly 17 and it works.
¿any idea who i can solve this?
Thanks
Latest WebLogic 12c only supports Spring 4 (4.2 I think).
Springboot 2.x requires Spring 5
Since WebLogic 12c does not support Spring 5, it does not support Springboot 2.x
But if you figure something out, do let me know :)
1) We are migrating from Jboss 5 to EAP 7.
2) The same code deploys under jboss 5 but throws below error when deploying under EAP7
Can someone help with how we accomplish
jboss-service.xml equivalent in EAP?
Thanks for your help.
There were many changes in between JBoss 5 and the latest EAP. You'll have to take a look at jboss-service.xml to see what it's trying to accomplish (this is generally just MBean configuration), there will be a new way to do this.
There are lots changes between EAP 5 and EAP 7. JBoss-service .xml is no longer valid. You will have to configure using standalone or domain.xml.
If you need messaging or clustering support then you will have to choose Ha or full or Full-ha profile.
I'm working to upgrade JDK for a Web app from 1.4 to 1.7 and Websphere Application server 6.1 to 8.5 (WAS 6.1 to 8.5).
The application is built using JSF 1.2. My question is does JSF 1.2 is compatible with Java 1.7 or does it require to upgrade JSF 1.2 to 2.0? Any pointers in this relation is most valuable.
Thanks in advance.
JSF 1.2 is compitible with java 1.6.
You can change your version of java in a
Project>Build Path>Configure then select Java to change it
If you want to use java 7, then you need to move on JSF 2.0
I had issues with JSF 1.2 and JDK > 7.0.21
I do not remember the exact cause, but that was a known issue and never fixed.
You can use JSF 1.2 with WAS 8.5, you will need to change default JSF via application options Applications > Application Types > WebSphere enterprise applications > application_name > JSP and JSF options and switch to Sun Reference Implementation 1.2.
For more details see Configuring JavaServer Faces implementation
We need to profile spring based web application running on JBOSS EAP 6 using some tool similar to Spring Insight.
Spring Insight help developers to understand and visualize the behavior of web application, however it doesn't support JBOSS EAP 6.
Maybe AppDynamics (http://www.appdynamics.com/) could be an alternative for you guys.