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).

This entry was posted in Java and tagged , . Bookmark the permalink.

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

  1. Phill says:

    Wow :) Thanks you saved me from going grey :p

  2. Nasseria says:

    Thanks, it was a applicable solution:)

  3. maosmurf says:

    Thanks!

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

  4. xwrs says:

    Glassfish suxxx

  5. llaith says:

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

    Ta.

  6. 1.april says:

    saved the day!! thanks

  7. замена батарей отопления в квартире says:

    ок :-) здорово

  8. Colin says:

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

    Thanks!

  9. Bahram Jowharshamshiri says:

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

  10. Ayesha says:

    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!!!” :D

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">