1

So here goes the problem leading to the question...

I have this javaEE application running on jBoss using MongoDB database. I use Morphia to communicate with mongo... The application has the following basic program components;

@EntityListeners(RootEntityListener.class)
public class RootEntity {
    @Id
    protected ObjectId id;
    @Indexed
    protected Long uid;
    @Indexed
    protected boolean active;
    ...
}

@Entity
public class User extends RootEntity {
    ...
}

@Entity
public class News extends RootEntity {
    ...
}

And then my Morphia config looks as follows;

//Morphia Setup
morphia = new Morphia();
morphia.map(User.class).map(News.class);
...

Then I do a query by calling the method shown below;

public List<News> findByUID(Long uId){
    Query<News> query = getNewsQuery().field("active").equal(true).field("uid").equal(uId);
    return query.asList();
}

Fine! So far... no error. But I get a weird warning for each model (User and News). See StackTrace below:

WARNING [org.mongodb.morphia.mapping.DefaultCreator] (http-localhost-127.0.0.1-8080-3) Class not found defined in dbObj: : 
java.lang.ClassNotFoundException: com.package.models.News from [Module "deployment.Wealth.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_45]
at java.lang.Class.forName(Unknown Source) [rt.jar:1.7.0_45]
at org.mongodb.morphia.mapping.DefaultCreator.getClass(DefaultCreator.java:89) [morphia-0.109.jar:]
at org.mongodb.morphia.mapping.DefaultCreator.createInstance(DefaultCreator.java:37) [morphia-0.109.jar:]
at org.mongodb.morphia.mapping.Mapper.fromDBObject(Mapper.java:298) [morphia-0.109.jar:]
at org.mongodb.morphia.query.MorphiaIterator.convertItem(MorphiaIterator.java:79) [morphia-0.109.jar:]
at org.mongodb.morphia.query.MorphiaIterator.processItem(MorphiaIterator.java:65) [morphia-0.109.jar:]
at org.mongodb.morphia.query.MorphiaIterator.next(MorphiaIterator.java:60) [morphia-0.109.jar:]
at org.mongodb.morphia.query.QueryImpl.asList(QueryImpl.java:312) [morphia-0.109.jar:]
at ng.wealth.business.NewsBean.findByActive(NewsBean.java:99) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_45]
...(*the rest omitted for brevity*)...

Now, I have found that this may have something to do with Morphia's class mapping... That org.mongodb.morphia.mapping.DefaultCreator is not loading the entity classes (User and News).

So after much research... and referencing the solution (they say it works) found here https://code.google.com/p/morphia/issues/detail?id=208, I override the org.mongodb.morphia.mapping.DefaultCreator by adding the following to my morphia config;

morphia.getMapper().getOptions().objectFactory = new DefaultCreator() {
    @Override
    protected ClassLoader getClassLoaderForClass() {
        return RootEntity.class.getClassLoader();
    }
};

Note: that in the original solution, the overriden method was getClassLoaderForClass(String clazz, DBObject object) but in my case (due to my version of Morphia - 0.109 - which i believe is probably the most recent obtained from mongo official site), the method is getClassLoaderForClass(). So, I accordingly override it by returning my RootEntity class loader.

But still the WARNING keeps coming. It doesn't necessarily break code because the Classes (User and News) actually get loaded and I can still grab values normally from them. But my logs get flooded with these warnings and perhaps I'm not just comfortable knowing that some part of the application still misbehaves with these strange warnings.

So what I need is a permanent solution to this problem... and a concrete explanation of why the answer actually solves the problem. Thanks y'all!

SourceVisor
  • 1,868
  • 1
  • 27
  • 43

3 Answers3

1

I had the same problem with a Play 2.4 application. For me, this worked:

// Overwrite objectFactorys ClassLoader Method to use Plays ClassLoader
// This prevents the log from beeing spammed with Warning-Messages about ClassNotFoundExceptions happening in Morphias objectFactory
morphia.getMapper().getOptions().setObjectFactory(new DefaultCreator() {
    @Override
    protected ClassLoader getClassLoaderForClass() {
        if(Play.maybeApplication().isDefined()) {
            return Play.classloader(Play.maybeApplication().get());
        } else {
            return PersistedObject.class.getClassLoader();
        }
    }
});

I don't know JavaEE very well, but they too have their own class loading paradigms which you need to take into consideration. Hope it helps.

Community
  • 1
  • 1
Raphael Mäder
  • 776
  • 5
  • 16
  • Thank you. I ran into the same issue with Play 2.5 + Morphia and your solution helped me a lot! – m.w. Jun 08 '17 at 11:49
0

I think the @Id annotation is required. The easy way out would be to add it with @Id protected ObjectId id. Or you ensure that your uid is unique, then you could use @Id protected Long uid (already indexed so @Indexed is then unnecessary).

PS: Not sure if indexing a boolean is worth it, since the cardinality is so low. And for your query you'd need a compound index anyway.

xeraa
  • 10,456
  • 3
  • 33
  • 66
  • Thanks for pointing my mistake. Sorry that was a typo. I've edited the code to look exactly as coded in my project... Still no luck on this issue... `uid` is a simple variable saved for a trivial purpose hence no need to `@id` it. To mention, I've also previously done `@Id protected ObjectId id` in RootEntity before moving it out to the `News` & `User` and the warnings still didn't stop coming... any other ideas? – SourceVisor Jan 15 '15 at 17:35
0

I only just saw this post this morning (coming from your other post) so first, I apologize for that. (The mongodb-users list has a bit more visibility for me but I do try to monitor and respond here when I can.) I just ran your test case on Morphia's master branch and got no weird errors. (master is just a few commits beyond 1.0.1.) If you're not too far down the path of moving to a pure driver solution, I'd recommend 1.0.1 and make sure migrating is necessary.

evanchooly
  • 6,102
  • 1
  • 16
  • 23
  • And yes, `@Id` is definitely required. :) – evanchooly Aug 20 '15 at 13:26
  • Ok... I have the morphia solution on another branch. I'll give the 1.0.1 a shot. Thanks – SourceVisor Aug 21 '15 at 08:10
  • I just gave this a shot and still get the same WARNINGs. even with morphia1.0.1... If i may ask, what does morphia need the *proxytoys* and *cglib-nodep* dependencies for?... I didn't add them to my JBoss module dependencies for morphia, because I figured they're both optional. Could this be the issue? – SourceVisor Aug 21 '15 at 08:58
  • Those are needed for the lazy references. If you're not using lazy references you don't need them. It's odd that you're seeing them when I'm not. I wonder if there's some classloader oddness because of jboss in the mix... – evanchooly Aug 21 '15 at 14:34