Open the server.log file (in the log directory, at the same level as your deploy directoy), and look for the "error" messages which are logged from the top down. This should give you the right clues.
Are the two methods:
and here is my local object.
public MainProjectLocal findByPrimaryKey(Integer pk)throws FinderException;
public Collection findByProjectNames(String project_name) throws FinderException;
on your loacl object like you said or did you mena on your local home object, because they need to be on the local home object.
I have the same problem in 3.2.4. My EAR would deploy (and work) great in 3.2.2, but now that I've upgraded to 3.2.4, I have this problem.
I've even tried copying an existing finder in that bean and renaming it, and I have the same results!
What are the earlier errors that you are getting?
I have the same problem with a .jar-file that deploys without any warnings or errors on jboss 3.0.8....
I've reported this as a bug to sourceforge project page, bug # 994547 (https://sourceforge.net/tracker/index.php?func=detail&aid=994547&group_id=22866&atid=376685)
Please continue discussing this issue there.
FYI (see bug), this bug seems to be fixed in JBoss 3.2.5 :-)
Posted to the bug:
Actually, this cause of this problem seems to be duplicate, different classes deployed, and jboss using the wrong version of the class (outside the jar it is deploying).
It probably would work in 3.2.4 too if the old version of the classes were removed.