[jira] Updated: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5700: -- Attachment: AMQ-1779.patch AMQ-1760.patch AMQ-1431.patch Attaching the migrated patches from 5.x to 4.1.2 Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933346#action_12933346 ] Ashish Jain commented on GERONIMO-5700: --- I am unable to build activemq 4.1.2 as per the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. I am using java 1.5.0_13 and maven 2.0.9. My build gets stuck at Running org.apache.activemq.network.DemandForwardingBridgeTest and it never moves there after for hours. Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5690) Clustering module fails to start on disabling JMXService gbean
[ https://issues.apache.org/jira/browse/GERONIMO-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933348#action_12933348 ] Ashish Jain commented on GERONIMO-5690: --- Thank you ashok for your tests. I will close the JIRA and will open a new track for 2.2 and 3.0. Thanks. Clustering module fails to start on disabling JMXService gbean -- Key: GERONIMO-5690 URL: https://issues.apache.org/jira/browse/GERONIMO-5690 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 Unable to start clustering module once you disable JMXService gbean. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933347#action_12933347 ] Ashish Jain commented on GERONIMO-5700: --- I am using windows xp sp3 Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5690) Clustering module fails to start on disabling JMXService gbean
[ https://issues.apache.org/jira/browse/GERONIMO-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5690: -- Fix Version/s: (was: 2.2.2) (was: 3.0) Clustering module fails to start on disabling JMXService gbean -- Key: GERONIMO-5690 URL: https://issues.apache.org/jira/browse/GERONIMO-5690 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Unable to start clustering module once you disable JMXService gbean. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5703) Track:Clustering module fails to start on disabling JMXService gbean
Track:Clustering module fails to start on disabling JMXService gbean Key: GERONIMO-5703 URL: https://issues.apache.org/jira/browse/GERONIMO-5703 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Track for GERONIMO-5690 for 2.2 and 3.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5690) Clustering module fails to start on disabling JMXService gbean
[ https://issues.apache.org/jira/browse/GERONIMO-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5690. - Resolution: Fixed Opened GERONIMO-5703 for 2.2 and 3.0. Clustering module fails to start on disabling JMXService gbean -- Key: GERONIMO-5690 URL: https://issues.apache.org/jira/browse/GERONIMO-5690 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Unable to start clustering module once you disable JMXService gbean. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo Branding
I just go through the requirements in http://www.apache.org/foundation/marks/pmcs quickly and here are some differences I've noticed. Not sure I was looking into the right direction. Project Website complied Project Naming and Description complied Website navigation links complied Trademark attributionswe don't have one on the Geronimo homepage, might need to update the main page? TM on logos and graphics we don't have the TM symbol in the graphic, might need to update the Graphic? Powered By ... Logos didn't find anything on Geronimo website similar to http://www.apache.org/images/apache_pb.gif, so we might just pass this one? Other trademark guideline GShell is written with Groovy, might need to use GShell for Groovy instead of GShell? just let me know if anything else I can help with. Jeff C On Wed, Nov 17, 2010 at 11:01 PM, Kevan Miller kevan.mil...@gmail.comwrote: All, We need to insure that the Geronimo website conforms to the current brand and trademark requirements as described in http://www.apache.org/foundation/marks/pmcs In particular, conforming to the naming and trademark attribution requirements will require updates. But, we'll need to review all of the requirements to insure that we're conforming. We'll need to include status in our next board report and have been asked to conform to these requirements by March 2011. Anybody interested in helping out with this? We should start with a review of the changes that are required (discuss on this list). --kevan
[jira] Created: (GERONIMO-5704) Track: Farming module provision of utilizing encrypted password instead of plain text
Track: Farming module provision of utilizing encrypted password instead of plain text - Key: GERONIMO-5704 URL: https://issues.apache.org/jira/browse/GERONIMO-5704 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Track for GERONIMO-5691 for 2,2 and 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933352#action_12933352 ] Ivan commented on GERONIMO-5700: I remembered that it is a known issue on windows xp (no sure where I saw this), you might need to build it on the Linux. Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5691) Farming module provision of utilizing encrypted password instead of plain text
[ https://issues.apache.org/jira/browse/GERONIMO-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5691. - Resolution: Fixed Fix Version/s: (was: 2.2.2) (was: 3.0) Ashok thanks a lot for your tests. I have opened GERONIMO-5704 for 2.2 and 3.0 track, Closing it Farming module provision of utilizing encrypted password instead of plain text -- Key: GERONIMO-5691 URL: https://issues.apache.org/jira/browse/GERONIMO-5691 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Farming module gbean ability to process encrypted password. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5693) Encryption logic for connectionPassword attribute in ldap realm
[ https://issues.apache.org/jira/browse/GERONIMO-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5693. - Resolution: Fixed Fix Version/s: (was: 2.2.2) (was: 3.0) Thank you Ashok for your test results. I have opened a new track GERONIMO-5705 for 2.2 and 3.0. Closing it. Encryption logic for connectionPassword attribute in ldap realm --- Key: GERONIMO-5693 URL: https://issues.apache.org/jira/browse/GERONIMO-5693 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 217 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Ldap realm list the connectionPassword option in plain text. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5705) Track: Encryption logic for connectionPassword attribute in ldap realm
Track: Encryption logic for connectionPassword attribute in ldap realm -- Key: GERONIMO-5705 URL: https://issues.apache.org/jira/browse/GERONIMO-5705 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Track for GERONIMO-5693 for 2.2 and 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5695) Upgrade wadi to 2.1.2
[ https://issues.apache.org/jira/browse/GERONIMO-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933360#action_12933360 ] Ashish Jain commented on GERONIMO-5695: --- Thank you ashok for your test results. Upgrade wadi to 2.1.2 - Key: GERONIMO-5695 URL: https://issues.apache.org/jira/browse/GERONIMO-5695 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 There are problems associated with WADI session replication manager which has been fixed in WADI 2.1.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5706) When derby authentication is disabled, DB manager portlet run SQL error: Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
When derby authentication is disabled, DB manager portlet run SQL error: Caused
by: java.sql.SQLException: Schema 'DBADMIN' does not exist
--
Key: GERONIMO-5706
URL: https://issues.apache.org/jira/browse/GERONIMO-5706
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: databases
Affects Versions: 2.1.7, 2.2.1
Environment: windows x86
sun java 1.5.0_22
Reporter: Forrest Xia
Assignee: viola.lu
Steps:
1. Get the latest 2.1.7 snapshot build
2. set env variable to disable derby authentication
C:\ set GERONIMO_OPTS=-Dderby.connection.requireAuthentication=false
3. start server
4. login admin console, go to DB Manager portlet to create a database
5. Execute these SQLs on the created derby db
create table name (name varchar(10));
insert into name values ('Tom');
6. Issue a select statement with DB manager portlet
select * from name
Then an exception like as below throws out:
javax.portlet.PortletException
at
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
at
org.apache.geronimo.console.internaldb.RunSQLPortlet.doView(RunSQLPortlet.java:146)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:144)
at
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
at
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at
org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:151)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
[jira] Commented: (GERONIMO-5692) Unlock keystore command line utility does not work with Configured Encryption
[ https://issues.apache.org/jira/browse/GERONIMO-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933362#action_12933362 ] Rex Wang commented on GERONIMO-5692: Hi, I refix this to use EncryptionManagerWrapperGBean instead of the new gbean. Could you please help verify? -Rex Unlock keystore command line utility does not work with Configured Encryption - Key: GERONIMO-5692 URL: https://issues.apache.org/jira/browse/GERONIMO-5692 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: crypto Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly g 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 Steps to recreate: 1) Enable ConfiguredEncryption as listed by the doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html. 2) Start the server 3) set JAVA_OPTS=location of truststoreKeystorePassword file 4) deploy.bat unlockKeystore name_of_the_keystore it fails to unlock the keystore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5706) When derby authentication is disabled, DB manager portlet run SQL error: Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
[
https://issues.apache.org/jira/browse/GERONIMO-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933363#action_12933363
]
Forrest Xia commented on GERONIMO-5706:
---
if using add proper schema prefix like this:
select * from app.name
then execution is successful.
So I think we should not assume dbadmin as the schema when derby auth is
disabled on the DB manager portlet.
When derby authentication is disabled, DB manager portlet run SQL error:
Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
--
Key: GERONIMO-5706
URL: https://issues.apache.org/jira/browse/GERONIMO-5706
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: databases
Affects Versions: 2.1.7, 2.2.1
Environment: windows x86
sun java 1.5.0_22
Reporter: Forrest Xia
Assignee: viola.lu
Steps:
1. Get the latest 2.1.7 snapshot build
2. set env variable to disable derby authentication
C:\ set GERONIMO_OPTS=-Dderby.connection.requireAuthentication=false
3. start server
4. login admin console, go to DB Manager portlet to create a database
5. Execute these SQLs on the created derby db
create table name (name varchar(10));
insert into name values ('Tom');
6. Issue a select statement with DB manager portlet
select * from name
Then an exception like as below throws out:
javax.portlet.PortletException
at
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
at
org.apache.geronimo.console.internaldb.RunSQLPortlet.doView(RunSQLPortlet.java:146)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:144)
at
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
at
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at
[jira] Commented: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933391#action_12933391 ] Ashish Jain commented on GERONIMO-5700: --- I tried building it on RHEL5 however I hit the same issue as my build is stuck stuck at Running org.apache.activemq.network.DemandForwardingBridgeTest. I am not sure if this is a network issue or a JDK related issue. Till now I have NOT applied any patch of GERONIMO-5700. I will try again with Java 6 and see if the behavior changes. Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- 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: 1036337
Geronimo Revision: 1036337 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 39 minutes 57 seconds [INFO] Finished at: Thu Nov 18 03:43:47 EST 2010 [INFO] Final Memory: 479M/998M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/logs-0300-tomcat/ Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 10.745 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.669 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/logs-0300-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.538 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/samples-0300.log Build status: FAILED
[jira] Commented: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933431#action_12933431 ] Ashish Jain commented on GERONIMO-5700: --- Looking at the activemq-log it suggests the following for DemandForwardingBridge test. Both the VMs are started thereafter nothing happens. No changes in the log and it remains as is. 2010-11-18 18:36:03,686 [Thread-2 ] INFO DemandForwardingBridge - Network connection between vm://localhost#0 and vm://remotehost#2(localhost) has been established. 2010-11-18 18:36:04,733 [main ] INFO TransportConnector - Connector vm://remotehost Stopped 2010-11-18 18:36:04,733 [main ] INFO TransportConnector - Connector vm://localhost Stopped 2010-11-18 18:36:04,733 [main ] INFO BrokerService - ActiveMQ Message Broker (localhost, ID:ashjain2-2138-1290085562592-10:1) is shutting down 2010-11-18 18:36:04,748 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:ashjain2-2138-1290085562592-10:1) stopped 2010-11-18 18:36:04,748 [main ] INFO BrokerService - ActiveMQ Message Broker (localhost, ID:ashjain2-2138-1290085562592-10:0) is shutting down 2010-11-18 18:36:04,748 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:ashjain2-2138-1290085562592-10:0) stopped 2010-11-18 18:36:04,748 [main ] INFO BrokerService - ActiveMQ null JMS Message Broker (localhost) is starting 2010-11-18 18:36:04,748 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ 2010-11-18 18:36:04,764 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:ashjain2-2138-1290085562592-10:2) started 2010-11-18 18:36:04,764 [main ] INFO TransportConnector - Connector vm://localhost Started 2010-11-18 18:36:04,764 [main ] INFO BrokerService - ActiveMQ null JMS Message Broker (localhost) is starting 2010-11-18 18:36:04,764 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ 2010-11-18 18:36:04,764 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:ashjain2-2138-1290085562592-10:3) started 2010-11-18 18:36:04,764 [main ] INFO TransportConnector - Connector vm://remotehost Started Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Problem building custom activemq for geronimo 2.1
Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish
Re: Problem building custom activemq for geronimo 2.1
More inputs are available in GERONIMO-5700. On Thu, Nov 18, 2010 at 8:07 PM, Ashish Jain ashja...@gmail.com wrote: Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish
[BUILD] trunk: Failed for Revision: 1036461
Geronimo Revision: 1036461 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/unit-test-reports 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M3-SNAPSHOT 3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M3-SNAPSHOT 4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M3-SNAPSHOT 5) org.eclipse.jetty:jetty-security:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:8.0.0.M3-SNAPSHOT 6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M3-SNAPSHOT -- 6 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] Updated: (GERONIMO-5706) When derby authentication is disabled, DB manager portlet run SQL error: Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
[
https://issues.apache.org/jira/browse/GERONIMO-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
viola.lu updated GERONIMO-5706:
---
Attachment: G5706.patch
Apply it to 21/22, thanks.
When derby authentication is disabled, DB manager portlet run SQL error:
Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
--
Key: GERONIMO-5706
URL: https://issues.apache.org/jira/browse/GERONIMO-5706
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: databases
Affects Versions: 2.1.7, 2.2.1
Environment: windows x86
sun java 1.5.0_22
Reporter: Forrest Xia
Assignee: viola.lu
Attachments: G5706.patch
Steps:
1. Get the latest 2.1.7 snapshot build
2. set env variable to disable derby authentication
C:\ set GERONIMO_OPTS=-Dderby.connection.requireAuthentication=false
3. start server
4. login admin console, go to DB Manager portlet to create a database
5. Execute these SQLs on the created derby db
create table name (name varchar(10));
insert into name values ('Tom');
6. Issue a select statement with DB manager portlet
select * from name
Then an exception like as below throws out:
javax.portlet.PortletException
at
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
at
org.apache.geronimo.console.internaldb.RunSQLPortlet.doView(RunSQLPortlet.java:146)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:144)
at
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
at
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at
Re: Geronimo Branding
Just read through the PMCS link, and I'd more or less concur with Jeff's comment. Quick scan of the main home page and a couple of possible additions come to mind, depending on the scope of this piece of work: - the header statement The goal of refers to the Geronimo project, rather than the Apache Geronimo project - theres a requirement for a prominent link to the ASF home page...which the link in the Overview panel may/may not comply with Agree on Trademarks/Powered by/Other guidelines. Guessing there'd be a need to check out the subproject sites as well (noted that the GBuild link in the nav panel looks to be broken). Happy to help out on this one. Cheers Dave On Thu, Nov 18, 2010 at 8:25 AM, chi runhua chirun...@gmail.com wrote: I just go through the requirements in http://www.apache.org/foundation/marks/pmcs quickly and here are some differences I've noticed. Not sure I was looking into the right direction. Project Website complied Project Naming and Description complied Website navigation links complied Trademark attributions we don't have one on the Geronimo homepage, might need to update the main page? TM on logos and graphics we don't have the TM symbol in the graphic, might need to update the Graphic? Powered By ... Logos didn't find anything on Geronimo website similar to http://www.apache.org/images/apache_pb.gif, so we might just pass this one? Other trademark guideline GShell is written with Groovy, might need to use GShell for Groovy instead of GShell? just let me know if anything else I can help with. Jeff C On Wed, Nov 17, 2010 at 11:01 PM, Kevan Miller kevan.mil...@gmail.com wrote: All, We need to insure that the Geronimo website conforms to the current brand and trademark requirements as described in http://www.apache.org/foundation/marks/pmcs In particular, conforming to the naming and trademark attribution requirements will require updates. But, we'll need to review all of the requirements to insure that we're conforming. We'll need to include status in our next board report and have been asked to conform to these requirements by March 2011. Anybody interested in helping out with this? We should start with a review of the changes that are required (discuss on this list). --kevan -- Cheers, Dave
Re: Geronimo Branding
Punted a reply to this, and now waiting to see if it bounces like the last one I tried. Assuming it doesn't and its cool to assist with this, how would I go about getting contributor status for things like the wiki ? I'm assuming any updates to the sites would need to be pursued via the JIRA ? Questionsalways chuffing questions :) dave On Wed, Nov 17, 2010 at 3:01 PM, Kevan Miller kevan.mil...@gmail.com wrote: All, We need to insure that the Geronimo website conforms to the current brand and trademark requirements as described in http://www.apache.org/foundation/marks/pmcs In particular, conforming to the naming and trademark attribution requirements will require updates. But, we'll need to review all of the requirements to insure that we're conforming. We'll need to include status in our next board report and have been asked to conform to these requirements by March 2011. Anybody interested in helping out with this? We should start with a review of the changes that are required (discuss on this list). --kevan -- Cheers, Dave
[BUILD] trunk: Failed for Revision: 1036599
Geronimo Revision: 1036599 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/unit-test-reports 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M3-SNAPSHOT 3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M3-SNAPSHOT 4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M3-SNAPSHOT 5) org.eclipse.jetty:jetty-security:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:8.0.0.M3-SNAPSHOT 6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M3-SNAPSHOT -- 6 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
Re: Geronimo Branding
On Nov 18, 2010, at 3:41 PM, Dave Horsey wrote: Punted a reply to this, and now waiting to see if it bounces like the last one I tried. Hi Dave, Two messages made it through. Are you getting emails rejected? Assuming it doesn't and its cool to assist with this, how would I go about getting contributor status for things like the wiki ? With an ICLA on file, all you have to do is create a Confluence id (https://cwiki.apache.org/confluence/dashboard.action -- click sign up), let us know your id, and ask... ;-) The ICLA insures that we have clear rights to license your documentation contributions under the Apache License. We *love* to have documentation contributors. So, your contributions would be most welcome. I'm assuming any updates to the sites would need to be pursued via the JIRA ? Depending on the scope of the changes required, we may want to create JIRA's for specific categories of changes. This might help us from stepping on each other's toes. Questionsalways chuffing questions :) Keep 'em coming! --kevan
[jira] Created: (GERONIMO-5707) Document the usage of dery authentication and possible problems during updgrade
Document the usage of dery authentication and possible problems during updgrade --- Key: GERONIMO-5707 URL: https://issues.apache.org/jira/browse/GERONIMO-5707 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Refer to GERONIMO-5689, GERONIMO-4296, users need provide credentials to access embedded derby databases starting from 2.1.7/2.2.1. We should have the document on 1. how to turn on/off the authentication 2. how to change the password of new derby admin 3. how to access user-defined databases when using previous versions 4. how to run sql statements when the derby authentication ss turned on 5. what happens to the datasource -- 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: 1036711
Geronimo Revision: 1036711 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101118/unit-test-reports 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M3-SNAPSHOT 3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M3-SNAPSHOT 4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M3-SNAPSHOT 5) org.eclipse.jetty:jetty-security:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:8.0.0.M3-SNAPSHOT 6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M3-SNAPSHOT -- 6 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] Closed: (GERONIMO-5706) When derby authentication is disabled, DB manager portlet run SQL error: Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
[
https://issues.apache.org/jira/browse/GERONIMO-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5706.
-
Resolution: Fixed
Fix Version/s: 2.2.1
2.1.7
commit to 2.1 branch at rev 1036727, 2.2 branch at rev 1036728.
Viola, thanks for this patch!
When derby authentication is disabled, DB manager portlet run SQL error:
Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
--
Key: GERONIMO-5706
URL: https://issues.apache.org/jira/browse/GERONIMO-5706
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: databases
Affects Versions: 2.1.7, 2.2.1
Environment: windows x86
sun java 1.5.0_22
Reporter: Forrest Xia
Assignee: viola.lu
Fix For: 2.1.7, 2.2.1
Attachments: G5706.patch
Steps:
1. Get the latest 2.1.7 snapshot build
2. set env variable to disable derby authentication
C:\ set GERONIMO_OPTS=-Dderby.connection.requireAuthentication=false
3. start server
4. login admin console, go to DB Manager portlet to create a database
5. Execute these SQLs on the created derby db
create table name (name varchar(10));
insert into name values ('Tom');
6. Issue a select statement with DB manager portlet
select * from name
Then an exception like as below throws out:
javax.portlet.PortletException
at
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
at
org.apache.geronimo.console.internaldb.RunSQLPortlet.doView(RunSQLPortlet.java:146)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:144)
at
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
at
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
at
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
at
Re: Problem building custom activemq for geronimo 2.1
I will have a look at it ... 2010/11/18 Ashish Jain ashja...@gmail.com More inputs are available in GERONIMO-5700. On Thu, Nov 18, 2010 at 8:07 PM, Ashish Jain ashja...@gmail.com wrote: Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish -- Ivan
Re: Problem building custom activemq for geronimo 2.1
I encountered the same problem when only built activemq-4.1.2 tag (without any of our patches). I think we can comment our the test from the build (activemq-4.1.2 had already commented out a lot of its tests...) -Rex 2010/11/18 Ashish Jain ashja...@gmail.com Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish -- Lei Wang (Rex) rwonly AT apache.org
[jira] Issue Comment Edited: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933693#action_12933693 ] Rex Wang edited comment on GERONIMO-5700 at 11/19/10 1:20 AM: -- I encountered the same problem when only built activemq-4.1.2 tag (without any of our patches). I think we can comment out the test from the build (activemq-4.1.2 had already commented out a lot of its tests...) -Rex was (Author: rwonly): I encountered the same problem when only built activemq-4.1.2 tag (without any of our patches). I think we can comment our the test from the build (activemq-4.1.2 had already commented out a lot of its tests...) -Rex Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933693#action_12933693 ] Rex Wang commented on GERONIMO-5700: I encountered the same problem when only built activemq-4.1.2 tag (without any of our patches). I think we can comment our the test from the build (activemq-4.1.2 had already commented out a lot of its tests...) -Rex Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 --- Key: GERONIMO-5700 URL: https://issues.apache.org/jira/browse/GERONIMO-5700 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5579) Problem with deploy:connect gogo command
[ https://issues.apache.org/jira/browse/GERONIMO-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933701#action_12933701 ] maojia commented on GERONIMO-5579: -- I tried the case again with a new geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin server built on 11/17/2010 and got the following error: geronimo deploy:connect -p 1109 Connecting to Geronimo server: localhost:1109 Username: system Password: *** Error executing command: Unable to connect to server at deployer:geronimo:jmx:// localhost:1109 -- Failed to retrieve RMIServer stub: javax.naming.ConfigurationE xception: rmiURLContextFactory.getObjectInstance: argument must be an RMI URL St ring or an array of them Problem with deploy:connect gogo command -- Key: GERONIMO-5579 URL: https://issues.apache.org/jira/browse/GERONIMO-5579 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Environment: windows platform Reporter: maojia Assignee: Ivan Priority: Minor Fix For: 3.0 Attachments: GERONIMO-5579.patch I started two server instances on my local Windows platform: geronimo-tomcat7-javaee6-3.0-SNAPSHOT using port 1099,started with the run Geronimo command; geronimo-tomcat6-javaee5-2.2 using port 1109, started with the startupcommand. On the karaf shell for the geronimo-tomcat7-javaee6-3.0-SNAPSHOT server: I ran the deploy:connect --port 1109command trying to connect the geronimo-tomcat6-javaee5-2.2 server. Connection establishedwas displayed. However,when running the deploy:list-modulescommand, it was the modules belonging to the geronimo-tomcat7-javaee6-3.0-SNAPSHOT server that was listed, indicating that it was still the geronimo-tomcat7-javaee6-3.0-SNAPSHOT server that was connected. The information on the command window is as follows: geronimo deploy:disconnect Not connected geronimo deploy:connect --hostname localhost --port 1109 Connection established geronimo deploy:list-modules Found 54 modules + org.apache.geronimo.configs/activemq-broker-blueprint/3.0-SNAPSHOT/car + org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car + org.apache.geronimo.configs/aries-deployer/3.0-SNAPSHOT/car + org.apache.geronimo.configs/axis2-deployer/3.0-SNAPSHOT/car + org.apache.geronimo.configs/bval-deployer/3.0-SNAPSHOT/car + org.apache.geronimo.configs/client-deployer/3.0-SNAPSHOT/car ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
