Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2149484.1118753089879.JavaMail.jira@ajax.apache.org>
Date: Tue, 14 Jun 2005 14:44:49 +0200 (CEST)
From: "Jacek Laskowski (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Resolved: (GERONIMO-671) Error: Deployment failed,
 Server reports: No deployer present in kernel
In-Reply-To: <815725599.1118613166267.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-671?page=all ]
     
Jacek Laskowski resolved GERONIMO-671:
--------------------------------------

    Fix Version: 1.0-M4
     Resolution: Fixed

Ok, I've finally got the better understanding why it happens. It's because the deployer tries to connect to a running Geronimo instance that accepts requests for deployer:geronimo:jmx:rmi://localhost/jndi/rmi:/JMXConnector. Depending on a running configuration (e.g. org/apache/geronimo/Server) it might not (and in many cases does not) contain the Deployer (the GBean with the name: *:name=Deployer,j2eeType=Deployer,*). There're two solutions to the issue:

  * (the most obvious one) to shut down the running instance

or

  * (the better one that leverages Geronimo configuration concept) to run the org/apache/geronimo/RuntimeDeployer together with your own configuration (your own application)

For the completeness' sake here's the scenario that the issue will show up.

1/ Run org/apache/geronimo/Server (or any configuration that doesn't contain the Deployer GBean - consult the available plans, i.e. grep -l Deployer src/plan/*.xml)
2/ Deploy your application (webapp, ejb, rar or anything else)
... it finishes with the error..
3/ Stop Geronimo
4/ Now it's up to you if you want to run both, your configuration and RuntimeDeployer or run nothing
5/ Deploy your application - it finishes without any troubles

org/apache/geronimo/deployment/plugin/local/AbstractDeployCommand.java of the deploy-tool module has been patched (see revision 190584) so that the error message would tell a bit more on the root cause of the error with a reference to this issue report:

   Error: Deployment failed, Server reports: No Deployer GBean present
   in running Geronimo kernel. The Deployer GBean would've been started
   up automatically if there hadn't been a Geronimo instance up
   already. Stop the running instance and run the deployer again or see
   http://issues.apache.org/jira/browse/GERONIMO-671 for possible
   alternatives

> Error: Deployment failed, Server reports: No deployer present in kernel
> -----------------------------------------------------------------------
>
>          Key: GERONIMO-671
>          URL: http://issues.apache.org/jira/browse/GERONIMO-671
>      Project: Geronimo
>         Type: Improvement
>   Components: deployment
>     Versions: 1.0-M4
>     Reporter: Jacek Laskowski
>     Assignee: Jacek Laskowski
>     Priority: Minor
>      Fix For: 1.0-M4

>
> It happens when the deployer is invoked from within the Netbeans module I'm working on. It distributes a webapp without any Geronimo-specific DDs. Before the distribute command is executed, Netbeans starts up Geronimo (it's configured to run org/apache/geronimo/Server). It's a rudimentary integration since it uses bin/deployer.jar.
> $ java -jar bin/deployer.jar --user system --password manager distribute C\:/Temp/WebApplication1/dist/WebApplication1.war
>     Error: Deployment failed, Server reports: No deployer present in
>     kernel

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira