Hi,
I am using XFire version 1.2.6
There seems to be a bug in JMSChannel.
The selector creation function used for topic queues looks like this:
private String createMessageSelector() {
System.out.println("JMSType='" + selector + "' and Source<>'" + MyID
+ "'");
return "JMSType='" + selector + "' and Source<>'" + MyID + "')";
}
The return and sysout do not match. There is an extra ')' at the end of the
string in the return statement. It needs to be removed. I have verified that
it works without the ')'.
Can someone please raise a ticket for this?
Thanks !
Regards
Mayank Thakore
Huawei Technologies
Mobile: +91-988-665-9544
****************************************************************************
****************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
_____
From: Kalle Korhonen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 10-40
To: [email protected]
Subject: Re: [xfire-user] Is chunking in client requests supported by xfire
services?
Should work. Which version of XFire are you using? Do you also have MTOM
enabled? (http://xfire.codehaus.org/MTOM) If memory serves me, there was
some some issue with stream not always being flushed in some older version.
Check that this isn't the case with your client.
Kalle
On 10/9/07, Sanja Jokic <[EMAIL PROTECTED]> wrote:
Hi,
I had JAX-WS client complaining about "Unexpected character '0' (code 48) in
prolog;" exception.
The exception was thrown intermittently, and I have been unable to find a
pattern in which it would occur.
After much examination, I found that he used Transfer-Encoding: chunked in
his requests.
My wild guess is that unexpected 0 might be related to chunk terminating
character.
Turning the chunking off seems to have fixed the problem, but we can't yet
be sure since the problem was intermittent.
Is chunking in client requests tested/supported by xfire services?
Does anyone has working client with chunking enabled?
Thanks!
