|
Home > Archive > WebSphere Application Server > June 2007 > CORBA NO_PERMISSION
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CORBA NO_PERMISSION
|
|
| Reinhal 2007-06-21, 7:26 pm |
| Hi,
I've 2 WAS 6.1.02 server with cluster vertical in 1 server.
I using WAS Scheduler API to run the schedule in the WAS. It's running fine at the server1 but I got error on server2 with the below information:
SystemOut_07.06.18_17.36.56.log:[6/15/07 15:48:19:160 CST] 00000034 AlarmListener E SCHD0063E: A task with ID 2 failed
to run on Scheduler JobScheduler (scheduler/JobScheduler) because of an exception: com.ibm.websphere.scheduler.No
tificationException: SCHD0137E: Unable to create EJB instance for NotificationSink: java.rmi.AccessException: CORBA NO_P
ERMISSION 0x49424307 No; nested exception is:
SystemOut_07.06.18_17.36.56.log: org.omg.CORBA.NO_PERMISSION: The WSCredential does not contain a forwardable tok
en. Please enable Identity Assertion for this scenario. vmcid: 0x49424000 minor code: 307 completed: No SCHD0140I: EJ
B information: Host: SEP-DV5-WAS-001 (192.168.51.130), Port: 9,900, J2EE component: SePAPP_CM#SePEJB_Job.jar#Notificati
onSinkSB.
The question is how to enable Identity Assertion for this scenario ?
Thanks in advances.
Regards
RH
| |
| Paul Ilechko 2007-06-22, 1:27 am |
| Reinhal wrote:
> Hi,
>
> I've 2 WAS 6.1.02 server with cluster vertical in 1 server.
> I using WAS Scheduler API to run the schedule in the WAS. It's running fine at the server1 but I got error on server2 with the below information:
>
>
> SystemOut_07.06.18_17.36.56.log:[6/15/07 15:48:19:160 CST] 00000034 AlarmListener E SCHD0063E: A task with ID 2 failed
> to run on Scheduler JobScheduler (scheduler/JobScheduler) because of an exception: com.ibm.websphere.scheduler.No
> tificationException: SCHD0137E: Unable to create EJB instance for NotificationSink: java.rmi.AccessException: CORBA NO_P
> ERMISSION 0x49424307 No; nested exception is:
> SystemOut_07.06.18_17.36.56.log: org.omg.CORBA.NO_PERMISSION: The WSCredential does not contain a forwardable tok
> en. Please enable Identity Assertion for this scenario. vmcid: 0x49424000 minor code: 307 completed: No SCHD0140I: EJ
> B information: Host: SEP-DV5-WAS-001 (192.168.51.130), Port: 9,900, J2EE component: SePAPP_CM#SePEJB_Job.jar#Notificati
> onSinkSB.
>
>
> The question is how to enable Identity Assertion for this scenario ?
> Thanks in advances.
http://publib.boulder.ibm.com/infoc...c_outbound.html
http://publib.boulder.ibm.com/infoc...iv2inbound.html
|
|
|
|
|