[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by Florian Beckmann (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
Florian Beckmann edited comment on AS7-5744 at 4/30/13 5:19 PM:
----------------------------------------------------------------
Actually I have none. This is Code from sphinx4.jar (http://cmusphinx.sourceforge.net), which is used in the app.
Here the code in ConfigurationManagerUtils from sphinx4.jar:
public static void configureLogger(Logger logger) {
LogManager logManager = LogManager.getLogManager();
ByteArrayOutputStream bos = new ByteArrayOutputStream();
Properties props = new Properties();
props.setProperty(".edu.cmu.sphinx.level", "FINEST");
props.setProperty("handlers", "java.util.logging.ConsoleHandler");
props.setProperty("java.util.logging.ConsoleHandler.level", "FINEST");
props.setProperty("java.util.logging.ConsoleHandler.formatter",
"edu.cmu.sphinx.util.SphinxLogFormatter");
try {
props.store(bos, "");
bos.close();
ByteArrayInputStream bis = new ByteArrayInputStream(bos.toByteArray());
logManager.readConfiguration(bis);
bis.close();
} catch (IOException ioe) {
System.err.println("Can't configure logger, using default configuration");
}
// Now we find the SphinxLogFormatter that the log manager created
// and configure it.
Handler[] handlers = logger.getHandlers();
for (Handler handler : handlers) {
handler.setFormatter(new SphinxLogFormatter());
}
}
was (Author: elessartelrunya):
Actually I have none. This is Code from sphinx4.jar (http://cmusphinx.sourceforge.net), which is used in the app.
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (WFLY-1302) Upgrade log4-jboss-logmanager
by James Perkins (JIRA)
James Perkins created WFLY-1302:
-----------------------------------
Summary: Upgrade log4-jboss-logmanager
Key: WFLY-1302
URL: https://issues.jboss.org/browse/WFLY-1302
Project: WildFly
Issue Type: Component Upgrade
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Minor
Fix For: 8.0.0.Alpha1
Upstream of log4j-jboss-logmanager contains a bug fix for serializing the {{ThrowableInformation}} correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by Florian Beckamann (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
Florian Beckamann commented on AS7-5744:
----------------------------------------
Actually I have none. This is Code from sphinx4.jar (http://cmusphinx.sourceforge.net), which is used in the app.
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (WFLY-1301) Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1301?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside updated WFLY-1301:
----------------------------------
Component/s: Web (JBoss Web)
> Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
> ---------------------------------------------------------------
>
> Key: WFLY-1301
> URL: https://issues.jboss.org/browse/WFLY-1301
> Project: WildFly
> Issue Type: Bug
> Components: Web (JBoss Web), Web Services
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Alessio Soldano
>
> {code}
> awhiteside@localhost jboss-as-8.0.0.Alpha1-SNAPSHOT# ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT
> JAVA: /usr/local/java/bin/java
> JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:28:15,876 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final
> 16:28:16,018 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.2.Final
> 16:28:16,068 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> 16:28:16,791 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.1.0.CR2
> 16:28:16,793 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 16:28:16,795 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.1.0.CR2
> 16:28:16,809 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.16.GA
> 16:28:16,838 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 16:28:16,861 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 16:28:16,876 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012605: Activated the following JSF Implementations: [main]
> 16:28:16,876 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
> 16:28:16,899 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
> 16:28:16,912 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 16:28:16,914 INFO [org.jboss.as.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 16:28:16,931 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.16.Final)
> 16:28:16,935 INFO [org.jboss.as.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 16:28:16,947 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.16.Final
> 16:28:16,949 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2
> 16:28:16,953 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
> 16:28:16,956 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 16:28:17,048 INFO [io.undertow] (ServerService Thread Pool -- 47) Creating file handler for path /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/welcome-content
> 16:28:17,099 INFO [org.jboss.as.undertow] (MSC service thread 1-4) Starting server server service: service jboss.undertow.server.default-server
> 16:28:17,105 INFO [org.jboss.as.undertow] (MSC service thread 1-3) Starting host default-host
> 16:28:17,105 INFO [org.jboss.as.undertow] (MSC service thread 1-3) registering handler io.undertow.server.handlers.resource.ResourceHandler@222ac389 under path '/'
> 16:28:17,120 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Alpha1
> 16:28:17,180 INFO [org.jboss.as.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
> 16:28:17,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "hawtio.war" (runtime-name: "hawtio.war")
> 16:28:17,335 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 16:28:17,336 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/standalone/deployments
> 16:28:17,336 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
> 16:28:17,337 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
> 16:28:17,991 INFO [io.undertow.servlet] (MSC service thread 1-8) jolokia-agent: Using access restrictor classpath:/jolokia-access.xml
> 16:28:18,115 INFO [org.jboss.as.undertow] (MSC service thread 1-8) JBAS018210: Register web context: /hawtio
> 16:28:18,143 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "hawtio.war" (runtime-name : "hawtio.war")
> 16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 2729ms - Started 198 of 234 services (55 services are lazy, passive or on-demand)
> 16:28:33,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "messaging-gateway.war" (runtime-name: "messaging-gateway.war")
> 16:28:35,396 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jaxb-api.jar in /content/messaging-gateway.war/WEB-INF/lib/jaxb-impl-2.2.6.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-api.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-extra.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_l10n.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_ja.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_zh.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_fr.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_de.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_es.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_it.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_sw.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_ko.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_zh_TW.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 16:28:35,437 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."messaging-gateway.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."messaging-gateway.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "messaging-gateway.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /RegistrationService_V11 is already registered. Web service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pattern.
> at org.jboss.as.webservices.metadata.model.AbstractDeployment.addEndpoint(AbstractDeployment.java:60)
> at org.jboss.as.webservices.metadata.model.JAXWSDeployment.addEndpoint(JAXWSDeployment.java:27)
> at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_POJO.processAnnotation(WSIntegrationProcessorJAXWS_POJO.java:98)
> at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:92)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> ... 5 more
> 16:28:35,442 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"messaging-gateway.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"messaging-gateway.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"messaging-gateway.war\"
> Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /RegistrationService_V11 is already registered. Web service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pattern."}}
> 16:28:35,485 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment messaging-gateway.war (runtime-name: messaging-gateway.war) in 42ms
> 16:28:35,486 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."messaging-gateway.war".PARSE
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (WFLY-1301) Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
by Aaron Whiteside (JIRA)
Aaron Whiteside created WFLY-1301:
-------------------------------------
Summary: Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
Key: WFLY-1301
URL: https://issues.jboss.org/browse/WFLY-1301
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 8.0.0.Alpha1
Reporter: Aaron Whiteside
Assignee: Alessio Soldano
{code}
awhiteside@localhost jboss-as-8.0.0.Alpha1-SNAPSHOT# ./bin/standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT
JAVA: /usr/local/java/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
16:28:15,876 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final
16:28:16,018 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.2.Final
16:28:16,068 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
16:28:16,791 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.1.0.CR2
16:28:16,793 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
16:28:16,795 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.1.0.CR2
16:28:16,809 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.16.GA
16:28:16,838 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:28:16,861 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:28:16,876 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012605: Activated the following JSF Implementations: [main]
16:28:16,876 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
16:28:16,899 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
16:28:16,912 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:28:16,914 INFO [org.jboss.as.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Alpha9 starting
16:28:16,931 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.16.Final)
16:28:16,935 INFO [org.jboss.as.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.0.Alpha9 starting
16:28:16,947 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.16.Final
16:28:16,949 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2
16:28:16,953 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
16:28:16,956 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:28:17,048 INFO [io.undertow] (ServerService Thread Pool -- 47) Creating file handler for path /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/welcome-content
16:28:17,099 INFO [org.jboss.as.undertow] (MSC service thread 1-4) Starting server server service: service jboss.undertow.server.default-server
16:28:17,105 INFO [org.jboss.as.undertow] (MSC service thread 1-3) Starting host default-host
16:28:17,105 INFO [org.jboss.as.undertow] (MSC service thread 1-3) registering handler io.undertow.server.handlers.resource.ResourceHandler@222ac389 under path '/'
16:28:17,120 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Alpha1
16:28:17,180 INFO [org.jboss.as.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
16:28:17,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "hawtio.war" (runtime-name: "hawtio.war")
16:28:17,335 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:28:17,336 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/standalone/deployments
16:28:17,336 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
16:28:17,337 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
16:28:17,991 INFO [io.undertow.servlet] (MSC service thread 1-8) jolokia-agent: Using access restrictor classpath:/jolokia-access.xml
16:28:18,115 INFO [org.jboss.as.undertow] (MSC service thread 1-8) JBAS018210: Register web context: /hawtio
16:28:18,143 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "hawtio.war" (runtime-name : "hawtio.war")
16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 2729ms - Started 198 of 234 services (55 services are lazy, passive or on-demand)
16:28:33,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "messaging-gateway.war" (runtime-name: "messaging-gateway.war")
16:28:35,396 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jaxb-api.jar in /content/messaging-gateway.war/WEB-INF/lib/jaxb-impl-2.2.6.jar does not point to a valid jar for a Class-Path reference.
16:28:35,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-api.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-extra.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_l10n.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_ja.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_zh.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_fr.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_de.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_es.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_it.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_sw.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_ko.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry webservices-rt_zh_TW.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
16:28:35,437 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."messaging-gateway.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."messaging-gateway.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "messaging-gateway.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /RegistrationService_V11 is already registered. Web service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pattern.
at org.jboss.as.webservices.metadata.model.AbstractDeployment.addEndpoint(AbstractDeployment.java:60)
at org.jboss.as.webservices.metadata.model.JAXWSDeployment.addEndpoint(JAXWSDeployment.java:27)
at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_POJO.processAnnotation(WSIntegrationProcessorJAXWS_POJO.java:98)
at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:92)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
... 5 more
16:28:35,442 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"messaging-gateway.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"messaging-gateway.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"messaging-gateway.war\"
Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /RegistrationService_V11 is already registered. Web service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pattern."}}
16:28:35,485 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment messaging-gateway.war (runtime-name: messaging-gateway.war) in 42ms
16:28:35,486 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."messaging-gateway.war".PARSE
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
James Perkins commented on AS7-5744:
------------------------------------
What does your logging.properties file look like? Is it in the JUL format?
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by Florian Beckamann (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
Florian Beckamann commented on AS7-5744:
----------------------------------------
I get the same error with JBoss EAP 6.1.0.Beta1 (linux kernel 3.8). The -Dorg.jboss.as.logging.per-deployment=false workaround seems to be ignored.
[0m[0m21:35:06,238 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.Beta1 (AS 7.2.0.Final-redhat-4) started in 4889ms - Started 170 of 227 services (56 services are passive or on-demand)
[0m[31m21:35:43,402 ERROR [stderr] (http-/0.0.0.0:8080-1) java.lang.IllegalArgumentException: className is null
[0m[31m21:35:43,403 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:59)
[0m[31m21:35:43,404 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54)
[0m[31m21:35:43,405 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:144)
[0m[31m21:35:43,406 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:606)
[0m[31m21:35:43,406 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:487)
[0m[31m21:35:43,407 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:96)
[0m[31m21:35:43,408 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.as.logging.logmanager.ConfigurationPersistence.configure(ConfigurationPersistence.java:128)
[0m[31m21:35:43,408 ERROR [stderr] (http-/0.0.0.0:8080-1) at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300)
[0m[31m21:35:43,409 ERROR [stderr] (http-/0.0.0.0:8080-1) at edu.cmu.sphinx.util.props.ConfigurationManagerUtils.configureLogger(ConfigurationManagerUtils.java:195)
[0m[31m21:35:43,409 ERROR [stderr] (http-/0.0.0.0:8080-1) at edu.cmu.sphinx.util.props.ConfigurationManagerUtils.configureLogger(ConfigurationManagerUtils.java:165)
[0m[31m21:35:43,410 ERROR [stderr] (http-/0.0.0.0:8080-1) at edu.cmu.sphinx.util.props.ConfigurationManager.<init>(ConfigurationManager.java:64)
So I guess the bug has to be re-opened!?
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (WFLY-976) Multi-JSF doesn't understand new modules structure
by Glenn Kastrinos (JIRA)
[ https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s... ]
Glenn Kastrinos commented on WFLY-976:
--------------------------------------
YES! Thank you so much for all of your help! It FINALLY compiles and deploys successfully with no errors, even when I added the tomahawk-1.1.9 jar and put the extension filters back into my web.xml. My only issue is that I can't seem to get the correct URL. http://127.0.0.1:8080/Localization/ should work, judging from the standalone.xml. I just get "404 - Not Found." Any thoughts?
I hope this post tree helps people that were in my position. Thank you again very much
> Multi-JSF doesn't understand new modules structure
> --------------------------------------------------
>
> Key: WFLY-976
> URL: https://issues.jboss.org/browse/WFLY-976
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Reporter: Stan Silvert
> Assignee: Stan Silvert
> Attachments: install-myfaces-2.1.11.cli, Localization.war, Localization.war
>
>
> With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default.
> The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script.
> See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months