Re: exposing exceptions that caused a rollback
Hi Djencks/Dblevins,
As we had discussed earlier about this issue and the possible patch. It
seems we cannot use javax.transaction.
TransactionRolledbackException.initCause(e) instead there is another class
with in openEJB
org.apache.openejb.core.transaction.TransactionRolledbackException which can
be utilized. So can we go ahead
and use this exception class. Are there any reasons why we had not used this
class earlier?
For your reference
have a look at line no 146 in the class
https://svn.apache.org/repos/asf/openejb/tags/openejb-3.0.3/container/openejb-core/src/main/java/org/apache/openejb/core/transaction/TransactionPolicy.java
Once I use this class I see better logging however it stills seems
incomplete. What can we do to get more logging in this case?
Snippets of log from my eclipse when I run the client
Caused by: java.lang.Exception: Transaction has timed out
at
org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:261)
... 18 more
Snippets of log from my geronimo.log
2011-02-24 14:35:50,625 DEBUG [OpenEJB] finished invoking method create.
Return
value:proxy=com.test.ibm.TestTransactionInterface;deployment=test4/TestTransaction;pk=205efedb35aa1fff:ef95222:12e56ea419b:-7fe4
2011-02-24 14:35:50,640 DEBUG [jndi] JNDI REQUEST:
JNDI_LOOKUP:null:TestTransactionRemote -- RESPONSE:
JNDI_BUSINESS_OBJECT:STATEFUL:test4/TestTransaction:com.test.ibm.TestTransactionInterface:205efedb35aa1fff:ef95222:12e56ea419b:-7fe4
2011-02-24 14:35:50,718 INFO [Transaction] TX RequiresNew: Suspended
transaction null
2011-02-24 14:35:50,718 INFO [Transaction] TX RequiresNew: Started
transaction org.apache.geronimo.transaction.manager.TransactionImpl@f5472d
2011-02-24 14:35:50,750 INFO [Runtime] Starting OpenJPA 1.2.2
2011-02-24 14:35:50,843 INFO [JDBC] Using dictionary class
org.apache.openjpa.jdbc.sql.DerbyDictionary (Apache Derby 10.5.3.0 -
(802917) ,Apache Derby Embedded JDBC Driver 10.5.3.0 - (802917)).
2011-02-24 14:36:02,015 INFO [Transaction] TX RequiresNew: Committing
transaction org.apache.geronimo.transaction.manager.TransactionImpl@f5472d
2011-02-24 14:36:02,109 INFO [Transaction] The transaction has been rolled
back rather than commited: Unable to commit: transaction marked for rollback
2011-02-24 14:36:02,109 INFO [Transaction] TX RequiresNew: No transaction
to resume
2011-02-24 14:36:02,109 DEBUG [ejb] EJB REQUEST:
EJB_OBJECT.BUSINESS_METHOD:test4/TestTransaction:firstMethod:205efedb35aa1fff:ef95222:12e56ea419b:-7fe4
-- RESPONSE:
EJB_APP_EXCEPTION:org.apache.openejb.core.transaction.TransactionRolledbackException:
Transaction was rolled back, presumably because setRollbackOnly was called
during a synchronization: Unable to commit: transaction marked for rollback
Thanks
Ashish
On Thu, Feb 24, 2011 at 9:26 AM, David Jencks david_jen...@yahoo.comwrote:
On Feb 23, 2011, at 7:35 PM, Kevan Miller wrote:
On Feb 22, 2011, at 4:37 PM, David Jencks wrote:
cf
https://issues.apache.org/jira/browse/GERONIMO-4576
https://issues.apache.org/jira/browse/OPENEJB-1091
For a long time we've known of this problem where an exception thrown by
a transaction synchronization that causes a transaction to be marked for
rollback only is lost. When the user or openejb tries to commit the
transaction the transaction manager throws a RollbackException which
currently doesn't have any information about the original exception.
People have complained about this for a long time now we're trying
to fix it.
There are two parts AFAICT. I think in openejb we just need to take the
TransactionRolledBackException we are currently throwing and call initCause
with the RollbackException from the tm. In TransactionPolicy this would be
something like
} catch (RollbackException e) {
txLogger.info(The transaction has been rolled back rather
than commited: + e.getMessage());
// TODO can't set initCause on a
TransactionRolledbackException, update the convertException and related code
to handle something else
Throwable txe = new
javax.transaction.TransactionRolledbackException(Transaction was rolled
back, presumably because setRollbackOnly was called during a
synchronization: +e.getMessage());
--throw new ApplicationException(txe);
++throw new ApplicationException(txe.initCause(e);
In the transaction implementation we need to keep track of the exception
that caused us to mark rollback only and then use it as the cause of the
RollbackException, e.g.
private Exception markRollbackCause;
...
RollbackException rollbackException = new RollbackException(Unable to
commit: transaction marked for rollback);
if (markRollbackCause != null) {
rollbackException.initCause(markRollbackCause);
}
throw rollbackException;
...
private void markRollbackCause(Exception e) {
if (markRollbackCause == null) {
markRollbackCause = e;
}
}
Re: Configuring front end host for axis2 web services
Hi David, I am not sure if we can use the request object. The request (org.apache.geronimo.webservices.WebServiceContainer.Request) object gives you the address for the remote host which is the address for the proxy server, however no information on the port. Another way could have been to utilize the header request.getHeader(X-Forwarded-Host) but this is not a standard header AFAIK. So this option can also to be ruled out. So I think modifying the schema is the best way ahead. Thanks Ashish On Tue, Feb 8, 2011 at 6:34 PM, Ashish Jain ashja...@gmail.com wrote: Thanks David and Jarek. I am investigating on the comment made by David and seems to have found some headers which are being appended by HTTP server. I will investigate further in this direction to find out if the request object can be used to attain this. Thanks Ashish On Tue, Feb 8, 2011 at 1:06 AM, David Jencks david_jen...@yahoo.comwrote: Changing the schema like this shouldn't be a problem if its necessary. I'd like to understand better why its necessary. Perhaps there's another way. I thought that the way this was coded was that the host and port from the incoming request were stuffed into the wsdl being returned. Doesn't the proxy server tell us what the original request was in some way such as a request attribute? Could we look for that information and use it if available and use the request itself if not? thanks david jencks On Feb 7, 2011, at 10:39 AM, Jarek Gawor wrote: Ashish, Modifying the schema (without changing the namespace) is fine as long as you make the new element(s) optional. That at least is what we have done in the past. Jarek On Fri, Jan 28, 2011 at 10:00 AM, Ashish Jain ashja...@gmail.com wrote: Hi, When geronimo is front ended with a proxy say Apache HTTP server and a web service is invoked via this proxy. The auto generated wsdl will have the soap:address as http://g_host:g_port/service_name. Instead it should be http://proxy_host: proxy:port/service_name. The method which takes care of all this is org.apache.geronimo.axis2.WSDLQueryHandler.writeResponse . The baseUri attribute in the class has to be modified so that appropriate soap:address can be written in the wsdl file. So as to get this property into geronimo one of the way would be to be able to specify in geronimo deployment descriptor. Adding a new attribute may require schema change. Is this acceptable? Are there any other alternative ways through which this can be achieved? Thanks Ashish
Re: Configuring front end host for axis2 web services
Hi David, Your bit on configuring the header can be another way. We can use a standard header name for this for example FrontEnd-Proxy-HostPort or may be some other name. HTTP Server provides a directive where custom headers can be appended to the requests. http://httpd.apache.org/docs/current/mod/mod_headers.html#requestheader I am very much hopeful that other HTTP servers will also provide a way to configure custom headers. So this option is also very much acceptable. Thanks Ashish On Thu, Feb 10, 2011 at 10:44 PM, David Jencks david_jen...@yahoo.comwrote: Hi Ashish, I was certainly thinking of X-Forwarded-Host. I'm not clear on whether this header includes the original port. Google hasn't shown me much info on how other people deal with this problem. I did find http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypreservehost which appears to indicate you can configure apache httpd to not introduce this problem in the first place. I can see that directly configuring the host would be useful in some circumstances, but I think it would be easier in more circumstances to be able to configure the header name for the original host. So I guess you are right and directly configuring the host is the best solution for now. I'll let you know if I can find any more information on this. thanks! david jencks On Feb 10, 2011, at 6:28 AM, Ashish Jain wrote: Hi David, I am not sure if we can use the request object. The request (org.apache.geronimo.webservices.WebServiceContainer.Request) object gives you the address for the remote host which is the address for the proxy server, however no information on the port. Another way could have been to utilize the header request.getHeader(X-Forwarded-Host) but this is not a standard header AFAIK. So this option can also to be ruled out. So I think modifying the schema is the best way ahead. Thanks Ashish On Tue, Feb 8, 2011 at 6:34 PM, Ashish Jain ashja...@gmail.com wrote: Thanks David and Jarek. I am investigating on the comment made by David and seems to have found some headers which are being appended by HTTP server. I will investigate further in this direction to find out if the request object can be used to attain this. Thanks Ashish On Tue, Feb 8, 2011 at 1:06 AM, David Jencks david_jen...@yahoo.comwrote: Changing the schema like this shouldn't be a problem if its necessary. I'd like to understand better why its necessary. Perhaps there's another way. I thought that the way this was coded was that the host and port from the incoming request were stuffed into the wsdl being returned. Doesn't the proxy server tell us what the original request was in some way such as a request attribute? Could we look for that information and use it if available and use the request itself if not? thanks david jencks On Feb 7, 2011, at 10:39 AM, Jarek Gawor wrote: Ashish, Modifying the schema (without changing the namespace) is fine as long as you make the new element(s) optional. That at least is what we have done in the past. Jarek On Fri, Jan 28, 2011 at 10:00 AM, Ashish Jain ashja...@gmail.com wrote: Hi, When geronimo is front ended with a proxy say Apache HTTP server and a web service is invoked via this proxy. The auto generated wsdl will have the soap:address as http://g_host:g_port/service_name. Instead it should be http://proxy_host: proxy:port/service_name. The method which takes care of all this is org.apache.geronimo.axis2.WSDLQueryHandler.writeResponse . The baseUri attribute in the class has to be modified so that appropriate soap:address can be written in the wsdl file. So as to get this property into geronimo one of the way would be to be able to specify in geronimo deployment descriptor. Adding a new attribute may require schema change. Is this acceptable? Are there any other alternative ways through which this can be achieved? Thanks Ashish
Re: Configuring front end host for axis2 web services
Thanks David and Jarek. I am investigating on the comment made by David and seems to have found some headers which are being appended by HTTP server. I will investigate further in this direction to find out if the request object can be used to attain this. Thanks Ashish On Tue, Feb 8, 2011 at 1:06 AM, David Jencks david_jen...@yahoo.com wrote: Changing the schema like this shouldn't be a problem if its necessary. I'd like to understand better why its necessary. Perhaps there's another way. I thought that the way this was coded was that the host and port from the incoming request were stuffed into the wsdl being returned. Doesn't the proxy server tell us what the original request was in some way such as a request attribute? Could we look for that information and use it if available and use the request itself if not? thanks david jencks On Feb 7, 2011, at 10:39 AM, Jarek Gawor wrote: Ashish, Modifying the schema (without changing the namespace) is fine as long as you make the new element(s) optional. That at least is what we have done in the past. Jarek On Fri, Jan 28, 2011 at 10:00 AM, Ashish Jain ashja...@gmail.com wrote: Hi, When geronimo is front ended with a proxy say Apache HTTP server and a web service is invoked via this proxy. The auto generated wsdl will have the soap:address as http://g_host:g_port/service_name. Instead it should be http://proxy_host: proxy:port/service_name. The method which takes care of all this is org.apache.geronimo.axis2.WSDLQueryHandler.writeResponse . The baseUri attribute in the class has to be modified so that appropriate soap:address can be written in the wsdl file. So as to get this property into geronimo one of the way would be to be able to specify in geronimo deployment descriptor. Adding a new attribute may require schema change. Is this acceptable? Are there any other alternative ways through which this can be achieved? Thanks Ashish
[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
Configuring front end host for axis2 web services
Hi, When geronimo is front ended with a proxy say Apache HTTP server and a web service is invoked via this proxy. The auto generated wsdl will have the soap:address as http://g_host:g_port/service_name. Instead it should be http://proxy_host: proxy:port/service_name. The method which takes care of all this is org.apache.geronimo.axis2.WSDLQueryHandler.writeResponse . The baseUri attribute in the class has to be modified so that appropriate soap:address can be written in the wsdl file. So as to get this property into geronimo one of the way would be to be able to specify in geronimo deployment descriptor. Adding a new attribute may require schema change. Is this acceptable? Are there any other alternative ways through which this can be achieved? Thanks Ashish
[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
[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.
Re: AnnotationHelperTest failures in trunk
Hi Rick, I had been facing a similar problem. I have deleted xbean from my local repo and now build seems to be running fine. Thanks Ashish On Thu, Dec 16, 2010 at 3:50 PM, Rick McGuire rick...@gmail.com wrote: On 12/15/2010 9:49 AM, Rick McGuire wrote: I was able to retrace my steps enough to track down the source of the regression. One of the things I had done late yesterday was build a new version of XBean from trunk. If I delete xbean from my local maven repo and refresh the snapshot from the snapshot repository, the build problem goes away. The last xbean snapshot was deployed October 21st, so it's a bit on the old side. Some update since then appears to have introduced a regression. Managed to track this down. The problem was caused by doing a local build of the xbean trunk. The last set of changes to the ClassFinder had a couple of bugs and returned some information in a different order. The bugs are fixed and the unit test has been adjusted to the new expected order. I deployed a new xbean snapshot and also committed a fix to the unit test so that it matches. Rick Rick On 12/15/2010 8:44 AM, Rick McGuire wrote: After doing an svn up this morning, I started receiving test failures in AnnotationHelperTest while building. Since there were only a few updates applied in the last day, I tried backing off each update to figure out what change caused the failure. I backed off all the way to rev 1048998, but am still seeing the test failures. I know I successfully built that revision yesterday (and I did multiple complete builds for the revisions I committed yesterday along the way). So, I'm a bit at a loss for what is causing these failures now. I suspect it's probably being caused by a new snapshot revision in some dependency, but I've not managed to locate the problem area. Is anybody else seeing this problem? Rick
Re: [ANNOUNCE] Availability of Geronimo 2.1.7
Congrats everyone for this new release and thanks to Rex in bringing out this new release. On Tue, Nov 30, 2010 at 3:05 PM, Rex Wang rwo...@gmail.com wrote: The Apache Geronimo project is pleased to announce the available of Apache Geronimo v2.1.7 server. This release includes many new features, improvements, and bug fixes. Please see the detail information in the release notes: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.7/RELEASE_NOTES-2.1.7.txt A couple highlights are: * Provide Generic Header based authentication support * Add db2 for iSeries tranql xa connector to server * Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns * Upgrade Tomcat to 6.0.29, wadi to 2.1.2, tranql to 1.7, OpenEJB to 3.0.3, txmanager to 2.2.1 etc. The individual jars and plugins have been available through maven repository, and you can also download the source jar and assemblies in http://www.apache.org/dist/geronimo/2.1.7/ I have posted a news along with the downloads page in our confluence, however it may need some time to sync to home page. A big THANK YOU to all that contributed to this release! Great work everyone! -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo 2.1.7 (2nd try)
Build runs fine. Some basic tests are fine. My +1. On Fri, Nov 26, 2010 at 12:55 PM, Rex Wang rwo...@gmail.com wrote: Thank you, Shawn! 2010/11/26 Shawn Jiang genspr...@gmail.com +1 server/jaxb/stax tck 100% passed. On Wed, Nov 24, 2010 at 5:23 PM, Rex Wang rwo...@gmail.com wrote: Hi Devs, The 2nd release candidate for Geronimo 2.1.7 has been created and staged. The tag has been created here: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.7/ The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-016/ The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/geronimo/2.1.7/geronimo-2.1.7-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/geronimo/2.1.7/geronimo-2.1.7-source-release.zip We have to verify the binaries pass the tck again, so the vote may be open for longer than the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Lei Wang (Rex) rwonly AT apache.org -- Shawn -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo 2.1.7 (1st try)
For me the build fails with the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: Unable t o download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -Dartifa ctId=car-maven-plugin -Dversion=2.1.7 -Dpackaging=maven-plugin -Dfile=/path/to/f ile Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -Dartifact Id=car-maven-plugin -Dversion=2.1.7 -Dpackaging=maven-plugin -Dfile=/path/to/fil e -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 47 seconds [INFO] Finished at: Mon Nov 22 13:48:32 IST 2010 [INFO] Final Memory: 83M/202M [INFO] Somehow I do not find the artifact for 2.1.7 in maven2 repo http://repo2.maven.org/maven2/org/apache/geronimo/buildsupport/car-maven-plugin/ On Mon, Nov 22, 2010 at 6:49 AM, Forrest Xia forres...@gmail.com wrote: +1 Some bug fixes testing is OK for me. Thank you Rex for bring this out! Forrest On Sat, Nov 20, 2010 at 8:29 PM, Rex Wang rwo...@gmail.com wrote: Hi Devs, A release candidate for Geronimo 2.1.7 has been created and staged. The tag has been created here: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.7/ The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-015/ The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-015/org/apache/geronimo/geronimo/ 2.1.7/geronimo-2.1.7-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-015/org/apache/geronimo/geronimo/ 2.1.7/geronimo-2.1.7-source-release.zip We have to verify the binaries pass the tck, so the vote may be open for longer than the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Lei Wang (Rex) rwonly AT apache.org
Re: Problem building custom activemq for geronimo 2.1
Thanks Rex and Ivan! My build runs successfully on linux now only change is I have to disable the test DemandForwardingBridgeTest. I have applied the patch as suggested in readme.txt 4.1.2-G20100308.README.TXT and build runs successfully now. I have used sun java 1.5.0_13 and maven 2.0.9. Now I am will apply the patch on GERONIMO-5700 and will post my results. --Ashish On Fri, Nov 19, 2010 at 2:45 PM, Ivan xhh...@gmail.com wrote: Those cases failed intermittently, guess there is a time slot somewhere. I will suggest to go ahead to apply the patch in GERONIMO-5700, and try it with a full TCK first. 2010/11/19 Rex Wang rwo...@gmail.com I encountered the same problem when only built activemq-4.1.2 tag (without any of our patches). I think we can comment our the test from the build (activemq-4.1.2 had already commented out a lot of its tests...) -Rex 2010/11/18 Ashish Jain ashja...@gmail.com Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish -- Lei Wang (Rex) rwonly AT apache.org -- Ivan
[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.
Re: Problem building custom activemq for geronimo 2.1
Somehow I am again seeing some intermittent failures at times RoundRobinDispatchPolicyTest will fail and at times Spring2XmlNamesapceWithoutRemoteSchemaTest is failing. This seems to be a very unpredictable behavior. This suggests that activemq 4.1.2 build is quite unstable. I think it is better to use 4.1.2 as is and defer JIRA 5700 for 2.1.7 release. On Fri, Nov 19, 2010 at 3:47 PM, Ashish Jain ashja...@gmail.com wrote: Thanks Rex and Ivan! My build runs successfully on linux now only change is I have to disable the test DemandForwardingBridgeTest. I have applied the patch as suggested in readme.txt 4.1.2-G20100308.README.TXT and build runs successfully now. I have used sun java 1.5.0_13 and maven 2.0.9. Now I am will apply the patch on GERONIMO-5700 and will post my results. --Ashish On Fri, Nov 19, 2010 at 2:45 PM, Ivan xhh...@gmail.com wrote: Those cases failed intermittently, guess there is a time slot somewhere. I will suggest to go ahead to apply the patch in GERONIMO-5700, and try it with a full TCK first. 2010/11/19 Rex Wang rwo...@gmail.com I encountered the same problem when only built activemq-4.1.2 tag (without any of our patches). I think we can comment our the test from the build (activemq-4.1.2 had already commented out a lot of its tests...) -Rex 2010/11/18 Ashish Jain ashja...@gmail.com Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish -- Lei Wang (Rex) rwonly AT apache.org -- Ivan
[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.
Problem building custom activemq for geronimo 2.1
Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish
Re: Problem building custom activemq for geronimo 2.1
More inputs are available in GERONIMO-5700. On Thu, Nov 18, 2010 at 8:07 PM, Ashish Jain ashja...@gmail.com wrote: Hi ALL, I am working on GERONIMO-5700 which requires to add new patches to geronimo custom activemq-core. Somehow I am not able to build this following the instructions in 2.1\repository\org\apache\activemq\4.1.2-G20100308.README.TXT. Till now I have NOT applied any new patches and using the original ones as listed in 4.1.2-G20100308.README.TXT. I have tried in Windows Xp SP3 and RHEL5 with a mix of Sun java5 and Sun java6. I do not have access to MACOS so donno if the build runs successfully in that. Thanks Ashish
[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.
Re: [Discussion] Geronimo 2.1.7 Release
Thanks Forrest and Janet for the commit and testing. On Mon, Nov 8, 2010 at 7:10 PM, han hongfang hanhongf...@gmail.com wrote: For GERONIMO-4296, Forrest has done some testing and committed it into both branch 2.1 and 2.2. Janet
[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.
Re: [Discussion] Geronimo 2.1.7 Release
The fix to JIRA https://issues.apache.org/jira/browse/GERONIMO-4296 also needs to make it to geronimo 2.1.7. Janet can you help us commit the patch for geronimo 2.1. On Tue, Nov 2, 2010 at 12:12 PM, Ashish Jain ashja...@gmail.com wrote: Hi Rex, There are couple of more fixes which have to go to 2.1.7. I will commit them asap. Thanks Ashish On Tue, Nov 2, 2010 at 8:35 AM, Rex Wang rwo...@gmail.com wrote: Hi All, Hope I can cut a release in 15th. Nov. Currently, the progress looks good. Only one jira is open, which relates to the new tranql release. Please see the status in: http://jira.codehaus.org/browse/TQL-26 https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.7+Release+Status It there any other jira that you think must be fixed in this release? To Ashish, do you have any further fixes that need to apply to this release? Thanks all for your help. -Rex 2010/10/18 Rex Wang rwo...@gmail.com Thanks for the input, Ashish. Hi, David Jencks, could you please take a look at the tranql fix if you have time? http://jira.codehaus.org/browse/TQL-26 -Rex 2010/10/18 Ashish Jain ashja...@gmail.com Hi Rex, All the issues mentioned below are MUST fix - *GERONIMO-5196*Add a own authenticator for Spnego login - *GERONIMO-5197*Generic Header based authentication support in geronimo - *GERONIMO-5591 * Removing the least used and oldest statements from prepared statement cache Fixes for 5196 and 5197 have already been applied to 2.1 branch. 5196 does need any approvals from tomcat community since all the code now resides with in geronimo and there is no dependency on tomcat for anything. For 5591 we need help from David to apply the fix and generate a new tranql release. 5591 is particularly important because prepared statement cache fails to work due this bug. Thanks Ashish On Thu, Oct 14, 2010 at 10:51 AM, Rex Wang rwo...@gmail.com wrote: Hi Devs, I am preparing the Geronimo 2.1.7 release, and have some issues need your opinions. 1. In this release, we upgrade several components, such as: - geronimo-javamail_1.4_mail 1.7 - 1.8.2 - txmanager 1.4 - 2.2 - tomcat 6.0.26 - 6.0.29 Besides, I found *OpenEJB *was upgraded to 3.0.3-SNAPSHOT. To *David B,* does OpenEJB community have any plan to release 3.0.3? 2. I went through all the JIRAs agaisnt 2.1.7, and try my best to clean the status. However, there still are 3 major ones opened: To *Ashish*, what's the status of the following two problems in tomcat community? I think it is not a MUST fix issue for G 2.1.7, Right? - *GERONIMO-5196*Add a own authenticator for Spnego login - *GERONIMO-5197*Generic Header based authentication support in geronimo To *Ashish/**Amit*, I see this seems an improvement? Is this a MUST fix issue for G2.1.7? If so, we have to persuade TranQL to make a new release first. - *GERONIMO-5591 * Removing the least used and oldest statements from prepared statement cache Well, I made up a status page in our confluence here, so you can check out the details there: https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.7+Release+Status Thoughts? -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: move tranql to java 1.6?
Hi David, Is the problem you are facing due to TQL-26? We also need to have a release of Tranql ra for DB2 on Iseries which is addressed through TQL-22. Thanks Ashish On Tue, Nov 2, 2010 at 9:37 AM, David Jencks david_jen...@yahoo.com wrote: I've been unable to compile tranql to try out a couple patches and release since apple removed java 1.5 from my mac and I haven't figured out how to get it back yet. Perhaps its time to move tranql to java 1.6 with the new methods on the sql interfaces? I'd assume we'd keep java 1.5 compatible class format. There's a patch that I think does this, although it looks like it has some additional problems that would need ironing out. Does anyone know if this will create problems running tranql on java 1.5 with java 1.5 compliant drivers? thanks david jencks
Re: [Discussion] Geronimo 2.1.7 Release
Hi Rex, There are couple of more fixes which have to go to 2.1.7. I will commit them asap. Thanks Ashish On Tue, Nov 2, 2010 at 8:35 AM, Rex Wang rwo...@gmail.com wrote: Hi All, Hope I can cut a release in 15th. Nov. Currently, the progress looks good. Only one jira is open, which relates to the new tranql release. Please see the status in: http://jira.codehaus.org/browse/TQL-26 https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.7+Release+Status It there any other jira that you think must be fixed in this release? To Ashish, do you have any further fixes that need to apply to this release? Thanks all for your help. -Rex 2010/10/18 Rex Wang rwo...@gmail.com Thanks for the input, Ashish. Hi, David Jencks, could you please take a look at the tranql fix if you have time? http://jira.codehaus.org/browse/TQL-26 -Rex 2010/10/18 Ashish Jain ashja...@gmail.com Hi Rex, All the issues mentioned below are MUST fix - *GERONIMO-5196*Add a own authenticator for Spnego login - *GERONIMO-5197*Generic Header based authentication support in geronimo - *GERONIMO-5591 * Removing the least used and oldest statements from prepared statement cache Fixes for 5196 and 5197 have already been applied to 2.1 branch. 5196 does need any approvals from tomcat community since all the code now resides with in geronimo and there is no dependency on tomcat for anything. For 5591 we need help from David to apply the fix and generate a new tranql release. 5591 is particularly important because prepared statement cache fails to work due this bug. Thanks Ashish On Thu, Oct 14, 2010 at 10:51 AM, Rex Wang rwo...@gmail.com wrote: Hi Devs, I am preparing the Geronimo 2.1.7 release, and have some issues need your opinions. 1. In this release, we upgrade several components, such as: - geronimo-javamail_1.4_mail 1.7 - 1.8.2 - txmanager 1.4 - 2.2 - tomcat 6.0.26 - 6.0.29 Besides, I found *OpenEJB *was upgraded to 3.0.3-SNAPSHOT. To *David B,* does OpenEJB community have any plan to release 3.0.3? 2. I went through all the JIRAs agaisnt 2.1.7, and try my best to clean the status. However, there still are 3 major ones opened: To *Ashish*, what's the status of the following two problems in tomcat community? I think it is not a MUST fix issue for G 2.1.7, Right? - *GERONIMO-5196*Add a own authenticator for Spnego login - *GERONIMO-5197*Generic Header based authentication support in geronimo To *Ashish/**Amit*, I see this seems an improvement? Is this a MUST fix issue for G2.1.7? If so, we have to persuade TranQL to make a new release first. - *GERONIMO-5591 * Removing the least used and oldest statements from prepared statement cache Well, I made up a status page in our confluence here, so you can check out the details there: https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.7+Release+Status Thoughts? -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: move tranql to java 1.6?
Hi David, TQL-21 has been applied. TQL-22 needs to be addressed. I have uploaded all new code for TQL-22 today which includes code for prepared statement cache. Thanks Ashish On Tue, Nov 2, 2010 at 1:05 PM, David Jencks david_jen...@yahoo.com wrote: On Nov 1, 2010, at 11:31 PM, Ashish Jain wrote: Hi David, Is the problem you are facing due to TQL-26? We also need to have a release of Tranql ra for DB2 on Iseries which is addressed through TQL-22. I was hoping to apply TQL-26 and TQL-24. TQL-25 has the patch to move to java 1.6, but it needs editing. If people think it won't cause problems to add the new sql methods, I'll work on applying that. I can do TQL-22 too. Have TQL-21 and 22 been applied? I also seem to have lost my ability to log into tranql jira :-( thanks david jencks Thanks Ashish On Tue, Nov 2, 2010 at 9:37 AM, David Jencks david_jen...@yahoo.comwrote: I've been unable to compile tranql to try out a couple patches and release since apple removed java 1.5 from my mac and I haven't figured out how to get it back yet. Perhaps its time to move tranql to java 1.6 with the new methods on the sql interfaces? I'd assume we'd keep java 1.5 compatible class format. There's a patch that I think does this, although it looks like it has some additional problems that would need ironing out. Does anyone know if this will create problems running tranql on java 1.5 with java 1.5 compliant drivers? thanks david jencks
Re: Welcome Janet Hong Fang Han as a new committer
Congrats Janet. On Fri, Oct 22, 2010 at 10:34 AM, viola lu viola...@gmail.com wrote: Congrats! On Fri, Oct 22, 2010 at 9:37 AM, han hongfang hanhongf...@gmail.comwrote: Thank you all for the congratulations. I'm excited and glad to work with all of you~ On Thu, Oct 21, 2010 at 8:40 PM, Ted Kirby ted.ki...@gmail.com wrote: Congratulations Janet! Welcome aboard! Ted On Wed, Oct 20, 2010 at 9:11 PM, Ivan xhh...@gmail.com wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan -- Best regards, Han Hong Fang -- viola
Re: [Discussion] Geronimo 2.1.7 Release
Hi Rex, All the issues mentioned below are MUST fix - *GERONIMO-5196*Add a own authenticator for Spnego login - *GERONIMO-5197*Generic Header based authentication support in geronimo - *GERONIMO-5591 * Removing the least used and oldest statements from prepared statement cache Fixes for 5196 and 5197 have already been applied to 2.1 branch. 5196 does need any approvals from tomcat community since all the code now resides with in geronimo and there is no dependency on tomcat for anything. For 5591 we need help from David to apply the fix and generate a new tranql release. 5591 is particularly important because prepared statement cache fails to work due this bug. Thanks Ashish On Thu, Oct 14, 2010 at 10:51 AM, Rex Wang rwo...@gmail.com wrote: Hi Devs, I am preparing the Geronimo 2.1.7 release, and have some issues need your opinions. 1. In this release, we upgrade several components, such as: - geronimo-javamail_1.4_mail 1.7 - 1.8.2 - txmanager 1.4 - 2.2 - tomcat 6.0.26 - 6.0.29 Besides, I found *OpenEJB *was upgraded to 3.0.3-SNAPSHOT. To *David B,* does OpenEJB community have any plan to release 3.0.3? 2. I went through all the JIRAs agaisnt 2.1.7, and try my best to clean the status. However, there still are 3 major ones opened: To *Ashish*, what's the status of the following two problems in tomcat community? I think it is not a MUST fix issue for G 2.1.7, Right? - *GERONIMO-5196*Add a own authenticator for Spnego login - *GERONIMO-5197*Generic Header based authentication support in geronimo To *Ashish/**Amit*, I see this seems an improvement? Is this a MUST fix issue for G2.1.7? If so, we have to persuade TranQL to make a new release first. - *GERONIMO-5591 * Removing the least used and oldest statements from prepared statement cache Well, I made up a status page in our confluence here, so you can check out the details there: https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.1.7+Release+Status Thoughts? -- Lei Wang (Rex) rwonly AT apache.org
[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.
Re: [BUILD] branches/2.1: Failed for Revision: 958826
I also get the same error. How is that I can upload new binaries for car-maven-plugin into the snapshots repository( http://repository.apache.org/snapshots)? On Tue, Jun 29, 2010 at 11:01 AM, ga...@apache.org wrote: Geronimo Revision: 958826 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100629/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100629/unit-test-reports Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:183) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots)
Re: [BUILD] branches/2.1: Failed for Revision: 958826
Thanks a lot Shawn. I will try out now. On Tue, Jun 29, 2010 at 3:13 PM, Shawn Jiang genspr...@gmail.com wrote: Before you run the command below, you need to add following snippet in your setting file. settings servers !-- apache snapshot deploy repo require this here -- server idapache.snapshots.https/id usernameyour_geronimo_username/username passwordyour_geronimo_password/password /server /servers /settings BTW: I've done the boot-strap this time. You can try to build it locally now. On Tue, Jun 29, 2010 at 4:58 PM, Shawn Jiang genspr...@gmail.com wrote: mvn clean deploy -Dstage=bootstrap On Tue, Jun 29, 2010 at 4:40 PM, Ashish Jain ashja...@gmail.com wrote: I also get the same error. How is that I can upload new binaries for car-maven-plugin into the snapshots repository( http://repository.apache.org/snapshots)? On Tue, Jun 29, 2010 at 11:01 AM, ga...@apache.org wrote: Geronimo Revision: 958826 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100629/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100629/unit-test-reports Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.7-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.7-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:183) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file
Re: [VOTE] Release Geronimo 2.1.6 - second attempt.
I was able to build and run a few sample applications. It looks fine. My +1. --Ashish On Tue, Jun 29, 2010 at 9:51 AM, Vamsavardhana Reddy c1vams...@gmail.comwrote: +1 On Wed, Jun 23, 2010 at 2:54 PM, Rick McGuire rick...@gmail.com wrote: A release candidate for Geronimo 2.1.6 has been created and staged. This version is the same as the previous release candidate except for an upgrade to the spring framework dependency. The tag has been created here: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.6 The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-008 The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-008/org/apache/geronimo/geronimo/2.1.6/geronimo-2.1.6-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-008/org/apache/geronimo/geronimo/2.1.6/geronimo-2.1.6-source-release.zip The distribution artifacts have been copied to a second staging repository for your convenience: http://people.apache.org/~rickmcguire/staging-repo/2.1.6/http://people.apache.org/%7Erickmcguire/staging-repo/2.1.6/ We have to verify the binaries pass the tck, so the vote may be open for longer than the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) Rick -- Vamsi
[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.
Re: [VOTE] Release Geronimo 2.1.6
My +1. --Ashish On Mon, Jun 21, 2010 at 9:42 AM, Vamsavardhana Reddy c1vams...@gmail.comwrote: +1 On Fri, Jun 18, 2010 at 10:01 PM, Rick McGuire rick...@gmail.com wrote: A release candidate for Geronimo 2.1.6 has been created and staged. The tag has been created here: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.6/ https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.5/ The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-001/ https://repository.apache.org/content/repositories/orgapachegeronimo-005/ The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/geronimo/geronimo/2.1.6/geronimo-2.1.6-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-005/org/apache/geronimo/geronimo/2.1.5/geronimo-2.1.5-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-001/org/apache/geronimo/geronimo/2.1.6/geronimo-2.1.6-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-005/org/apache/geronimo/geronimo/2.1.5/geronimo-2.1.5-source-release.zip The distribution artifacts have been copied to a second staging repository for your convenience: http://people.apache.org/~rickmcguire/staging-repo/2.1.6/http://people.apache.org/%7Erickmcguire/staging-repo/2.1.6/ We have to verify the binaries pass the tck, so the vote may be open for longer than the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) Rick -- Vamsi
[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.
