Logout failure by AuthContext

Hi All,
I have setup a J2EE agent and IdServer successfully. I would like to write a logout jsp/servlet at agent side server. I try to use AuthContext where logout method is offered. Here is the code:
AuthContext lc = new AuthContext(token);
lc.logout();
But logout didn't succeed and there is error message in amAuth debug log at IdServer side.
05/11/2004 02:53:30:363 PM HKT: Thread[Thread-83,5,main]
failureModuleSet is : [LDAP]
05/11/2004 02:53:30:370 PM HKT: Thread[Thread-83,5,main]
LOGINFAILED Error....
05/11/2004 02:53:30:371 PM HKT: Thread[Thread-83,5,main]
Exception
com.sun.identity.authentication.spi.AuthLoginException(1):null
java.io.IOException(2):110
java.io.IOException: 110
at com.sun.identity.authentication.service.DSAMECallbackHandler.handle(DSAMECallbackHandler.java:114)
at javax.security.auth.login.LoginContext$5.run(LoginContext.java:812)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:808)
at com.sun.identity.authentication.spi.AMLoginModule.login(AMLoginModule.java:766)
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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
at com.sun.identity.authentication.service.AMLoginContext.run(AMLoginContext.java:284)
05/11/2004 02:53:30:375 PM HKT: Thread[Thread-83,5,main]
Came to before if Failed loop
Does anyone have this experience before? Any help will be appreciated.

