Authenticating Host SPN using Kerberos Login module

Hi,
I have written an application that needs to support Java GSS based context establishment using Java's Kerberos Login module with the clients.This application is hosted in Tomcat and I have a limitation that tomcat is running as "LocalSystem" account on the host machine(Not to confuse with Administrator account on the host machine) so it is not having password.
On the AD to which this host is connected has SPN registered for this host machine like any other computer account. But my doubt is how will I authenticate my application(Using Kerberos Login module) using that Host SPN if I do not have any password for the "LocalSystem". I am giving user name as "HOST/<machine-name", or "<machine-name>" but it fails at the application side saying no encryption key found. If I try to give some random password I get error message from AD saying that Pre Authentication failed.
Without authentication my application to AD I am not able to get the Kerberos Key which is required for context establishment for GSS.
Any help in this regard will be really helpful.
Thanks.

Thanks for your response!
My application is just an authentication module in a bigger application which is not under my control. This application is hosted on Apache Tomcat and provide both the options to run as "LocalSystem" account and domain account. So I have to provide support for both the options.
I am getting increasingly convinced that Java Kerberos module can't handle the authentication for "LocalSystem" account and I need to opt for some Windows Native Apis for that. If that is the case Can someone tell me how can i proceed for that. I have no idea which Windows apis to use for it.
Thanks.
Edited by: Java-Dev-01 on Mar 14, 2010 6:03 AM

