当前位置: 首页 > 知识库问答 >
问题:

jboss-eap-7.1.0一旦开始部署cas,就会停止记录serverstartup日志。版本5.3.8的战争

王宏深
2023-03-14

我已经在JBOSS EAP 7.1.0中部署了CAS 5.3.8 WAR文件。但是在服务器启动时,一旦JBOSS开始部署CAS WAR,它就会停止记录启动信息,下面是启动日志,

14:19:30,699 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final-redhat-1
14:19:31,108 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
14:19:31,258 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
14:19:32,466 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:19:32,481 INFO  [org.wildfly.security] (ServerService Thread Pool -- 22) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
14:19:32,483 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 27) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:19:33,491 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:19:33,505 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.5.4.Final-redhat-1
14:19:33,511 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
14:19:33,542 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 24 core threads with 192 task threads based on your 12 available processors
14:19:33,547 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 58) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
14:19:33,548 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 50) WFLYNAM0001: Activating Naming Subsystem
14:19:33,558 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 43) WFLYRS0016: RESTEasy version 3.0.24.Final-redhat-1
14:19:33,560 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem.
14:19:33,564 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 60) WFLYWS0002: Activating WebServices Extension
14:19:33,569 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 57) WFLYSEC0002: Activating Security Subsystem
14:19:33,571 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:19:33,575 INFO  [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final-redhat-1)
14:19:33,591 INFO  [org.jboss.as.security] (MSC service thread 1-6) WFLYSEC0001: Current PicketBox version=5.0.2.Final-redhat-1
14:19:33,602 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
14:19:33,604 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final-redhat-2 starting
14:19:33,621 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
14:19:33,630 INFO  [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
14:19:33,632 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:19:33,684 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.5.Final-redhat-1
14:19:33,779 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 192 (per class), which is derived from thread worker pool sizing.
14:19:33,779 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 48 (per class), which is derived from the number of CPUs on this host.
14:19:33,797 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0014: Creating file handler for path 'E:\FusionBanking\POC\CAS538_Upgrade\jboss-eap-7.1.0\jboss-eap-7.1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
14:19:33,806 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
14:19:33,808 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
14:19:33,872 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
14:19:33,884 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0493: EJB subsystem suspension complete
14:19:33,967 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:19:33,974 INFO  [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
14:19:33,989 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-4) WFLYDM0111: Keystore E:\FusionBanking\POC\CAS538_Upgrade\jboss-eap-7.1.0\jboss-eap-7.1\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
14:19:33,992 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory E:\FusionBanking\POC\CAS538_Upgrade\jboss-eap-7.1.0\jboss-eap-7.1\standalone\deployments
14:19:34,004 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
14:19:34,224 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
14:19:34,346 INFO  [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1)
14:19:39,384 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0003: Could not index class META-INF/versions/9/module-info.class at /E:/FusionBanking/POC/CAS538_Upgrade/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/cas.war/WEB-INF/lib/log4j-api-2.11.0.jar: java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 32
        at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:1417)
        at org.jboss.jandex.Indexer.index(Indexer.java:1451)
        at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99)
        at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

14:19:41,740 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/POC/CAS538_Upgrade/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar  does not point to a valid jar for a Class-Path reference.
14:19:41,757 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/POC/CAS538_Upgrade/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar  does not point to a valid jar for a Class-Path reference.
14:19:41,757 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/POC/CAS538_Upgrade/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar  does not point to a valid jar for a Class-Path reference.
14:19:41,757 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/POC/CAS538_Upgrade/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar  does not point to a valid jar for a Class-Path reference.
14:19:43,380 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final-redhat-1
14:19:43,525 WARN  [org.jboss.as.ee] (MSC service thread 1-8) WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
14:19:43,526 WARN  [org.jboss.as.ee] (MSC service thread 1-8) WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
14:19:43,587 WARN  [org.jboss.as.jaxrs] (MSC service thread 1-8) WFLYRS0015: No Servlet declaration found for JAX-RS application.  In cas.war either provide a class that extends javax.ws.rs.core.Application or declare a servlet class in web.xml.
14:19:43,589 WARN  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0013: Deployment cas.war contains CDI annotations but no bean archive was found (no beans.xml or class with bean defining annotations was present).
14:19:43,769 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started client-mappings cache from ejb container
14:19:43,895 INFO  [io.undertow.servlet] (ServerService Thread Pool -- 80) 2 Spring WebApplicationInitializers detected on classpath

