error found in hot deploy/redeploy

[fkclai]

"fkclai" wrote:

"fkclai" wrote:
Dear all,

I am working on a web application using jboss-3.0.1 and tomcat-4.0.4 and found a redeploy problem.

I deploy the war(for jsp,sevrlet) and jar(for session bean) into the jboss, both deployment is success without error and the application work without problem.

BUT, WHEN I update the session bean and redeploy the jar again. the jar is deployed success without error, PROBLEM is my application doesn't work again, the following error show in the console. It seem can't located my EBSHolidaySrvHome which I haven't updated it.

**BUT After restart the JBoss, the problem solved, What is the reason? is it mean I need to restart the Jboss everytime for every updated on EJB?

Remark: it does not happen in war(JSP, Sevrlet).

thanks a lot,
Calvin Lai

10:51:47,930 ERROR [LogInterceptor] EJBException:
javax.ejb.EJBException: Invalid invocation, check your deployment packaging, method=public abstract gov.eitsd.ebs.ejb.service.EBSHolidaySrv gov.eitsd.ebs.ejb.service.EBSHolidaySrvHome.create() throws javax.ejb.CreateException,java.rmi.RemoteException
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invokeHo
me(StatelessSessionContainer.java:597)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invo
keHome(CachedConnectionInterceptor.java:206)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invokeHome(
StatelessSessionInstanceInterceptor.java:57)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInte
rceptor.java:111)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxIntercep
torCMT.java:178)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.ja
va:52)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityIntercep
tor.java:105)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:1
29)
at org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSessionCo
ntainer.java:300)

[juha]

If you're packaging the WAR and EJB jar separately you need to redeploy them both (or package them into a single EAR).

[fkclai]

Dear Juha Lindfors

Thanks a lot of your reply, following your suggestion, I have redeployed both war and EJB jar again OR package them into a single EAR. BUT the problem is same.

The problem still not solve.

Any people can help????

Thanks,
Calvin Lai