weblogic | Chef cookbook for installing and managing weblogic | Configuration Management library

In /etc/hosts on all servers and clients, or in DNS

You are running the project via Java 1.8 and add the --add-opens option to the runner. However Java 1.8 does not support it.

So, the first option is to use Java 11 to run the project, as Java 11 can recognize this VM option.

Another solution is to find a place where --add-opens is added and remove it. Check Run configuration in IntelliJ IDEA (VM options field) and Maven/Gradle configuration files for argLine (Maven) and jvmArgs (Gradle)

DCEVM and HotswapAgent do not support Weblogic. Maintainers are clear about that, it is mentioned in many issues: here, here and here.

So if you are looking for a solution that will flawlessly work out of the box on WLS, is up-to-date and supported for recent java versions, then I'm afraid DCEVM is not one.

But if your are ok with unsecure, hacky solution, then read on.

The first problem with dcevm and weblogic is to even get it running. I tested weblogic docker image with dcevm + HotswapAgent and most combinations of oraclejdk and dcevm versions cause error or other JVM/WLS crash on startup. Long time ago the maintainers said oraclejdk should work with dcevm, but I guess this is not actively supported/tested and just works by coincidence on some combination of versions. Deep magic used by WLS doesn't help also.

But thanks to some comments I found WLS will start on these two:

• oraclejdk 1.8.0_05 + dcevm installer-light-jdk8u5.52.jar (25.5-b02-dcevmlight-58)
• oraclejdk 1.8.0_25 + dcevm DCEVM-light-8u45-installer.jar (25.45-b02-dcevmlight-15

NOTE: These versions are ancient and probably have lots of security vulnerabilities, use at your own risk.

procedure:

• overwrite original java /u01/jdk/ in the image,
• take linux_amd64_compiler2/product/libjvm.so from dcevm installer and put it in /u01/jdk/jre/lib/amd64/dcevm
• add -XXaltjvm=dcevm to weblogic commandline.
• (optionally) to get HotswapAgent features:
  • add hotswap-agent-core.jar or hotswap-agent.jar in /u01/jdk/jre/lib/amd64/hotswap together with option -javaagent:/u01/jdk/jre/lib/amd64/hotswap/hotswap-agent.jar on wls commandline
  • add hotswap-agent.properties to your war/ear/classpath
  • see also https://github.com/HotswapProjects/HotswapAgent/pull/418

Now run a remote debugging session, modify a class by adding a new method and recompile - hotswapping new method is not supported by standard hotswap, it will only work when dcevm is active.

The /cs/ path is a Servlet. PeopleSoft moves files into the cache from the database. With a standard install, it is common to purge the contents of the ../cache/ and let the /cs/ servlet restore as needed. You should not populate that directory yourself.

As PeopleSoft builds the HTML for a page, it creates resource names, such as PT_NAV_BULLET_1.gif. The image definition in app designer is PT_NAV_BULLET. The _1 is the cache version.

I've had 403's when requesting files out of the cache directory when I'm not first signed into PeopleSoft. This makes sense because the /cs/ servlet is handling the request, and it doesn't know who you are.

Try clearing the ../cache/ directory, restart the webserver, and log into PeopleSoft. It should all work as expected. AFter a sign in, if you look at the cache directory, you will notice it suddenly has lots of *.css, *.js, *.png files.

You can do gradle dependencies

and check which dependency is using slf4j and exclude one using

the exclude command like this exclude(group="org.slf4j", module="slf4j-log4j12"

Am not pretty sure about this easy fix but you can try to add this to your build.gradle first

You could change the number of capture groups from 5 to the 2 that you need in the replacement. Instead of using .+, you can either use .*? or use a negated character class to match any char except a commen [^,]+

If the surrounding parenthesis of the example data should not be part of the replacement, you can use:

the problem is at the data.json.values syntax, please replace with data.json["values"]

the two tasks to show the difference:

I found a solution. I add configuration to WEB-INF/weblogic.xml like below and it works.

Do you have this in your pom.xml to exclude packaging of the tomcat jar files when creating the war file?