A hint for the “Object foo is not a known entity type” errors from Glassfish

As a JavaEE-codemonkey you have perhaps noticed this error:

java.lang.IllegalArgumentException: Object: Ting@193c227 is not a known entity type.

This will occur when you have redeployed an app f.ex through Eclipse to Glassfish, the Glassfish server has not quite understood that it`s time to update its version, so what you need to do then is to simply restart the server (or domain).

10 thoughts on “A hint for the “Object foo is not a known entity type” errors from Glassfish

  1. Thanks!

    After googling for over 1hr, you had the correct answer 🙂

  2. Again, a simple thing but it worked. After 30 mins of frustration, you saved me at least the same again!

    Ta.

  3. ок 🙂 здорово

  4. I had this exact problem, but with JDeveloper and its’ integrated Weblogic server. A restart solved it 🙂

    Thanks!

  5. Thanks. You saved me a lot of frustration. I wish someone would create a website for small tips like this one.

  6. I did that anyway and was feeling kinda stupid… then saw ur post.. now i’m like “okay, so thr r more ppl who think like me!!!” 😀