we are running JDI and EnterprisePortal (WAS 6.40, SPS 16) for developing on the same server. The server is shutting down each night for offline backup and is going online again next morning. In our project we are using Web Dypro, EJBs and Spring.
After deploying either directly from DevStudio or via auto deploy from CBS everything is working as expected. But after restart of the server we get a ClassCastException during bean lookup in Web Dynpro. It seems that the bean instance on server side is not in line with the bean instance used by client side.
Could the following be happened?
After restart, the server initializes the EJBs. Afterwards the JDI is automatically (???) deploying the client DC package (including client bean). Later when using the bean, we have two different versions of the bean and therefore a ClassCastException arises.
We implemented the Springframework according to the description in HowTo "Spring Integration on SAP NetWeaver" (https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/73af6078-0801-0010-8fa1-deaa9647c5dd). A brief review of the server default trace log did not bring up any hints.
Is it possible that the order of starting the processes (J2EE Engine, JDI, EP) during server restart plays an important role?
Is there anybody who has some ideas?
Thanks and best regards