Use the Apache Commons CLI to parse the command line
Key: AMQ-720
URL: https://issues.apache.org/activemq/browse/AMQ-720
Project: ActiveMQ
Type: Improvement
Versions: 4.1
Reporter: Adrian Co
Assigned
Looks like acks are not being sent back to the broker. Please file a JIRA.
On 5/23/06, vince-el-matador [EMAIL PROTECTED] wrote:
This has to see with Session.prefetchSize (that is 1000) by default.
making Session.prefetchSize=2000 makes it hanging at message 1999 ! :-)
--
View this message
I was planning on fixing the geronimo.bat and geronimo.sh scripts (as
part of GERONIMO-1638) to remove the GERONIMO_BASE environment variable
(that is no longer valid and AFAIK never worked properly) and add
GERONIMO_SERVER_NAME and GERONIMO_SERVER_DIR environment variables to be
in sync with
[ http://issues.apache.org/jira/browse/GERONIMO-2037?page=all ]
John Sisson reassigned GERONIMO-2037:
-
Assign To: John Sisson
Build failing on some Windows boxes and Solaris x86
---
Key:
Matt Hogstrom wrote:
Based on the list below I think 1,2 and 3 are new function and 4 is a
bug fix.
Aaron Mulder wrote:
Here are the things that I still want to squeeze into 1.1:
- fix console JMS to accept new providers at runtime
- fix console security realms to accept new providers at
+1
Gianny
Matt Hogstrom wrote:
Jason replied on another thread that he prefers to stay with 1.2 for
the release.
Here is the proposed nomenclature
trunk(stays 1.2 but is completely replaced with branches/1.1)
branches/1.1unchanged
branches/dead-1.2 (is a copy of the original
[ http://issues.apache.org/jira/browse/GERONIMO-2037?page=all ]
John Sisson closed GERONIMO-2037:
-
Resolution: Invalid
Cleaning out my local Maven repository fixed it. Must have been a corrupt jar.
Doing a quick comparion of the repository that
+1
John
Matt Hogstrom wrote:
Jason replied on another thread that he prefers to stay with 1.2 for
the release.
Here is the proposed nomenclature
trunk(stays 1.2 but is completely replaced with branches/1.1)
branches/1.1unchanged
branches/dead-1.2 (is a copy of the original
David J,
Based on your suggestions, I have used the following conventions to
add dependency elements to the plan file :
type = jar/unspecified : generate importclasses/import
If the version is specified, it is kept otherwise
+1
On May 22, 2006, at 5:33 PM, Matt Hogstrom wrote:
Jason replied on another thread that he prefers to stay with 1.2
for the release.
Here is the proposed nomenclature
trunk (stays 1.2 but is completely replaced with branches/1.1)
branches/1.1unchanged
branches/dead-1.2 (is
Hi,
I have a few doubts related to implementation of global jndi.
* Currently we have java:comp/env stored in Local JNDI. In Global JNDI
should objects be bound using a different namespace e.g) java: or
java:global?
* When we implement global JNDI we have some entries in Global and All
entries
U can do like this :
consumer.Listener += new MessageListener(OnMessage);
with
protected void OnMessage(IMessage message)
{
ActiveMQTextMessage msg = message as ActiveMQTextMessage;
// do whatever U like with msg
}
--
View this message in context:
using .NET 2.0 ,C# + trunk, the consumer async call back hangs at 999th call
!
Here is the code :
public void allInOne()
{
ISession session;
IDestination destination;
IConnectionFactory factory;
IMessageProducer producer;
IMessageConsumer consumer;
I agree with your comments on the addition of the X so please go ahead and make the changes you
indicated below. Let's experiment with this and get it working well. User feedback would be good
for this as well.
John Sisson wrote:
I was planning on fixing the geronimo.bat and geronimo.sh
I appreciate your concerns but as you noted there are a number of other bug fixes and blockers that
*you* moved into the 1.1 stream that need to be addressed. Null pointer exceptions, etc. If we
were in better shape on the usability front I would agree with you. There are so many of those I
After a couple of brief but very useful conversations
with other Geronimo committers at JavaOne, I thought
I'd post a progress report on the servlet spec 2.5
sandbox.
As I posted back in on 9th April, I've
made a sandbox for upgrading Geronimo to the
2.5 servlet spec, and at the same time
OK. I'm well aware that I've assigned a large number of 1.1 issues to
myself. Is there someone else I should assign them to? And do you
have a list of the other issues that you feel need to be addressed
for the 1.1 release?
Thanks,
Aaron
On 5/23/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
How about adding a JIRA number at the end so in that JIRA we include the dead certificate (the
why's, what's and how's), i.e. 1.2-dead-1234
Cheers!
Hernan
Prasad Kashyap wrote:
+1 to move 1.1 to trunk and calling it 1.2
+1 for D Jencks suggestion on the naming of the old trunk to 1.2-dead.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rodent of Unusual Size wrote:
Dain Sundstrom wrote:
Yes. I believe my answer was covered by your answer to Jan, No, the
experimental areas continue as they have. Only the main lines and
branches of development are affected.
I have an
[ http://issues.apache.org/jira/browse/GERONIMO-2046?page=all ]
Jeff Genender closed GERONIMO-2046:
---
Resolution: Fixed
Excellent...thanks Bill.
Adding geronimo-cache/LICENSE.txt
Adding geronimo-cache/pom.xml
Adding
Restting Geronimo Build Tree for 1.2 Development for post 1.1 activities
Key: GERONIMO-2053
URL: http://issues.apache.org/jira/browse/GERONIMO-2053
Project: Geronimo
Type: Task
Security:
Here is a JIRA to track this change
http://issues.apache.org/jira/browse/GERONIMO-2053
Please review. Here is the text of the JIRA right now so you can avoid a link.
** Begin **
To get us back on track for 1.2 development this JIRA is being opened to track and document changes
to the
All,
Here is what I would like to define as our closing set for 1.1
* Restoration of Codehaus repos to get OEJB and TranQL up and running.
* Complete testing of current performance fixes and commit them.
* Close out SNAPSHOTs to final releases (depends partially on the above)
* Complete the
Ken, et al,
I'm not sure about other people's feelings regarding exceptions to the Review then commit but I'd
like to request some special consideration for DevTools and DayTrader. Both of these dev trees are
external to mainline Geronimo development and as such have a very limited set of
+1
-dain
On May 22, 2006, at 11:08 PM, John Sisson wrote:
I was planning on fixing the geronimo.bat and geronimo.sh scripts
(as part of GERONIMO-1638) to remove the GERONIMO_BASE environment
variable (that is no longer valid and AFAIK never worked properly)
and add GERONIMO_SERVER_NAME
[ https://issues.apache.org/activemq/browse/AMQ-714?page=all ]
Kyle Himmerick updated AMQ-714:
---
Attachment: issue.zip
The attached zip contains two xbean configurations
wildcard.xml defines a last image recovery policy on FOO.*
explicit.xml defines a
+1
On 5/18/06, Matt Hogstrom [EMAIL PROTECTED]
��B�%¨ߨU[�_Ec�S;@_�p�A�C[!���[u.���
���$��ol��;��\�;�ɰ0�(قh�,��VJI�w���e�MF�� ���ҩ����1�Gi��f��LTʹ��3R��
��
�,v�� ;}틗c��t��1:����u5�m��ȹ� k~�~���Y ��� 9�ECGw�(�r�?t�
�V1��B�b���^d�|��c��Y�
How about we fix the actual show stoppers (only some of these
blockers are show stoppers) and ship what we got? Then we just do a
dot release every few weeks as any additional things are fixed. I
think having more regular (short) releases will be positive for the
community and will help
How about we create an experimental section of the console menu,
that only displays if you click the show experimental link (I'd
guess it can all be done with java script on the browser side). I
remember for 1.0 we removed a lot of portlets, but I think it would
be ok to include most of
+1
david jencks
On May 22, 2006, at 11:08 PM, John Sisson wrote:
I was planning on fixing the geronimo.bat and geronimo.sh scripts
(as part of GERONIMO-1638) to remove the GERONIMO_BASE environment
variable (that is no longer valid and AFAIK never worked properly)
and add
+1000
Dain Sundstrom wrote:
How about we fix the actual show stoppers (only some of these blockers
are show stoppers) and ship what we got? Then we just do a dot release
every few weeks as any additional things are fixed. I think having more
regular (short) releases will be positive for the
[ http://issues.apache.org/jira/browse/GERONIMO-2051?page=all ]
Paul McMahan updated GERONIMO-2051:
---
Attachment: GERONIMO-2051.patch
Console Jetty HTTPS connector has wrong trust store help text
[ http://issues.apache.org/jira/browse/GERONIMO-2051?page=all ]
Paul McMahan updated GERONIMO-2051:
---
Patch Info: [Patch Available]
Console Jetty HTTPS connector has wrong trust store help text
More Maven 2 build improvements
---
Key: AMQ-722
URL: https://issues.apache.org/activemq/browse/AMQ-722
Project: ActiveMQ
Type: Improvement
Reporter: Carlos Sanchez
Attachments: activemq.patch
--
This message is automatically
[
https://issues.apache.org/activemq/browse/AMQ-722?page=comments#action_36206 ]
Carlos Sanchez commented on AMQ-722:
Not sure if you want activemq-core-test inside the assembly
More Maven 2 build improvements
---
[ http://issues.apache.org/jira/browse/GERONIMO-1960?page=all ]
Aaron Mulder updated GERONIMO-1960:
---
Attachment: geronimo-service.xml
Attached a replacement for the sample deployment plan that accounts for
config-module change.
Bad GBean reference
+1 from me.
On 5/23/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
+1000
Dain Sundstrom wrote:
How about we fix the actual show stoppers (only some of these blockers
are show stoppers) and ship what we got? Then we just do a dot release
every few weeks as any additional things are fixed. I
[
https://issues.apache.org/activemq/browse/AMQ-722?page=comments#action_36207 ]
Guillaume Nodet commented on AMQ-722:
-
The final assembly has to be named incubator-activemq to follow the incubator
policy.
I have not tested the patch, but it seems the
+1
On May 23, 2006, at 2:00 PM, Dain Sundstrom wrote:
How about we fix the actual show stoppers (only some of these
blockers are show stoppers) and ship what we got? Then we just do
a dot release every few weeks as any additional things are fixed.
I think having more regular (short)
This was posted a few days ago, but since I personally ran into it
again, I'm going to repost.
If you see the following error while building openejb:
/Users/dain/work/geronimo/branches/1.1/openejb/modules/core/src/java/
org/openejb/corba/proxy/CORBAProxyReference.java:88: cannot resolve
I like the idea, but think we need more discussion on it -
How long would we do 1.1.x releases - until 1.2 is released?
We would require each committer to update trunk as fixes were applied to
1.1.x, right?
What criteria would be used to determine what could go into a 1.1.x vs.
what should
I'm unclear as to the required procedure for RTC. Is it required to
literally include the patch contents in an email to the dev list or
does a link to a JIRA issue suffice?
For an patch by a non-committer attached to a JIRA issue that I wish
to apply, can I vote for it or does it in fact
[
https://issues.apache.org/activemq/browse/AMQ-722?page=comments#action_36208 ]
Carlos Sanchez commented on AMQ-722:
Yes, I changed that, you can forget that part
More Maven 2 build improvements
---
Key:
I'll start a new thread on the 1.2 topic.
Donald Woods wrote:
I like the idea, but think we need more discussion on it -
How long would we do 1.1.x releases - until 1.2 is released?
We would require each committer to update trunk as fixes were applied to
1.1.x, right?
What criteria would
1.1 is almost complete and its time to start thinking about 1.2. Aaron summarized the discussion at
Java One in his note. I believe Aaron even volunteered to be the release manager for 1.2 :)
Here's my 2c to get this off the ground.
I am planning on working in performance improvements around
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
David Jencks updated GERONIMO-2006:
---
Attachment: badPlan.xml
Updated badPlan.xml with configId moduleId change and
context-priority-classloader removed.
Deploying an application with
I'd like to apply the patch http://issues.apache.org/jira/secure/
attachment/12334350/GERONIMO-2006.patch
from http://issues.apache.org/jira/browse/GERONIMO-2006
It fixes a buffer overflow problem in tomcat (which presumably
doesn't need a vote since it's a bug fix) and does some simple
Do we need votes for bug fixes?
Regards,
Alan
David Jencks wrote:
I'd like to apply the patch
http://issues.apache.org/jira/secure/attachment/12334350/GERONIMO-2006.patch
from http://issues.apache.org/jira/browse/GERONIMO-2006
It fixes a buffer overflow problem in tomcat (which
Hi folks,
I checked out a fresh copy of the 1.1 branch and tried to build. It
gets as far as:
+
| configurations Geronimo Configuration for performing service deployments
| Memory: 40M/50M
+
DEPRECATED: the
I think we don't.
This is an excerpt from Ken's note. As I understand, documentation and specific bug fixes are
excluded from RTC.
...This means that all code changes that aren't for
documentation or a specific bug fix need to be
submitted as patches to the dev@geronimo.apache.org
list before
On May 23, 2006, at 2:47 PM, Alan D. Cabrera wrote:
Do we need votes for bug fixes?
IIUC no but this includes new functionality as well, as I attempted
to indicate below.
thanks
david jencks
Regards,
Alan
David Jencks wrote:
I'd like to apply the patch
Toby, I have been hitting that problem too on debian with a fresh
checkout or after running the clean target. I don't know what the
underlying problem is, but compiling a second time seems to work past
it (just type maven -o new4 new5 to complete the build). This
problem may be related to the
+1
Regards,
Alan
David Jencks wrote:
On May 23, 2006, at 2:47 PM, Alan D. Cabrera wrote:
Do we need votes for bug fixes?
IIUC no but this includes new functionality as well, as I attempted to
indicate below.
thanks
david jencks
Regards,
Alan
David Jencks wrote:
I'd like to apply
Matt Hogstrom wrote:
1.1 is almost complete and its time to start thinking about 1.2.
Aaron summarized the discussion at Java One in his note. I believe
Aaron even volunteered to be the release manager for 1.2 :)
Isn't that like leaving the fox in charge of the chicken coop? ;)
Here's my
/me mumbles something about roses...
Regards,
Alan
Dain Sundstrom wrote:
How about we create an experimental section of the console menu,
that only displays if you click the show experimental link (I'd
guess it can all be done with java script on the browser side). I
remember for 1.0 we
+1 from me.
David Jencks wrote:
I'd like to apply the patch
http://issues.apache.org/jira/secure/attachment/12334350/GERONIMO-2006.patch
from http://issues.apache.org/jira/browse/GERONIMO-2006
It fixes a buffer overflow problem in tomcat (which presumably doesn't
need a vote since it's
* E254
Matt Hogstrom wrote:
+1000
Dain Sundstrom wrote:
How about we fix the actual show stoppers (only some of these
blockers are show stoppers) and ship what we got? Then we just do a
dot release every few weeks as any additional things are fixed. I
think having more regular (short)
Ahh, so I wasn't the only one having the problem :-)
Ensure all the geronimo plugins in your local repo are deleted. That
seemed to fix it for me in GERONIMO-2037. I didn't have the time to
spend working out which plugin and change introduced the problem.
John
Paul McMahan wrote:
Toby, I
+1 to fixing
John
David Jencks wrote:
I'd like to apply the patch
http://issues.apache.org/jira/secure/attachment/12334350/GERONIMO-2006.patch
from http://issues.apache.org/jira/browse/GERONIMO-2006
It fixes a buffer overflow problem in tomcat (which presumably doesn't
need a vote since
+1
John
Dain Sundstrom wrote:
How about we fix the actual show stoppers (only some of these blockers
are show stoppers) and ship what we got? Then we just do a dot
release every few weeks as any additional things are fixed. I think
having more regular (short) releases will be positive for
+1
Gianny
David Jencks wrote:
I'd like to apply the patch http://issues.apache.org/jira/secure/
attachment/12334350/GERONIMO-2006.patch
from http://issues.apache.org/jira/browse/GERONIMO-2006
It fixes a buffer overflow problem in tomcat (which presumably
doesn't need a vote since it's a
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
David Jencks closed GERONIMO-2006:
--
Resolution: Fixed
Assign To: David Jencks (was: Aaron Mulder)
applied in rev 409023. +1 from jgenender, acabrera, gdamour, and possibly
So what alan is point out is I just suggested we add one more
feature. I agree that this is another feature, so what do we want to
do? I think we have three choices:
1) My idea below, isolate the broken porlets to an experimental
section
2) Just remove the broken portlets
3) Fix the
On May 23, 2006, at 6:28 AM, Krishnakumar B wrote:
Hi,
I have a few doubts related to implementation of global jndi.
* Currently we have java:comp/env stored in Local JNDI. In Global JNDI
should objects be bound using a different namespace e.g) java: or
java:global?
IIUC java: is reserved
I won't know this will work until I see it in action :-) but this
basically looks good to me.
On May 23, 2006, at 6:12 AM, anita kulshreshtha wrote:
David J,
Based on your suggestions, I have used the following
conventions to
add dependency elements to the plan file :
type =
+1
david jencks
On May 22, 2006, at 2:33 PM, Matt Hogstrom wrote:
Jason replied on another thread that he prefers to stay with 1.2
for the release.
Here is the proposed nomenclature
trunk (stays 1.2 but is completely replaced with branches/1.1)
branches/1.1unchanged
So, following your lead this is what I'm currently thinking of
working on, not necessarily in order:
- global jndi. I hope that this will involve advising Krishnakumar
rather than implementing it myself.
- pluggable jacc. This is sort of half done. The remaining part is
making
[ http://issues.apache.org/jira/browse/GERONIMO-1900?page=all ]
Prasad Kashyap reopened GERONIMO-1900:
--
I tried the Continuum build from 05/23/06 that i downloaded from
http://people.apache.org/repository/geronimo/distributions/
The examples
[
http://issues.apache.org/jira/browse/GERONIMO-1900?page=comments#action_12413050
]
Aaron Mulder commented on GERONIMO-1900:
I'm pretty sure this means the plugins need to be rebuilt.
Sample app links on welcome app are broken by default
On May 23, 2006, at 5:19 PM, David Jencks wrote:
On May 23, 2006, at 6:28 AM, Krishnakumar B wrote:
Hi,
I have a few doubts related to implementation of global jndi.
* Currently we have java:comp/env stored in Local JNDI. In Global
JNDI
should objects be bound using a different
On May 23, 2006, at 12:53 PM, Donald Woods wrote:
I like the idea, but think we need more discussion on it -
I think we need a compromise here. If we make it too restrictive,
people won't work on dot releases and they will drag out the normal
release cycle to polish their bits because
[ http://issues.apache.org/jira/browse/GERONIMO-1960?page=all ]
Dain Sundstrom updated GERONIMO-1960:
-
Attachment: 1960.patch
NOTE: This patch needs further discussion on the dev list before it can be
applied (see the last item)...
I added a
Paul,
Thanks for the tip. Looks like I need to do an online build, and
people.apache.org has been bouncy for the past few hours, but I'll try
a maven new4 new5 again tomorrow morning. Appreciate the help!
Toby
I finished the patch for GERONIMO-1960 (http://issues.apache.org/jira/
browse/GERONIMO-1960), but I think it may be destabilizing and should
be move to 1.1.1.
I added a verify method to Deployment context which is called from
getConfigurationData(). This method verifies the references and
Inline
Dain Sundstrom wrote:
On May 23, 2006, at 12:53 PM, Donald Woods wrote:
I like the idea, but think we need more discussion on it -
I think we need a compromise here. If we make it too restrictive,
people won't work on dot releases and they will drag out the normal
release cycle to
David J,
Here it is... These are the configurations without the openejb.
Just FYI few points :
1. The o.a.g.d.BootstrapPlugin.bootstrap uses hardcoded
Maven1Repository. I keep changing the following lines to switch between
m1 and m2. I would like to change this:
Maven1Repository
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Kevan Miller reopened GERONIMO-2006:
Assign To: Kevan Miller (was: David Jencks)
The commit associated with this defect was incomplete. It was missing
PlanExportServlet.
As
77 matches
Mail list logo
