[jira] Created: (GERONIMO-3696) Tomcat Clustering over WADI
Tomcat Clustering over WADI --- Key: GERONIMO-3696 URL: https://issues.apache.org/jira/browse/GERONIMO-3696 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Clustering Affects Versions: 2.0.2 Reporter: Gianny Damour Assignee: Gianny Damour Fix For: 2.1 Users should be able to cluster Tomcat web-applications the same way they are doing it with Jetty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Minimal server startup issue
On Dec 10, 2007, at 9:12 PM, Gianny Damour wrote: Hi, Thanks for having fixed this problem David. I may have introduced this bug while working on the property editor stuff. So, I will have a look at it and see if we can avoid this explicit registration of property editors. I recall this problem from long long ago. I think it has reappeared when I started constructing the config.xml files and they are no longer in order of expected module startup. I thought of a couple other possible solutions such as ordering the configs in config.xml according to the dependencies, but we'd still be relying on more or less accidental behavior, namely a particular gbean having its gbeanInfo loaded before any attributes needing the property editor are loaded. I think explicitly calling out the property editor to be used is a much more satisfactory solution. Even though you didn't cause the problem you might be able to think of a better way to fix it :-) thanks david jencks Thanks, Gianny On 11/12/2007, at 1:14 PM, David Jencks wrote: Jarek found a startup ordering issue in the minimal servers that I solved by explicitly specifying the property editor for the defaultEnvironment attributes. Rev. 603109. thanks david jencks
[jira] Closed: (GERONIMO-3696) Tomcat Clustering over WADI
[ https://issues.apache.org/jira/browse/GERONIMO-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gianny Damour closed GERONIMO-3696. --- Resolution: Fixed This is now implemented. Tomcat Clustering over WADI --- Key: GERONIMO-3696 URL: https://issues.apache.org/jira/browse/GERONIMO-3696 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.0.2 Reporter: Gianny Damour Assignee: Gianny Damour Fix For: 2.1 Users should be able to cluster Tomcat web-applications the same way they are doing it with Jetty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Release Genesis 1.3
Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
[jira] Updated: (GERONIMO-1711) WebServer Connectors portlet should provide a restart option for connectors
[ https://issues.apache.org/jira/browse/GERONIMO-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-1711: -- Affects Version/s: 2.1 2.0.x Fix Version/s: (was: Wish List) 2.1 2.0.x WebServer Connectors portlet should provide a restart option for connectors - Key: GERONIMO-1711 URL: https://issues.apache.org/jira/browse/GERONIMO-1711 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.1, 1.2, 2.0.x, 2.1 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Priority: Minor Fix For: 2.0.x, 2.1 WebServer Connectors portlet currently provides start, stop, edit and delete options. It does not provide a restart option for connectors that is already running. If any properties are edited, the changes are not reflected until the connector is stopped and started again. If one has to depend on this stop and start options clicked in succession, the admin console may not be accessible as soon as the connector is stopped and there is no way of issuing a start from admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1711) WebServer Connectors portlet should provide a restart option for connectors
[ https://issues.apache.org/jira/browse/GERONIMO-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy closed GERONIMO-1711. - Resolution: Fixed Completed: At revision: 603211 in branches\2.0 and trunk. o Added a restart action for connectors WebServer Connectors portlet should provide a restart option for connectors - Key: GERONIMO-1711 URL: https://issues.apache.org/jira/browse/GERONIMO-1711 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 1.1, 1.2, 2.0.x, 2.1 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Priority: Minor Fix For: 2.0.x, 2.1 WebServer Connectors portlet currently provides start, stop, edit and delete options. It does not provide a restart option for connectors that is already running. If any properties are edited, the changes are not reflected until the connector is stopped and started again. If one has to depend on this stop and start options clicked in succession, the admin console may not be accessible as soon as the connector is stopped and there is no way of issuing a start from admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Clustering of Tomcat Web-applications over WADI
Hi, I have just checked in support for clustering of Tomcat Web- applications over WADI. This works pretty much the same way Jetty Web- applications are clustered over WADI. For instance, to cluster a Tomcat Web-app, a tomcat-clustering-wadi element, see geronimo-tomcat-clustering-wadi-1.2.xsd for more details, is added to the Geronimo tomcat deployment descriptor, e.g.: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2; environment moduleId groupIdgroupId/groupId artifactIdartifactId/artifactId version2.0/version typewar/type /moduleId /environment tomcat-clustering-wadi / // this is the element I am referring to /web-app The presence of this element along with a distributable element in the standard DD triggers the build of the Web-application as a clustered application. I am now working on the clustering of SFSB over WADI. If people wants to work on load-time weaving of AspectJ aspects at the Tomcat or Jetty Web-application scope to tightly integrate the field or method level state tracking mechanism of WADI, then please feel free to ping me. This would be my next task after the clustering of SFSB and I could use some helps. Thanks, Gianny
Re: [VOTE] Release Genesis 1.3
+1 On Dec 11, 2007 10:58 AM, Jason Dillon [EMAIL PROTECTED] wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Created: (GERONIMO-3697) Monitoring Console fix ups
Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Unable to commit
Folks, am unable to commit this morning. Does anyone know why? My password, I have not forgotten it, is not being accepted. Thanks Anita Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
Re: [VOTE] Release Genesis 1.3
+0 ++Vamsi On Dec 11, 2007 5:22 PM, Guillaume Nodet [EMAIL PROTECTED] wrote: +1 On Dec 11, 2007 10:58 AM, Jason Dillon [EMAIL PROTECTED] wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: Unable to commit
Sorry for the fuss... I used a different user name :(. I need to wake up. Going to get some tea... Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: Folks, am unable to commit this morning. Does anyone know why? My password, I have not forgotten it, is not being accepted. Thanks Anita Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
[jira] Commented: (GERONIMO-3678) Monitoring console should accept a port no for server to be monitored
[ https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550439 ] Anita Kulshreshtha commented on GERONIMO-3678: -- Rev 603235, Removed SQL to populate DB with the default data. Monitoring console should accept a port no for server to be monitored - Key: GERONIMO-3678 URL: https://issues.apache.org/jira/browse/GERONIMO-3678 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3678.patch Currently the Monitoring Console accepts an IP address for the server to be monitored. This works for default geronimo instances. For non default installations we need to be able to specify the EJB port.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Genesis 1.3
+1 Jason Dillon wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
[jira] Created: (GERONIMO-3698) Installation of Admin Console fails with missing dependency
Installation of Admin Console fails with missing dependency --- Key: GERONIMO-3698 URL: https://issues.apache.org/jira/browse/GERONIMO-3698 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Plugins Affects Versions: 2.1 Reporter: Kevan Miller Fix For: 2.1 Installation of the Jetty admin console fails with a missing dependency. Starting with a framework assembly, I installed the Jetty Admin Console: 6: Geronimo Plugins :: Administration Console - Jetty (2.1-SNAPSHOT) The installation fails with a missing dependency for: org.apache.geronimo.configs/jetty6/2.1-SNAPSHOT/car The installation works if I first install the jetty6 plugin. Here's the full failure info: Install Services [enter a comma separated list of numbers or 'q' to quit]: 6 Checking for status every 1000ms: Downloading org.apache.geronimo.plugins/console-jetty/2.1-SNAPSHOT/car Copying commons-collections/commons-collections/3.1/jar to the repository (100%) Downloading org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car Downloading org.apache.geronimo.modules/geronimo-client/2.1-SNAPSHOT/jar 320 kB of org.apache.tomcat/jasper-jdt/6.0.13/jar Starting org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car Installation Complete! Used existing: org.apache.geronimo.configs/jee-specs/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.modules/geronimo-core/2.1-SNAPSHOT/jar Used existing: org.apache.geronimo.modules/geronimo-common/2.1-SNAPSHOT/jar Used existing: org.apache.geronimo.modules/geronimo-management/2.1-SNAPSHOT/jar Used existing: asm/asm/2.2.3/jar Used existing: asm/asm-commons/2.2.3/jar Used existing: org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.modules/geronimo-deploy-jsr88/2.1-SNAPSHOT/jar Used existing: org.apache.geronimo.configs/server-security-config/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.modules/geronimo-transformer/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.plugins/pluto-support/2.1-SNAPSHOT/car Installed new: org.apache.pluto/pluto-portal-driver/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-portal-driver-impl/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-container/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-descriptor-api/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-descriptor-impl/1.2.0-G601060/jar Installed new: commons-logging/commons-logging-api/1.0.4/jar Installed new: commons-beanutils/commons-beanutils/1.6.1/jar Installed new: commons-collections/commons-collections/3.1/jar Installed new: javax.portlet/portlet-api/1.0/jar Installed new: org.apache.geronimo.configs/spring/2.1-SNAPSHOT/car Installed new: org.springframework/spring-core/2.0.5/jar Installed new: org.springframework/spring-beans/2.0.5/jar Installed new: org.springframework/spring-context/2.0.5/jar Installed new: org.springframework/spring-web/2.0.5/jar Installed new: org.codehaus.castor/castor/1.0.5/jar Installed new: org.apache.geronimo.plugins/geronimo-pluto/2.1-SNAPSHOT/jar Installed new: org.apache.pluto/pluto-taglib/1.2.0-G601060/jar Installed new: commons-digester/commons-digester/1.8/jar Installed new: org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car Installed new: org.apache.geronimo.modules/geronimo-j2ee-schema/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.schema/geronimo-schema-jee_5/1.1/jar Installed new: org.apache.geronimo.schema/geronimo-schema-j2ee_1.4/1.2/jar Installed new: org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car Installed new: org.apache.geronimo.modules/geronimo-j2ee/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-webservices/2.1-SNAPSHOT/jar Installed new: org.apache.xbean/xbean-reflect/3.2/jar Installed new: org.apache.geronimo.modules/geronimo-test-ddbean/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-naming-builder/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-security-builder/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-j2ee-builder/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-client/2.1-SNAPSHOT/jar Installed new: org.apache.xbean/xbean-finder/3.2/jar Installed new: org.apache.geronimo.modules/geronimo-web-2.5-builder/2.1-SNAPSHOT/jar Installed new: commons-fileupload/commons-fileupload/1.1.1/jar Installed new: commons-io/commons-io/1.1/jar Installed new: org.apache.geronimo.plugins/console-core/2.1-SNAPSHOT/jar Installed new: org.directwebremoting/dwr/2.0.1/jar Installed new: org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car Installed new: org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car
[BUILD] 2.0: Failed for Revision: 603232
Geronimo Revision: 603232 built with tests included See the full build-0800.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/build-0800.log Download the binaries from http://people.apache.org/~prasad/binaries/2.0/20071211 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 25 minutes 48 seconds [INFO] Finished at: Tue Dec 11 08:31:22 EST 2007 [INFO] Final Memory: 267M/867M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/~prasad/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/logs-0800-tomcat/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 158.079 sec FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/logs-0800-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 155.592 sec FAILURE!
jira 404's
Is anybody else having problems with Jira? When I create a Geronimo Jira, I get the following 404: HTTP Status 404 - No view for result [error] exists for action [ViewIssue] type Status report message No view for result [error] exists for action [ViewIssue] description The requested resource (No view for result [error] exists for action [ViewIssue]) is not available. Apache Tomcat/5.5.20
structure of GShell commands
We currently have the following structure for Geronimo GShell commands: geronimo/ start-server stop-server start-client deploy/ install-library disconnect deploy ... This doesn't make much sense to me. Let's either assume GShell is used for Geronimo server or assume that GShell can be used for multiple target environments, but not both... I think the current deploy/ commands should be under the geronimo tree. What do others think? I think applying a bit more structure, now, will minimize entropy over time... Anybody want to have a shot at proposing a command structure? --kevan
Re: svn commit: r603211 - in /geronimo/server: branches/2.0/applications/console/geronimo-console-standard/src/main/java/org/apache/geronimo/console/webmanager/ branches/2.0/applications/console/geron
Vamsi,
Please run the console testsuites. I believe this change is causing
failures in trunk and branches/2.0.
Jarek
On Dec 11, 2007 6:29 AM, [EMAIL PROTECTED] wrote:
Author: vamsic007
Date: Tue Dec 11 03:29:36 2007
New Revision: 603211
URL: http://svn.apache.org/viewvc?rev=603211view=rev
Log:
GERONIMO-1711 WebServer Connectors portlet should provide a restart option
for connectors
o Added a restart action for connectors
Modified:
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/java/org/apache/geronimo/console/webmanager/ConnectorPortlet.java
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp
geronimo/server/trunk/plugins/console/console-base-portlets/src/main/java/org/apache/geronimo/console/webmanager/ConnectorPortlet.java
geronimo/server/trunk/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp
Modified:
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/java/org/apache/geronimo/console/webmanager/ConnectorPortlet.java
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/java/org/apache/geronimo/console/webmanager/ConnectorPortlet.java?rev=603211r1=603210r2=603211view=diff
==
---
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/java/org/apache/geronimo/console/webmanager/ConnectorPortlet.java
(original)
+++
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/java/org/apache/geronimo/console/webmanager/ConnectorPortlet.java
Tue Dec 11 03:29:36 2007
@@ -52,7 +52,7 @@
import org.apache.geronimo.management.geronimo.WebManager.ConnectorType;
/**
- * A portlet that lets you list, add, remove, start, stop, and edit web
+ * A portlet that lets you list, add, remove, start, stop, restart and edit
web
* connectors (currently, either Tomcat or Jetty).
*
* @version $Rev$ $Date$
@@ -223,6 +223,22 @@
}
}
else {
+log.error(Incorrect connector reference); //Replace this
with correct error processing
+}
+actionResponse.setRenderParameter(PARM_CONNECTOR_URI,
connectorURI);
+actionResponse.setRenderParameter(PARM_MODE, list);
+} else if(mode.equals(restart)) {
+String connectorURI =
actionRequest.getParameter(PARM_CONNECTOR_URI);
+// work with the current connector to restart it.
+NetworkConnector connector =
PortletManager.getNetworkConnector(actionRequest, new
AbstractName(URI.create(connectorURI)));
+if(connector != null) {
+try {
+((GeronimoManagedBean)connector).stop();
+((GeronimoManagedBean)connector).start();
+} catch (Exception e) {
+log.error(Unable to restart connector, e); //todo: get
into rendered page somehow?
+}
+} else {
log.error(Incorrect connector reference); //Replace this
with correct error processing
}
actionResponse.setRenderParameter(PARM_CONNECTOR_URI,
connectorURI);
Modified:
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp?rev=603211r1=603210r2=603211view=diff
==
---
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp
(original)
+++
geronimo/server/branches/2.0/applications/console/geronimo-console-standard/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp
Tue Dec 11 03:29:36 2007
@@ -14,6 +14,9 @@
See the License for the specific language governing permissions and
limitations under the License.
--%
+
+%-- $Rev$ $Date$ --%
+
%@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c %
%@ taglib uri=http://java.sun.com/jsp/jstl/functions; prefix=fn %
%@ taglib uri=http://java.sun.com/portlet; prefix=portlet%
@@ -63,6 +66,14 @@
/portlet:actionURL
c:if test=${info.port eq serverPort} onClick=return
confirm('Console application will not be available if ${info.uniqueName} is
stopped. Stop ${info.uniqueName}?');/c:if
stop/a
+ a href=portlet:actionURL portletMode=view
+ portlet:param name=mode value=restart /
+
[jira] Created: (GSHELL-95) format of help command is confusing (or command processing is wrong)
format of help command is confusing (or command processing is wrong) Key: GSHELL-95 URL: https://issues.apache.org/jira/browse/GSHELL-95 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Components: CLI Affects Versions: 1.0-alpha-1 Reporter: Kevan Miller Assignee: Jason Dillon Fix For: 1.0-alpha-1 The formatting of available commands displayed by the help command is confusing. For instance /remote rsh-server Start a GShell server rsh Connect to a remote GShell server '/remote' implies that the command is: '/remote/rsh-server'. it is actually: 'remote/rsh-server' The following would be more intuitive, I think. Pretty sure somebody can improve on this, also... ;-) remote/ rsh-serverStart a GShell server rsh Connect to a remote GShell server The help command should make hierarchical structure of commands more obvious. Are there plans (or something I haven't realized, yet) for some sort of command navigation? e.g.: cd geronimo start-server -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3693) monitoring client does not perform operations correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3693. Resolution: Fixed Fix Version/s: 2.1 monitoring client does not perform operations correctly --- Key: GERONIMO-3693 URL: https://issues.apache.org/jira/browse/GERONIMO-3693 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.1 Attachments: geronimo-3693.patch Currently the second operand value is not being pulled from the mrc-server, instead there the second operand value is being assigned the first operand value. Additionally, the javascript that is generated from StatsGraph.java does not check to see if there is a division by zero. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-96) alias command fails
alias command fails --- Key: GSHELL-96 URL: https://issues.apache.org/jira/browse/GSHELL-96 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Reporter: Kevan Miller Assignee: Jason Dillon Running the alias command fails with an IllegalStateException: [EMAIL PROTECTED]:/ alias ERROR IllegalStateException: Alias file /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml does not exist Could be that Geronimo should be including this file in assemblies, or gshell should create (if not present), or something else is wrong... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-95) format of help command is confusing (or command processing is wrong)
[ https://issues.apache.org/jira/browse/GSHELL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GSHELL-95. -- Resolution: Duplicate duplicate of GSHELL-86 I think we need to clean up the help command for release format of help command is confusing (or command processing is wrong) Key: GSHELL-95 URL: https://issues.apache.org/jira/browse/GSHELL-95 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Components: CLI Affects Versions: 1.0-alpha-1 Reporter: Kevan Miller Assignee: Jason Dillon Fix For: 1.0-alpha-1 The formatting of available commands displayed by the help command is confusing. For instance /remote rsh-server Start a GShell server rsh Connect to a remote GShell server '/remote' implies that the command is: '/remote/rsh-server'. it is actually: 'remote/rsh-server' The following would be more intuitive, I think. Pretty sure somebody can improve on this, also... ;-) remote/ rsh-serverStart a GShell server rsh Connect to a remote GShell server The help command should make hierarchical structure of commands more obvious. Are there plans (or something I haven't realized, yet) for some sort of command navigation? e.g.: cd geronimo start-server -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] 2.1: Failed for Revision: 603264
OpenEJB trunk at 603232
Geronimo Revision: 603264 built with tests included
See the full build-1005.log file at
http://people.apache.org/~prasad/binaries/trunk/20071211/build-1005.log
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/prasad/geronimo/trunk/plugins/system-database/system-database-jetty/target/resources/META-INF/plan.xml
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/system-database/system-database-jetty/target/system-database-jetty-2.1-SNAPSHOT.car
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: system-database-jetty-2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/system-database/system-database-jetty/target/system-database-jetty-2.1-SNAPSHOT.car
to
/home/prasad/.m2/repository/org/apache/geronimo/plugins/system-database-jetty/2.1-SNAPSHOT/system-database-jetty-2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Modules :: Tomcat Clustering over WADI
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-wadi/target/classes/META-INF
[INFO] Copying 2 files to
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-wadi/target/classes/META-INF
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 2 source files to
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-wadi/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-wadi/target/geronimo-tomcat6-clustering-wadi-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in:
geronimo-tomcat6-clustering-wadi-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-wadi/target/geronimo-tomcat6-clustering-wadi-2.1-SNAPSHOT.jar
to
/home/prasad/.m2/repository/org/apache/geronimo/modules/geronimo-tomcat6-clustering-wadi/2.1-SNAPSHOT/geronimo-tomcat6-clustering-wadi-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Modules :: Tomcat :: Clustering Builder for WADI
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.042 seconds
Time to generate code: 0.021 seconds
Time to compile code: 1.684 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/target/classes/META-INF
[INFO] Copying 2 files to
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/target/classes/META-INF
[INFO] [buildsupport:copy-xmlbeans-schemas {execution: default}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/target/clover/classes
[INFO] Copying 11 files to
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/target/clover/classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/target/test-classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/src/test/java/org/apache/geronimo/tomcat/cluster/wadi/builder/WADITomcatClusteringBuilderTest.java:[65,12]
cannot find symbol
symbol : class WADITomcatClusteringBuilder
location: class
org.apache.geronimo.tomcat.cluster.wadi.builder.WADITomcatClusteringBuilderTest
/home/prasad/geronimo/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi/src/test/java/org/apache/geronimo/tomcat/cluster/wadi/builder
Re: [VOTE] Release Genesis 1.3
+1 Regards, Alan On Dec 11, 2007, at 1:58 AM, Jason Dillon wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
Re: [DISCUSS] Moving the Monitoring Plugin Into Trunk
On Dec 10, 2007, at 7:18 AM, Jeff Genender wrote: Anita Kulshreshtha wrote: I see Monitoring Console as a tool, a standard J2EE Application, that has been packaged for a convenient installation in Geronimo. It talks to a geronimo specific agent to discover and monitor a geronimo instance running elsewhere. I do not see it as an integral part of G, and hence prefer /plugins. Its location in svn does not affect the convenience of using it. It will always be installed from 'plugins' portlet and will be visible as an available plugin. IMHO, it should definitely be a plugin (as should everything we ship), but I think it should be a plugin that is installed by default. As pointed out in another email, monitoring is typically shipped and active in some form for most other application servers. If most of the users find it helpful to have automatically enabled, then its probably good that we do so. I would probably suggest as we get closer to a release date that we get more input from users on this subject so we can make a proper and informed decision. This reflects my sentiments as well. Regards, Alan
Re: [VOTE] Release activation and jsvamail spec jars + javamail provider jars.
+1 Regards, Alan On Dec 7, 2007, at 4:01 AM, Rick McGuire wrote: [ ] +1 - Release the jars [ ] 0 - No opinion [ ] -1 - Do not release the jars We're voting on the following which are required for the Geronimo 2.1 release: 1) Release 1.0.0 of the activation 1.1 spec API. The artifact in question is geronimo-activation_1.1_spec-1.0.1. This is the OSGIfied jar file, needed because of the javamail dependency. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-activation_1.1_spec-1.0.1.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 2) Release 1.2 of the javamail 1.4 spec API. The artifact in question is geronimo-javamail_1.4_spec-1.2. This jar has the OSGI changes, plus a number of bug fixes. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_spec-1.2.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-javamail_1.4_spec-1.2 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.2 3) Release 1.3 of the javamail 1.4 mail package. This package includes new providers for the imap, imaps, and pop3s protocols and a significantly rewritten version of the pop3 provider. This package has a top level pom and two child artifacts: top level pom: geronimo-javamail_1.4-1.3 javamail providers: geroinimo_javamail_1.4_provider-1.3 javamail mail:geroinimo_javamail_1.4_mail-1.3 The geroinimo_javamail_1.4_mail-1.3 artifact is the uber-jar containing the merged spec and provider class files. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_-1.3.tar.gz The source used to build this is located at https://svn.apache.org/repos/asf/geronimo/javamail/branches/geronimo-javamail_1.4-1.3 The tag will be created at https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.3
Re: [VOTE] Release Genesis 1.3
+1 Jay Jason Dillon wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
Re: [VOTE] Release activation and jsvamail spec jars + javamail provider jars.
+1 Jay Rick McGuire wrote: [ ] +1 - Release the jars [ ] 0 - No opinion [ ] -1 - Do not release the jars We're voting on the following which are required for the Geronimo 2.1 release: 1) Release 1.0.0 of the activation 1.1 spec API. The artifact in question is geronimo-activation_1.1_spec-1.0.1. This is the OSGIfied jar file, needed because of the javamail dependency. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-activation_1.1_spec-1.0.1.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 2) Release 1.2 of the javamail 1.4 spec API. The artifact in question is geronimo-javamail_1.4_spec-1.2. This jar has the OSGI changes, plus a number of bug fixes. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_spec-1.2.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-javamail_1.4_spec-1.2 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.2 3) Release 1.3 of the javamail 1.4 mail package. This package includes new providers for the imap, imaps, and pop3s protocols and a significantly rewritten version of the pop3 provider. This package has a top level pom and two child artifacts: top level pom: geronimo-javamail_1.4-1.3 javamail providers: geroinimo_javamail_1.4_provider-1.3 javamail mail:geroinimo_javamail_1.4_mail-1.3 The geroinimo_javamail_1.4_mail-1.3 artifact is the uber-jar containing the merged spec and provider class files. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_-1.3.tar.gz The source used to build this is located at https://svn.apache.org/repos/asf/geronimo/javamail/branches/geronimo-javamail_1.4-1.3 The tag will be created at https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.3
Re: [VOTE] Release activation and jsvamail spec jars + javamail provider jars.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 Jay D. McHugh wrote: +1 Jay Rick McGuire wrote: [ ] +1 - Release the jars [ ] 0 - No opinion [ ] -1 - Do not release the jars We're voting on the following which are required for the Geronimo 2.1 release: 1) Release 1.0.0 of the activation 1.1 spec API. The artifact in question is geronimo-activation_1.1_spec-1.0.1. This is the OSGIfied jar file, needed because of the javamail dependency. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-activation_1.1_spec-1.0.1.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 2) Release 1.2 of the javamail 1.4 spec API. The artifact in question is geronimo-javamail_1.4_spec-1.2. This jar has the OSGI changes, plus a number of bug fixes. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_spec-1.2.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-javamail_1.4_spec-1.2 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.2 3) Release 1.3 of the javamail 1.4 mail package. This package includes new providers for the imap, imaps, and pop3s protocols and a significantly rewritten version of the pop3 provider. This package has a top level pom and two child artifacts: top level pom: geronimo-javamail_1.4-1.3 javamail providers: geroinimo_javamail_1.4_provider-1.3 javamail mail:geroinimo_javamail_1.4_mail-1.3 The geroinimo_javamail_1.4_mail-1.3 artifact is the uber-jar containing the merged spec and provider class files. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_-1.3.tar.gz The source used to build this is located at https://svn.apache.org/repos/asf/geronimo/javamail/branches/geronimo-javamail_1.4-1.3 The tag will be created at https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.3 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHXrZIgNg6eWEDv1kRAkyeAKCmGruQGJq6WPJwsv+Cfa2Jy5VhuACgzilj KV+4zaJSGvqotzmu30jCRK8= =+EbA -END PGP SIGNATURE-
[jira] Assigned: (GERONIMO-3690) All deployer command line tools fail with NoClassDefFoundError
[ https://issues.apache.org/jira/browse/GERONIMO-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3690: - Assignee: Jarek Gawor All deployer command line tools fail with NoClassDefFoundError -- Key: GERONIMO-3690 URL: https://issues.apache.org/jira/browse/GERONIMO-3690 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor C:\targetgeronimo-jetty6-javaee5-2.1-SNAPSHOT\bin\deploy.bat list-targets Using GERONIMO_BASE: C:\target\geronimo-jetty6-javaee5-2.1-SNAPSHOT Using GERONIMO_HOME: C:\target\geronimo-jetty6-javaee5-2.1-SNAPSHOT Using GERONIMO_TMPDIR: var\temp Using JRE_HOME:c:\Program Files\Java\jdk1.5.0_14\jre 01:08:28,656 WARN [ConfigurationUtil] Could not load gbean org.apache.geronimo. configs/online-deployer/2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.confi gs/online-deployer/2.1-SNAPSHOT/car,j2eeType=RemoteDeploymentManager,name=Module ConfigurerRegistry java.lang.NoClassDefFoundError: org/codehaus/plexus/archiver/ArchiverException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getMethod0(Class.java:2642) at java.lang.Class.getMethod(Class.java:1579) at org.apache.geronimo.gbean.runtime.GBeanAttribute.init(GBeanAttribut e.java:237) at org.apache.geronimo.gbean.runtime.GBeanInstance.init(GBeanInstance. java:245) at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja va:354) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:433) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:200) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:159) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.loadBoo tConfiguration(MainConfigurationBootstrapper.java:84) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.getMain (MainConfigurationBootstrapper.java:57) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(Ma inConfigurationBootstrapper.java:38) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31 ) Looks like plexus-archiver dependency was added to geronimo-system module but it was not added to the classpath of command line tools. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3690) All deployer command line tools fail with NoClassDefFoundError
[ https://issues.apache.org/jira/browse/GERONIMO-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3690. --- Resolution: Fixed Fix Version/s: 2.1 Added plexus-archiver to the classpath of the deployer. Committed revision 603288. This might not be the best solution as the plexus-archiver library will now also live in the lib/ directory. If there is a better solution (e.g. removing/reducing the plexus dependency) this fix can be reverted. All deployer command line tools fail with NoClassDefFoundError -- Key: GERONIMO-3690 URL: https://issues.apache.org/jira/browse/GERONIMO-3690 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1 C:\targetgeronimo-jetty6-javaee5-2.1-SNAPSHOT\bin\deploy.bat list-targets Using GERONIMO_BASE: C:\target\geronimo-jetty6-javaee5-2.1-SNAPSHOT Using GERONIMO_HOME: C:\target\geronimo-jetty6-javaee5-2.1-SNAPSHOT Using GERONIMO_TMPDIR: var\temp Using JRE_HOME:c:\Program Files\Java\jdk1.5.0_14\jre 01:08:28,656 WARN [ConfigurationUtil] Could not load gbean org.apache.geronimo. configs/online-deployer/2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.confi gs/online-deployer/2.1-SNAPSHOT/car,j2eeType=RemoteDeploymentManager,name=Module ConfigurerRegistry java.lang.NoClassDefFoundError: org/codehaus/plexus/archiver/ArchiverException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getMethod0(Class.java:2642) at java.lang.Class.getMethod(Class.java:1579) at org.apache.geronimo.gbean.runtime.GBeanAttribute.init(GBeanAttribut e.java:237) at org.apache.geronimo.gbean.runtime.GBeanInstance.init(GBeanInstance. java:245) at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja va:354) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:433) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:200) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:159) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.loadBoo tConfiguration(MainConfigurationBootstrapper.java:84) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.getMain (MainConfigurationBootstrapper.java:57) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(Ma inConfigurationBootstrapper.java:38) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31 ) Looks like plexus-archiver dependency was added to geronimo-system module but it was not added to the classpath of command line tools. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-86) command groups in help screen
[
https://issues.apache.org/jira/browse/GSHELL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550563
]
Guillaume Nodet commented on GSHELL-86:
---
FYI, we are using things in a somewhat different way in ServiceMix.
Commands are grouped into subcommands, so instead of listing all the commands,
we only list the first level.
{noformat}
[EMAIL PROTECTED]:/ ?
For information about ServiceMix, visit:
http://servicemix.apache.org
Available commands:
. Alias to: source
? Alias to: help
clear Clear the terminal screen
createCreate a new ServiceMix instance
echo Echo or print arguments to STDOUT
exit Exit the (sub)shell
help Show command help
set Set a variable
sourceLoad a file/url into the current shell
unset Unset a variable
Available shells:
obr
osgi
remote
[EMAIL PROTECTED]:/ ? obr
Available commands in obr:
addUrlAdd a list of repository URLs to the repository service
deployDeploy
info Display the meta-data for the specified bundles.
list List
listUrl Display the repository URLs currently associated with
the repository service.
removeUrl Remove a list of repository URLs from the repository
service
sourceSource
start Start
[EMAIL PROTECTED]:/ ? obr info
Command info
Display the meta-data for the specified bundles.
obr:info
--
-h (--help)Display this help message
[EMAIL PROTECTED]:/
{noformat}
command groups in help screen
-
Key: GSHELL-86
URL: https://issues.apache.org/jira/browse/GSHELL-86
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Reporter: Jarek Gawor
Fix For: 1.0-alpha-1
The help screen shows the following:
...
/deploy
list-plugins Install plugins into a geronimo server
connect Connect to a Geronimo server
disconnectDisconnect from a Geronimo server
..
which I would interpret that I need to type /deploy/connect to execute the
command. But that does not work but deploy/connect works. So I would
propose updating the help screen to show the slash at the end of the group
name instead of the front. e.g.:
...
deploy/
list-plugins Install plugins into a geronimo server
connect Connect to a Geronimo server
disconnectDisconnect from a Geronimo server
..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Genesis 1.3
+0 Jacek On Dec 11, 2007 10:58 AM, Jason Dillon [EMAIL PROTECTED] wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: [VOTE] Release activation and jsvamail spec jars + javamail provider jars.
+1 Jacek On Dec 7, 2007 1:01 PM, Rick McGuire [EMAIL PROTECTED] wrote: [ ] +1 - Release the jars [ ] 0 - No opinion [ ] -1 - Do not release the jars We're voting on the following which are required for the Geronimo 2.1 release: 1) Release 1.0.0 of the activation 1.1 spec API. The artifact in question is geronimo-activation_1.1_spec-1.0.1. This is the OSGIfied jar file, needed because of the javamail dependency. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-activation_1.1_spec-1.0.1.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 2) Release 1.2 of the javamail 1.4 spec API. The artifact in question is geronimo-javamail_1.4_spec-1.2. This jar has the OSGI changes, plus a number of bug fixes. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_spec-1.2.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-javamail_1.4_spec-1.2 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.2 3) Release 1.3 of the javamail 1.4 mail package. This package includes new providers for the imap, imaps, and pop3s protocols and a significantly rewritten version of the pop3 provider. This package has a top level pom and two child artifacts: top level pom: geronimo-javamail_1.4-1.3 javamail providers: geroinimo_javamail_1.4_provider-1.3 javamail mail:geroinimo_javamail_1.4_mail-1.3 The geroinimo_javamail_1.4_mail-1.3 artifact is the uber-jar containing the merged spec and provider class files. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_-1.3.tar.gz The source used to build this is located at https://svn.apache.org/repos/asf/geronimo/javamail/branches/geronimo-javamail_1.4-1.3 The tag will be created at https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.3 -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Created: (GERONIMO-3699) Corba error on app client shutdown
Corba error on app client shutdown -- Key: GERONIMO-3699 URL: https://issues.apache.org/jira/browse/GERONIMO-3699 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: CORBA Affects Versions: 2.1 Reporter: Jarek Gawor When executing app client I see the following exception: 13:15:36,312 ERROR [GBeanInstance] Problem in doStop of org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car,j2eeType=CORBABean,name=Server java.lang.NoSuchMethodError: org.omg.PortableInterceptor.IORInterceptor_3_0.adapter_manager_state_changed(Ljava/lang/String;S)V at org.apache.yoko.orb.OB.PIManager.adapterManagerStateChange(PIManager.java:532) at org.apache.yoko.orb.OBPortableServer.POAManager_impl.deactivate(POAManager_impl.java:360) at org.apache.yoko.orb.OBPortableServer.POAManagerFactory_impl._OB_deactivate(POAManagerFactory_impl.java:342) at org.apache.yoko.orb.OB.ORBControl.completeServerShutdown(ORBControl.java:100) at org.apache.yoko.orb.OB.ORBControl.shutdownServer(ORBControl.java:427) at org.apache.yoko.orb.OB.ORBControl.shutdownServerClient(ORBControl.java:455) at org.apache.yoko.orb.OBCORBA.ORB_impl.destroy(ORB_impl.java:1390) at org.apache.geronimo.corba.CORBABean.doStop(CORBABean.java:260) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1159) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) Exception in thread Yoko:Server:StarterThread java.lang.NoClassDefFoundError: org/apache/yoko/orb/OB/GIOPConnectionThreaded$ReceiverThread at org.apache.yoko.orb.OB.GIOPServerStarterThreaded.starterRun(GIOPServerStarterThreaded.java:243) at org.apache.yoko.orb.OB.GIOPServerStarterThreaded$StarterThread.run(GIOPServerStarterThreaded.java:34) I deployed jaxb-client application from testsuites on jetty assembly and executed: java -jar geronimo-jetty6-javaee5-2.1-SNAPSHOT\bin\client.jar JEE5/JAXBClient/1.1/car -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3699) Corba error on app client shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550672 ] Rick McGuire commented on GERONIMO-3699: This error usually occurs because the Yoko jars are not in the endorsed dirs. The JVM residenent org.omg.* classes are not compatible with the ones required for Yoko. If you're invoking the client directly with the java command, the endorsed dirs are not set up correctly. Corba error on app client shutdown -- Key: GERONIMO-3699 URL: https://issues.apache.org/jira/browse/GERONIMO-3699 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: CORBA Affects Versions: 2.1 Reporter: Jarek Gawor When executing app client I see the following exception: 13:15:36,312 ERROR [GBeanInstance] Problem in doStop of org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car,j2eeType=CORBABean,name=Server java.lang.NoSuchMethodError: org.omg.PortableInterceptor.IORInterceptor_3_0.adapter_manager_state_changed(Ljava/lang/String;S)V at org.apache.yoko.orb.OB.PIManager.adapterManagerStateChange(PIManager.java:532) at org.apache.yoko.orb.OBPortableServer.POAManager_impl.deactivate(POAManager_impl.java:360) at org.apache.yoko.orb.OBPortableServer.POAManagerFactory_impl._OB_deactivate(POAManagerFactory_impl.java:342) at org.apache.yoko.orb.OB.ORBControl.completeServerShutdown(ORBControl.java:100) at org.apache.yoko.orb.OB.ORBControl.shutdownServer(ORBControl.java:427) at org.apache.yoko.orb.OB.ORBControl.shutdownServerClient(ORBControl.java:455) at org.apache.yoko.orb.OBCORBA.ORB_impl.destroy(ORB_impl.java:1390) at org.apache.geronimo.corba.CORBABean.doStop(CORBABean.java:260) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1159) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) Exception in thread Yoko:Server:StarterThread java.lang.NoClassDefFoundError: org/apache/yoko/orb/OB/GIOPConnectionThreaded$ReceiverThread at org.apache.yoko.orb.OB.GIOPServerStarterThreaded.starterRun(GIOPServerStarterThreaded.java:243) at org.apache.yoko.orb.OB.GIOPServerStarterThreaded$StarterThread.run(GIOPServerStarterThreaded.java:34) I deployed jaxb-client application from testsuites on jetty assembly and executed: java -jar geronimo-jetty6-javaee5-2.1-SNAPSHOT\bin\client.jar JEE5/JAXBClient/1.1/car -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3523) java.io.IOException: FULL head
[ https://issues.apache.org/jira/browse/GERONIMO-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550678 ] Mike McLean commented on GERONIMO-3523: --- While waiting for version 2.1, what is one to do to create a JMS resource. Are there docs somewhere on how to do it manually, or is there a way to integrate some sort of patch. java.io.IOException: FULL head -- Key: GERONIMO-3523 URL: https://issues.apache.org/jira/browse/GERONIMO-3523 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0.x Reporter: Jarek Gawor Assignee: Paul McMahan Fix For: 2.1 On Jetty the testsuite/console-testsuite/advanced tests usually fail with strange errors while the same works fine on Tomcat. On the server I see the following errors: 16:22:43,046 WARN [log] handle failed java.io.IOException: FULL head at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) The tests fail with different errors e.g. (it changes from run to run): testNewJMSResource(org.apache.geronimo.testsuite.console.JMSResourcesTest) Time elapsed: 7.86 sec FAILURE! com.thoughtworks.selenium.SeleniumException: ERROR: Element //[EMAIL PROTECTED]'Add Destination'] not found at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:73) at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:82) at org.apache.geronimo.testsuite.console.JMSResourcesTest.testNewJMSResource(JMSResourcesTest.java:47) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3699) Corba error on app client shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3699: - Assignee: Jarek Gawor Corba error on app client shutdown -- Key: GERONIMO-3699 URL: https://issues.apache.org/jira/browse/GERONIMO-3699 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: CORBA Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor When executing app client I see the following exception: 13:15:36,312 ERROR [GBeanInstance] Problem in doStop of org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car,j2eeType=CORBABean,name=Server java.lang.NoSuchMethodError: org.omg.PortableInterceptor.IORInterceptor_3_0.adapter_manager_state_changed(Ljava/lang/String;S)V at org.apache.yoko.orb.OB.PIManager.adapterManagerStateChange(PIManager.java:532) at org.apache.yoko.orb.OBPortableServer.POAManager_impl.deactivate(POAManager_impl.java:360) at org.apache.yoko.orb.OBPortableServer.POAManagerFactory_impl._OB_deactivate(POAManagerFactory_impl.java:342) at org.apache.yoko.orb.OB.ORBControl.completeServerShutdown(ORBControl.java:100) at org.apache.yoko.orb.OB.ORBControl.shutdownServer(ORBControl.java:427) at org.apache.yoko.orb.OB.ORBControl.shutdownServerClient(ORBControl.java:455) at org.apache.yoko.orb.OBCORBA.ORB_impl.destroy(ORB_impl.java:1390) at org.apache.geronimo.corba.CORBABean.doStop(CORBABean.java:260) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1159) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) Exception in thread Yoko:Server:StarterThread java.lang.NoClassDefFoundError: org/apache/yoko/orb/OB/GIOPConnectionThreaded$ReceiverThread at org.apache.yoko.orb.OB.GIOPServerStarterThreaded.starterRun(GIOPServerStarterThreaded.java:243) at org.apache.yoko.orb.OB.GIOPServerStarterThreaded$StarterThread.run(GIOPServerStarterThreaded.java:34) I deployed jaxb-client application from testsuites on jetty assembly and executed: java -jar geronimo-jetty6-javaee5-2.1-SNAPSHOT\bin\client.jar JEE5/JAXBClient/1.1/car -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3699) Corba error on app client shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3699. --- Resolution: Fixed Fix Version/s: 2.1 Rick, thanks! That was it. I just added client.sh and client.bat files for the app client that configure the jvm correctly (revision 603337). Corba error on app client shutdown -- Key: GERONIMO-3699 URL: https://issues.apache.org/jira/browse/GERONIMO-3699 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: CORBA Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1 When executing app client I see the following exception: 13:15:36,312 ERROR [GBeanInstance] Problem in doStop of org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/client-corba-yoko/2.1-SNAPSHOT/car,j2eeType=CORBABean,name=Server java.lang.NoSuchMethodError: org.omg.PortableInterceptor.IORInterceptor_3_0.adapter_manager_state_changed(Ljava/lang/String;S)V at org.apache.yoko.orb.OB.PIManager.adapterManagerStateChange(PIManager.java:532) at org.apache.yoko.orb.OBPortableServer.POAManager_impl.deactivate(POAManager_impl.java:360) at org.apache.yoko.orb.OBPortableServer.POAManagerFactory_impl._OB_deactivate(POAManagerFactory_impl.java:342) at org.apache.yoko.orb.OB.ORBControl.completeServerShutdown(ORBControl.java:100) at org.apache.yoko.orb.OB.ORBControl.shutdownServer(ORBControl.java:427) at org.apache.yoko.orb.OB.ORBControl.shutdownServerClient(ORBControl.java:455) at org.apache.yoko.orb.OBCORBA.ORB_impl.destroy(ORB_impl.java:1390) at org.apache.geronimo.corba.CORBABean.doStop(CORBABean.java:260) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1159) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:561) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) Exception in thread Yoko:Server:StarterThread java.lang.NoClassDefFoundError: org/apache/yoko/orb/OB/GIOPConnectionThreaded$ReceiverThread at org.apache.yoko.orb.OB.GIOPServerStarterThreaded.starterRun(GIOPServerStarterThreaded.java:243) at org.apache.yoko.orb.OB.GIOPServerStarterThreaded$StarterThread.run(GIOPServerStarterThreaded.java:34) I deployed jaxb-client application from testsuites on jetty assembly and executed: java -jar geronimo-jetty6-javaee5-2.1-SNAPSHOT\bin\client.jar JEE5/JAXBClient/1.1/car -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-20) `set foo=bar` does not work as expected
[
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550683
]
Jason Warner commented on GSHELL-20:
Are we deciding to forgo this band-aid and put our hopes in a more fleshed out
parser?
`set foo=bar` does not work as expected
-
Key: GSHELL-20
URL: https://issues.apache.org/jira/browse/GSHELL-20
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Commands, Core
Affects Versions: 0.0.1
Reporter: Jason Dillon
Assignee: Jason Warner
Priority: Critical
Fix For: 1.0-alpha-2
Attachments: GShell-20.patch, GShell-20SingleQuote.patch
Due to the way parsing happens, this line:
{noformat}
set foo=bar
{noformat}
Ends up calling the command with 2 arguments: foo= and bar, which is not
what the command expects, which is one argument of: foo=bar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] 2.1: Failed for Revision: 603314
OpenEJB trunk at 603232 Geronimo Revision: 603314 built with tests included See the full build-1230.log file at http://people.apache.org/~prasad/binaries/trunk/20071211/build-1230.log Download the binaries from http://people.apache.org/~prasad/binaries/trunk/20071211 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 33 minutes 38 seconds [INFO] Finished at: Tue Dec 11 13:19:46 EST 2007 [INFO] Final Memory: 284M/1011M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/~prasad/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/~prasad/binaries/trunk/20071211/logs-1230-tomcat/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 54.463 sec FAILURE! -- [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.228 sec FAILURE! [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.28 sec FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/~prasad/binaries/trunk/20071211/logs-1230-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 60.401 sec FAILURE! -- [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.269 sec FAILURE! [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.308 sec FAILURE!
Re: svn commit: r603314 - in /geronimo/server/trunk/plugins/tomcat/geronimo-tomcat6-clustering-builder-wadi: java/ src/main/java/
Ooops. I wonder how this happened. I must have move this folder by dragging it unintentionally within my IDE to another folder. Thanks for the fix. Thanks, Gianny On 12/12/2007, at 4:33 AM, [EMAIL PROTECTED] wrote: Author: gawor Date: Tue Dec 11 09:33:48 2007 New Revision: 603314 URL: http://svn.apache.org/viewvc?rev=603314view=rev Log: move code to the right place. fixes build problem caused by rev 603174 Added: geronimo/server/trunk/plugins/tomcat/geronimo-tomcat6- clustering-builder-wadi/src/main/java/ - copied from r603270, geronimo/server/trunk/plugins/tomcat/ geronimo-tomcat6-clustering-builder-wadi/java/ Removed: geronimo/server/trunk/plugins/tomcat/geronimo-tomcat6- clustering-builder-wadi/java/
[jira] Updated: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.
[ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-3528: Attachment: TestedResults2_including_G3667.html Jarek, I have rebuilt snapshot from current source code (r602608) and retested it. As you say, I have verified that all test cases are OK results. I have uploaded the test results again. Thank you for supporting! Cannot lookup JNDI context inside some servlet event listeners. --- Key: GERONIMO-3528 URL: https://issues.apache.org/jira/browse/GERONIMO-3528 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: naming Affects Versions: 1.1.1, 2.0.1 Reporter: Kan Ogawa Assignee: Jarek Gawor Fix For: 2.0.x, 2.1 Attachments: examples.war, TestedResults.html, TestedResults2_including_G3667.html, TestedResults_including_G3667.html In some servlet event listeners, JNDI context lookup fails. I encountered this issue while testing the following use case: - When http session has became invalid by timeout, web container automatically updates the logoff datetime to database system. So I have made sample application to reproduce this issue and the tested results. This stack trace is one of NG results: 16:23:35,661 ERROR [[/examples]] Session event listener threw exception java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.lookup(ContextFlyweight.java:44) at org.apache.xbean.naming.context.ContextFederation.getFederatedBinding(ContextFederation.java:71) at org.apache.xbean.naming.context.AbstractFederatedContext.getBinding(AbstractFederatedContext.java:63) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:129) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597) at javax.naming.InitialContext.lookup(InitialContext.java:351) at examples.DBConnector.testConnection(DBConnector.java:26) at examples.HttpSessionListenerImpl.sessionDestroyed(HttpSessionListenerImpl.java:15) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:702) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:592) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:682) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:667) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) at java.lang.Thread.run(Thread.java:595) If Geronimo v1.1, the stack trace is: [ERROR] HttpSession - SystemDatabase doesn't have been lookuped from JNDI Context. javax.naming.NameNotFoundException: comp/env/jdbc/SystemDatasource at org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:45) at javax.naming.InitialContext.lookup(InitialContext.java:351) at examples.DBConnector.testConnection(DBConnector.java:26) at examples.HttpSessionListenerImpl.sessionDestroyed(HttpSessionListenerImpl.java:15) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:685) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:577) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:678) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:663) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1283) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1568) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1557) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a
[jira] Closed: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.
[ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor closed GERONIMO-3528. - Resolution: Fixed Great! Thanks for double checking. Cannot lookup JNDI context inside some servlet event listeners. --- Key: GERONIMO-3528 URL: https://issues.apache.org/jira/browse/GERONIMO-3528 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: naming Affects Versions: 1.1.1, 2.0.1 Reporter: Kan Ogawa Assignee: Jarek Gawor Fix For: 2.0.x, 2.1 Attachments: examples.war, TestedResults.html, TestedResults2_including_G3667.html, TestedResults_including_G3667.html In some servlet event listeners, JNDI context lookup fails. I encountered this issue while testing the following use case: - When http session has became invalid by timeout, web container automatically updates the logoff datetime to database system. So I have made sample application to reproduce this issue and the tested results. This stack trace is one of NG results: 16:23:35,661 ERROR [[/examples]] Session event listener threw exception java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.lookup(ContextFlyweight.java:44) at org.apache.xbean.naming.context.ContextFederation.getFederatedBinding(ContextFederation.java:71) at org.apache.xbean.naming.context.AbstractFederatedContext.getBinding(AbstractFederatedContext.java:63) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:129) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597) at javax.naming.InitialContext.lookup(InitialContext.java:351) at examples.DBConnector.testConnection(DBConnector.java:26) at examples.HttpSessionListenerImpl.sessionDestroyed(HttpSessionListenerImpl.java:15) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:702) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:592) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:682) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:667) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) at java.lang.Thread.run(Thread.java:595) If Geronimo v1.1, the stack trace is: [ERROR] HttpSession - SystemDatabase doesn't have been lookuped from JNDI Context. javax.naming.NameNotFoundException: comp/env/jdbc/SystemDatasource at org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:45) at javax.naming.InitialContext.lookup(InitialContext.java:351) at examples.DBConnector.testConnection(DBConnector.java:26) at examples.HttpSessionListenerImpl.sessionDestroyed(HttpSessionListenerImpl.java:15) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:685) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:577) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:678) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:663) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1283) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1568) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1557) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: jira 404's
I get that too :-( --jason -Original Message- From: Kevan Miller [EMAIL PROTECTED] Date: Tue, 11 Dec 2007 09:49:58 To:Geronimo Dev dev@geronimo.apache.org Subject: jira 404's Is anybody else having problems with Jira? When I create a Geronimo Jira, I get the following 404: HTTP Status 404 - No view for result [error] exists for action [ViewIssue] type Status report message No view for result [error] exists for action [ViewIssue] description The requested resource (No view for result [error] exists for action [ViewIssue]) is not available. Apache Tomcat/5.5.20
Re: jira 404's
I get that too :-( --jason --Original Message-- From: Kevan Miller To: Geronimo Dev ReplyTo: dev@geronimo.apache.org Sent: Dec 11, 2007 6:49 AM Subject: jira 404's Is anybody else having problems with Jira? When I create a Geronimo Jira, I get the following 404: HTTP Status 404 - No view for result [error] exists for action [ViewIssue] type Status report message No view for result [error] exists for action [ViewIssue] description The requested resource (No view for result [error] exists for action [ViewIssue]) is not available. Apache Tomcat/5.5.20
[BUILD] 2.0: Failed for Revision: 603331
Geronimo Revision: 603331 built with tests included See the full build-1400.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/build-1400.log Download the binaries from http://people.apache.org/~prasad/binaries/2.0/20071211 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 25 minutes 12 seconds [INFO] Finished at: Tue Dec 11 14:36:13 EST 2007 [INFO] Final Memory: 229M/1018M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/~prasad/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/logs-1400-tomcat/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 158.153 sec FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/logs-1400-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 161.61 sec FAILURE!
[jira] Commented: (GERONIMO-3700) alias command fails
[
https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550721
]
Jason Dillon commented on GERONIMO-3700:
The alias command has been introduced in {{geronimo-commands}} and is not
really part of the core GShell bits, so I'm moving this issue.
I've yet to really look at what the alias command is doing, though I did
suggest that we wanted to use the command alias mechanism in GShell for this...
but perhaps that mechanism needs more work to be more useful.
alias command fails
---
Key: GERONIMO-3700
URL: https://issues.apache.org/jira/browse/GERONIMO-3700
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Kevan Miller
Assignee: Jason Dillon
Running the alias command fails with an IllegalStateException:
[EMAIL PROTECTED]:/ alias
ERROR IllegalStateException: Alias file
/Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml
does not exist
Could be that Geronimo should be including this file in assemblies, or gshell
should create (if not present), or something else is wrong...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3700) alias command fails
[ https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-3700: --- Component/s: gbuild Fix Version/s: 2.1 alias command fails --- Key: GERONIMO-3700 URL: https://issues.apache.org/jira/browse/GERONIMO-3700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: gbuild Reporter: Kevan Miller Assignee: Jason Dillon Fix For: 2.1 Running the alias command fails with an IllegalStateException: [EMAIL PROTECTED]:/ alias ERROR IllegalStateException: Alias file /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml does not exist Could be that Geronimo should be including this file in assemblies, or gshell should create (if not present), or something else is wrong... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3700) alias command fails
[ https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-3700: --- Component/s: (was: gbuild) general alias command fails --- Key: GERONIMO-3700 URL: https://issues.apache.org/jira/browse/GERONIMO-3700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: general Reporter: Kevan Miller Assignee: Jason Dillon Fix For: 2.1 Running the alias command fails with an IllegalStateException: [EMAIL PROTECTED]:/ alias ERROR IllegalStateException: Alias file /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml does not exist Could be that Geronimo should be including this file in assemblies, or gshell should create (if not present), or something else is wrong... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3695) jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3695: - Assignee: Jarek Gawor jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies --- Key: GERONIMO-3695 URL: https://issues.apache.org/jira/browse/GERONIMO-3695 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor With some recent changes the jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3701) Update Tomcat build image for Geronimo to 6.0.14 and include fix for Webdav security exposure
Update Tomcat build image for Geronimo to 6.0.14 and include fix for Webdav security exposure - Key: GERONIMO-3701 URL: https://issues.apache.org/jira/browse/GERONIMO-3701 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1 Replace the tomcat 6.0.13 private build for Geronimo with a 6.0.14 image. Also include the fix for the tomcat Webdav security issue. Remove older tomcat build images from geronimo repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Tomcat webdav issue and Geronimo 2.1
Kevan Miller wrote:
On Dec 7, 2007, at 2:44 PM, Joe Bohn wrote:
I was just looking into updating Tomcat for the Geronimo 2.1 release
with an eye toward getting a fix integrated for the Webdav servlet
security issue.
There are 3 possible approaches:
1) Apply the Webdav patch to the 6.0.13 image with the annotation
changes and one other minor change (basically our current
6.0.13_G543818 build plus the WebDav fix). Check this into our
private repository in trunk.
2) Checkout 6.0.14, apply the Webdav patch and annotation changes.
Check this into our private repository in trunk.
3) Checkout tomcat trunk (6.0.x) which already includes the Webdav
patch but not the annotation changes. Apply the annotation changes
for our private build and check it into our repository in trunk.
I personally think #2 is probably best although it might expose some
other issues in tomcat. We could always fall back to #1 if necessary.
There was an attempt made at a tomcat 6.0.15 a few weeks back but it
failed due to some context and tck issues ... hence my reservations
with 6.0.x since it probably has those same issues.
OK. Good, I think, to upgrade to 6.0.14. So, I like your plan # 2.
I just checked in this upgrade in
http://svn.apache.org/viewvc?rev=603398view=rev
I hope it works (some quick testing looks promising).
After digging into this now for tomcat 6.0.14 I can safely say that we
really need to come up with a better way. IMO we need to get Tomcat to
integrate these annotation changes soon or revert back to using the
native Tomcat mechanisms to support annotations. At the moment Tomcat
still has the annotation changes sitting in their sandbox and the code
in their new trunk is drifting.
Here are steps that I followed to create the patch to save the manual
changes that were necessary so that we can recreate the tomcat image. I
checked these directions in as
repository/org/apache/tomcat/6.0.14-G602188.README.TXT
Private Build of Tomcat for Geronimo.
How to build Tomcat 6_0_14 with modifications for Geronimo:
Checkout tomcat 6.0.14
svn co
https://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_14
tomcat_6_0_14
Apply the custom patch for Geronimo Annotation changes, Webdav fix, and
build fix.
cd tomcat_6_0_14
patch -p0 -u tomcat_6_0_14-G602188.patch (checked in as a peer to
this file)
- Respond y to the 3 prompts Reversed (or previously applied)
patch detected! Assume -R? [n]
svn delete java/org/apache/jasper/runtime/AnnotationHelper.java --force
svn delete java/org/apache/AnnotationProcessor.java --force
svn delete
java/org/apache/catalina/util/DefaultAnnotationProcessor.java --force
Build tomcat
cd tomcat_6_0_14
Per tomcat build instructions install ant-1.6.5 or later and set
ANT_HOME as well as add ant/bin to PATH
You must run as the super user for the first build that downloads
more ant eclipse artifacts
ant download - to setup build for tomcat
Exit super user
ant - to build tomcat artifacts
Copy to appropriate jars and rename into geronimo/repository
cd tomcat_6_0_14
cp /build/lib/catalina.jar
geronimo-root/repository/org/apache/tomcat/catalina/6.0.14-G602188/catalina-6.0.14-G602188.jar
cp /build/lib/jasper.jar
geronimo-root/repository/org/apache/tomcat/jasper/6.0.14-G602188/jasper-6.0.14-G602188.jar
How the patch was created:
Checkout tomcat 6.0.14
svn co
https://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_14
tomcat_6_0_14
Apply annotation changes from old tomcat trunk
cd tomcat_6_0_14
svn merge -r 542188:542189
https://svn.apache.org/repos/asf/tomcat/sandbox/gdev6x/ .
manually correct merge conflicts
Apply the Webdav security fix from the new tomcat trunk
svn merge -r 587081:587082
https://svn.apache.org/repos/asf/tomcat/trunk/ .
manually correct merge conflicts
Fix the tomcat build properties before attempting ant download
- Before you can build tomcat you need to make some manual changes to
build.properties.default
- replace jdt.jar=${jdt.lib}/org.eclipse.jdt.core_3.2.3.v_686_R32x.jar
with jdt.jar=${jdt.lib}/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
and
- replace
jdt.loc=http://sunsite.informatik.rwth-aachen.de/eclipse/downloads/drops/R-3.2.2-200702121330/eclipse-JDT-3.2.2.zip
with
jdt.loc=http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.3.1-200709211145/eclipse-JDT-3.3.1.zip
The merge earlier keeps a history on added parts. As a result, the
added parts will not appear on patch created from this image. To correct
this we must revert the addition changes and manually add the parts
back. Perform the following commands:
svn revert java/org/apache/InstanceManager.java
svn addjava/org/apache/InstanceManager.java
svn revert java/org/apache/jasper/runtime/InstanceManagerFactory.java
snv add
[jira] Commented: (GERONIMO-3695) jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550762 ] Jarek Gawor commented on GERONIMO-3695: --- As per David Jencks' recommendation, the jaxws-tools are installed as a plugin now (revision 603427). jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies --- Key: GERONIMO-3695 URL: https://issues.apache.org/jira/browse/GERONIMO-3695 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor With some recent changes the jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3686) AsyncHttpClient does not reuse connection even if connections are persistent
[ https://issues.apache.org/jira/browse/GERONIMO-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550779 ] Sangjin Lee commented on GERONIMO-3686: --- I'm making a small correction to the patch, and will upload a revised version shortly. The issue is that I forgot to add an additional configuration option called reuseConnection. Connection reuse is different than the SO_KEEPALIVE on the socket... AsyncHttpClient does not reuse connection even if connections are persistent Key: GERONIMO-3686 URL: https://issues.apache.org/jira/browse/GERONIMO-3686 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Attachments: 3686.patch Each time AsyncHttpClient.sendRequest() is called, a new TCP connection is opened, even though connections may be kept alive per HTTP spec. If connections are kept open, they should be reused for more requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3686) AsyncHttpClient does not reuse connection even if connections are persistent
[ https://issues.apache.org/jira/browse/GERONIMO-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated GERONIMO-3686: -- Attachment: 3686.patch a revised patch that correctly uses the new setting AsyncHttpClient does not reuse connection even if connections are persistent Key: GERONIMO-3686 URL: https://issues.apache.org/jira/browse/GERONIMO-3686 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Attachments: 3686.patch Each time AsyncHttpClient.sendRequest() is called, a new TCP connection is opened, even though connections may be kept alive per HTTP spec. If connections are kept open, they should be reused for more requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3686) AsyncHttpClient does not reuse connection even if connections are persistent
[ https://issues.apache.org/jira/browse/GERONIMO-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated GERONIMO-3686: -- Attachment: (was: 3686.patch) AsyncHttpClient does not reuse connection even if connections are persistent Key: GERONIMO-3686 URL: https://issues.apache.org/jira/browse/GERONIMO-3686 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Attachments: 3686.patch Each time AsyncHttpClient.sendRequest() is called, a new TCP connection is opened, even though connections may be kept alive per HTTP spec. If connections are kept open, they should be reused for more requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3695) jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3695. --- Resolution: Fixed Fix Version/s: 2.1 The duplicate jaxws batch and script files in both javaee assemblies were removed as part of revision 603432. jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies --- Key: GERONIMO-3695 URL: https://issues.apache.org/jira/browse/GERONIMO-3695 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1 With some recent changes the jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] 2.0: Failed for Revision: 603431
Geronimo Revision: 603431 built with tests included See the full build-2000.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/build-2000.log Download the binaries from http://people.apache.org/~prasad/binaries/2.0/20071211 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 32 minutes 11 seconds [INFO] Finished at: Tue Dec 11 20:42:05 EST 2007 [INFO] Final Memory: 248M/849M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/~prasad/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/logs-2000-tomcat/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 158.537 sec FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/~prasad/binaries/2.0/20071211/logs-2000-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 157.971 sec FAILURE!
Re: [VOTE] Release Genesis 1.3
+1 On Dec 11, 2007, at 4:58 AM, Jason Dillon wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
Re: [VOTE] Release activation and jsvamail spec jars + javamail provider jars.
+1 On Dec 7, 2007, at 7:01 AM, Rick McGuire wrote: [ ] +1 - Release the jars [ ] 0 - No opinion [ ] -1 - Do not release the jars We're voting on the following which are required for the Geronimo 2.1 release: 1) Release 1.0.0 of the activation 1.1 spec API. The artifact in question is geronimo-activation_1.1_spec-1.0.1. This is the OSGIfied jar file, needed because of the javamail dependency. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-activation_1.1_spec-1.0.1.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-activation_1.1_spec-1.0.1 2) Release 1.2 of the javamail 1.4 spec API. The artifact in question is geronimo-javamail_1.4_spec-1.2. This jar has the OSGI changes, plus a number of bug fixes. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_spec-1.2.tar.gz The current branch used to build the release candidate is at https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-javamail_1.4_spec-1.2 The tag will be created at https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.2 3) Release 1.3 of the javamail 1.4 mail package. This package includes new providers for the imap, imaps, and pop3s protocols and a significantly rewritten version of the pop3 provider. This package has a top level pom and two child artifacts: top level pom: geronimo-javamail_1.4-1.3 javamail providers: geroinimo_javamail_1.4_provider-1.3 javamail mail:geroinimo_javamail_1.4_mail-1.3 The geroinimo_javamail_1.4_mail-1.3 artifact is the uber-jar containing the merged spec and provider class files. The release archive is located here: http://people.apache.org/~rickmcguire/releases/geronimo-javamail_1.4_-1.3.tar.gz The source used to build this is located at https://svn.apache.org/repos/asf/geronimo/javamail/branches/geronimo-javamail_1.4-1.3 The tag will be created at https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.3
Re: [VOTE] Release activation and jsvamail spec jars + javamail provider jars.
On Dec 7, 2007, at 7:01 AM, Rick McGuire wrote: [ ] +1 - Release the jars [ ] 0 - No opinion [ ] -1 - Do not release the jars +1 --kevan
GShell ANSI colors support on Window.
It was a bit of bummer when I noticed that GShell has no colorized output on Windows. :( But I noticed that the Perl guys were able to do it. See the Win32::Console::ANSI' project [1]. So I updated the jline dll that is used on Windows with the c code that the Perl project is using and BAM!, we have color. I sent a note out to the jline project about this. Hopefully they incorporate this feature into future releases. -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
Re: GShell ANSI colors support on Window.
Swt! --jason -Original Message- From: Hiram Chirino [EMAIL PROTECTED] Date: Wed, 12 Dec 2007 00:19:47 To:dev@geronimo.apache.org, [EMAIL PROTECTED] Subject: GShell ANSI colors support on Window. It was a bit of bummer when I noticed that GShell has no colorized output on Windows. :( But I noticed that the Perl guys were able to do it. See the Win32::Console::ANSI' project [1]. So I updated the jline dll that is used on Windows with the c code that the Perl project is using and BAM!, we have color. I sent a note out to the jline project about this. Hopefully they incorporate this feature into future releases. -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
[jira] Commented: (GERONIMO-3689) should provide additional thread pool to isolate running of the callback event notification
[ https://issues.apache.org/jira/browse/GERONIMO-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550839 ] Sangjin Lee commented on GERONIMO-3689: --- I have a patch ready for this, but earlier patches are kind of backed up, so I'll wait until they're cleared. should provide additional thread pool to isolate running of the callback event notification - Key: GERONIMO-3689 URL: https://issues.apache.org/jira/browse/GERONIMO-3689 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee The mina 1.1 documentation recommends disabling the default ThreadModel, as well as additionally providing an ExecutorFilter to isolate code that runs when events are notified (IoHandler) and thus in our case callback code. The default ThreadModel should be disabled by SocketConnectorConfig.setThreadModel(ThreadModel.MANUAL), and there should be an option of supplying a thread pool at the end of the filter chain. Please see http://mina.apache.org/configuring-thread-model.html for more discussion... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Genesis 1.3
+1 Thanks, Erik B. Craig On Dec 11, 2007, at 4:58 AM, Jason Dillon wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
[jira] Commented: (GERONIMO-3698) Installation of Admin Console fails with missing dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550848 ] Jarek Gawor commented on GERONIMO-3698: --- console-jetty does not have an explicit dependency on jetty but it does list jetty as a prerequisite. It looks like the prerequisite check is not done during plugin installation (but other checks are performed). So I think we should fix the installer. Installation of Admin Console fails with missing dependency --- Key: GERONIMO-3698 URL: https://issues.apache.org/jira/browse/GERONIMO-3698 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1 Reporter: Kevan Miller Fix For: 2.1 Installation of the Jetty admin console fails with a missing dependency. Starting with a framework assembly, I installed the Jetty Admin Console: 6: Geronimo Plugins :: Administration Console - Jetty (2.1-SNAPSHOT) The installation fails with a missing dependency for: org.apache.geronimo.configs/jetty6/2.1-SNAPSHOT/car The installation works if I first install the jetty6 plugin. Here's the full failure info: Install Services [enter a comma separated list of numbers or 'q' to quit]: 6 Checking for status every 1000ms: Downloading org.apache.geronimo.plugins/console-jetty/2.1-SNAPSHOT/car Copying commons-collections/commons-collections/3.1/jar to the repository (100%) Downloading org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car Downloading org.apache.geronimo.modules/geronimo-client/2.1-SNAPSHOT/jar 320 kB of org.apache.tomcat/jasper-jdt/6.0.13/jar Starting org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car Installation Complete! Used existing: org.apache.geronimo.configs/jee-specs/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.modules/geronimo-core/2.1-SNAPSHOT/jar Used existing: org.apache.geronimo.modules/geronimo-common/2.1-SNAPSHOT/jar Used existing: org.apache.geronimo.modules/geronimo-management/2.1-SNAPSHOT/jar Used existing: asm/asm/2.2.3/jar Used existing: asm/asm-commons/2.2.3/jar Used existing: org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.modules/geronimo-deploy-jsr88/2.1-SNAPSHOT/jar Used existing: org.apache.geronimo.configs/server-security-config/2.1-SNAPSHOT/car Used existing: org.apache.geronimo.modules/geronimo-transformer/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.plugins/pluto-support/2.1-SNAPSHOT/car Installed new: org.apache.pluto/pluto-portal-driver/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-portal-driver-impl/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-container/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-descriptor-api/1.2.0-G601060/jar Installed new: org.apache.pluto/pluto-descriptor-impl/1.2.0-G601060/jar Installed new: commons-logging/commons-logging-api/1.0.4/jar Installed new: commons-beanutils/commons-beanutils/1.6.1/jar Installed new: commons-collections/commons-collections/3.1/jar Installed new: javax.portlet/portlet-api/1.0/jar Installed new: org.apache.geronimo.configs/spring/2.1-SNAPSHOT/car Installed new: org.springframework/spring-core/2.0.5/jar Installed new: org.springframework/spring-beans/2.0.5/jar Installed new: org.springframework/spring-context/2.0.5/jar Installed new: org.springframework/spring-web/2.0.5/jar Installed new: org.codehaus.castor/castor/1.0.5/jar Installed new: org.apache.geronimo.plugins/geronimo-pluto/2.1-SNAPSHOT/jar Installed new: org.apache.pluto/pluto-taglib/1.2.0-G601060/jar Installed new: commons-digester/commons-digester/1.8/jar Installed new: org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car Installed new: org.apache.geronimo.modules/geronimo-j2ee-schema/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.schema/geronimo-schema-jee_5/1.1/jar Installed new: org.apache.geronimo.schema/geronimo-schema-j2ee_1.4/1.2/jar Installed new: org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car Installed new: org.apache.geronimo.modules/geronimo-j2ee/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-webservices/2.1-SNAPSHOT/jar Installed new: org.apache.xbean/xbean-reflect/3.2/jar Installed new: org.apache.geronimo.modules/geronimo-test-ddbean/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-naming-builder/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-security-builder/2.1-SNAPSHOT/jar Installed new: org.apache.geronimo.modules/geronimo-j2ee-builder/2.1-SNAPSHOT/jar Installed new:
Re: [VOTE] Release Genesis 1.3
+1 Thanks, Gianny On 11/12/2007, at 8:58 PM, Jason Dillon wrote: Folks, a small change to Genesis was made to support a custom legal resource bundle for the GShell release. I'd like to get this out so we can get GShell out too. +1 -Release it +0 -Eh, whatever -1 -Um, no no no no no... --jason
[jira] Commented: (GERONIMO-3523) java.io.IOException: FULL head
[ https://issues.apache.org/jira/browse/GERONIMO-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550851 ] Jarek Gawor commented on GERONIMO-3523: --- Mike, There is a number of alternatives: 1) Use 2.0.2 Tomcat assembly instead of Jetty. 2) Download 2.0.3-SNAPSHOT binary from: http://people.apache.org/~prasad/binaries/2.0/20071211/ 3) Build 2.0.3-SNAPSHOT from source (branches/2.0) And make sure not to use IE. It also has some problems with long URLs. java.io.IOException: FULL head -- Key: GERONIMO-3523 URL: https://issues.apache.org/jira/browse/GERONIMO-3523 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0.x Reporter: Jarek Gawor Assignee: Paul McMahan Fix For: 2.1 On Jetty the testsuite/console-testsuite/advanced tests usually fail with strange errors while the same works fine on Tomcat. On the server I see the following errors: 16:22:43,046 WARN [log] handle failed java.io.IOException: FULL head at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) The tests fail with different errors e.g. (it changes from run to run): testNewJMSResource(org.apache.geronimo.testsuite.console.JMSResourcesTest) Time elapsed: 7.86 sec FAILURE! com.thoughtworks.selenium.SeleniumException: ERROR: Element //[EMAIL PROTECTED]'Add Destination'] not found at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:73) at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:82) at org.apache.geronimo.testsuite.console.JMSResourcesTest.testNewJMSResource(JMSResourcesTest.java:47) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
