I´m starting to use mongo for a new project, and using the last 2.2.0 and the last 2.9.1 java driver
I´m getting this:
Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: Java heap space
at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223)
at com.mongodb.Mongo$1.createNew(Mongo.java:624)
at com.mongodb.Mongo$1.createNew(Mongo.java:621)
at org.bson.util.SimplePool.get(SimplePool.java:44)
at com.mongodb.OutMessage.<init>(OutMessage.java:132)
at com.mongodb.OutMessage.<init>(OutMessage.java:124)
at com.mongodb.OutMessage.query(OutMessage.java:83)
at com.mongodb.OutMessage.query(OutMessage.java:79)
at com.mongodb.OutMessage.query(OutMessage.java:75)
at com.mongodb.DBPort.findOne(DBPort.java:142)
at com.mongodb.DBPort.runCommand(DBPort.java:148)
at com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 )
at com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614)
at com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766)
at com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736)
Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception
there is no query at all just connected.
I´m connected like this:
static private Mongo M;
static private DB MDB;
M = new Mongo(hosts);
M.setWriteConcern(WriteConcern.SAFE);
MDB= M.getDB( DataBase);
On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
> Hi,
> I´m starting to use mongo for a new project, and using the last 2.2.0 and > the last 2.9.1 java driver
> I´m getting this:
> Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: > Java heap space > at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223) > at com.mongodb.Mongo$1.createNew(Mongo.java:624) > at com.mongodb.Mongo$1.createNew(Mongo.java:621) > at org.bson.util.SimplePool.get(SimplePool.java:44) > at com.mongodb.OutMessage.<init>(OutMessage.java:132) > at com.mongodb.OutMessage.<init>(OutMessage.java:124) > at com.mongodb.OutMessage.query(OutMessage.java:83) > at com.mongodb.OutMessage.query(OutMessage.java:79) > at com.mongodb.OutMessage.query(OutMessage.java:75) > at com.mongodb.DBPort.findOne(DBPort.java:142) > at com.mongodb.DBPort.runCommand(DBPort.java:148) > at > com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 )
> at > com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614)
> at > com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766) > at > com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736) > Exception in thread "ReplicaSetStatus:Updater" Exception in thread > "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" > Exception in thread "ReplicaSetStatus:Updater" Exception in thread > "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" > Exception in thread "ReplicaSetStatus:Updater" Exception
> there is no query at all just connected.
> I´m connected like this:
> static private Mongo M; > static private DB MDB;
> M = new Mongo(hosts); > M.setWriteConcern(WriteConcern.SAFE); > MDB= M.getDB( DataBase);
> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
> Hi,
> I´m starting to use mongo for a new project, and using the last 2.2.0 and the last 2.9.1 java driver
> I´m getting this:
> Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: Java heap space > at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223) > at com.mongodb.Mongo$1.createNew(Mongo.java:624) > at com.mongodb.Mongo$1.createNew(Mongo.java:621) > at org.bson.util.SimplePool.get(SimplePool.java:44) > at com.mongodb.OutMessage.<init>(OutMessage.java:132) > at com.mongodb.OutMessage.<init>(OutMessage.java:124) > at com.mongodb.OutMessage.query(OutMessage.java:83) > at com.mongodb.OutMessage.query(OutMessage.java:79) > at com.mongodb.OutMessage.query(OutMessage.java:75) > at com.mongodb.DBPort.findOne(DBPort.java:142) > at com.mongodb.DBPort.runCommand(DBPort.java:148) > at com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 ) > at com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614) > at com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766) > at com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736) > Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception
> there is no query at all just connected.
> I´m connected like this:
> static private Mongo M; > static private DB MDB;
> M = new Mongo(hosts); > M.setWriteConcern(WriteConcern.SAFE); > MDB= M.getDB( DataBase);
> best regard.
> -- > You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>> Hi,
>> I´m starting to use mongo for a new project, and using the last 2.2.0 and
>> the last 2.9.1 java driver
>> I´m getting this:
>> Exception in thread "ReplicaSetStatus:Updater"
>> java.lang.OutOfMemoryError: Java heap space
>> at org.bson.io.PoolOutputBuffer.<**init>(PoolOutputBuffer.java:**223)
>> at com.mongodb.Mongo$1.createNew(**Mongo.java:624)
>> at com.mongodb.Mongo$1.createNew(**Mongo.java:621)
>> at org.bson.util.SimplePool.get(**SimplePool.java:44)
>> at com.mongodb.OutMessage.<init>(**OutMessage.java:132)
>> at com.mongodb.OutMessage.<init>(**OutMessage.java:124)
>> at com.mongodb.OutMessage.query(**OutMessage.java:83)
>> at com.mongodb.OutMessage.query(**OutMessage.java:79)
>> at com.mongodb.OutMessage.query(**OutMessage.java:75)
>> at com.mongodb.DBPort.findOne(**DBPort.java:142)
>> at com.mongodb.DBPort.runCommand(**DBPort.java:148)
>> at com.mongodb.ConnectionStatus$**UpdatableNode.update(**ConnectionStatus.java :184)
>> at com.mongodb.ReplicaSetStatus$**UpdatableReplicaSetNode.**
>> update(ReplicaSetStatus.java:**614)
>> at com.mongodb.ReplicaSetStatus$**Updater.updateAll(**ReplicaSetStatus.java:76 6)
>> at com.mongodb.ReplicaSetStatus$**Updater.run(ReplicaSetStatus.**java:736)
>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread
>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater"
>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread
>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater"
>> Exception in thread "ReplicaSetStatus:Updater" Exception
>> there is no query at all just connected.
>> I´m connected like this:
>> static private Mongo M;
>> static private DB MDB;
>> M = new Mongo(hosts);
>> M.setWriteConcern(**WriteConcern.SAFE);
>> MDB= M.getDB( DataBase);
>> best regard.
> --
> You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
> --
> You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
>> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>> Hi,
>> I´m starting to use mongo for a new project, and using the last 2.2.0 and the last 2.9.1 java driver
>> I´m getting this:
>> Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: Java heap space >> at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223) >> at com.mongodb.Mongo$1.createNew(Mongo.java:624) >> at com.mongodb.Mongo$1.createNew(Mongo.java:621) >> at org.bson.util.SimplePool.get(SimplePool.java:44) >> at com.mongodb.OutMessage.<init>(OutMessage.java:132) >> at com.mongodb.OutMessage.<init>(OutMessage.java:124) >> at com.mongodb.OutMessage.query(OutMessage.java:83) >> at com.mongodb.OutMessage.query(OutMessage.java:79) >> at com.mongodb.OutMessage.query(OutMessage.java:75) >> at com.mongodb.DBPort.findOne(DBPort.java:142) >> at com.mongodb.DBPort.runCommand(DBPort.java:148) >> at com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 ) >> at com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614) >> at com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766) >> at com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736) >> Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception
>> there is no query at all just connected.
>> I´m connected like this:
>> static private Mongo M; >> static private DB MDB;
>> M = new Mongo(hosts); >> M.setWriteConcern(WriteConcern.SAFE); >> MDB= M.getDB( DataBase);
>> best regard.
>> -- >> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb
> -- > You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
> -- > You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
> From: Sebastian Gutierrez <scg...@gmail.com>
> Subject: Re: [mongodb-user] Problem with mongo 2.2.0 and java connection
> Date: October 9, 2012 9:38:06 AM GMT-02:00
> To: mongodb-user@googlegroups.com
> yes is a war file
> is executed one, and is on a singleton class, in the startup of the application.
>>> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>>> Hi,
>>> I´m starting to use mongo for a new project, and using the last 2.2.0 and the last 2.9.1 java driver
>>> I´m getting this:
>>> Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: Java heap space >>> at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223) >>> at com.mongodb.Mongo$1.createNew(Mongo.java:624) >>> at com.mongodb.Mongo$1.createNew(Mongo.java:621) >>> at org.bson.util.SimplePool.get(SimplePool.java:44) >>> at com.mongodb.OutMessage.<init>(OutMessage.java:132) >>> at com.mongodb.OutMessage.<init>(OutMessage.java:124) >>> at com.mongodb.OutMessage.query(OutMessage.java:83) >>> at com.mongodb.OutMessage.query(OutMessage.java:79) >>> at com.mongodb.OutMessage.query(OutMessage.java:75) >>> at com.mongodb.DBPort.findOne(DBPort.java:142) >>> at com.mongodb.DBPort.runCommand(DBPort.java:148) >>> at com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 ) >>> at com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614) >>> at com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766) >>> at com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736) >>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception
>>> there is no query at all just connected.
>>> I´m connected like this:
>>> static private Mongo M; >>> static private DB MDB;
>>> M = new Mongo(hosts); >>> M.setWriteConcern(WriteConcern.SAFE); >>> MDB= M.getDB( DataBase);
>>> best regard.
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongodb-user@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> mongodb-user+unsubscribe@googlegroups.com
>>> See also the IRC channel -- freenode.net#mongodb
>> -- >> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb
>> -- >> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb
>> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>>> Hi,
>>> I´m starting to use mongo for a new project, and using the last 2.2.0
>>> and the last 2.9.1 java driver
>>> I´m getting this:
>>> Exception in thread "ReplicaSetStatus:Updater"
>>> java.lang.OutOfMemoryError: Java heap space
>>> at org.bson.io.PoolOutputBuffer.<**init>(PoolOutputBuffer.java:*
>>> *223)
>>> at com.mongodb.Mongo$1.createNew(**Mongo.java:624)
>>> at com.mongodb.Mongo$1.createNew(**Mongo.java:621)
>>> at org.bson.util.SimplePool.get(**SimplePool.java:44)
>>> at com.mongodb.OutMessage.<init>(**OutMessage.java:132)
>>> at com.mongodb.OutMessage.<init>(**OutMessage.java:124)
>>> at com.mongodb.OutMessage.query(**OutMessage.java:83)
>>> at com.mongodb.OutMessage.query(**OutMessage.java:79)
>>> at com.mongodb.OutMessage.query(**OutMessage.java:75)
>>> at com.mongodb.DBPort.findOne(**DBPort.java:142)
>>> at com.mongodb.DBPort.runCommand(**DBPort.java:148)
>>> at com.mongodb.ConnectionStatus$**UpdatableNode.update(**ConnectionStatus.java :184)
>>> at com.mongodb.ReplicaSetStatus$**UpdatableReplicaSetNode.**
>>> update(ReplicaSetStatus.java:**614)
>>> at com.mongodb.ReplicaSetStatus$**Updater.updateAll(**ReplicaSetStatus.java:76 6)
>>> at com.mongodb.ReplicaSetStatus$**Updater.run(ReplicaSetStatus.*
>>> *java:736)
>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread
>>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater"
>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread
>>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater"
>>> Exception in thread "ReplicaSetStatus:Updater" Exception
>>> there is no query at all just connected.
>>> I´m connected like this:
>>> static private Mongo M;
>>> static private DB MDB;
>>> M = new Mongo(hosts);
>>> M.setWriteConcern(**WriteConcern.SAFE);
>>> MDB= M.getDB( DataBase);
>>> best regard.
>> --
>> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb
>> --
>> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb<http://freenode.net/#mongodb>
> --
> You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
> --
> You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
octavian.covals...@gmail.com> wrote:
> What framework are you using to create your web app? Can you check the
> actual memory usage with visualvm tool?
> Also, can you create a simple console app with the same code used and
> connect to mongodb? Maybe this will narrow it down...
> On Wed, Oct 10, 2012 at 7:55 AM, Sebastian Gutierrez <scg...@gmail.com>wrote:
>> any idea???
>> I´m totally lost with this.
>> thanks
>> Begin forwarded message:
>> *From: *Sebastian Gutierrez <scg...@gmail.com>
>> *Subject: **Re: [mongodb-user] Problem with mongo 2.2.0 and java
>> connection*
>> *Date: *October 9, 2012 9:38:06 AM GMT-02:00
>> *To: *mongodb-user@googlegroups.com
>> yes is a war file
>> is executed one, and is on a singleton class, in the startup of the
>> application.
>> this is a jetty server that deploys the war file, as I said, is doing
>> nothing just starting, same arquitecture I have with mysql with no problems.
>> thanks
>> On Oct 8, 2012, at 3:29 PM, Octavian Covalschi <
>> octavian.covals...@gmail.com> wrote:
>> Is this a web app? Are you passing any jvm args at all? Also, is this
>> code executed only once? If yes, when?
>> On Mon, Oct 8, 2012 at 10:43 AM, Sebastian Gutierrez <scg...@gmail.com>wrote:
>>> compiling on mac, running on linux
>>> java version "1.7.0_07"
>>> Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
>>> Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
>>> same arquitecture I have with mysql, remember this is doing nothing. is
>>> just when starts, until my server goes down…..
>>> ReplicaSetStatus is not from my code..
>>> any idea?
>>> thanks!
>>> On Oct 8, 2012, at 1:01 PM, Gianfranco <gianfra...@10gen.com> wrote:
>>> In what platform are you compiling this? Windows, Mac, Linux, etc?
>>> See this page for more info on this JVM heap issue:
>>> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>>>> Hi,
>>>> I´m starting to use mongo for a new project, and using the last 2.2.0
>>>> and the last 2.9.1 java driver
>>>> I´m getting this:
>>>> Exception in thread "ReplicaSetStatus:Updater"
>>>> java.lang.OutOfMemoryError: Java heap space
>>>> at org.bson.io.PoolOutputBuffer.<**init>(PoolOutputBuffer.java:
>>>> **223)
>>>> at com.mongodb.Mongo$1.createNew(**Mongo.java:624)
>>>> at com.mongodb.Mongo$1.createNew(**Mongo.java:621)
>>>> at org.bson.util.SimplePool.get(**SimplePool.java:44)
>>>> at com.mongodb.OutMessage.<init>(**OutMessage.java:132)
>>>> at com.mongodb.OutMessage.<init>(**OutMessage.java:124)
>>>> at com.mongodb.OutMessage.query(**OutMessage.java:83)
>>>> at com.mongodb.OutMessage.query(**OutMessage.java:79)
>>>> at com.mongodb.OutMessage.query(**OutMessage.java:75)
>>>> at com.mongodb.DBPort.findOne(**DBPort.java:142)
>>>> at com.mongodb.DBPort.runCommand(**DBPort.java:148)
>>>> at com.mongodb.ConnectionStatus$**UpdatableNode.update(**ConnectionStatus.java :184)
>>>> at com.mongodb.ReplicaSetStatus$**UpdatableReplicaSetNode.**
>>>> update(ReplicaSetStatus.java:**614)
>>>> at com.mongodb.ReplicaSetStatus$**Updater.updateAll(**ReplicaSetStatus.java:76 6)
>>>> at com.mongodb.ReplicaSetStatus$**Updater.run(ReplicaSetStatus.
>>>> **java:736)
>>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread
>>>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater"
>>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread
>>>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater"
>>>> Exception in thread "ReplicaSetStatus:Updater" Exception
>>>> there is no query at all just connected.
>>>> I´m connected like this:
>>>> static private Mongo M;
>>>> static private DB MDB;
>>>> M = new Mongo(hosts);
>>>> M.setWriteConcern(**WriteConcern.SAFE);
>>>> MDB= M.getDB( DataBase);
>>>> best regard.
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongodb-user@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> mongodb-user+unsubscribe@googlegroups.com
>>> See also the IRC channel -- freenode.net#mongodb
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongodb-user@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> mongodb-user+unsubscribe@googlegroups.com
>>> See also the IRC channel -- freenode.net#mongodb<http://freenode.net/#mongodb>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb
>> --
>> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongodb-user@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongodb-user+unsubscribe@googlegroups.com
>> See also the IRC channel -- freenode.net#mongodb
JAX and Jersey for RESTFull webservice, as I said, everything is the same as I have on other apps that serves many connections with mysql with no problem.
is there anyway to give more log?? or give someone access to check? Im evaluating NoSQL databases for a big project, and Mongo seems like the one I would like to use, but I feel like I can´t even start with
it, I also tested driver 2.8.1 with the same result.
maybe some mongo configuration??? I haven´t touch any config since install
I will try to make a console application as soon as I can.
thanks
On Oct 10, 2012, at 11:06 AM, Octavian Covalschi <octavian.covals...@gmail.com> wrote:
> What framework are you using to create your web app? Can you check the actual memory usage with visualvm tool?
> Also, can you create a simple console app with the same code used and connect to mongodb? Maybe this will narrow it down...
> On Wed, Oct 10, 2012 at 7:55 AM, Sebastian Gutierrez <scg...@gmail.com> wrote:
> any idea???
> I´m totally lost with this.
> thanks
> Begin forwarded message:
>> From: Sebastian Gutierrez <scg...@gmail.com>
>> Subject: Re: [mongodb-user] Problem with mongo 2.2.0 and java connection
>> Date: October 9, 2012 9:38:06 AM GMT-02:00
>> To: mongodb-user@googlegroups.com
>> yes is a war file
>> is executed one, and is on a singleton class, in the startup of the application.
>>>> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>>>> Hi,
>>>> I´m starting to use mongo for a new project, and using the last 2.2.0 and the last 2.9.1 java driver
>>>> I´m getting this:
>>>> Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: Java heap space >>>> at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223) >>>> at com.mongodb.Mongo$1.createNew(Mongo.java:624) >>>> at com.mongodb.Mongo$1.createNew(Mongo.java:621) >>>> at org.bson.util.SimplePool.get(SimplePool.java:44) >>>> at com.mongodb.OutMessage.<init>(OutMessage.java:132) >>>> at com.mongodb.OutMessage.<init>(OutMessage.java:124) >>>> at com.mongodb.OutMessage.query(OutMessage.java:83) >>>> at com.mongodb.OutMessage.query(OutMessage.java:79) >>>> at com.mongodb.OutMessage.query(OutMessage.java:75) >>>> at com.mongodb.DBPort.findOne(DBPort.java:142) >>>> at com.mongodb.DBPort.runCommand(DBPort.java:148) >>>> at com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 ) >>>> at com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614) >>>> at com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766) >>>> at com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736) >>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" Exception
>>>> there is no query at all just connected.
>>>> I´m connected like this:
>>>> static private Mongo M; >>>> static private DB MDB;
>>>> M = new Mongo(hosts); >>>> M.setWriteConcern(WriteConcern.SAFE); >>>> MDB= M.getDB( DataBase);
>>>> best regard.
>>>> -- >>>> You received this message because you are subscribed to the Google
>>>> Groups "mongodb-user" group.
>>>> To post to this group, send email to mongodb-user@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> mongodb-user+unsubscribe@googlegroups.com
>>>> See also the IRC channel -- freenode.net#mongodb
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongodb-user@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> mongodb-user+unsubscribe@googlegroups.com
>>> See also the IRC channel -- freenode.net#mongodb
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongodb-user@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> mongodb-user+unsubscribe@googlegroups.com
>>> See also the IRC channel -- freenode.net#mongodb
> -- > You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
> -- > You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongodb-user@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user+unsubscribe@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb
On Wednesday, October 10, 2012 10:55:43 AM UTC-4, Sebastian Gutierrez wrote:
> the components are:
> JAX and Jersey for RESTFull webservice, as I said, everything is the same > as I have on other apps that serves many connections with mysql with no > problem.
> is there anyway to give more log?? or give someone access to check? Im > evaluating NoSQL databases for a big project, and Mongo seems like the one > I would like to use, but I feel like I can´t even start with
> it, I also tested driver 2.8.1 with the same result.
> maybe some mongo configuration??? I haven´t touch any config since install
> I will try to make a console application as soon as I can.
> thanks
> On Oct 10, 2012, at 11:06 AM, Octavian Covalschi <octavian....@gmail.com<javascript:>> > wrote:
> What framework are you using to create your web app? Can you check the > actual memory usage with visualvm tool?
> Also, can you create a simple console app with the same code used and > connect to mongodb? Maybe this will narrow it down...
> On Wed, Oct 10, 2012 at 7:55 AM, Sebastian Gutierrez <scg...@gmail.com<javascript:>
> > wrote:
>> any idea???
>> I´m totally lost with this.
>> thanks
>> Begin forwarded message:
>> *From: *Sebastian Gutierrez <scg...@gmail.com <javascript:>>
>> *Subject: **Re: [mongodb-user] Problem with mongo 2.2.0 and java >> connection*
>> *Date: *October 9, 2012 9:38:06 AM GMT-02:00
>> *To: *mongod...@googlegroups.com <javascript:>
>> yes is a war file
>> is executed one, and is on a singleton class, in the startup of the >> application.
>> this is a jetty server that deploys the war file, as I said, is doing >> nothing just starting, same arquitecture I have with mysql with no problems.
>> thanks
>> On Oct 8, 2012, at 3:29 PM, Octavian Covalschi <octavian....@gmail.com<javascript:>> >> wrote:
>> Is this a web app? Are you passing any jvm args at all? Also, is this >> code executed only once? If yes, when?
>> On Mon, Oct 8, 2012 at 10:43 AM, Sebastian Gutierrez <scg...@gmail.com<javascript:>
>> > wrote:
>>> compiling on mac, running on linux
>>> java version "1.7.0_07"
>>> Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
>>> Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
>>> same arquitecture I have with mysql, remember this is doing nothing. is >>> just when starts, until my server goes down…..
>>> ReplicaSetStatus is not from my code..
>>> any idea?
>>> thanks!
>>> On Oct 8, 2012, at 1:01 PM, Gianfranco <gianf...@10gen.com <javascript:>> >>> wrote:
>>> In what platform are you compiling this? Windows, Mac, Linux, etc?
>>> See this page for more info on this JVM heap issue:
>>> On Monday, October 8, 2012 3:25:29 PM UTC+1, Sebastian Gutierrez wrote:
>>>> Hi,
>>>> I´m starting to use mongo for a new project, and using the last 2.2.0 >>>> and the last 2.9.1 java driver
>>>> I´m getting this:
>>>> Exception in thread "ReplicaSetStatus:Updater" >>>> java.lang.OutOfMemoryError: Java heap space >>>> at org.bson.io.PoolOutputBuffer.<**init>(PoolOutputBuffer.java:
>>>> **223) >>>> at com.mongodb.Mongo$1.createNew(**Mongo.java:624) >>>> at com.mongodb.Mongo$1.createNew(**Mongo.java:621) >>>> at org.bson.util.SimplePool.get(**SimplePool.java:44) >>>> at com.mongodb.OutMessage.<init>(**OutMessage.java:132) >>>> at com.mongodb.OutMessage.<init>(**OutMessage.java:124) >>>> at com.mongodb.OutMessage.query(**OutMessage.java:83) >>>> at com.mongodb.OutMessage.query(**OutMessage.java:79) >>>> at com.mongodb.OutMessage.query(**OutMessage.java:75) >>>> at com.mongodb.DBPort.findOne(**DBPort.java:142) >>>> at com.mongodb.DBPort.runCommand(**DBPort.java:148) >>>> at com.mongodb.ConnectionStatus$**UpdatableNode.update(**ConnectionStatus.java :184)
>>>> at com.mongodb.ReplicaSetStatus$**UpdatableReplicaSetNode.**
>>>> update(ReplicaSetStatus.java:**614) >>>> at com.mongodb.ReplicaSetStatus$**Updater.updateAll(**ReplicaSetStatus.java:76 6)
>>>> at com.mongodb.ReplicaSetStatus$**Updater.run(ReplicaSetStatus.
>>>> **java:736) >>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread >>>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" >>>> Exception in thread "ReplicaSetStatus:Updater" Exception in thread >>>> "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" >>>> Exception in thread "ReplicaSetStatus:Updater" Exception
>>>> there is no query at all just connected.
>>>> I´m connected like this:
>>>> static private Mongo M; >>>> static private DB MDB;
>>>> M = new Mongo(hosts); >>>> M.setWriteConcern(**WriteConcern.SAFE); >>>> MDB= M.getDB( DataBase);
>>>> best regard.
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongod...@googlegroups.com<javascript:>
>>> To unsubscribe from this group, send email to
>>> mongodb-user...@googlegroups.com <javascript:>
>>> See also the IRC channel -- freenode.net#mongodb
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "mongodb-user" group.
>>> To post to this group, send email to mongod...@googlegroups.com<javascript:>
>>> To unsubscribe from this group, send email to
>>> mongodb-user...@googlegroups.com <javascript:>
>>> See also the IRC channel -- freenode.net#mongodb<http://freenode.net/#mongodb>
>> -- >> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongod...@googlegroups.com<javascript:>
>> To unsubscribe from this group, send email to
>> mongodb-user...@googlegroups.com <javascript:>
>> See also the IRC channel -- freenode.net#mongodb
>> -- >> You received this message because you are subscribed to the Google
>> Groups "mongodb-user" group.
>> To post to this group, send email to mongod...@googlegroups.com<javascript:>
>> To unsubscribe from this group, send email to
>> mongodb-user...@googlegroups.com <javascript:>
>> See also the IRC channel -- freenode.net#mongodb<http://freenode.net/#mongodb>
> -- > You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com<javascript:>
> To unsubscribe from this group, send email to
> mongodb-user...@googlegroups.com <javascript:>
> See also the IRC channel -- freenode.net#mongodb
I agree with the recommendations to try VisualVM (or even jconsole) or jmap. VisualVM will be very helpful for monitoring heap growth before and after you connect to MongoDB, as well as for checking which classes' objects are occupying most of the heap.
You might also want to try the following JVM args:
This will write a log file with a lot of useful info on heap usage and garbage collection. You can then tail it while connecting. Make sure the argument to -Xloggc includes a relative or absolute path to a directory your webapp can write to, such as your webapp's existing log directory.
I've used the above JVM args to track down several memory-related problems. The overhead is pretty small, so I use those settings in production with an app that has a 55 GB heap.
On Monday, October 8, 2012 7:25:29 AM UTC-7, Sebastian Gutierrez wrote:
> Hi,
> I´m starting to use mongo for a new project, and using the last 2.2.0 and > the last 2.9.1 java driver
> I´m getting this:
> Exception in thread "ReplicaSetStatus:Updater" java.lang.OutOfMemoryError: > Java heap space > at org.bson.io.PoolOutputBuffer.<init>(PoolOutputBuffer.java:223) > at com.mongodb.Mongo$1.createNew(Mongo.java:624) > at com.mongodb.Mongo$1.createNew(Mongo.java:621) > at org.bson.util.SimplePool.get(SimplePool.java:44) > at com.mongodb.OutMessage.<init>(OutMessage.java:132) > at com.mongodb.OutMessage.<init>(OutMessage.java:124) > at com.mongodb.OutMessage.query(OutMessage.java:83) > at com.mongodb.OutMessage.query(OutMessage.java:79) > at com.mongodb.OutMessage.query(OutMessage.java:75) > at com.mongodb.DBPort.findOne(DBPort.java:142) > at com.mongodb.DBPort.runCommand(DBPort.java:148) > at > com.mongodb.ConnectionStatus$UpdatableNode.update(ConnectionStatus.java:184 )
> at > com.mongodb.ReplicaSetStatus$UpdatableReplicaSetNode.update(ReplicaSetStatu s.java:614)
> at > com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:766) > at > com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:736) > Exception in thread "ReplicaSetStatus:Updater" Exception in thread > "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" > Exception in thread "ReplicaSetStatus:Updater" Exception in thread > "ReplicaSetStatus:Updater" Exception in thread "ReplicaSetStatus:Updater" > Exception in thread "ReplicaSetStatus:Updater" Exception
> there is no query at all just connected.
> I´m connected like this:
> static private Mongo M; > static private DB MDB;
> M = new Mongo(hosts); > M.setWriteConcern(WriteConcern.SAFE); > MDB= M.getDB( DataBase);