[jira] Commented: (GERONIMO-5767) Utilize karaf features functionality to replace part of our plugins functionality with karaf features
[ https://issues.apache.org/jira/browse/GERONIMO-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12989628#comment-12989628 ] Ashish Jain commented on GERONIMO-5767: --- David, unable to build this up. It fails due to missing pax-logging-service:jar:1.6.0-SNAPSHOT and pax-logging-api:jar:1.6.0-SNAPSHOT. I have looked into https://oss.sonatype.org/content/repositories/ops4j-snapshots/org/ops4j/pax/logging/pax-logging-api/ but snapshot jar seems to be missing. Utilize karaf features functionality to replace part of our plugins functionality with karaf features -- Key: GERONIMO-5767 URL: https://issues.apache.org/jira/browse/GERONIMO-5767 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Environment: Geronimo 3.0 Reporter: Ashish Jain Assignee: Ashish Jain -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5767) Utilize karaf features functionality to replace part of our plugins functionality with karaf features
[ https://issues.apache.org/jira/browse/GERONIMO-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984091#action_12984091 ] Ashish Jain commented on GERONIMO-5767: --- David, when I access the link https://djen...@github.com/djencks/karaf.git it gives 404. Utilize karaf features functionality to replace part of our plugins functionality with karaf features -- Key: GERONIMO-5767 URL: https://issues.apache.org/jira/browse/GERONIMO-5767 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Environment: Geronimo 3.0 Reporter: Ashish Jain Assignee: Ashish Jain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5767) Utilize karaf features functionality to replace part of our plugins functionality with karaf features
Utilize karaf features functionality to replace part of our plugins functionality with karaf features -- Key: GERONIMO-5767 URL: https://issues.apache.org/jira/browse/GERONIMO-5767 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Environment: Geronimo 3.0 Reporter: Ashish Jain Assignee: Ashish Jain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5766) Assembly plugin to create a custom karaf instance
Assembly plugin to create a custom karaf instance - Key: GERONIMO-5766 URL: https://issues.apache.org/jira/browse/GERONIMO-5766 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Environment: Geronimo 3.0 Reporter: Ashish Jain Assignee: Ashish Jain Create a assembly plugin to chalk out a custom karaf instance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5586) Provide a way to transform traditional jar to OSGi bundle when user install the jar into G repository.
[ https://issues.apache.org/jira/browse/GERONIMO-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain reassigned GERONIMO-5586: - Assignee: Ashish Jain (was: Rex Wang) Provide a way to transform traditional jar to OSGi bundle when user install the jar into G repository. -- Key: GERONIMO-5586 URL: https://issues.apache.org/jira/browse/GERONIMO-5586 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Forrest Xia Assignee: Ashish Jain As G server fundamentally turn into an OSGi based java ee application server, all libraries are required to be a OSGi bundle. But this may not work friendly to popular Java EE user. Let's say a simple scenario that deploys a data source to G server: 1. User uses install-library command or admin console to install the jdbc driver into G repository 2. User prepare a datasource deployment plan that depends on the installed jdbc driver 3. User uses deploy command or admin console to deploy the datasource The deployer will report a ClassNotFound exception saying jdbc driver class is not found. Java EE user may confuse around here, since they know they've installed the jdbc libraries into the repository, but why encounter the CNF exception? From user-friendly aspect, G server is better to provide a way to transform traditional jar into a OSGi bundle transparently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5521) NoClassDefFoundError when deploying a datasource with non-OSGi jdbc lib dependencies
[ https://issues.apache.org/jira/browse/GERONIMO-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain reassigned GERONIMO-5521: - Assignee: Ashish Jain (was: Rex Wang) NoClassDefFoundError when deploying a datasource with non-OSGi jdbc lib dependencies Key: GERONIMO-5521 URL: https://issues.apache.org/jira/browse/GERONIMO-5521 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 3.0 Environment: ubuntu 8.04 x86-32 sun java 1.6.0_20 Reporter: Forrest Xia Assignee: Ashish Jain Steps: 1. start geronimo tomcat we profile assembly 2. install jdbc library via deploy install-library command. The jdbc libraries are not bundlized yet 3. define a datasource deployment plan with dependencies on the jdbc libraries 4. deploy the datasource via proper tranql adapter An exception throws like this: 2010-08-11 09:02:59,585 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.samples.daytrader.plugins/daytrader-db2-datasource/3.0-M1/car?J2EEApplication=null,JCAConnectionFactory=jdbc/TradeDataSource,JCAResource=tranql-connector-db2-xa-1.5,ResourceAdapter=tranql-connector-db2-xa-1.5,ResourceAdapterModule=org.apache.geronimo.samples.daytrader.plugins/daytrader-db2-datasource/3.0-M1/car,j2eeType=JCAManagedConnectionFactory,name=jdbc/TradeDataSource java.lang.NoClassDefFoundError: com.ibm.db2.jcc.DB2XADataSource at org.tranql.connector.db2.XAMCF.init(XAMCF.java:51) at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1325) at org.apache.geronimo.connector.wrapper.outbound.ManagedConnectionFactoryWrapper.init(ManagedConnectionFactoryWrapper.java:115) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:44) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) at java.lang.reflect.Constructor.newInstance(Constructor.java:516) at org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:952) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:933) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:560) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:460) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:224) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:698) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:677) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at
[jira] Created: (GERONIMO-5734) Enable sharelib in osgi based geronimo
Enable sharelib in osgi based geronimo --- Key: GERONIMO-5734 URL: https://issues.apache.org/jira/browse/GERONIMO-5734 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0 Environment: geronimo 3.0 Reporter: Ashish Jain Assignee: Ashish Jain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (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:all-tabpanel ] Ashish Jain closed GERONIMO-5692. - Resolution: Fixed Fix Version/s: (was: 2.2.2) (was: 3.0) Thank you Ashok and Forrest for your test results. I will open a new track for 2.2 and 3.0. 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 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] Created: (GERONIMO-5708) Track: Unlock keystore command line utility does not work with Configured Encryption
Track: Unlock keystore command line utility does not work with Configured Encryption - Key: GERONIMO-5708 URL: https://issues.apache.org/jira/browse/GERONIMO-5708 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-5692 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] Updated: (GERONIMO-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5683: -- Affects Version/s: (was: 3.0-M1) (was: 2.2.1) Fix Version/s: (was: 2.2.2) (was: 3.0) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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=12933782#action_12933782 ] Ashish Jain commented on GERONIMO-5692: --- GERONIMO-5708 is the new track for 2.2. and 3.0. 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 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] Created: (GERONIMO-5709) Track: Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
Track: Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache - Key: GERONIMO-5709 URL: https://issues.apache.org/jira/browse/GERONIMO-5709 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-5683 in 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-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5683. - Resolution: Fixed Opening a separate track Geronimo- 5709 for g 2.2 and g 3.0. Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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: -- Affects Version/s: (was: 2.1.6) Fix Version/s: (was: 2.1.7) 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 Environment: geronimo tomcat assembly 2.1.6 Reporter: Ashish Jain Assignee: Ashish Jain 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-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.
[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] 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] 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.
[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.
[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=12932924#action_12932924 ] Ashish Jain commented on GERONIMO-5690: --- applied to 2.1 branch @revision 1035997. For 2.2.2 and 3.0 I will open a separate track. 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-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:comment-tabpanelfocusedCommentId=12932927#action_12932927 ] Ashish Jain commented on GERONIMO-5691: --- Applied to 2.1 @revision 1035998 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, 2.2.2, 3.0 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] Commented: (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:comment-tabpanelfocusedCommentId=12932928#action_12932928 ] Ashish Jain commented on GERONIMO-5691: --- I will open a separate track for 2.2 and 3.0 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, 2.2.2, 3.0 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] 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=12932929#action_12932929 ] Ashish Jain commented on GERONIMO-5692: --- Fix applied At revision: 1036002 to 2.1 branch. I will open a separate track for 2.2 and 3.0. 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-5693) Encryption logic for connectionPassword attribute in ldap realm
[ https://issues.apache.org/jira/browse/GERONIMO-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932930#action_12932930 ] Ashish Jain commented on GERONIMO-5693: --- Completed: At revision: 1036008 to 2.1 branch. 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, 2.2.2, 3.0 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] Commented: (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:comment-tabpanelfocusedCommentId=12932931#action_12932931 ] Ashish Jain commented on GERONIMO-5693: --- I will open a separate track for 2.2 and 3.0. 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, 2.2.2, 3.0 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] Closed: (GERONIMO-5694) Upgrade active mq version to 5.3
[ https://issues.apache.org/jira/browse/GERONIMO-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5694. - Resolution: Invalid Such an aggresive upgrade is not acceptable. Upgrade active mq version to 5.3 Key: GERONIMO-5694 URL: https://issues.apache.org/jira/browse/GERONIMO-5694 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 217 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. All these have been fixed in Active Mq v5.2 and 5.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5694) Upgrade active mq version to 5.3
[ https://issues.apache.org/jira/browse/GERONIMO-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932933#action_12932933 ] Ashish Jain commented on GERONIMO-5694: --- These patches will be applied to current used version of active MQ in g 2.1 which is 4.1.2. I will open a new track for this. Upgrade active mq version to 5.3 Key: GERONIMO-5694 URL: https://issues.apache.org/jira/browse/GERONIMO-5694 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 217 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. All these have been fixed in Active Mq v5.2 and 5.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5695) Upgrade wadi to 2.1.2
[ https://issues.apache.org/jira/browse/GERONIMO-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5695. - Resolution: Fixed 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] 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=12932940#action_12932940 ] Ashish Jain commented on GERONIMO-5695: --- Applied to 2.1 At revision: 1036023 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] Commented: (GERONIMO-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932942#action_12932942 ] Ashish Jain commented on GERONIMO-5683: --- Applied to 2.1 branch At revision: 1036024. Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6, 2.2.1, 3.0-M1 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
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 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-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932397#action_12932397 ] Ashish Jain commented on GERONIMO-5683: --- Thank you Jarek/Kevan. I will revert back the changes and will instead make the init method synchronized. Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6, 2.2.1, 3.0-M1 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932009#action_12932009 ] Ashish Jain commented on GERONIMO-5683: --- Applied to 2.1 At revision: 1035171 Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6, 2.2.1, 3.0-M1 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5690) Clustering module fails to start on disabling JMXService gbean
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] Created: (GERONIMO-5691) Farming module provision of utilizing encrypted password instead of plain text
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, 2.2.2, 3.0 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] Created: (GERONIMO-5692) Unlock keystore command line utility does not work with Configured Encryption
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] Created: (GERONIMO-5693) Encryption logic for connectionPassword attribute in ldap realm
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, 2.2.2, 3.0 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-5694) Upgrade active mq version to 5.3
Upgrade active mq version to 5.3 Key: GERONIMO-5694 URL: https://issues.apache.org/jira/browse/GERONIMO-5694 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.1.6 Environment: Geronimo tomcat assembly 217 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and AMQ-1760. All these have been fixed in Active Mq v5.2 and 5.3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5695) Upgrade wadi to 2.1.2
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-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.6, 2.2.1, 3.0-M1 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5683) Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain reassigned GERONIMO-5683: - Assignee: Ashish Jain Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache --- Key: GERONIMO-5683 URL: https://issues.apache.org/jira/browse/GERONIMO-5683 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.6, 2.2.1, 3.0-M1 Environment: geronimo tomcat assembly 2.1.7 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 The following error is encountered under heavy load when there are multiple threads accessing GeronimoTldLocationsCache.scanJars. java.lang.ArrayIndexOutOfBoundsException at java.util.ArrayList.ensureCapacity(ArrayList.java:196) at java.util.ArrayList.add(ArrayList.java:377) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:479) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.scanJars (GeronimoTldLocationsCache.java:457) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.init (GeronimoTldLocationsCache.java:218) at org.apache.geronimo.jasper.GeronimoTldLocationsCache.getLocation (GeronimoTldLocationsCache.java:209) at org.apache.jasper.JspCompilationContext.getTldLocation (JspCompilationContext.java:550) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java: 430) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5196) Add a own authenticator for Spnego login
[ https://issues.apache.org/jira/browse/GERONIMO-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5196. - Resolution: Fixed Fixed in 2.1. GERONIMO-5651 opened for 3.0 and 2.2. Add a own authenticator for Spnego login Key: GERONIMO-5196 URL: https://issues.apache.org/jira/browse/GERONIMO-5196 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 It should be possible to use a custom authenticator for Spnego login. This includes the ability to have a different authentication method for web.xml. This is an improvement over GERONIMO-5129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5652) Generic Header based authentication support in geronimo 2.2 and 3.0
Generic Header based authentication support in geronimo 2.2 and 3.0 --- Key: GERONIMO-5652 URL: https://issues.apache.org/jira/browse/GERONIMO-5652 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Affects Versions: 2.2.1, 3.0 Reporter: Ashish Jain Assignee: Ashish Jain Continuation of GERONIMO-5197 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-5197) Generic Header based authentication support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5197. - Resolution: Fixed Fixed in 2.1. GERONIMO-5652 opened for 2.2 and 3.0. Generic Header based authentication support in geronimo --- Key: GERONIMO-5197 URL: https://issues.apache.org/jira/browse/GERONIMO-5197 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 Geronimo should provide a generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5305) DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender
[ https://issues.apache.org/jira/browse/GERONIMO-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888726#action_12888726 ] Ashish Jain commented on GERONIMO-5305: --- Applied to 2.1 branch @ revision 964318. Thanks for the patch Amit Puri. DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender -- Key: GERONIMO-5305 URL: https://issues.apache.org/jira/browse/GERONIMO-5305 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.1, 2.1.5, 2.2 Reporter: Amit Puri Fix For: 2.1.7 Attachments: GERONIMO-5305.patch When we use DisableMcastInterceptor GBean, it only disables the mcast sender but not the receiver. Thats why, In the case of Unicast clustering configuration, when we specified the DisableMcastInterceptor GBean in plan to disable the multicast, we can still see multicast socket. I am adding code to disable mcast receiver also in DisableMcastInterceptor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5305) DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender
[ https://issues.apache.org/jira/browse/GERONIMO-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888731#action_12888731 ] Ashish Jain commented on GERONIMO-5305: --- Applied to 2.2 branch @ revision 964322. Thanks for the patch Amit Puri. DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender -- Key: GERONIMO-5305 URL: https://issues.apache.org/jira/browse/GERONIMO-5305 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.1, 2.1.5, 2.2 Reporter: Amit Puri Fix For: 2.1.7 Attachments: GERONIMO-5305.patch When we use DisableMcastInterceptor GBean, it only disables the mcast sender but not the receiver. Thats why, In the case of Unicast clustering configuration, when we specified the DisableMcastInterceptor GBean in plan to disable the multicast, we can still see multicast socket. I am adding code to disable mcast receiver also in DisableMcastInterceptor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5305) DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender
[ https://issues.apache.org/jira/browse/GERONIMO-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888732#action_12888732 ] Ashish Jain commented on GERONIMO-5305: --- Applied to trunk @ revision 964332. Thanks for the patch Amit Puri. DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender -- Key: GERONIMO-5305 URL: https://issues.apache.org/jira/browse/GERONIMO-5305 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.1, 2.1.5, 2.2 Reporter: Amit Puri Fix For: 2.1.7, 2.2.2, 3.0-M1 Attachments: GERONIMO-5305.patch When we use DisableMcastInterceptor GBean, it only disables the mcast sender but not the receiver. Thats why, In the case of Unicast clustering configuration, when we specified the DisableMcastInterceptor GBean in plan to disable the multicast, we can still see multicast socket. I am adding code to disable mcast receiver also in DisableMcastInterceptor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5305) DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender
[ https://issues.apache.org/jira/browse/GERONIMO-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5305: -- Fix Version/s: 2.2.2 3.0-M1 DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender -- Key: GERONIMO-5305 URL: https://issues.apache.org/jira/browse/GERONIMO-5305 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.1, 2.1.5, 2.2 Reporter: Amit Puri Fix For: 2.1.7, 2.2.2, 3.0-M1 Attachments: GERONIMO-5305.patch When we use DisableMcastInterceptor GBean, it only disables the mcast sender but not the receiver. Thats why, In the case of Unicast clustering configuration, when we specified the DisableMcastInterceptor GBean in plan to disable the multicast, we can still see multicast socket. I am adding code to disable mcast receiver also in DisableMcastInterceptor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5305) DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender
[ https://issues.apache.org/jira/browse/GERONIMO-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5305. - Resolution: Fixed Fixed in 2.1, 2.2 and trunk. DisableMcastInterceptor GBean should disable the mcast receiver also with mcast sender -- Key: GERONIMO-5305 URL: https://issues.apache.org/jira/browse/GERONIMO-5305 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.1, 2.1.5, 2.2 Reporter: Amit Puri Fix For: 2.1.7, 2.2.2, 3.0-M1 Attachments: GERONIMO-5305.patch When we use DisableMcastInterceptor GBean, it only disables the mcast sender but not the receiver. Thats why, In the case of Unicast clustering configuration, when we specified the DisableMcastInterceptor GBean in plan to disable the multicast, we can still see multicast socket. I am adding code to disable mcast receiver also in DisableMcastInterceptor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5431) Web Connector portlet does not persist values
[ https://issues.apache.org/jira/browse/GERONIMO-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885879#action_12885879 ] Ashish Jain commented on GERONIMO-5431: --- Applied to 2.1 branch @revision 961301 Web Connector portlet does not persist values - Key: GERONIMO-5431 URL: https://issues.apache.org/jira/browse/GERONIMO-5431 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.7 Environment: Geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain In WebConnector portlet values are not persisting after modifications. Couple of test cases. 1) In websslconnector try setting the values for truststorePass, truststoreFile as null. Portlet does not persist the values and values are never modfied. 2) Modify WebConnector for example threadPriority. Portlet still shows the same value. However I see websslconnector being modified. As of now I am investigating this on 2.1...I will update the JIRA for 2.2/3.0 later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5431) Web Connector portlet does not persist values
[ https://issues.apache.org/jira/browse/GERONIMO-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain reassigned GERONIMO-5431: - Assignee: Ashish Jain Web Connector portlet does not persist values - Key: GERONIMO-5431 URL: https://issues.apache.org/jira/browse/GERONIMO-5431 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.7 Environment: Geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain In WebConnector portlet values are not persisting after modifications. Couple of test cases. 1) In websslconnector try setting the values for truststorePass, truststoreFile as null. Portlet does not persist the values and values are never modfied. 2) Modify WebConnector for example threadPriority. Portlet still shows the same value. However I see websslconnector being modified. As of now I am investigating this on 2.1...I will update the JIRA for 2.2/3.0 later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5431) Web Connector portlet does not persist values
Web Connector portlet does not persist values - Key: GERONIMO-5431 URL: https://issues.apache.org/jira/browse/GERONIMO-5431 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.7 Environment: Geronimo tomcat assembly Reporter: Ashish Jain In WebConnector portlet values are not persisting after modifications. Couple of test cases. 1) In websslconnector try setting the values for truststorePass, truststoreFile as null. Portlet does not persist the values and values are never modfied. 2) Modify WebConnector for example threadPriority. Portlet still shows the same value. However I see websslconnector being modified. As of now I am investigating this on 2.1...I will update the JIRA for 2.2/3.0 later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
Encrypt password values in server.xml for geronimo 2.2 onwards -- Key: GERONIMO-5432 URL: https://issues.apache.org/jira/browse/GERONIMO-5432 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.2 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0-M1 Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5424) Encrypt truststore pass for tomcat web ssl connector
Encrypt truststore pass for tomcat web ssl connector Key: GERONIMO-5424 URL: https://issues.apache.org/jira/browse/GERONIMO-5424 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 In config.xml truststore password is listed 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] Commented: (GERONIMO-5424) Encrypt truststore pass for tomcat web ssl connector
[ https://issues.apache.org/jira/browse/GERONIMO-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12884629#action_12884629 ] Ashish Jain commented on GERONIMO-5424: --- Applied to 21 branch @ rev 959940 Encrypt truststore pass for tomcat web ssl connector Key: GERONIMO-5424 URL: https://issues.apache.org/jira/browse/GERONIMO-5424 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 In config.xml truststore password is listed 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] Updated: (GERONIMO-5197) Generic Header based authentication support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5197: -- Fix Version/s: 2.1.7 (was: Wish List) Generic Header based authentication support in geronimo --- Key: GERONIMO-5197 URL: https://issues.apache.org/jira/browse/GERONIMO-5197 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 Geronimo should provide a generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5196) Add a own authenticator for Spnego login
[ https://issues.apache.org/jira/browse/GERONIMO-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5196: -- Fix Version/s: 2.1.7 (was: Wish List) Add a own authenticator for Spnego login Key: GERONIMO-5196 URL: https://issues.apache.org/jira/browse/GERONIMO-5196 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7, 2.2.2, 3.0 It should be possible to use a custom authenticator for Spnego login. This includes the ability to have a different authentication method for web.xml. This is an improvement over GERONIMO-5129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5401) Geronimo encrypts empty passwords
Geronimo encrypts empty passwords
-
Key: GERONIMO-5401
URL: https://issues.apache.org/jira/browse/GERONIMO-5401
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: databases
Affects Versions: 2.1.5
Environment: Geronimo tomcat assembly.
Reporter: Ashish Jain
Assignee: Ashish Jain
Fix For: 2.1.7
This can be observed as follows
1) Create a test db pool with empty passwords. I had used derby embedded xa.
2) Deploy it.
3) Check the config.ser. You can see a password string encrypted with {Simple}
or {Configured}.
The same behavior can be seen for SystemDatasource.
This behavior is misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5401) Geronimo encrypts empty passwords
[
https://issues.apache.org/jira/browse/GERONIMO-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882102#action_12882102
]
Ashish Jain commented on GERONIMO-5401:
---
applied to 2.1 branch At revision: 957469
Geronimo encrypts empty passwords
-
Key: GERONIMO-5401
URL: https://issues.apache.org/jira/browse/GERONIMO-5401
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: databases
Affects Versions: 2.1.5
Environment: Geronimo tomcat assembly.
Reporter: Ashish Jain
Assignee: Ashish Jain
Fix For: 2.1.7
This can be observed as follows
1) Create a test db pool with empty passwords. I had used derby embedded xa.
2) Deploy it.
3) Check the config.ser. You can see a password string encrypted with
{Simple} or {Configured}.
The same behavior can be seen for SystemDatasource.
This behavior is misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5402) Incorrect instructions to utilize ConfiguredEncryption
Incorrect instructions to utilize ConfiguredEncryption --- Key: GERONIMO-5402 URL: https://issues.apache.org/jira/browse/GERONIMO-5402 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.1.5 Environment: geronimo tomcat assembly. Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html and doc reference for org.apache.geronimo.system.util.ConfiguredEncryption are incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5402) Incorrect instructions to utilize ConfiguredEncryption
[ https://issues.apache.org/jira/browse/GERONIMO-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882105#action_12882105 ] Ashish Jain commented on GERONIMO-5402: --- Applied to 2.1 branch At revision: 957476 Incorrect instructions to utilize ConfiguredEncryption --- Key: GERONIMO-5402 URL: https://issues.apache.org/jira/browse/GERONIMO-5402 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.5 Environment: geronimo tomcat assembly. Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html and doc reference for org.apache.geronimo.system.util.ConfiguredEncryption are incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5402) Incorrect instructions to utilize ConfiguredEncryption
[ https://issues.apache.org/jira/browse/GERONIMO-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882107#action_12882107 ] Ashish Jain commented on GERONIMO-5402: --- Modified the doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html. Incorrect instructions to utilize ConfiguredEncryption --- Key: GERONIMO-5402 URL: https://issues.apache.org/jira/browse/GERONIMO-5402 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.5 Environment: geronimo tomcat assembly. Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html and doc reference for org.apache.geronimo.system.util.ConfiguredEncryption are incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5402) Incorrect instructions to utilize ConfiguredEncryption
[ https://issues.apache.org/jira/browse/GERONIMO-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882126#action_12882126 ] Ashish Jain commented on GERONIMO-5402: --- Updated other docs https://cwiki.apache.org/GMOxDOC22/basic-hints-on-security-configuration.html https://cwiki.apache.org/GMOxDOC21/basic-hints-on-security-configuration.html https://cwiki.apache.org/GMOxDOC30/obscuring-passwords.html Incorrect instructions to utilize ConfiguredEncryption --- Key: GERONIMO-5402 URL: https://issues.apache.org/jira/browse/GERONIMO-5402 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.5 Environment: geronimo tomcat assembly. Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.7 https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html and doc reference for org.apache.geronimo.system.util.ConfiguredEncryption are incorrect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5378) Upgrade CXF version to 2.0.13
Upgrade CXF version to 2.0.13 -- Key: GERONIMO-5378 URL: https://issues.apache.org/jira/browse/GERONIMO-5378 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Priority: Trivial Fix For: 2.1.6 CXF community has recently released CXF 2.0.13.Upgrade the g 2.1 branch to cxf 2.0.13. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5378) Upgrade CXF version to 2.0.13
[ https://issues.apache.org/jira/browse/GERONIMO-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5378. - Resolution: Fixed Applied @rev 953246. Closing it. Upgrade CXF version to 2.0.13 -- Key: GERONIMO-5378 URL: https://issues.apache.org/jira/browse/GERONIMO-5378 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Priority: Trivial Fix For: 2.1.6 CXF community has recently released CXF 2.0.13.Upgrade the g 2.1 branch to cxf 2.0.13. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5379) Update geronimo custom Axis2 build for Axis2-4450
Update geronimo custom Axis2 build for Axis2-4450 - Key: GERONIMO-5379 URL: https://issues.apache.org/jira/browse/GERONIMO-5379 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Priority: Trivial Fix For: 2.1.6 Apply the fixes of AXIS2-4450 to geronimo custom AXIS2 for 2.1 branch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5379) Update geronimo custom Axis2 build for Axis2-4450
[ https://issues.apache.org/jira/browse/GERONIMO-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5379. - Resolution: Fixed Applied @ rev 953250. Closing it. Update geronimo custom Axis2 build for Axis2-4450 - Key: GERONIMO-5379 URL: https://issues.apache.org/jira/browse/GERONIMO-5379 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Priority: Trivial Fix For: 2.1.6 Apply the fixes of AXIS2-4450 to geronimo custom AXIS2 for 2.1 branch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5129) Fix to be picked from tomcat for Spnego support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5129. - Resolution: Fixed This is no longer required as we are going to have our own authenticators. Fix to be picked from tomcat for Spnego support in geronimo --- Key: GERONIMO-5129 URL: https://issues.apache.org/jira/browse/GERONIMO-5129 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Tomcat Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, Wish List -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5295) Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool
[ https://issues.apache.org/jira/browse/GERONIMO-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866084#action_12866084 ] Ashish Jain commented on GERONIMO-5295: --- Applied to trunk At revision: 943029. Closing it. Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool --- Key: GERONIMO-5295 URL: https://issues.apache.org/jira/browse/GERONIMO-5295 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Shawn Jiang Assignee: Ashish Jain Fix For: 3.0 This is opened to continue track https://issues.apache.org/jira/browse/GERONIMO-5180 in geronimo 3.x. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5295) Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool
[ https://issues.apache.org/jira/browse/GERONIMO-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5295. - Resolution: Fixed Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool --- Key: GERONIMO-5295 URL: https://issues.apache.org/jira/browse/GERONIMO-5295 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Shawn Jiang Assignee: Ashish Jain Fix For: 3.0 This is opened to continue track https://issues.apache.org/jira/browse/GERONIMO-5180 in geronimo 3.x. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5294) Remove the dependency of clustering over JMXConnector for 3.x
[ https://issues.apache.org/jira/browse/GERONIMO-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866092#action_12866092 ] Ashish Jain commented on GERONIMO-5294: --- Applied to trunk At revision: 943045 Remove the dependency of clustering over JMXConnector for 3.x - Key: GERONIMO-5294 URL: https://issues.apache.org/jira/browse/GERONIMO-5294 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Shawn Jiang Assignee: Ashish Jain Fix For: 3.0 This is opened to continue track https://issues.apache.org/jira/browse/GERONIMO-5148 in geronimo 3.x. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5294) Remove the dependency of clustering over JMXConnector for 3.x
[ https://issues.apache.org/jira/browse/GERONIMO-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5294. - Resolution: Fixed Closing it. Remove the dependency of clustering over JMXConnector for 3.x - Key: GERONIMO-5294 URL: https://issues.apache.org/jira/browse/GERONIMO-5294 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Shawn Jiang Assignee: Ashish Jain Fix For: 3.0 This is opened to continue track https://issues.apache.org/jira/browse/GERONIMO-5148 in geronimo 3.x. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-4795. - Resolution: Won't Fix Closing it. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: Wish List Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5180) Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool
[ https://issues.apache.org/jira/browse/GERONIMO-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861310#action_12861310 ] Ashish Jain commented on GERONIMO-5180: --- Applied to 2.2 branch @ revision: 938356 Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool --- Key: GERONIMO-5180 URL: https://issues.apache.org/jira/browse/GERONIMO-5180 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.5, 2.2.1, 3.0 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Here are the steps to recreate this issue: 1) Create a keystore using keytool.exe available in JAVA_HOME/bin. 2) Now use the command deploy unlockKeystore Keystore_Name An exception is thrown suggesting keystore does not exist. To overcome this exception access the admin console keystore portlet, this operation will add the newly created keystore as a gbean into geronimo. Now try #2 unlock will be successful. To fix this issue up there are 2 possibilities on which I will put up a discussion on dev list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5148) Remove the dependency of clustering over JMXConnector
[ https://issues.apache.org/jira/browse/GERONIMO-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861312#action_12861312 ] Ashish Jain commented on GERONIMO-5148: --- Applied to 2.2 @revision 938358. Remove the dependency of clustering over JMXConnector - Key: GERONIMO-5148 URL: https://issues.apache.org/jira/browse/GERONIMO-5148 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5148.patch, 5148_updated_21.patch, JavaAgent.jar It should be possible to make use of JMXSecureConnector for clustering. Currently if we use JMXSecureConnector than we have to disable the clustering modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4892) Farm Deployment Error if deploy more than one applications
[
https://issues.apache.org/jira/browse/GERONIMO-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Jain closed GERONIMO-4892.
-
Resolution: Fixed
Farm Deployment Error if deploy more than one applications
--
Key: GERONIMO-4892
URL: https://issues.apache.org/jira/browse/GERONIMO-4892
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands
Affects Versions: 2.1.4, 2.2
Environment: oS: winxp and win2003
Reporter: viola.lu
Assignee: Ashish Jain
Fix For: 2.2.1
Attachments: 4892.patch, GERONIMO-4892_updated.patch, LOGS_4892.rar,
TwoFarm.zip
Win2003 as master node( NODE2) with config.xml
...
module name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car
gbean
name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node1
gbeanInfo=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=nameNODE1/attribute
attribute
propertyEditor=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor
name=extendedJMXConnectorInfo
ns:javabean
class=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo
xmlns= xmlns:ns10=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
xmlns:ns12=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns14=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns8_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns4=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns8=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns14_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns12_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns10_=http://geronimo.apache.org/xml/ns/attributes-1.2;
ns:property name=usernamesystem/ns:property
ns:property name=passwordmanager/ns:property
ns:property name=protocolrmi/ns:property
ns:property name=host9.186.10.167/ns:property
ns:property name=port1099/ns:property
ns:property name=urlPathJMXConnector/ns:property
ns:property name=localfalse/ns:property
/ns:javabean
/attribute
/gbean
gbean name=NodeInfo
attribute name=name${ClusterNodeName}/attribute
/gbean
gbean name=ClusterInfo
attribute name=name${FarmName}/attribute
/gbean
/module
...
WinXP as node 1
WinXp. as node 1
..
module name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car
gbean
name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node2
gbeanInfo=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=nameNODE2/attribute
attribute
propertyEditor=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor
name=extendedJMXConnectorInfo
ns:javabean
class=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo
xmlns= xmlns:ns20=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns10=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns22=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
xmlns:ns12=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns14=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns18=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns19=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns4=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns7=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns8=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns18_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns9=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns16_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns14_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns12_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns22_=http://geronimo.apache.org/xml/ns/attributes-1.2;
ns:property name=usernamesystem/ns:property
ns:property
[jira] Commented: (GERONIMO-4892) Farm Deployment Error if deploy more than one applications
[
https://issues.apache.org/jira/browse/GERONIMO-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12860909#action_12860909
]
Ashish Jain commented on GERONIMO-4892:
---
Applied @rev 938021 to 2.2 branch.
Farm Deployment Error if deploy more than one applications
--
Key: GERONIMO-4892
URL: https://issues.apache.org/jira/browse/GERONIMO-4892
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands
Affects Versions: 2.1.4, 2.2
Environment: oS: winxp and win2003
Reporter: viola.lu
Assignee: Ashish Jain
Fix For: 2.2.1
Attachments: 4892.patch, GERONIMO-4892_updated.patch, LOGS_4892.rar,
TwoFarm.zip
Win2003 as master node( NODE2) with config.xml
...
module name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car
gbean
name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node1
gbeanInfo=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=nameNODE1/attribute
attribute
propertyEditor=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor
name=extendedJMXConnectorInfo
ns:javabean
class=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo
xmlns= xmlns:ns10=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
xmlns:ns12=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns14=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns8_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns4=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns8=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns14_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns12_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns10_=http://geronimo.apache.org/xml/ns/attributes-1.2;
ns:property name=usernamesystem/ns:property
ns:property name=passwordmanager/ns:property
ns:property name=protocolrmi/ns:property
ns:property name=host9.186.10.167/ns:property
ns:property name=port1099/ns:property
ns:property name=urlPathJMXConnector/ns:property
ns:property name=localfalse/ns:property
/ns:javabean
/attribute
/gbean
gbean name=NodeInfo
attribute name=name${ClusterNodeName}/attribute
/gbean
gbean name=ClusterInfo
attribute name=name${FarmName}/attribute
/gbean
/module
...
WinXP as node 1
WinXp. as node 1
..
module name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car
gbean
name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node2
gbeanInfo=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=nameNODE2/attribute
attribute
propertyEditor=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor
name=extendedJMXConnectorInfo
ns:javabean
class=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo
xmlns= xmlns:ns20=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns10=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns22=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
xmlns:ns12=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns14=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns18=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns19=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns4=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns7=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns8=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns18_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns9=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns16_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns14_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns12_=http://geronimo.apache.org/xml/ns/attributes-1.2;
[jira] Created: (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
Modify the redeploy behavior to start all the running childs along with the parent -- Key: GERONIMO-5265 URL: https://issues.apache.org/jira/browse/GERONIMO-5265 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment Affects Versions: 2.1.5, 2.2.1, 3.0 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.1, 3.0 Kindly refer the discussion thread http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
[ https://issues.apache.org/jira/browse/GERONIMO-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5265: -- Attachment: 5265_21.patch Modify the redeploy behavior to start all the running childs along with the parent -- Key: GERONIMO-5265 URL: https://issues.apache.org/jira/browse/GERONIMO-5265 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1.5, 2.2.1, 3.0 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.1, 3.0 Attachments: 5265_21.patch Kindly refer the discussion thread http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5209) Geronimo support for tranql XA JDBC adapter for DB2 on ISeries
Geronimo support for tranql XA JDBC adapter for DB2 on ISeries -- Key: GERONIMO-5209 URL: https://issues.apache.org/jira/browse/GERONIMO-5209 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: connector Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.1, 3.0 Geronimo should provide a way to connect to DB2 on ISeries using the JTOpen drivers. For more information on JTOpen refer http://jt400.sourceforge.net/. Currently the generic traql jdbc adapter can be utilized but only for non XA transaction support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5209) Geronimo support for tranql XA JDBC adapter for DB2 on ISeries
[ https://issues.apache.org/jira/browse/GERONIMO-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850863#action_12850863 ] Ashish Jain commented on GERONIMO-5209: --- Tranql JIRA link http://jira.codehaus.org/browse/TQL-22. Geronimo support for tranql XA JDBC adapter for DB2 on ISeries -- Key: GERONIMO-5209 URL: https://issues.apache.org/jira/browse/GERONIMO-5209 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: connector Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.1, 3.0 Geronimo should provide a way to connect to DB2 on ISeries using the JTOpen drivers. For more information on JTOpen refer http://jt400.sourceforge.net/. Currently the generic traql jdbc adapter can be utilized but only for non XA transaction support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5180) Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool
[ https://issues.apache.org/jira/browse/GERONIMO-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848727#action_12848727 ] Ashish Jain commented on GERONIMO-5180: --- Applied to 2.1 branch At revision: 926589. Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool --- Key: GERONIMO-5180 URL: https://issues.apache.org/jira/browse/GERONIMO-5180 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.5, 2.2.1, 3.0 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Here are the steps to recreate this issue: 1) Create a keystore using keytool.exe available in JAVA_HOME/bin. 2) Now use the command deploy unlockKeystore Keystore_Name An exception is thrown suggesting keystore does not exist. To overcome this exception access the admin console keystore portlet, this operation will add the newly created keystore as a gbean into geronimo. Now try #2 unlock will be successful. To fix this issue up there are 2 possibilities on which I will put up a discussion on dev list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5196) Add a own authenticator for Spnego login
Add a own authenticator for Spnego login Key: GERONIMO-5196 URL: https://issues.apache.org/jira/browse/GERONIMO-5196 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 It should be possible to use a custom authenticator for Spnego login. This includes the ability to have a different authentication method for web.xml. This is an improvement over GERONIMO-5129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5197) Generic Header based authentication support in geronimo
Generic Header based authentication support in geronimo --- Key: GERONIMO-5197 URL: https://issues.apache.org/jira/browse/GERONIMO-5197 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Geronimo should provide a generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5196) Add a own authenticator for Spnego login
[ https://issues.apache.org/jira/browse/GERONIMO-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848075#action_12848075 ] Ashish Jain commented on GERONIMO-5196: --- New code is available @ https://issues.apache.org/bugzilla/show_bug.cgi?id=48685 . Details on the attachment Updated version of the patch against Tomcat 6.0.26 . Using this code users can specify SPNEGO as the auth-method in web.xml. Add a own authenticator for Spnego login Key: GERONIMO-5196 URL: https://issues.apache.org/jira/browse/GERONIMO-5196 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 It should be possible to use a custom authenticator for Spnego login. This includes the ability to have a different authentication method for web.xml. This is an improvement over GERONIMO-5129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5199) GShell equivalent for server startup with secure option, command unlock keystore and command redeploy for farming
GShell equivalent for server startup with secure option, command unlock keystore and command redeploy for farming - Key: GERONIMO-5199 URL: https://issues.apache.org/jira/browse/GERONIMO-5199 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Gshell equivalents for server startup with secure option, command unlock keystore and command redeploy for farming are required. Refer GERONIMO-5027, GERONIMO-5148 and GERONIMO-5156. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Fix Version/s: (was: 2.1.5) Wish List Moving to wish list as no action is required for g 2.1.5 release. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: Wish List Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5027) Redeploy option for farming
[ https://issues.apache.org/jira/browse/GERONIMO-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846827#action_12846827 ] Ashish Jain commented on GERONIMO-5027: --- Thanks Shawn I will open a new JIRA for GShell equivalence. Redeploy option for farming --- Key: GERONIMO-5027 URL: https://issues.apache.org/jira/browse/GERONIMO-5027 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.1.4, 2.2 Environment: Windows XP g214 Reporter: Ashish Jain Assignee: Shawn Jiang Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5027_21.patch, 5027_21_updated.patch Redeploy feature for farming. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5129) Fix to be picked from tomcat for Spnego support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846828#action_12846828 ] Ashish Jain commented on GERONIMO-5129: --- Ivan, For the newer releases I will incorporate the changes as suggested. David, I will add this to my work list to research on open source jaspic spnego module. I will close this JIRA now and will open new one for further improvements on spnego infrastructure. Fix to be picked from tomcat for Spnego support in geronimo --- Key: GERONIMO-5129 URL: https://issues.apache.org/jira/browse/GERONIMO-5129 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Tomcat Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5129) Fix to be picked from tomcat for Spnego support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5129. - Resolution: Fixed Fix to be picked from tomcat for Spnego support in geronimo --- Key: GERONIMO-5129 URL: https://issues.apache.org/jira/browse/GERONIMO-5129 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Tomcat Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5130) Documentation for using Spnego with geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5130. - Resolution: Fixed Modified the document to incorporate the changes as per GERONIMO-5131. Closing it off. Documentation for using Spnego with geronimo Key: GERONIMO-5130 URL: https://issues.apache.org/jira/browse/GERONIMO-5130 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: documentation Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
