How to resolve jar package conflicts when deploying springboot to weblogic

Background

In a certain project, the customer required to use existing weblogic to deploy the developed springboot, so some configuration adjustments were made to springboot, mainly including removing tomcat dependency and adding startup class processing.

It usually goes smoothly, but in fact there are always some minor problems.

Question 1

When the package is released to weblogic and started, the error shown in the following figure is:

The exception content can be very It is easy to judge that this is an error caused by jar package conflict.

After locating, weblogic has a directory wls12213\oracle_common\modules\thirdparty, which stores some third-party default jar packages. During the project startup process, the jar here is loaded first by default. package, and then load the jar package in the project project. Because you cannot guarantee that the version of the jar package in the project project and the jar package in weblogic are exactly the same, a common class loading conflict occurs due to inconsistent jar package versions.

Check the official website information, weblogic also has a solution. You can define which classes need to be loaded first from the jar package of the project engineering package by adding and configuring the weblogic.xml file.

The configuration method is as follows:

Create a webapp directory at the same level as the springboot project code and resource, then create a WEB-INF directory under the webapp directory, and add weblogic.xml The file is placed in WEB-INF. Taking the springboot-weblogic-demo project as an example, its full path is springboot-weblogic-demo\\src\main\webapp\WEB-INF\weblogic.xml, among which The content is as follows:

<?xml version=&#39;1.0&#39; encoding=&#39;UTF-8&#39;?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd">
    <container-descriptor>
        <prefer-application-packages>
            <package-name>org.slf4j</package-name>
            <package-name>javax.validation.*</package-name>
            <package-name>org.hibernate.*</package-name>
            <package-name>javax.el.*</package-name>
            <package-name>org.springframework.*</package-name>
            <!--解决项目中jackson的jar包和weblogic中thirdparty的jar包冲突问题，配置优先加载项目中的jar-->
            <package-name>com.fasterxml.jackson.*</package-name>
        </prefer-application-packages>
    </container-descriptor>
    <context-root>/springboot-weblogic-demo</context-root>
</weblogic-web-app>

Only add and configure this file, there is no other configuration. I have not added the operations of adding web.xml mentioned on the Internet here. The example is based on springboot 2.7 .2 Normal deployment operation.

Problem 2

There was also a GC error during the deployment processGC overhead limit exceeded. This problem is relatively easy to solve. Modify the memory value for the weblogic startup environment. , just increase it.

Modify the corresponding fileD:\weblogic\fmw_12.2.1.3.0_wls_quick_Disk1_1of1\wls12213\user_projects\domains\base_domain\bin\setDomainEnv.cmd, around the beginning of line 200, modify The final content is as follows:

if NOT "%JAVA_VENDOR%"=="HP" (
	if "%VM_TYPE%"=="HotSpot" (
		set WLS_MEM_ARGS_64BIT=-Xms1024m -Xmx4096m
		set WLS_MEM_ARGS_32BIT=-Xms256m -Xmx512m
	)
)

Restart the weblogic service, and you can see the remaining memory configuration after we modified it at the beginning:

##WLS_MEM_ARGS_64BIT The original value is -Xms256m -Xmx512m, or you can add more memory settings, for example: -Xms512m -Xmx1024m -XX:MaxNewSize=1024m -XX:MaxPermSize=1024m

The above is the detailed content of How to resolve jar package conflicts when deploying springboot to weblogic. For more information, please follow other related articles on the PHP Chinese website!