[
https://issues.apache.org/jira/browse/QPID-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon resolved QPID-1712.
Resolution: Fixed
The value of _cycleRetries was 0 as a default hence resulting in the
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Description:
The default roundrobin failover policy does not reset the cursor position
after a successful failover. This means that
[
https://issues.apache.org/jira/browse/QPID-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1712:
--
Assignee: Arnaud Simon
> Roundrobin failover policy does not reset the cursor position afte
Hello,
I have been playing with our 0.10 cluster. When testing it I used a java
client and 2 brokers. I quickly ran into this issue:
org.apache.qpid.transport.ConnectionException: connection closed
at org.apache.qpid.transport.Connection.send(Connection.java:294)
at org.apache.qpid.transport.S
[
https://issues.apache.org/jira/browse/QPID-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676581#action_12676581
]
Arnaud Simon commented on QPID-1684:
Solved: Revision: 747722
public c
[
https://issues.apache.org/jira/browse/QPID-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon updated QPID-1684:
---
Status: Ready To Review (was: In Progress)
> Object of a JMS ObjectMessage is nullify after
[
https://issues.apache.org/jira/browse/QPID-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1684:
--
Assignee: Arnaud Simon
> Object of a JMS ObjectMessage is nullify after the first acc
Components: Java Client
Affects Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Description:
The object of a JMS ObjectMessage can only be accessed once. The object is
returned the first time it is accessed using the method getObject and any
subsequent access returns
[
https://issues.apache.org/jira/browse/QPID-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676300#action_12676300
]
Arnaud Simon commented on QPID-1642:
no, the problem is that we need to know whe
Marnie McCormack wrote:
Hi Arnaud,
I think you've misunderstood here. It's great to have Etienne onboard, and
ideal to have someone with the skills he has working with us.
I don't know who has misunderstood who but I do appreciate your effort
to help.
I think that a good understanding of th
Marnie McCormack wrote:
This JIRA exists with links to applicable design notes:
https://issues.apache.org/jira/browse/QPID-33
Maybe we want to close this obsolete JIRA and give a new start with a
fresh one.
I'd recommend a starting point for any new contributer being something a
little sma
Hi Rob,
Sketching some ideas on clustering would be good...
Unfortunately/Fortunately (depending on your point of view) we're
about to start some major surgery on the Java Broker to bring in 0-10
protocol support and ready it for AMQP 1-0 (based on the ideas in the
preliminary drafts from the AMQ
istributed computing (clustering
and replication) and a strong java background.
I worked on MOM services replication with the mentoring of Arnaud
Simon, during my Ph.D. years.
Therefore, if needed, Arnaud can be referred to as my reference, I guess :)
After exchanging a few emails with Arnaud
[
https://issues.apache.org/jira/browse/QPID-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon updated QPID-1665:
---
Status: Ready To Review (was: In Progress)
> (0.10 client) session does not ack messages bef
[
https://issues.apache.org/jira/browse/QPID-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1665:
--
Assignee: Arnaud Simon
> (0.10 client) session does not ack messages before maxprefetch/2
Issue Type: Bug
Components: Java Client
Affects Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Description:
The following is done in AMQSession_0_10 method acknowledgeMessage
if (unackedCount >= prefetch/2)
{
flushAcknowledgme
Question 1: Change the version number from M.x:
[X ] Change the release from M.x to any of the other options
Question 2: Change the version number to:
[X] 1.5
Arnaud
-
Apache Qpid - AMQP Messaging Implementation
Project:
: Java Client
Affects Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Applications that are packaged in .ear or for example in JBoss specific archive
(*.esb, *.sar) require to retrieve amqp.properties from the CLASSPATH of the
classloader that deployed the archive
[
https://issues.apache.org/jira/browse/QPID-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon deleted QPID-1656:
---
> llows an amqp.properties file to be fo
Reporter: Arnaud Simon
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
: Arnaud Simon
Assignee: Arnaud Simon
Fix For: M5
It would be nice to provide some headers exchange samples. At the minute we
cannot use straight JMS (I believe we are currently addressing that) but we
however should provide AMQPish samples.
--
This message is
[
https://issues.apache.org/jira/browse/QPID-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1643:
--
Assignee: Rafael H. Schloming
We'll need to fix the receive no wait issue first
&g
Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Description
When the queue is empty then a Queue browser waits 1s before returning null and
when the enumeration is created.
Solution
The implementation should use a receive no wait instead of a receive with a 1s
delay
[
https://issues.apache.org/jira/browse/QPID-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670399#action_12670399
]
Arnaud Simon commented on QPID-1642:
Actually we cannot do a take as the message
[
https://issues.apache.org/jira/browse/QPID-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1642:
--
Assignee: Rafael H. Schloming
Can you validate the solution?
> JMS ReceiveNowait does
Type: Bug
Components: Java Client
Affects Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Description:
The first invocation of receiveNoWait does not return a message even if the
queue is full.
How to replicate:
1) create a queue
2) send a message
3) try to
IMessage wrapper
Key: QPID-1620
URL: https://issues.apache.org/jira/browse/QPID-1620
Project: Qpid
Issue Type: Improvement
Components: Dot Net Client
Affects Versions: M4
Reporter: Arnaud Simon
[
https://issues.apache.org/jira/browse/QPID-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon updated QPID-1587:
---
Status: Ready To Review (was: In Progress)
> Add java LVQ samp
Add java LVQ samples
Key: QPID-1587
URL: https://issues.apache.org/jira/browse/QPID-1587
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: M5
Reporter: Arnaud
[
https://issues.apache.org/jira/browse/QPID-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1587:
--
Assignee: Arnaud Simon
> Add java LVQ samples
>
>
>
: C++ Broker
Affects Versions: M4
Reporter: Arnaud Simon
Description of problem: C++ broker crashes when a standard message is sent to a
LVQ
Steps to reproduce are:
- Create a LVQ queue with key foo
- Send 10 messages with the key foo
- Send a message without a key
On 12/24/2008 04:07 PM, Robert Greig wrote:
2008/12/24 Aidan Skinner:
what's happening with M4? Are we going to roll another RC after the
break? Is there going to be a branch or should we still avoid checking
in big changes to trunk? Is there a list of stuff that needs doing?
Jira still see
[
https://issues.apache.org/jira/browse/QPID-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon resolved QPID-1547.
Resolution: Fixed
Fix Version/s: M4
I have tested the fix on Windows and linux. It works
[
https://issues.apache.org/jira/browse/QPID-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon updated QPID-1547:
---
Status: Ready To Review (was: In Progress)
> Client always displays exception on Wind
On 12/23/2008 12:02 AM, Robert Greig wrote:
2008/12/22 Arnaud Simon:
I am referring to the files that are out of date. So, yes WCF is outdated on
the repo. I could either chek in or you can. that's your call.
OK - just one other thing to check - are there any files you hav
On 12/22/2008 11:33 PM, Robert Greig wrote:
2008/12/22 Arnaud Simon:
It looks as if the assembly files must be updated. I can od that if you
like. Or you can check in the one you have.
I don't quite understand. Which file(s) are you referring to?
RG
I am referring to the
On 12/22/2008 09:45 PM, Robert Greig wrote:
2008/12/22 Arnaud Simon:
It is working fine on my box, but I am building it with Visual studio
though. I also have some diffs on some assembly files but I doubt this is
what is causing the errors.
It looks as if the assembly files
On 12/22/2008 12:54 PM, Robert Greig wrote:
I have been working on fixing the msbuild scripts for the .net client
(QPID-1524).
In doing this I have found that the WCF client (which has no nant build script)
does not build. Looking at the errors I don't think it could ever have worked.
It
[
https://issues.apache.org/jira/browse/QPID-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon updated QPID-1545:
---
Attachment: core.qpidd.4273.zip
core
> ACL failure
> ---
>
> Ke
[
https://issues.apache.org/jira/browse/QPID-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon updated QPID-1545:
---
Attachment: acldump.txt
acl dump
> ACL failure
> ---
>
> Ke
[
https://issues.apache.org/jira/browse/QPID-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Simon reassigned QPID-1547:
--
Assignee: Arnaud Simon
> Client always displays exception on Wind
: M4
Reporter: Arnaud Simon
A java client running on Windows always displays the following exception when
closing a JMS connection:
org.apache.qpid.AMQException: socket closed
at
org.apache.qpid.client.AMQConnectionDelegate_0_10.closeConnection(AMQConnectionDelegate_0_10.java
[
https://issues.apache.org/jira/browse/QPID-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658104#action_12658104
]
Arnaud Simon commented on QPID-1545:
= ACL file was:
# sample qpid ACL file
#
ACL failure
---
Key: QPID-1545
URL: https://issues.apache.org/jira/browse/QPID-1545
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: M4
Reporter: Arnaud Simon
The c++ broker is
44 matches
Mail list logo
