[jira] Created: (GSHELL-157) Dynamically adding / removing commands does not work well
Dynamically adding / removing commands does not work well - Key: GSHELL-157 URL: https://issues.apache.org/jira/browse/GSHELL-157 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 When resolving commands, the command resolver uses a virtual file system. Unfortunately, the data for virtual file systems is always cached, which means that removing a command will still make it available for resolution. The cache problem is caused by the DelegateFileObject which does not refresh the underlying file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.0: Failed for Revision: 741019
Geronimo Revision: 741019 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090205/build-0200.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.0/20090205 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 34 minutes 24 seconds [INFO] Finished at: Thu Feb 05 02:38:22 EST 2009 [INFO] Final Memory: 219M/862M [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/2.0/20090205/logs-0200-tomcat/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.278 sec FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.321 sec FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.638 sec FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.284 sec FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090205/logs-0200-jetty/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.32 sec FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.338 sec FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.681 sec FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.31 sec FAILURE!
[jira] Resolved: (GSHELL-157) Dynamically adding / removing commands does not work well
[ https://issues.apache.org/jira/browse/GSHELL-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved GSHELL-157. Resolution: Fixed Sending gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/registry/CommandResolverImpl.java Sending gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/registry/GroupDirectoryResolver.java Transmitting file data .. Committed revision 741042. Dynamically adding / removing commands does not work well - Key: GSHELL-157 URL: https://issues.apache.org/jira/browse/GSHELL-157 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 When resolving commands, the command resolver uses a virtual file system. Unfortunately, the data for virtual file systems is always cached, which means that removing a command will still make it available for resolution. The cache problem is caused by the DelegateFileObject which does not refresh the underlying file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4517) Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages.
[ https://issues.apache.org/jira/browse/GERONIMO-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gang Yin updated GERONIMO-4517: --- Attachment: js-localization-plugin.patch patch for plugin Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages. --- Key: GERONIMO-4517 URL: https://issues.apache.org/jira/browse/GERONIMO-4517 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Gang Yin Assignee: Gang Yin Priority: Minor Fix For: 2.2 Attachments: js-localization-activemq.patch, js-localization-console.patch, js-localization-core.patch, js-localization-openejb.patch, js-localization-plugin.patch, js-localization-sysdb.patch, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg Currently all the messages generated from backend is displayed in a unified manner(G-4484), but frontend javascript use alert boxes to display all kinds of messages without distinguishing their types(e.g. error, warn, info), and the UX of alert boxes is not so good, so I'm going to extend the unified message display style of backend messages to frontend messages. Also, the localization work will be done meantime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4517) Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages.
[ https://issues.apache.org/jira/browse/GERONIMO-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670679#action_12670679 ] Gang Yin commented on GERONIMO-4517: Hi, Donald, All needed patches are submitted, please help tp review and commit them, thanks. BYW, The first patch has alredy been committed by you. Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages. --- Key: GERONIMO-4517 URL: https://issues.apache.org/jira/browse/GERONIMO-4517 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Gang Yin Assignee: Gang Yin Priority: Minor Fix For: 2.2 Attachments: js-localization-activemq.patch, js-localization-console.patch, js-localization-core.patch, js-localization-openejb.patch, js-localization-plugin.patch, js-localization-sysdb.patch, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg Currently all the messages generated from backend is displayed in a unified manner(G-4484), but frontend javascript use alert boxes to display all kinds of messages without distinguishing their types(e.g. error, warn, info), and the UX of alert boxes is not so good, so I'm going to extend the unified message display style of backend messages to frontend messages. Also, the localization work will be done meantime. -- 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: 741025
Geronimo Revision: 741025 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 11 seconds
[INFO] Finished at: Thu Feb 05 03:45:32 EST 2009
[INFO] Final Memory: 429M/972M
[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/20090205/logs-0300-tomcat/test.log
[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:45.867
[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 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:14.249)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.693)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:35.638)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:17.017)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:20.136)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:22.711)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.727)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:45.047)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:44.327)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:57.347)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:31.094)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.880)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:31.863)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:50.942)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:43.894) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:05.810)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.624)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.543)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:45.552)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.677)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
[jira] Assigned: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manu T George reassigned GERONIMO-4369: --- Assignee: Manu T George (was: Ivan) The new attribute values are overwrote while restarting the DB pool connector - Key: GERONIMO-4369 URL: https://issues.apache.org/jira/browse/GERONIMO-4369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: Geronimo 2.2 snapshot JDK 1.5 Windows XP Reporter: Ivan Assignee: Manu T George Priority: Blocker Fix For: 2.1.4, 2.2 Attachments: Geronimo-4369-01.21.patch, Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, Geronimo-4369-11.19.patch After editing the values in the db pool, then restart it in the console, the new values lost. When saving the new attribute values, such as user name, the gbeandata in the configurationManager is not updated, so while restarting the connector, the gbinstance copies those old values from it. So the new persistent values do not take effect, Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manu T George updated GERONIMO-4369: Attachment: G-4369-0205.patch This patch provides an alternative approach and applies the over ridden values to the configuration object before calling restart from the ConfigManagerPortlet. We lookup the ManageableAttributeStore and then call the applyOverrides method to achieve the same. There seems to be only one attribute store namely the !--User-editable attribute service-- gbean name=AttributeManager class=org.apache.geronimo.system.configuration.LocalAttributeManager reference name=ServerInfo nameServerInfo/name /reference attribute name=configFilevar/config/config.xml/attribute attribute name=substitutionsFilevar/config/config-substitutions.properties/attribute attribute name=substitutionPrefixorg.apache.geronimo.config.substitution./attribute /gbean If there are any objections or errors that you see with this patch please point them out on the jira The new attribute values are overwrote while restarting the DB pool connector - Key: GERONIMO-4369 URL: https://issues.apache.org/jira/browse/GERONIMO-4369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: Geronimo 2.2 snapshot JDK 1.5 Windows XP Reporter: Ivan Assignee: Manu T George Priority: Blocker Fix For: 2.1.4, 2.2 Attachments: G-4369-0205.patch, Geronimo-4369-01.21.patch, Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, Geronimo-4369-11.19.patch After editing the values in the db pool, then restart it in the console, the new values lost. When saving the new attribute values, such as user name, the gbeandata in the configurationManager is not updated, so while restarting the connector, the gbinstance copies those old values from it. So the new persistent values do not take effect, Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-158) The group.name has an incorrect value at the root when using '..' from a subshell
The group.name has an incorrect value at the root when using '..' from a subshell - Key: GSHELL-158 URL: https://issues.apache.org/jira/browse/GSHELL-158 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GSHELL-158) The group.name has an incorrect value at the root when using '..' from a subshell
[ https://issues.apache.org/jira/browse/GSHELL-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved GSHELL-158. Resolution: Fixed Sending gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/registry/CommandResolverImpl.java Transmitting file data . Committed revision 741078. The group.name has an incorrect value at the root when using '..' from a subshell - Key: GSHELL-158 URL: https://issues.apache.org/jira/browse/GSHELL-158 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[
https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670726#action_12670726
]
Manu T George commented on GERONIMO-4369:
-
With patch Geronimo-4369-01.21.patch i faced the following errors
1) On restart from console changes are lost
2) Admin console shows stop start and restart messages
3) Failure to start some modules
4) Significant increase in startup time
5) Stopping and Starting the server also results in all changes being lost
I also think that this is just not a restart problem. There are two separate
issues at work here that I am seeing
1) Changes made are lost during restart from admin console of the connector
This is because the changes made to the attributeStore are not
applied to the configurations on restart. Can be fixed by patch
G-4369-0205.patch
2) Some Changes made are lost on stopping and starting the server or the
connector
Not fixed by any of the patches
1) is fixed with the patch i have supplied. Also changes to some of the fields
like database name and createDatabase are getting reflected even on server
restart of config stop and start.
however 2 is still open and This leads me to believe that this problem is
localized to the db manager portlet. On seeing config.xml I see only a few
values are persisted
module name=console.dbpool/Testman/1.0/rar
gbean
name=console.dbpool/Testman/1.0/rar?J2EEApplication=null,JCAConnectionFactory=Testman,JCAResource=console.dbpool/Testman/1.0/rar,ResourceAdapter=console.dbpool/Testman/1.0/rar,ResourceAdapterModule=console.dbpool/Testman/1.0/rar,j2eeType=JCAManagedConnectionFactory,name=Testman
attribute name=DatabaseNameTESTMANT/attribute
attribute name=CreateDatabasefalse/attribute
attribute name=ShutdownDatabasesystem/attribute
attribute
name=Password{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEHnh03EmiNu4VTuWH+xZiRBwdAADQUVT/attribute
attribute name=LoginTimeout0/attribute
attribute name=UserName/
/gbean
/module
Changes to these values are reflected on stop and start as expected and to the
other fields that are not in config.xml are not reflected
If fix for 1 is acceptable then we can reduce the severity of this JIRA as it
won't affect other portlets with that fix
If not acceptable I think we should revert back to restartConfiguration in the
ConfigManagerPortlet as that seems better than what we have now.
Note:
The geronimo build I am testing on is a few weeks old. I will test with a new
build as soon as I can
I tested the above for an embedded derby datasource . I am not sure whether the
same will occur for other datasources
The new attribute values are overwrote while restarting the DB pool connector
-
Key: GERONIMO-4369
URL: https://issues.apache.org/jira/browse/GERONIMO-4369
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.2
Environment: Geronimo 2.2 snapshot
JDK 1.5
Windows XP
Reporter: Ivan
Assignee: Manu T George
Priority: Blocker
Fix For: 2.1.4, 2.2
Attachments: G-4369-0205.patch, Geronimo-4369-01.21.patch,
Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch,
Geronimo-4369-11.19.patch
After editing the values in the db pool, then restart it in the console, the
new values lost.
When saving the new attribute values, such as user name, the gbeandata in
the configurationManager is not updated, so while restarting the connector,
the gbinstance copies those old values from it. So the new persistent values
do not take effect,
Do I miss anything, thanks for any comment !
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3759:
---
Fix Version/s: (was: 2.1.3)
2.1.4
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Jason Warner
Fix For: 2.1.3, 2.2
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml, tomcat_server.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3759:
---
Fix Version/s: (was: 2.1.4)
2.1.3
undo latest changes to fix version
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Jason Warner
Fix For: 2.1.3, 2.2
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml, tomcat_server.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4517) Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages.
[ https://issues.apache.org/jira/browse/GERONIMO-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4517: --- Patch Info: [Patch Available] Assignee: (was: Gang Yin) Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages. --- Key: GERONIMO-4517 URL: https://issues.apache.org/jira/browse/GERONIMO-4517 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Gang Yin Priority: Minor Fix For: 2.2 Attachments: js-localization-activemq.patch, js-localization-console.patch, js-localization-core.patch, js-localization-openejb.patch, js-localization-plugin.patch, js-localization-sysdb.patch, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg Currently all the messages generated from backend is displayed in a unified manner(G-4484), but frontend javascript use alert boxes to display all kinds of messages without distinguishing their types(e.g. error, warn, info), and the UX of alert boxes is not so good, so I'm going to extend the unified message display style of backend messages to frontend messages. Also, the localization work will be done meantime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670756#action_12670756 ] Donald Woods commented on GERONIMO-4369: go ahead and apply to 2.1.4 and 2.2 and #2 can be addressed in 2.1.5 and 2.2 if time permits The new attribute values are overwrote while restarting the DB pool connector - Key: GERONIMO-4369 URL: https://issues.apache.org/jira/browse/GERONIMO-4369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: Geronimo 2.2 snapshot JDK 1.5 Windows XP Reporter: Ivan Assignee: Manu T George Priority: Blocker Fix For: 2.1.4, 2.2 Attachments: G-4369-0205.patch, Geronimo-4369-01.21.patch, Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, Geronimo-4369-11.19.patch After editing the values in the db pool, then restart it in the console, the new values lost. When saving the new attribute values, such as user name, the gbeandata in the configurationManager is not updated, so while restarting the connector, the gbinstance copies those old values from it. So the new persistent values do not take effect, Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] geronimo-jpa_2.0_spec first early access release
Any replies from Sun on this? -Donald Donald Woods wrote: Geir, any updates on getting item (iii) below removed, so we can release the early spec implementation and a OpenJPA 2.0.0 M1 release? -Donald David Jencks wrote: On Jan 30, 2009, at 2:00 PM, Donald Woods wrote: Any updates on item (iii)? Can we just include the notice for EA-1 and revisit for the next release? My interpretation of Geir's response is that we can't distribute stuff with this restriction, so no, we have to wait until the conditions are changed at which point the existing jar under vote will be OK. thanks david jencks -Donald David Jencks wrote: Looks like a problem. I sent a note to legal-discuss about (iii). I'll work on setting up a new release candidate. thanks david jencks On Jan 29, 2009, at 7:46 AM, Jeremy Bauer wrote: David, While searching the JSR-317 draft for direction regarding early access naming, I found that the notice (page 2) includes the clauses below, notably item iii. Does clause iii need to be added to the NOTICE in the EA jar? Also, should the Geronimo EA NOTICE use JPA 2.0 EARLY ACCESS instead of simply JPA 2.0 in order to meet clause ii? jsr-317 draft NOTICE ... 2.Distribute implementations of the Specification to third parties for their testing and evaluation use, provided that any such implementation: (i) does not modify, subset, superset or otherwise extend the Licensor Name Space, or include any public or protected packages, classes, Java interfaces, fields or methods within the Licensor Name Space other than those required/authorized by the Specification or Specifications being implemented; (ii)is clearly and prominently marked with the word UNTESTED or EARLY ACCESS or INCOMPATIBLE or UNSTABLE or BETA in any list of available builds and in proximity to every link initiating its download, where the list or link is under Licensee's control; and (iii)includes the following notice: This is an implementation of an early-draft specification developed under the Java Community Process (JCP) and is made available for testing and evaluation purposes only. The code is not compatible with any specification of the JCP. /jsr-317 draft -Jeremy On Wed, Jan 28, 2009 at 4:25 PM, David Jencks david_jen...@yahoo.com mailto:david_jen...@yahoo.com wrote: I've been working with the OpenJPA project to develop the jpa 2.0 spec jar in our spec repository. They are ready for their first early access milestone release. I've staged the release here: http://people.apache.org/~djencks/staging-repo/specs/geronimo-jpa_2.0_spec/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0-EA-1/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0-EA-1 I haven't staged the site. I don't think its necessary for a early access release, but will reconsider on request. I ran rat on the project, and the autochecking thinks the legal files are ok. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks david jencks
[BUILD] trunk: Failed for Revision: 741096
Geronimo Revision: 741096 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 7 seconds
[INFO] Finished at: Thu Feb 05 09:44:06 EST 2009
[INFO] Final Memory: 393M/1001M
[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/20090205/logs-0900-tomcat/test.log
[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:45.572
[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 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:04:23.501)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.631)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:34.440)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:17.172)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:21.958)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.269)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:45.925)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:46.716)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:47.568)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:39.101)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.032)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.683)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:29.510)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.470)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:39.769) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:04.046)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:28.698)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.344)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:42.162)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.394)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
Re: Time for Geronimo 2.1.4 release?
Jay, Updating OpenEJB 3.0.1 to xbean 3.5 will require 2.0.3 and 2.1.4 to update the asm 3.1 library (and that will need even more changes). I know some other libs have deps on the asm lib so we might run into problems later on. How about we only upgrade xbean-naming to 3.5 first and leave other xbean dependencies on 3.4.1? If that doesn't work we can try 3.5 for everything. Jarek On Wed, Feb 4, 2009 at 9:55 AM, Jay D. McHugh jaydmch...@gmail.com wrote: All of the 2.0.3 build issues are fixed. I will try building 2.0.3 with XBeans 3.5 now and let you all know what happens. If it will build, then I might take a look to see whether I can figure out what changes are necessary for OpenEJB 3.0.1 to use XBeans 3.5 too. Jay Jay D. McHugh wrote: The problem is with the version of ASM that is brought in when using a higher version of XBeans. OpenEJB is using a method that has been removed: org.objectweb.asm.ClassReader.accept And Geronimo (already - not counting XBeans 3.5) is using classes that have been removed: LinkResolver UniqueDefaultLinkResolver Jay Joe Bohn wrote: Thanks for the info Jay and for doing some more digging. I don't really have a strong desire to push everything to xBean 3.5. I was just trying to eliminate the use of multiple xBean versions as this could potentially cause problems (and confusion) for our users. It looks like we originally moved up to xBean 3.5 (actually 3.5-SNAPSHOT) to resolve a jca context issue (Geronimo-4375). However, it looks like it was soon discovered that there were issues with the OpenEJB, ASM and xBean versions in G. As a result ... we ended up reverting back to an older ASM and xBean 3.3 for finder and reflect while keeping the newer xbean-naming 3.5 so that the original issue was still resolved. That seems to be working and is perhaps the best approach. I was just concerned about using the various xBean versions in our Geronimo 2.1.4 server. Perhaps using the various xBean versions is still the best thing to do here. I didn't realize that there were core issues in OpenEJB attempting to use anything greater than 3.4.1. Thanks, Joe Jay D. McHugh wrote: Hey everyone, If we want to get OpenEJB 3.0.1 to move up to XBeans 3.5, then I think that we'll need to chip in to resolve the problems that pop up when you use a version greater than 3.4.1. That was the highest version (available at the time) that could be used in the OpenEJB 3.0 branch without causing errors. I'll try switching to XBeans 3.5 (after the build I am in the middle of finishes) and let you all know if it goes through cleanly. My feeling is that it won't though. Also, I have been trying to get a 'final' Geronimo 2.0.x release put together and will need OpenEJB 3.0.1 for that (3.0 no longer builds because the artifacts for XBeans changed groupIds). Jay Joe Bohn wrote: I was relaying the information second-hand ... so it's very possible I got it wrong. It looks like there is a dependency xBean in OpenEJB ... but it's 3.4.1 rather than 3.3 (as we have in the branches/2.1). So, perhaps if we can convince OpenEJB 3.0.x to xBean 3.5 we can then make the references consistent in our 2.1 branch. Thanks, Joe Donald Woods wrote: I don't see any dependencies on Xbean in OpenJPA 1.0.x or 1.2.x. Maybe you're thinking about OpenEJB? -Donald Joe Bohn wrote: I agree we should get a 2.1.4 release out ... and you certainly have my vote for release manager! The only thing I would add to the list is to get our xBean references to a consistent versions. I noticed this as I was updating branches/2.1 and trunk to pull in the newly released xBean 3.5. In branches/2.1 we have a mix of 3.3 dependencies (finder and reflect) and 3.5 dependencies (naming). I've been told that this was due to OpenJPA dependencies on 3.3. Now that we are pulling in a new OpenJPA release we will hopefully be able to update everything to use xBean 3.5. Joe Jarek Gawor wrote: Hi, I think it's time for Geronimo 2.1.4 release. We've had a lot of important fixes since 2.1.3 and we should get them out to our users. And if we agree, I would also like to volunteer to be a release manager for this release. Looking at the current status for 2.1.4 there are still a few things that we need to do before we can go ahead with the release. I updated the http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.4+Release+Status page with some of these items. If there are any open bugs that _need_ to be fixed for 2.1.4 or if I missed anything in that list please just update that wiki page. Thanks, Jarek
[jira] Commented: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670895#action_12670895
]
Jason Warner commented on GERONIMO-3759:
I'm not sure what specifically the error you receive has to do with this jira
other than that you're using the config.xml posted here, which also confuses
me. What are you attempting to do?
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Jason Warner
Fix For: 2.1.3, 2.2
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml, tomcat_server.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
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: 741247
Geronimo Revision: 741247 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 18 seconds
[INFO] Finished at: Thu Feb 05 15:47:34 EST 2009
[INFO] Final Memory: 394M/1014M
[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/20090205/logs-1500-tomcat/test.log
[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.491
[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 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:13.985)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.879)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:35.692)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:17.420)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:19.967)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:24.243)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.800)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:45.591)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:56.047)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:38.650)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:29.653)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.931)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.080)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:53.937)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:40.988) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:13.002)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.177)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:46.271)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:42.000)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.578)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test
[jira] Commented: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670974#action_12670974 ] Ivan commented on GERONIMO-4369: Thanks for your comments, Manu. I partly agreed your suggestions, 1. On restart from console changes are lost what I did in the patch Geronimo-4369-01.21 is the same with the previous one, except for trying to restart all the stopped configurations. Not sure which changes will be lost (except for those properties mentioned in 2))? 2. Admin console shows stop start and restart messages. I just want to show the full cycle about the restart process, maybe I print two much messages. 3. Failure to start modules. Not sure which modules are not started ? 4. Significant increase in startup time It is sure, I have no idea about it, anyway, it needs time to restart so much components. 5. Stopping and Starting the server also results in all changes being lost Not sure which changes are lost ? Could you please give an example. For your solution, basicly, it is better. Only one concern is that, if I restart configuration A, and A has a child configurtion B, only applies the changes to A may be not enough, some changes on B maybe lost. I have not try it, wish I made a mistake, ^_^ The new attribute values are overwrote while restarting the DB pool connector - Key: GERONIMO-4369 URL: https://issues.apache.org/jira/browse/GERONIMO-4369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: Geronimo 2.2 snapshot JDK 1.5 Windows XP Reporter: Ivan Assignee: Manu T George Priority: Blocker Fix For: 2.1.4, 2.2 Attachments: G-4369-0205.patch, Geronimo-4369-01.21.patch, Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, Geronimo-4369-11.19.patch After editing the values in the db pool, then restart it in the console, the new values lost. When saving the new attribute values, such as user name, the gbeandata in the configurationManager is not updated, so while restarting the connector, the gbinstance copies those old values from it. So the new persistent values do not take effect, Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.0: Failed for Revision: 741350
Geronimo Revision: 741350 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090205/build-2000.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.0/20090205 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 33 minutes 39 seconds [INFO] Finished at: Thu Feb 05 20:41:49 EST 2009 [INFO] Final Memory: 216M/862M [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/2.0/20090205/logs-2000-tomcat/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.293 sec FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.327 sec FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.657 sec FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.286 sec FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090205/logs-2000-jetty/test.log [INFO] Running deployment-testsuite.deployment [INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.333 sec FAILURE! -- [INFO] Running jpa-testsuite.jpa [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.36 sec FAILURE! [INFO] Running sec-testsuite.security [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.677 sec FAILURE! -- [INFO] Running web-testsuite.references [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.34 sec FAILURE!
[BUILD] trunk: Failed for Revision: 741359
Geronimo Revision: 741359 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090205
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 45 seconds
[INFO] Finished at: Thu Feb 05 21:43:35 EST 2009
[INFO] Final Memory: 608M/993M
[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/20090205/logs-2100-tomcat/test.log
[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:41.641
[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 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.734)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:29.058)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.880)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.420)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:21.884)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:20.040)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:42.898)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:48.899)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:48.529)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.055)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:31.164)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.272)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:31.376)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.944)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:43.353) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:11.852)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.474)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.301)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:35.148) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.928)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:28.190)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
[jira] Commented: (GERONIMO-4257) Problem with processing and delivery jms messages
[ https://issues.apache.org/jira/browse/GERONIMO-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671013#action_12671013 ] Ivan commented on GERONIMO-4257: I try it with the 2.2 snapshot of 20090202 1) When message is waiting for delivery to MDB i cannot undeploy module with this MDB from command line. I have to stop module via G-console and then undeploy - Could not reproduce it, I could undeploy the module while there are messages waiting for delivery to the MDB. 2) If messages are waiting for delivery and I shutdown server (geronimo stop) and the run it again none of messages are delivered to listener - After refering to the ActiveMQ document, add the ?consumer.retroactive=true to the queue name, those messages would be redeliveried to the MDB Please refer to the link http://activemq.apache.org/retroactive-consumer.html 3) When MDB onMessage method throws i.e. NullPointerException, the transaction is rolledback but a) message is not being redelivered anymore, b) module couldn't be restarted == application stops working Could not reproduce, the message is redeliveried. Thanks ! Problem with processing and delivery jms messages - Key: GERONIMO-4257 URL: https://issues.apache.org/jira/browse/GERONIMO-4257 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, OpenEJB, transaction manager Affects Versions: 2.1.1, 2.1.2 Environment: Windows XPPro SP2, JDK 6 Reporter: Tomasz Mazan Priority: Critical I've found strange Geronimo 2.1.2 behaviour with using JMS. 1) When message is waiting for delivery to MDB i cannot undeploy module with this MDB from command line. I have to stop module via G-console and then undeploy 2) If messages are waiting for delivery and I shutdown server (geronimo stop) and the run it again none of messages are delivered to listener 3) When MDB onMessage method throws i.e. NullPointerException, the transaction is rolledback but a) message is not being redelivered anymore, b) module couldn't be restarted == application stops working :( Geronimo 2.1 hadn't these features. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4485: Attachment: plugin-portlets.patch Port the GERONIMO-4474 patch for V2.1 - Key: GERONIMO-4485 URL: https://issues.apache.org/jira/browse/GERONIMO-4485 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.4 Attachments: console-base-portlets.patch, console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, plancreator-console-tomcat.patch, plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch Target release should be 2.2, if you can attach the patches by Jan. 7th. If you would like to see this in 2.1.4, then please attach additional patches created from that branch and we'll try to get them in after we wrap up the 2.2 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-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4485: Attachment: (was: plugin-portlets.patch) Port the GERONIMO-4474 patch for V2.1 - Key: GERONIMO-4485 URL: https://issues.apache.org/jira/browse/GERONIMO-4485 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.4 Attachments: console-base-portlets.patch, console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, plancreator-console-tomcat.patch, plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch Target release should be 2.2, if you can attach the patches by Jan. 7th. If you would like to see this in 2.1.4, then please attach additional patches created from that branch and we'll try to get them in after we wrap up the 2.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4525) No effective exit code for all Windows commands
[ https://issues.apache.org/jira/browse/GERONIMO-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-4525: - Assignee: Jarek Gawor No effective exit code for all Windows commands --- Key: GERONIMO-4525 URL: https://issues.apache.org/jira/browse/GERONIMO-4525 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3 Environment: MS Windows Reporter: Jack Cai Assignee: Jarek Gawor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4525_Jack.patch There are multiple problems in the current Windows batch commands (including geronimo.bat, startup.bat, etc.) - It's not recommended to define an environment variable with the name ERRORLEVEL. See [1]. - Set a value to ERRORLEVEL has no effect to the exit code of the batch command (so the documented exit code 0 and 1 are not actually there). - The value of the ERRORLEVEL variable will also get unset when the @endlocal command is called. [1] http://blogs.msdn.com/oldnewthing/archive/2008/09/26/8965755.aspx -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4485: Attachment: (was: console-base-portlets.patch) Port the GERONIMO-4474 patch for V2.1 - Key: GERONIMO-4485 URL: https://issues.apache.org/jira/browse/GERONIMO-4485 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.4 Attachments: console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, plancreator-console-tomcat.patch, plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch Target release should be 2.2, if you can attach the patches by Jan. 7th. If you would like to see this in 2.1.4, then please attach additional patches created from that branch and we'll try to get them in after we wrap up the 2.2 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-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4485: Attachment: console-base-portlets.patch Port the GERONIMO-4474 patch for V2.1 - Key: GERONIMO-4485 URL: https://issues.apache.org/jira/browse/GERONIMO-4485 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.4 Attachments: console-base-portlets.patch, console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, plancreator-console-tomcat.patch, plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch Target release should be 2.2, if you can attach the patches by Jan. 7th. If you would like to see this in 2.1.4, then please attach additional patches created from that branch and we'll try to get them in after we wrap up the 2.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671023#action_12671023 ] Manu T George commented on GERONIMO-4369: - Ivan, Regarding 1 I was not able to get the changes to persist on restart from admin console using the patch you provided. (Remember #2 above In case of stop and start #2 applies that is the reason none are getting saved). Actually this is due to #2 Regarding 2 Yes too many messages are printed. Try starting openejb module the entire screen is filled with messages :) Regarding 3 The j2ee-corba-yoko configuration as you mentioned doesn't restart. But if you use restartConfiguration it does. Regarding 4 I built two servers one with restartConfiguration (w/o ur patch) and one with yours and saw restart takes a lot of time with yours but less time with the restartConfiguration The reason for restart itself is to reduce the time taken to start again. Doing stop and start results in more time taken 5) This is regarding #2. Just pointing out that both patches don't fix it Regarding your point I thought of that but what I thought was that that use case occurrence is very rare(I dont see users making changes to parent and child configurations and restarting the parent that often) and maybe the overhead of applying overrides to each child configuration will not be worth it. Smacks of laziness :).I will try that out and see what the overhead is and update my patch. If the overhead is too high then I will need figure out a way to applyOverrides only for configurations that are dirty. Maybe the applyOverrides method already does that or there is some other way to check this. Thank you for analyzing my patch and pointing this out and for contributing all the other patches that helped. The new attribute values are overwrote while restarting the DB pool connector - Key: GERONIMO-4369 URL: https://issues.apache.org/jira/browse/GERONIMO-4369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: Geronimo 2.2 snapshot JDK 1.5 Windows XP Reporter: Ivan Assignee: Manu T George Priority: Blocker Fix For: 2.1.4, 2.2 Attachments: G-4369-0205.patch, Geronimo-4369-01.21.patch, Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, Geronimo-4369-11.19.patch After editing the values in the db pool, then restart it in the console, the new values lost. When saving the new attribute values, such as user name, the gbeandata in the configurationManager is not updated, so while restarting the connector, the gbinstance copies those old values from it. So the new persistent values do not take effect, Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4528) Accessing a web service's WSDL throws a NPE
Accessing a web service's WSDL throws a NPE
---
Key: GERONIMO-4528
URL: https://issues.apache.org/jira/browse/GERONIMO-4528
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.2
Environment: 2.2-SNAPSHOT from SVN
Reporter: Janko Heilgeist
I've deployed a web service whose WSDL contains various schema imports without
schemaLocations:
{code:xml}xs:import
namespace=http://schemas.ggf.org/jsdl/2005/11/jsdl/{code}
These imports are resolved via a jax-ws-catalog.xml:
{code:xml}
public
publicId=http://schemas.ggf.org/jsdl/2005/11/jsdl;
uri=schemas/ext/jsdl/jsdl-1.0.xsd/
{code}
Accessing this WSDL via Geronimo with the ?wsdl-URL results in a
NullPointerException on Tomcat/Axis. The code tries to update the
schemaLocation to a server-local URL and, for this reason, retrieves the
imported schema. But it never checks for a valid return value. Jetty/CXF simply
copies these import-elements to the output WSDL without further ado.
{code}
2009-02-06 08:02:21,239 ERROR [Axis2WebServiceContainer] Exception occurred
while trying to invoke service method doService()
java.lang.NullPointerException
at
org.apache.geronimo.axis2.WSDLQueryHandler.updateSchemaImports(WSDLQueryHandler.java:244)
at
org.apache.geronimo.axis2.WSDLQueryHandler.updateSchemaImports(WSDLQueryHandler.java:252)
at
org.apache.geronimo.axis2.WSDLQueryHandler.updateSchemaImports(WSDLQueryHandler.java:268)
at
org.apache.geronimo.axis2.WSDLQueryHandler.updateDefinition(WSDLQueryHandler.java:230)
at
org.apache.geronimo.axis2.WSDLQueryHandler.updateDefinition(WSDLQueryHandler.java:219)
at
org.apache.geronimo.axis2.WSDLQueryHandler.init(WSDLQueryHandler.java:158)
at
org.apache.geronimo.axis2.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:108)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.processGETRequest(Axis2WebServiceContainer.java:366)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:306)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.getWsdl(Axis2WebServiceContainer.java:190)
at
org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.handle(TomcatEJBWebServiceContext.java:213)
at
org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:187)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
{code}
IMHO, both assemblies should first consult an existing jax-ws-catalog.xml to
resolve the schemaLocations. If this doesn't work they should copy the import
verbatim and let the client resolve via its own catalog.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4485: Attachment: activemq-portlets.patch Attached the activemq-portlets patch. Port the GERONIMO-4474 patch for V2.1 - Key: GERONIMO-4485 URL: https://issues.apache.org/jira/browse/GERONIMO-4485 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.4 Attachments: activemq-portlets.patch, console-base-portlets.patch, console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, plancreator-console-tomcat.patch, plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch Target release should be 2.2, if you can attach the patches by Jan. 7th. If you would like to see this in 2.1.4, then please attach additional patches created from that branch and we'll try to get them in after we wrap up the 2.2 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
