Just a hunch, but maybe its the threads package being used on this particular system. For example, on older versions of Linux each thread you spawned was implemented as a separate process.
Joe QWERTY? wrote: > > > > ttmdev wrote: >> >> That is rather strange, because the activemq script starts only one >> instance of the broker. >> >> >> QWERTY? wrote: >>> >>> >>> >>> ttmdev wrote: >>>> >>>> Yup, looks like it. What version of AMQ are you using and are you >>>> using the $ACTIVEMQ_HOME/bin/activemq script to start the broker? >>>> >>>> Joe >>>> >>>> >>> >>> Yes - I just cd into /bin and ./activemq - and off it goes >>> >>> >> >> > > yeh you're telling me, because im running almost the exact same setup on > my other systems the only thing that is different is the database SID > > -- View this message in context: http://www.nabble.com/ActiveMQ-5.0.0-OutOfMemory-tp15814744s2354p15841026.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
