Hi Rupert

Did you get a chance to look at what i tried doing to resolve the mentioned
issue based on pointers shared.

Can you please let me know if i am doing something wrong here or missing
something as the issue persists

best regards
tarandeep


On Wed, Jul 24, 2013 at 6:35 PM, Tarandeep Singh, Sawhney <
tsawh...@innodata.com> wrote:

> Thanks Rupert and Fabian for your responses.
>
> Hi Rupert,
>
> Thanks for suggesting workarounds.
>
> We have tried all three workarounds but the issue persists. I am sure i am
> missing something, if you can please review below findings will help us
> identify gaps in our approach.
> *
> *
> *"1. reduce the size of the configuration (e.g. by removing comment
> lines from the field mappings)"*
>
> We are configuring EntityHubLinking engine and we dont see any comments as
> it is present while configuring ReferenceSite.
>
> *"2. configure the Site using the configuration file located in
> "stanbol/fileinstall". Make sure that changes to the file confirm to
> the syntax required by the *.config files"
> *
>
> We tried configuring EntityHubLinking engine by editing "*
> org.apache.stanbol.enhancer.engines.entityhublinking.EntityhubLinkingEngine.org.apache.stanbol.enhancer.engines.entityhublinking.EntityhubLinkingEngine.f7141185-9fe8-4ab9-ad05-fa4988399694
> .config" *file located under "*stanbol/fileinstall*" folder. We added
> fields value under "*enhancer.engines.linking.dereferenceFields*"*  *property.
> But this didn't result in we getting more information for additional fields
> in derefrenced entities.
>
> Do i need to restart stanbol server after editing *.config files ?
> The catch here is on our OS, felix configurations doesnt persist after
> restarting stanbol.
>
> *"3. running Stanbol as WAR within a Tomcat. In Tomcat you can configure
> the headerBufferSize like explained in [3]"
> *
>
> We added stanbol.war to tomcat, however it is throwing an exception on
> opening Felix console. Following is exception stack trace
>
> java.security.AccessControlException: access denied 
> ("java.security.AllPermission" "<all permissions>" "<all actions>")
>       
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:366)
>       
> java.security.AccessController.checkPermission(AccessController.java:560)
>       
> org.apache.stanbol.commons.security.auth.felix.WebConsoleSecurityProvider.authenticate(WebConsoleSecurityProvider.java:54)
>       
> org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext.handleSecurity(OsgiManagerHttpContext.java:104)
>       
> org.apache.felix.http.base.internal.context.ServletContextImpl.handleSecurity(ServletContextImpl.java:272)
>       
> org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:91)
>       
> org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
>       
> org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)
>       
> org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)
>       
> org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
>       
> org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78)
>       
> org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
>       
> org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
>       
> org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78)
>       
> org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
>       
> org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
>       
> org.apache.stanbol.commons.httpqueryheaders.impl.QueryHeadersFilter.doFilter(QueryHeadersFilter.java:75)
>       
> org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
>       
> org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
>       
> org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
>       
> org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
>       
> org.apache.stanbol.commons.web.resources.ResourceServingFilter.doFilterHttp(ResourceServingFilter.java:148)
>       
> org.apache.stanbol.commons.web.resources.ResourceServingFilter.doFilter(ResourceServingFilter.java:91)
>       
> org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
>       
> org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
>       
> org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
>       
> org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
>       
> org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
>       
> org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
>       
> org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>       org.apache.felix.http.proxy.ProxyServlet.service(ProxyServlet.java:60)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>       
> org.apache.sling.launchpad.base.webapp.SlingServletDelegate.service(SlingServletDelegate.java:278)
>       
> org.apache.sling.launchpad.webapp.SlingServlet.service(SlingServlet.java:174)
>
> Best regards
> tarandeep
>
>
>
>
> On Wed, Jul 24, 2013 at 1:00 AM, Fabian Christ <
> christ.fab...@googlemail.com> wrote:
>
>> Hi,
>>
>> just as an additional info. The Stanbol dev mailing list (as any other
>> public list at the ASF) is archived.
>>
>> You can search in this archive, e.g. at http://stanbol.markmail.org/
>>
>> Best,
>>  - Fabian
>>
>> 2013/7/23 Tarandeep Singh, Sawhney <tsawh...@innodata.com>:
>> > thanks so much Rupert for your reaponse.
>> >
>> > i recently joined dev community so wasnt aware of this issue reported
>> > earlier also.
>> >
>> > thanks again and i will try out work around options you have suggested
>> amd
>> > will revert if some more help is needed
>> >
>> > best regards
>> > tarandeep
>> > On Jul 23, 2013 7:57 PM, "Rupert Westenthaler" <
>> > rupert.westentha...@gmail.com> wrote:
>> >
>> >> Hi Tarandeep,
>> >>
>> >> this Issue does not appear the first time here on the list. So you
>> >> might also want to search the archives for more information.
>> >>
>> >> When using the Felix Webconsole to configure an OSGI component the
>> >> size of the configuration MUST NOT exceed the headerBufferSize [1] of
>> >> the embedded Jetty server. For more information see FELIX-3265 [2].
>> >> The problem is that with the currently released version of the Jetty
>> >> plugin it is not possible to configure the headerBufferSize.
>> >>
>> >> To workaround this limitation you have three possibilities:
>> >>
>> >> 1. reduce the size of the configuration (e.g. by removing comment
>> >> lines from the field mappings)
>> >> 2. configure the Site using the configuration file located in
>> >> "stanbol/fileinstall". Make sure that changes to the file confirm to
>> >> the syntax required by the *.config files
>> >> 3. running Stanbol as WAR within a Tomcat. In Tomcat you can configure
>> >> the headerBufferSize like explained in [3]
>> >>
>> >> I usually use option (2)
>> >>
>> >> best
>> >> Rupert
>> >>
>> >>
>> >> [1] http://docs.codehaus.org/display/JETTY/Configuring+Connectors
>> >> [2] https://issues.apache.org/jira/browse/FELIX-3265
>> >> [3]
>> >>
>> http://serverfault.com/questions/56691/whats-the-maximum-url-length-in-tomcat
>> >>
>> >>
>> >> On Tue, Jul 23, 2013 at 3:13 PM, Tarandeep Singh, Sawhney
>> >> <tsawh...@innodata.com> wrote:
>> >> > Hi All,
>> >> >
>> >> > We are facing an issue while adding field mappings beyond 12-14
>> fields as
>> >> > defined in EntityHubLinking Engine property *"Fields used for
>> >> > dereferencing".*
>> >> > *
>> >> > *
>> >> > We have created our own reference site for additional DBpedia data.
>> But
>> >> > when we try to map properties for dereferenced entities beyond above
>> >> limit,
>> >> > felix throws an error *"ajax head full" *and so we are unable to
>> >> configure
>> >> > all the required field mappings.
>> >> >
>> >> > Can you please provide some help for any workaround or point out
>> >> something
>> >> > that we are missing.
>> >> >
>> >> > best regards,
>> >> > tarandeep
>> >> >
>> >> > --
>> >> >
>> >> > "This e-mail and any attachments transmitted with it are for the
>> sole use
>> >> > of the intended recipient(s) and may contain confidential ,
>> proprietary
>> >> or
>> >> > privileged information. If you are not the intended recipient, please
>> >> > contact the sender by reply e-mail and destroy all copies of the
>> original
>> >> > message. Any unauthorized review, use, disclosure, dissemination,
>> >> > forwarding, printing or copying of this e-mail or any action taken in
>> >> > reliance on this e-mail is strictly prohibited and may be unlawful."
>> >>
>> >>
>> >>
>> >> --
>> >> | Rupert Westenthaler             rupert.westentha...@gmail.com
>> >> | Bodenlehenstraße 11                             ++43-699-11108907
>> >> | A-5500 Bischofshofen
>> >>
>> >
>> > --
>> >
>> > "This e-mail and any attachments transmitted with it are for the sole
>> use
>> > of the intended recipient(s) and may contain confidential , proprietary
>> or
>> > privileged information. If you are not the intended recipient, please
>> > contact the sender by reply e-mail and destroy all copies of the
>> original
>> > message. Any unauthorized review, use, disclosure, dissemination,
>> > forwarding, printing or copying of this e-mail or any action taken in
>> > reliance on this e-mail is strictly prohibited and may be unlawful."
>>
>>
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>
>
>

-- 

"This e-mail and any attachments transmitted with it are for the sole use 
of the intended recipient(s) and may contain confidential , proprietary or 
privileged information. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message. Any unauthorized review, use, disclosure, dissemination, 
forwarding, printing or copying of this e-mail or any action taken in 
reliance on this e-mail is strictly prohibited and may be unlawful."

Reply via email to