'credentials token expired' exception in WAS - Websphere

This is a discussion on 'credentials token expired' exception in WAS - Websphere ; Currently our 'heaviest' IBM-AIX-WAS related problem is 'credentials token expired'. We tried DDC and other options. We therefore turned for the IBM support, as described below. Unfortunatley, it doesn't seem to be 'to the point' (their recommendation is to upgrade). ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: 'credentials token expired' exception in WAS

  1. 'credentials token expired' exception in WAS

    Currently our 'heaviest' IBM-AIX-WAS related problem is 'credentials
    token expired'.

    We tried DDC and other options.

    We therefore turned for the IBM support, as described below.

    Unfortunatley, it doesn't seem to be 'to the point' (their
    recommendation is to upgrade).

    Does anyone has more productive suggestions to solve this problem
    without upgrading the WAS

    Regards,


    ______________________________________________


    ================================================== =========================================

    Hi ,

    Thanks for the update.
    Since you were only able to re-send the output snippet from the
    original update, not sure how much that will add in our investigation
    of this issue. Currently WAS v5.1.1.1 is being
    used, the current recommended update for WAS is: v5.1.1.3, see
    the document below.

    Title: Recommended Updates for WebSphere Application Server Base
    and Network Deployment editions
    Url:
    http://www-1.ibm.com/support/docview...swg27004980#51

    WAS version 5.1.1.3 is at:

    Title: 5.1.1.3: WebSphere Application Server Version 5.1.1
    Cumulative Fix 3
    Url:
    http://www-1.ibm.com/support/docview...=utf-8&lang=en

    Please apply the recommended WAS version 5.1.1.3, to see if it
    addresses this issue.

    Best Regards,
    Harry

    ================================================== ===========================================

    Hi.

    Here is the whole exception, snippet of which I've sent you before:


    [4/6/05 15:47:50:169 EEST] 3aefab8c SASRas E JSAS0202E:
    [CSICredentialsManager.getClientSubject] Credential token expired.
    org.omg.CORBA.NO_PERMISSION vmcid: 0x49424000 minor code: 306
    completed: No
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSICredent ialsManager.getClientSubject(CSICredentialsManager .java:580)
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I$2.run(CSIClientRI.java:443)
    at
    com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:111)
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I.send_request(CSIClientRI.java:439)
    at
    com.ibm.rmi.pi.InterceptorManager.iterateSendReque st(InterceptorManager.java:404)
    at
    com.ibm.rmi.iiop.ClientRequestImpl.(ClientRequestImpl.java:136)
    at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:141)
    at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:97)
    at
    com.ibm.rmi.corba.ClientDelegate._createRequest(Cl ientDelegate.java:1854)
    at
    com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1132)
    at
    com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1285)
    at
    com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1065)
    at
    com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1251)
    at
    com.ibm.rmi.corba.ClientDelegate.request(ClientDel egate.java:1731)
    at
    com.ibm.CORBA.iiop.ClientDelegate.request(ClientDe legate.java:1207)
    at
    org.omg.CORBA.portable.ObjectImpl._request(ObjectI mpl.java:460)
    at
    ..oms.simulator._Simulator_Stub.remove(_Simulator_ Stub.java:116)
    at amdocs.oms.connector.EjbClient.Dispose(EjbClient.j ava:328)
    at .oms.infra.IlSession.DisposeAllClients(IlSession.j ava:719)
    at amdocs.oms.infra.IlSession.onTerminate(IlSession.j ava:641)
    at
    ..epi.session.EpiSessionContext.remove(EpiSessionC ontext.java:1974)
    at
    ..epi.session.InternalSessionContext.remove(Intern alSessionContext.java:212)
    at
    ..epi.session.EpiStatelessSessionBean.remove(EpiSt atelessSessionBean.java:92)
    at
    ..epi.proxy.session.bean.EJSRemoteStatelessProxySe ssion_5422376a.remove(Unknown
    Source)
    at
    ..epi.proxy.session.bean._ProxySession_Stub.remove (_ProxySession_Stub.java:1606)
    at
    ..epi.proxy.session.client.SessionInfoCls.destroy( SessionInfoCls.java:151)
    at
    ..epi.proxy.uda.UdaConnectionCls.sessionDestroy(Ud aConnectionCls.java:958)
    at
    ..epi.proxy.uda.UdaConnectionCls.executeMessage(Ud aConnectionCls.java:398)
    at
    ..epi.proxy.uda.UdaConnectionCls.access$000(UdaCon nectionCls.java:42)
    at
    ..epi.proxy.uda.UdaConnectionCls$UserAction.run(Ud aConnectionCls.java:318)
    at java.security.AccessController.doPrivileged1(Nativ e Method)
    at
    java.security.AccessController.doPrivileged(Access Controller.java:321)
    at javax.security.auth.Subject.doAs(Subject.java:477)
    at
    com.ibm.websphere.security.auth.WSSubject.doAs(WSS ubject.java:112)
    at
    epi.appserver.websphere_5.ClientAppserverConnectio nCls.doAs(ClientAppserverConnectionCls.java:108)
    at
    ..epi.appserver.ClientConnectionCls.doAs(ClientCon nectionCls.java:175)
    at
    ..epi.proxy.uda.UdaConnectionCls.processMessage(Ud aConnectionCls.java:273)
    at
    ..epi.proxy.uda.UdaConnectionCls.run(UdaConnection Cls.java:168)
    at amdocs.epi.session.EpiRunnable.run(EpiRunnable.jav a:208)
    at
    ..epi.concurrent.PooledExecutor$Worker.run(PooledE xecutor.java:728)
    at java.lang.Thread.run(Thread.java:567)
    at amdocs.epi.session.EpiThread.run(EpiThread.java:48 )


    There is no AuthenticationFailedException or another problems in the
    SystemOut.log

    regards


    -----Original Message-----
    From: pwdts@us.ibm.com [mailtowdts@us.ibm.com]
    Sent: Wed, April 06, 2005 5:05 PM

    Subject: IBM Technical Support: WAS5111 ND JSAS0202E 10 min after
    server
    is started. (PMR 87821,756,000)


    Hi

    Thanks for the additional information.
    The CORBA.NO.PERMISSION error from the original email is below.
    Typically the CORBA exception is triggered by an underlying
    com.ibm.WebSphereSecurity.AuthenticationFailedExce ption.
    In the ouput snippet sent in I do not see the
    AuthenticationFailedException.

    Below message is from the original update
    >[3/27/05 16:26:25:757 GMT+02:00] 180026ad SASRas E JSAS0202E:
    >[CSICredentialsManager.getClientSubject] Credential token >expired.
    >org.omg.CORBA.NO_PERMISSION vmcid: 0x49424000 minor code: 306
    >completed: No


    To help with the investigation, please reply back with the full
    systemOut.log showing the problem (as an email attachment).

    Best Regards,
    Harry

    ================================================== =======================

    Hi.

    Several clarifications:

    1. We have UserSession object that is implemented as statefull session
    EJB. This Session performs several calls
    to another stateless session EJB called Simulator. The User Session
    lives between 5 to 20 minutes and for better
    performance caches the reference to Simulator remote interface and
    reuse it in each call to Simulator.
    At the logout UserSession calls remove() on the Simulator home
    interface (this is what I tried to express shortly
    when I mentioned that the Simulator is an EJB).

    We get this exception both on attempts to call the Simulator and on
    call to remove() in the cases when there was
    some delay (about 10 minutes) after the previous call to Simulator.

    2. It seems that this exception doesn't reach our code and what we see
    is just print stuck output in WAS level.
    So we don't have to implement reconnection though we will do it in any
    case.

    3. We want to get rid of these exceptions because they blow up our
    logs when we run load tests.
    4. Could it be that we can achieve this goal by proper configuration
    of our WAS Security settings?

    regards



    -----Original Message-----
    From: pwdts@us.ibm.com [mailtowdts@us.ibm.com]
    Sent: Tue, April 05, 2005 4:38 PM
    T
    Subject: IBM Technical Support: WAS5111 ND JSAS0202E 10 min after
    server
    is started. (PMR 87821,756,000)


    Hi Dimitry,

    From the output snippet sent in investigating the JSAS0202E
    message being generated.

    1. From WAS v5.1 infocenter:

    JSAS0202E: [{0}] Credential token expired. {1}
    Explanation: The credential token associated with the user credential
    has expired. This typically occurs with LTPA.

    User Response: Close the client and login again

    2. Also see PQ83105 which looks to address a similar JSAS0202E
    issue.

    Title: PQ83105: Periodically, EJB create fails with
    CORBA:NO_PERMISSION
    Url: http://www-1.ibm.com/support/docview...id=swg1PQ83105

    But looking at defect fixes(below) see PQ83105 is in WAS v511, so with
    WAS v5111 you have already have this update.

    Title: 5.1.0.1 - 5.1.1.3: List of Defects for Base, Network
    Deployment,
    and Express Editions
    Url:
    http://www-1.ibm.com/support/docview...xt=SSEQTP&q1=P
    Q83105&uid=swg27004936&loc=en_US&cs=utf-8&lang=en

    To help with the investigation of the JSAS0202E you are seeing,
    please reply to the below.

    -Does the infocenter suggestion (from 1. above) help in
    your environment ?
    -At the end of the original email update, it mentions
    "The Simulator is EJB.". What does this mean ?
    -What type of EJB simulator test is being run?
    -Is the error reproducable?
    -Do you have a work-around to get past the error ?

    Best Regards,
    Harry

    ================================================== ================================================== =====

    We have received the Remote E-mail Support (AAQ) item that you
    submitted. It has been assigned a tracking number. Please
    refer to this number in any future correspondence: PMR# 87821,756.

    Thank you,


    IBM Corporation
    PWISV Technical Support
    pwisvts@us.ibm.com
    (800) 426-9990 or (770) 863-2048

    ================================================== ============================================

    (Subject: Remote e-mail support for WebSphere Application Server on
    Unix/Win


    The system is:
    IBM pSeries 7040-671
    AIX: 5.2.0
    WAS: WebSphere Platform 5.1 [ND 5.1.1.1 cf10435.07] [JDK 1.4.2.3
    ${ptf.jdk.build.level}] [BASE 5.1.1.1 cf10435.07]

    We start to get the following exception 10 minutes after the server is
    up:

    [3/27/05 16:26:25:757 GMT+02:00] 180026ad SASRas E JSAS0202E:
    [CSICredentialsManager.getClientSubject] Credential token expired.
    org.omg.CORBA.NO_PERMISSION vmcid: 0x49424000 minor code: 306
    completed: No
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSICredent ialsManager.getClientSubject(CSICredentialsManager .java:580)
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I$2.run(CSIClientRI.java:443)
    at
    com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java(Compiled
    Code))
    at
    com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I.send_request(CSIClientRI.java:439)
    at
    com.ibm.rmi.pi.InterceptorManager.iterateSendReque st(InterceptorManager.java(Compiled
    Code))
    at
    com.ibm.rmi.iiop.ClientRequestImpl.(ClientRequestImpl.java:136)
    at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:141)
    at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:97)
    at
    com.ibm.rmi.corba.ClientDelegate._createRequest(Cl ientDelegate.java:1899)
    at
    com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1177)
    at
    com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1285)
    at
    com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1110)
    at
    com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1251)
    at com.ibm.rmi.corba.ClientDelegate.request(ClientDel egate.java:1776)
    at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDe legate.java:1207)
    at org.omg.CORBA.portable.ObjectImpl._request(ObjectI mpl.java:460)
    at ......simulator._Simulator_Stub.remove(_Simulator_ Stub.java:116)

    The Simulator is EJB.





  2. Re: 'credentials token expired' exception in WAS

    Hello,

    As far as I can see from the PQ they mentionned, it sounds applicable to
    your issue. The strange is that, according to the Defect List, it was
    released in WAS 5.1.1.1, which you are running...

    Now, as the issue looks fairly easy to reproduce, I'd apply WAS 5.1.1.3 on a
    test system while discussing with IBM support (you could even obtain the
    individual fix if you can negotiate and argument). Also, Support requested
    to see the complete log file, so it be wise to send it. Even if you feel
    like it's not necessary, it's a support guy's life to obtain logs, so they
    ask them all the time... And as you want Support guys to support you and not
    blame you all the time because you don't cooperate... :-)



  3. Re: 'credentials token expired' exception in WAS

    Maybe you should try to see if the error comes always exactly after the same
    amount of time after the beginning of the thread (or transaction or call...)
    (60sec, 120 secs...etc) and try to find if you didnt reach some rmi timeout
    or another one ...
    Had already received similar messages with and EJB client batch that receive
    that kind of error after exactly 2 hours (the LTPA token timeout...)
    Have you looked at the value set for the LTPA token timeout? From memory the
    default is 2hours. Look also at the transaction timeout value (2 minutes)
    and other timeouts
    If your system is under stress, wait time grows and you may reach some
    timeout...
    Hope that helps...

    "Family man" wrote in message
    news:h6qn51l85pmhmiijv5didncdaj18cjav29@4ax.com...
    > Currently our 'heaviest' IBM-AIX-WAS related problem is 'credentials
    > token expired'.
    >
    > We tried DDC and other options.
    >
    > We therefore turned for the IBM support, as described below.
    >
    > Unfortunatley, it doesn't seem to be 'to the point' (their
    > recommendation is to upgrade).
    >
    > Does anyone has more productive suggestions to solve this problem
    > without upgrading the WAS
    >
    > Regards,
    >
    >
    > ______________________________________________
    >
    >
    > ================================================== =========================================
    >
    > Hi ,
    >
    > Thanks for the update.
    > Since you were only able to re-send the output snippet from the
    > original update, not sure how much that will add in our investigation
    > of this issue. Currently WAS v5.1.1.1 is being
    > used, the current recommended update for WAS is: v5.1.1.3, see
    > the document below.
    >
    > Title: Recommended Updates for WebSphere Application Server Base
    > and Network Deployment editions
    > Url:
    > http://www-1.ibm.com/support/docview...swg27004980#51
    >
    > WAS version 5.1.1.3 is at:
    >
    > Title: 5.1.1.3: WebSphere Application Server Version 5.1.1
    > Cumulative Fix 3
    > Url:
    > http://www-1.ibm.com/support/docview...=utf-8&lang=en
    >
    > Please apply the recommended WAS version 5.1.1.3, to see if it
    > addresses this issue.
    >
    > Best Regards,
    > Harry
    >
    > ================================================== ===========================================
    >
    > Hi.
    >
    > Here is the whole exception, snippet of which I've sent you before:
    >
    >
    > [4/6/05 15:47:50:169 EEST] 3aefab8c SASRas E JSAS0202E:
    > [CSICredentialsManager.getClientSubject] Credential token expired.
    > org.omg.CORBA.NO_PERMISSION vmcid: 0x49424000 minor code: 306
    > completed: No
    > at
    > com.ibm.ISecurityLocalObjectBaseL13Impl.CSICredent ialsManager.getClientSubject(CSICredentialsManager .java:580)
    > at
    > com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I$2.run(CSIClientRI.java:443)
    > at
    > com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:111)
    > at
    > com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I.send_request(CSIClientRI.java:439)
    > at
    > com.ibm.rmi.pi.InterceptorManager.iterateSendReque st(InterceptorManager.java:404)
    > at
    > com.ibm.rmi.iiop.ClientRequestImpl.(ClientRequestImpl.java:136)
    > at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:141)
    > at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:97)
    > at
    > com.ibm.rmi.corba.ClientDelegate._createRequest(Cl ientDelegate.java:1854)
    > at
    > com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1132)
    > at
    > com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1285)
    > at
    > com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1065)
    > at
    > com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1251)
    > at
    > com.ibm.rmi.corba.ClientDelegate.request(ClientDel egate.java:1731)
    > at
    > com.ibm.CORBA.iiop.ClientDelegate.request(ClientDe legate.java:1207)
    > at
    > org.omg.CORBA.portable.ObjectImpl._request(ObjectI mpl.java:460)
    > at
    > .oms.simulator._Simulator_Stub.remove(_Simulator_S tub.java:116)
    > at amdocs.oms.connector.EjbClient.Dispose(EjbClient.j ava:328)
    > at .oms.infra.IlSession.DisposeAllClients(IlSession.j ava:719)
    > at amdocs.oms.infra.IlSession.onTerminate(IlSession.j ava:641)
    > at
    > .epi.session.EpiSessionContext.remove(EpiSessionCo ntext.java:1974)
    > at
    > .epi.session.InternalSessionContext.remove(Interna lSessionContext.java:212)
    > at
    > .epi.session.EpiStatelessSessionBean.remove(EpiSta telessSessionBean.java:92)
    > at
    > .epi.proxy.session.bean.EJSRemoteStatelessProxySes sion_5422376a.remove(Unknown
    > Source)
    > at
    > .epi.proxy.session.bean._ProxySession_Stub.remove( _ProxySession_Stub.java:1606)
    > at
    > .epi.proxy.session.client.SessionInfoCls.destroy(S essionInfoCls.java:151)
    > at
    > .epi.proxy.uda.UdaConnectionCls.sessionDestroy(Uda ConnectionCls.java:958)
    > at
    > .epi.proxy.uda.UdaConnectionCls.executeMessage(Uda ConnectionCls.java:398)
    > at
    > .epi.proxy.uda.UdaConnectionCls.access$000(UdaConn ectionCls.java:42)
    > at
    > .epi.proxy.uda.UdaConnectionCls$UserAction.run(Uda ConnectionCls.java:318)
    > at java.security.AccessController.doPrivileged1(Nativ e Method)
    > at
    > java.security.AccessController.doPrivileged(Access Controller.java:321)
    > at javax.security.auth.Subject.doAs(Subject.java:477)
    > at
    > com.ibm.websphere.security.auth.WSSubject.doAs(WSS ubject.java:112)
    > at
    > epi.appserver.websphere_5.ClientAppserverConnectio nCls.doAs(ClientAppserverConnectionCls.java:108)
    > at
    > .epi.appserver.ClientConnectionCls.doAs(ClientConn ectionCls.java:175)
    > at
    > .epi.proxy.uda.UdaConnectionCls.processMessage(Uda ConnectionCls.java:273)
    > at
    > .epi.proxy.uda.UdaConnectionCls.run(UdaConnectionC ls.java:168)
    > at amdocs.epi.session.EpiRunnable.run(EpiRunnable.jav a:208)
    > at
    > .epi.concurrent.PooledExecutor$Worker.run(PooledEx ecutor.java:728)
    > at java.lang.Thread.run(Thread.java:567)
    > at amdocs.epi.session.EpiThread.run(EpiThread.java:48 )
    >
    >
    > There is no AuthenticationFailedException or another problems in the
    > SystemOut.log
    >
    > regards
    >
    >
    > -----Original Message-----
    > From: pwdts@us.ibm.com [mailtowdts@us.ibm.com]
    > Sent: Wed, April 06, 2005 5:05 PM
    >
    > Subject: IBM Technical Support: WAS5111 ND JSAS0202E 10 min after
    > server
    > is started. (PMR 87821,756,000)
    >
    >
    > Hi
    >
    > Thanks for the additional information.
    > The CORBA.NO.PERMISSION error from the original email is below.
    > Typically the CORBA exception is triggered by an underlying
    > com.ibm.WebSphereSecurity.AuthenticationFailedExce ption.
    > In the ouput snippet sent in I do not see the
    > AuthenticationFailedException.
    >
    > Below message is from the original update
    >>[3/27/05 16:26:25:757 GMT+02:00] 180026ad SASRas E JSAS0202E:
    >>[CSICredentialsManager.getClientSubject] Credential token >expired.
    >>org.omg.CORBA.NO_PERMISSION vmcid: 0x49424000 minor code: 306
    >>completed: No

    >
    > To help with the investigation, please reply back with the full
    > systemOut.log showing the problem (as an email attachment).
    >
    > Best Regards,
    > Harry
    >
    > ================================================== =======================
    >
    > Hi.
    >
    > Several clarifications:
    >
    > 1. We have UserSession object that is implemented as statefull session
    > EJB. This Session performs several calls
    > to another stateless session EJB called Simulator. The User Session
    > lives between 5 to 20 minutes and for better
    > performance caches the reference to Simulator remote interface and
    > reuse it in each call to Simulator.
    > At the logout UserSession calls remove() on the Simulator home
    > interface (this is what I tried to express shortly
    > when I mentioned that the Simulator is an EJB).
    >
    > We get this exception both on attempts to call the Simulator and on
    > call to remove() in the cases when there was
    > some delay (about 10 minutes) after the previous call to Simulator.
    >
    > 2. It seems that this exception doesn't reach our code and what we see
    > is just print stuck output in WAS level.
    > So we don't have to implement reconnection though we will do it in any
    > case.
    >
    > 3. We want to get rid of these exceptions because they blow up our
    > logs when we run load tests.
    > 4. Could it be that we can achieve this goal by proper configuration
    > of our WAS Security settings?
    >
    > regards
    >
    >
    >
    > -----Original Message-----
    > From: pwdts@us.ibm.com [mailtowdts@us.ibm.com]
    > Sent: Tue, April 05, 2005 4:38 PM
    > T
    > Subject: IBM Technical Support: WAS5111 ND JSAS0202E 10 min after
    > server
    > is started. (PMR 87821,756,000)
    >
    >
    > Hi Dimitry,
    >
    > From the output snippet sent in investigating the JSAS0202E
    > message being generated.
    >
    > 1. From WAS v5.1 infocenter:
    >
    > JSAS0202E: [{0}] Credential token expired. {1}
    > Explanation: The credential token associated with the user credential
    > has expired. This typically occurs with LTPA.
    >
    > User Response: Close the client and login again
    >
    > 2. Also see PQ83105 which looks to address a similar JSAS0202E
    > issue.
    >
    > Title: PQ83105: Periodically, EJB create fails with
    > CORBA:NO_PERMISSION
    > Url: http://www-1.ibm.com/support/docview...id=swg1PQ83105
    >
    >But looking at defect fixes(below) see PQ83105 is in WAS v511, so with
    > WAS v5111 you have already have this update.
    >
    > Title: 5.1.0.1 - 5.1.1.3: List of Defects for Base, Network
    > Deployment,
    > and Express Editions
    > Url:
    > http://www-1.ibm.com/support/docview...xt=SSEQTP&q1=P
    > Q83105&uid=swg27004936&loc=en_US&cs=utf-8&lang=en
    >
    > To help with the investigation of the JSAS0202E you are seeing,
    > please reply to the below.
    >
    > -Does the infocenter suggestion (from 1. above) help in
    > your environment ?
    > -At the end of the original email update, it mentions
    > "The Simulator is EJB.". What does this mean ?
    > -What type of EJB simulator test is being run?
    > -Is the error reproducable?
    > -Do you have a work-around to get past the error ?
    >
    > Best Regards,
    > Harry
    >
    > ================================================== ================================================== =====
    >
    > We have received the Remote E-mail Support (AAQ) item that you
    > submitted. It has been assigned a tracking number. Please
    > refer to this number in any future correspondence: PMR# 87821,756.
    >
    > Thank you,
    >
    >
    > IBM Corporation
    > PWISV Technical Support
    > pwisvts@us.ibm.com
    > (800) 426-9990 or (770) 863-2048
    >
    > ================================================== ============================================
    >
    > (Subject: Remote e-mail support for WebSphere Application Server on
    > Unix/Win
    >
    >
    > The system is:
    > IBM pSeries 7040-671
    > AIX: 5.2.0
    > WAS: WebSphere Platform 5.1 [ND 5.1.1.1 cf10435.07] [JDK 1.4.2.3
    > ${ptf.jdk.build.level}] [BASE 5.1.1.1 cf10435.07]
    >
    > We start to get the following exception 10 minutes after the server is
    > up:
    >
    > [3/27/05 16:26:25:757 GMT+02:00] 180026ad SASRas E JSAS0202E:
    > [CSICredentialsManager.getClientSubject] Credential token expired.
    > org.omg.CORBA.NO_PERMISSION vmcid: 0x49424000 minor code: 306
    > completed: No
    > at
    > com.ibm.ISecurityLocalObjectBaseL13Impl.CSICredent ialsManager.getClientSubject(CSICredentialsManager .java:580)
    > at
    > com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I$2.run(CSIClientRI.java:443)
    > at
    > com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java(Compiled
    > Code))
    > at
    > com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientR I.send_request(CSIClientRI.java:439)
    > at
    > com.ibm.rmi.pi.InterceptorManager.iterateSendReque st(InterceptorManager.java(Compiled
    > Code))
    > at
    > com.ibm.rmi.iiop.ClientRequestImpl.(ClientRequestImpl.java:136)
    > at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:141)
    > at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.j ava:97)
    > at
    > com.ibm.rmi.corba.ClientDelegate._createRequest(Cl ientDelegate.java:1899)
    > at
    > com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1177)
    > at
    > com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1285)
    > at
    > com.ibm.rmi.corba.ClientDelegate.createRequest(Cli entDelegate.java:1110)
    > at
    > com.ibm.CORBA.iiop.ClientDelegate.createRequest(Cl ientDelegate.java:1251)
    > at com.ibm.rmi.corba.ClientDelegate.request(ClientDel egate.java:1776)
    > at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDe legate.java:1207)
    > at org.omg.CORBA.portable.ObjectImpl._request(ObjectI mpl.java:460)
    > at ......simulator._Simulator_Stub.remove(_Simulator_ Stub.java:116)
    >
    > The Simulator is EJB.
    >
    >
    >
    >




+ Reply to Thread