You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by Jeff Davis <jd...@idalica.com> on 2008/08/08 21:03:30 UTC
Issue with XSLT mediator when using a remote registry (SimpleURLRegistry)
Has anyone experienced issues when trying to use a large XSTL when using the
remote registry (SimpleURLRegistry)? I've got a situation where I have a
modestly sized XSTL, and when I use the localEntry to fetch and apply it, it
works fine. However, when using the registry, it hangs up. It's finding the
XSTL fine, because if I prune it way down in size, it works fine. It only
has trouble as the stylesheet grows in size, apparently.
The last entries in the console log are:
DEBUG XSLTMediator Start : XSLT mediator
DEBUG StAXUtils XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
DEBUG XSLTMediator Using byte array serialization for transformation
I didn't see anything in Jira on this particular issue.
jeff
Re: Issue with XSLT mediator when using a remote registry (SimpleURLRegistry)
Posted by Andreas Veithen <an...@skynet.be>.
I think this issue is the same as SYNAPSE-406 and SYNAPSE-428 and has
already been fixed by Indika.
Andreas
On 10 août 08, at 16:10, Ruwan Linton wrote:
> Thanks for the information Jeff, I will try to reproduce this and
> please
> specify the size of the XSLT that you have used from the registry in
> the
> JIRA
>
> Thanks,
> Ruwan
>
> On Sun, Aug 10, 2008 at 3:12 AM, Jeff Davis <jd...@idalica.com>
> wrote:
>
>> Hey Ruwan,
>>
>> I'm not entirely sure it's a memory issue. I had tried increasing the
>> memory
>> previously, and have my startup set with the following:
>>
>> $JAVA_HOME/bin/java -server -Xms512M -Xmx1024M -Xss20M
>>
>> I'll go a ahead an submit a Jira. I had also submitted a Jira a few
>> weeks
>> back regarding a somewhat similar issue I had experienced with the
>> validator, when using a very large XSD (it too had hung up).
>>
>> Thanks for all of your help!
>>
>> jeff
>>
>> On Fri, Aug 8, 2008 at 9:21 PM, Ruwan Linton <ru...@gmail.com>
>> wrote:
>>
>>> Jeff,
>>>
>>> This can be due to the memory issue, because we load the XSLT to the
>> memory
>>> even though the source and result is prevented from being loaded
>>> fully
>> into
>>> memory when those are very large.
>>>
>>> Can you increase the maximum memory size for the java process
>>> which is
>>> running the Synapse and see? you can use the -Xmx systme property to
>>> increase the memory in the synapse.sh
>>>
>>> Also you may go ahead and file a JIRA for this, I will have a look
>>> at
>> it...
>>>
>>> Thanks,
>>> Ruwan
>>>
>>> On Sat, Aug 9, 2008 at 12:33 AM, Jeff Davis <jd...@idalica.com>
>>> wrote:
>>>
>>>> Has anyone experienced issues when trying to use a large XSTL when
>> using
>>>> the
>>>> remote registry (SimpleURLRegistry)? I've got a situation where I
>>>> have
>> a
>>>> modestly sized XSTL, and when I use the localEntry to fetch and
>>>> apply
>> it,
>>>> it
>>>> works fine. However, when using the registry, it hangs up. It's
>>>> finding
>>> the
>>>> XSTL fine, because if I prune it way down in size, it works fine.
>>>> It
>> only
>>>> has trouble as the stylesheet grows in size, apparently.
>>>>
>>>> The last entries in the console log are:
>>>>
>>>> DEBUG XSLTMediator Start : XSLT mediator
>>>> DEBUG StAXUtils XMLStreamWriter is
>>>> com.ctc.wstx.sw.SimpleNsStreamWriter
>>>> DEBUG XSLTMediator Using byte array serialization for
>>>> transformation
>>>>
>>>>
>>>> I didn't see anything in Jira on this particular issue.
>>>>
>>>> jeff
>>>>
>>>
>>>
>>>
>>> --
>>> Ruwan Linton
>>> http://wso2.org - "Oxygenating the Web Services Platform"
>>> http://ruwansblog.blogspot.com/
>>>
>>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
Re: Issue with XSLT mediator when using a remote registry (SimpleURLRegistry)
Posted by Ruwan Linton <ru...@gmail.com>.
Thanks for the information Jeff, I will try to reproduce this and please
specify the size of the XSLT that you have used from the registry in the
JIRA
Thanks,
Ruwan
On Sun, Aug 10, 2008 at 3:12 AM, Jeff Davis <jd...@idalica.com> wrote:
> Hey Ruwan,
>
> I'm not entirely sure it's a memory issue. I had tried increasing the
> memory
> previously, and have my startup set with the following:
>
> $JAVA_HOME/bin/java -server -Xms512M -Xmx1024M -Xss20M
>
> I'll go a ahead an submit a Jira. I had also submitted a Jira a few weeks
> back regarding a somewhat similar issue I had experienced with the
> validator, when using a very large XSD (it too had hung up).
>
> Thanks for all of your help!
>
> jeff
>
> On Fri, Aug 8, 2008 at 9:21 PM, Ruwan Linton <ru...@gmail.com>
> wrote:
>
> > Jeff,
> >
> > This can be due to the memory issue, because we load the XSLT to the
> memory
> > even though the source and result is prevented from being loaded fully
> into
> > memory when those are very large.
> >
> > Can you increase the maximum memory size for the java process which is
> > running the Synapse and see? you can use the -Xmx systme property to
> > increase the memory in the synapse.sh
> >
> > Also you may go ahead and file a JIRA for this, I will have a look at
> it...
> >
> > Thanks,
> > Ruwan
> >
> > On Sat, Aug 9, 2008 at 12:33 AM, Jeff Davis <jd...@idalica.com> wrote:
> >
> > > Has anyone experienced issues when trying to use a large XSTL when
> using
> > > the
> > > remote registry (SimpleURLRegistry)? I've got a situation where I have
> a
> > > modestly sized XSTL, and when I use the localEntry to fetch and apply
> it,
> > > it
> > > works fine. However, when using the registry, it hangs up. It's finding
> > the
> > > XSTL fine, because if I prune it way down in size, it works fine. It
> only
> > > has trouble as the stylesheet grows in size, apparently.
> > >
> > > The last entries in the console log are:
> > >
> > > DEBUG XSLTMediator Start : XSLT mediator
> > > DEBUG StAXUtils XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
> > > DEBUG XSLTMediator Using byte array serialization for transformation
> > >
> > >
> > > I didn't see anything in Jira on this particular issue.
> > >
> > > jeff
> > >
> >
> >
> >
> > --
> > Ruwan Linton
> > http://wso2.org - "Oxygenating the Web Services Platform"
> > http://ruwansblog.blogspot.com/
> >
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: Issue with XSLT mediator when using a remote registry (SimpleURLRegistry)
Posted by Jeff Davis <jd...@idalica.com>.
Hey Ruwan,
I'm not entirely sure it's a memory issue. I had tried increasing the memory
previously, and have my startup set with the following:
$JAVA_HOME/bin/java -server -Xms512M -Xmx1024M -Xss20M
I'll go a ahead an submit a Jira. I had also submitted a Jira a few weeks
back regarding a somewhat similar issue I had experienced with the
validator, when using a very large XSD (it too had hung up).
Thanks for all of your help!
jeff
On Fri, Aug 8, 2008 at 9:21 PM, Ruwan Linton <ru...@gmail.com> wrote:
> Jeff,
>
> This can be due to the memory issue, because we load the XSLT to the memory
> even though the source and result is prevented from being loaded fully into
> memory when those are very large.
>
> Can you increase the maximum memory size for the java process which is
> running the Synapse and see? you can use the -Xmx systme property to
> increase the memory in the synapse.sh
>
> Also you may go ahead and file a JIRA for this, I will have a look at it...
>
> Thanks,
> Ruwan
>
> On Sat, Aug 9, 2008 at 12:33 AM, Jeff Davis <jd...@idalica.com> wrote:
>
> > Has anyone experienced issues when trying to use a large XSTL when using
> > the
> > remote registry (SimpleURLRegistry)? I've got a situation where I have a
> > modestly sized XSTL, and when I use the localEntry to fetch and apply it,
> > it
> > works fine. However, when using the registry, it hangs up. It's finding
> the
> > XSTL fine, because if I prune it way down in size, it works fine. It only
> > has trouble as the stylesheet grows in size, apparently.
> >
> > The last entries in the console log are:
> >
> > DEBUG XSLTMediator Start : XSLT mediator
> > DEBUG StAXUtils XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
> > DEBUG XSLTMediator Using byte array serialization for transformation
> >
> >
> > I didn't see anything in Jira on this particular issue.
> >
> > jeff
> >
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
>
Re: Issue with XSLT mediator when using a remote registry (SimpleURLRegistry)
Posted by Ruwan Linton <ru...@gmail.com>.
Jeff,
This can be due to the memory issue, because we load the XSLT to the memory
even though the source and result is prevented from being loaded fully into
memory when those are very large.
Can you increase the maximum memory size for the java process which is
running the Synapse and see? you can use the -Xmx systme property to
increase the memory in the synapse.sh
Also you may go ahead and file a JIRA for this, I will have a look at it...
Thanks,
Ruwan
On Sat, Aug 9, 2008 at 12:33 AM, Jeff Davis <jd...@idalica.com> wrote:
> Has anyone experienced issues when trying to use a large XSTL when using
> the
> remote registry (SimpleURLRegistry)? I've got a situation where I have a
> modestly sized XSTL, and when I use the localEntry to fetch and apply it,
> it
> works fine. However, when using the registry, it hangs up. It's finding the
> XSTL fine, because if I prune it way down in size, it works fine. It only
> has trouble as the stylesheet grows in size, apparently.
>
> The last entries in the console log are:
>
> DEBUG XSLTMediator Start : XSLT mediator
> DEBUG StAXUtils XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
> DEBUG XSLTMediator Using byte array serialization for transformation
>
>
> I didn't see anything in Jira on this particular issue.
>
> jeff
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/