1. You wrote: "Thanks Dr. Smoke for responding. So if I set Mail to check after the log out limits, then it should resolve this?"If Mail's checking was the cause, then yes. For example, setting Mail to check once every two hours, but log out after 45 minutes of inactivity.
2. You wrote: "On second thought, no programs are open, generally, when I leave."You'd want to be certain about that.
However, assuming you've closed all your usual applications and documents, then one would have to consider background processes. If you close all open applications, but then launch Activity Monitor, you'll see that your Mac has a slew of background processes that are always running.
Some of these faceless, background processes may be invoked as third-party Startup or Login Items you've installed. My "Troubleshooting Startup and Login Items" FAQ can help you pin that down if such an item is causing the problem.
It could also be something with your Internet connection. Consider "Mac OS X: Dial-up connection (PPP) fails to automatically disconnect." You might want to consult with your networking group (I'm presuming this is a work computer) to see if some network polling might be involved.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Similar Messages

  • Failed to getSSOToken after second connection in one JVM

    I met a problem when connected to two hosts to getSSOToken. I can get the SSO token in the first connection but failed in the second connection. And during the second connection, login succeeded, but failed to getSSOToken from AuthContext. The code is:
    import com.iplanet.am.util.SystemProperties;
    import com.iplanet.sso.SSOToken;
    import com.sun.identity.authentication.AuthContext;
    import com.sun.identity.authentication.spi.AuthLoginException;
    import javax.net.ssl.*;
    import javax.security.auth.callback.Callback;
    import javax.security.auth.callback.NameCallback;
    import javax.security.auth.callback.PasswordCallback;
    import java.io.File;
    import java.io.FileOutputStream;
    import java.io.IOException;
    import java.security.KeyStore;
    import java.security.SecureRandom;
    import java.security.cert.CertificateException;
    import java.security.cert.X509Certificate;
    public class AuthSession {
    public static void main(String[] args) throws Exception {
    AuthSession session1 = new AuthSession();
    session1.login("IP1", "login1", "pass1");
    String cookie1 = session1.getCookieId();
    System.out.println("Cookie: " + cookie1);
    session1.logout();
    AuthSession session2 = new AuthSession();
    session2.login("IP2", "login2", "pass2");
    String cookie2 = session2.getCookieId();
    System.out.println("Cookie: " + cookie2);
    session2.logout();
    private AuthContext authContext = null;
    private SSOToken ssoToken = null;
    private static final String NGSSO_SEC_LOGIN_MODULE = "NgssoSecLoginModule";
    private static final int PORT = 58082;
    private static final String COOKIE_NAME = "iPlanetDirectoryPro";
    public void login(String host, String user, String pwd) throws Exception {
    this.authContext = getAuthContext(host, user, pwd);
    public void logout() {
    try {
    if (authContext != null) {
    authContext.logout();
    authContext.reset();
    authContext = null;
    } catch (AuthLoginException e) {
    throw new RuntimeException(e);
    public String getCookieName() {
    return COOKIE_NAME;
    public String getCookieId() throws Exception {
    return getSSOToken().getTokenID().toString();
    private SSOToken getSSOToken() throws Exception {
    if (authContext != null) {
    if (ssoToken == null) {
    ssoToken = authContext.getSSOToken();
    return ssoToken;
    return null;
    private static AuthContext getAuthContext(String hostname, String login, String password) throws Exception {
    String url = "https://" + hostname + ":" + PORT + "/amserver/namingservice";
    initProperties(password, url, hostname);
    AuthContext localAuthContext = new AuthContext("/");
    localAuthContext.login(AuthContext.IndexType.MODULE_INSTANCE, NGSSO_SEC_LOGIN_MODULE);
    Callback[] callbacks = localAuthContext.getRequirements();
    while (callbacks != null) {
    NameCallback nameCallBack = null;
    PasswordCallback passwordCallback = null;
    for (Callback callback : callbacks) {
    if (callback instanceof NameCallback) {
    nameCallBack = (NameCallback) callback;
    if (callback instanceof PasswordCallback) {
    passwordCallback = (PasswordCallback) callback;
    if (nameCallBack != null && passwordCallback != null) {
    nameCallBack.setName(login);
    passwordCallback.setPassword(password.toCharArray());
    } else {
    throw new Exception("connection failed on '" + hostname + "'");
    localAuthContext.submitRequirements(callbacks);
    callbacks = localAuthContext.getRequirements();
    if (localAuthContext.getStatus() != AuthContext.Status.SUCCESS) {
    throw new Exception("bad login/pwd on '" + hostname + "'");
    return localAuthContext;
    private static String getKeyStore(String password) throws Exception {
    File keyStore = File.createTempFile("wskeys_", ".keystore");
    keyStore.deleteOnExit();
    String keyStoreFileName = keyStore.getAbsolutePath().replaceAll("\\\\", "/");
    PrivateTrustManager trustManager = new PrivateTrustManager(keyStoreFileName, password);
    SSLContext context = SSLContext.getInstance("SSL");
    context.init(null, new TrustManager[]{trustManager}, new SecureRandom());
    HttpsURLConnection.setDefaultSSLSocketFactory(context.getSocketFactory());
    return keyStoreFileName;
    private static void initProperties(String password, String url, final String hostname) throws Exception {
    String keyFileName = getKeyStore(password);
    HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier() {
    public boolean verify(String urlHostName, javax.net.ssl.SSLSession session) {
    return true;
    System.setProperty("javax.net.ssl.trustStore", keyFileName);
    System.setProperty("javax.net.ssl.trustStorePassword", password);
    SystemProperties.initializeProperties("com.iplanet.am.naming.url", url);
    SystemProperties.initializeProperties("com.iplanet.services.debug.level", "error");
    SystemProperties.initializeProperties("com.iplanet.services.debug.directory","D:\\tmp");
    System.setProperty("com.iplanet.am.naming.url", url);
    System.setProperty("com.sun.identity.agents.app.username", "administrator");
    System.setProperty("com.iplanet.am.service.password", password);
    System.setProperty("com.iplanet.am.naming.failover.url","");
    System.setProperty("com.iplanet.services.debug.level","error");
    System.setProperty("com.sun.identity.agents.notification.enabled","false");
    System.setProperty("com.iplanet.am.server.protocol", "https");
    System.setProperty("com.iplanet.am.server.host", hostname);
    System.setProperty("com.iplanet.am.server.port", String.valueOf(PORT));
    System.getProperty("com.iplanet.am.serverMode");
    private static class PrivateTrustManager implements X509TrustManager {
    private String keyStoreName;
    private String password;
    public PrivateTrustManager(String keyStoreName, String password) {
    this.keyStoreName = keyStoreName;
    this.password = password;
    public void checkClientTrusted(X509Certificate[] chains, String authType) {
    public void checkServerTrusted(X509Certificate[] chains, String authType)
    throws CertificateException {
    FileOutputStream keyStoreOutputStream = null;
    try {
    KeyStore keyStore = KeyStore.getInstance("JKS", "SUN");
    char[] storePassword = password.toCharArray();
    keyStore.load(null, storePassword);
    for (X509Certificate oneChain : chains) {
    keyStore.setCertificateEntry("wskey", oneChain);
    keyStoreOutputStream = new FileOutputStream(keyStoreName);
    keyStore.store(keyStoreOutputStream, storePassword);
    } catch (Exception e) {
    throw new CertificateException(e);
    finally {
    try {
    if (keyStoreOutputStream != null) {
    keyStoreOutputStream.close();
    } catch (IOException e) {
    e.printStackTrace();
    public X509Certificate[] getAcceptedIssuers() {
    return new X509Certificate[0];
    Does anyone have idea? Thanks a lot!

    And when the java code is executed, below exception is thrown:
    com.iplanet.sso.SSOException: AQIC5wM2LY4SfcwNBIUIhyedKiqTZSd+vcrG5/PD5Pir+lc=@AAJTSQACMDE=# Invalid session ID.AQIC5wM2LY4SfcwNBIUIhyedKiqTZSd+vcrG5/PD5Pir+lc=@AAJTSQACMDE=#
         at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:178)
         at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:305)
         at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1071)
         at AuthSession.getSSOToken(AuthSession.java:77)
         at AuthSession.getCookieId(AuthSession.java:70)
         at AuthSession.main(AuthSession.java:36)
    Exception in thread "main" com.sun.identity.common.L10NMessageImpl: Error occurred while creating SSOToken.
         at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1074)
         at AuthSession.getSSOToken(AuthSession.java:77)
         at AuthSession.getCookieId(AuthSession.java:70)
         at AuthSession.main(AuthSession.java:36)
    It's strange that it can be succeeded to invoke authContext.getAuthIdentifier(), while failed to getSSOToken().getTokenID().toString().

  • UCCX 10.5 CAD agent cannot log out

    UCCX version 10.5.1.10000-24
    CAD agent can log in, go ready/not ready just fine.  But when agent hits the logout button, it fails. 
    CAD logs shows logout failure as below.  Trying to figure out why agent can't log out and how to fix it. 
    2015-01-08 16:37:42:747 DEBUG [0x2fdc] Configuration.cpp[978] GetLocalConfigPath: CC0978                Local Path: C:\Program Files (x86)\Cisco\Desktop\
    2015-01-08 16:37:42:747 DEBUG [0x2fdc] MainFrm.cpp[1265] CMainFrame::ACDLoginLogout: MF1265 User clicked ACD LOGIN/LOGOUT button
    2015-01-08 16:37:42:748 DEBUG [0x2fdc] MainFrm.cpp[1390] CMainFrame::ACDLoginLogout: MF1390 User clicked ACD LOGOUT button
    2015-01-08 16:37:42:748 DEBUG [0x2fdc] AgentStateManager.cpp[1125] CAgentStateManager::SetReasonCode: Begin.
    2015-01-08 16:37:42:748 DEBUG [0x2fdc] AgentStateManager.cpp[1125] CAgentStateManager::SetReasonCode: End.
    2015-01-08 16:37:42:748 DEBUG [0x2fdc] AgentStateManager.cpp[155] CAgentStateManager::HandleRequest: Begin handling agent state change request. Use <PromptedReasonCode=0> to SetAgentState.
    2015-01-08 16:37:42:748 DEBUG [0x2fdc] CJToolbars.cpp[679] CCJMainToolBars::CheckButton: set check for <Login> to true
    2015-01-08 16:37:42:748 DEBUG [0x2fdc] PhoneDev.cpp[506] SetAgentState: Begin. Set Agent State AS_LOGOUT       , Invoked ID 9, AgentID joeb, DeviceID 7004, PeripheralID 1, reasonCode 0, ForcedFlag 0
    2015-01-08 16:37:42:750 DEBUG [0x2fdc] PhoneDev.cpp[586] SetAgentState: Set Agent state to AS_LOGOUT         NOT successful
    2015-01-08 16:37:42:750 DEBUG [0x2fdc] PhoneDev.cpp[506] SetAgentState: End.
    2015-01-08 16:37:42:750 DEBUG [0x2fdc] AgentStateManager.cpp[200] CAgentStateManager::HandleRequest: ASM0200  The agent state change succeeded
    2015-01-08 16:37:42:750 DEBUG [0x2fdc] CJToolbars.cpp[679] CCJMainToolBars::CheckButton: set check for <Login> to false
    2015-01-08 16:37:42:750 DEBUG [0x2fdc] AgentStateManager.cpp[260] CAgentStateManager::HandleRequest: ASM0260 End handling agent state change request

    Certainly something to try, but I don't see why that would make a difference in an inability to log out.  I have many customers who only use the default workflow and haven't seen any of them with this issue previously.
    Are you guessing here, or have you actually seen that resolve similar problems?

  • RFID tag detection failure on Logout and Login to MI Client

    Hi,
    We have implemented RFID in our MAM3.0 ; application. Every thing is working fine after login to client and could read the data from the tag. But once logout from the client (by clicking on logout from MI client) and login again, I am unable to read the data from the RFID tag. Seems that it is not connecting to the RFID reader. I am getting CAF exception and RFID read exception.
    I am using MI2.5 SP 21 Client
    Below is the trace of the exception
    RFID READ ERROR: RFID tag detection failure
    [20090205 15:06:07:058] E [Unknown                  ] com.sap.mbs.mam.rfid.exception.RFIDTagAccessException: RFID tag detection failure
    com.sap.mbs.mam.rfid.exception.RFIDTagAccessException: RFID tag detection failure
    at com.sap.mbs.mam.rfid.util.impl.ZRFIDTagHandlerImpl.executeRFIDTagRead()
    at com.sap.mbs.mam.notification.control.ZNotificationEdit.onRFIDInsert()
    at com.sap.mbs.core.control.AbstractViewController.process()
    at com.sap.mbs.core.control.DefaultStateMachine.process()
    at com.sap.mbs.core.web.FrontServlet.doHandleEvent()
    at com.sap.mbs.mam.application.web.FrontServlet.doHandleEvent()
    at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe()
    After restarting the device, I am able to read the data from RFID tag. Did anyone encounter this kind of error for this particular scenario. Please advise how to resolve this issue.
    Thanks in Advance,
    Chinna.

    Hi,
    please refer this link
    RFID tag reading failed - MI 7.0, MAM 3.0
    Regards
    Manohar

  • GDM failure on logout

    When I try to log out or switch user I see only the console and can log in and out to both my users. Nothing crashes.
    This didn't help https://wiki.archlinux.org/index.php/GD … _on_logout
    What I did from the very beginning:
    1. At Arch installation I've created a user hg1 in group hg1
    2. Recently assigned hg1 to users and made users the primary group for the user hg1
    3. Removed the group named hg1
    4. Created a new user using
    useradd -m -g users -s /bin/bash agg
    and asigned a passwd for it.
    5. While reviewing the /etc/group I saw the user hg1 is no longer in the wheel group but I did nothing about that.
    6. Tried logging out and switching between users for the very first time on that system.
    # cat /etc/group
    root:x:0:root
    bin:x:1:root,bin,daemon
    daemon:x:2:root,bin,daemon
    sys:x:3:root,bin
    adm:x:4:root,daemon
    tty:x:5:
    disk:x:6:root
    lp:x:7:daemon
    mem:x:8:
    kmem:x:9:
    wheel:x:10:root
    ftp:x:11:
    mail:x:12:
    uucp:x:14:
    log:x:19:root
    utmp:x:20:
    locate:x:21:
    rfkill:x:24:
    smmsp:x:25:
    http:x:33:
    games:x:50:
    lock:x:54:
    uuidd:x:68:
    dbus:x:81:
    network:x:90:
    video:x:91:
    audio:x:92:
    optical:x:93:
    floppy:x:94:
    storage:x:95:
    scanner:x:96:
    input:x:97:
    power:x:98:
    nobody:x:99:
    users:x:100:hg1
    systemd-journal:x:190:
    systemd-journal-gateway:x:191:
    systemd-timesync:x:192:
    systemd-network:x:193:
    systemd-bus-proxy:x:194:
    systemd-resolve:x:195:
    systemd-journal-remote:x:999:
    systemd-journal-upload:x:998:
    avahi:x:84:
    polkitd:x:102:
    colord:x:124:
    rtkit:x:133:
    gdm:x:120:
    git:x:997:
    brlapi:x:996:
    proc:x:26:

    It seems like a Mutter or GDM bug. After installation and creation of hg1 I've set it to autologin using Gnome GUI. Then:
    - I created the user agg
    - tested logging out / user switching functionality and saw the bug
    - in the Gnome GUI I've disabled the autologin setting
    - now logging out and switching works but with Mutter crashing and quickly restarting each time
    I'll wait a few weeks, post a bug report and post my findings here.

  • Runtime failure in custom tag

              I was curious if you knew what specifically you did to remove the runtime error.
              I am also getting the runtime failure. The try/catch that another discussion thread
              suggested does not catch the error since the exception is thrown prior to the
              doStart and doEnd Tag methods. I know that the exception is thrown immediately
              after the constructor is called for the tag and before the setParent method is
              called.
              Anyway, thank you in advance for any suggestions you might have.
              try { // begin instantiate/release try/catch/finally block... //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
                   westerncommon_jsptag_HeaderTag_0 = (western.common.jsptag.HeaderTag)java.beans.Beans.instantiate(getClass().getClassLoader(),
              "western.common.jsptag.HeaderTag"); //[ /wattage/wtgMainMenu.jsp; Line: 36]
              westerncommon_jsptag_HeaderTag_0.setPageContext(pageContext); //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
              westerncommon_jsptag_HeaderTag_0.setParent(null); //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
                   westerncommon_jsptag_HeaderTag_0.setNavMenuHREF(weblogic.utils.StringUtils.valueOf("wtgLogout.jsp"));
              //[ /wattage/wtgMainMenu.jsp; Line: 36]
              westerncommon_jsptag_HeaderTag_0.setNavMenu(weblogic.utils.StringUtils.valueOf("Logout"));
              //[ /wattage/wtgMainMenu.jsp; Line: 36]
              westerncommon_jsptag_HeaderTag_0.setTitle(weblogic.utils.StringUtils.valueOf("Main
              Menu")); //[ /wattage/wtgMainMenu.jsp; Line: 36]
              int int0 = westerncommon_jsptag_HeaderTag_0.doStartTag(); //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
                   if (_int_0 == BodyTag.EVAL_BODY_TAG) { //[ /wattage/wtgMainMenu.jsp; Line: 36]
                        throw new JspTagException("Since tag class western.common.jsptag.HeaderTag does
              not implements BodyTag, it cannot return BodyTag.EVAL_BODY_TAG"); //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
              } //[ /wattage/wtgMainMenu.jsp; Line: 36]
              /*** sync AT_BEGIN TagExtra Vars here ***/ //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
              if (_int_0 != Tag.SKIP_BODY) { // begin !SKIP_BODY... //[ /wattage/wtgMainMenu.jsp;
              Line: 36]
                        //[ /wattage/wtgMainMenu.jsp; Line: 36]
                        out.print("\r\n");
                             //[ /wattage/wtgMainMenu.jsp; Line: 37]
                   } // end !SKIP_BODY //[ /wattage/wtgMainMenu.jsp; Line: 37]
              if (_western_common_jsptag_HeaderTag_0.doEndTag() == Tag.SKIP_PAGE) return;
              //[ /wattage/wtgMainMenu.jsp; Line: 37]
              } catch (java.lang.Exception javalang_Exception_0) { // instantiate/release
              try/catch/finally //[ /wattage/wtgMainMenu.jsp; Line: 37]
                   throw new ServletException("runtime failure in custom tag 'HeaderTag'", javalang_Exception_0);
              //[ /wattage/wtgMainMenu.jsp; Line: 37]
              } finally { // instantiate/release try/catch/finally block... //[ /wattage/wtgMainMenu.jsp;
              Line: 37]
                   if (_western_common_jsptag_HeaderTag_0 != null) westerncommon_jsptag_HeaderTag_0.release();
              //[ /wattage/wtgMainMenu.jsp; Line: 37]
              } //[ /wattage/wtgMainMenu.jsp; Line: 37]
              ----------CONSOLE OUTPUT-------------
              Getting Page permissions for page: wtgMainMenu.jsp user: 0
              Page Permissions: Insert-1 View-1 Update-1 Delete-1
              HeaderTag -- Constructing
              Thu Apr 05 11:19:00 CDT 2001:<E> <ServletContext-General> exception raised on
              wattage/wtgMainMenu.jsp'
              javax.servlet.ServletException: runtime failure in custom tag 'HeaderTag'
              at jsp_servlet.wattage.wtgmainmenu._jspService(wtgmainmenu.java:398)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:124)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:744)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:692)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              ContextManager.java:251)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              a:363)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

    I just started getting this error after a year in production environment without any problems. Did you every find out what caused this or better yet how to prevent this?
              Dan.
              

  • Java failure in Safari

    Today it started.
    I can't get any java based websites to run. No chats, no online games..nada.
    I do see the Java coffee cup with it's arrows.
    Went to Sun's website and tested, it shoed I had version 1.42 and 5.0 release1, but did not load the java image it stated I would see
    Is there a reset for Java?....some other indimidation factor?
    Any suggestions before I call Apple?

    Spent some time with AppleCare and resolved the Java problem.
    1) Test with a new user. Logout and make a new user. See if that helps.
    2) Go back to user w/ problem, pull Caches folder from Libray and put on desktop. Logout and log back in w/ same user. See if that helps.
    3) Rename Preferences to Preferences.old and logout and login w/ same user.
    If the problem persists, logout and login with the new user, pull the cache folder to desktop and rename Preferences folder w/ .old after the name
    4) Reboot in safe mode ( restart w/ Shift key held until you see the Grey Apple logo and the spinning gear under it. Release shift key and let it go. It will take a few minutes.
    5) Try a website with the java failure, like yahoo games or do a google for java pages and try one of those. If it works great. You can then start putting the old preferences, one at a time, back into the new preferences folder. Like the mail.plist, extrenal things.plists, and other stuff you installed after you got the computer or upgraded OSX.
    6) The cache folder can be deleted.
    7) Keep the old prefs around, its very small and may have something you'll need down the road, if something doesn't run right.
    This worked for me, as I cannot use any Java downloader from Apple. They will not install on the new Intel iMac.
    This reminded me of the OS9 method of testing extension one at a time, whih worked.
    As nothing is erased or lost this seems to be a very good method in finding software failures.
    Thanks Apple Care

  • How can I redirect logout page in PS 6.0?

    How or Where can I change http://<portalserver>/amserver/UI/Logout to http://<portalserver>/portal/dt in Portal Server 6.0?
    Thanks a lot for ideas.

    En el identity server -> Services -> Authentication Configuration se puede configurar urls para Login Success o Login Failure por ejemplo. Cuando un usuario hace logout el portal muestra el display profile del usuario authless/annonymous que esta en la organizacion por defecto. Lo que tendria que hacer es modificar ese display profile y hacer alli la redireccion.
    Puedo saber su nombre? seria bueno conocer a alguien en Colombia que maneje el JES.
    Saludos.
    Pedro Solorzano.

  • Disk Utility Failure?

    Hi all!
    Before I start, let me first say that I did search for my problem here before posting, however the results I found were not exactly under the same circumstances as my own.
    The long and short of it is this: I was running "Disk Utility" from my installation CD (I started up from the CD). While running "Disk Verify" and "Disk Repair," I received the following message just as the progress bar was complete:
    "Disk could not be repaired because Disk Utility failed on exit."
    According to the utility, it claimed my hard drive only needed "minor" repairs, and obviously my computer is still very usable (lol), but this still freaked me out a little bit.
    Is there something I can (or should) be doing to rectify this? My computer isn't horridly slow or buggy, so perhaps I should go on about my business--unless there is a fairly straightforward way of getting everything back to normal.
    Thanks ahead of time for your help!

    Hi Miriam!
    Well, I used Disk Utility to VERIFY my disk, and here's what I got:
    Verifying volume “Dexter”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Overlapped extent allocation (file 51706 /usr/share/man/man1/history.1)
    Overlapped extent allocation (file 51707 /usr/share/man/man1/hup.1)
    Overlapped extent allocation (file 51708 /usr/share/man/man1/if.1)
    Overlapped extent allocation (file 51709 /usr/share/man/man1/jobid.1)
    Overlapped extent allocation (file 51714 /usr/share/man/man1/limit.1)
    Overlapped extent allocation (file 51716 /usr/share/man/man1/log.1)
    Overlapped extent allocation (file 51718 /usr/share/man/man1/logout.1)
    Overlapped extent allocation (file 51719 /usr/share/man/man1/ls-F.1)
    51719 /usr/share/man/man1/ls-F.1
    ion (file %@)",1)
    51721 /usr/share/man/man1/notify.1
    Overlapped extent allocation (file 51722 /usr/share/man/man1/onintr.1)
    Overlapped extent allocation (file 51723 /usr/share/man/man1/popd.1)
    Overlapped extent allocation (file 51726 /usr/share/man/man1/pushd.1)
    Overlapped extent allocation (file 51728 /usr/share/man/man1/readonly.1)
    Overlapped extent allocation (file 51729 /usr/share/man/man1/rehash.1)
    Overlapped extent allocation (file Overlapped extent allocation (file 1730 /usr/share/man/man1/repeat.1)
    Overlapped extent allocation (file 51731 /usr/share/man/man1/sched.1)
    Overlapped extent allocation (file 51733 /usr/share/man/man1/set.1)
    Overlapped extent allocation (file 51734 /usr/share/man/man1/setenv.1)
    Overlapped extent allocation (file 51735 /usr/share/man/man1/settc.1)
    Overlapped extent allocation (file 51736 /usr/share/man/man1/setty.1)
    Overlapped extent allocation (file Overlapped extent allocation (file /setvar.1)
    Overlapped extent allocation (file 51738 /usr/share/man/man1/shift.1)
    Overlapped extent allocation (file 51740 /usr/share/man/man1/source.1)
    Overlapped extent allocation (file 51741 /usr/share/man/man1/stop.1)
    Overlapped extent allocation (file 51743 /usr/share/man/man1/suspend.1)
    Overlapped extent allocation (file 51744 /usr/share/man/man1/switch.1)
    Overlapped extent allocation (file 51746 /usr/share/man/man1/telltc.1)
    51746 /usr/share/man/man1/telltc.1
    pped extent allocation (file %@)",1)
    51747 /usr/share/man/man1/then.1
    Overlapped extent allocation (file 51749 /usr/share/man/man1/trap.1)
    Checking volume bitmap.
    Volume Bit Map needs minor repair
    Checking volume information.
    Volume Header needs minor repair
    .",1)
    Dexter
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    Hmmm so I'm getting the same error when I verify from my disk! So--you're saying my next step is TechToolPro or Disk Warrior? I just wish they weren't so pricey... I guess something like cocktail, etc isn't going to help something like this... lol
    Message was edited by: Doug Dellis

  • Hal start failure,relogin gdm,and cant see gnome desktop

    Hal start failure,relogin gdm,and cant see gnome desktop
    When system start ,I can see gdm. When you enter a user and name password to login the desktop, the screen flash, immediately logout from the desktop,Back to the login interface.
    manual start hal ,failure.
    Thanks.
    Last edited by wevol (2009-12-18 14:12:35)

    I had a similar issue with HAL on my netbook (Lenovo S10e) running arch i686 kernelversion 2.6.32. When typing as root
    $ /etc/rc.d/hal start
    it failed.
    I then killed the hald process via
    $ killall hald
    and now it starts fine.
    Don't know what caused the problem, has there been a hal update recently?

  • [OAM] Want to use custom System Error page and OOTB logout page simultaneously

    Hi,
    I have developed a custom OAM System Error screen (Error.jsp). To do that, I took oamcustompages.war from the installation directory, create Error.jsp and deploy it on oam_server1 server. After that, I run the updateCustomPages(extension="jsp", context="/oamcustompages") on wlst. This works fine.
    But now, if I invoke xxxx/oam/server/logout I have the following:
    <html><head><title>302 Moved Temporarily</title></head>
    <body bgcolor="#FFFFFF">
    <p>This document you requested has moved temporarily.</p>
    <p>It's now at <a href="http://lablnx246:8888/URLWeb/oamcustompages/pages/Logout.jsp">http://lablnx246:8888/URLWeb/oamcustompages/pages/Logout.jsp</a>.</p>
    </body></html>
    So.. it appears that all pages ootb have been replaced by the custom war. Is there any way to only let Error.jsp active and other pages be called OOTB?
    Thanks!

    The updateCustomPages will change the default OOTB behaviour
    If you do not want this, you can leverage the Success URL/Failure URL configuration in the Authentication policy and point it to the custom error handler

  • Forced logout after writeback

    I have very strange issue.
    After pressing the writeback button, system forces logout (goes to the login screen).
    At the same time writeback works, and is executed correctly (including commit).
    Has anyone encountered this issue?
    Below is my writeback message file - the WriteBackAccessApproval message gets triggered.
    <?xml version="1.0" encoding="utf-8" ?>
    <WebMessageTables xmlns:sawm="com.siebel.analytics.web/message/v1">
    <WebMessageTable lang="en-us" system="WriteBack" table="Messages">
    <WebMessage name="WriteBackAccessRequest">
    <XML>
    <writeBack connectionPool="Connection Pool">
    <insert>begin
                                  obiee_user_management_pkg.save_access_right_request('@{c5}','@{c3}','@{c0}','@{c54}','@{c62}','@{c64}', '@{c79}');
                             end;</insert>
                   <update>begin
                                  obiee_user_management_pkg.save_access_right_request('@{c5}','@{c3}','@{c0}','@{c54}','@{c62}','@{c64}', '@{c79}');
                             end;</update>
              </writeBack>
    </XML>
    </WebMessage>
    <WebMessage name="WriteBackAccessApproval">
    <XML>
    <writeBack connectionPool="Connection Pool">
    <insert>begin
                                  obiee_user_management_pkg.approve_request('@{c0}', '@{c9}', '@{c10}');
                             end;</insert>
                   <update>begin
                                  obiee_user_management_pkg.approve_request('@{c0}', '@{c9}', '@{c10}');
                             end;</update>
              </writeBack>
    </XML>
    </WebMessage>
    </WebMessageTable>
    </WebMessageTables>

    Hi Martins,
    Can you check your presentation server log file and your BI server log file and post any errors you see in them here? I'm wondering if some type of failure is happening after the write back occured.
    Thanks!
    -Joe

  • Logout prompt/ change log out dialog

    Hi All,
    I was wondering if somebody could help me. I would like to run a script when a user selects log out from the apple drop down to ask the user if they backed up their data before it allows them to log out.  I created a script that prompts you and then brings you to the logout screen but do not know how to get it to run, or something similar to run, when you select log out.  Obviously, I do not want it to run when the user has already logged out..
    The other option I see that could work would be to change the message, "are you sure you want to quit all applications and log out now?" which I cannot figure out how to do.
    Any help would be greatly appreciated
    Thanks,
    Marissa

    By the way the script is:
    tell application "Finder" to display dialog "Please Backup Your Data
    There is a risk of data loss if the machine experiences a hardware failure or an accident occurs" buttons {"Log Out", "Cancel"} default button "Cancel" with icon stop
    if button returned of result is "Log Out" then
              tell application "System Events"
      log out
              end tell
    end if

  • Primus: fatal: failure contacting bumblebee daemon [SOLVED]

    I just did a pacman -Syu which broke my system as usual. This time I get the above error message when trying to use primusrun:
    primus: fatal: failure contacting bumblebee daemon
    Trying to run glxshperes gives a slightly different message:
    $ primusrun glxspheres
    primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver
    and via optirun, just for the heck of it:
    $ optirun glxgears
    [ 2702.399865] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
    [ 2702.399894] [ERROR]Aborting because fallback start is disabled.
    <<SOLUTION: Replace all the *-bumblebee packages by * packages, this means enabling multiverse repo and drawing all of it from official repos instead of anything from AUR. Examples: nvidia instead of nvidia-bumblebee, primus instead of primus-git, nvidia-utils instead of nvidia-utils-bumblebee, lib32-nvidia-utils instead of lib32-nvidia-utils-bumblebee. Some time ago the 'official' instructions were exactly the other way round, but it seems this was now completely reverted.>>
    I noticed:
    1) primus in official repos (I was using git so far) causes a timeout from about 40 mirrors until it finds one where the download works. I hope that's no bad sign of some sort?
    2) bumblebeed update created new bumblebee.conf.pacnew and xorg.conf.nvidia.pacnew
    3) off-topic: When I clicked 'logout' in XFCE's applications menu, usually I get a box where I can pick whether I wanna logout/restart/shutdown etc, but this time it just straightly logged me out (makes sense I guess).
    4) after rebooting my system I saw I think two systemd error messages pop up for a split second, that usually did not occur.
    5) Xorg.8.log had the line "[633217.731] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 19.1, need < 19.0).  The driver will continue to load, but may behave strangely.", is this responsible maybe? Version conflict between X and nvidia?
    I tried:
    I restarted after the pacman -Syu update.
    I tried primusrun-git from AUR and primusrun from <community> but both exit with the error message.
    I tried the new conf files (copied the pacnew files to the normal filenames) but they don't work either.
    I checked:
    Bumbleed is running, systemctl shows
    bumblebeed.service loaded active running Bumblebee C Daemon
    and lspci | grep VGA shows the usual
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    01:00.0 VGA compatible controller: NVIDIA Corporation Device 0fd4 (rev a1)
    (After I try to start something with primusrun, the indicator light switches on and remains on, I can turn it off again with the usual
    echo OFF > /proc/acpi/bbswitch
    dmesg has these:
    [ 94.057043] nvidia: disagrees about version of symbol pv_mmu_ops
    [ 94.057047] nvidia: Unknown symbol pv_mmu_ops (err -22)
    echoing 'OFF' to bbswitch seems fine though (it worked, as I mentioned)
    [ 16.326834] bbswitch: version 0.6
    [ 16.326840] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
    [ 16.326843] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
    [ 16.326903] bbswitch: detected an Optimus _DSM function
    [ 16.326908] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
    [ 16.327995] bbswitch: disabling discrete graphics
    Here is /var/log/Xorg.8.log (trimmed):
    X.Org X Server 1.14.1
    [633217.228] X Protocol Version 11, Revision 0
    [633217.228] Build Operating System: Linux 3.8.7-1-ARCH x86_64
    [633217.229] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
    [633217.229] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [633217.293] (++) ModulePath set to "/usr/lib/nvidia-bumblebee/xorg/,/usr/lib/xorg/modules"
    [633217.295] Initializing built-in extension XVideo
    [633217.295] Initializing built-in extension XVideo-MotionCompensation
    [633217.295] Initializing built-in extension XFree86-VidModeExtension
    [633217.295] Initializing built-in extension XFree86-DGA
    [633217.295] Initializing built-in extension XFree86-DRI
    [633217.295] Initializing built-in extension DRI2
    [633217.295] (II) LoadModule: "glx"
    [633217.308] (II) Loading /usr/lib/nvidia-bumblebee/xorg/modules/extensions/libglx.so
    [633217.680] (II) Module glx: vendor="NVIDIA Corporation"
    [633217.680] compiled for 4.0.2, module version = 1.0.0
    [633217.681] Module class: X.Org Server Extension
    [633217.681] (II) NVIDIA GLX Module 313.26 Wed Feb 27 13:10:40 PST 2013
    [633217.681] Loading extension GLX
    [633217.681] (II) LoadModule: "nvidia"
    [633217.705] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [633217.731] (II) Module nvidia: vendor="NVIDIA Corporation"
    [633217.731] compiled for 4.0.2, module version = 1.0.0
    [633217.731] Module class: X.Org Video Driver
    [633217.731] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 19.1, need < 19.0). The driver will continue to load, but may behave strangely.
    [633217.732] (II) NVIDIA dlloader X Driver 313.26 Wed Feb 27 12:52:26 PST 2013
    [633217.732] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [633217.732] (--) using VT number 7
    [633217.733] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [633217.733] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [633217.733] (==) NVIDIA(0): RGB weight 888
    [633217.733] (==) NVIDIA(0): Default visual is TrueColor
    [633217.733] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [633217.733] (**) NVIDIA(0): Option "NoLogo" "true"
    [633217.733] (**) NVIDIA(0): Option "UseEDID" "false"
    [633217.733] (**) NVIDIA(0): Option "ConnectedMonitor" "CRT-0"
    [633217.734] (**) NVIDIA(0): Enabling 2D acceleration
    [633217.734] (**) NVIDIA(0): ConnectedMonitor string: "CRT-0"
    [633217.734] (**) NVIDIA(0): Ignoring EDIDs
    [633218.796] (II) NVIDIA(0): Implicitly enabling NoScanout
    [633218.796] (WW) NVIDIA(0): Failed to enable display hotplug notification
    [633218.799] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 660M (GK107) at PCI:1:0:0 (GPU-0)
    [633218.799] (--) NVIDIA(0): Memory: 2097152 kBytes
    [633218.799] (--) NVIDIA(0): VideoBIOS: 80.07.27.00.05
    [633218.799] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [633218.799] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 660M at PCI:1:0:0
    [633218.799] (--) NVIDIA(0): none
    [633218.799] (II) NVIDIA(0): Validated MetaModes:
    [633218.799] (II) NVIDIA(0): "nvidia-auto-select"
    [633218.799] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
    [633218.799] (WW) NVIDIA(0): Unable to get display device for DPI computation.
    [633218.799] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
    [633218.799] (--) Depth 24 pixmap format is 32 bpp
    [633218.799] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [633218.799] (II) NVIDIA: access.
    [633218.805] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [633218.805] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [633218.805] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [633218.805] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [633218.805] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [633218.805] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [633218.805] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [633218.805] (II) NVIDIA(0): Config Options in the README.
    [633218.806] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
    [633218.857] Loading extension NV-GLX
    [633218.865] (==) NVIDIA(0): Disabling shared memory pixmaps
    [633218.865] (==) NVIDIA(0): Backing store disabled
    [633218.865] (==) NVIDIA(0): Silken mouse enabled
    [633218.866] (==) NVIDIA(0): DPMS enabled
    [633218.866] Loading extension NV-CONTROL
    [633218.866] (II) Loading sub module "dri2"
    [633218.866] (II) LoadModule: "dri2"
    [633218.866] (II) Module "dri2" already built-in
    [633218.866] (II) NVIDIA(0): [DRI2] Setup complete
    [633218.866] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [633218.866] (--) RandR disabled
    [633218.879] (II) Initializing extension GLX
    Any ideas?
    PS: In this light I was wondering whether the https://wiki.archlinux.org/index.php/Bumblebee article is still up to date or might need reworking of some sort (I don't have any actual ideas to base this on though, was just a thought)
    PPS: https://bbs.archlinux.org/viewtopic.php?pid=1264430
    Last edited by Jindur (2013-04-27 18:10:21)

    iambig wrote:
    Hi,
    i haved some trouble too, from what i understood
    nvidia-bumblebee
    is deprecated, you should install
    nvidia
    otherwise i am not still able to use optirun/primus.
    Hm, so far it was emphasized NOT to install nvidia, because that would actually break it, but to use nvidia-bumblebee instead.
    Do you maybe have a link to information saying that it is now exactly the other way round?
    Has 'nvidia' been confirmed to work with bumblebee by anyone? Does it work for you?
    Edit: I just saw in my Xorg.8.log:
    [633217.731] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 19.1, need < 19.0). The driver will continue to load, but may behave strangely.
    Maybe this has to do with it? It seems there might be a version conflict between X and nvidia drivers?
    If anyone can confirm that the basic 'nvidia' packages are indeed replacing 'nvidia-bumblebee' now, instead of the other way round, I'll give them a try
    Last edited by Jindur (2013-04-26 12:30:37)

  • Xfce 4.4 - black or no desktop at all after logout

    I have this quite annoying problem with my xfce - after logout starting xfce takes more time and when it finishes I see black screen without icons and wallpaper, but panel, taskbar  are loaded correctly.  checking 'Allow xfce to manage your desktop' option brings no result - I noticed that deleting .cache and .config helps...but not always. Could U help me?

    I don't know if this issue is related or not, but I'll post it. I'm running a fresh install of "duke" with xfce4
    everything was working well. I wanted my desktop icons to remain in a certain order (I didn't want the mounted cd-rom icon at the top of the screen.) so, I went into the xfce settings manager thinking that there would be a setting under desktop preferences. Well I played with the desktop icons drop down menu and now I get this when I try to start xfdesktop:
    (xfdesktop:5747): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Bitstream Vera Sans Not-Rotated 0'
    Segmentation fault
    I'm not sure where to begin. I've already tried updating pango, gtk, and my bitstream fonts.
    UPDATE
    removing: ttf-bitstream-vera & ttf-freefonts brings back xfdesktop, but it looks crappy.
    Last edited by kjs (2007-05-20 23:14:11)

Maybe you are looking for