You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Nell Gawor (JIRA)" <de...@geronimo.apache.org> on 2005/11/22 15:56:43 UTC

[jira] Created: (GERONIMO-1218) deploy command cannot be run when server is stopped as help indicates

deploy command cannot be run when server is stopped as help indicates
---------------------------------------------------------------------

         Key: GERONIMO-1218
         URL: http://issues.apache.org/jira/browse/GERONIMO-1218
     Project: Geronimo
        Type: Bug
  Components: deployment  
    Versions: 1.0-M5    
 Environment: Windows 2000
    Reporter: Nell Gawor


I'm not 100% sure if this is a documentation problem or a deployment problem, but I'm pretty sure its just a documentation problem.  When running

java -jar deployer.jar help deploy

The help says:

"If the server is not currently running, the module will be
marked to start next time the server is started."

Trying to actually run
java -jar deployer.jar deploy hello.war

when the server is not started starts the offline deployer and complains

09:50:56,736 INFO  [SecurityServiceImpl] JACC factory registered
    Error: This command cannot be run unless connecting to a running
    server.  Specify --url if server is not running on the default port
    on localhost.

Using distribute instead works as expected.

-- 
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


[jira] Commented: (GERONIMO-1218) deploy command cannot be run when server is stopped as help indicates

Posted by "Nell Gawor (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-1218?page=comments#action_12358259 ] 

Nell Gawor commented on GERONIMO-1218:
--------------------------------------

The same issue also exists with the redeploy help documentation. It says:

"Regardless of whether the old module was running or not, the new
module will be started (if the server is running) or marked to
start (if the server is not running)."

but redeploy fails when the server is not running.

> deploy command cannot be run when server is stopped as help indicates
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-1218
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1218
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M5
>  Environment: Windows 2000
>     Reporter: Nell Gawor

>
> I'm not 100% sure if this is a documentation problem or a deployment problem, but I'm pretty sure its just a documentation problem.  When running
> java -jar deployer.jar help deploy
> The help says:
> "If the server is not currently running, the module will be
> marked to start next time the server is started."
> Trying to actually run
> java -jar deployer.jar deploy hello.war
> when the server is not started starts the offline deployer and complains
> 09:50:56,736 INFO  [SecurityServiceImpl] JACC factory registered
>     Error: This command cannot be run unless connecting to a running
>     server.  Specify --url if server is not running on the default port
>     on localhost.
> Using distribute instead works as expected.

-- 
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


[jira] Resolved: (GERONIMO-1218) deploy command cannot be run when server is stopped as help indicates

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1218?page=all ]
     
Aaron Mulder resolved GERONIMO-1218:
------------------------------------

    Fix Version: 1.0
     Resolution: Fixed
      Assign To: Aaron Mulder

Fixed in HEAD (355915) and 1.0 branch (355916)

> deploy command cannot be run when server is stopped as help indicates
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-1218
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1218
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M5
>  Environment: Windows 2000
>     Reporter: Nell Gawor
>     Assignee: Aaron Mulder
>      Fix For: 1.0

>
> I'm not 100% sure if this is a documentation problem or a deployment problem, but I'm pretty sure its just a documentation problem.  When running
> java -jar deployer.jar help deploy
> The help says:
> "If the server is not currently running, the module will be
> marked to start next time the server is started."
> Trying to actually run
> java -jar deployer.jar deploy hello.war
> when the server is not started starts the offline deployer and complains
> 09:50:56,736 INFO  [SecurityServiceImpl] JACC factory registered
>     Error: This command cannot be run unless connecting to a running
>     server.  Specify --url if server is not running on the default port
>     on localhost.
> Using distribute instead works as expected.

-- 
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


[jira] Commented: (GERONIMO-1218) deploy command cannot be run when server is stopped as help indicates

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-1218?page=comments#action_12358261 ] 

Aaron Mulder commented on GERONIMO-1218:
----------------------------------------

I think at this point it's a documentation problem.  We've backed off allowing much while the server is not running.  I'm open to reconsidering if people think this is valuable -- I think the main difference for deploy is that we have to be able to alter the runtime persistent configuration list, and for redeploy we have to be able to do that plus undeploy.

Note that you can achieve a similar thing by copying your WAR into the hot deploy directory.  The difference is that it won't actually be deployed until the server is running, so we can be sure that the server environment is set up properly before starting the deploy process.

> deploy command cannot be run when server is stopped as help indicates
> ---------------------------------------------------------------------
>
>          Key: GERONIMO-1218
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1218
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M5
>  Environment: Windows 2000
>     Reporter: Nell Gawor

>
> I'm not 100% sure if this is a documentation problem or a deployment problem, but I'm pretty sure its just a documentation problem.  When running
> java -jar deployer.jar help deploy
> The help says:
> "If the server is not currently running, the module will be
> marked to start next time the server is started."
> Trying to actually run
> java -jar deployer.jar deploy hello.war
> when the server is not started starts the offline deployer and complains
> 09:50:56,736 INFO  [SecurityServiceImpl] JACC factory registered
>     Error: This command cannot be run unless connecting to a running
>     server.  Specify --url if server is not running on the default port
>     on localhost.
> Using distribute instead works as expected.

-- 
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