[esb-issues] [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)

[ https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu... ] Daniel Bevenius commented on JBESB-2760: ---------------------------------------- This might not have been such an big issue after all. I noticed that my host file was incorrect for my local machine name. This is what caused the error I saw when starting up the AS without any ESB stuff deployed. After deploying the ESB I get the following error upon startup: 13:13:02,967 ERROR [org.apache.catalina.startup.TldConfig] Exception processing JAR at resource path /opt/jboss/as/src/trunk/build/output/jboss-6.0.0.Alpha1/server/default/tmp/3j001-il4ug9-fxpyi7je-1-fxpyk6tm-af/jbpm-console.war/WEB-INF/lib/gravel-1.0.0.GA.jar in context /jbpm-console: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:203) at java.util.jar.JarFile.<init>(JarFile.java:132) at java.util.jar.JarFile.<init>(JarFile.java:97) at org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:461) at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:301) at org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4540) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4308) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:462) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:116) at org.jboss.web.deployers.WebModule.start(WebModule.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Just deploying the jbpm-console.war will produce the same issue. Also stopping the server does not work as there are jars that are missing for the shutdown task: <classpath> <pathelement location=&quot;(a){serverHome}/bin/shutdown.jar&quot;/&gt; <pathelement location=&quot;(a){serverHome}/client/jbossall-client.jar&quot;/&gt; <pathelement location=&quot;(a){serverHome}/lib/jboss-bootstrap-spi-as.jar&quot;/&gt; <pathelement location=&quot;(a){serverHome}/lib/jboss-bootstrap-spi-mc.jar&quot;/&gt; <pathelement location=&quot;(a){serverHome}/lib/jboss-bootstrap-spi.jar&quot;/&gt; <pathelement location=&quot;(a){serverHome}/lib/jboss-system-jmx.jar&quot;/&gt; <pathelement location=&quot;(a){serverHome}/lib/jboss-kernel.jar&quot;/&gt; </classpath> Adding the above will shutdown the server. Note that these jars are not in shutdown.sh and it displays the same errors when run. There is still an issue with the build though as this version of AS does not seem to write any string to server.log which means that the stop-server target will always timeout causing the build to fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira