6 Replies Latest reply on Mar 1, 2006 9:31 AM by Annegret Sternagel

    update to JBoss 4.0.4RC1, principal now anonymus

    Annegret Sternagel Newbie

      Hello,

      I updated from JBoss 4.0.3SP1 to JBoss 4.0.4RC1 (installer, including EJB3)
      Now when I call a stateful SessionBean from an other Stateful SessionBean (EJB2) the original principal is no longer propagated but anonymus.
      I didn't change anything in the code or configuration.

      Logging output JBoss 4.0.3SP1

      2006-02-28 14:12:12,129 DEBUG [org.jboss.ejb.StatefulSessionContainer] Created new session ID: ek88q6ox-2p
      2006-02-28 14:12:12,139 DEBUG [org.jboss.ejb.StatefulSessionContainer] Using create method for session: public void com.tenovis.oam.i33.as.sb.SubscriberSBBean.ejbCreate() throws java.rmi.RemoteException,javax.ejb.CreateException
      2006-02-28 14:12:12,139 INFO [com.tenovis.oam.i33.as.sb.SubscriberSBBean] **** SubscriberSB created by AdminUser
      2006-02-28 14:12:12,149 DEBUG [org.jboss.proxy.ejb.ProxyFactory] seting invoker proxy binding for stateful session: stateful-rmi-invoker
      2006-02-28 14:12:14,622 DEBUG [org.jboss.ejb.StatefulSessionContainer] Created new session ID: ek88q8m6-2q
      2006-02-28 14:12:14,622 DEBUG [org.jboss.ejb.StatefulSessionContainer] Using create method for session: public void com.tenovis.oam.i33.as.versionsb.SubscriberSBBean.ejbCreate(java.lang.String) throws java.rmi.RemoteException,javax.ejb.CreateException
      2006-02-28 14:12:14,622 INFO [com.tenovis.oam.i55l030.as.sb.SubscriberSBBean] **** SubscriberSB created by AdminUser
      2006-02-28 14:12:14,622 DEBUG [org.jboss.proxy.ejb.ProxyFactory] seting invoker proxy binding for stateful session: stateful-rmi-invoker
      




      Logging output JBoss 4.0.4RC1
      2006-02-28 14:38:47,942 DEBUG [org.jboss.ejb.StatefulSessionContainer] Created new session ID: ek89oe12-2i
      2006-02-28 14:38:47,942 DEBUG [org.jboss.ejb.StatefulSessionContainer] Using create method for session: public void com.tenovis.oam.i33.as.sb.SubscriberSBBean.ejbCreate() throws java.rmi.RemoteException,javax.ejb.CreateException
      2006-02-28 14:38:47,952 INFO [com.tenovis.oam.i33.as.sb.SubscriberSBBean] **** SubscriberSB created by AdminUser
      2006-02-28 14:38:47,962 DEBUG [org.jboss.proxy.ejb.ProxyFactory] seting invoker proxy binding for stateful session: stateful-rmi-invoker
      2006-02-28 14:38:48,213 DEBUG [org.jboss.ejb.StatefulSessionContainer] Created new session ID: ek89oe8l-2j
      2006-02-28 14:38:48,213 DEBUG [org.jboss.ejb.StatefulSessionContainer] Using create method for session: public void com.tenovis.oam.i33.as.versionsb.SubscriberSBBean.ejbCreate(java.lang.String) throws java.rmi.RemoteException,javax.ejb.CreateException
      2006-02-28 14:38:48,213 INFO [com.tenovis.oam.i55l030.as.sb.SubscriberSBBean] **** SubscriberSB created by anonymous
      2006-02-28 14:38:48,293 DEBUG [org.jboss.proxy.ejb.ProxyFactory] seting invoker proxy binding for stateful session: stateful-rmi-invoker
      



      The configuration of the ejb-jar.xml is
      <session>
       <ejb-name>SubscriberSB</ejb-name>
       <home>com.tenovis.oam.i33.as.sb.SubscriberSBHome</home>
       <remote>com.tenovis.oam.i33.as.sb.SubscriberSB</remote>
       <ejb-class>com.tenovis.oam.i33.as.sb.SubscriberSBBean</ejb-class>
       <session-type>Stateful</session-type>
       <transaction-type>Container</transaction-type>
       <security-identity>
       <run-as>
       <role-name>Internal</role-name>
       </run-as>
       </security-identity>
       <security-role-ref>
       <role-name>Admin</role-name>
       <role-link>Admin</role-link>
       </security-role-ref>
      </session>
      


      The sucurity configuration allows all methods for Admin.

      Is this a bug ?
      Is there a workaround ?

      Annegret