OpenSSO Enterprise Login Module for IDM 7.1

I have a fully configured OpenSSO Enterprise environment running on Glassfish v2.1 and am trying to implement SSO into an IDM 7.1 environment that is also running on a Glassfish 2.1 server with a centrally managed v3.0 policy agent.
While working my way through the "Integration Guide" for IDM and OpenSSO I've come to the step where I am to change the Identity Manager Login Module Groups. We are not provisioning directly from IDM to OpenSSO but rather to the LDAP that OpenSSO authenticates with so I have not configured the OpenSSO resource adapter.
When I get to Assigning the Login Module I initially did not have the Sun OpenSSO Realm Login Module so i want back and added a custom resource called: com.waveset.adapter.SunAccessManagerRealmResourceAdapter which was available because I had put the openssoclientsdk.jar in the idm/WEB-INF/lib folder and added that to the class suffix in the JVM settings.
The Realm resource adapter appears to work as I can create a new instance and am prompted for the correct fields.
When i go back to assign the Login Module I now get a Sun Access Manager Realm Adapter in the dropdown box but cannot select it.
The question is, where do I get the custom login module that will allow IDM 7.1 to work with OpenSSO Enterprise?
Thanks, Craig

Hi ,
I am a colleague of Peter, just to straighten out our problem.
Our custom login module extends AMLoginModule and when the Access Manager instantiates the object it calls the method defined in AMLoginModule :
" public Callback[] getCallback(int index) "
This method contains a call to "AMModuleProperties.getModuleProperties(fileName);"
Our problem is, das the method is already called with filename being null, which is the cause for the Exception to be thrown.
So could anybody give us a hint what filename is supposed to be at this point? As it seems that Access Manager is lacking a property which it normally would associate with filename.
My first guess was that it is looking for <moduleName>.xml, but this file is properly located in "/etc/opt/SUNWam/config/xml" and accessible.
Any help appreciated.
Thank you in advance!

Similar Messages

Custom login module for weblogic portal 10.3.2

Hi everyone
i want to develop a custom portal login module for weblogic..
can anyone help me out with details how can i implement it ...any links provided will ve very useful
Thanks in advance.

