Ahah, Obvious really I guess.
Thanks James -----Original Message----- From: Achim Nierbeck [mailto:[email protected]] Sent: 11 December 2014 11:03 To: [email protected] Subject: Re: setting XSS stack size questions Hi if you don't define it, it's using the defaults for the JVM. regards, Achim 2014-12-11 11:35 GMT+01:00 BURN, James <[email protected]>: > Did anyone have any thoughts on this? In particular: > > If I don't define Xss in my /bin/setenv or /etc/KARAF-wrapper.conf > file is this set by default by ServiceMix on startup? If so what is it > set at (and how can I see this)? > > Thanks > > James > > -----Original Message----- > From: BURN, James [mailto:[email protected]] > Sent: 05 November 2014 11:05 > To: users > Subject: setting XSS stack size questions > > Hi > > We experienced an out of memory error which I think was caused by > multiple threads being generated by a camel Jetty route. > > We've worked around this for now and am looking at controlling this > with httpClientMaxThreads or using camel http > > However, it got me looking at the JVM memory settings again. > > Currently we have > -Xms128M -Xmx6144M > > For ServiceMix on an 8Gb server. > > I've not added a Xss on startup yet and was thinking of doing so which > I think may have avoided the error. > > Can someone tell me please: > > If I don't define Xss in my /bin/setenv or /etc/KARAF-wrapper.conf > file is this set by default by ServiceMix on startup? If so what is it > set at (and how can I see this)? > > If not then what is the policy for assigning memory for new threads? > > Are there downsides to setting Xss on ServiceMix startup? > > Thanks > > James > Oxford University Press (UK) Disclaimer > > This message is confidential. You should not copy it or disclose its > contents to anyone. You may use and apply the information for the > intended purpose only. OUP does not accept legal responsibility for > the contents of this message. Any views or opinions presented are > those of the author only and not of OUP. If this email has come to you > in error, please delete it, along with any attachments. Please note > that OUP may intercept incoming and outgoing email communications. > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master Oxford University Press (UK) Disclaimer This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.
