Author Archives: Robins

[Solved] Maven Multi-Project Compile Error: The POM for xxx is invalid

Reference address: the POM for XXX is invalid

Compilation warning:

[WARNING] The POM for com.gtcom:output-common:jar:1.0.0-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details

Solution:

If there is no remote warehouse, select install on the parent project. If there is a remote warehouse, select deploy on the parent project.

Error message:

D:\Java\jdk-11.0.13\bin\java.exe -Dmaven.multiModuleProjectDirectory=D:\IdeaProjects\gtcom-output\output-backstage "-Dmaven.home=D:\JetBrains\IntelliJ IDEA 2021.3\plugins\maven\lib\maven3" "-Dclassworlds.conf=D:\JetBrains\IntelliJ IDEA 2021.3\plugins\maven\lib\maven3\bin\m2.conf" "-Dmaven.ext.class.path=D:\JetBrains\IntelliJ IDEA 2021.3\plugins\maven\lib\maven-event-listener.jar" "-javaagent:D:\JetBrains\IntelliJ IDEA 2021.3\lib\idea_rt.jar=61663:D:\JetBrains\IntelliJ IDEA 2021.3\bin" -Dfile.encoding=UTF-8 -classpath "D:\JetBrains\IntelliJ IDEA 2021.3\plugins\maven\lib\maven3\boot\plexus-classworlds-2.6.0.jar;D:\JetBrains\IntelliJ IDEA 2021.3\plugins\maven\lib\maven3\boot\plexus-classworlds.license" org.codehaus.classworlds.Launcher -Didea.version=2021.3 -DskipTests=true compile
[INFO] Scanning for projects...
[INFO] 
[INFO] ---------------------< com.gtcom:output-backstage >---------------------
[INFO] Building output-backstage 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for com.gtcom:output-common:jar:1.0.0-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ output-backstage ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 4 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ output-backstage ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 source files to D:\IdeaProjects\gtcom-output\output-backstage\target\classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.074 s
[INFO] Finished at: 2022-01-20T19:57:55+08:00
[INFO] ------------------------------------------------------------------------
---------------------------------------------------
constituent[0]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/conf/logging/
constituent[1]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/cdi-api-1.0.jar
constituent[2]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/commons-cli-1.4.jar
constituent[3]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/commons-io-2.5.jar
constituent[4]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/commons-lang3-3.8.1.jar
constituent[5]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/guava-25.1-android.jar
constituent[6]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/guice-4.2.1-no_aop.jar
constituent[7]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/jansi-1.17.1.jar
constituent[8]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/javax.inject-1.jar
constituent[9]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/jcl-over-slf4j-1.7.29.jar
constituent[10]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/jsoup-1.12.1.jar
constituent[11]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/jsr250-api-1.0.jar
constituent[12]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-artifact-3.8.1.jar
constituent[13]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-builder-support-3.8.1.jar
constituent[14]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-compat-3.8.1.jar
constituent[15]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-core-3.8.1.jar
constituent[16]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-embedder-3.8.1.jar
constituent[17]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-model-3.8.1.jar
constituent[18]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-model-builder-3.8.1.jar
constituent[19]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-plugin-api-3.8.1.jar
constituent[20]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-repository-metadata-3.8.1.jar
constituent[21]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-api-1.6.2.jar
constituent[22]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-connector-basic-1.6.2.jar
constituent[23]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-impl-1.6.2.jar
constituent[24]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-provider-3.8.1.jar
constituent[25]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-spi-1.6.2.jar
constituent[26]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-transport-wagon-1.6.2.jar
constituent[27]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-resolver-util-1.6.2.jar
constituent[28]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-settings-3.8.1.jar
constituent[29]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-settings-builder-3.8.1.jar
constituent[30]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-shared-utils-3.2.1.jar
constituent[31]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/maven-slf4j-provider-3.8.1.jar
constituent[32]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/org.eclipse.sisu.inject-0.3.4.jar
constituent[33]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/org.eclipse.sisu.plexus-0.3.4.jar
constituent[34]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/plexus-cipher-1.7.jar
constituent[35]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/plexus-component-annotations-2.1.0.jar
constituent[36]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/plexus-interpolation-1.25.jar
constituent[37]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/plexus-sec-dispatcher-1.4.jar
constituent[38]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/plexus-utils-3.2.1.jar
constituent[39]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/slf4j-api-1.7.29.jar
constituent[40]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/wagon-file-3.4.3.jar
constituent[41]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/wagon-http-3.4.3-shaded.jar
constituent[42]: file:/D:/JetBrains/IntelliJ%20IDEA%202021.3/plugins/maven/lib/maven3/lib/wagon-provider-api-3.4.3.jar
---------------------------------------------------
Exception in thread "main" java.lang.AssertionError
	at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155)
	at jdk.compiler/com.sun.tools.javac.util.Assert.check(Assert.java:46)
	at jdk.compiler/com.sun.tools.javac.comp.Modules.enter(Modules.java:247)
	at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.readSourceFile(JavaCompiler.java:837)
	at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$ImplicitCompleter.complete(JavacProcessingEnvironment.java:1535)
	at jdk.compiler/com.sun.tools.javac.code.Symbol.complete(Symbol.java:642)
	at jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:1326)
	at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.complete(Type.java:1140)
	at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.getTypeArguments(Type.java:1066)
	at jdk.compiler/com.sun.tools.javac.code.Printer.visitClassType(Printer.java:237)
	at jdk.compiler/com.sun.tools.javac.code.Printer.visitClassType(Printer.java:52)
	at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.accept(Type.java:993)
	at jdk.compiler/com.sun.tools.javac.code.Printer.visit(Printer.java:136)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArgument(AbstractDiagnosticFormatter.java:199)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArguments(AbstractDiagnosticFormatter.java:167)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:111)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:67)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArgument(AbstractDiagnosticFormatter.java:185)
	at jdk.compiler/com.sun.tools.javac.util.AbstractDiagnosticFormatter.formatArguments(AbstractDiagnosticFormatter.java:167)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:111)
	at jdk.compiler/com.sun.tools.javac.util.BasicDiagnosticFormatter.formatMessage(BasicDiagnosticFormatter.java:67)
	at jdk.compiler/com.sun.tools.javac.util.JCDiagnostic.getMessage(JCDiagnostic.java:788)
	at jdk.compiler/com.sun.tools.javac.api.ClientCodeWrapper$DiagnosticSourceUnwrapper.getMessage(ClientCodeWrapper.java:799)
	at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:149)
	at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
	at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
	at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)

