You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/12/14 11:26:45 UTC
[jira] Created: (GERONIMO-1360) Misleading error for missing web deployer
Misleading error for missing web deployer
-----------------------------------------
Key: GERONIMO-1360
URL: http://issues.apache.org/jira/browse/GERONIMO-1360
Project: Geronimo
Type: Bug
Components: deployment
Versions: 1.0
Reporter: Aaron Mulder
Fix For: 1.1
I recently experienced trouble deploying an ear file containing a war
module. After a lot of head scratching (and waste of Aaron's time) I
discovered that the source of the error was that the jetty-deployer
wasn't started.
The error returned by the deployer was "Module was not a war:
Adventure.war", which didn't help me a lot to say the least.
The error is printed from EARConfigBuilder.java in module j2ee-builder.
I'm on the 1.0 candidate build being voted about earlier today. Transcript [1] at
the bottom of this mail exposes the error.
I know that I'm partly to blame (the jetty-deployer is active in the
default configuration), but nonetheless someone might want to create a JIRA?
Kindly,
Jakob
----
Transcript [1]:
$ java -jar target/geronimo-1.0/bin/deployer.jar --user system
--password manager distribute target/plan/consumerwebsit
e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
Distributed org/apache/geronimo/Adventure1.0.1
~/projects/geronimo-ab/sandbox/adventurebuilder
$ java -jar target/geronimo-1.0/bin/deployer.jar --user system
--password manager stop geronimo/jetty-deployer/1.0/car
Stopped geronimo/jetty-deployer/1.0/car
~/projects/geronimo-ab/sandbox/adventurebuilder
$ java -jar target/geronimo-1.0/bin/deployer.jar --user system
--password manager distribute target/plan/consumerwebsit
e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
Error: Operation failed: Module was not a war: adventure.war
---
[2] Running configurations:
+ geronimo/activemq-broker/1.0/car
+ geronimo/j2ee-server/1.0/car
+ geronimo/jetty-deployer/1.0/car
+ geronimo/ldap-realm/1.0/car
+ geronimo/uddi-jetty/1.0/car
`-> uddi-jetty @ http://jrf:8080/juddi
`-> uddi-db
+ geronimo/online-deployer/1.0/car
+ geronimo/activemq/1.0/car
+ geronimo/directory/1.0/car
+ geronimo/j2ee-security/1.0/car
+ geronimo/j2ee-deployer/1.0/car
+ geronimo/system-database/1.0/car
+ geronimo/j2ee-system/1.0/car
+ geronimo/rmi-naming/1.0/car
+ geronimo/jetty/1.0/car
+ geronimo/webconsole-jetty/1.0/car
`-> geronimo-console-standard-1.0.war @
http://jrf:8080/console-standard
`-> geronimo-console-framework-1.0.war @ http://jrf:8080/console
+ geronimo/geronimo-gbean-deployer/1.0/car
--
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] Updated: (GERONIMO-1360) Misleading error for missing web
deployer
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1360?page=all ]
Aaron Mulder updated GERONIMO-1360:
-----------------------------------
Fix Version: 1.1
(was: 1.2)
Assign To: Aaron Mulder
Priority: Critical (was: Major)
Maybe the error message needs still more attention, and should present the option that the appropriate deployer is not active (or disabled if you're using the minimal tomcat install)
> Misleading error for missing web deployer
> -----------------------------------------
>
> Key: GERONIMO-1360
> URL: http://issues.apache.org/jira/browse/GERONIMO-1360
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.1
>
> I recently experienced trouble deploying an ear file containing a war
> module. After a lot of head scratching (and waste of Aaron's time) I
> discovered that the source of the error was that the jetty-deployer
> wasn't started.
> The error returned by the deployer was "Module was not a war:
> Adventure.war", which didn't help me a lot to say the least.
> The error is printed from EARConfigBuilder.java in module j2ee-builder.
> I'm on the 1.0 candidate build being voted about earlier today. Transcript [1] at
> the bottom of this mail exposes the error.
> I know that I'm partly to blame (the jetty-deployer is active in the
> default configuration), but nonetheless someone might want to create a JIRA?
> Kindly,
> Jakob
> ----
> Transcript [1]:
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Distributed org/apache/geronimo/Adventure1.0.1
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager stop geronimo/jetty-deployer/1.0/car
> Stopped geronimo/jetty-deployer/1.0/car
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Error: Operation failed: Module was not a war: adventure.war
> ---
> [2] Running configurations:
> + geronimo/activemq-broker/1.0/car
> + geronimo/j2ee-server/1.0/car
> + geronimo/jetty-deployer/1.0/car
> + geronimo/ldap-realm/1.0/car
> + geronimo/uddi-jetty/1.0/car
> `-> uddi-jetty @ http://jrf:8080/juddi
> `-> uddi-db
> + geronimo/online-deployer/1.0/car
> + geronimo/activemq/1.0/car
> + geronimo/directory/1.0/car
> + geronimo/j2ee-security/1.0/car
> + geronimo/j2ee-deployer/1.0/car
> + geronimo/system-database/1.0/car
> + geronimo/j2ee-system/1.0/car
> + geronimo/rmi-naming/1.0/car
> + geronimo/jetty/1.0/car
> + geronimo/webconsole-jetty/1.0/car
> `-> geronimo-console-standard-1.0.war @
> http://jrf:8080/console-standard
> `-> geronimo-console-framework-1.0.war @ http://jrf:8080/console
> + geronimo/geronimo-gbean-deployer/1.0/car
--
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-1360) Misleading error for missing web
deployer
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1360?page=all ]
Aaron Mulder resolved GERONIMO-1360:
------------------------------------
Resolution: Fixed
Patch applied, thanks
> Misleading error for missing web deployer
> -----------------------------------------
>
> Key: GERONIMO-1360
> URL: http://issues.apache.org/jira/browse/GERONIMO-1360
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.1
> Attachments: 1360-missing-deployer-error-msg.patch
>
> I recently experienced trouble deploying an ear file containing a war
> module. After a lot of head scratching (and waste of Aaron's time) I
> discovered that the source of the error was that the jetty-deployer
> wasn't started.
> The error returned by the deployer was "Module was not a war:
> Adventure.war", which didn't help me a lot to say the least.
> The error is printed from EARConfigBuilder.java in module j2ee-builder.
> I'm on the 1.0 candidate build being voted about earlier today. Transcript [1] at
> the bottom of this mail exposes the error.
> I know that I'm partly to blame (the jetty-deployer is active in the
> default configuration), but nonetheless someone might want to create a JIRA?
> Kindly,
> Jakob
> ----
> Transcript [1]:
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Distributed org/apache/geronimo/Adventure1.0.1
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager stop geronimo/jetty-deployer/1.0/car
> Stopped geronimo/jetty-deployer/1.0/car
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Error: Operation failed: Module was not a war: adventure.war
> ---
> [2] Running configurations:
> + geronimo/activemq-broker/1.0/car
> + geronimo/j2ee-server/1.0/car
> + geronimo/jetty-deployer/1.0/car
> + geronimo/ldap-realm/1.0/car
> + geronimo/uddi-jetty/1.0/car
> `-> uddi-jetty @ http://jrf:8080/juddi
> `-> uddi-db
> + geronimo/online-deployer/1.0/car
> + geronimo/activemq/1.0/car
> + geronimo/directory/1.0/car
> + geronimo/j2ee-security/1.0/car
> + geronimo/j2ee-deployer/1.0/car
> + geronimo/system-database/1.0/car
> + geronimo/j2ee-system/1.0/car
> + geronimo/rmi-naming/1.0/car
> + geronimo/jetty/1.0/car
> + geronimo/webconsole-jetty/1.0/car
> `-> geronimo-console-standard-1.0.war @
> http://jrf:8080/console-standard
> `-> geronimo-console-framework-1.0.war @ http://jrf:8080/console
> + geronimo/geronimo-gbean-deployer/1.0/car
--
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] Updated: (GERONIMO-1360) Misleading error for missing web
deployer
Posted by "Erin Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1360?page=all ]
Erin Mulder updated GERONIMO-1360:
----------------------------------
Attachment: 1360-missing-deployer-error-msg.patch
This patch changes the error message to the following:
"Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed."
Kind of wordy, but gives more guidance than the old message.
> Misleading error for missing web deployer
> -----------------------------------------
>
> Key: GERONIMO-1360
> URL: http://issues.apache.org/jira/browse/GERONIMO-1360
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.1
> Attachments: 1360-missing-deployer-error-msg.patch
>
> I recently experienced trouble deploying an ear file containing a war
> module. After a lot of head scratching (and waste of Aaron's time) I
> discovered that the source of the error was that the jetty-deployer
> wasn't started.
> The error returned by the deployer was "Module was not a war:
> Adventure.war", which didn't help me a lot to say the least.
> The error is printed from EARConfigBuilder.java in module j2ee-builder.
> I'm on the 1.0 candidate build being voted about earlier today. Transcript [1] at
> the bottom of this mail exposes the error.
> I know that I'm partly to blame (the jetty-deployer is active in the
> default configuration), but nonetheless someone might want to create a JIRA?
> Kindly,
> Jakob
> ----
> Transcript [1]:
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Distributed org/apache/geronimo/Adventure1.0.1
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager stop geronimo/jetty-deployer/1.0/car
> Stopped geronimo/jetty-deployer/1.0/car
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Error: Operation failed: Module was not a war: adventure.war
> ---
> [2] Running configurations:
> + geronimo/activemq-broker/1.0/car
> + geronimo/j2ee-server/1.0/car
> + geronimo/jetty-deployer/1.0/car
> + geronimo/ldap-realm/1.0/car
> + geronimo/uddi-jetty/1.0/car
> `-> uddi-jetty @ http://jrf:8080/juddi
> `-> uddi-db
> + geronimo/online-deployer/1.0/car
> + geronimo/activemq/1.0/car
> + geronimo/directory/1.0/car
> + geronimo/j2ee-security/1.0/car
> + geronimo/j2ee-deployer/1.0/car
> + geronimo/system-database/1.0/car
> + geronimo/j2ee-system/1.0/car
> + geronimo/rmi-naming/1.0/car
> + geronimo/jetty/1.0/car
> + geronimo/webconsole-jetty/1.0/car
> `-> geronimo-console-standard-1.0.war @
> http://jrf:8080/console-standard
> `-> geronimo-console-framework-1.0.war @ http://jrf:8080/console
> + geronimo/geronimo-gbean-deployer/1.0/car
--
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] Updated: (GERONIMO-1360) Misleading error for missing web
deployer
Posted by "Erin Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1360?page=all ]
Erin Mulder updated GERONIMO-1360:
----------------------------------
Patch Info: [Patch Available]
> Misleading error for missing web deployer
> -----------------------------------------
>
> Key: GERONIMO-1360
> URL: http://issues.apache.org/jira/browse/GERONIMO-1360
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.1
> Attachments: 1360-missing-deployer-error-msg.patch
>
> I recently experienced trouble deploying an ear file containing a war
> module. After a lot of head scratching (and waste of Aaron's time) I
> discovered that the source of the error was that the jetty-deployer
> wasn't started.
> The error returned by the deployer was "Module was not a war:
> Adventure.war", which didn't help me a lot to say the least.
> The error is printed from EARConfigBuilder.java in module j2ee-builder.
> I'm on the 1.0 candidate build being voted about earlier today. Transcript [1] at
> the bottom of this mail exposes the error.
> I know that I'm partly to blame (the jetty-deployer is active in the
> default configuration), but nonetheless someone might want to create a JIRA?
> Kindly,
> Jakob
> ----
> Transcript [1]:
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Distributed org/apache/geronimo/Adventure1.0.1
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager stop geronimo/jetty-deployer/1.0/car
> Stopped geronimo/jetty-deployer/1.0/car
> ~/projects/geronimo-ab/sandbox/adventurebuilder
> $ java -jar target/geronimo-1.0/bin/deployer.jar --user system
> --password manager distribute target/plan/consumerwebsit
> e1.0.1.ear-plan.xml adventure1.0.3/consumerwebsite.ear
> Error: Operation failed: Module was not a war: adventure.war
> ---
> [2] Running configurations:
> + geronimo/activemq-broker/1.0/car
> + geronimo/j2ee-server/1.0/car
> + geronimo/jetty-deployer/1.0/car
> + geronimo/ldap-realm/1.0/car
> + geronimo/uddi-jetty/1.0/car
> `-> uddi-jetty @ http://jrf:8080/juddi
> `-> uddi-db
> + geronimo/online-deployer/1.0/car
> + geronimo/activemq/1.0/car
> + geronimo/directory/1.0/car
> + geronimo/j2ee-security/1.0/car
> + geronimo/j2ee-deployer/1.0/car
> + geronimo/system-database/1.0/car
> + geronimo/j2ee-system/1.0/car
> + geronimo/rmi-naming/1.0/car
> + geronimo/jetty/1.0/car
> + geronimo/webconsole-jetty/1.0/car
> `-> geronimo-console-standard-1.0.war @
> http://jrf:8080/console-standard
> `-> geronimo-console-framework-1.0.war @ http://jrf:8080/console
> + geronimo/geronimo-gbean-deployer/1.0/car
--
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