NullPointerExceptions after last night's deployment

12 views
Skip to first unread message

bradford

unread,
Mar 4, 2011, 9:29:33 AM3/4/11
to mongodb-user
I deployed some code last night that serves tons of images from
MongoDB as well as some page content.

I now see my error logs littered with the following:

SEVERE: unexpected error getting config from node: mongo1.foo.com:
27017
java.lang.NullPointerException
at com.mongodb.OutMessage.reset(OutMessage.java:73)
at com.mongodb.OutMessage.<init>(OutMessage.java:51)
at com.mongodb.OutMessage.query(OutMessage.java:38)
at com.mongodb.DBPort.findOne(DBPort.java:142)
at com.mongodb.ReplicaSetStatus
$Node.update(ReplicaSetStatus.java:156)
at
com.mongodb.ReplicaSetStatus.updateAll(ReplicaSetStatus.java:277)
at com.mongodb.ReplicaSetStatus
$Updater.run(ReplicaSetStatus.java:238)
Mar 4, 2011 9:16:30 AM com.mongodb.ReplicaSetStatus$Node update
SEVERE: can't update node: mongo2.foo.com:27017
java.lang.NullPointerException
at com.mongodb.OutMessage.reset(OutMessage.java:73)
at com.mongodb.OutMessage.<init>(OutMessage.java:51)
at com.mongodb.OutMessage.query(OutMessage.java:38)
at com.mongodb.DBPort.findOne(DBPort.java:142)
at com.mongodb.DBPort.runCommand(DBPort.java:159)
at com.mongodb.ReplicaSetStatus
$Node.update(ReplicaSetStatus.java:119)
at
com.mongodb.ReplicaSetStatus.updateAll(ReplicaSetStatus.java:277)
at com.mongodb.ReplicaSetStatus
$Updater.run(ReplicaSetStatus.java:238)
Mar 4, 2011 9:16:35 AM com.mongodb.ReplicaSetStatus$Node update

The application seems running fine, from my quick observation. Any
ideas what's going on?

We use no authentication on our replica sets.

> rs.status()
{
"set" : "foo",
"date" : "Fri Mar 04 2011 08:56:26 GMT-0500 (EST)",
"myState" : 1,
"members" : [
{
"_id" : 0,
"name" : "mongo1.foo.com:27017",
"health" : 1,
"state" : 1,
"self" : true
},
{
"_id" : 1,
"name" : "mongo2.foo.com:27017",
"health" : 1,
"state" : 2,
"uptime" : 4295791,
"lastHeartbeat" : "Fri Mar 04 2011 08:56:25
GMT-0500 (EST)"
},
{
"_id" : 2,
"name" : "arb.foo.com:27017",
"health" : 1,
"state" : 7,
"uptime" : 4295791,
"lastHeartbeat" : "Fri Mar 04 2011 08:56:25
GMT-0500 (EST)"
}
],
"ok" : 1
}

Thanks,
Bradford

bradford

unread,
Mar 4, 2011, 9:38:22 AM3/4/11
to mongodb-user
Also, I'm using version 2.4 of the Mongo Java Driver.

bradford

unread,
Mar 4, 2011, 10:45:16 AM3/4/11
to mongodb-user
I'm also running 1.6.5. I just want to know what's going on and if
this is something critical. It is in production, but I haven't
observed any odd behavior.

In the future, is this something I would need commercial support for
to get an immediate reply? I understand the mailing list is not
support.

Thanks,
Bradford

Eliot Horowitz

unread,
Mar 4, 2011, 11:38:33 AM3/4/11
to mongod...@googlegroups.com
There were a couple of issues fixed for 2.5 (hopefully coming out
today) that should address this.
Nothing to worry about re corruption or data loss beyond the thread
where the exception occurred.

> --
> 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.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>
>

Reply all
Reply to author
Forward
0 new messages