在上述行之后,没有日志登录到服务器控制台。它甚至不记录启动信息,例如,

14:39:16,270INFO[org.jboss.as](Controller Boot Thread)WFLYSRV0060: Http管理界面监听http://127.0.0.1:9990/management14:39:16,271INFO[org.jboss.as](Controller Boot Thread)WFLYSRV0051:管理员控制台监听http://127.0.0.1:999014:39:16,271INFO[org.jboss.as](Controller Boot Thread)WFLYSRV0025: JBoss EAP 7.1.0。GA(WildFly Core 3.0.10。Fall-redhat-1)在3064ms中开始-553个服务中的292个开始(347个服务是惰性的、被动的或按需的)。

已设置为独立。xml。但这不应停止记录启动日志。这里我看到的是CAS。战争有log4j2。WEB-INF中的xml。这会导致任何问题吗?

共有1个答案

赖诚
2023-03-14

这与JANDEX-40相同,JANDEX-40报告了上游JANDEX组件。我们为JBoss EAP 7.1提出了JBEAP-15261。z、 此日志消息不会记录在未来的EAP 7版本中(暂定为EAP 7.1.5或更高版本)。

这是无害的,因此您可以忽略此警告消息。但是,如果您想要一种解决方法来抑制此警告消息,可以手动生成注释索引并打包生成的META-INF/jandex。问题jar中的idx。然后,在html" target="_blank">部署期间不会为jar生成注释索引。

您可以执行以下命令来生成注释索引并在war中打包索引(使用-m选项更新指定的jar文件以包含注释索引):

    java -jar $JBOSS_HOME/modules/system/layers/base/org/jboss/jandex/main/jandex-2.0.2.Final-redhat-1.jar -m log4j-api-2.11.1.jar

如果您使用的是EAP 7.1.4(或更高版本),则可以使用以下命令:

java -jar $JBOSS_HOME/jboss-modules.jar -mp $JBOSS_HOME/modules/ org.jboss.jandex -m log4j-api-2.11.1.jar

请注意,AS7-944将模块的自动注释扫描添加到EAP 7中。EAP 7中的当前实现是全有或全无。如果将索引添加到模块内的jar文件中,则不会执行任何扫描。因此,您可能需要执行应用程序中打包的所有jar文件。

参考号:https://access.redhat.com/solutions/3568471

 类似资料:
  • 我正在使用Java8构建我的应用程序,并计划使用JBoss EAP 7.1.0进行生产部署,但我没有得到JBoss EAP 7.1.0附带的Wildfly版本。我找到了Wildfly核心3.0.1,但什么是Wildfly核心? 还建议将JBoss EAP 6.4的Java版本更新到Java8并使用它吗?

  • 嗨,当我使用Selenium IDE记录一些测试时,我遇到了一个以前没有显示的奇怪问题。 > 打开Selenium IDE时,它不会自动获取url。 这是关键问题:一旦我停止录制或播放也会停止录制的测试用例,当我再次单击录制按钮时,它不再记录任何额外的操作。 我不确定这是Selenium IDE的问题还是Firefox的问题。我使用的是Selenium IDE 1.9.1和Firefox 17,当

  • 使用JBOSS 6.2 EAP作为应用服务器开发web应用程序。正在尝试自定义日志记录。要为指定位置的不同模块创建不同的日志。 做了一些家庭作业并尝试添加 在standalone的profile部分中。xml 并在同一文件中添加了记录器 此外,无法找到log4j。jboss文件夹中的xml。刚接触JBoss的人,猜一下遗漏了什么或走错了方向。有人能帮忙吗。

  • 我有一个简单的spring boot应用程序打包为。能够部署到外部Tomcat容器的war文件。我有一个日志。但是,当部署到Tomcat时,日志不会写入文件。

  • 我想用SpringBoot1.5配置log4j。10.释放。我排除了,并添加了log4j依赖项。在spring启动之前,我有所有日志,但在spring启动之后,init日志停止。 控制台日志: 和log4j2。xml文件: 你知道我做错了什么吗?

  • 我一直在尝试关闭石英的恼人的调试日志记录。我使用log4j作为日志框架,我已经尝试将这一行添加到lg4j属性文件中 我仍然收到大量的调试日志消息 如何关闭此功能? 编辑。我已经将我的配置移动到xml文件...但仍然遇到同样烦人的问题 编辑2。。。这是我的pom。xml文件(有趣的部分) 类路径中的EDIT3 jar