As mentioned previously, this is definitely a compatibility problem from jboss 4 to 5.1. Have you moved configuration directly from jboss 4 to jboss 5.1? This is just a guess, but maybe that unknown method is being invoked by reflection based on outdated configuration from jboss 4 ...