[jira] Created: (GSHELL-154) Create classes to represent links and aliases
Create classes to represent links and aliases - Key: GSHELL-154 URL: https://issues.apache.org/jira/browse/GSHELL-154 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Reporter: Guillaume Nodet Assignee: Jason Dillon This allows the plugin parser to be decoupled from the command registry by parsing a list of commands, links and aliases to be later registered by the command bundle itself. This is a requirement if the parser has to be somewhat decoupled from the registries, as in ServiceMix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4472) Incorrect Dojo link path in OpenEJB portlet
Incorrect Dojo link path in OpenEJB portlet --- Key: GERONIMO-4472 URL: https://issues.apache.org/jira/browse/GERONIMO-4472 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Reporter: Ivan No sure in which version, dojo path has been fixed. So currently dojo path should be something like /dojo/dojo/dojo.js. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4472) Incorrect Dojo link path in OpenEJB portlet
[ https://issues.apache.org/jira/browse/GERONIMO-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-4472: --- Priority: Minor (was: Major) Incorrect Dojo link path in OpenEJB portlet --- Key: GERONIMO-4472 URL: https://issues.apache.org/jira/browse/GERONIMO-4472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Ivan Priority: Minor No sure in which version, dojo path has been fixed. So currently dojo path should be something like /dojo/dojo/dojo.js. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4472) Incorrect Dojo link path in OpenEJB portlet
[ https://issues.apache.org/jira/browse/GERONIMO-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-4472: --- Attachment: Geronimo-4472.patch Update dojo link path. Thanks ! Incorrect Dojo link path in OpenEJB portlet --- Key: GERONIMO-4472 URL: https://issues.apache.org/jira/browse/GERONIMO-4472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Ivan Priority: Minor Attachments: Geronimo-4472.patch No sure in which version, dojo path has been fixed. So currently dojo path should be something like /dojo/dojo/dojo.js. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GSHELL-154) Create interfaces to represent links and aliases
[ https://issues.apache.org/jira/browse/GSHELL-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved GSHELL-154. Resolution: Fixed Fix Version/s: 1.0-alpha-2 Assignee: Guillaume Nodet (was: Jason Dillon) Adding gshell-api/src/main/java/org/apache/geronimo/gshell/command/Alias.java Adding gshell-api/src/main/java/org/apache/geronimo/gshell/command/Link.java Adding gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/command/AliasImpl.java Adding gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/command/LinkImpl.java Sending gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/config/PluginParser.java Sending gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/plugin/bundle/CommandBundle.java Transmitting file data .. Committed revision 727321. Create interfaces to represent links and aliases Key: GSHELL-154 URL: https://issues.apache.org/jira/browse/GSHELL-154 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 This allows the plugin parser to be decoupled from the command registry by parsing a list of commands, links and aliases to be later registered by the command bundle itself. This is a requirement if the parser has to be somewhat decoupled from the registries, as in ServiceMix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-154) Create interfaces to represent links and aliases
[ https://issues.apache.org/jira/browse/GSHELL-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated GSHELL-154: --- Summary: Create interfaces to represent links and aliases (was: Create classes to represent links and aliases) Create interfaces to represent links and aliases Key: GSHELL-154 URL: https://issues.apache.org/jira/browse/GSHELL-154 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Reporter: Guillaume Nodet Assignee: Jason Dillon Fix For: 1.0-alpha-2 This allows the plugin parser to be decoupled from the command registry by parsing a list of commands, links and aliases to be later registered by the command bundle itself. This is a requirement if the parser has to be somewhat decoupled from the registries, as in ServiceMix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4471) improve heuristic exception handling in rollback when txmanager.commit is called
[ https://issues.apache.org/jira/browse/GERONIMO-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated GERONIMO-4471: -- Description: Improve heuristic exception handling during rollback, when txmanager.commit is called by providing a rollbackResourcesDuringCommit method to throw appropriate heuristic exceptions. The logic is: 1. If XAException.XA_HEURRB arisen from XAResource rollback, this means transaction has been heuristically rolled back, thus we just throw normal RollbackException. 2. If XAException.XA_HEURMIX arisen from XAResource rollback, this means transaction has been heuristically rolled back and committed, thus we just throw HeuristicMixedException. 3. If XAException.XA_HEURCOM arisen from XAResource rollback, this means transaction has been heuristically committed. In this case, if transaction has ever been committed (via other XAResources enlisted), then we throw HeuristicMixedException. 4. Other XAExceptions, throw SystemExceptions. 5. If no specific XAException or only XAException.XA_HEURRB, throw RollbackException. The rollbackResourcesDuringCommit method will be used during the commit context instead of the current rollbackResources method. was: Improve heuristic exception handling during rollback, when txmanager.commit is called by providing a rollbackResourcesDuringCommit method to throw appropriate heuristic exceptions. The logic is: 1. If XAException.XA_HEURRB arisen from XAResource rollback, this means transaction has been heuristically rolled back, thus we just throw normal RollbackException. 2. If XAException.XA_HEURMIX arisen from XAResource rollback, this means transaction has been heuristically rolled back and committed, thus we just throw HeuristicMixedException. 3. If XAException.XA_HEURCOM arisen from XAResource rollback, this means transaction has been heuristically committed. In this case, if transaction has ever been committed (via other XAResources enlisted), then we throw HeuristicMixedException. 4. Other XAExceptions, throw SystemExceptions. 5. If no specific XAException or only XAException.XA_HEURRB, throw RollbackException. The rollbackResourcesDuringCommit method will be used during the commit context instead of the current rollbackResources method. Also, during the internalPrepare method, it has: //TODO document why this is true from the spec. //XAException during prepare means we can assume resource is rolled back. rms.remove(); I don't think this is correct. Per jta spec page 50, If the resource manager wants to roll back the transaction, it should do so by throwing an appropriate XAException in the prepare method. With that, I think we cannot assume resource is already rolled back. It is just the resource manager wants to roll back the transaction. thus I propose us remove the rms.remove() here, so that this rm can be included in the rollback action. Remove stuff under Also, during the internalPrepare method, it has:, because I saw more details on this from the OTS spec, in multiple places, such as: The resource can return VoteRollback under any circumstances, including not having any knowledge about the transaction (which might happen after a crash). If this response is returned, the transaction must be rolled back. Furthermore, the Transaction Service is not required to perform any additional operations on this resource. Returning VoteRollback to prepare A Resource that replies VoteRollback has no requirement to log. Once having replied, the Resource can return recoverable resources to their prior state and forget the transaction. improve heuristic exception handling in rollback when txmanager.commit is called Key: GERONIMO-4471 URL: https://issues.apache.org/jira/browse/GERONIMO-4471 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: transaction manager Affects Versions: 2.2 Reporter: Lin Sun Assignee: Lin Sun Fix For: 2.2 Improve heuristic exception handling during rollback, when txmanager.commit is called by providing a rollbackResourcesDuringCommit method to throw appropriate heuristic exceptions. The logic is: 1. If XAException.XA_HEURRB arisen from XAResource rollback, this means transaction has been heuristically rolled back, thus we just throw normal RollbackException. 2. If XAException.XA_HEURMIX arisen from XAResource rollback, this means transaction has been heuristically rolled back and committed, thus we just throw HeuristicMixedException. 3. If XAException.XA_HEURCOM arisen from XAResource rollback, this means
Re: [jira] Created: (GSHELL-151) Repackage org.apache.geronimo.gshell.* - org.apache.gshell.*
Seems that as a community we should keep our project name as part of all groupIds we generate... If no one else feels that way, then fine, I will not call for a vote, but my opinion stands... :-) -Donald Kevan Miller wrote: On Dec 17, 2008, at 7:27 AM, Jason Dillon wrote: On Dec 16, 2008, at 11:41 AM, Donald Woods wrote: Seems like something we should vote on, given our specs, samples, components and plugin subprojects all use org.apache.geronimo.* IMO specs, samples, components and plugins are all specific to geronimo, so the sub-package makes sense. xbean on the other hand is not geronimo specific directly under o.a. IMO GShell is not geronimo-specific, closer in nature to xbean than to specs or components. So for me the change of packages makes a lot of sense. I agree. There's no requirement that sub-projects fall under a top-level project namespace. There are certainly lots of examples of this... XBean and Yoko being two examples within Geronimo. There are lot's of examples outside of Geronimo... If we have a fundamental difference of opinion on this, then we can certainly put it to a group vote. Barring such a disagreement, I don't think a vote is needed... I'll assume that subsequent discussion will determine if a vote is needed. --kevan
[Fwd: DO NOT REPLY [Bug 45197] Need to support the JSTL 1.2 specification]
Work has resumed on creating an Apache implementation of JSTL 1.2 -Donald Original Message Subject: DO NOT REPLY [Bug 45197] Need to support the JSTL 1.2 specification Date: Wed, 17 Dec 2008 00:36:21 -0800 (PST) From: bugzi...@apache.org To: dwo...@apache.org References: bug-45197-46...@https.issues.apache.org/bugzilla/ https://issues.apache.org/bugzilla/show_bug.cgi?id=45197 --- Comment #8 from Henri Yandell bay...@apache.org 2008-12-17 00:36:20 PST --- Branch created - trunk for standard is now 1.2 specific. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are a voter for the bug. You are on the CC list for the bug.
Re: [Fwd: DO NOT REPLY [Bug 45197] Need to support the JSTL 1.2 specification]
Yep, I've been following that too. It it gets released in time we can consider for inclusion in 2.2. Joe Donald Woods wrote: Work has resumed on creating an Apache implementation of JSTL 1.2 -Donald Original Message Subject: DO NOT REPLY [Bug 45197] Need to support the JSTL 1.2 specification Date: Wed, 17 Dec 2008 00:36:21 -0800 (PST) From: bugzi...@apache.org To: dwo...@apache.org References: bug-45197-46...@https.issues.apache.org/bugzilla/ https://issues.apache.org/bugzilla/show_bug.cgi?id=45197 --- Comment #8 from Henri Yandell bay...@apache.org 2008-12-17 00:36:20 PST --- Branch created - trunk for standard is now 1.2 specific.
[jira] Commented: (GERONIMO-1511) Rewrite JMS portlet
[ https://issues.apache.org/jira/browse/GERONIMO-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657333#action_12657333 ] Ivan commented on GERONIMO-1511: Hi, I would like to try to write some JMS portlets, so that we could do some configurations on the Broker. But I am not sure that whether anyone has focused on it. Could those guys give some comments, so that we could avoid some duplicate stuff. Thanks ! Rewrite JMS portlet --- Key: GERONIMO-1511 URL: https://issues.apache.org/jira/browse/GERONIMO-1511 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: ActiveMQ, connector, console Affects Versions: 1.0 Reporter: Aaron Mulder Assignee: David Jencks Fix For: 2.2 The JMS connection factory and destination portlets should be replaced by a single JMS manager portlet. This should use the JMSManager and show all the available JMS brokers, listing the available connection factories and destinations for each one. When adding a connection factory or destination, it should use the JSR-88 DConfigBeans to construct the deployment plan for the new configuration. I'm not yet sure whether it should group the resources by configuration, perhaps just list the owning configuration there. I'm also not sure whether it's important to be able to add connection factories and destinations simultaneously in a single new configuration -- probably not, though it would be nice in terms of generating plans and so on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (GERONIMO-1511) Rewrite JMS portlet
I would recommend opening a new JIRA for tracking of this work, as G1511 is closed as being Fixed and G4337 should be closed as soon as all of the JMS TCK testcases are passing. -Donald Ivan (JIRA) wrote: [ https://issues.apache.org/jira/browse/GERONIMO-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657333#action_12657333 ] Ivan commented on GERONIMO-1511: Hi, I would like to try to write some JMS portlets, so that we could do some configurations on the Broker. But I am not sure that whether anyone has focused on it. Could those guys give some comments, so that we could avoid some duplicate stuff. Thanks ! Rewrite JMS portlet --- Key: GERONIMO-1511 URL: https://issues.apache.org/jira/browse/GERONIMO-1511 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: ActiveMQ, connector, console Affects Versions: 1.0 Reporter: Aaron Mulder Assignee: David Jencks Fix For: 2.2 The JMS connection factory and destination portlets should be replaced by a single JMS manager portlet. This should use the JMSManager and show all the available JMS brokers, listing the available connection factories and destinations for each one. When adding a connection factory or destination, it should use the JSR-88 DConfigBeans to construct the deployment plan for the new configuration. I'm not yet sure whether it should group the resources by configuration, perhaps just list the owning configuration there. I'm also not sure whether it's important to be able to add connection factories and destinations simultaneously in a single new configuration -- probably not, though it would be nice in terms of generating plans and so on.
[jira] Updated: (GERONIMO-4472) Incorrect Dojo link path in OpenEJB portlet
[ https://issues.apache.org/jira/browse/GERONIMO-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4472: --- Patch Info: [Patch Available] Affects Version/s: 2.2 Fix Version/s: 2.2 Assignee: Donald Woods Incorrect Dojo link path in OpenEJB portlet --- Key: GERONIMO-4472 URL: https://issues.apache.org/jira/browse/GERONIMO-4472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Assignee: Donald Woods Priority: Minor Fix For: 2.2 Attachments: Geronimo-4472.patch No sure in which version, dojo path has been fixed. So currently dojo path should be something like /dojo/dojo/dojo.js. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4472) Incorrect Dojo link path in OpenEJB portlet
[ https://issues.apache.org/jira/browse/GERONIMO-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMO-4472. -- Resolution: Fixed Rev727471 in trunk (2.2-SNAPSHOT) Thanks Ivan for the patch. Incorrect Dojo link path in OpenEJB portlet --- Key: GERONIMO-4472 URL: https://issues.apache.org/jira/browse/GERONIMO-4472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Assignee: Donald Woods Priority: Minor Fix For: 2.2 Attachments: Geronimo-4472.patch No sure in which version, dojo path has been fixed. So currently dojo path should be something like /dojo/dojo/dojo.js. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address for many listening ports
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657492#action_12657492 ] Donald Woods commented on GERONIMO-4442: Testing ORBConfigAdapter patch from Shawn. Will apply as soon as my build and testsuite runs complete. Unable to configure IP address for many listening ports --- Key: GERONIMO-4442 URL: https://issues.apache.org/jira/browse/GERONIMO-4442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.1.3 Reporter: Kevan Miller Priority: Critical Fix For: 2.1.4, 2.2 Attachments: G4222_ORBConfigAdapter.patch I tried to configure the listening IP address for our server sockets. I configured all 'host' properties in config-substitution.properties to be '127.0.0.1' and got the following results: Listening on Ports: 1050 127.0.0.1 CORBA Naming Service 1099 127.0.0.1 RMI Naming 1527 127.0.0.1 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 127.0.0.1 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 127.0.0.1 Tomcat Connector AJP AJP 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS 127.0.0.1 JMX Remoting Connector 61613 127.0.0.1 ActiveMQ Transport Connector 61616 127.0.0.1 ActiveMQ Transport Connector Unfortunately, that's not accurate. netstat reveals the following actual results: $ netstat -an | grep LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63519*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 127.0.0.1.4201 *.*LISTEN tcp4 0 0 127.0.0.1.61613*.*LISTEN tcp4 0 0 127.0.0.1.61616*.*LISTEN tcp4 0 0 127.0.0.1.1527 *.*LISTEN tcp4 0 0 127.0.0.1.8443 *.*LISTEN tcp4 0 0 127.0.0.1.8009 *.*LISTEN tcp4 0 0 127.0.0.1.8080 *.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN Configuring the host properties to be an actual ip address/hostname is a bit worse (not sure what's going on with ActiveMQ): Listening on Ports: 1050 10.0.1.196 CORBA Naming Service 1099 10.0.1.196 RMI Naming 1527 10.0.1.196 Derby Connector 2001 10.0.1.196 OpenEJB ORB Adapter 4201 10.0.1.196 OpenEJB Daemon 6882 10.0.1.196 OpenEJB ORB Adapter 8009 10.0.1.196 Tomcat Connector AJP AJP 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS 10.0.1.196 JMX Remoting Connector 61613 0.0.0.0ActiveMQ Transport Connector 61616 0.0.0.0ActiveMQ Transport Connector Netstat shows: $ netstat -an | grep LISTEN tcp6 0 0 fe80::1%lo0.631*.*LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63569*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 10.0.1.196.4201*.*LISTEN tcp4 0 0 *.61613*.*LISTEN tcp4 0 0 *.61616*.*LISTEN tcp4 0 0 10.0.1.196.1527*.*LISTEN tcp4 0 0 10.0.1.196.8443*.*LISTEN tcp4 0 0 10.0.1.196.8009*.*LISTEN tcp4 0 0 10.0.1.196.8080*.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4298) Upgrade to ActiveMQ 5.2.0 or later
[ https://issues.apache.org/jira/browse/GERONIMO-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMO-4298. -- Resolution: Duplicate Duplicate. Work was done using GERONIMO-4337 Upgrade to ActiveMQ 5.2.0 or later -- Key: GERONIMO-4298 URL: https://issues.apache.org/jira/browse/GERONIMO-4298 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.2 Reporter: Donald Woods Priority: Critical Fix For: 2.2 Upgrade to ActiveMQ 5.2.0 or later, which will also require some rework of the JMS Portlets. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo v2.2 discussion
I'm starting to review the JIRAs we have in the 2.2 bucket and will start moving any that are not assigned to someone or deemed as critical/stop-ship for the 2.2 release out to a future release (2.2.1, 3.0 or Wish List.) The goal is to have the first pass of this review done by EoD tomorrow (Thursday) so we can update the 2.2 Status page with the latest set of required JIRAs for 2.2 -Donald Hernan Cunico wrote: Hi All, We kinda started to have some discussion some time ago but couldn't find any hit on nabble so not sure were we left it. I added a Geronimo v2.2 Roadmap ../GMOxDEV/geronimo-v22-roadmap.html page at the top of the Development section in the wiki front page, http://cwiki.apache.org/geronimo/ so we can resume the discussion and collect all our thoughts in one place. (edit access is limited to committers/contributors though) Does anybody already have a list? Cheers! Hernan
[jira] Updated: (GERONIMO-4214) Port WAR PlanCreator to dojo+dwr+jaxb
[ https://issues.apache.org/jira/browse/GERONIMO-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4214: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Port WAR PlanCreator to dojo+dwr+jaxb - Key: GERONIMO-4214 URL: https://issues.apache.org/jira/browse/GERONIMO-4214 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shrey Banga Assignee: Shrey Banga Fix For: Wish List Port the WAR PlanCreator to dojo+dwr+jaxb, on the lines of EAR PlanCreator and get rid of all the xmlbean wrapper classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4213) Show a Loading message while PlanCreator loads
[ https://issues.apache.org/jira/browse/GERONIMO-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4213: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Show a Loading message while PlanCreator loads Key: GERONIMO-4213 URL: https://issues.apache.org/jira/browse/GERONIMO-4213 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shrey Banga Assignee: Shrey Banga Fix For: Wish List Presently users can see all the dijit components until they are parsed which is ugly. It should be replaced with a Loading message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4025) Accessibility issues: No caption tag or summary property, no column and row scope property for data tables in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4025: -- Assignee: Donald Woods Accessibility issues: No caption tag or summary property, no column and row scope property for data tables in admin console --- Key: GERONIMO-4025 URL: https://issues.apache.org/jira/browse/GERONIMO-4025 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.1, 2.1.2, 2.1.x, 2.2 Environment: Windows XP SP2, IE 6.0 JAWS 8.0 Reporter: Forrest Xia Assignee: Donald Woods Fix For: 2.2 Attachments: GERONIMO-4025-activemq-and-monitoring.patch, GERONIMO-4025-configmanager-and-infomanager.patch, GERONIMO-4025-console.patch, GERONIMO-4025-DB-Properties_zh.patch, GERONIMO-4025-DB-style.patch, GERONIMO-4025-DB.patch To enable accessibility feature for data tables in the admin console, these techniques should be used: 1. Add caption tag or summary property to data table, for example table border=1 captionServer information/caption OR table border=1 summary=Server information 2. Add scope property to column and row headers, for example tr th scope=colProperty name/th th scope=colProperty value/th /tr tr tdGeronimo Version/td td2.1.1/td /tr The data tables on these pages shall be improved: Server-Information Server-Java System Info server-Web Server Server-Thread Pools Server-JMS Server Server-Monitoring Services-Database Pools Services-JMS Resources Applications-Web App WARs Applications-System modules Applications-Application EARs Applications-EJB JARs Applications-J2EE Connectors Applications-App Clients Security-Users and Groups Security-Keystores Security-Security Realms Embedded DB-DB Info Embedded DB-DB Manager -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4197) Use JAXB+DWR to eliminate ConfigData overhead
[ https://issues.apache.org/jira/browse/GERONIMO-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4197: --- Patch Info: [Patch Available] Use JAXB+DWR to eliminate ConfigData overhead - Key: GERONIMO-4197 URL: https://issues.apache.org/jira/browse/GERONIMO-4197 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shrey Banga Assignee: Shrey Banga Fix For: 2.2 Attachments: EAR_JAXB_1.patch Presently PlanCreator uses a set of ConfigData classes which basically wrap around xmlbean classes to create the deployment plans. These classes are exposed to DWR through EARHelper. As a result, a lot of code needs to be written to transfer data between multiple formats, ie from JSON to Java objects to XML. The idea is to use DWR to expose JAXB classes directly so that the xml can be generated using calls directly from the javascript, eliminating the ConfigData and EARHelper classes. This will ease the process of generating deployment plans, like that used by GEP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4196) Handle Resources in EAR PlanCreator
[ https://issues.apache.org/jira/browse/GERONIMO-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4196: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Handle Resources in EAR PlanCreator --- Key: GERONIMO-4196 URL: https://issues.apache.org/jira/browse/GERONIMO-4196 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shrey Banga Assignee: Shrey Banga Fix For: Wish List Create a Resource tab for adding application specific resources such as: 1. Database Connection Pools 2. JMS Connection Factories Destinations 3. Security Realms 4. Credential Stores The intention would be to reuse the existing wizards for theses resources by opening just the portlet in a popup, walk the user through it and update the information once the wizard closes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4195) Handle References in EAR PlanCreator
[ https://issues.apache.org/jira/browse/GERONIMO-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4195: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Handle References in EAR PlanCreator Key: GERONIMO-4195 URL: https://issues.apache.org/jira/browse/GERONIMO-4195 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shrey Banga Assignee: Shrey Banga Fix For: Wish List -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3433) Admin Console Wizard to auto generate geronimo-application.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3433: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Admin Console Wizard to auto generate geronimo-application.xml -- Key: GERONIMO-3433 URL: https://issues.apache.org/jira/browse/GERONIMO-3433 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shiva Kumar H R Assignee: Shrey Banga Fix For: Wish List For a background about this work please see GERONIMO-3254 GERONIMO-3432. Enhance Create Plan portlet other Admin Console Wizards to help server-administrators in auto creating the Geronimo Deployment Plan for a J2EE/Java-EE application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4197) Use JAXB+DWR to eliminate ConfigData overhead
[ https://issues.apache.org/jira/browse/GERONIMO-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4197: -- Assignee: (was: Shrey Banga) Unassigning, as a committer needs to review and apply the patch. Use JAXB+DWR to eliminate ConfigData overhead - Key: GERONIMO-4197 URL: https://issues.apache.org/jira/browse/GERONIMO-4197 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shrey Banga Fix For: 2.2 Attachments: EAR_JAXB_1.patch Presently PlanCreator uses a set of ConfigData classes which basically wrap around xmlbean classes to create the deployment plans. These classes are exposed to DWR through EARHelper. As a result, a lot of code needs to be written to transfer data between multiple formats, ie from JSON to Java objects to XML. The idea is to use DWR to expose JAXB classes directly so that the xml can be generated using calls directly from the javascript, eliminating the ConfigData and EARHelper classes. This will ease the process of generating deployment plans, like that used by GEP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4394) Run Geronimo as a Windows service out of box
[ https://issues.apache.org/jira/browse/GERONIMO-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4394: --- Attachment: GERONIMO-4394_Jack.patch Thanks Jarek for your advice! Now I've come out with a more impact version. I can successfully install the car to a running server to add those new commands into its bin dir. The only myth left is that after installation, the car in the server's repo is not a car archive, but extracted there. I've created a patch for the 2.1.x branch. It can be easily applied to 2.2 branch if all occurances of 2.1.4-SNAPSHOT are replaced with 2.2-SNAPSHOT. The patch does not include the 2 binary exe files though. I'm not sure about the convention of how to add them (in the patch or separately?), so I just attach them separately here. They should both be put into the plugins/osservice/geronimo-procrun/src/main/resources/bin/ dir. Run Geronimo as a Windows service out of box Key: GERONIMO-4394 URL: https://issues.apache.org/jira/browse/GERONIMO-4394 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Environment: Windows platforms Reporter: Jack Cai Assignee: Jack Cai Fix For: 2.2 Attachments: GERONIMO-4394_Jack.patch, osservice.zip Although there is already an option provided by the Java Service Wrapper, some users are more interested in seeing something similar to what is provided by Tomcat. Provided that we can easily take the technology from Tomcat (http://commons.apache.org/daemon/procrun.html), I'm keen to implement this same thing for Geronimo. The advantage of using Apache Commons procrun is that - 1. Out-of-box experience, no need to download and install a third party component; 2. Tray icon that further improves usability. Eventually we would think to provide this run as a service capability for Linux/Unix platforms, but Windows would be a good start. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3870) Expose JSR77 stats in OpenEJB
[ https://issues.apache.org/jira/browse/GERONIMO-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3870: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Expose JSR77 stats in OpenEJB - Key: GERONIMO-3870 URL: https://issues.apache.org/jira/browse/GERONIMO-3870 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, OpenEJB Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Erik B. Craig Fix For: Wish List There should be JSR77 compliant statistics exposed in OpenEJB so that they may be monitored/tracked with the monitoring plug-in -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4442) Unable to configure IP address for many listening ports
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4442: -- Assignee: Donald Woods Unable to configure IP address for many listening ports --- Key: GERONIMO-4442 URL: https://issues.apache.org/jira/browse/GERONIMO-4442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.1.3 Reporter: Kevan Miller Assignee: Donald Woods Priority: Critical Fix For: 2.1.4, 2.2 Attachments: G4222_ORBConfigAdapter.patch I tried to configure the listening IP address for our server sockets. I configured all 'host' properties in config-substitution.properties to be '127.0.0.1' and got the following results: Listening on Ports: 1050 127.0.0.1 CORBA Naming Service 1099 127.0.0.1 RMI Naming 1527 127.0.0.1 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 127.0.0.1 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 127.0.0.1 Tomcat Connector AJP AJP 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS 127.0.0.1 JMX Remoting Connector 61613 127.0.0.1 ActiveMQ Transport Connector 61616 127.0.0.1 ActiveMQ Transport Connector Unfortunately, that's not accurate. netstat reveals the following actual results: $ netstat -an | grep LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63519*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 127.0.0.1.4201 *.*LISTEN tcp4 0 0 127.0.0.1.61613*.*LISTEN tcp4 0 0 127.0.0.1.61616*.*LISTEN tcp4 0 0 127.0.0.1.1527 *.*LISTEN tcp4 0 0 127.0.0.1.8443 *.*LISTEN tcp4 0 0 127.0.0.1.8009 *.*LISTEN tcp4 0 0 127.0.0.1.8080 *.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN Configuring the host properties to be an actual ip address/hostname is a bit worse (not sure what's going on with ActiveMQ): Listening on Ports: 1050 10.0.1.196 CORBA Naming Service 1099 10.0.1.196 RMI Naming 1527 10.0.1.196 Derby Connector 2001 10.0.1.196 OpenEJB ORB Adapter 4201 10.0.1.196 OpenEJB Daemon 6882 10.0.1.196 OpenEJB ORB Adapter 8009 10.0.1.196 Tomcat Connector AJP AJP 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS 10.0.1.196 JMX Remoting Connector 61613 0.0.0.0ActiveMQ Transport Connector 61616 0.0.0.0ActiveMQ Transport Connector Netstat shows: $ netstat -an | grep LISTEN tcp6 0 0 fe80::1%lo0.631*.*LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63569*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 10.0.1.196.4201*.*LISTEN tcp4 0 0 *.61613*.*LISTEN tcp4 0 0 *.61616*.*LISTEN tcp4 0 0 10.0.1.196.1527*.*LISTEN tcp4 0 0 10.0.1.196.8443*.*LISTEN tcp4 0 0 10.0.1.196.8009*.*LISTEN tcp4 0 0 10.0.1.196.8080*.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3886) Create portles to allow GShell instances in a Geronimo server to be configured via the Web UI
[ https://issues.apache.org/jira/browse/GERONIMO-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3886: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Create portles to allow GShell instances in a Geronimo server to be configured via the Web UI - Key: GERONIMO-3886 URL: https://issues.apache.org/jira/browse/GERONIMO-3886 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Jason Dillon Fix For: Wish List -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3885) Create GBean(s) to launch a GShell instance in a Geronimo server
[ https://issues.apache.org/jira/browse/GERONIMO-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3885: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Create GBean(s) to launch a GShell instance in a Geronimo server Key: GERONIMO-3885 URL: https://issues.apache.org/jira/browse/GERONIMO-3885 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: Jason Dillon Fix For: Wish List Need a GBean (or two) to launch a GShell instance (or more than one if desired) inside of a Geronimo server. Needs to have some configuration for options and an initial set of commands to execute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3661) Optimize GShell libs for G server assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3661: --- Affects Version/s: 2.2 Fix Version/s: (was: 2.2) Wish List Requires a new GShell release, which will not be ready in time for 2.2, so moving to Wish List. Optimize GShell libs for G server assemblies Key: GERONIMO-3661 URL: https://issues.apache.org/jira/browse/GERONIMO-3661 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.1, 2.2 Reporter: Jason Dillon Assignee: Jason Dillon Priority: Blocker Fix For: Wish List -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4200) Create plugins to enable cgi-bin support in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4200: --- Affects Version/s: 2.2 2.1.4 Fix Version/s: (was: 2.1.4) (was: 2.2) Wish List Also need a solution for Jetty users. Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Create plugins to enable cgi-bin support in Geronimo Key: GERONIMO-4200 URL: https://issues.apache.org/jira/browse/GERONIMO-4200 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Fix For: Wish List Attachments: cgi-bin.war A user asked about enabling cgi-bin support in Geronimo. Would be nice if we had Jetty/Tomcat plugins to enable this support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4394) Run Geronimo as a Windows service out of box
[ https://issues.apache.org/jira/browse/GERONIMO-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4394: --- Attachment: geronimosrv.exe This file should go to plugins/osservice/geronimo-procrun/src/main/resources/bin/. It is compiled from Apache Commons Daemo rev727325 with the patch attached in https://issues.apache.org/jira/browse/DAEMON-118 from me. Run Geronimo as a Windows service out of box Key: GERONIMO-4394 URL: https://issues.apache.org/jira/browse/GERONIMO-4394 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Environment: Windows platforms Reporter: Jack Cai Assignee: Jack Cai Fix For: 2.2 Attachments: GERONIMO-4394_Jack.patch, geronimosrv.exe, geronimosrvw.exe, osservice.zip Although there is already an option provided by the Java Service Wrapper, some users are more interested in seeing something similar to what is provided by Tomcat. Provided that we can easily take the technology from Tomcat (http://commons.apache.org/daemon/procrun.html), I'm keen to implement this same thing for Geronimo. The advantage of using Apache Commons procrun is that - 1. Out-of-box experience, no need to download and install a third party component; 2. Tray icon that further improves usability. Eventually we would think to provide this run as a service capability for Linux/Unix platforms, but Windows would be a good start. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4011) Need new release of JLine to fix GShell problems on Windows
[ https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4011: --- Affects Version/s: 2.1.4 2.1.3 Fix Version/s: (was: 2.2) Wish List Hopefully will not be needed once we have a newer GShell release. Need new release of JLine to fix GShell problems on Windows --- Key: GERONIMO-4011 URL: https://issues.apache.org/jira/browse/GERONIMO-4011 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Jason Dillon Fix For: Wish List Attachments: jline-0.9.95-SNAPSHOT.jar There are several GShell problems on Windows, due to JLine bugs. I'm going to try and create a patched build of JLine 0.9.94 to resolve these issues, as Geronimo packages the JLine jar into our assembly for GShell to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4324) Upgrade to MyFaces v1.2.4
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4324: --- Fix Version/s: (was: 2.1.4) (was: 2.0.3) (was: 2.2) Wish List Moving to Wish List, as v1.2.4 caused TCK failures. Upgrade to MyFaces v1.2.4 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Minor Fix For: Wish List Upgrade to MyFaces v1.2.4 released on August 30th. Release Notes - https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12313378 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (GSHELL-151) Repackage org.apache.geronimo.gshell.* - org.apache.gshell.*
On Dec 16, 2008, at 11:41 AM, Donald Woods wrote: Seems like something we should vote on, given our specs, samples, components and plugin subprojects all use org.apache.geronimo.* IMO specs, samples, components and plugins are all specific to geronimo, so the sub-package makes sense. xbean on the other hand is not geronimo specific directly under o.a. IMO GShell is not geronimo-specific, closer in nature to xbean than to specs or components. So for me the change of packages makes a lot of sense. --jason -Donald Jason Dillon wrote: No, it just seems that subprojects don't seem to use the parents namespace. mina, activemq seems to follow that, even xbean does that. so i figured I would drop the extra layer. --jason On Dec 16, 2008, at 12:39 AM, Donald Woods wrote: Are you proposing GShell becoming a TLP and not a Geronimo subproject? -Donald Jason Dillon (JIRA) wrote: Repackage org.apache.geronimo.gshell.* - org.apache.gshell.* - Key: GSHELL-151 URL: https://issues.apache.org/jira/browse/ GSHELL-151 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Build Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 1.0-beta-1
How can we get the TranQL connectors for MS SQL, Informix and Oracle RAC released?
We have several TranQL connectors that can be pulled into the Geronimo 2.2 release, if we can get the TranQL project to accept and release them: GERONIMO-4365 - Informix XA GERONIMO-4297 - Oracle RAC GERONIMO-4279 - Microsoft SQL 2000/2005 XA Anyone have time to do this or should we just pull them into our svn components branch and release them as Geronimo artifacts? -Donald
[jira] Commented: (GERONIMO-4394) Run Geronimo as a Windows service out of box
[ https://issues.apache.org/jira/browse/GERONIMO-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657515#action_12657515 ] Jarek Gawor commented on GERONIMO-4394: --- I'm unable to execute the attached .exe files. Maybe they got corrupted somehow or do I need to do something else to run them (e.g. install some dll)? Run Geronimo as a Windows service out of box Key: GERONIMO-4394 URL: https://issues.apache.org/jira/browse/GERONIMO-4394 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Environment: Windows platforms Reporter: Jack Cai Assignee: Jack Cai Fix For: 2.2 Attachments: GERONIMO-4394_Jack.patch, geronimosrv.exe, geronimosrvw.exe, osservice.zip Although there is already an option provided by the Java Service Wrapper, some users are more interested in seeing something similar to what is provided by Tomcat. Provided that we can easily take the technology from Tomcat (http://commons.apache.org/daemon/procrun.html), I'm keen to implement this same thing for Geronimo. The advantage of using Apache Commons procrun is that - 1. Out-of-box experience, no need to download and install a third party component; 2. Tray icon that further improves usability. Eventually we would think to provide this run as a service capability for Linux/Unix platforms, but Windows would be a good start. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4365) Pull in TranQL Informix XA connector
[ https://issues.apache.org/jira/browse/GERONIMO-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4365: -- Assignee: Donald Woods Pull in TranQL Informix XA connector Key: GERONIMO-4365 URL: https://issues.apache.org/jira/browse/GERONIMO-4365 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: databases Affects Versions: 2.1.3, 2.2 Reporter: Rex Wang Assignee: Donald Woods Fix For: 2.1.4, 2.2 We can pull in the patch in TranQL which provides informix XA connector. http://jira.codehaus.org/browse/TQL-12 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4279) Pull in TranQL SQLServer 2000 and 2005 XA connector
[ https://issues.apache.org/jira/browse/GERONIMO-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4279: -- Assignee: Donald Woods Pull in TranQL SQLServer 2000 and 2005 XA connector Key: GERONIMO-4279 URL: https://issues.apache.org/jira/browse/GERONIMO-4279 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: databases Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: Jack Cai Assignee: Donald Woods There is a patch in TranQL that provides SQL Server 2000 and 2005 XA connector [1]. It will be useful to pull it into Geronimo. [1] http://jira.codehaus.org/browse/TQL-11 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4451) locking and unlocking for availability of a keystore results in duplicate attributes in config.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4451: -- Assignee: Donald Woods locking and unlocking for availability of a keystore results in duplicate attributes in config.xml -- Key: GERONIMO-4451 URL: https://issues.apache.org/jira/browse/GERONIMO-4451 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.3 Environment: Ubuntu Linux 8.10, Sun Java 1.6, Geronimo 2.1.3 w/ Jetty. Reporter: Christian Svensson Assignee: Donald Woods Fix For: 2.1.4, 2.2 Transcribing mail conversation: Hello! I've been trying for the better part of today getting keystores to automatically unlock on startup - with very limited success. Is there something that I should know about keystore password / key password? Digging around some old mailing list threads said something about key password must be equal to keystore password - any more of those gotchas? The problem is that I create (or change password on geronimo-default for that matter) a new keystore, assign SSL to use the certificate and restart the server: org.apache.geronimo.management.geronimo.KeystoreIsLocked: Keystore 'plasma-ssl' is locked; please use the keystore page in the admin console to unlock it at org.apache.geronimo.security.keystore.FileKeystoreManager.createSSLContext(FileKeystoreManager.java:343) at org.apache.geronimo.jetty6.connector.GeronimoSelectChannelSSLListener.createSSLContext(GeronimoSelectChannelSSLListener.java:54) Resetting the SSL connector to using geronimo-default / geronimo with secret / secret as passwords makes it work again - but why on earth doesn't Geronimo unlock my keystores on startup? I mean, it saves the password (or something like it) in config.xml. - This is how I created my setup: 1. Create a new keystore 'plasma-ssl' 2. Create a new private key 'wildcard' 3. Now the text on Available says trust only or something like that, I lock it and then unlock it in order for it to change to 1 key ready 4. Then I configure my HTTPS connector to use the new keystore 5. Since the web server does not seem to do anything when I press Shutdown in the console, I use Ctrl+C to kill it. 6. Start the server again 7. Message appears. --- Hmm... the 3rd step is indeed unearthing a bug. At that step, a second attribute element is getting added (instead of replacing the existing element) to the keystore gbean for keystorePassword and keyPasswords attributes in config.xml . Can you create an issue in the JIRA [1]? The problem summary is, locking and unlocking for availability of a keystore results in duplicate attributes in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4464) GShell does not support login option of old deploy scripts
[ https://issues.apache.org/jira/browse/GERONIMO-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4464: --- Fix Version/s: (was: 2.1.4) (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. GShell does not support login option of old deploy scripts -- Key: GERONIMO-4464 URL: https://issues.apache.org/jira/browse/GERONIMO-4464 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands, startup/shutdown Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Priority: Minor Fix For: Wish List The deploy.sh login function is missing from gsh. Also need this to use gsh for user scripting without requiring users to hard-code username/password in their scripts. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4418) Sample on how to setup app specific JUL logging
[ https://issues.apache.org/jira/browse/GERONIMO-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4418: --- Fix Version/s: (was: 2.2) Wish List Summary: Sample on how to setup app specific JUL logging (was: Sample on how to setup app specific logging) Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Sample on how to setup app specific JUL logging --- Key: GERONIMO-4418 URL: https://issues.apache.org/jira/browse/GERONIMO-4418 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Reporter: Donald Woods Priority: Minor Fix For: Wish List From the user list at - http://www.nabble.com/Configuring-log4j-as-jvm-environment-variable-fails-to20378195s134.html#a20378195 We should create a new sample to show users how to setup custom logging for their web apps. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (GSHELL-151) Repackage org.apache.geronimo.gshell.* - org.apache.gshell.*
On Dec 17, 2008, at 7:27 AM, Jason Dillon wrote: On Dec 16, 2008, at 11:41 AM, Donald Woods wrote: Seems like something we should vote on, given our specs, samples, components and plugin subprojects all use org.apache.geronimo.* IMO specs, samples, components and plugins are all specific to geronimo, so the sub-package makes sense. xbean on the other hand is not geronimo specific directly under o.a. IMO GShell is not geronimo-specific, closer in nature to xbean than to specs or components. So for me the change of packages makes a lot of sense. I agree. There's no requirement that sub-projects fall under a top-level project namespace. There are certainly lots of examples of this... XBean and Yoko being two examples within Geronimo. There are lot's of examples outside of Geronimo... If we have a fundamental difference of opinion on this, then we can certainly put it to a group vote. Barring such a disagreement, I don't think a vote is needed... I'll assume that subsequent discussion will determine if a vote is needed. --kevan
[jira] Updated: (GERONIMO-4437) Upgrade to Jetty 6.1.11
[ https://issues.apache.org/jira/browse/GERONIMO-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4437: --- Fix Version/s: (was: 2.2) Wish List Both Jetty 6.1.11 and 6.1.14 had issues, so moving this out of 2.2. Upgrade to Jetty 6.1.11 --- Key: GERONIMO-4437 URL: https://issues.apache.org/jira/browse/GERONIMO-4437 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies, Jetty Affects Versions: 2.2 Reporter: Donald Woods Assignee: Joe Bohn Fix For: Wish List Upgrade to newer Jetty release, 6.1.11. We looked into 6.1.14 but that causes some tck issues for us so we'll use 6.1.11 for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4394) Run Geronimo as a Windows service out of box
[ https://issues.apache.org/jira/browse/GERONIMO-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4394: --- Attachment: geronimosrvw.exe This file should go to plugins/osservice/geronimo-procrun/src/main/resources/bin/. It is compiled from Apache Commons Daemo rev727325 without any changes. Run Geronimo as a Windows service out of box Key: GERONIMO-4394 URL: https://issues.apache.org/jira/browse/GERONIMO-4394 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Environment: Windows platforms Reporter: Jack Cai Assignee: Jack Cai Fix For: 2.2 Attachments: GERONIMO-4394_Jack.patch, geronimosrvw.exe, osservice.zip Although there is already an option provided by the Java Service Wrapper, some users are more interested in seeing something similar to what is provided by Tomcat. Provided that we can easily take the technology from Tomcat (http://commons.apache.org/daemon/procrun.html), I'm keen to implement this same thing for Geronimo. The advantage of using Apache Commons procrun is that - 1. Out-of-box experience, no need to download and install a third party component; 2. Tray icon that further improves usability. Eventually we would think to provide this run as a service capability for Linux/Unix platforms, but Windows would be a good start. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4420) Create Files under repository even if fail to deploy a jar having problems.
[ https://issues.apache.org/jira/browse/GERONIMO-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4420: --- Patch Info: [Patch Available] Assignee: Donald Woods Create Files under repository even if fail to deploy a jar having problems. --- Key: GERONIMO-4420 URL: https://issues.apache.org/jira/browse/GERONIMO-4420 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1.3 Environment: OS:Any platform Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4420.patch, testejb.jar Defect transfers from GEP: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Steps: 1.Deploy attached testejb.jar, and this jar has some problems in it.So when deploy it via command or admin console, errors exist. 2.But in repository, files for this deployed jar are created already.If i redeploy this jar or deploy it second time, it will inform me : it exists in repository, i should remove it manually from repository. no log in server.log. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4295) Upgrade to Derby 10.4.2.0
[ https://issues.apache.org/jira/browse/GERONIMO-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMO-4295. -- Resolution: Fixed Fix Version/s: (was: 2.0.4) (was: 2.1.4) Upgrade to Derby 10.4.2.0 - Key: GERONIMO-4295 URL: https://issues.apache.org/jira/browse/GERONIMO-4295 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.3, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Minor Fix For: 2.2 Upgrade to Derby 10.4.2.0, which was released on Sept. 5, 2008. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4295) Upgrade to Derby 10.4.2.0
[ https://issues.apache.org/jira/browse/GERONIMO-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-4295: -- Fix Version/s: 2.1.4 Looks like Derby version was also updated in branches/2.0. Upgrade to Derby 10.4.2.0 - Key: GERONIMO-4295 URL: https://issues.apache.org/jira/browse/GERONIMO-4295 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.3, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Minor Fix For: 2.1.4, 2.2 Upgrade to Derby 10.4.2.0, which was released on Sept. 5, 2008. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4295) Upgrade to Derby 10.4.2.0
[ https://issues.apache.org/jira/browse/GERONIMO-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-4295: -- Fix Version/s: (was: 2.1.4) 2.0.3 Upgrade to Derby 10.4.2.0 - Key: GERONIMO-4295 URL: https://issues.apache.org/jira/browse/GERONIMO-4295 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.3, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Minor Fix For: 2.0.3, 2.2 Upgrade to Derby 10.4.2.0, which was released on Sept. 5, 2008. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2451) Deployment fails
[ https://issues.apache.org/jira/browse/GERONIMO-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-2451: --- Fix Version/s: (was: 2.1.4) (was: 2.2) Verification Required Need further details from the user, since the Console deploys and local cmdline deploy works. Have you modified the default ports or hostnames in config-substitutions.properties or config.xml? Is there a firewall on the remote machine that blocks non-HTTP traffic? Have you changed the default Geronimo admin uid/pwd (system/manager) on the remote machine? Deployment fails Key: GERONIMO-2451 URL: https://issues.apache.org/jira/browse/GERONIMO-2451 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.1.1, 2.1.3 Environment: Windows XP Professional, Sun JDK 1.4.2_12, geronimo-tomcat-j2ee-1.1.1.zip Reporter: Ali Sadik Kumlali Fix For: Verification Required Hi, 1) When I deploy the sample application's[1] jms-resource-plan.xml from Geronimo Server Console, I get Deployer operation failed exception [2]. When I deploy it from the command line[3] it is deployed without any problem. 2) When I deploy sample's ear file (Order.ear) I get the same error [4]. But this time, deploying from command line[5] doesn't work either[6] 3) When I extract ejb jar (OrderEjb.jar) from the ear (Order.ear) and deploy it from Geronimo Server Console, it works without a problem. I made some Googling and found a very similar problem[7] regarding 1.0 release which was expected to be fixed in 1.1. I, in fact, didn't see this problem with 1.1. [1] http://cwiki.apache.org/confluence/display/GMOxDOC11/JMS+and+MDB+sample+application [2] Deployer operation failed: Cound not open module file: D:\programs\geronimo\var\ temp\geronimo-deployer25421.tmpdir\jms-resource-plan.xml org.apache.geronimo.common.DeploymentException: Cound not open module file: D:\p rograms\geronimo\var\temp\geronimo-deployer25421.tmpdir\jms-resource-plan.xml at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:221) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.i nvoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:852) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doD eploy(AbstractDeployCommand.java:106) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(Dis tributeCommand.java:60) at java.lang.Thread.run(Thread.java:534) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:111) at java.util.jar.JarFile.init(JarFile.java:127) at java.util.jar.JarFile.init(JarFile.java:92) at org.apache.geronimo.deployment.util.DeploymentUtil.createJarFile(Depl oymentUtil.java:187) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:219) ... 10 more [Fatal Error] :1:1: Content is not allowed in prolog. [3] java -jar deployer.jar --user system --password manager deploy c:\tmp\ge-activemq-rar-1.1.1.rar c:\tmp\jms-resource-plan.xml [4] Deployer operation failed: Invalid moduleFile: OrderEjb.jar org.apache.geronimo.common.DeploymentException: Invalid moduleFile: OrderEjb.jar at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARCo nfigBuilder.java:748) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARCo nfigBuilder.java:364) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPla n(EARConfigBuilder.java:263) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLI B$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at
[jira] Updated: (GERONIMO-4313) Deploy exploded web application from Console
[ https://issues.apache.org/jira/browse/GERONIMO-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4313: --- Affects Version/s: 2.2 Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Deploy exploded web application from Console Key: GERONIMO-4313 URL: https://issues.apache.org/jira/browse/GERONIMO-4313 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Reporter: Jürgen Weber Fix For: Wish List Attachments: fileChooser.png Deploying exploded web applications from the Geronimo Console is not possible, this has to be done with the deploy tool: ./deploy.sh deploy --inPlace /mywebapp Deployment of server-accessible web applications should also be possible via the Geronimo Console. Generally, it should be possible to do everything via the Console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address for many listening ports
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657533#action_12657533 ] Donald Woods commented on GERONIMO-4442: ORBConfigAdapter patch from Shawn applied to trunk (2.2-SNAPSHOT) and 2.1.4-SNAPSHOT. Unable to configure IP address for many listening ports --- Key: GERONIMO-4442 URL: https://issues.apache.org/jira/browse/GERONIMO-4442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.1.3 Reporter: Kevan Miller Assignee: Donald Woods Priority: Critical Fix For: 2.1.4, 2.2 Attachments: G4222_ORBConfigAdapter.patch I tried to configure the listening IP address for our server sockets. I configured all 'host' properties in config-substitution.properties to be '127.0.0.1' and got the following results: Listening on Ports: 1050 127.0.0.1 CORBA Naming Service 1099 127.0.0.1 RMI Naming 1527 127.0.0.1 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 127.0.0.1 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 127.0.0.1 Tomcat Connector AJP AJP 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS 127.0.0.1 JMX Remoting Connector 61613 127.0.0.1 ActiveMQ Transport Connector 61616 127.0.0.1 ActiveMQ Transport Connector Unfortunately, that's not accurate. netstat reveals the following actual results: $ netstat -an | grep LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63519*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 127.0.0.1.4201 *.*LISTEN tcp4 0 0 127.0.0.1.61613*.*LISTEN tcp4 0 0 127.0.0.1.61616*.*LISTEN tcp4 0 0 127.0.0.1.1527 *.*LISTEN tcp4 0 0 127.0.0.1.8443 *.*LISTEN tcp4 0 0 127.0.0.1.8009 *.*LISTEN tcp4 0 0 127.0.0.1.8080 *.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN Configuring the host properties to be an actual ip address/hostname is a bit worse (not sure what's going on with ActiveMQ): Listening on Ports: 1050 10.0.1.196 CORBA Naming Service 1099 10.0.1.196 RMI Naming 1527 10.0.1.196 Derby Connector 2001 10.0.1.196 OpenEJB ORB Adapter 4201 10.0.1.196 OpenEJB Daemon 6882 10.0.1.196 OpenEJB ORB Adapter 8009 10.0.1.196 Tomcat Connector AJP AJP 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS 10.0.1.196 JMX Remoting Connector 61613 0.0.0.0ActiveMQ Transport Connector 61616 0.0.0.0ActiveMQ Transport Connector Netstat shows: $ netstat -an | grep LISTEN tcp6 0 0 fe80::1%lo0.631*.*LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63569*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 10.0.1.196.4201*.*LISTEN tcp4 0 0 *.61613*.*LISTEN tcp4 0 0 *.61616*.*LISTEN tcp4 0 0 10.0.1.196.1527*.*LISTEN tcp4 0 0 10.0.1.196.8443*.*LISTEN tcp4 0 0 10.0.1.196.8009*.*LISTEN tcp4 0 0 10.0.1.196.8080*.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-1511) Rewrite JMS portlet
[ https://issues.apache.org/jira/browse/GERONIMO-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657365#action_12657365 ] Donald Woods commented on GERONIMO-1511: For the new AMQ 5.2 support, no one is looking at updating the JMS Server portlet to handle the new XML/Spring based config. So any help would be greatly appreciated! Rewrite JMS portlet --- Key: GERONIMO-1511 URL: https://issues.apache.org/jira/browse/GERONIMO-1511 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: ActiveMQ, connector, console Affects Versions: 1.0 Reporter: Aaron Mulder Assignee: David Jencks Fix For: 2.2 The JMS connection factory and destination portlets should be replaced by a single JMS manager portlet. This should use the JMSManager and show all the available JMS brokers, listing the available connection factories and destinations for each one. When adding a connection factory or destination, it should use the JSR-88 DConfigBeans to construct the deployment plan for the new configuration. I'm not yet sure whether it should group the resources by configuration, perhaps just list the owning configuration there. I'm also not sure whether it's important to be able to add connection factories and destinations simultaneously in a single new configuration -- probably not, though it would be nice in terms of generating plans and so on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4442) Unable to configure IP address for many listening ports
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4442: --- Patch Info: [Patch Available] Assignee: Kevan Miller (was: Donald Woods) Kevan, anything else needed for this JIRA? Unable to configure IP address for many listening ports --- Key: GERONIMO-4442 URL: https://issues.apache.org/jira/browse/GERONIMO-4442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.1.3 Reporter: Kevan Miller Assignee: Kevan Miller Priority: Critical Fix For: 2.1.4, 2.2 Attachments: G4222_ORBConfigAdapter.patch I tried to configure the listening IP address for our server sockets. I configured all 'host' properties in config-substitution.properties to be '127.0.0.1' and got the following results: Listening on Ports: 1050 127.0.0.1 CORBA Naming Service 1099 127.0.0.1 RMI Naming 1527 127.0.0.1 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 127.0.0.1 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 127.0.0.1 Tomcat Connector AJP AJP 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS 127.0.0.1 JMX Remoting Connector 61613 127.0.0.1 ActiveMQ Transport Connector 61616 127.0.0.1 ActiveMQ Transport Connector Unfortunately, that's not accurate. netstat reveals the following actual results: $ netstat -an | grep LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63519*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 127.0.0.1.4201 *.*LISTEN tcp4 0 0 127.0.0.1.61613*.*LISTEN tcp4 0 0 127.0.0.1.61616*.*LISTEN tcp4 0 0 127.0.0.1.1527 *.*LISTEN tcp4 0 0 127.0.0.1.8443 *.*LISTEN tcp4 0 0 127.0.0.1.8009 *.*LISTEN tcp4 0 0 127.0.0.1.8080 *.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN Configuring the host properties to be an actual ip address/hostname is a bit worse (not sure what's going on with ActiveMQ): Listening on Ports: 1050 10.0.1.196 CORBA Naming Service 1099 10.0.1.196 RMI Naming 1527 10.0.1.196 Derby Connector 2001 10.0.1.196 OpenEJB ORB Adapter 4201 10.0.1.196 OpenEJB Daemon 6882 10.0.1.196 OpenEJB ORB Adapter 8009 10.0.1.196 Tomcat Connector AJP AJP 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS 10.0.1.196 JMX Remoting Connector 61613 0.0.0.0ActiveMQ Transport Connector 61616 0.0.0.0ActiveMQ Transport Connector Netstat shows: $ netstat -an | grep LISTEN tcp6 0 0 fe80::1%lo0.631*.*LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63569*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 10.0.1.196.4201*.*LISTEN tcp4 0 0 *.61613*.*LISTEN tcp4 0 0 *.61616*.*LISTEN tcp4 0 0 10.0.1.196.1527*.*LISTEN tcp4 0 0 10.0.1.196.8443*.*LISTEN tcp4 0 0 10.0.1.196.8009*.*LISTEN tcp4 0 0 10.0.1.196.8080*.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-4394) Run Geronimo as a Windows service out of box
[ https://issues.apache.org/jira/browse/GERONIMO-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657321#action_12657321 ] caijunj edited comment on GERONIMO-4394 at 12/17/08 2:01 AM: -- Thanks Jarek for your advice! Now I've come out with a more compact version. I can successfully install the car to a running server to add those new commands into its bin dir. The only myth left is that after installation, the car in the server's repo is not a car archive, but extracted there. I've created a patch for the 2.1.x branch. It can be easily applied to 2.2 branch if all occurances of 2.1.4-SNAPSHOT are replaced with 2.2-SNAPSHOT. The patch does not include the 2 binary exe files though. I'm not sure about the convention of how to add them (in the patch or separately?), so I just attach them separately here. They should both be put into the plugins/osservice/geronimo-procrun/src/main/resources/bin/ dir. was (Author: caijunj): Thanks Jarek for your advice! Now I've come out with a more impact version. I can successfully install the car to a running server to add those new commands into its bin dir. The only myth left is that after installation, the car in the server's repo is not a car archive, but extracted there. I've created a patch for the 2.1.x branch. It can be easily applied to 2.2 branch if all occurances of 2.1.4-SNAPSHOT are replaced with 2.2-SNAPSHOT. The patch does not include the 2 binary exe files though. I'm not sure about the convention of how to add them (in the patch or separately?), so I just attach them separately here. They should both be put into the plugins/osservice/geronimo-procrun/src/main/resources/bin/ dir. Run Geronimo as a Windows service out of box Key: GERONIMO-4394 URL: https://issues.apache.org/jira/browse/GERONIMO-4394 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Environment: Windows platforms Reporter: Jack Cai Assignee: Jack Cai Fix For: 2.2 Attachments: GERONIMO-4394_Jack.patch, geronimosrv.exe, geronimosrvw.exe, osservice.zip Although there is already an option provided by the Java Service Wrapper, some users are more interested in seeing something similar to what is provided by Tomcat. Provided that we can easily take the technology from Tomcat (http://commons.apache.org/daemon/procrun.html), I'm keen to implement this same thing for Geronimo. The advantage of using Apache Commons procrun is that - 1. Out-of-box experience, no need to download and install a third party component; 2. Tray icon that further improves usability. Eventually we would think to provide this run as a service capability for Linux/Unix platforms, but Windows would be a good start. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address for many listening ports
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657543#action_12657543 ] Kevan Miller commented on GERONIMO-4442: Not clear to me from the jira comments that ActiveMQ has been fixed. Looks like we're at least close... Thanks Shawn, Jarek, and Donald! Has anybody tested with the latest source? Unable to configure IP address for many listening ports --- Key: GERONIMO-4442 URL: https://issues.apache.org/jira/browse/GERONIMO-4442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.1.3 Reporter: Kevan Miller Assignee: Kevan Miller Priority: Critical Fix For: 2.1.4, 2.2 Attachments: G4222_ORBConfigAdapter.patch I tried to configure the listening IP address for our server sockets. I configured all 'host' properties in config-substitution.properties to be '127.0.0.1' and got the following results: Listening on Ports: 1050 127.0.0.1 CORBA Naming Service 1099 127.0.0.1 RMI Naming 1527 127.0.0.1 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 127.0.0.1 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 127.0.0.1 Tomcat Connector AJP AJP 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS 127.0.0.1 JMX Remoting Connector 61613 127.0.0.1 ActiveMQ Transport Connector 61616 127.0.0.1 ActiveMQ Transport Connector Unfortunately, that's not accurate. netstat reveals the following actual results: $ netstat -an | grep LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63519*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 127.0.0.1.4201 *.*LISTEN tcp4 0 0 127.0.0.1.61613*.*LISTEN tcp4 0 0 127.0.0.1.61616*.*LISTEN tcp4 0 0 127.0.0.1.1527 *.*LISTEN tcp4 0 0 127.0.0.1.8443 *.*LISTEN tcp4 0 0 127.0.0.1.8009 *.*LISTEN tcp4 0 0 127.0.0.1.8080 *.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN Configuring the host properties to be an actual ip address/hostname is a bit worse (not sure what's going on with ActiveMQ): Listening on Ports: 1050 10.0.1.196 CORBA Naming Service 1099 10.0.1.196 RMI Naming 1527 10.0.1.196 Derby Connector 2001 10.0.1.196 OpenEJB ORB Adapter 4201 10.0.1.196 OpenEJB Daemon 6882 10.0.1.196 OpenEJB ORB Adapter 8009 10.0.1.196 Tomcat Connector AJP AJP 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS 10.0.1.196 JMX Remoting Connector 61613 0.0.0.0ActiveMQ Transport Connector 61616 0.0.0.0ActiveMQ Transport Connector Netstat shows: $ netstat -an | grep LISTEN tcp6 0 0 fe80::1%lo0.631*.*LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63569*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 10.0.1.196.4201*.*LISTEN tcp4 0 0 *.61613*.*LISTEN tcp4 0 0 *.61616*.*LISTEN tcp4 0 0 10.0.1.196.1527*.*LISTEN tcp4 0 0 10.0.1.196.8443*.*LISTEN tcp4 0 0 10.0.1.196.8009*.*LISTEN tcp4 0 0 10.0.1.196.8080*.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo VM-appliance?
On Dec 15, 2008, at 3:45 AM, Jason Dillon wrote: On Dec 15, 2008, at 3:24 PM, David Jencks wrote: I think this is a great idea. I doubt we can host it at apache. unless we do something like bsd + harmony (not even sure if that is likely to work) Thats what I've been realizing... But can we link to it/documented it from apache? I don't see why not... We could not release any non-ASF compatibly licensed binaries (e.g. (L)GPL) from Apache. However, this does not prevent us from providing build/configuration support for such an appliance. We could provide instructions on how to obtain incompatible licensed artifacts. Just need to make sure that users understand that their actions may have potential licensing implications. If the *only* realization of this work requires the presence of (L)GPL artifacts, then, IIUC, it might need to be hosted outside of Apache. This would require some analysis on our part as well as a review on legal-disc...@. Regardless, assuming the work is useful to Geronimo users, I'd think we'd want to let Geronimo users know about it. We'd do this for any other Geronimo-related works, also... So, I don't see an issue with linking to and describing the project. Documenting the project might be another issue... --kevan
[jira] Commented: (GERONIMO-4084) Set up samples with itests and plugins and a separate datasource plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657526#action_12657526 ] Donald Woods commented on GERONIMO-4084: Is there more work to do? If so, what? Set up samples with itests and plugins and a separate datasource plugin --- Key: GERONIMO-4084 URL: https://issues.apache.org/jira/browse/GERONIMO-4084 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.x, 2.2 Reporter: David Jencks Fix For: 2.2 1. separate datasource definition into a separate plugin 2. provide plugin integration tests that at least check that the plugins can be installed into a running server Unclear if we need also a demo of how to include the datasource in the main plugin. Unclear if this should be included in the 2.1 samples release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4419) Create a TomcatUsersLoginModule that can use unmodified tomcat-users.xml files
[ https://issues.apache.org/jira/browse/GERONIMO-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4419: --- Fix Version/s: (was: 2.2) Wish List Moving to Wish List, as this is not critical enough to hold up the 2.2 release. Create a TomcatUsersLoginModule that can use unmodified tomcat-users.xml files -- Key: GERONIMO-4419 URL: https://issues.apache.org/jira/browse/GERONIMO-4419 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: security Reporter: Donald Woods Priority: Minor Fix For: Wish List Allow Tomcat users to use their tomcat-users.xml unmodified in Geronimo by creating a new LoginModule security provider. See http://www.nabble.com/Geronimo-security-question-to20244202s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-546) add summary page to Server Plugin Manager
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed resolved GERONIMODEVTOOLS-546. Resolution: Fixed Fixed with r727514. Added another page to the wizard that has a table that lists the plugins that were removed or added to the server during the final installation process. add summary page to Server Plugin Manager - Key: GERONIMODEVTOOLS-546 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-546 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Reporter: B.J. Reed Assignee: B.J. Reed Priority: Minor Fix For: 2.2.0, 2.1.4 Would be nice to have a final page to show all the things that got added to or removed from the server during the processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: How can we get the TranQL connectors for MS SQL, Informix and Oracle RAC released?
On Dec 17, 2008, at 11:53 AM, Donald Woods wrote: We have several TranQL connectors that can be pulled into the Geronimo 2.2 release, if we can get the TranQL project to accept and release them: GERONIMO-4365 - Informix XA GERONIMO-4297 - Oracle RAC GERONIMO-4279 - Microsoft SQL 2000/2005 XA Anyone have time to do this or should we just pull them into our svn components branch and release them as Geronimo artifacts? I doubt we can host the code at apache for licensing reasons. I'll see if I can make some time to look at this. david jencks -Donald
[jira] Commented: (GERONIMO-4442) Unable to configure IP address for many listening ports
[
https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657564#action_12657564
]
Kevan Miller commented on GERONIMO-4442:
Hmm. I'm getting the following error trying to start a server on my Mac:
{noformat}
2008-12-17 16:15:29,776 WARN [2-SNAPSHOT/car,j2eeType=GBean,name=JMXService]
Failure in JMXConnector
service:jmx:rmi://0.0.0.0:/jndi/rmi://0.0.0.0:1099/JMXConnector
2008-12-17 16:15:29,777 ERROR [GBeanInstanceState] Error while starting; GBean
is now in the FAILED state:
abstractName=org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car,j2eeType=GBean,name=JMXService
java.io.IOException: Cannot bind to URL [rmi://0.0.0.0:1099/JMXConnector]:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 0.0.0.0; nested
exception is:
java.net.ConnectException: Operation timed out]
at
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at
org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.java:201)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$7713edc.startConfiguration(generated)
at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
{noformat}
Anybody else?
Unable to configure IP address for many listening ports
---
Key: GERONIMO-4442
URL: https://issues.apache.org/jira/browse/GERONIMO-4442
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0.2, 2.1.3
Reporter: Kevan Miller
Assignee: Kevan Miller
Priority: Critical
Fix For: 2.1.4, 2.2
Attachments: G4222_ORBConfigAdapter.patch
I tried to configure the listening IP address for our server sockets. I
configured all 'host' properties in config-substitution.properties to be
'127.0.0.1' and got the following results:
Listening on Ports:
1050 127.0.0.1 CORBA Naming Service
1099 127.0.0.1 RMI Naming
1527 127.0.0.1 Derby Connector
2001 127.0.0.1 OpenEJB ORB Adapter
4201 127.0.0.1 OpenEJB Daemon
6882 127.0.0.1 OpenEJB ORB Adapter
8009 127.0.0.1 Tomcat Connector AJP AJP
8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP
8443 127.0.0.1 Tomcat Connector
[jira] Commented: (GERONIMO-4442) Unable to configure IP address for many listening ports
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657570#action_12657570 ] Kevan Miller commented on GERONIMO-4442: On a hunch, I plugged my ethernet cable into my Mac. I was then able to start the server successfully. I disconnected my ethernet cable. Server startup again failed. Unable to configure IP address for many listening ports --- Key: GERONIMO-4442 URL: https://issues.apache.org/jira/browse/GERONIMO-4442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.1.3 Reporter: Kevan Miller Assignee: Kevan Miller Priority: Critical Fix For: 2.1.4, 2.2 Attachments: G4222_ORBConfigAdapter.patch I tried to configure the listening IP address for our server sockets. I configured all 'host' properties in config-substitution.properties to be '127.0.0.1' and got the following results: Listening on Ports: 1050 127.0.0.1 CORBA Naming Service 1099 127.0.0.1 RMI Naming 1527 127.0.0.1 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 127.0.0.1 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 127.0.0.1 Tomcat Connector AJP AJP 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS 127.0.0.1 JMX Remoting Connector 61613 127.0.0.1 ActiveMQ Transport Connector 61616 127.0.0.1 ActiveMQ Transport Connector Unfortunately, that's not accurate. netstat reveals the following actual results: $ netstat -an | grep LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63519*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 127.0.0.1.4201 *.*LISTEN tcp4 0 0 127.0.0.1.61613*.*LISTEN tcp4 0 0 127.0.0.1.61616*.*LISTEN tcp4 0 0 127.0.0.1.1527 *.*LISTEN tcp4 0 0 127.0.0.1.8443 *.*LISTEN tcp4 0 0 127.0.0.1.8009 *.*LISTEN tcp4 0 0 127.0.0.1.8080 *.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN Configuring the host properties to be an actual ip address/hostname is a bit worse (not sure what's going on with ActiveMQ): Listening on Ports: 1050 10.0.1.196 CORBA Naming Service 1099 10.0.1.196 RMI Naming 1527 10.0.1.196 Derby Connector 2001 10.0.1.196 OpenEJB ORB Adapter 4201 10.0.1.196 OpenEJB Daemon 6882 10.0.1.196 OpenEJB ORB Adapter 8009 10.0.1.196 Tomcat Connector AJP AJP 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS 10.0.1.196 JMX Remoting Connector 61613 0.0.0.0ActiveMQ Transport Connector 61616 0.0.0.0ActiveMQ Transport Connector Netstat shows: $ netstat -an | grep LISTEN tcp6 0 0 fe80::1%lo0.631*.*LISTEN tcp4 0 0 *.6882 *.*LISTEN tcp4 0 0 *.2001 *.*LISTEN tcp4 0 0 *.63569*.*LISTEN tcp4 0 0 *.1050 *.*LISTEN tcp4 0 0 10.0.1.196.4201*.*LISTEN tcp4 0 0 *.61613*.*LISTEN tcp4 0 0 *.61616*.*LISTEN tcp4 0 0 10.0.1.196.1527*.*LISTEN tcp4 0 0 10.0.1.196.8443*.*LISTEN tcp4 0 0 10.0.1.196.8009*.*LISTEN tcp4 0 0 10.0.1.196.8080*.*LISTEN tcp4 0 0 *. *.*LISTEN tcp4 0 0 *.1099 *.*LISTEN -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 727499
Geronimo Revision: 727499 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081217/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081217
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 32 seconds
[INFO] Finished at: Wed Dec 17 15:43:12 EST 2008
[INFO] Final Memory: 391M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081217/logs-1500-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:44.728
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 35 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:12.548)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:29.899)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:36.548)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.163)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:12.195)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:22.110)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:44.463)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.216)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:22.609)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:45.850)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.503)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.675)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.387)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:49.631)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:51.983)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.908)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.405)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:52.153)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security
[jira] Commented: (GERONIMO-4442) Unable to configure IP address for many listening ports
[
https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657646#action_12657646
]
Shawn Jiang commented on GERONIMO-4442:
---
It seems as the server can't be shutdown when the host is localhost/127.0.0.1
or the real IP. I got following error when trying to shutdown the server:
{code}
Username: system
Password: ***
Locating server on port 1099...
Could not communicate with the server. The server may not be running or the por
t number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.Servi
ceUnavailableException [Root exception is java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect])
{code}
guess it's caused by the limited RMI or JMX address.
Unable to configure IP address for many listening ports
---
Key: GERONIMO-4442
URL: https://issues.apache.org/jira/browse/GERONIMO-4442
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0.2, 2.1.3
Reporter: Kevan Miller
Assignee: Kevan Miller
Priority: Critical
Fix For: 2.1.4, 2.2
Attachments: G4222_ORBConfigAdapter.patch
I tried to configure the listening IP address for our server sockets. I
configured all 'host' properties in config-substitution.properties to be
'127.0.0.1' and got the following results:
Listening on Ports:
1050 127.0.0.1 CORBA Naming Service
1099 127.0.0.1 RMI Naming
1527 127.0.0.1 Derby Connector
2001 127.0.0.1 OpenEJB ORB Adapter
4201 127.0.0.1 OpenEJB Daemon
6882 127.0.0.1 OpenEJB ORB Adapter
8009 127.0.0.1 Tomcat Connector AJP AJP
8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP
8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS
127.0.0.1 JMX Remoting Connector
61613 127.0.0.1 ActiveMQ Transport Connector
61616 127.0.0.1 ActiveMQ Transport Connector
Unfortunately, that's not accurate. netstat reveals the following actual
results:
$ netstat -an | grep LISTEN
tcp4 0 0 *.6882 *.*LISTEN
tcp4 0 0 *.2001 *.*LISTEN
tcp4 0 0 *.63519*.*LISTEN
tcp4 0 0 *.1050 *.*LISTEN
tcp4 0 0 127.0.0.1.4201 *.*LISTEN
tcp4 0 0 127.0.0.1.61613*.*LISTEN
tcp4 0 0 127.0.0.1.61616*.*LISTEN
tcp4 0 0 127.0.0.1.1527 *.*LISTEN
tcp4 0 0 127.0.0.1.8443 *.*LISTEN
tcp4 0 0 127.0.0.1.8009 *.*LISTEN
tcp4 0 0 127.0.0.1.8080 *.*LISTEN
tcp4 0 0 *. *.*LISTEN
tcp4 0 0 *.1099 *.*LISTEN
Configuring the host properties to be an actual ip address/hostname is a bit
worse (not sure what's going on with ActiveMQ):
Listening on Ports:
1050 10.0.1.196 CORBA Naming Service
1099 10.0.1.196 RMI Naming
1527 10.0.1.196 Derby Connector
2001 10.0.1.196 OpenEJB ORB Adapter
4201 10.0.1.196 OpenEJB Daemon
6882 10.0.1.196 OpenEJB ORB Adapter
8009 10.0.1.196 Tomcat Connector AJP AJP
8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP
8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS
10.0.1.196 JMX Remoting Connector
61613 0.0.0.0ActiveMQ Transport Connector
61616 0.0.0.0ActiveMQ Transport Connector
Netstat shows:
$ netstat -an | grep LISTEN
tcp6 0 0 fe80::1%lo0.631*.*LISTEN
tcp4 0 0 *.6882 *.*LISTEN
tcp4 0 0 *.2001 *.*LISTEN
tcp4 0 0 *.63569*.*LISTEN
tcp4 0 0 *.1050 *.*LISTEN
tcp4 0 0 10.0.1.196.4201*.*LISTEN
tcp4 0 0 *.61613*.*LISTEN
tcp4 0 0 *.61616*.*LISTEN
tcp4 0 0 10.0.1.196.1527*.*LISTEN
tcp4 0 0 10.0.1.196.8443*.*LISTEN
tcp4 0 0 10.0.1.196.8009*.*LISTEN
tcp4 0 0 10.0.1.196.8080*.*LISTEN
tcp4 0 0 *. *.*LISTEN
tcp4 0 0
[jira] Issue Comment Edited: (GERONIMO-4442) Unable to configure IP address for many listening ports
[
https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657646#action_12657646
]
genspring edited comment on GERONIMO-4442 at 12/17/08 5:54 PM:
-
It seems as the server can't be shutdown when the host is localhost/127.0.0.1.
If the ip is set to the real IP x.x.x.x. use
{code}
Y:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin\shutdown.bat --host x.x.x.x
{code}
the server shutdown without problem. But if you set the ip to 127.0.0.1 then
try to shutdown it.
{code}
Y:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin\shutdown.bat --host 127.0.0.1
{code}
will get error:
{code}
Username: system
Password: ***
Locating server on port 1099...
Could not communicate with the server. The server may not be running or the por
t number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.Servi
ceUnavailableException [Root exception is java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect])
{code}
I guess it's caused by the limited RMI or JMX address.
was (Author: genspring):
It seems as the server can't be shutdown when the host is
localhost/127.0.0.1 or the real IP. I got following error when trying to
shutdown the server:
{code}
Username: system
Password: ***
Locating server on port 1099...
Could not communicate with the server. The server may not be running or the por
t number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.Servi
ceUnavailableException [Root exception is java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect])
{code}
guess it's caused by the limited RMI or JMX address.
Unable to configure IP address for many listening ports
---
Key: GERONIMO-4442
URL: https://issues.apache.org/jira/browse/GERONIMO-4442
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0.2, 2.1.3
Reporter: Kevan Miller
Assignee: Kevan Miller
Priority: Critical
Fix For: 2.1.4, 2.2
Attachments: G4222_ORBConfigAdapter.patch
I tried to configure the listening IP address for our server sockets. I
configured all 'host' properties in config-substitution.properties to be
'127.0.0.1' and got the following results:
Listening on Ports:
1050 127.0.0.1 CORBA Naming Service
1099 127.0.0.1 RMI Naming
1527 127.0.0.1 Derby Connector
2001 127.0.0.1 OpenEJB ORB Adapter
4201 127.0.0.1 OpenEJB Daemon
6882 127.0.0.1 OpenEJB ORB Adapter
8009 127.0.0.1 Tomcat Connector AJP AJP
8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP
8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS
127.0.0.1 JMX Remoting Connector
61613 127.0.0.1 ActiveMQ Transport Connector
61616 127.0.0.1 ActiveMQ Transport Connector
Unfortunately, that's not accurate. netstat reveals the following actual
results:
$ netstat -an | grep LISTEN
tcp4 0 0 *.6882 *.*LISTEN
tcp4 0 0 *.2001 *.*LISTEN
tcp4 0 0 *.63519*.*LISTEN
tcp4 0 0 *.1050 *.*LISTEN
tcp4 0 0 127.0.0.1.4201 *.*LISTEN
tcp4 0 0 127.0.0.1.61613*.*LISTEN
tcp4 0 0 127.0.0.1.61616*.*LISTEN
tcp4 0 0 127.0.0.1.1527 *.*LISTEN
tcp4 0 0 127.0.0.1.8443 *.*LISTEN
tcp4 0 0 127.0.0.1.8009 *.*LISTEN
tcp4 0 0 127.0.0.1.8080 *.*LISTEN
tcp4 0 0 *. *.*LISTEN
tcp4 0 0 *.1099 *.*LISTEN
Configuring the host properties to be an actual ip address/hostname is a bit
worse (not sure what's going on with ActiveMQ):
Listening on Ports:
1050 10.0.1.196 CORBA Naming Service
1099 10.0.1.196 RMI Naming
1527 10.0.1.196 Derby Connector
2001 10.0.1.196 OpenEJB ORB Adapter
4201 10.0.1.196 OpenEJB Daemon
6882 10.0.1.196 OpenEJB ORB Adapter
8009 10.0.1.196 Tomcat Connector AJP AJP
8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP
8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS
10.0.1.196 JMX Remoting Connector
61613 0.0.0.0ActiveMQ Transport Connector
61616 0.0.0.0ActiveMQ Transport Connector
Netstat shows:
$ netstat -an |
[jira] Created: (GERONIMO-4473) Validate the artifact fields when adding an archive to the repository
Validate the artifact fields when adding an archive to the repository - Key: GERONIMO-4473 URL: https://issues.apache.org/jira/browse/GERONIMO-4473 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.2 Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to excluding ( ) , ; : \ / ' and .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4473) Validate the artifact fields when adding an archive to the repository
[ https://issues.apache.org/jira/browse/GERONIMO-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4473: --- Description: Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to exclude ( ) , ; : \ / ' and .. (was: Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to excluding ( ) , ; : \ / ' and ..) Validate the artifact fields when adding an archive to the repository - Key: GERONIMO-4473 URL: https://issues.apache.org/jira/browse/GERONIMO-4473 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.2 Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to exclude ( ) , ; : \ / ' and .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
trunk testsuite failures
It looks like we have I'm hitting failures attempting to run the testsuite on my mac in the following tests. Are others seeing the same thing? - webservices-testsuite/jaxws-provider-tests - webservices-testsuite/jaxws-tests - webservices-testsuite/jaxws-wsa-tests - webservices-testsuite/saaj-tests - webservices-testsuite/stax-tests Joe
Re: trunk testsuite failures
On Tomcat or Jetty? Any specific errors? Jarek On Wed, Dec 17, 2008 at 10:52 PM, Joe Bohn joe.b...@earthlink.net wrote: It looks like we have I'm hitting failures attempting to run the testsuite on my mac in the following tests. Are others seeing the same thing? - webservices-testsuite/jaxws-provider-tests - webservices-testsuite/jaxws-tests - webservices-testsuite/jaxws-wsa-tests - webservices-testsuite/saaj-tests - webservices-testsuite/stax-tests Joe
[BUILD] trunk: Failed for Revision: 727618
Geronimo Revision: 727618 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081217/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081217
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 34 seconds
[INFO] Finished at: Wed Dec 17 21:41:51 EST 2008
[INFO] Final Memory: 630M/986M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081217/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:43.206
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 35 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.355)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.262)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.871)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.310)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:26.316)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:18.358)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:41.994)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.253)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:41.714)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:45.377)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.921)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.292)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.466)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.131)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.326)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:48.742)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:25.690)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:51.639)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security
Re: trunk testsuite failures
I've been building with just mvn (and no other parms) ... so it defaults
to jetty I believe and runs the tests.
I think it's just timing out. Here's a portion of the build.log from
jaxws-provider-tests. It's consistent - failing every time.
OUT: [INFO] Starting module:
org.apache.geronimo.testsuite/provider-ear/2.2-SNAPSHOT/ear
OUT: Dec 17, 2008 10:26:08 PM ClientCommunicatorAdmin Checker-run
OUT: WARNING: Failed to check the connection:
java.net.SocketTimeoutException: Read timed out
OUT: Deployer operation failed: Error unmarshaling return header; nested
exception is:
OUT:java.net.SocketTimeoutException: Read timed out
OUT: java.rmi.UnmarshalException: Error unmarshaling return header;
nested exception is:
OUT:java.net.SocketTimeoutException: Read timed out
OUT: at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203)
OUT:at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
OUT:at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
OUT: at
javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source)
OUT: at
javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:972)
OUT: at
org.apache.geronimo.system.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:886)
OUT: at
org.apache.geronimo.system.jmx.KernelDelegate.invoke(KernelDelegate.java:547)
OUT: at
org.apache.geronimo.kernel.basic.KernelOperationInvoker.invoke(KernelOperationInvoker.java:46)
OUT: at
org.apache.geronimo.system.jmx.JMXProxyMethodInterceptor.intercept(JMXProxyMethodInterceptor.java:89)
OUT: at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$fb863628.startConfiguration(generated)
OUT: at
org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67)
OUT:at java.lang.Thread.run(Thread.java:613)
OUT: Caused by: java.net.SocketTimeoutException: Read timed out
OUT:at java.net.SocketInputStream.socketRead0(Native Method)
OUT:at java.net.SocketInputStream.read(SocketInputStream.java:129)
OUT:at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
OUT:at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
OUT:at java.io.DataInputStream.readByte(DataInputStream.java:241)
OUT: at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:189)
OUT:... 11 more
OUT: [WARNING] Ignoring failure !
OUT: [INFO] [surefire:test {execution: integration}]
OUT: [INFO] Surefire report directory:
/Users/bohn/geronimo/testsuite/webservices-testsuite/jaxws-provider-tests/provider-ear/target/surefire-reports
OUT: ---
OUT: T E S T S
OUT: ---
OUT: Running TestSuite
OUT: Tests run: 18, Failures: 18, Errors: 0, Skipped: 0, Time elapsed:
447.755 sec FAILURE!
OUT: Results :
OUT: Failed tests:
OUT:
testHTTPDataSource(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testHTTPSourceMessageMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testHTTPSourcePayloadMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP11SOAPMessage(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP11SourceMessageMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP11SourcePayloadMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP12SOAPMessage(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP12SourceMessageMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP12SourcePayloadMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testHTTPDataSource(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testHTTPSourceMessageMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testHTTPSourcePayloadMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP11SOAPMessage(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP11SourceMessageMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP11SourcePayloadMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP12SOAPMessage(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP12SourceMessageMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP12SourcePayloadMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT: Tests run: 18, Failures: 18, Errors: 0, Skipped: 0
OUT: [INFO]
OUT: [ERROR] BUILD FAILURE
OUT: [INFO]
OUT: [INFO] There are test failures.
OUT: Please refer to
/Users/bohn/geronimo/testsuite/webservices-testsuite/jaxws-provider-tests/provider-ear/target/surefire-reports
for the individual test results.
OUT: [INFO]
OUT: [INFO] Trace
OUT:
[jira] Resolved: (GERONIMO-1367) Shutdown JAR should use deployer stored username/password
[ https://issues.apache.org/jira/browse/GERONIMO-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-1367. --- Resolution: Fixed Assignee: Jarek Gawor (was: Donald Woods) Committed changes to trunk (revision 727643) and branches/2.1 (revision 72764). For branches/2.1 this change might cause some problems reading existing saved credentials as the SavedAuthentication class was moved to another location (i.e. might cause some deserialization errors) Shutdown JAR should use deployer stored username/password - Key: GERONIMO-1367 URL: https://issues.apache.org/jira/browse/GERONIMO-1367 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: startup/shutdown, usability Affects Versions: 1.0 Reporter: Aaron Mulder Assignee: Jarek Gawor Priority: Minor Fix For: 2.1.4, 2.2 Attachments: GERONIMO-1367.patch It would be nice if the shutdown script used the username and password saved by the deployer so you didn't need to specify them or re-enter them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4474) Pull out the text in the JSP files to resource bundle files
Pull out the text in the JSP files to resource bundle files --- Key: GERONIMO-4474 URL: https://issues.apache.org/jira/browse/GERONIMO-4474 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Priority: Minor Currently in the admin console, some text are hard coded in the JSP files. We need to pull them out to the resource bundle files, so that we could deliver multi-language versions in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: trunk testsuite failures
Hmm.. any errors on the server side in the logs?
Jarek
On Wed, Dec 17, 2008 at 11:25 PM, Joe Bohn joe.b...@earthlink.net wrote:
I've been building with just mvn (and no other parms) ... so it defaults to
jetty I believe and runs the tests.
I think it's just timing out. Here's a portion of the build.log from
jaxws-provider-tests. It's consistent - failing every time.
OUT: [INFO] Starting module:
org.apache.geronimo.testsuite/provider-ear/2.2-SNAPSHOT/ear
OUT: Dec 17, 2008 10:26:08 PM ClientCommunicatorAdmin Checker-run
OUT: WARNING: Failed to check the connection:
java.net.SocketTimeoutException: Read timed out
OUT: Deployer operation failed: Error unmarshaling return header; nested
exception is:
OUT:java.net.SocketTimeoutException: Read timed out
OUT: java.rmi.UnmarshalException: Error unmarshaling return header; nested
exception is:
OUT:java.net.SocketTimeoutException: Read timed out
OUT:at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203)
OUT:at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
OUT:at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
OUT:at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown
Source)
OUT:at
javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:972)
OUT:at
org.apache.geronimo.system.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:886)
OUT:at
org.apache.geronimo.system.jmx.KernelDelegate.invoke(KernelDelegate.java:547)
OUT:at
org.apache.geronimo.kernel.basic.KernelOperationInvoker.invoke(KernelOperationInvoker.java:46)
OUT:at
org.apache.geronimo.system.jmx.JMXProxyMethodInterceptor.intercept(JMXProxyMethodInterceptor.java:89)
OUT:at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$fb863628.startConfiguration(generated)
OUT:at
org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67)
OUT:at java.lang.Thread.run(Thread.java:613)
OUT: Caused by: java.net.SocketTimeoutException: Read timed out
OUT:at java.net.SocketInputStream.socketRead0(Native Method)
OUT:at java.net.SocketInputStream.read(SocketInputStream.java:129)
OUT:at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
OUT:at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
OUT:at java.io.DataInputStream.readByte(DataInputStream.java:241)
OUT:at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:189)
OUT:... 11 more
OUT: [WARNING] Ignoring failure !
OUT: [INFO] [surefire:test {execution: integration}]
OUT: [INFO] Surefire report directory:
/Users/bohn/geronimo/testsuite/webservices-testsuite/jaxws-provider-tests/provider-ear/target/surefire-reports
OUT: ---
OUT: T E S T S
OUT: ---
OUT: Running TestSuite
OUT: Tests run: 18, Failures: 18, Errors: 0, Skipped: 0, Time elapsed:
447.755 sec FAILURE!
OUT: Results :
OUT: Failed tests:
OUT: testHTTPDataSource(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testHTTPSourceMessageMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testHTTPSourcePayloadMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP11SOAPMessage(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP11SourceMessageMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP11SourcePayloadMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP12SOAPMessage(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP12SourceMessageMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT:
testSOAP12SourcePayloadMode(org.apache.geronimo.jaxws.provider.EJBProviderTest)
OUT: testHTTPDataSource(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testHTTPSourceMessageMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testHTTPSourcePayloadMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP11SOAPMessage(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP11SourceMessageMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP11SourcePayloadMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP12SOAPMessage(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP12SourceMessageMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT:
testSOAP12SourcePayloadMode(org.apache.geronimo.jaxws.provider.WebProviderTest)
OUT: Tests run: 18, Failures: 18, Errors: 0, Skipped: 0
OUT: [INFO]
OUT: [ERROR] BUILD FAILURE
OUT: [INFO]
OUT: [INFO] There are test failures.
OUT: Please refer to
Re: git, hg or bzr for G development?
I've been doing some experimenting using svn.eu.apache.org with git, so far it has gone well. I've been reading infra mail some folks do run into problems from time to time. So I'm limiting my changes to only small things, no large refactorings yet, but it is looking very hopeful. That and there has been some discussion on the infra list about an ASF git repo, hopefully that will be per TLP, but who knows. --jason On Dec 6, 2008, at 1:22 AM, Kevan Miller wrote: On Dec 4, 2008, at 9:13 AM, Jason Dillon wrote: Has anyone figured out a way to use git, hg, or bzr for G (or other ASF) development? Some projects are creating git mirrors of svn. There's been some chatter on infrastructure@ I haven't really looked at it. I don't recall any hg or bzr discussions. IIUC, you have to use the eu svn server. Also saw the following http://markmail.org/message/fzzy7nepk7olx5fl#query :+page:1+mid:zrujbjp7dqj5di4z+state:results --kevan
Re: svn commit: r727321 - in /geronimo/gshell/trunk: gshell-api/src/main/java/org/apache/geronimo/gshell/command/ gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/comma
Thx :-)
--jason
On Dec 17, 2008, at 4:31 PM, gno...@apache.org wrote:
Author: gnodet
Date: Wed Dec 17 01:31:44 2008
New Revision: 727321
URL: http://svn.apache.org/viewvc?rev=727321view=rev
Log:
GSHELL-154: Create interfaces to represent links and aliases
Added:
geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Alias.java
geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Link.java
geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
java/org/apache/geronimo/gshell/wisdom/command/AliasImpl.java
geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
java/org/apache/geronimo/gshell/wisdom/command/LinkImpl.java
Modified:
geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
java/org/apache/geronimo/gshell/wisdom/config/PluginParser.java
geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
java/org/apache/geronimo/gshell/wisdom/plugin/bundle/
CommandBundle.java
Added: geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Alias.java
URL:
http://svn.apache.org/viewvc/geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/geronimo/gshell/command/Alias.java?rev=727321view=auto
=
=
=
=
=
=
=
=
==
--- geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Alias.java (added)
+++ geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Alias.java Wed Dec 17 01:31:44 2008
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+package org.apache.geronimo.gshell.command;
+
+/**
+ * Convenient way to register an alias.
+ *
+ * @version $Rev: 705507 $ $Date: 2008-10-17 10:22:12 +0200 (Fri,
17 Oct 2008) $
+ */
+public interface Alias {
+
+String getName();
+
+String getAlias();
+
+}
Added: geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Link.java
URL:
http://svn.apache.org/viewvc/geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/geronimo/gshell/command/Link.java?rev=727321view=auto
=
=
=
=
=
=
=
=
==
--- geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Link.java (added)
+++ geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
geronimo/gshell/command/Link.java Wed Dec 17 01:31:44 2008
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+package org.apache.geronimo.gshell.command;
+
+/**
+ * Provides a convenient way to register a link
+ *
+ * @version $Rev: 705507 $ $Date: 2008-10-17 10:22:12 +0200 (Fri,
17 Oct 2008) $
+ */
+public interface Link {
+
+String getName();
+
+String getTarget();
+
+}
Added: geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/
main/java/org/apache/geronimo/gshell/wisdom/command/AliasImpl.java
URL:
http://svn.apache.org/viewvc/geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/command/AliasImpl.java?rev=727321view=auto
=
=
=
=
=
=
=
=
==
--- geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
java/org/apache/geronimo/gshell/wisdom/command/AliasImpl.java (added)
+++
[jira] Created: (GERONIMO-4475) Improve JMS portlet for Borker configuration
Improve JMS portlet for Borker configuration Key: GERONIMO-4475 URL: https://issues.apache.org/jira/browse/GERONIMO-4475 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Fix For: Wish List Currently in the administrator console, the users could not add another embed broker. Also, they could not edit the broker through administrator console. I list the features that I could see : 1. While creating the broker, let the use upload a configuration file. 2. While editing the broker, show a text area, so that the user could edit the spring XML file in it. Shall we give the user a more friendly interface, so that they do not need the edit the XML file directly. I am not sure how it should look like. 3. Update the connector port let, so that while creating a new connector, the user could specify the broker that it belongs to. Please help to give some comments ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
