[jira] Commented: (GERONIMODEVTOOLS-562) Can't install plugin via GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679536#action_12679536 ] viola.lu commented on GERONIMODEVTOOLS-562: --- for jdk 1.5, it can list out plugin, but errors exit after install it. Can't install plugin via GEP Key: GERONIMODEVTOOLS-562 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-562 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.4 Environment: os:win 2003 JDK: 1.6 Reporter: viola.lu Assignee: Tim McConnell Attachments: sample-plugins.zip Steps: 1.Extract attached sample plugin file 2.In eclipse, right-click g server , choose open and click convert app to plugin, choose sample plugin location as local repository and click next, but no plugin is listed to install, so this also result in summary page can't display for server plugin manger But i can install it via admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Whence the geronimo kernel?
I as user see Geronimo not as GBeans nor as OSGI server, I see it as JEE server. So my requirements are to have a server - that runs standard JEE applications - without changes necessary - on an Apache licensed server Therefore the change to OSGI should be transparent to users, I wouldn't want to have to specify OSGI dependencies for JEE applications. If there is OSGI below, fine. If I can use it, fine. But it should not be necessary for standard JEE apps. Thanks, Juergen -- View this message in context: http://www.nabble.com/Whence-the-geronimo-kernel--tp22343125s134p22372881.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: svn commit: r700193 - in /geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main: java/org/apache/geronimo/console/internaldb/ resources/ webapp/WEB-INF/view/internaldb/
Yep, I think that was the case.
-Donald
David Jencks wrote:
On Mar 4, 2009, at 12:52 PM, Joe Bohn wrote:
I know this is going way back in time ... but any idea why this change
deleted the content of dbViewerMaximized.jsp but kept the empty file
around?
That's easy to do when you run patch -p0 which can empty files but not
run svn rm on them.
I discovered this when checking for source headers. This file is
flagged because it doesn't contain a header - but more than that it
doesn't contain anything at all.
I presume we can delete the entire file. Does anybody know of any
reason why we should not do this?
There are a few other instances of similar files that we need to deal
with as well.
I expect the *Maximized.jsp were never referenced and the patch author
deleted them but did not succeed in conveying the need to run svn rm to
the patch applier.
thanks
david jencks
Joe
dwo...@apache.org wrote:
Author: dwoods
Date: Mon Sep 29 11:09:17 2008
New Revision: 700193
URL: http://svn.apache.org/viewvc?rev=700193view=rev
Log:
GERONIMO-4225 Allow Run SQL portlet run sql against any configured
data source. Thanks to Michal Borowiecki for the patch.
Added:
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/webapp/WEB-INF/view/internaldb/listDatabasesMaximized.jsp
(with props)
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/webapp/WEB-INF/view/internaldb/listTablesMaximized.jsp
(with props)
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/webapp/WEB-INF/view/internaldb/viewTableContentsMaximized.jsp
(with props)
Modified:
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DBViewerHelper.java
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DBViewerPortlet.java
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DerbyConnectionUtil.java
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/RunSQLHelper.java
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/RunSQLPortlet.java
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/resources/systemdatabase.properties
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/webapp/WEB-INF/view/internaldb/dbViewerMaximized.jsp
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/webapp/WEB-INF/view/internaldb/runSQLNormal.jsp
Modified:
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DBViewerHelper.java
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DBViewerHelper.java?rev=700193r1=700192r2=700193view=diff
==
---
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DBViewerHelper.java
(original)
+++
geronimo/server/branches/2.1/plugins/system-database/sysdb-portlets/src/main/java/org/apache/geronimo/console/internaldb/DBViewerHelper.java
Mon Sep 29 11:09:17 2008
@@ -18,9 +18,20 @@
package org.apache.geronimo.console.internaldb;
import java.io.File;
+import java.util.ArrayList;
import java.util.Collection;
+import java.util.List;
import java.util.Vector;
+import org.apache.geronimo.console.util.KernelManagementHelper;
+import org.apache.geronimo.console.util.ManagementHelper;
+import org.apache.geronimo.console.util.PortletManager;
+import org.apache.geronimo.gbean.AbstractName;
+import org.apache.geronimo.j2ee.j2eeobjectnames.NameFactory;
+import org.apache.geronimo.kernel.Kernel;
+import org.apache.geronimo.kernel.KernelRegistry;
+import org.apache.geronimo.management.geronimo.ResourceAdapterModule;
+
public class DBViewerHelper {
private static final String SYS_TBL_PREFIX = SYS.;
@@ -28,6 +39,34 @@
private static final int COUNT_COL = 1;
/**
+ * List the databases having datasources deployed.
+ *
+ * @param derbySysHome
+ * @return
+ */
+public CollectionString getDataSourceNames() {
+
+ListString databaseNames = new ArrayListString();
+
+Kernel kernel = KernelRegistry.getSingleKernel();
+ManagementHelper helper = new KernelManagementHelper(kernel);
+ResourceAdapterModule[] modules =
helper.getOutboundRAModules(helper.getDomains()[0].getServerInstances()[0],
javax.sql.DataSource);
+for (ResourceAdapterModule module : modules) {
+
[jira] Closed: (GERONIMODEVTOOLS-561) Can't change version in project facets
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMODEVTOOLS-561. - Resolution: Won't Fix Closing as requested by Viola Can't change version in project facets -- Key: GERONIMODEVTOOLS-561 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-561 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.4 Environment: OS:windows JDK 1.5 Reporter: viola.lu Assignee: Delos Dai Priority: Minor 1.Create an application client in eclipse and run it on geronimo runtime 2.Right-click project properties and choose App client version from 5 to 1.4, but error exists: App Client 5 can't be uninstalled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4561) An invalid string system shows up in the Login Timeout field in Derby Embedded or Derby Embedded XA database pool configuration page
[ https://issues.apache.org/jira/browse/GERONIMO-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4561: --- Patch Info: [Patch Available] Fix Version/s: 2.2 2.1.4 Assignee: Joe Bohn An invalid string system shows up in the Login Timeout field in Derby Embedded or Derby Embedded XA database pool configuration page Key: GERONIMO-4561 URL: https://issues.apache.org/jira/browse/GERONIMO-4561 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: Windows XP + IBM JDK 6 Reporter: Ying Tang Assignee: Joe Bohn Priority: Trivial Fix For: 2.1.4, 2.2 Attachments: 1.5vs1.6.JPG, Geronimo-4561.patch 1. In the database pools portlet, create a database pool with the type Derby embedded XA or Derby embedded. 2. In the resulting configuration page, the Login Timeout field will have a default value system. This property claimed to be ignored by Derby. 3. Select JAR, specify database name, confirm password, and deploy. An error occurs: 2009-03-02 15:46:11,156 ERROR [Deployer] Deployment failed due to org.apache.geronimo.common.propertyeditor.PropertyEditorException: For input string: system at org.apache.geronimo.common.propertyeditor.IntegerEditor.getValue(IntegerEditor.java:34) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.getValue(ConnectorModuleBuilder.java:817) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.setDynamicGBeanDataAttributes(ConnectorModuleBuilder.java:782) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.addOutboundGBeans(ConnectorModuleBuilder.java:929) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.addConnectorGBeans(ConnectorModuleBuilder.java:597) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.initContext(ConnectorModuleBuilder.java:524) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:595) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:59) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39) at java.lang.reflect.Method.invoke(Method.java:612) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:735) Caused by: java.lang.NumberFormatException: For input string: system at java.lang.Throwable.init(Throwable.java:67) at java.lang.NumberFormatException.forInputString(NumberFormatException.java:61) at java.lang.Integer.parseInt(Integer.java:460) at java.lang.Integer.valueOf(Integer.java:566) at org.apache.geronimo.common.propertyeditor.IntegerEditor.getValue(IntegerEditor.java:31) ... 19 more 2009-03-02 15:46:11,265 INFO [DatabasePoolPortlet] Deployment Failed! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4561) An invalid string system shows up in the Login Timeout field in Derby Embedded or Derby Embedded XA database pool configuration page
[ https://issues.apache.org/jira/browse/GERONIMO-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4561: -- Assignee: Jarek Gawor (was: Joe Bohn) An invalid string system shows up in the Login Timeout field in Derby Embedded or Derby Embedded XA database pool configuration page Key: GERONIMO-4561 URL: https://issues.apache.org/jira/browse/GERONIMO-4561 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: Windows XP + IBM JDK 6 Reporter: Ying Tang Assignee: Jarek Gawor Priority: Trivial Fix For: 2.1.4, 2.2 Attachments: 1.5vs1.6.JPG, Geronimo-4561.patch 1. In the database pools portlet, create a database pool with the type Derby embedded XA or Derby embedded. 2. In the resulting configuration page, the Login Timeout field will have a default value system. This property claimed to be ignored by Derby. 3. Select JAR, specify database name, confirm password, and deploy. An error occurs: 2009-03-02 15:46:11,156 ERROR [Deployer] Deployment failed due to org.apache.geronimo.common.propertyeditor.PropertyEditorException: For input string: system at org.apache.geronimo.common.propertyeditor.IntegerEditor.getValue(IntegerEditor.java:34) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.getValue(ConnectorModuleBuilder.java:817) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.setDynamicGBeanDataAttributes(ConnectorModuleBuilder.java:782) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.addOutboundGBeans(ConnectorModuleBuilder.java:929) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.addConnectorGBeans(ConnectorModuleBuilder.java:597) at org.apache.geronimo.connector.deployment.ConnectorModuleBuilder.initContext(ConnectorModuleBuilder.java:524) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:595) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:59) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39) at java.lang.reflect.Method.invoke(Method.java:612) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:735) Caused by: java.lang.NumberFormatException: For input string: system at java.lang.Throwable.init(Throwable.java:67) at java.lang.NumberFormatException.forInputString(NumberFormatException.java:61) at java.lang.Integer.parseInt(Integer.java:460) at java.lang.Integer.valueOf(Integer.java:566) at org.apache.geronimo.common.propertyeditor.IntegerEditor.getValue(IntegerEditor.java:31) ... 19 more 2009-03-02 15:46:11,265 INFO [DatabasePoolPortlet] Deployment Failed! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-555) Generated geronimo-plugin.xml file is empy after converting application to plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMODEVTOOLS-555: - Assignee: (was: Tim McConnell) Generated geronimo-plugin.xml file is empy after converting application to plugin -- Key: GERONIMODEVTOOLS-555 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-555 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Environment: SunJDk 1.6 Reporter: viola.lu 1.Install GEP 2.2 snapshot on eclispe, start G2.2snapshot in it. 2.Open defined server, and launch convert apps to plugins 3.Choose deployed app cviewer and conver it to plugin, successfully saved ,but check geronimo-plugin.xml, it's empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4550: --- Patch Info: [Patch Available] Fix Version/s: 2.2 2.1.4 Assignee: Donald Woods (was: Gang Yin) No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.1.4, 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Whence the geronimo kernel?
I think this is a fair requirement from.I also think the OSGi community is aware of this requirement. For example, the web container in OSGi spec that I am following, it requires the web container in OSGi to support deployment of traditional war file as well as the OSGi bundle war file. Lin On Fri, Mar 6, 2009 at 8:52 AM, Juergen Weber webe...@gmail.com wrote: Therefore the change to OSGI should be transparent to users, I wouldn't want to have to specify OSGI dependencies for JEE applications. If there is OSGI below, fine. If I can use it, fine. But it should not be necessary for standard JEE apps. Thanks, Juergen -- View this message in context: http://www.nabble.com/Whence-the-geronimo-kernel--tp22343125s134p22372881.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Whence the geronimo kernel?
On Mar 6, 2009, at 8:52 AM, Juergen Weber wrote: I as user see Geronimo not as GBeans nor as OSGI server, I see it as JEE server. So my requirements are to have a server - that runs standard JEE applications - without changes necessary - on an Apache licensed server Therefore the change to OSGI should be transparent to users, I wouldn't want to have to specify OSGI dependencies for JEE applications. If there is OSGI below, fine. If I can use it, fine. But it should not be necessary for standard JEE apps. Absolutely agree. To the point that I might not have thought to bother stating it -- so I'm glad you did... ;-) I would expect that OSGi features would become available to JEE users, but they'd not be forced or even expected to use them. --kevan
[jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679627#action_12679627 ] Joe Bohn commented on GERONIMO-4507: Applied locale-priority_fix2_v22.patch to trunk in rev 750949. Please verify and provide a patch for branches/2.1. Thanks! Admin console should honor the priority of user agent's language setting Key: GERONIMO-4507 URL: https://issues.apache.org/jira/browse/GERONIMO-4507 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Environment: All Reporter: Jack Cai Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Attachments: locale-priority.patch, locale-priority_fix.patch, locale-priority_fix2_v22.patch, locale-priority_V21.patch See discussion: http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4546) New Axis2 rs spec import
[ https://issues.apache.org/jira/browse/GERONIMO-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4546. --- Resolution: Fixed This was a new dependency added recently to Axis2 trunk. However, I just switched Geronimo to use Axis2 1.5-SNAPSHOT (branches/1_5) which does not have this dependency, so I ended up reverting your change. However, this dependency might still be needed in the future if we switch back to Axis2 trunk. Thanks for taking care of it while I was out. New Axis2 rs spec import Key: GERONIMO-4546 URL: https://issues.apache.org/jira/browse/GERONIMO-4546 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.2 Reporter: David Jencks Assignee: Jarek Gawor Fix For: 2.2 Axis 2 dependencies have changed, adding dependency groupIdjavax.ws.rs/groupId artifactIdjsr311-api/artifactId typejar/type /dependency I'm hoping Jarek can figure out if we want/need to include this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3934) geronimo/start-server --timeout option does not work as expected
[ https://issues.apache.org/jira/browse/GERONIMO-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3934: - Assignee: (was: Jarek Gawor) geronimo/start-server --timeout option does not work as expected Key: GERONIMO-3934 URL: https://issues.apache.org/jira/browse/GERONIMO-3934 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor The --timeout option specifies the time in which the server must start up in. However, it looks like the timeout causes the server to shutdown after the given number of seconds even if the server started up successfully. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4532: --- Fix Version/s: (was: 2.1.4) Port the GERONIMO-4484 patch for V2.1 - Key: GERONIMO-4532 URL: https://issues.apache.org/jira/browse/GERONIMO-4532 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 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor I think that this issue is very important. After the GERONIMO-4485 patches are committed, I will try to port GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679631#action_12679631 ] Joe Bohn commented on GERONIMO-4532: Some of the updates to trunk for GERONIMO-4484 seem to have messed up the formatting of some of the views. Likewise, we are nearly ready to ship a Geronimo 2.1.4 release and there is not yet a patch available. At this point I don't think it makes sense to add this into 2.1.4. I'm removing 2.1.4 from the fix version. We can consider this for a future 2.1.* release once issues have been resolved and we have a branches/2.1 patch available. Port the GERONIMO-4484 patch for V2.1 - Key: GERONIMO-4532 URL: https://issues.apache.org/jira/browse/GERONIMO-4532 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 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor I think that this issue is very important. After the GERONIMO-4485 patches are committed, I will try to port GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4550: --- Fix Version/s: (was: 2.1.4) It appears that this fix is dependent upon the common message update which is not yet available in 2.1 and there is only a patch for 2.2. We're getting close to a 2.1.4 release and introducing these changes would be too disruptive at this point in time. Therefore, I'm removing the fix version of 2.1.4 from the JIRA. No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Welcome ivan Hai Hong Xu as a new committer
I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald
Re: Welcome ivan Hai Hong Xu as a new committer
On Mar 6, 2009, at 12:06 PM, Donald Woods wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. Congrats Ivan! I've updated svn permissions. So, you should have commit rights to Geronimo, now. Welcome aboard! --kevan
Re: Welcome ivan Hai Hong Xu as a new committer
Congrats Ivan! Joe Donald Woods wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald
Re: Welcome ivan Hai Hong Xu as a new committer
Congratulations! On Fri, Mar 6, 2009 at 12:24 PM, Joe Bohn joe.b...@earthlink.net wrote: Congrats Ivan! Joe Donald Woods wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald -- ~Jason Warner
Re: Welcome ivan Hai Hong Xu as a new committer
Congrats Ivan! Jarek On Fri, Mar 6, 2009 at 12:06 PM, Donald Woods dwo...@apache.org wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald
[jira] Commented: (GERONIMO-4574) PolicyContext handler data objects are never released
[ https://issues.apache.org/jira/browse/GERONIMO-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679663#action_12679663 ] Jarek Gawor commented on GERONIMO-4574: --- I added some calls to reset the PolicyContext handler data object to null in trunk (revision 750994) and branches/2.1 (revision 75099). However, that's not an optimal solution. It should be restoring to the previous handler data object but there is no easy way to get the current handler data value. PolicyContext handler data objects are never released - Key: GERONIMO-4574 URL: https://issues.apache.org/jira/browse/GERONIMO-4574 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.4, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor PolicyContext.setHandlerData() sets a given object on the thread. In Geronimo Jetty and Tomcat code this is called to set the HttpServletRequest object as the policy handler data. The problem is, that there is no call to unset the handler data object from the thread. That causes the HttpServletRequest objects (and its references) to stay in memory longer then necessary. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679671#action_12679671 ] Donald Woods commented on GERONIMO-4550: Didn't see where the patch depended on the CommonMessage feature. Applied to 2.1.4 as Rev751010. No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4550: --- Fix Version/s: 2.1.4 No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.1.4, 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4549: --- Attachment: Geronimo-4549_0307.patch I've got some progress now. 1. For the original problem, it happens in such scenario: if there are two names which share some common intermediate parts, e.g., test/test1/GBean/R1 and test/test2/GBean/R2, then any attempts to remove any of them will fail. This can be fixed by using passed-in removeNotEmptyContext instead of false in org.apache.xbean.naming.context.WritableContext$NestedWritableContext.removeBinding(). I've read through related code and feel it's a safe update. 2. There is another more serious problem exposed after the above problem is fixed, i.e., the index entries in WritableContext will not be removed when the corresponding object is removed. This will result in subsequent lookup for that object continuing to succeed. I've also fixed this. I wrote two testcases for future regression. The patched code passes all previous unit tests in addition to the new ones. Also verified the JMS resource issue in Admin Console is now resolved. JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4549_0307.patch Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4574) PolicyContext handler data objects are never released
[ https://issues.apache.org/jira/browse/GERONIMO-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4574. --- Resolution: Fixed Fix Version/s: 2.2 2.1.4 PolicyContext handler data objects are never released - Key: GERONIMO-4574 URL: https://issues.apache.org/jira/browse/GERONIMO-4574 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.4, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.4, 2.2 PolicyContext.setHandlerData() sets a given object on the thread. In Geronimo Jetty and Tomcat code this is called to set the HttpServletRequest object as the policy handler data. The problem is, that there is no call to unset the handler data object from the thread. That causes the HttpServletRequest objects (and its references) to stay in memory longer then necessary. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome ivan Hai Hong Xu as a new committer
Great! Congratulatiosn Ivan! -Jack 2009/3/7 Jarek Gawor jga...@gmail.com Congrats Ivan! Jarek On Fri, Mar 6, 2009 at 12:06 PM, Donald Woods dwo...@apache.org wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald
Re: Welcome ivan Hai Hong Xu as a new committer
Congrats Ivan!!! Lin On Fri, Mar 6, 2009 at 12:06 PM, Donald Woods dwo...@apache.org wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679683#action_12679683 ] Donald Woods commented on GERONIMO-4549: Joe, +1 for getting this into 2.1.4, even if it delays a RC by a couple days JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4549_0307.patch Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4575) Update Repository List in Plugin portlet does not display error message when geronimo.apache.org is down
Update Repository List in Plugin portlet does not display error message when
geronimo.apache.org is down
Key: GERONIMO-4575
URL: https://issues.apache.org/jira/browse/GERONIMO-4575
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console
Affects Versions: 2.1.3, 2.2
Reporter: Donald Woods
Priority: Minor
Fix For: 2.2
Just noticed that when geronimo.apache.org is down or cannot be reached, that
the Plugins portlet does not display a error message when the Update Repository
List link is used, but throws an exception in the console -
{noformat}
2009-03-06 13:46:15,268 ERROR [PluginRepositoryDownloader] Unable to save
download repositories
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
at sun.net.www.http.HttpClient.init(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:321)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
...
{noformat}
We should use the new CommonMessage feature to display the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods resolved GERONIMO-4550. Resolution: Fixed Applied patch for trunk as Rev751035. No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.1.4, 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome ivan Hai Hong Xu as a new committer
Congratulations! Jay Donald Woods wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald
[jira] Assigned: (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 reassigned GERONIMO-4517: -- Assignee: Ivan (was: Donald Woods) 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: Ivan 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-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679693#action_12679693 ] Joe Bohn commented on GERONIMO-4549: So it seems that this really is an XBean issue. We should create a JIRA under their project: http://issues.apache.org/jira/browse/XBEAN For us to get this into Geronimo 2.1.4 we would need another xbean release first. It would most likely delay 2.1.4 more than just a few days. JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4549_0307.patch Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4576) Make persistence exceptions more visible to client
Make persistence exceptions more visible to client -- Key: GERONIMO-4576 URL: https://issues.apache.org/jira/browse/GERONIMO-4576 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: persistence Affects Versions: 2.2 Environment: Linux, Windows Reporter: Joe Bohn Assignee: David Jencks Priority: Minor Fix For: 2.2 See http://issues.apache.org/jira/browse/GERONIMO-3907 for details of the original problem. That core problem was resolved. However, upon resolution it was mentioned that it would be beneficial to report more specific failure information back to the client. From GERONIMO-3907: Ralf Baumhof - 06/May/08 06:17 AM Today if have tested the new Geronimo release 2.1.1 (published on 28.04.2008). The problem is now fixed. If the server gets an error on trying a commit, this error is now thrown to the web bean. Exception text: javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Root Cause: javax.transaction.TransactionRolledbackException : Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Unfortunately there is no proper root cause attached to the exception. So the cause can only be seen in the server console, but can not be reported to the user. It would be very nice if you could change this in a later release. Thanks for your help. Vincent MATHON - 06/Nov/08 02:03 AM I agree that exceptions on the server side should not be thrown to the client side since such exceptions types might not be known by the client. However, for unit testing purpose, it is useful to attach the root cause to the RollBackException. I have modified a few lines in org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the root cause in case of RollBackException and it works for my unit testing purpose (I have not enough background on the java transaction architecture topic to submit a patch for production). It would be great to define a configuration parameter that permits to provide the root cause to the client and keep the current behaviour that does not by default. Geoff Callender - 22/Dec/08 03:36 AM It's useful for more than unit testing - it's essential to be able to inform the client what's wrong with the request. I've added some examples of this to https://issues.apache.org/jira/browse/OPENEJB-782 . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679706#action_12679706 ] Joe Bohn commented on GERONIMO-3907: I created http://issues.apache.org/jira/browse/GERONIMO-4576 to address the further enhancements that are mentioned in this JIRA so that it can be closed as it appears the original problem was resolved in Geronimo 2.1.1. Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.4, 2.2 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68) at javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75) at
[jira] Updated: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3907: --- Fix Version/s: (was: 2.1.4) (was: 2.2) 2.1.1 Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.1 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68) at javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:54) at javax.faces.component.UICommand.broadcast(UICommand.java:121) at
[jira] Resolved: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3907. Resolution: Fixed As confirmed in comments the core issue was resolved in 2.1.1. Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.1 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68) at javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:54) at javax.faces.component.UICommand.broadcast(UICommand.java:121) at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:292)
Re: Welcome ivan Hai Hong Xu as a new committer
Thanks very much, it is my honour to be the Geronimo committer. ^_^ 2009/3/7 Jay D. McHugh jaydmch...@gmail.com Congratulations! Jay Donald Woods wrote: I would like to welcome Ivan aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was just created this morning (xuhaihong), so you should start seeing some commits from him soon. -Donald -- Ivan
[BUILD] trunk: Failed for Revision: 751159
Geronimo Revision: 751159 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090306/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090306
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 23 minutes 53 seconds
[INFO] Finished at: Fri Mar 06 21:45:27 EST 2009
[INFO] Final Memory: 427M/994M
[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/20090306/logs-2100-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:40.652
[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:02.667)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.134)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.311)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.855)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:26.647)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:20.888)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:42.935)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:50.132)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:55.713)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.949)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.007)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.406)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:33.139)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:03.203)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.581)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:03.728)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.163)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:50.473)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:36.619) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.986)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679822#action_12679822 ] Jack Cai commented on GERONIMO-4549: If pulling in this fix solely delays Geronimo 2.1.4 release, then I'm inclined to exclude it for the time being. After all, it's almost 6 months now since last Geronimo release. Let's just get it into the trunk. Opened an XBean issue: https://issues.apache.org/jira/browse/XBEAN-122 JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4549_0307.patch Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome ivan Hai Hong Xu as a new committer
Congrats haihong! You will be very busy from now on. ^_^
[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=12679827#action_12679827 ] Gang Yin commented on GERONIMO-4517: Hi Ivan, As Donald has reassigned this JIRA to you, please help to review and commit these patches after I submit the patch for TranQL localization. Thanks. BTW, the first patch in the list had already been committed. 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: Ivan 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-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679828#action_12679828 ] Gang Yin commented on GERONIMO-4507: Thanks Joe, I will provide a patch for 2.1 branch soon. Admin console should honor the priority of user agent's language setting Key: GERONIMO-4507 URL: https://issues.apache.org/jira/browse/GERONIMO-4507 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Environment: All Reporter: Jack Cai Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Attachments: locale-priority.patch, locale-priority_fix.patch, locale-priority_fix2_v22.patch, locale-priority_V21.patch See discussion: http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679830#action_12679830 ] Gang Yin commented on GERONIMO-4550: Donald is right, the patch for 2.1 branch doesn't depend on the CommonMessage feature. Thanks Donald. Thanks Joe. No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.1.4, 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (XBEAN-122) Object cannot be removed from context in many circumstances
Object cannot be removed from context in many circumstances --- Key: XBEAN-122 URL: https://issues.apache.org/jira/browse/XBEAN-122 Project: XBean Issue Type: Bug Components: naming Affects Versions: 3.5 Reporter: Jack Cai Attachments: Geronimo-4549_0307.patch See https://issues.apache.org/jira/browse/GERONIMO-4549 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