The process has ended, exit code 1

webpack4 Use webpack-dev-server Error [How to Solve]

Today, I reported an error with webpack dev server in the project to visually check the version problem
the webpack version used in the project is "webpack": "^ 4.28.4"
the default is "webpack dev server": "^ 4.7.3" , and the reduced version is "webpack dev server": "^ 3.1.14" . The problem is solved

Then start the error report:
check the data and find that the startup command is changed to NPX webpack server -- config webpack dev.js

[How to Solve] Reason: Incompatible library version

Today’s respondent reported the following errors when testing the PIL package in Python:

Reason: Incompatible library version: _imaging.cpython-37m-darwin.so requires version 14.0.0 or later, but libjpeg.9.dylib provides version 12.0.0

By analyzing the error message, we can see that it is caused by the version incompatibility between libraries, because the PIL library is old and only supports python2.7, which may lead to this problem. So we think about how to solve it.

Solution

First, consider reloading the library. The basic environment of this environment is Python 3.7. Therefore, enter the code on the command line, delete the library first, and then reinstall it.

conda uninstall pillow
conda install pillow

Finally, the test re imports the library successfully and outputs the size of the picture

Successfully solve the problem!

[Solved] docker Commands Execute Error: Segmentation fault

If you execute any docker command, you will report an error segmentation fault. There have been no similar errors when using docker before. After troubleshooting, it was found that the available memory was only 110m. It was speculated that the memory was not enough, so the command to clean the memory was executed, but the parameters were changed to 1, 2 and 3, which could not clean the memory.

sync
echo 1 > /proc/sys/vm/drop_caches

The solution is found on GitHub. First enter

sysctl vm.overcommit_memory

The output is 0, and then change the parameters

sysctl vm.overcommit_memory=1

At this time, the application that occupies a lot of memory has been restarted automatically. If not, execute the above cleaning command.

Spring Error: Transaction synchronization is not active