Similar Messages

  • Portal authentication using two login module stacks?

    G'day,
    I am noticing something odd when I authenticate to the portal: there are two login module stacks used.
    Background: I have created a custom logon page, which is basically a form with username/password input as per [this guide|http://help.sap.com/saphelp_nw04/helpdata/en/62/601e1eebf54ca6a97e2873c8c63517/content.htm|Changing the logon screen]. I then modified the authschemes.xml file by defining a new authscheme "mylogon" that uses my own login module stack ("mystack") and uses the new logon page ("mylogonform"). This new authscheme is then made the default reference:
    <authscheme name="mylogon">
      <authentication-template>mystack</authentication-template>
      <priority>21</priority>
      <frontendtype>2</frontendtype>
      <frontendtarget>com.foo.bar.mylogonpage</frontendtarget>
    </authscheme>
    <authscheme-refs>
      <authscheme-ref name="default"><authscheme>mylogon</authscheme></authscheme-ref>
      <authscheme-ref name="UserAdminScheme"><authscheme>mylogon</authscheme></authscheme-ref>
    </authscheme-refs>
    When I want to access the portal, up pops the "mylogonform" page, and on clicking the "submit" button the portal page for the user is shown.
    Now here is the interesting thing: when the "ticket" login module stack is unchanged (ie. it uses the BasicpasswordLoginModule), then the log shows that authentication to the portal uses just my login module.
    This can be seen as follows, where I navigate to the portal, logon as one user, then logoff and logon as another user:
    Message : LOGIN.OK
    User: tu-1
    Authentication Stack: mystack
    Message : LOGOUT.OK
    User: tu-1
    Authentication Stack: mystack
    Message : LOGIN.OK
    User: Administrator
    Authentication Stack: mystack
    The "mylogonform" page is shown when logon is required in both cases.
    However, if I modify the "ticket" login module stack by replacing the BasicPasswordLogonModule with a custom logon module that does automatic authentication, then the following is observed when the "mylogonform" page is displayed:
    Message : LOGIN.FAILED
    User: N/A
    Authentication Stack: ticket
    Message : LOGIN.OK
    User: tu-1
    Authentication Stack: ticket
    For some reason, the modified "ticket" login module stack is now being executed, which was not the case when this login module stack was unmodified.
    This stack automatically authenticates the current user (the initial failure is because the new login module asks the browser to send authentication data), and this "failure" causes the logon form to be displayed.
    I can logon to the portal as the same user, and the logs show that "mystack" login module stack is used:
    Message : LOGIN.OK
    User: tu-1
    Authentication Stack: mystack
    Logoff shows that "mystack" is used for the actual logoff, but "ticket" is called again automatically and succeeds:
    Message : LOGOUT.OK
    User: tu-1
    Authentication Stack: mystack
    Message : LOGIN.FAILED
    User: N/A
    Authentication Stack: ticket
    Message : LOGIN.OK
    User: tu-1
    Authentication Stack: ticket
    (Again, the initial logon failure is the new login module requesting that the browser send authentication data in the next request).
    This brings up the "mylogonform" page, even though it appears that a user has already been authenticated. If I try to logon as another user, the following is shown:
    Message : LOGIN.FAILED
    User: Administrator
    Authentication Stack: mystack
    Login Module                                                            Flag        Initialize  Login      Commit     Abort      Details
    com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          exception  false      true       authscheme not sufficient: basicauthentication<mylogonform
    Central Checks                                                                                exception             Call logout before login.
    I guess one cannot authenticate as a new user until the current user has been logged out.
    So ... why does the "ticket" login module get called in the second case, but not in the first case (or only shows logging in the second case) ?
    What is the logic behind portal authentication and showing a logon page?
    If I want to use custom authentication and a custom logon page, why is the "ticket" stack called at all?

    Jayesh,
    there is no such thing like "login module stacks". The <b>do</b> exist on the other hand:
    - login module
    - logon stacks
    Login module and logon stacks are part of the JAAS concept for defining a complex pluggable authentication scheme, original by SUN (see: java.sun.com/products/jaas)
    A logon process is defined by a logon stack which itself consists of several login modules. Each login module performs an authentication step. Example:
    login module 1: check if valid sap logon ticket provided
    if module 1 fails: then login module 2: request user id/password
    if module 2 succeeds: then login module 3: create new sap logon ticket for user
    You can define multiple logon stacks and configure individual applications to use the one stack or the other.
    The logon stack configuration is done using visual administrator. Here select the security provider service for configuring logon stacks.
    btw: As logon stacks are "java-only", there are no transaction names (which only exist on Web AS ABAP).
    Regards,
    Dominik

  • Kerberos Login Module

    Hi,
    I´m trying to configure SPNegoLoginModule for Kerberos Authentication using EP6 with EP SP15 according:
    http://help.sap.com/saphelp_nw04/helpdata/en/43/4e80824d155f86e10000000a1553f6/frameset.htm
    I know that there is a tool provided by SAP called SPNego Config Test Web App. How I get this?
    The portal server must be a Domain Controller?
    Thanks,
    Daniel.

    Hello Tom Bo,
    Thanks for reply. I´m implemented SPNego login module on SPS15 but When I try to log on with Internet Explorer the portal returns the message " user authentication failed".
    I´ve set the folowwing parameters:
      com.sap.spnego.uid.resolution.mode = simple
      com.sap.spnego.uid.resolution.attr = uniquename
    I dont know what's gng wrong.
    Regards,
    Daniel.

  • Help - using custom login module with embedded jdev oc4j to access ejb 3

    Hi All (Frank ??),
    I'm just wondering if anyone has successfully been able to leverage a custom login module in combination
    with a client that connects to a local EJB 3 stateless session bean through Jdeveloper 10.1.3.2's embedded oc4j.
    I have spent 2+ days trying to get this to work - and i think I resound now to the fact im going to
    have to deploy to oc4j standalone instead.
    I got close.. but finally was trumped with the following error from the client trying to access the ejb:-
    javax.naming.NoPermissionException: Not allowed to look up XXXXXX, check the namespace-access tag
    setting in orion-application.xml for details.
    Using the various guides available, I had no problem getting the custom login module working
    with a local servlet running from JDev's embedded oc4j.. however with ejb - no such luck.
    I have a roles table (possible values Member, Admin) - that maps to sr_Member and sr_Admin
    respectively in various config files.
    I'm using EJB 3 annotations for protecting methods .. for example
    @RolesAllowed("sr_Member")
    Steps that I had to do so far :-
    In <jdevhome>\jdev\system\oracle.jwee.10.1.3.40.66\embedded-oc4j\config\system-jazn-data.xml1) Add custom login module
        <application>
          <name>current-workspace-app</name>
          <login-modules>
            <login-module>
              <class>kr.security.KnowRushLoginModule</class>
              <control-flag>required</control-flag>
              <options>
                <option>
                  <name>dataSource</name>
                  <value>jdbc/DB_XE_KNOWRUSHDS</value>
                </option>
                <option>
                  <name>user.table</name>
                  <value>users</value>
                </option>
                <option>
                  <name>user.pk.column</name>
                  <value>id</value>
                </option>
                <option>
                  <name>user.name.column</name>
                  <value>email_address</value>
                </option>
                <option>
                  <name>user.password.column</name>
                  <value>password</value>
                </option>
                <option>
                  <name>role.table</name>
                  <value>roles</value>
                </option>
                <option>
                  <name>role.to.user.fk.column</name>
                  <value>user_id</value>
                </option>
                <option>
                  <name>role.name.column</name>
                  <value>name</value>
                </option>
              </options>
            </login-module>
          </login-modules>
        </application>2) Grant login rmi permission to roles associated with custom login module (also in system-jazn-data.xml)
      <grant>
        <grantee>
          <principals>
            <principal>
              <realm-name>jazn.com</realm-name>
              <type>role</type>
              <class>kr.security.principals.KRRolePrincipal</class>
              <name>Admin</name>
            </principal>
          </principals>
        </grantee>
        <permissions>
          <permission>
            <class>com.evermind.server.rmi.RMIPermission</class>
            <name>login</name>
          </permission>
        </permissions>
      </grant>
      <grant>
        <grantee>
          <principals>
            <principal>
              <realm-name>jazn.com</realm-name>
              <type>role</type>
              <class>kr.security.principals.KRRolePrincipal</class>
              <name>Member</name>
            </principal>
          </principals>
        </grantee>
        <permissions>
          <permission>
            <class>com.evermind.server.rmi.RMIPermission</class>
            <name>login</name>
          </permission>
        </permissions>
      </grant>3) I've tried creating various oracle and j2ee deployment descriptors (even though ejb-jar.xml and orion-ejb-jar.xml get created automatically when running the session bean in jdev).
    My ejb-jar.xml contains :-
    <?xml version="1.0" encoding="utf-8"?>
    <ejb-jar xmlns ....
      <assembly-descriptor>
        <security-role>
          <role-name>sr_Admin</role-name>
        </security-role>
        <security-role>
          <role-name>sr_Member</role-name>
        </security-role>
      </assembly-descriptor>
    </ejb-jar>Note- i'm not specifying the enterprise-beans stuff, as JDev seems to populate this automatically.
    My orion-ejb-jar.xml contains ...
    <?xml version="1.0" encoding="utf-8"?>
    <orion-ejb-jar ...
      <assembly-descriptor>
        <security-role-mapping name="sr_Admin">
          <group name="Admin"></group>
        </security-role-mapping>
        <security-role-mapping name="sr_Member">
          <group name="Member"></group>
        </security-role-mapping>
        <default-method-access>
          <security-role-mapping name="sr_Member" impliesAll="true">
          </security-role-mapping>
        </default-method-access>
      </assembly-descriptor>My orion-application.xml contains ...
    <?xml version="1.0" encoding="utf-8"?>
    <orion-application xmlns ...
      <security-role-mapping name="sr_Admin">
        <group name="Admin"></group>
      </security-role-mapping>
      <security-role-mapping name="sr_Member">
        <group name="Member"></group>
      </security-role-mapping>
      <jazn provider="XML">
        <property name="role.mapping.dynamic" value="true"></property>
        <property name="custom.loginmodule.provider" value="true"></property>
      </jazn>
      <namespace-access>
        <read-access>
          <namespace-resource root="">
            <security-role-mapping name="sr_Admin">
              <group name="Admin"/>
              <group name="Member"/>
            </security-role-mapping>
          </namespace-resource>
        </read-access>
        <write-access>
          <namespace-resource root="">
            <security-role-mapping name="sr_Admin">
              <group name="Admin"/>
              <group name="Member"/>
            </security-role-mapping>
          </namespace-resource>
        </write-access>
      </namespace-access>
    </orion-application>My essentially auto-generated EJB 3 client does the following :-
          Hashtable env = new Hashtable();
          env.put(Context.SECURITY_PRINCIPAL, "matt.shannon");
          env.put(Context.SECURITY_CREDENTIALS, "welcome1");
          final Context context = new InitialContext(env);
          KRFacade kRFacade = (KRFacade)context.lookup("KRFacade");
    ...And throws the error
    20/04/2007 00:55:37 oracle.j2ee.rmi.RMIMessages
    EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
    WARNING: Exception returned by remote server: {0}
    javax.naming.NoPermissionException: Not allowed to look
    up KRFacade, check the namespace-access tag setting in
    orion-application.xml for details
         at
    com.evermind.server.rmi.RMIClientConnection.handleLookupRe
    sponse(RMIClientConnection.java:819)
         at
    com.evermind.server.rmi.RMIClientConnection.handleOrmiComm
    andResponse(RMIClientConnection.java:283)
    ....I can see from the console that the user was successfully authenticated :-
    20/04/2007 00:55:37 kr.security.KnowRushLoginModule validate
    WARNING: [KnowRushLoginModule] User matt.shannon authenticated
    And that user is granted both the Admin, and Member roles.
    The test servlet using basic authentication correctly detects the user and roles perfectly...
      public void doGet(HttpServletRequest request,
                        HttpServletResponse response)
        throws ServletException, IOException
        LOGGER.log(Level.INFO,LOGPREFIX +"doGet called");
        response.setContentType(CONTENT_TYPE);
        PrintWriter out = response.getWriter();
        out.println("<html>");
        out.println("<head><title>ExampleServlet</title></head>");
        out.println("<body>");
        out.println("<p>The servlet has received a GET. This is the reply.</p>");
        out.println("<br> getRemoteUser = " + request.getRemoteUser());
        out.println("<br> getUserPrincipal = " + request.getUserPrincipal());
        out.println("<br> isUserInRole('sr_Admin') = "+request.isUserInRole("sr_Admin"));
        out.println("<br> isUserInRole('sr_Memeber') = "+request.isUserInRole("sr_Member"));Anyone got any ideas what could be going wrong?
    cheers
    Matt.
    Message was edited by:
    mshannon

    Thanks for the response. I checked out your blog and tried your suggestions. I'm sure it works well in standalone OC4J, but i was still unable to get it to function correctly from JDeveloper embedded.
    Did you ever get the code working directly from JDeveloper?
    Your custom code essentially seems to be the equivalent of a grant within system-jazn-data.xml.
    For example, the following grant to a custom jaas role (JAAS_ADMIN) that gets added by my custom login module gives them rmi login access :-
         <grant>
              <grantee>
                   <principals>
                        <principal>
                             <realm-name>jazn.com</realm-name>
                             <type>role</type>
                             <class>kr.security.principals.KRRolePrincipal</class>
                             <name>JAAS_Admin</name>
                        </principal>
                   </principals>
              </grantee>
              <permissions>
                   <permission>
                        <class>com.evermind.server.rmi.RMIPermission</class>
                        <name>login</name>
                   </permission>
              </permissions>
         </grant>If I add the following to orion-application.xml
      <!-- Granting login permission to users accessing this EJB. -->
      <namespace-access>
        <read-access>
          <namespace-resource root="">
            <security-role-mapping>
              <group name="JAAS_Admin"></group>
            </security-role-mapping>
          </namespace-resource>
        </read-access>Running a standalone client against the embedded jdev oc4j server gives the namespace-access error.
    I tried out your code by essentially creating a static reference to a singleton class that does the role lookup/provisioning with rmi login grant :-
    From custom login module :-
      private static KRSecurityHelper singleton = new KRSecurityHelper();
      protected Principal[] m_Principals;
        Vector v = new Vector();
          v.add(singleton.getCustomRmiConnectRole());
          // set principals in LoginModule
          m_Principals=(Principal[]) v.toArray(new Principal[v.size()]);
    Singleton class :-
    package kr.security;
    import com.evermind.server.rmi.RMIPermission;
    import java.util.logging.Level;
    import java.util.logging.Logger;
    import oracle.security.jazn.JAZNConfig;
    import oracle.security.jazn.policy.Grantee;
    import oracle.security.jazn.realm.Realm;
    import oracle.security.jazn.realm.RealmManager;
    import oracle.security.jazn.realm.RealmRole;
    import oracle.security.jazn.realm.RoleManager;
    import oracle.security.jazn.policy.JAZNPolicy;
    import oracle.security.jazn.JAZNException;
    public class KRSecurityHelper
      private static final Logger LOGGER = Logger.getLogger("kr.security");
      private static final String LOGPREFIX = "[KRSecurityHelper] ";
      public static String CUSTOM_RMI_CONNECT_ROLE = "remote_connect";
      private RealmRole m_Role = null;
      public KRSecurityHelper()
        LOGGER.log(Level.FINEST,LOGPREFIX +"calling JAZNConfig.getJAZNConfig");
        JAZNConfig jc = JAZNConfig.getJAZNConfig();
        LOGGER.log(Level.FINEST,LOGPREFIX +"calling jc.getRealmManager");
        RealmManager realmMgr = jc.getRealmManager();
        try
          // Get the default realm .. e.g. jazn.com
          LOGGER.log(Level.FINEST,LOGPREFIX +"calling jc.getGetDefaultRealm");
          Realm r = realmMgr.getRealm(jc.getDefaultRealm());
          LOGGER.log(Level.INFO,LOGPREFIX +"default realm: "+r.getName());
          // Access the role manager for the remote connection role
          LOGGER.log(Level.FINEST,
            LOGPREFIX +"calling default_realm.getRoleManager");
          RoleManager roleMgr = r.getRoleManager();
          LOGGER.log(Level.INFO,LOGPREFIX +"looking up custom role '"
            CUSTOM_RMI_CONNECT_ROLE "'");
          RealmRole rmiConnectRole = roleMgr.getRole(CUSTOM_RMI_CONNECT_ROLE);
          if (rmiConnectRole == null)
            LOGGER.log(Level.INFO,LOGPREFIX +"role does not exist, create it...");
            rmiConnectRole = roleMgr.createRole(CUSTOM_RMI_CONNECT_ROLE);
            LOGGER.log(Level.FINEST,LOGPREFIX +"constructing new grantee");
            Grantee gtee = new Grantee(rmiConnectRole);
            LOGGER.log(Level.FINEST,LOGPREFIX +"constructing login rmi permission");
            RMIPermission login = new RMIPermission("login");
            LOGGER.log(Level.FINEST,
              LOGPREFIX +"constructing subject.propagation rmi permission");
            RMIPermission subjectprop = new RMIPermission("subject.propagation");
            // make policy changes
            LOGGER.log(Level.FINEST,LOGPREFIX +"calling jc.getPolicy");
            JAZNPolicy policy = jc.getPolicy();
            if (policy != null)
              LOGGER.log(Level.INFO, LOGPREFIX
                + "add to policy grant for RMI 'login' permission to "
                + CUSTOM_RMI_CONNECT_ROLE);
              policy.grant(gtee, login);
              LOGGER.log(Level.INFO, LOGPREFIX
                + "add to policy grant for RMI 'subject.propagation' permission to "
                + CUSTOM_RMI_CONNECT_ROLE);
              policy.grant(gtee, subjectprop);
              // m_Role = rmiConnectRole;
              m_Role = roleMgr.getRole(CUSTOM_RMI_CONNECT_ROLE);
              LOGGER.log(Level.INFO, LOGPREFIX
                + m_Role.getName() + ":" + m_Role.getFullName() + ":" + m_Role.getFullName());
            else
              LOGGER.log(Level.WARNING,LOGPREFIX +"Cannot find jazn policy!");
          else
            LOGGER.log(Level.INFO,LOGPREFIX +"custom role already exists");
            m_Role = rmiConnectRole;
        catch (JAZNException e)
          LOGGER.log(Level.WARNING,
            LOGPREFIX +"Cannot configure JAZN for remote connections");
      public RealmRole getCustomRmiConnectRole()
        return m_Role;
    }Using the code approach and switching application.xml across so that namespace access is for the group remote_connect, I get the following error from my bean :-
    INFO: Login permission not granted for current-workspace-app (test.user)
    Thus, the login permission that I'm adding through the custom remote_connect role does not seem to work. Even if it did, i'm pretty sure I would still get that namespace error.
    This has been such a frustrating process. All the custom login module samples using embedded JDeveloper show simple j2ee servlet protection based on settings in web.xml.
    There are no samples showing jdeveloper embedded oc4j using ejb with custom login modules.
    Hopefully the oc4j jdev gurus like Frank can write a paper that demonstrates this.
    Matt.

  • LMS 3.2 Windows - 10 minute timeout while using TACACS+ Login Module

    Hello,
    we have changed our login module to TACACS+ (Non-ACS). All works fine when we use users which are set up in TACACS+. Using an account which does not exist (or only exists in CiscoWorks Local login module - even as fallback user) we register a timeout of 10 minutes until the login module fails the request (turned on Debugging and watching the stdout.log of tomcat). While running the backup.pl script it seems that the user "admin" tries to access the web server, but as this user is not set up in TACACS+ we have to wait 20 or more minutes until the backup starts. So, is there a way to set a timeout value for that login module?Is it known that the admin account is needed to perform the backup?
    Thanks and kind regards
    Allessandro

    This delay is coming from your TACACS server.  Can you shorten the authentication failure there?  As for the user ID, check your System Identity User under Common Services > Server > Security > System Identity Setup.  Make sure this use exists in the TACACS databases.

  • Security constraints not being applied after using custom login module

    I am using form based authentication and I applied the custom login module - DBProcLoginModule to work with the embedded OC4J (JDeveloper 10.1.3.2). I have specified two security contraints in web.xml. The authentication is working correctly, however the security contraints are not being applied. All users are able to access all url resources. The security constraints were working properly before applying the custom login module. Pls help.
    Leena

    Hi,
    if "All users are able to access all url resources" then this indicates that the RL isn't properly protected. If the authorization would fail then noone would have access and you would see error code 401
    Make sure the role names in web.xml are the same as added by the LoginModule. Also make sure you set the dynamic.role property and the custom security provider property in the orion-application.xml
    <jazn provider="XML">
         <property name="custom.loginmodule.provider" value="true"/>
         <property name="role.mapping.dynamic" value="true"/>
    </jazn>
    Note that the above is not required (because done automatically) if the custom LoginModule configuration is deployed through the orion-application.xml file
    Frank

  • Help : Call Login Module directly when iView is launched - without submit

    Hi there,
    we have developed a login module on for our NW2004S SP13 Portal, that checks the IP address of the client to be in a valid range. If so, the standard SAP login screen must be bypassed. If not, the standard login screen needs to be shown (we use the standard sap umLogonPage, we only made a copy z.com.portal.runtime.logon.par) and added to the portalapp.xml an entry which is a copy of the 'certlogon' entry..
    -> What we like to achieve is that the logonstack is called directly when the application is launched.
    a) Code below functions, but only one problem : when the IP Address is invalid (login module returns false), a blank page is shown instead of the default userid / pw page.
        In case of valid IP OK, invalid IP (login module returns false) blank page :o(
    b) As an alternatice, in my opinion, it would be best to use the standard SAP class in the portalapp.xml  (com.sap.sapportals.portal.ume.component.logon.SAPMLogonComponent) & have some sort of servlet in front
    The behaviour of which page to return in case of failed logon is contained in com.sap.portal.runtime.logon_api.jar, class com.sap.sapportals.portal.ume.component.logon.SAPMLogonComponent -> class SAPMLogonLogic).
    How can this be done? I've already cracked my head over it, but can't get this to work -
    My coding for a) :
    package z.x.sapportals.portal.ume.component.logon;
    import com.sap.security.api.logon.ILogonFrontend;
    import com.sapportals.portal.prt.component.AbstractPortalComponent;
    import com.sapportals.portal.prt.component.IPortalComponentRequest;
    import com.sapportals.portal.prt.component.IPortalComponentResponse;
    import com.sapportals.portal.prt.session.IUserContext;
    public class xSAPMLogonComponent extends AbstractPortalComponent     implements ILogonFrontend
         protected void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
              response.write("\n<!-- component context:" + request.getComponentContext().getComponentName() + "-->\n");
              response.write("<!-- class: " + getClass().getName() + "-->\n");
              String firstName ="";
              String lastName = "";
              String logonUid = "";
              String password = "";
              String authscheme = "";
              IUserContext userContext = request.getUser();
              if (userContext != null)
                   firstName = userContext.getFirstName();
                   lastName = userContext.getLastName();
                   logonUid = userContext.getLogonUid();
                   password = "dummy";
                   authscheme = (String)request.getValue("com.sap.security.logon.authscheme.required");
                   response.write("Welcome :");
                   response.write("logonUid = " + logonUid + "<br><br>");
                   response.write("j_password = " + password + "<br><br>");
                   response.write("<form id=\"redirform\" method=\"post\" >");
                   response.write("<input type=\"hidden\" name=\"login_submit\" value=\"on\">");
                   response.write("<input type=\"hidden\" name=\"j_user\" value=\"" + logonUid + "\">");
                   response.write("<input type=\"hidden\" name=\"j_password\" value=\"" + password + "\">");
                   response.write("<input type=\"hidden\" name=\"j_authscheme\" value=\"" + authscheme + "\">");
                   response.write("<input type=\"submit\" value=\"send\">");
                   response.write("</form>");
    //                      Commented out javascript auto submit to press submit manually for testing
         /* (non-Javadoc)
    @see com.sap.security.api.logon.ILogonFrontend#getTarget()
         public Object getTarget()
              // TODO Auto-generated method stub
              return this;
         /* (non-Javadoc)
    @see com.sap.security.api.logon.ILogonFrontend#getType()
         public int getType() {
              // TODO Auto-generated method stub
              return 2;
    Portalapp.xml :
        <component name="iplogon">
          <component-config>
            <property name="ClassName" value="z.x.sapportals.portal.ume.component.logon.xSAPMLogonComponent"/>
            <property name="SafetyLevel" value="no_safety"/>
            <property name="LocalModeAllowed" value="true"/>
          </component-config>
          <component-profile>
            <property name="AuthScheme" value="anonymous"/>
            <property name="com.sap.portal.pcm.Category" value="platform">
              <property name="inheritance" value="final"/>
            </property>
            <property name="SupportedUserAgents" value="(MSIE, >=5.0, *) (Netscape, *, ) (Mozilla,,*)">
              <property name="inheritance" value="final"/>
            </property>
          </component-profile>
        </component>
    authschemes.xml
            <authscheme name="iplogon">
                <authentication-template>
                    radiusExtended
                </authentication-template>
                <priority>22</priority>
                <frontendtype>2</frontendtype>
                <frontendtarget>z.x.portal.runtime.logon.iplogon</frontendtarget>
            </authscheme>

    Hi,
    I'm not sure if you have already solved this issue, I was looking up another issue and came across this topic, maybe I can close this topic for you.....
    Here is what you could do...
    1) Create a custom login module stack with your login module
    2) Create a authentication scheme that refers this stack
      For example, you have defined a login module stack called certlogon in the Security Provider service in the Visual Administrator. You   want to create an authentication scheme that uses this login module stack. To do this, you add the following excerpt to the authschemes.xmlfile.
    <authscheme name="myauthscheme">
          <!-- multiple login modules can be defined -->
          <authentication-template>
            certlogon
          </authentication-template>
          <priority>20</priority>
          <!-- the frontendtype TARGET_FORWARD = 0 -->
          <!-- TARGET_REDIRECT = 1, TARGET_JAVAIVIEW = 2 -->
          <frontendtype>2</frontendtype>
          <!-- target object -->
          <frontendtarget>
            com.mycompany.certlogonapp
          </frontendtarget>
      </authscheme>
    In this schema refer your custom login application.
    thanks,
    Sudhir

  • Custom login module Authentication works but Authorization Does not work

    Hi:
    I am using custom login module and switched on the ADF authentication using adf-config.xml file. My custom authentication works i.e. it returns true but when it finally tries to display the page 401 Unauthorized message is shown. I am using JDev 10.1.3.2.
    Is there any other settings I need to perform. Could you please let me know.
    Thanks

    I have the same issue, please refer to this thread.
    Re: ADF Security Authorization

  • 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.

  • Web Proxy Authentication using Kerberos or NTLM - ForeFront TMG

    Hi All
    I was hoping someone would be able to guide me on addressing an issue I have with authenticating MACs against the web proxy. I have scoured the internet and looked on the forums but I can't seem to find a solution to the problem I am experiencing.
    Our network consists and an AD domain, and a single TMG server 2010. The TMG server is enabled for integrated authentication for the Web Proxy. All the MACs have been added to the AD Domain, so all users logon as themselves. Authentication to various shares
    are granted using Kerberos - so part of the Kerberos infrastructure works.
    My Problem:
    Currently, my MAC clients are prompted for a username and password when accessing the internet within Firefox and Camino. If I use Safari I have my credentials twice as the keychains saves my credentials seperately, for HTTP and HTTPS traffic.
    Ideal Solution
    Since a kerberos ticket is issued to the user who has logged in by the domain controller, I would like to use kerberos to authenicate the user for web access.
    What I've done so far
    There is a feature within Firefox and Camino web browsers to enable trusted websites to use your kerberos ticket. If you open Mozilla, navigate to about:config and look for 'network.negotiate-auth.trusted-uris' and add various internal sites (not proxy).
    The authentication works perfectly using Kerberos as you can see the tickets that have been handed out using 'klist' and I'm not prompted for my username or password. If I disable it, it stops working and I am prompted for my username and password. I have
    tried typing in the proxy address, also tried putting in the proxy port too but to no success within the trusted-uris text field.  Maybe there is a different way of putting in the address?
    I have enabled Kerberos on the computer account in AD for the firewall (Trust this computer for delegation to any service (kerberos only)), but without any success. I must admit, I haven't rebooted the TMG server though.
    I hope someone can help me out, and really appreciate your time and support.
    Thanks
    Jamie

    Hi All
    I have resolved my issue. I added the SPN of HTTP/SERVERNAME & HTTP/IPADDRESSOFSERVER to the firewall computer account and replicated my changes and now I have authenication working on my MACS without any username and password prompts, apart
    from the user logging into the domain. Beautiful.
    https://community.mcafee.com/docs/DOC-2682 - This detailed article from McAfee helped me signfictantly.
    Cheers Anyway,
    Jamie

  • Error using 10.1.3 Security Provider:3rd party LDAP or Custom Login Module

    Hello all,
    After deploying my JSF/ADF application using Jdeveloper 10.1.3 to Oracle Application Server 10.1.3, I used the Application Server control to change the 'Security Provider' configuration:
    1. Using 3rd Party LDAP Provider (Novell eDirectory)
    I get the following error when restarting the application with the new config.
    06/06/21 16:42:32 Error while configuring security provider MBean for application AccessList
    06/06/21 16:42:32 java.lang.ClassNotFoundException: oracle/security/jazn/jmx/CustomLDAPSecurityProvider
    2. Using Custom Login Module (again programmatically talks to eDirectory and it works in UIX/10.1.2 application)
    I get the following error when restarting the application with the new config.
    06/06/21 14:31:19 Error while configuring security provider MBean for application AccessList
    06/06/21 14:31:19 java.lang.ClassNotFoundException: oracle/security/jazn/jmx/LoginModuleSecurityProviderAlso, I get this error with both the settings..
    06/06/21 14:31:19 WARNING: Application.setConfig Application: AccessList is in failed state as initialization failedjava.lang.
    InstantiationException
    Jun 21, 2006 2:31:19 PM com.evermind.server.Application setConfig
    WARNING: Application: AccessList is in failed state as initialization failedjava.lang.InstantiationException
    06/06/21 14:31:19 java.lang.InstantiationException
    06/06/21 14:31:19       at com.evermind.server.ApplicationStateRunning.initDataSources(ApplicationStateRunning.java:1424)
    06/06/21 14:31:19       at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:195)
    java.lang.ClassNotFoundException error leads me to believe, I am just missing to include some libraries..
    I have included "bc4j.security" in my web project and I am not sure if that is what is needed!
    Will appreciate your help..
    Thanks,
    Karthik

    The problem i had with my Custom login module was that JDeveloper includes the datasources listed in the connection tab.
    When JDeveloper does that it writes the username and password in the jazn-data.xml. But with the Custom Login module the reference in de data-source declaration cannot find the password. that's why i got the InstantiationException at the initDataSources point.
    In tools>preferences>deployment you can uncheck the option:
    Bundle Default data-sources.xml During Deployment.
    The problem with this is when i specify a datasource in the data-sources.xml i included myself, jdeveloper will also put de datasources under the Connections tab in the data-sources.xml.
    Does anyone knows how to stop jdeveloper putting the datasources automatic in the file, or how to prevent jdeveloper storing the password in jazn-data.xml?

  • JAAS login module configuration in Oracle application server

    I have a LDAP login module implementing javax.security.auth.spi.LoginModule. This login module works well with tomcat and weblogic, if I configure the JVM arguments -Djava.security.auth.login.config and -Djava.security.policy to pont to the login.conf and access.policy files. The login.conf file has the below content
    FREEWAY_SERV
    com.wipro.freeway.security.LdapLoginModule required debug=true portal=false;
    FREEWAY_PORT
    com.wipro.freeway.security.LdapLoginModule required debug=true portal=true;
    The application uses these login modules by passing Name of the JAAS configuration (FREEWAY_SERV or FREEWAY_PORT).
    I would like to use the same login modules and code in Oracle application sever 10.1.3 and I haven't got any success yet.
    Could anybody please help me to get this right?
    Thanks in advance.
    Message was edited by:
    vinayalva

    Hi,
    in OracleAs bet is to use Enterprise Manager to configure the login module. The LoginModule needs to be configured in the system-jazn-data.xml file, which is located in teh j2ee/home/config directory of the OC4J you use. Enterprise Manager does this all for you.
    In your application deployment the orion-application.xml file needs to specify that a custom LoginModule should be used. Again ENterprise Manager does it for you.
    To use the LoginModule e.d. for J2EE authentication, just make sure that the application name of the J2EE deployment matches the name of the LoginModule configuration
    If you want to use pure JAAS you may have to change the OC4J properties file in the j2ee/home/config directory. Best suggestion to give is to get the online documentation for OC4J security
    Frank

  • J2EE 6.40 Custom Login Module - how to config

    hello all,
    i am using WAS J2EE 6.40 Sneak Preview edition. Read all i can find about custom login module, in the forum and the online help. still confused. pls help.
    here is the background info:
    - i am writing a web app. the EAR file contains 5 ejbs, 1 war and bunch of java classes in jars.
    - access to my web app is protected through url pattern (in web.xml), i've defined the same named security role in web.xml and on j2ee engine.
    - my login module does the user name and password checking. both are stored in database through some other means.
    - login is FORM based
    following the discussion in another thread on the topic, i did the following:
    #1 develop my login module code. packaged it in a jar, then sda file. deploy the sda as a llibrary to the engine.
    #2 add my login module to the security store through the security provider service.
    #3 configure my web app to use the custom login module in web-j2ee-engine.xml
    #4 deploy my web app through the ear file
    at this point, in the visual administrator, i can see the library, the custom login module (added to the UME User Store), and also my web app has authentication set to use the custom login module (under policy configurations tab).
    now i try to login to my web app. it correctly complains when i enter non-existent user or wrong password and brings me to the login failed jsp page. but when i enter both correctly (as stored in my database), i get http 403 error code. i know it is 403 because i set that error code to a special jsp page in web.xml.
    question is why? now i create a user on the j2ee engine with the same name as in my user database. then i can login ok. i am confident that my login module is called since i see the println lines in j2ee engine server logs.
    ??? so i must be missing something obvious. is it because my web app is protected through security-role? i even tried removing all such roles, but still same problem.
    ??? or do i completely mis-understand how custom login modules are supposed to work. i thought it means i can authenticate users any way i want without having to use the j2ee engine's user mgmt. pls tell me if i am totally wrong.
    ??? or maybe my login module code is missing some key stmts. how should it tell the j2ee engine that a user is authenticated? in the login() method, it returns true if user name/passwd match. in the commit() method, it adds the principal to the subject. i don't what else is required.
    does anyone have a working scenario using custom login modules?
    thanks very much for your inputs and thoughts.
    wentao

    Hi Astrid,
    I guess I have the same understanding of JAAS as you. I want to deploy an application that internally makes use of JAAS to authenticate users. There is a LoginModule that authenticates users against some database tables containing all the user data and profile. The application was not designed to be deployed to NetWeaver. So it does not make use of UME or some other NetWeaver specific feature. Actually it handles user management and authoroization issues completely on its own. The only reason for having JAAS is to allow customers to plug in their own LoginModule to use some other kind of user store.
    When deploying the web application to a simple servlet engine like Tomcat, all I have to do is to register my LoginModule in the "jaas.conf" file that is parsed by JAAS default implementation. I also tell the JVM where my jaas.conf file is located by appending a "-Djava..." runtime parameter to the JVM startup script.
    When using other application servers like IBM WebSphere things become a bit different. Normally you use the administration GUI of that server to configure your LoginModules. WebSphere for example keeps the login configuration in an internal database rather than writing everything into a "jaas.conf" text file. But the way the application can use the LoginModule is the same as in Tomcat.
    But when it comes to Netweaver, it seems to me that it's not possible to define a LoginModule that your application can use WITHOUT having to couple it tightly to UME. Or did I get something wrong? Initially I've tried to modify the JVM's parameters (using SAP J2EE Config Tool) to include the location of my "jaas.conf" file containing the my login configuration. But that did not work. The parameter was really passed to the JVM but anyway my LoginModule was not found, I guess that NetWeaver has some own implementation of the JAAS interfaces that just ignore the plain text JAAS configuration files (like WebSphere also does).
    The documentation that I have downloaded from SDN doesn't seem to match the 6.4 sneak preview version that I just downloaded some days ago. They say you should deploy your LoginModule as a library and add a refernce to the application. I tried that out but it did not help. The login configuration that the application wants to access is still not found. Actually there seems to be no way to specify the name for a JAAS Login Configuration in NetWeaver. At least I cound not find that in the documentation.
    So basically my question is: is it possible to deploy an application that wants to use some own LoginModule (either deployed separately or together with the application, that does not matter) without making use of Netweaver specific features like UME? The application has its own user management infrastructure and just needs a way to setup a JAAS Login Configuration to access its own LoginModule.
    Thanks in advance
    Henning

  • HttpServletRequest in JAAS-Login Module in NetWeaver 7.3x

    I've developed for a company severall login modules where I use the com.sap.security.api.logon.WebCallback class to get the HttpServletRequest
    object.
    In NW 7.3x this class is now deprecated and is not working anymore.
    Is there any successor class or any other possibility to get the HttpServletRequest in the jaas-context?
    Best regards
    Thomas

    Hi,
    We had the same problem.
    What we found was that Sap has a new Login Module called HeaderVariableLoginModule which you have to create using the class com.sap.security.core.server.jaas.HeaderVariableLoginModule. You can do this in NWA -> Configuration -> Authentication and Single Sign-On -> Login Module, then click on the create button and fill out the fields with the information i just gave you.
    The list of Login Modules should now include HeaderVariableLoginModule, which you can configure by selecting the row of this module, and adding two options-  ume.configuration.active=true and Header=REMOTE_USER.
    It appears that this Login Module is covertly delivered as a class in every Netweaver version >= 7.0.
    Good luck,
    Steven McElwee, Duke University
    PS- I tried to attach a word document that shows the procedure for this, but this system rejected it. I can email it you if you let me know where to send it. In our case we used "Header=uid" rather than "Header="REMOTE_USER".

  • 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 &#8594; 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

Maybe you are looking for

  • Moving and Arranging Objects?

    I want to create a Flash animation in which a user has a bunch of objects in front of them (say, four apples, five oranges and three plums) and three containers. They can drag the objects and put them in any of the three containers. How would I go ab

  • Damaged image files in gallery of 311 - 5.92

    hi, when tapping accidentally on a picture in the gallery while it is still scrolling, there is a great chance (in my case 100%; I have been able to reproduce it) that this picture file will be damaged, leaving only about some lines of pixels visible

  • Unable to access the following endpoint(s)

    Hi All,     Here i man unable to invoke the siebel services when i try to access the end point i receving this error and also i added oracle/no_authentication_client_policy also still it's problam please any help on this Non Recoverable System Fault

  • Singleton & EJB & Clustering

    Hello: although I have read information about this question in http://java.sun.com/developer/technicalArticles/Programming/singletons/ , I continue having doubts. I need a class (A) called by stateless session beans to get next value from one previou

  • Spotlight is trying to use wrong importer for numbers documents?

    For a while now I've been unable to find numbers documents via spotlight, and today I tried to reindex one of them just to try and get a handle on the problem and this is what happened... $ mdimport /Users/camden/Documents/spreadsheet.numbers (Error)