3 Replies Latest reply on Jan 30, 2007 11:20 AM by Peter Johnson

    Deployment on custom server

    Raju B Newbie

      When I try to deploy an EAR on JBoss custom server (not default server), I get all kinds of exceptions. The deployment works fine on default server.

      I guess I need to copy some xml/JAR files from default to custom server but I don't know which ones. Can anyone help me?

        • 1. Re: Deployment on custom server
          Peter Johnson Master

          Based on the information you have provided, the solution is to deploy to default since that works.

          But seriously, we cannot help you if you don't tell us what the problem is, and saying 'I changed some stuff and now get exceptions' is not telling us about the problem. So provide the following:

          1) How did you create your custom configuration? Via the installer? If so, what options did you select? If you started with one of the standard configurations (all, default, minimal) and added/removed files, what did you start with and what did you remove?

          2) What exceptions are you getting? Usually you need to look only at the first exception, and its 'caused by' exception, if there is one.

          • 2. Re: Deployment on custom server
            Raju B Newbie

            My original intent was to use only Messaging. So I did the following to create a "standalone-messaging" server.

            1) Extracted jboss-4.0.4.GA.zip to C:\java folder
            2) Extracted jboss-messaging-1.0.1.GA.zip C:\java folder.
            3) Extracted apache-ant-1.6.5-bin.zip to C:\java
            4) Opened a command prompt and did the following:
            cd C:\java\jboss-messaging-1.0.1.GA\util
            set JBOSS_HOME=C:\java\jboss-4.0.4.GA
            C:\java\apache-ant-1.6.5\bin\ant -f release-admin.xml standalone

            Now, when I tried to deploy an EAR to "standalone-messaging" server (I did not remove any files), I received the following exception:

            2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
            2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
            2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
            2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] Deployment of package: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear is waiting for an appropriate deployer.
            2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear -> file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
            2007-01-30 11:03:56,697 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

            --- Packages waiting for a deployer ---
            org.jboss.deployment.DeploymentInfo@c94153c9 { url=file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
            altDD: null
            lastDeployed: 1170173036697
            lastModified: 1170173036697
            mbeans:

            --- Incompletely deployed packages ---
            org.jboss.deployment.DeploymentInfo@c94153c9 { url=file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
            altDD: null
            lastDeployed: 1170173036697
            lastModified: 1170173036697
            mbeans:


            2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true
            2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Started jboss.deployment:flavor=URL,type=DeploymentScanner
            2007-01-30 11:03:56,728 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.deployment:flavor=URL,type=DeploymentScanner dependent components: []
            2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml
            2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/conf/jboss-service.xml
            2007-01-30 11:03:56,728 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Saw org.jboss.system.server.started notification, starting connectors





            • 3. Re: Deployment on custom server
              Peter Johnson Master

              That explains it. The standalone messaging server supports only JMS, and thus only messaging clients. It does not support EAR files, nor EJBs.