Re: jms proxy problem with snapshot build

[Andreas Veithen <an...@gmail.com>]

FYI: Since the JMS transport is built on AbstractTransportListener,
recent snapshots would be impacted by the issue described in
WSCOMMONS-466/SYNAPSE-542. This might explain why the transport is
malfunctioning in such a catastrophic way.

Andreas

On Tue, Apr 21, 2009 at 20:04, Asankha C. Perera <as...@apache.org> wrote:
> Hi Keith
>>
>> Sorry for the confusion.  The message should read:
>>
>> I pulled SNAPSHOT build 608.
>> I publish 40 messages to my "incoming queue" before I start Synapse.
>> When I start Syanpse, I no longer see the "FATAL synapse is not
>> initialized"
>> problems that I was seeing with a previous snapshot build.  However it
>> takes
>> an insanely long time to process the messages.  Only 19 of the 40 messages
>> got processed and it took about 20 minutes.  The other 21 messages got
>> dropped on the floor somewhere.
>>
>
> Do you know what is responsible for the delays? i.e. waiting for backend
> messages that never arrive?? Can you attach your synapse.xml and axis2.xml
> and a brief description of the problem you are trying to solve and the
> overview of the configuration you have thus implemented?
>>
>> The other problem that I see is that is seems to pull all the messages off
>> the incoming queue into memory as soon as Synapse comes up.  So Synapse
>> comes up, I see my 40 messages get removed from the "incoming queue." At
>> this point the messages seem to be in memory and are getting processed by
>> Synapse.  If synapse would go down all the messages in memory would be
>> lost
>> because they were already ripped off the incoming queue.
>>
>
> Are you reading messages transactionally?
>>
>> A further problem I am having is that in my sequence flow the messages end
>> up getting cloned to 6 sequences.  The cloning loses a bunch of messages.
>> In the synapse.log, I see "... 1 of 6..." 40 times but then I only see "2
>> of
>> 6" and so on 19 times.   I don't see any errors it just seems that the
>> cloning isn't happening as much as it should and I lose messages.
>>
>
> Hmm.. this would need further analysis..
>>
>> Also, can someone shed some light on what the ..../repository/fault should
>> be.  I get this error in the synpase.log
>> 2009-04-21 09:41:22,342 [-] [main] DEBUG SynapseConfigUtils Can not open a
>> connection to the URL with a path :file:./repository/fault
>> 2009-04-21 09:41:22,342 [-] [main] DEBUG SynapseConfigUtils Trying  to
>> resolve an absolute path of the  URL using the synapse.home :
>> /opt/ads/icdl/synapseMediators/dist/synapse-icdl
>> 2009-04-21 09:41:22,343 [-] [main] DEBUG SynapseConfigUtils Failed to
>> resolve an absolute path of the  URL using the synapse.home :
>> /opt/ads/icdl/synapseMediators/dist/synapse-icdl
>> 2009-04-21 09:41:22,343 [-] [main]  WARN SynapseConfigUtils IO Error
>> reading
>> from URL :
>> /opt/ads/icdl/synapseMediators/dist/synapse-icdl/./repository/faultjava.io.F
>> ileNotFoundException:
>> /opt/ads/icdl/synapseMediators/dist/synapse-icdl/./repository/fault (No
>> such
>> file or directory)
>>
>
> Seems like you are encountering faults, and the fault sequence is not
> found.. sharing the resources I asked for could be helpful. Please remove
> any passwords etc before posting these publicly
>
> cheers
> asankha
>
> --
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
>
>
>