What ML version are you using?
On Tue, Oct 15, 2013 at 1:30 PM, Kampf, Arne <[email protected]> wrote: > Hi Harry,**** > > ** ** > > Thanks for the fast response. No, I’m not really sure I’m using the > settings correctly, because the system doesn’t behave in the way I expect > it to do… But yes, I increased both settings, the max time limit as well as > the default time limit – so from my point of view the transaction should be > “allowed” to take more than these 600 secs. As another test I reduced the > values to 30 seconds; but without any effect, still 600 secs can be seen in > the host status. As said: this only seems to happen when using the HTTP > server, XDBC shows the “new” values I configured.**** > > ** ** > > Taken from an export of the http server:**** > > <session-timeout>3600</session-timeout>**** > > <max-time-limit>3600</max-time-limit>**** > > <default-time-limit>3600</default-time-limit>**** > > <static-expires>3600</static-expires>**** > > ** ** > > Perhaps a little background: we use the REST interface (HTTP server), a > web service call starts a small function which spawns the “real” > functionality in order to do it asynchronous. Using the XDBC server I > directly start the routine, no spawn in here. Maybe my mistake is in this > kind of call?**** > > ** ** > > Currently I do not use xdmp:set-request-time-limit, because as far as I > understood the default (which I increased) should be used if I don’t set it. > **** > > ** ** > > Regards,**** > > Arne**** > > ** ** > > *Von:* [email protected] [mailto: > [email protected]] *Im Auftrag von *Harry B. > *Gesendet:* Dienstag, 15. Oktober 2013 19:33 > *An:* MarkLogic Developer Discussion > *Betreff:* Re: [MarkLogic Dev General] increase time limit for HTTP > server via admin interface**** > > ** ** > > Are you sure you're using the settings correctly?**** > > ** ** > > There's two settings involved...*max time limit* (default is like 3600) > and *default time limit* (default is 600)**** > > ** ** > > If you increase max time limit, but don't have your application call > xdmp:set-request-time-limit higher than the 600, it will still only allow > 600, which is the default limit. **** > > ** ** > > I think what you want to do is increase the default time limit for that > application in the admin config to 3600. Alternately, you can leave the > default and use xdmp:set-request-time-limit() in your code to go higher, > but no matter what you put in that function, you won't exceed the max time > limit setting...**** > > ** ** > > Hope this helps. It took me a few times fighting this to get the settings > straight in my head. I was thinking of them differently.**** > > ** ** > > On Tue, Oct 15, 2013 at 11:51 AM, Kampf, Arne <[email protected]> > wrote:**** > > Hi all,**** > > **** > > maybe I’m too blind to see, but somehow I can’t figure out where the > problem is…**** > > **** > > I’m trying to increase the default time limit for an HTTP server by > setting the value in the admin console. I can see that this change is > stored, I can retrieve it, if I restart MarkLogic I can see it is still > there. I also changed the session timeout and max time limit, just to be > sure. So far, so good, seems to be fine. But if I start a query on this > server and check the transaction information in the host status (admin > console) I see a limit of 600 sec there, no matter what I set the limit to. > **** > > As another test I started the same routine using an XDBC server, all > limits set to 3600 as an example. And for this server I can see the > expected limit when checking the host status…**** > > **** > > I know that ten minutes should be enough for a transaction “in general”, > but as this is a process which should run only once or twice there is not > much time for improving the implementation.**** > > **** > > Can someone tell me why I can’t seem to set the time limit for the HTTP > server?**** > > **** > > Thanks in advance,**** > > Arne**** > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general**** > > ** ** > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