The credentials given on that page are wrong for 10.3.2. (They might be correct for 10.3, but that's not my problem.) I found the correct credentials -- weblogic / webl0gic -- at this URL:
weblogic portal 10.3.2 sample domain admin console question
It's also given correctly in section 6 of the Getting Started Guide, but you have to know to look there first.
Edited by: dwschulze on Aug 19, 2010 1:47 PM

Custom Login Module for EP7

Hello Experts,
i have a requirement to develop a custom Login Module for EP7. I am fine with the programming part and on this side everything should be fine. I am puzzling about the configuration. My LoginModule is configured according to this link: [SAP HELP|http://help.sap.com/saphelp_nw2004s/helpdata/en/46/3ce9402f3f8031e10000000a1550b0/content.htm]. But when i configure sap.com/irj*irj in SecurityProvider in Visual Admin, the changes do not take affect. I restarted the portal as well as the Server. I am on NW2004s SP 14.
What am I missing.
Thanks for any help,
best Regards,
Rene

Hello Laura,
thank you for your reply. I have read you link and I doubt that this is the solution. In authschemes.xml you define the user interface for authentication and priority. In Visual admin, you can define the loginModule for your Scheme. But this must be possible without defining an authscheme. Am I right? In my understanding you only have to declare the loginmodule for the application in Visual Admin. And thats it.
So what i have to do to change the login module for the Portal (irj).
Any help will be appreciated,
best regards,
Rene

How to configure login modules for certificate logon

Hello,
perhaps someone of you has also tried to implement SSO via Client Certificates and is able to help me...
I have configured the login modules for rule based authentication with the option Rule1.getUserFrom = wholeCert and I have attached my certificate to my user in useradmin.
And also added the login module to the template ticket, as suggested by the documentation at help.sap.com
But when I logon to the portal or other application (for example useradmin) via https the authentication doesn't work (but I'm still able to logon via password).
I also tried auto. certifcate mapping and mapping by subject name but in every case the system ignores the configured login module. There are no errors in the log files.
Thank You,
Frank

Hi Frank,
did you configure the SSO for an individual policy configuration or did you edit and save the changes the ticket policy config? I ask, b/c if you applied the changes to the individual policy config then the SSO with certificates will be used <b>only</b> when you access the applications for that policy config.
You can also double check the login module flags - perhaps the authentication check doesn't reach the ClientCertLM at all.
Since you followed the help portal instruction I assume you've enabled strong crypto - it is required for client cert SSO. Ano easily committed mistake is to also not use the HTTPS port in the access URL.
Let me know if this helps...
Yonko

Custom login module for EP7.4 with Captcha

Hi
I am trying to create a custom login module which validates the captcha shown at the login screen using SAP help link:
http://help.sap.com/saphelp_nw73/helpdata/en/48/ff4faf222b3697e10000000a42189b/content.htm?frameset=/en/48/fcea4f62944e88e10000000a421937/frameset.htm&current_toc=/en/74/8ff534d56846e2abc61fe5612927bf/plain.htm&node_id=20
The session is being set in the Captcha servlet which is used to render the image on the login page.
However when I am trying to compare it with input or print the session value, its throwing an exception.
I checked in the NWA logs and it just shows the following error message:
6. com.temp.loginModule.MyLoginModuleClass OPTIONAL ok exception true Authentication did not succeed.
Please help me analyse the error stack. Can someone point where do i check the detailed logs to trace the issue?
Please find below source of my login module.
package com.temp.loginModule;
import java.io.IOException;
import java.util.Map;
import javax.security.auth.login.LoginException;
import javax.security.auth.Subject;
import javax.security.auth.callback.CallbackHandler;
import javax.security.auth.callback.Callback;
import javax.security.auth.callback.NameCallback;
import javax.security.auth.callback.UnsupportedCallbackException;
import nl.captcha.Captcha;
import com.sap.engine.interfaces.security.auth.AbstractLoginModule;
import com.sap.engine.lib.security.http.HttpGetterCallback;
import com.sap.engine.lib.security.http.HttpCallback;
import com.sap.engine.lib.security.LoginExceptionDetails;
import com.sap.engine.lib.security.Principal;
public class MyLoginModuleClass extends AbstractLoginModule{
private CallbackHandler callbackHandler = null;
private Subject subject = null;
private Map sharedState = null;
private Map options = null;
// This is the name of the user you have created on
// the AS Java so you can test the login module
private String userName = null;
private boolean successful;
private boolean nameSet;
public void initialize(Subject subject, CallbackHandler callbackHandler,
Map sharedState, Map options) {
// This is the only required step for the method
super.initialize(subject, callbackHandler, sharedState, options);
// Initializing the values of the variables
this.callbackHandler = callbackHandler;
this.subject = subject;
this.sharedState = sharedState;
this.options = options;
this.successful = false;
this.nameSet = false;
* Retrieves the user credentials and checks them. This is
* the first part of the authentication process.
public boolean login() throws LoginException {
// HttpGetterCallback httpGetterCallback = new HttpGetterCallback();
//       httpGetterCallback.setType(HttpCallback.REQUEST_PARAMETER);
//       httpGetterCallback.setName("captchaInput");
       String value = null;
//       try {
//       callbackHandler.handle(new Callback[] { httpGetterCallback });
//           String[] arrayRequestparam = (String[]) httpGetterCallback.getValue();
//           if(arrayRequestparam!=null && arrayRequestparam.length>0)
//           value = arrayRequestparam[0];
//       } catch (UnsupportedCallbackException e) {
//       throwNewLoginException("An error occurred while trying to validate credentials.");
//       } catch (IOException e) {
//            throwUserLoginException(e, LoginExceptionDetails.IO_EXCEPTION);
value = getRequestValue("captchaInput");
userName = getRequestValue("j_username");
HttpGetterCallback httpGetterCallbackSessionCaptcha = new HttpGetterCallback();
httpGetterCallbackSessionCaptcha.setType(HttpCallback.SESSION_ATTRIBUTE);
httpGetterCallbackSessionCaptcha.setName("myCaptchaLogin");
try {
callbackHandler.handle(new Callback[] { httpGetterCallbackSessionCaptcha });
Captcha arraySessionParam = (Captcha) httpGetterCallbackSessionCaptcha.getValue();
// System.out.println("****************************************************httpGetterCallbackSessionCaptcha" + (arraySessionParam==null?"null session":arraySessionParam.getAnswer())+
// "\n captchaInput" + value+"*********************");
if(arraySessionParam==null || !arraySessionParam.isCorrect(value)){
throwNewLoginException("Entered code does not match with the image code.Session:"+(arraySessionParam==null?"null":arraySessionParam.getAnswer())+" Param:"+ value);
// throwUserLoginException(new Exception("Entered code does not match with the image code."));
httpGetterCallbackSessionCaptcha.setValue(null);
} catch (UnsupportedCallbackException e) {
throwNewLoginException("An error occurred while trying to validate credentials.");
} catch (IOException e) {
throwUserLoginException(e, LoginExceptionDetails.IO_EXCEPTION);
// Retrieve the user credentials via the callback
// handler.
// In this case we get the user name from the HTTP
// NameCallback.
// NameCallback nameCallback = new NameCallback("User name: ");
/* The type and the name specify which part of the HTTP request
* should be retrieved. For Web container authentication, the
* supported types are defined in the interface
* com.sap.engine.lib.security.http.HttpCallback.
* For programmatical authentication with custom callback
* handler the supported types depend on the used callback handler.
// try {
// callbackHandler.handle(new Callback[] {nameCallback});
// catch (UnsupportedCallbackException e) {
// return false;
// catch (IOException e) {
// throwUserLoginException(e, LoginExceptionDetails.IO_EXCEPTION);
// userName = nameCallback.getName();
// if( userName == null || userName.length() == 0 ) {
// return false;
/* When you know the user name, update the user information
* using data from the persistence. The operation must
* be done before the user credentials checks. This method also
* checks the user name so that if a user with that name does not
* exist in the active user store, a
* java.lang.SecurityException is thrown.
// try {
// refreshUserInfo(userName);
// } catch (SecurityException e) {
// throwUserLoginException(e);
/* Checks if the given user name starts with the specified
* prefix in the login module options. If no prefix is specified,
* then all users are trusted.
// String prefix = (String) options.get("user_name_prefix");
// if ((prefix != null) && !userName.startsWith(prefix)) {
// throwNewLoginException("The user is not trusted.");
/* This is done if the authentication of the login module is
* successful.
* Only one and exactly one login module from the stack must put
* the user name in the shared state. This user name represents
* the authenticated user.
* For example if the login attempt is successful, method
* getRemoteUser() of
* the HTTP request will retrieve exactly this name.
if (sharedState.get(AbstractLoginModule.NAME) == null) {
sharedState.put(AbstractLoginModule.NAME, userName);
nameSet = true;
successful = true;
return true;
* Commit the login. This is the second part of the authentication
* process.
* If a user name has been stored by the login() method,
* the user name is added to the subject as a new principal.
public boolean commit() throws LoginException {
if (successful) {
/* The principals that are added to the subject should
* implement java.security.Principal.You can use the class
* com.sap.engine.lib.security.Principal for this purpose.
Principal principal = new Principal(userName);
subject.getPrincipals().add(principal);
/* If the login is successful, then the principal corresponding
* to the <userName> (the same user name that has been added
* to the subject) must be added in the shared state too.
* This principal is considered to be the main principal
* representing the user.
* For example, this principal will be retrieved from method
* getUserPrincipal() of the HTTP request.
if (nameSet) {
sharedState.put(AbstractLoginModule.PRINCIPAL, principal);
} else {
userName = null;
return true;
* Abort the authentication process.
public boolean abort() throws LoginException {
if (successful) {
userName = null;
successful = false;
return true;
* Log out the user. Also removes the principals and
* destroys or removes the credentials that were associated
* with the user during the commit phase.
public boolean logout() throws LoginException {
// Remove principals and credentials from subject
if (successful) {
subject.getPrincipals(Principal.class).clear();
successful = false;
return true;
private String getRequestValue(String parameterName)
     throws LoginException {
       HttpGetterCallback httpGetterCallback = new HttpGetterCallback();
       httpGetterCallback.setType(HttpCallback.REQUEST_PARAMETER);
       httpGetterCallback.setName(parameterName);
       String value = null;
       try {
      callbackHandler.handle(new Callback[] { httpGetterCallback });
           String[] arrayRequestparam = (String[]) httpGetterCallback.getValue();
           value = arrayRequestparam[0];
       } catch (UnsupportedCallbackException e) {
            return null;
       } catch (IOException e) {
            throwUserLoginException(e, LoginExceptionDetails.IO_EXCEPTION);
       return value;
Regards
Ramanender Singh

Ramanender,
JAAS modules usually requires a restart whenever you need to change them. So be very careful with what you expect once you re-deploy your code.
Once the library is loaded it will never reload itself until you perform a restart of the VM.
Connect to the debug port may help, but basic debugging will not take you too far either.
I would recommend you to use the log tracing facility on your code. Just enter the following class attribute:
import com.sap.tc.logging.Location;
private static final Location trace = Location.getLocation(<your_classname_here>.class);
trace.warningT("Some Warning Text Here..." + variable here);
trace.debugT("Some Warning Text Here..." + variable here);
You may need to go NWA and set the Location Severity Level to Debug according to your needs.
Leave the trace code on your module for IT personnel to debug it if necessary. Don't forget to have the severity level of your code properly set.
Meaning: You don't want to have every trace message your module sills out with warningT() or infoT().
There is a excellent blog here on how this works
Then you will be able to inspect some variable contents while the callbackhandler is being executed.
Pay special attention with the timing - variables have a lifetime when dealing with login modules.
Use the entering(<method_name>) and exiting(<method_name> just ot make sure where in the code the variable should be populated and when.
BR,
Ivan

Custom Login Module for Tomcat to procted apps using Oracle Access Manager

Hi all,
I have the following scenario.
A web application deployed in Tomcat to be protected using OAM. One solution is to use Access Gate though we have other alternative as Proxy infront of Tomcat with a webgate. Now I am implementing the Access Gate solution.
So, when the user clicks the tomcat application, then the prompt (BASIC) appears for login details. custom login module should kick in and take those login details and authenticate against OAM using Access SDK API.
I have created access gate profile and installed Access SDK. Ran the ConfigureAccessGateTool as well.
I did some research googling for login module. I came to know that we need to write a custom realm for it. So, this realm implementation involves specifying role-name etc., in web.xml where the role-name would have been defined in tomcat-users.xml.
This means that the user trying to authenticate against OAM has to have some roles defined in Tomcat to login. I didnot understand the flow end to end as how this will work.
Please let me know if anybody has done this of customization.
Thanks,
Mahendra.

Hi Ambarish,
Initially I thought of implementing the way you suggested in Option 2.
But there will be various redirections when we use option 2 as the login page should redirect it to a page where OAM authentication and authorization stuff has to be handled. And accordingly we have to redirect it to specific pages upon successful atn and atz. Hence, I was opted using Custom Login Module.
However, I have been trying Option 2 now. In web.xml, I have specified a login page with FORM scheme. The login redirects it to another page say OAM_Authentication_Handler.jsp. Here we code which serves atn and atz. Upon doing this, I have observed that the protected resource in OAM is not getting evaluated using the method
String ms_protocol = "http";
String ms_method = "GET";
String ms_resource = "http://localhost:8080/FormLogin/private.jsp";
ObResourceRequest rrq = new ObResourceRequest(ms_protocol, ms_resource, ms_method);
The method rrq.isProtected() is returning false which implies it to unprotected. I have tested using Access Tester for the resource and it results in expected behaviour.
Is there any limitation here by using this approach?
Any ideas?
Thanks,
Mahendra.

Login module for the J2EE application

Hi ,
I am trying to use the BasicPasswordLoginModule for my J2EE application which will be deployed in the SAP J2EE engine.My application will not be accessed through the portal.
I am having a login screen in my application for which i want to use the already avaliable login module. ie.. BasicPasswordLoginModule.
When i am trying to get the login(). i am getting the following the error.
"javax.security.auth.login.LoginException: No LoginModules configured for BasicPasswordLoginModule".
Please let me know what needs to be done.
PS: The version environment is CE 7.1
Regards
Abu Bakar

Hi Julius
I am totally confused, my application is a pure J2EE application which has only one screen which just displays the details. And i want only the login screen to be implemented. I have gone through a couple of dec from sap which tells to created a custom login module if requiredl but i want to user the FORM based authentication and use the BasicPasswordLoginModule(in-built in WAS)
All that i am doing is written a web.xml with the following information:
<login-config>
   <auth-method>FORM</auth-method>
   <form-login-config>
   <form-login-page>/home.jsp</form-login-page>
   <form-error-page>/relogin.jsp</form-error-page>
   </form-login-config>
</login-config>
<security-role>
    <role-name>App_Viewer</role-name>
</security-role>
web-j2ee-engine with following information:
<security-role-map>
          <role-name>App_Viewer</role-name>
           <server-role-name>Administrator</server-role-name>
     </security-role-map>
     <login-module-configuration>
     <login-module-stack>
     
          <login-module>
          
               <login-module-name>BasicPasswordLoginModule</login-module-name>
               <flag>SUFFICIENT</flag>
               <options>
                    <option>
                    
                    <name>UserNamePrefix</name>
                    <value>Admin</value>
                    </option>
               </options>
          </login-module>
     </login-module-stack>
     <security-policy-domain></security-policy-domain>
</login-module-configuration>
And I am not sure, if the above mentioned details are enough. My implementation code is as follows:
try {
          HttpServletRequest request = (HttpServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();
          HttpServletResponse response = (HttpServletResponse) FacesContext.getCurrentInstance().getExternalContext().getResponse();
          request.setAttribute(ILoginConstants.LOGON_UID_ALIAS, this.getUserName());
          request.setAttribute(ILoginConstants.LOGON_PWD_ALIAS, this.getPassword());
          UMFactory.getLogonAuthenticator().logon(request, response, "BasicPasswordLoginModule");
          status = success;
     } catch (Exception e) {
          e.printStackTrace();
          status = e.toString();
In the NWA i have just configured the UserNamePrefix with Admin, thats all . Since the form login authentication method is already configure with the BasicPasswordLoginModule, I left it untouched.
I also implemented a custom login module and deployed it but not sure how to use it in my code.
Please let me know if i am in the rite track. Correct me if i am wrong. At the end of the day i want to use the login screen just to get authenticated. I am also not bothered about the password changing etc.. As the users who are going to use my application are the users in the Identity Management. Few portions of my screen should be allowed to be displayed based on the roles.
PS: My application is not configured in the portal. Its an independent application deployed on the WAS(CE 7.1).
Please advice
Regards
Abu Bakar

HP Enterprise Integration Module for SAP - Windows Server 2008

Is there a download for the HP Enterprise Integration Module which will run on Windows Server 2008 for QC Version 10? HP Support has directed me to SAP Support for the Integration Versino 2.5 and above.

Hello John,
now I have a resolution.
I have deinstalled the MS SQL 2008 and install MS SQL 2005 plus SP2 at windows 2008 64bit VMware.
After reinstall HP Quality Center everything works fine.
( SQL 2008 is not official supported )
But there is another problem with the HP Enterprise Integration module 2.50 for SAP Solution Manager 7.0 EhP1,
the installer has a problem and does not work at windows 2008.
- this is a known HP problem and they should be published a newer version without the installer problem.
Today (april 6) I can't find an update, takes a while ... the "bad" version "setup_win.exe" has 132.327 kb.
you can only download the package from:
http://update.external.hp.com/qualitycenter/qc100/ent/enterprise_integration/index.html
you can find all add-ins at:
http://update.external.hp.com/qualitycenter/qc100/index.html
You should patch HP QC 10.00 with patch 10, see note 1329891 for details, takes 10 minutes or so.
With reards,
Michael

DBMS based custom login module for ADF 11g on Web Logic Server (10.3.1.0)

We have the requirement of creating a login page, wherein the authentication is performed against users records stored in a specific table in Oracle Database. The ADF 11g developer guide does not provide any example to accomplish the same. Though there are numerous examples of achieving the same using OC4J, but there is none available to achieve this on Web Logic Server. Do we have any documentation or information available on this?

User,
Have a search on the forum or check the WLS documentation. WLS has built-in authenticators for this that you can likely use.
John

Custom login module error: Login permission not granted for myapp (myuser)

I have developed a custom login module for my application. I have followed the steps outlined in security guide and other postings. I could not log into the application when I access EJBs from an RMI client. I get the following error.
Login permission not granted for myapp (myuser)
I did grant the login permission to myuser.
I am using OC4J 10.1.3.1.0
Here are the steps I followed and the configuration files. Can anybody help me out?
1. Created a custom login module and packaged it in EAR along with other classes. In the commit method, I added my user into principals of subject. Here is the code,
==================================================================
public boolean commit() throws LoginException {
try {
if (!loginOk) {
return false;
Set<Principal> principals = subject.getPrincipals();
principals.add(user);
loginOk = true;
} finally {
// Some audit logs are written here.
return loginOk;
===============================================================
2. Added custom login module in orion-application.xml. Here are the relevant portions of orion-application.xml
===============================================================
<jazn provider="XML">
<property name="role.mapping.dynamic" value="true" />
<property name="custom.loginmodule.provider" value="true" />
<property name="role.compare.ignorecase" value="true" />
</jazn>
<jazn-loginconfig>
<application>
<name>myApp</name>
<login-modules>
<login-module>
<class>com.test.myServerLoginModule</class>
<control-flag>required</control-flag>
<options>
<option>
<name>maxRetries</name>
<value>3</value>
</option>
<option>
<name>debug</name>
<value>true</value>
</option>
</options>
</login-module>
</login-modules>
</application>
</jazn-loginconfig>
<namespace-access>
<read-access>
<namespace-resource root="">
<security-role-mapping name="myUser">
<group name="users"/>
<group name="oc4j-app-administrators"/>
</security-role-mapping>
<security-role-mapping name="esp_operator">
<group name="users"/>
<group name="oc4j-app-administrators"/>
</security-role-mapping>
</namespace-resource>
</read-access>
</namespace-access>
===============================================================
3. After the application is deployed on the EAR, I can see the custom login module in system-jazn-data.xml. The command line jazn admin tool lists my custom login module for my application.
4. I have an RMI client, the client JNDI properties are
==============================================================
java.naming.factory.initial=oracle.j2ee.naming.ApplicationClientInitialContextFactory
java.naming.factory.url.pkgs=oracle.j2ee.naming
==============================================================
The value for java.naming.provider.url is constructed dynamically and it is ormi://myserver:23791/myapp
java.naming.security.principal is set to the user who is trying to login, myuser, in this case.
java.naming.security.credentials is set to the password entered by myuser, password in this case.
5. I used jazn admin tool to grant login permission to my user.
===============================================================
a. Added user
java -jar jazn.jar -user oc4jadmin -password welcome -adduser jazn.com myuser password
b. Grant roles
java -jar jazn.jar -user oc4jadmin -password welcome -grantrole users ja
zn.com myuser
java -jar jazn.jar -user oc4jadmin -password welcome -grantrole oc4j-app
-administrators jazn.com myuser
c. Grant RMI permission
java -jar jazn.jar -user oc4jadmin -password welcome -grantperm jazn.com
-user myuser com.evermind.server.rmi.RMIPermission login
===============================================================
After the permission is granted, the folowing piece of XML is added to system-jazn-data.xml.
===============================================================
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>user</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmUser</class>
                         <name>jazn.com/esp_administrator</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
          </permissions>
     </grant>
==============================================================
My principal class is not of type, oracle.security.jazn.spi.xml.XMLRealmUser. Hence, I changed system-jazn-data.xml to include com.test.MyUser instead of oracle.security.jazn.spi.xml.XMLRealmUser. Either way, I get Not Authorized and Login permission not granted for myapp (myuser).
Can anybody help me out, please?
Thank you,
Sri
Message was edited by:
user532586

I finally got it to work. But I have a problem granting RMI Permission "login", if the depth of my Principal class within the inheritance hierarachy is more than one. My hierarachy of my principal class is
Object --> ObjectA --> ObjectB --> ObjectC --> ObjectD
ObjectD is my principal class. ObjectB implements java.security.Principal. ObjectA has implementations for methods equals, hashcode and toString. ObjectB has implementations for getName.
When I try to grant RMI permission for ObjectD, I get an error that says null.
If I override the methods, equals, hashcode, toString, and getName in ObjectD and provide implementations, I still could not grant permission using jazn tool. I get error that says null. If I update the system-jazn-data.xml with the following grant tag, I could get into the application without any errors.
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <class>com.test.ObjectD</class>
                         <name>developers</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
          </permissions>
     </grant>
If I create a new class, myPrincipal that implements java.security.Principal, I donot have any problems. I can grant permission and access application.
Any ideas why I could not use ObjectD as my principal class for granting RMI permission?
Message was edited by:
user532586

Urgent: JAAS Login Module Deployment Problem

Hi,
I have developed a JAAS Login module for the portal (EP6 SP9 sneak preview) and i am getting the following error:
GroupAssignmentLoginModuleLibrary does not exist in LoadContextWrapper.modifyName.
com.sap.engine.services.security.exceptions.BaseSecurityException: Can not load a login Module
The next line is a ClassNotFoundException for the Login Module and the class found in negative cache.
Please let me know if you know the solution to this problem.
It is an urgent issue and a solution will be suitably rewarded.
Regards,
Vibhu

Hi Diego,
Scenario 1: SAP EP to SAP Backend Integration
      In this scenario the most commonly used strategy
      is SAP logon tickets. As far as I know this is the
      best and simple way to implement SSO.
Scenario 2: SAP EP to Non SAP systems.
      In this scenario various mechanisms can be used.
      It depends on the application you are integrating
      with. SAP does deliver SSO soultions with Lotus
      Notes and Outlook etc. If supported probably it is
      simple to use the SAP solution [Reliability and
      Support].
Scenario 3: Enterprise Uses third party authetication
      Software.
      For the authntication if the company chooses to use
      some third party product like SiteMinder etc, then
      you can simply use this solution for SAP EP authe-
      tication, and also all your other enterprise
      applications based on the product support. But SAP
      EP to other SAP systems be best integrated with SAP
      logon tickets.
Scenario 4: SSO using homegrown authetication or some
      third party JAAS module.
      If you have significant applications that are home
      grown that uses some custom authentication mecha-
      nism (Example: Authentication based on ID and
      Password stored in company database ) you can write
      a JAAS module extention to authenticate using that
      database. In other words JAAS is flexible and
      for using external authentication mechanisms.
There are several mechanisms available that all depends
on your internal applications/security mechanism/integration etc.
Here is the link to one of the good articles on SDN about the SAP supported SSO mechanisms.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/58094632-0301-0010-a391-fc0de26f010e
Hope this information is useful.
-Venkat Malempati

Assigning a login module to a Web Dynpro application

Hi everybody,
I would like a Web Dynpro application to use a custom login module for authentication. How can I do this?
What I found is the Security Provider (in the Visual Administrator tool) where I can add a login module to the "form" authentication mechanism for example. But if I do this I think all applications using this mechanism have to use my custom login module, right?
I wonder if I have to add my Web Dynpro application as a component to the Security Provider so that I can assign login modules to it. Am I on the right way? If yes, how can I do this? If I choose "Add" from the "Policy Configurations" tab a popup appears where I can enter the name for a new component. How do I specify my application there?
Thanks in advance for all answers,
Torben

Hi,
Web Dynpro applications use the ticket authentication template. U wud need to add your login module to the ticket template's login stack.
Incase you are accessing the Web Dynpro applications thru the EP u wud need to make changes to the authschemes.xml file too.
regards,
Vishal

Custom Login Module - Commit Method return TRUE always?

Hi,
I am creating a custom login module for my portal authentication.
For the login module, should the commit() method always return TRUE?
The example code on help.sap.com indicates yes to this question.
However, the JAVA Sun standard indicates that commit should return FALSE if the preceding login method returned FALSE.
Does the SAP example stray from the SUN standard? How should I code the commit() method such that it works (Always TRUE, or follow lead of login() method)?
Regards,
Kevin

Hi Kevin,
I'm actually working with this document: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/jaas%20login%20module%20development%20on%20webas%20java%20640.pdf#search=%22classloader%20sda%20jar%20reference%22">JAAS Login Modules</a>.
There is also example code. If it should be ignored they return false, otherwise true (page 32).
Regards,
Marcus
Message was edited by: Marcus Freiheit

Can I get the resource in a JAAS login module?

G'day,
I am writing a custom JAAS login module for deplyment in Netweaver application server. I'd like to get information about the resource that is protected by that login module (specifically, the URL).
The HttpGetterCallback class does not provide this information. All I can get is the host name and port from the HTTP headers.
Is there any way to get the full URL of the resource within a login module?
-- Geoff

G'day,
Note also that I tried using the WebCallback class, which has a getRequest() method that returns a HttpServletRequest.
But this callback seems to be ignored by the callback handler used in Netweaver AS, as the getRequest() method returns null, even though the login module is used to protect a servlet.
[ As an aside, I passed a custom callback to the CallbackHandler supplied by Netweaver AS, and the callbackHandler.handle() method did not throw UnsupportedCallbackException, which seems to be in violation of the JAAS standard ]
So ... HttpGetterCallback does not return resource URL information, and WebCallback is apparently ignored by the callback handler (which should really throw an exception here).
Are there any other ways to get the URL of the resource in a Netweaver AS login module?

Problem in JASS Login Module

Hi All,
I am implementing the JAAS login module. I have created the class file, Library file and also created the SDA file .But while configuring an Application to Use the Login Module in Policy Configurations Components which Components should i choose to apply login module for portal.
My Scenario
   While logging into portal with a user id it should check the password in the some other system.
For this which component should I choose in the Policy Configurations → Authentication tab > components in Visual administrator.
Thanks & Regards
Praveen.K.T

Hi Dagfinn,
   This is the log which i got once i Log into the portal . defaulttrace.0.trc
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!FILESET[0, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.19.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5#0014221E20B500680000019D00001484000426C21E13447B#1168515077593#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#XIAFUSER#347##cgnsap28_SNW_16885150#XIAFUSER#40a1f1a0a16711dbaec80014221e20b5#SAPEngine_Application_Thread[impl:3]_73##0#0#Error#1#/System/Server#Plain###User XIAFUSER, IP address
HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].#
#1.5#0014221E20B5006D0000009700001484000426C21F9057F2#1168515102562#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Cannot write to transaction log TX119.tx.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.store(TransactionLogFileImpl.java:289)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onMessageRequest(SessionHandler.java:602)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:103)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.sendMessage(Session.java:1494)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:464)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:276)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:245)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.postEvent(ISPEventSession.java:231)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.fireEvent(ISPTimerEvent.java:298)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:336)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX119.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.store(TransactionLogFileImpl.java:279)
     ... 21 more
#1.5#0014221E20B5006D0000009900001484000426C21F905D72#1168515102562#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Cannot write to transaction log TX119.tx.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.sendMessage(Session.java:1496)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:464)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:276)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:245)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.postEvent(ISPEventSession.java:231)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.fireEvent(ISPTimerEvent.java:298)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:336)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006D0000009A00001484000426C21F905F05#1168515102562#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout()#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/Version#Plain###Exception occured during timer callback - Message posting Failed.#
#1.5#0014221E20B5006D0000009B00001484000426C21F907395#1168515102578#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Internal error.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:131)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.setCommitState(TransactionLogFileImpl.java:391)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onRollbackRequest(SessionHandler.java:430)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:112)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.rollback(Session.java:356)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.rollback(SessionImpl.java:206)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:249)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX119.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:123)
     ... 19 more
#1.5#0014221E20B5006D0000009D00001484000426C21F907951#1168515102578#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.rollback(SessionImpl.java:206)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:249)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006D0000009E00001484000426C21F9087B7#1168515102578#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Internal error.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:131)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.setCommitState(TransactionLogFileImpl.java:391)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onRollbackRequest(SessionHandler.java:430)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:112)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.rollback(Session.java:356)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:276)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX119.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:123)
     ... 22 more
#1.5#0014221E20B5006D000000A000001484000426C21F908D43#1168515102578#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:276)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006D000000A100001484000426C21F909BEE#1168515102578#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Internal error.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:131)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.setCommitState(TransactionLogFileImpl.java:391)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onRollbackRequest(SessionHandler.java:430)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:112)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.rollback(Session.java:356)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.connection.Connection.close(Connection.java:132)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.connectionClosed(QueueConnectionFactoryImpl.java:215)
     at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.close(ConnectionImpl.java:268)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionImpl.close(QueueConnectionImpl.java:69)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:287)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX119.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:123)
     ... 23 more
#1.5#0014221E20B5006D000000A300001484000426C21F90A23A#1168515102578#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.connection.Connection.close(Connection.java:132)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.connectionClosed(QueueConnectionFactoryImpl.java:215)
     at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.close(ConnectionImpl.java:268)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionImpl.close(QueueConnectionImpl.java:69)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:287)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006D000000A400001484000426C21F90A3F8#1168515102578#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/Version#Plain###Errors occured while closing Event Session#
#1.5#0014221E20B5006D000000A500001484000426C21F90A4EB#1168515102578#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/Version#Plain###Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.rollback(SessionImpl.java:206)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:249)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006D000000A600001484000426C21F90A642#1168515102578#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/Version#Plain###Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:276)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006D000000A700001484000426C21F90A7C8#1168515102578#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0####4f88a420a16711dbbd2c0014221e20b5#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/Version#Plain###Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.connection.Connection.close(Connection.java:132)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.connectionClosed(QueueConnectionFactoryImpl.java:215)
     at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.close(ConnectionImpl.java:268)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionImpl.close(QueueConnectionImpl.java:69)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:287)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006E000000A300001484000426C21FE01941#1168515107796#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#XIAFUSER#352##cgnsap28_SNW_16885150#XIAFUSER#52a4ff50a16711dbc8230014221e20b5#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/System/Server#Plain###User XIAFUSER, IP address
HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].#
#1.5#0014221E20B50069000000E300001484000426C220EE5949#1168515125500#com.sapmarkets.bam.jmxadapter.util.LogDirectory##com.sapmarkets.bam.jmxadapter.util.LogDirectory#J2EE_ADMIN#244####3fc43bd0a16711dba4820014221e20b5#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server#Plain###Error writing log directory entryG:
tmp
CGNSAP28_SNW_01_16885150_lv_.xml (Access is denied)#
#1.5#0014221E20B50069000000E500001484000426C220EE5AE4#1168515125500#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_ADMIN#244####3fc43bd0a16711dba4820014221e20b5#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register     a new log#
#1.5#0014221E20B50069000000E700001484000426C220EE5C53#1168515125500#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_ADMIN#244####3fc43bd0a16711dba4820014221e20b5#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server#Plain###com.sapmarkets.bam.util.BAMRuntimeException: <Localization failed: ResourceBundle='com.sapmarkets.bam.util.LogViewerMessages', ID='Error while writing to directory.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error while writing to directory.#
#1.5#0014221E20B50069000000E900001484000426C220EE6731#1168515125500#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_ADMIN#244####3fc43bd0a16711dba4820014221e20b5#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server#Plain###Originated from: com.sapmarkets.bam.util.BAMRuntimeException: <Localization failed: ResourceBundle='com.sapmarkets.bam.util.LogViewerMessages', ID='Error while writing to directory.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error while writing to directory.
     at com.sapmarkets.bam.jmxadapter.util.LogDirectory.write(LogDirectory.java:779)
     at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.addToDirectory(AbstractFileLogHandler.java:361)
     at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:249)
     at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
     at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
     at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
     at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
     at com.sap.tc.logging.LoggingManager.notifyAddLog(LoggingManager.java:342)
     at com.sap.tc.logging.LogController.addLog(LogController.java:1317)
     at com.sap.sql.trace.SQLTrace.onJ2ee(SQLTrace.java:323)
     at com.sap.engine.services.log_configurator.admin.LogConfigurator.setSQLTrace(LogConfigurator.java:1373)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.setAttribute(DefaultMBeanInvoker.java:217)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.setAttribute(AdditionalInfoProviderMBean.java:244)
     at com.sap.pj.jmx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:849)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.setAttribute(MBeanServerWrapperInterceptor.java:399)
     at com.sap.engine.services.jmx.CompletionInterceptor.setAttribute(CompletionInterceptor.java:520)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.setAttribute(BasicMBeanServerInterceptor.java:403)
     at com.sap.jmx.provider.ProviderInterceptor.setAttribute(ProviderInterceptor.java:289)
     at com.sap.engine.services.jmx.RedirectInterceptor.setAttribute(RedirectInterceptor.java:466)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.setAttribute(MBeanServerInterceptorChain.java:312)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.setAttribute(MBeanServerSecurityWrapper.java:378)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:146)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.setAttribute(ClusterInterceptor.java:1260)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:117)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000D300001484000426C22119800E#1168515128328#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#XIAFUSER#355##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/System/Server#Plain###User XIAFUSER, IP address
HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].#
#1.5#0014221E20B5006B000000D400001484000426C2215A561B#1168515132578#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Cannot write to transaction log TX11d.tx.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.store(TransactionLogFileImpl.java:289)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onMessageRequest(SessionHandler.java:602)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:103)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.sendMessage(Session.java:1494)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:464)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:276)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:245)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.postEvent(ISPEventSession.java:231)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.fireEvent(ISPTimerEvent.java:298)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:336)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX11d.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.store(TransactionLogFileImpl.java:279)
     ... 21 more
#1.5#0014221E20B5006B000000D600001484000426C2215A5C1E#1168515132578#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Cannot write to transaction log TX11d.tx.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.sendMessage(Session.java:1496)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:464)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:276)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:245)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.postEvent(ISPEventSession.java:231)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.fireEvent(ISPTimerEvent.java:298)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:336)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000D700001484000426C2215A5D37#1168515132578#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout()#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/Version#Plain###Exception occured during timer callback - Message posting Failed.#
#1.5#0014221E20B5006B000000D800001484000426C2215A7168#1168515132593#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Internal error.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:131)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.setCommitState(TransactionLogFileImpl.java:391)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onRollbackRequest(SessionHandler.java:430)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:112)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.rollback(Session.java:356)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.rollback(SessionImpl.java:206)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:249)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX11d.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:123)
     ... 19 more
#1.5#0014221E20B5006B000000DA00001484000426C2215A7665#1168515132593#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.rollback(SessionImpl.java:206)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:249)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000DB00001484000426C2215A836C#1168515132593#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Internal error.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:131)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.setCommitState(TransactionLogFileImpl.java:391)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onRollbackRequest(SessionHandler.java:430)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:112)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.rollback(Session.java:356)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:276)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX11d.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:123)
     ... 22 more
#1.5#0014221E20B5006B000000DD00001484000426C2215A88D2#1168515132593#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:276)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000DE00001484000426C2215A95CC#1168515132593#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Internal error.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:131)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.setCommitState(TransactionLogFileImpl.java:391)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onRollbackRequest(SessionHandler.java:430)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:112)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.rollback(Session.java:356)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.connection.Connection.close(Connection.java:132)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.connectionClosed(QueueConnectionFactoryImpl.java:215)
     at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.close(ConnectionImpl.java:268)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionImpl.close(QueueConnectionImpl.java:69)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:287)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX11d.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.setState(TransactionLogFileImpl.java:123)
     ... 23 more
#1.5#0014221E20B5006B000000E000001484000426C2215A9B81#1168515132593#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.connection.Connection.close(Connection.java:132)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.connectionClosed(QueueConnectionFactoryImpl.java:215)
     at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.close(ConnectionImpl.java:268)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionImpl.close(QueueConnectionImpl.java:69)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:287)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000E100001484000426C2215A9D34#1168515132593#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/Version#Plain###Errors occured while closing Event Session#
#1.5#0014221E20B5006B000000E200001484000426C2215A9E25#1168515132593#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/Version#Plain###Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.rollback(SessionImpl.java:206)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:249)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000E300001484000426C2215A9F86#1168515132593#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/Version#Plain###Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:276)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B5006B000000E400001484000426C2215AA0F9#1168515132593#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close()#J2EE_GUEST#0##cgnsap28_SNW_16885150#XIAFUSER#5edd0c90a16711dbb44c0014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/Version#Plain###Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.rollback(Session.java:357)
     at com.sap.jms.client.session.Session.close(Session.java:184)
     at com.sap.jms.client.connection.Connection.close(Connection.java:132)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.connectionClosed(QueueConnectionFactoryImpl.java:215)
     at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.close(ConnectionImpl.java:268)
     at com.sap.engine.services.jmsconnector.cci.QueueConnectionImpl.close(QueueConnectionImpl.java:69)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:287)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:366)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0014221E20B500690000010000001484000426C221AB8C9D#1168515137906#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#XIAFUSER#358##cgnsap28_SNW_16885150#XIAFUSER#6494fa30a16711dbb56f0014221e20b5#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server#Plain###User XIAFUSER, IP address
HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].#
#1.5#0014221E20B5006B000000E500001484000426C22324289D#1168515162593#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0####7350a510a16711dba0c40014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerException: Cannot write to transaction log TX121.tx.
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.store(TransactionLogFileImpl.java:289)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.onMessageRequest(SessionHandler.java:602)
     at com.sap.jms.server.sessioncontainer.handler.SessionHandler.process(SessionHandler.java:103)
     at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
     at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
     at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
     at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
     at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:572)
     at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait(SynchronousNetworkAdapter.java:130)
     at com.sap.jms.client.connection.Connection.sendPacket(Connection.java:656)
     at com.sap.jms.client.session.Session.sendMessage(Session.java:1494)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:464)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:276)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:245)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.postEvent(ISPEventSession.java:231)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.fireEvent(ISPTimerEvent.java:298)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:336)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.FileNotFoundException: C:
Documents and Settings
snwadm
sapjms
101a59e
1
TX121.tx (Access is denied)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl$TxContextImpl.assureOpened(TransactionLogFileImpl.java:50)
     at com.sap.jms.server.sessioncontainer.transactionlog.TransactionLogFileImpl.store(TransactionLogFileImpl.java:279)
     ... 21 more
#1.5#0014221E20B5006B000000E700001484000426C223242E19#1168515162593#com.sap.jms.client.session.Session##com.sap.jms.client.session.Session#J2EE_GUEST#0####7350a510a16711dba0c40014221e20b5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Cannot write to transaction log TX121.tx.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2533)
     at com.sap.jms.client.session.Session.sendMessage(Session.java:1496)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:464)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:276)
     at com.sap.jms.client.session.MessageProducer.send(MessageProducer.java:245)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.postEvent(ISPEventSession.java:231)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.fireEvent(ISPTimerEvent.java:298)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:336)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run

OpenSSO Enterprise Login Module for IDM 7.1

Similar Messages

Maybe you are looking for