-
1. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
I just created a bug for this https://issues.jboss.org/browse/AS7-1280. Something within the .war is leading to this issue. Can you please attach the .war to this thread?
-
2. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
I've tried to deploy 2 war files ... the first one, after include some dependency libraries, deployed successfully , the second (more complex) war I've got similar error.
This is when I start with the working war:
codeit@wksp-boaglio:~/jboss-as-web-7.0.0.Final/bin$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/codeit/jboss-as-web-7.0.0.Final
JAVA: /home/codeit/jdk/atual/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
=========================================================================
15:10:05,973 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA
15:10:06,190 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
15:10:06,228 INFO [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting
15:10:06,843 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
15:10:06,850 INFO [org.jboss.as.logging] Removing bootstrap log handlers
15:10:06,914 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.1)
15:10:06,933 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
15:10:07,030 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
15:10:07,040 INFO [org.jboss.as.naming] (MSC service thread 1-3) Starting Naming Service
15:10:07,044 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
15:10:07,062 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
15:10:07,075 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
15:10:07,083 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
15:10:07,091 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
15:10:07,235 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/codeit/jdk/atual/jre/lib/amd64/server:/home/codeit/jdk/atual/jre/lib/amd64:/home/codeit/jdk/atual/jre/../lib/amd64:/usr/lib:/oracle/product/11.2.0/dbhome_1/lib:/home/codeit/yjp-10-eap-build10030/bin/linux-x86-64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
15:10:07,258 INFO [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:9999
15:10:07,271 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
15:10:07,275 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-5) Starting remote JMX connector
15:10:07,418 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
15:10:07,472 INFO [org.jboss.as.connector] (MSC service thread 1-5) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
15:10:07,528 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) Bound data source [java:/VPDataSource]
15:10:07,795 INFO [org.jboss.as.deployment] (MSC service thread 1-5) Started FileSystemDeploymentService for directory /home/codeit/jboss-as-web-7.0.0.Final/standalone/deployments
15:10:07,805 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final "Lightning" started in 2003ms - Started 92 of 147 services (55 services are passive or on-demand)
15:10:07,848 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "vp-services.war"
15:10:14,536 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxb-api.jar in "/content/vp-services.war/WEB-INF/lib/jaxb-impl-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
15:10:14,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry activation.jar in "/content/vp-services.war/WEB-INF/lib/jaxb-impl-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
15:10:14,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jsr173_1.0_api.jar in "/content/vp-services.war/WEB-INF/lib/jaxb-impl-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
15:10:14,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxb1-impl.jar in "/content/vp-services.war/WEB-INF/lib/jaxb-impl-2.1.3.jar" does not point to a valid jar for a Class-Path reference.
15:10:14,669 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-2) Encountered invalid class name "org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer" for service type "org.xmlpull.v1.XmlPullParserFactory"
15:10:16,075 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/services]] (MSC service thread 1-8) Initializing Spring root WebApplicationContext
15:10:16,077 ERROR [stderr] (MSC service thread 1-8) log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader).
15:10:16,077 ERROR [stderr] (MSC service thread 1-8) log4j:WARN Please initialize the log4j system properly.
15:10:18,995 ERROR [stderr] (MSC service thread 1-8) SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
15:10:18,995 ERROR [stderr] (MSC service thread 1-8) SLF4J: Defaulting to no-operation (NOP) logger implementation
15:10:18,995 ERROR [stderr] (MSC service thread 1-8) SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
15:10:20,230 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-8) Hibernate Validator 4.1.0.Final
15:10:20,235 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] (MSC service thread 1-8) Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
15:10:20,942 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] (MSC service thread 1-8) Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
15:10:20,947 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] (MSC service thread 1-8) Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
15:10:25,287 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-8) Inicializando Mojarra 2.0.4 (FCS b09-jbossorg-4) para o contexto '/services'
15:10:27,159 INFO [org.jboss.web] (MSC service thread 1-8) registering web context: /services
15:10:27,280 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "vp-services.war"
And this is when I copy the "bad" war to $HOME/jboss-as-web-7.0.0.Final/standalone/deployments/ :
15:19:57,571 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "vpcontrol.war"
15:20:06,218 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry activation.jar in "/content/vpcontrol.war/WEB-INF/lib/mail-1.4.jar" does not point to a valid jar for a Class-Path reference.
15:20:06,472 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."vpcontrol.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."vpcontrol.war".PARSE: Failed to process phase PARSE of deployment "vpcontrol.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed
at org.jboss.msc.service.ServiceName.of(ServiceName.java:85)
at org.jboss.msc.service.ServiceName.append(ServiceName.java:112)
at org.jboss.as.ee.component.ComponentDescription.<init>(ComponentDescription.java:145)
at org.jboss.as.web.deployment.component.WebComponentDescription.<init>(WebComponentDescription.java:37)
at org.jboss.as.web.deployment.component.WebComponentProcessor.deploy(WebComponentProcessor.java:126)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
15:20:06,497 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployment of "vpcontrol.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"vpcontrol.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"vpcontrol.war\".PARSE: Failed to process phase PARSE of deployment \"vpcontrol.war\""}}
15:20:06,498 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) Service status report
Services which failed to start:
service jboss.deployment.unit."vpcontrol.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."vpcontrol.war".PARSE: Failed to process phase PARSE of deployment "vpcontrol.war"
15:20:06,499 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.\"vpcontrol.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"vpcontrol.war\".PARSE: Failed to process phase PARSE of deployment \"vpcontrol.war\""}}}}
15:20:06,728 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Stopped deployment vpcontrol.war in 222ms
I will be glad to help you guys with your amazing work but I'm not sure if my boss allows me to put this war file here
-
3. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
I have the same problem.
As per
AS7-1280 Skip component creation for empty class names (and the code proposed)
It could be an issue of my deployment and/or not...
Could you please let me know if I should look into my code in order to guess this posible error? and if so: What should I look for? Any clues?
Thanks
-
5. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
David, would you be able to debug the AS7 code? If so, then setting a breakpoint in getComponentClasses() method should reveal who/what adds the empty component class name. Or maybe you would be able to share your application so that we can take a quick look?
-
6. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
Hi jaikiran,
I downloaded AS7-1280 from GIT and replaced the build from the Final version with this build and the problem gone (due to the code where avoids null or black class names..)
If you are interested, I could modify the code to see the class...
-
7. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
David Calvente wrote:
If you are interested, I could modify the code to see the class...
Sure, we would like to know where that empty class name comes from.
-
8. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
David Calvente wrote:
Hi jaikiran,
I downloaded AS7-1280 from GIT and replaced the build from the Final version with this build and the problem gone (due to the code where avoids null or black class names..)
By the way, that commit is already pushed to AS7 upstream. So it's available in our nightly builds http://community.jboss.org/thread/167590
-
9. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
Hi,
I have been looking into the code and putting some sysout in:
private void getAllComponentClasses(WebCommonMetaData metaData, Set<String> classes)
and
private void getAllComponentClasses(TldMetaData metaData, Set<String> classes) {
and I realized that the classes with empty names come from some TldMetaData, method: tag.getTagClass() , in my case, from
TldMetaData with metaData.getName() -> http://www.springframework.org/tags/faces
Maybe this is due to some module (spring) that needs to be loaded. But I created in modules\org\springframework\spring\main a module.xml with content:
<module xmlns="urn:jboss:module:1.0" name="org.springframework.spring">
<resources>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api" />
<module name="javax.jms.api" />
<module name="javax.annotation.api" />
<module name="org.apache.commons.logging" />
</dependencies>
</module>
and added a
Dependencies: org.springframework.spring
in the War MANIFEST.MF
But no success
By the way: I've readed that I should install spring module manually or using JBossWS-CXF installation scripts Could you please tell me how to get it installed? I have another issue that avoids my deployment to read the WebContext Annotation and maybe it's related...
-
10. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
Thanks for looking into it. And indeed you are right, it's a spring tld which is the culprit https://src.springframework.org/svn/spring-webflow/branches/spring-webflow-2.0-maintenance/spring-faces/src/main/resources/META-INF/spring-faces.tld which has elements like this all over the file:
<tag-class></tag-class>
I've no clue why they don't specify the class name. I'll check tomorrow.
David Calvente wrote:
Maybe this is due to some module (spring) that needs to be loaded. But I created in modules\org\springframework\spring\main a module.xml with content:
<module xmlns="urn:jboss:module:1.0" name="org.springframework.spring">
<resources>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api" />
<module name="javax.jms.api" />
<module name="javax.annotation.api" />
<module name="org.apache.commons.logging" />
</dependencies>
</module>
and added a
Dependencies: org.springframework.spring
in the War MANIFEST.MF
But no success
You don't have to add that module to your application. The tld is probably being picked up because the spring jar is present within the WEB-INF/lib of your .war.
David Calvente wrote:
By the way: I've readed that I should install spring module manually or using JBossWS-CXF installation scripts Could you please tell me how to get it installed? I have another issue that avoids my deployment to read the WebContext Annotation and maybe it's related...
Could you please open a new thread for this. That'll help in separating out the issues. Someone from JBossWS team will perhaps be able to help in that.
Thanks again, for debugging this.
-
11. Re: JBoss 7 Final - ERROR [org.jboss.msc.service.fail] - Empty name segment is not allowed
I got the same error and solved it by adding a file /WEB-INF/beans.xml in the WAR with the following content:
<?xml version="1.0"?>
<beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">
</beans>
Hope this helps.
