Hi, I’m on 6.4.0 version, I’ve installed with no pain all distribution wars on oracle weblogic 12c.
I properly changed every configuration file (flowable-default.properties) inside each war, pointing to mysql as database and then i made some changes to redirection parameters, which their default values pointed to localhost on port 8080 instead of <my_remote_ip>:7001 (weblogic server default port).
So database is generated and filled up correctly, tables which refer to user access are filled correctly.
When I try to access to remote resource
<my_remote_server_ip>:7001/flowable-modeler
I get a redirection like this:
<my_remote_server_ip>:7001/flowable-idm/#/login?redirectOnAuthSuccess=true&redirectUrl=http://<my_remote_serve>_ip>:7001/flowable-modeler
with login prompt, then entering correct credentials server comes back again to login page.
Have I mess something during configuration step? Or is simply uncompliant with oracle Weblogic Server?
Any help would by grately appreciated.
Hi ,
I am on 6.4.0 version & using Tomcat application server. Our services has a requirement moving to Oracle weblogic 12c platform. When the containers (flowable-admin,flowable-idm,flowable-modeler,flowable-rest & flowable-task) are deployed in weblogic (after changing to weblogic port in each properties files) I am running into below exception
org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘httpPutFormContentFilter’ defined in class path resource [org/springframework/boot/autoconfigure/web/servlet/WebMvcAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.web.servlet.filter.OrderedHttpPutFormContentFilter]: Factory method ‘httpPutFormContentFilter’ threw exception; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.fasterxml.jackson.datatype.jsr310.JavaTimeModule]: Constructor threw exception; nested exception is java.lang.IllegalAccessError: tried to access method com.fasterxml.jackson.databind.ser.std.StdSerializer.(Ljava/lang/Class;)V from class com.fasterxml.jackson.datatype.jsr310.JavaTimeModule
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:155)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:544)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:780)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:412)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:333)
at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:157)
at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:137)
After a few trial & error i could find the list of packages / classes that are in conflict with weblogic libraries & jars. Solution to overcome these exceptions would to explicitly mention weblogic class cloader where the classes should be loaded from in wls:prefer-application-packages ( weblogic.xml)
I was running into same issue where every time I logged on it kept sending me back to login when deployed to weblogic (tomcat worked fine:. Spent good amount of time trying to debug and figured I’d share what I did to fix since I had trouble finding any help.I needed the following added to weblogics config.xml security-configuration: