0 Replies Latest reply on May 13, 2009 11:25 PM by Joseph Wroblewski

    EBJContext exception in websphere -- may be causing memory leak

    Joseph Wroblewski Newbie
      Using Seam 2.1.1 GA
      Websphere 6.1 with EJB3 feature pack

      I get the following exception in websphere only (no problems in JBoss):

      |com.ibm.wsspi.injectionengine.InjectionException: EJBContext may only be looked up by or injected into an EJB
              at com.ibm.ws.ejbcontainer.injection.factory.EJBContextObjectFactory.getObjectInstance(EJBContextObjectFactory.java:84)
              at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
              at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:917)|

      Though these exception occur in the log, the application works fine. However, after extended usage, performance begins to degrade quickly.  IBM analysis indicates extensive garbage collection due to probable memory leak.

      It happens in two methods.  The only thing I have found in common so far is both methods are using "out"- jection

      @Out(scope = ScopeType.BUSINESS_PROCESS, required=false)

      Any clues are welcome.