First, make sure that the @Transactional annotation is added to the calling method
1. Add the @Transactional annotation where transaction management is required. The @Transactional annotation can be applied to interface definitions and interface methods, class definitions and public methods of classes.
2. @Transactional annotations can only be applied to public visibility methods. If you use the @Transactional annotation on a protected, private, or package-visible method, it will not report an error, but the annotated method will not display the configured transaction settings.
3. Note that the mere presence of the @Transactional annotation is not sufficient to enable transactional behavior, it is only a metadata. You must use the configuration element in the configuration file to actually enable the transaction behavior. (spring configuration file, turn on declarative transactions)
The value of the “proxy-target-class” attribute of the element controls whether interface-based or class-based proxies are created. If the “proxy-target-class” property is set to “true”, then the class-based proxy will work (this requires the CGLIB library cglib.jar in the CLASSPATH). If the “proxy-target-class” property is set to “false” or if this property is omitted, then the standard JDK interface-based proxy will work.
5. The Spring team recommends using @Transactional annotations on specific classes (or methods of classes) and not on any interfaces that the class is intended to implement. Using @Transactional annotations on interfaces will only work if you set up an interface-based proxy. Because annotations are not inheritable, this means that if a class-based proxy is being used, then the transaction settings will not be recognized by the class-based proxy and the object will not be wrapped by the transaction proxy.
6. @Transactional transactions are opened, either by interface-based or class-based proxies are created. So in the same class a non-transactional method calls another transactional method, the transaction will not work.
Pay special attention to point 6: a non-transactional method in the same class calls another transactional method, the transaction will not work. This point caught my attention, maybe my annotated @Transactional departingCar method is also called by another method in the class that does not open a transaction, if this is true, everything makes sense.

Springboot2.6.X configurate swagger error [How to Solve] 

org.springframework.context.ApplicationContextException: Failed to start bean 'documentationPluginsBootstrapper'; nested exception is java.lang.NullPointerException
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:181)
	at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54)
	at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:356)
	at java.lang.Iterable.forEach(Iterable.java:75)

Modify YML file

spring:
  mvc:
    pathmatch:
      matching-strategy: ant_path_matcher

[Solved] Hive On Spark Error: Remote Spark Driver – HiveServer2 connection has been closed

Error Messages:

Failed to monitor Job[-1] with exception ‘java.lang.IllegalStateException(Connection to remote Spark driver was lost)’ Last known state = SENT
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.spark.SparkTask. Unable to send message SyncJobRequest{job=org.apache.hadoop.hive.ql.exec.spark.status.impl.RemoteSparkJobStatus$GetAppIDJob@7805478c} because the Remote Spark Driver - HiveServer2 connection has been closed.

The real cause of this problem requires going to Yarn and looking at the Application’s detailed logs at

It turns out that the executor-memory is too small and needs to be modified in the hive configuration page

Save the changes and restart the relevant components, the problem is solved.

[Solved] Tencent cloud SMS service error: FailedOperation.TemplateIncorrectOrUnapproved

1. Problem
an error occurs when sending a text message:

"Code":"FailedOperation.TemplateIncorrectOrUnapproved",
"Message":"template is not approved or request content does not match the approved template content"

2. Solution
the reason for the error is that the template content parameters are inconsistent with the set parameters. Set to consistent. As shown in the following figure, the template content has two parameters, so the templateparamset in the code should also set two parameters

    /* Template parameters: If no template parameters, set to empty */
    String[] templateParamSet = {"", "60"};
    req.setTemplateParamSet(templateParamSet);

[Solved] webpack Package Error: TypeError: this.getOptions is not a function style-loader

I used style-loader in the project today, and found an error in packaging: typeerror: this Getoptions is not a function
visual inspection is a version problem. The default version of style-loader is 3.3.1. The reduced version is 2.0.0, and the problem is solved
PS: the webpack version used is 4.28.4

[Solved] Springboot Project Error: Mail server connection failed;

 

Error background

Using springboot2 Error in 2.0 integrated mail function

Error message:

org.springframework.mail.MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: Could not connect to SMTP host: smtp.qq.com, port: 587;nested exception is:
	javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?. Failed messages: javax.mail.MessagingException: Could not connect to SMTP host: smtp.qq.com, port: 587;nested exception is:
	javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
; message exception details (1) are:Failed message 1:
javax.mail.MessagingException: Could not connect to SMTP host: smtp.qq.com, port: 587;
  nested exception is:

Solution:

Modify the configuration file (in the context of using QQ mailbox)

spring:
  mail:
    host: smtp.qq.com
    port: 587
    username: e-mail
    password: Authorization Code
    default-encoding: UTF-8
    properties:
      mail:
        smtp:
          socketFactory:
            class: javax.net.ssl.SSLSocketFactory

result

After modifying the configuration, the problem is solved!