Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

WAS 6.1 ND Security CORBA.NO_PERMISSION vmcid: 0x49424000  minor code: 309

Posted on 2010-08-24
Last Modified: 2013-12-11
Hi All,

we are running 3 physical WAS6.1 ND with 3 servers on every machine.

By time (environment was running without problems before) we always get on the same server the following Exception:

        >>    org.omg.CORBA.NO_PERMISSION: handleStatefulContext > MessageInContext  vmcid: 0x49424000  minor code: 309  completed: No
        >>         at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRIBase.handleStatefulContext(CSIServerRIBase.java:1764)
        >>         at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRI.receive_request(CSIServerRI.java:489)
        >>         at com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorManager.java:631)
        >>         at com.ibm.rmi.pi.InterceptorManager.iterateServerInterceptors(InterceptorManager.java:535)
        >>         at com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest(InterceptorManager.java:777)
        >>         at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:616)
        >>         at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:480)
        >>         at com.ibm.rmi.iiop.ORB.process(ORB.java:512)
        >>         at com.ibm.CORBA.iiop.ORB.process(ORB.java:1571)
        >>         at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2717)
        >>         at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2582)
        >>         at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62)
        >>         at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
        >>         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

The minor code says that the on the server already exists with the context-id but the information by the client provided is different from the original information provided.

Now my question:

Does anybody have a hint what the reason could be that this error pops up?

with kind regards
Question by:uniquare
  • 3
  • 2
  • 2
  • +1
LVL 41

Expert Comment

ID: 33516914
Does this describe your situation accurately?

LVL 41

Expert Comment

ID: 33516927
If this is the case, the fix is described here:


and is available in

The latest fix level for 6.1 is


If you need help with understanding how to get, and install the fix, let me know.

Author Comment

ID: 33518744
Hi HonorGod,

thanks for your reply.

The situation described is not the situation at all, as i have understood the situation you posted occurs immediatley after a nodeagent had been restarted, and the application servers had been running all the time.

In my case, the error occurs after some time (in the current case 12 hours after the restart of all nodeagents and application servers).
As i have described above the minor code (309 instead of 300) says the server already had been registered after the restart, and are reregistering with another information.

Our current Fixpack installed on the Servers is so the Fix had been provided.

with kind regards
Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

LVL 41

Expert Comment

ID: 33519545
uniquare - Thanks for the clarification!  Let me look around, and see what I can find.

Accepted Solution

AdminRAM earned 500 total points
ID: 33520044
If you see Credential token expired then following apar will match. This kind of problem occured during load test or heavy load  and intermitent problem. I fixed the problem by applying the apar PK96506. WebSphere Application Server fails to retry requests causing Credential token expired error.


additional continuation apar if the above doesn't fix


Author Comment

ID: 33520525
Hi AdminRAM,

thanks for your answers, all your answers and links are looking very good, but i am a always a little bit confused about the different minor codes.

Our Credential token isn't expired, as far as i know. Can you provide me an Information how i can check fast if the token is expired? Is this possible to do in a running productive system without influence on the performance?

As in your link above i already thought my next step should be to disable stateful CSIv2 sessions to suppress this error, but this would only suppress it and i would have no clue if this error is resulting from our application or it is an error which occurs through a wrong configuration of the WAS 6.1.

The next step we will try now is to install the current fix-pack and will look if the error occurs one more time :)

Expert Comment

ID: 33521044

how i can check fast if the token is expired?

Generally in exception stack you will see this message

Caused by: org.omg.CORBA.NO_PERMISSION: JSAS0202E: [{0}]
Credential token expired.

com.ibm.ISecurityLocalObjectCSIv2UtilityImpl.SessionManager.retry(SessionManager.java(Compiled Code))

Is this possible to do in a running productive system without influence on the performance?

I heared if fix also fixed other minor code but for only  Credential token expired However t you might need to check with IBM.

PM13384 is not yet released. it is tearget on v6.1.0.35 you might need to check with ibm for ifix...:-)
LVL 59

Expert Comment

by:Kevin Cross
ID: 36042235
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
endX challenge 2 101
eclipse compiler vs Installed JREs option 3 105
replace a word with other 1 45
diffSum example 4 50
Most of the developers using Tomcat find it easy to configure the datasource in Server.xml and use the JNDI name in the code to get the connection.  So the default connection pool using DBCP (or any other framework) is made available and the life go…
This article is about some of the basic and important steps to be used to improve the performance in web-sphere commerce application development. 1) Always leverage the Dyna-caching facility provided by the product 2) Remove the unwanted code …
The viewer will learn how to implement Singleton Design Pattern in Java.
This tutorial covers a practical example of lazy loading technique and early loading technique in a Singleton Design Pattern.

837 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question