Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-167

Failing Deployment on startup receives a very meager error message

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.0.0.CR1
    • Component/s: None
    • Labels:
      None

      Description

      The following shows a server which has an invalid deployment in standalone.xml:

      $ ./standalone.sh 
      =========================================================================
      
        JBoss Bootstrap Environment
      
        JBOSS_HOME: /home/carlo/work/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT
      
        JAVA: /usr/lib/jvm/java-6-sun/bin/java
      
        JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
      
      =========================================================================
      
      14:41:10,570 INFO  [org.jboss.modules] JBoss Modules version 1.0.0.Beta17
      14:41:10,715 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.Beta8
      14:41:10,747 INFO  [org.jboss.as] JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" starting
      14:41:11,091 INFO  [org.jboss.as.server] Activating core services
      14:41:11,175 INFO  [org.jboss.as] creating native management service using network interface (default) port (9999)
      14:41:11,181 INFO  [org.jboss.as] creating http management service using network interface (default) port (9990)
      14:41:11,196 INFO  [org.jboss.as.arquillian] Activating Arquillian Subsystem
      14:41:11,201 INFO  [org.jboss.as.ee] Activating EE subsystem
      14:41:11,234 INFO  [org.jboss.as.naming] Activating Naming Subsystem
      14:41:11,340 INFO  [org.jboss.as.connector.subsystems.datasources] Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
      14:41:11,348 INFO  [org.jboss.as.osgi] Activating OSGi Subsystem
      14:41:11,584 INFO  [org.jboss.as.webservices] Activating WebServices Extension
      14:41:11,663 ERROR [org.jboss.as.server] Boot update failed: "None of the following parameters were defined [input-stream-index, bytes, hash, url]."
      14:41:11,676 INFO  [org.jboss.as.naming] Starting Naming Service 
      14:41:11,679 INFO  [org.jboss.as.logging] Removing bootstrap log handlers
      14:41:11,689 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-16) Starting remote JMX connector
      14:41:11,701 INFO  [org.jboss.as.deployment] (MSC service thread 1-10) Started FileSystemDeploymentService for directory /home/carlo/work/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/standalone/deployments
      14:41:11,708 INFO  [org.jboss.wsf.common.management.AbstractServerConfig] (MSC service thread 1-11) JBoss Web Services - Stack CXF Server 4.0.0.Alpha4
      14:41:11,722 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 3.1.0.Beta2
      14:41:11,799 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting..
      14:41:11,802 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-9) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-sun-1.6.0.24/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.24/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.24/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
      14:41:11,831 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-14) Starting Coyote HTTP/1.1 on http-dwarf-127.0.0.1-8080
      14:41:11,850 INFO  [org.jboss.as.connector] (MSC service thread 1-9) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.Beta5)
      14:41:11,874 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) Bound JDBC Data-source [java:/H2DS]
      14:41:11,918 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.1.Final-r2319 dwarf:5455 for CORE protocol
      14:41:11,919 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.1.Final-r2319 dwarf:5445 for CORE protocol
      14:41:11,920 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
      14:41:11,986 INFO  [org.jboss.as] (MSC service thread 1-12) JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" started in 1545ms - Started 99 of 123 services (24 services are passive or on-demand)
      

      In a normal (80x24) terminal everything before 11,813 has scrolled away. So it appears to be a normal startup.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                wolfc Carlo de Wolf
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: