Hi, I'm not 100% sure where the size limit is. Attached is the xslt that gives the problem.
You can see the problem when you refer to it like this:
<syn:registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
<syn:parameter name="root">file:./resources/</syn:parameter>
<syn:parameter name="cachableDuration">1000</syn:parameter>
</syn:registry>
...
<<< the xslt mediator her
key="transform/check_token.xslt"
Regards,
Harm
On Tue, Jan 13, 2009 at 11:29 AM, Ruwan Linton <[email protected]> wrote:
> Hi Harm,
>
> We haven't come across this issue and it seems like an issue with the
> SimpleURL Registry.... can you please be more specific on the file size
> which causes this issue, if you can attach the file that is causing the
> trouble, that would be perfect.
>
> Also, have you tried this same scenario with the WSO2 Registry as the
> registry back end instead of the SimpleURL registry, just make sure the
> issue resides in the registry.
>
> Thanks,
> Ruwan
>
> Harm Verhagen wrote:
> > Hi
> >
> >
> > I'm seeing weird problems with the wso2 bus and the registry.
> > Whenever a file (eg: wsdl or xslt) gets a certain size (or complexity
> > ?) the file (and the complete bus) refuses to work, unless the file is
> > moved from the SimpleURLRegistry to the local registry.
> >
> > We saw the problem with wsdl files (several) and xslt files (several).
> > A perferctly fine working configuration. Add a few lines to the
> > xslt/wsdl file (lines that are obviously correct). and then the bus no
> > longer works. (restarting doesn't help etc... )
> > The 'same' file put in the local registry works as a charm.
> >
> > *version*: wso2esb v1.7.1
> >
> > synapse.xml
> > <syn:registry
> > provider="org.apache.synapse.registry.url.SimpleURLRegistry">
> > <syn:parameter name="root">file:./resources/</syn:parameter>
> > <syn:parameter name="cachableDuration">1000</syn:parameter>
> > </syn:registry>
> > ...
> > ...
> > key="transform/some.xslt"
> >
> >
> > *How to reproduce:*
> > - Use a xslt file that is big enough (or complex enough ??) in the
> > SimpleURLRegistry
> >
> > *result*
> > Whenever a message is processes that requires the offending file the
> > wso2esb bus hangs in loading that particular file.
> > 2009-01-13 10:02:16,775 [127.0.0.1-vloeki_v01] [HttpServerWorker-5]
> > DEBUG LogMediator Start : Log mediator
> > 2009-01-13 10:02:16,775 [127.0.0.1-vloeki_v01] [HttpServerWorker-5]
> > INFO LogMediator CHECK_TOKEN_RESULT = FAULT
> > 2009-01-13 10:02:16,775 [127.0.0.1-vloeki_v01] [HttpServerWorker-5]
> > DEBUG LogMediator End : Log mediator
> > 2009-01-13 10:02:16,776 [127.0.0.1-vloeki_v01] [HttpServerWorker-5]
> > DEBUG XSLTMediator Start : XSLT mediator
> > 2009-01-13 10:02:16,776 [127.0.0.1-vloeki_v01] [HttpServerWorker-5]
> > DEBUG XSLTMediator Using byte array serialization for transformation
> > ...
> > hangs..
> >
> >
> > *workaround:*
> > Move the file (xslt or wsdl) to the local registry:
> > <syn:localEntry key="XXX_1_0_xslt"
> > src="file:registry/XSLT/XXX_1_0.xslt"/>
> > ...
> > key="XXX_1_0_xslt"
> > Then everything works fine.
> > Or...
> > shorten the wsdl/xslt file. (remove some lines) then it also works
> > in the SimpleURLRegistry.
> >
> >
> > Is this a known problem ?
> >
> > Regards,
> > Harm Verhagen
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Esb-java-user mailing list
> > [email protected]
> > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
> >
>
>
> _______________________________________________
> Esb-java-user mailing list
> [email protected]
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
check_token.xslt
Description: Binary data
_______________________________________________ Esb-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
