Fix (APAR):  JR30699

Status:  Fix

Release:  6.1.2,6.1.0.2,6.1.0.1,6.0.2.5,6.0.2.4

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR30699

Byte size of APAR:  56375

Date: 2008-11-03

Abstract:  "ServiceRuntimeException: The run-as authentication data is not configured for role <role-name>" gets thrown at application startup.

Description/symptom of problem:  
JR30699 resolves the following problem:

ERROR DESCRIPTION:?                                             
Exception data:                                                 
com.ibm.websphere.sca.ServiceRuntimeException: The              
run-as authentication data is not configured for role           
ProcessExecuter                                                 
                                                                
ApplicationBinding class is not a part of security component.   
Client has the same issues, and symptoms as this PMR.           
                                                                
It seems like the problem is between SCA securitymanager and    
 ejb deployment model.                                          
more precise: the                                               
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl
method                                                          
getDeploymentDescriptor()                                       
                                                                
The problem's root cause could be a timing problem between SCA  
and                                                             
EJB during initialization. In other words, at startup, the SCA  
securitymanager requests information too early, before the      
information is made available by the initialization.            
                                                                
The working theory, which is that there is a threading issue,   
where the SCA thread is obtaining and using binding data while  
that data is still being populated / deserialized.              
                                                                
The problem appears to be that this SecurityManagerImpl is using
a                                                               
DeployedApplication after the application has already been      
started.                                                        
Once an application is started, the EAR file is closed down, and
things                                                          
are not going to work properly.                                 
this code should be reading its data from the bindings          
during                                                          
application startup (DeployedObjectListener waiting for STARTED 
or                                                              
STARTING) rather than holding a reference to the                
DeployedApplication.                                            

LOCAL FIX:?                                                     
NA                                                              

PROBLEM SUMMARY:?

USERS AFFECTED:
Users of WebSphere Process Server and
WebSphere Enterprise Service Bus
6.0.2.4, 6.1, 6.1.0.1, 6.1.0.2 and 6.1.2
users.

PROBLEM DESCRIPTION:
"ServiceRuntimeException: The run-as
authentication data is not configured
for role
<role-name>" gets thrown at
application startup.

RECOMMENDATION:
None

Due to timing issue at the startup of the application, the
information queried by WPS from WAS is not available, leading
to ServiceRuntimeException.

PROBLEM CONCLUSION:?                                            
Appling this interim fix will resolve the issue.                


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: