OIM problem with weblogic administration server (configuring OIM)

Hi,
I have this software installed:
- Oracle database 11gR2 (schemas made with RCU)
- SOA Suite generic 11.1.1.2.0
- Repository Creation Utility
- Weblogic Server 1034
- JDK 1.6.0_24
- IAM_generic 11.1.1.1.3.0 (OIM)
when I'm configuring the oracle identity management 11.1.1.3.0 and I'm in the weblogic administration server screen I write in the fields:
url administration server : t3://localhost:7001
Username: weblogic
Password: ****** (correct)
when it tries to connect to weblogic I get an error that says:
INST-6180: It has not been possible to get the URL server managed by the OIM domain // (spanish translation of the error)
then if look at the weblogic standard output (and in the admin server log) I see the following error
####<23-feb-2011 21H04' CET> <Warning> <RMI> <WIN-5GJP37O0LUL> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1298491447915> <BEA-080003> <RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.getAttribute(Ljavax.management.ObjectName;Ljava.lang.String;Ljavax.security.auth.Subject;)
java.lang.NullPointerException.
java.lang.NullPointerException
     at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:768)
     at weblogic.management.mbeanservers.internal.JMXContextInterceptor.getMBeanContextLoader(JMXContextInterceptor.java:475)
     at weblogic.management.mbeanservers.internal.JMXContextInterceptor.getAttribute(JMXContextInterceptor.java:146)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
     at java.security.AccessController.doPrivileged(Native Method)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
     at java.security.AccessController.doPrivileged(Native Method)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
     at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:299)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:279)
     at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$5$1.run(JMXConnectorSubjectForwarder.java:326)
     at java.security.AccessController.doPrivileged(Native Method)
     at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$5.run(JMXConnectorSubjectForwarder.java:324)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.getAttribute(JMXConnectorSubjectForwarder.java:319)
     at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1404)
     at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
     at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
     at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:600)
     at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Thanks for your time

As mentioned earlier in this thread please use 10.3.3 weblogic .
I have created 8 post step by step installation series for OIM/OAM/OAAM/OAPM inclding SOA here http://onlineappsdba.com/index.php/2010/08/05/oracleidm-11g-step-by-installation-of-oam-oim-oaam-oapm-oin-111130-part-i-load-schema/
IDAM 11g certification matrix is at http://www.oracle.com/technetwork/middleware/id-mgmt/identity-accessmgmt-11gr1certmatrix-161244.xls
Atul Kumar
- Book "OAM/OIM 11g for Administrators" -> http://onlineappsdba.com/index.php/2011/02/23/my-book-oracle-identity-access-manager-11g-for-administrators-is-now-available-in-raw-format/
Edited by: onlineAppsDBA.com on May 15, 2011 2:15 PM

Similar Messages

  • Problem with The Administration Server

    Hi, I have the following problem....
    sorry for my bad english....
    on the server sun is installed "iplanet slapd-server" and all the users they are autenticatede whit it....
    now i want to install SJES and i want to use this "iplanet slapd-server"....
    when i run /usr/sbin/mpsadmserver configure:
    oot@server:/shared/java_ent_sys_2005Q4/Solaris_sparc> /usr/sbin/mpsadmserver configure
    Enter the fully qualified name of the computer
    Fully Qualified Computer Name [server.dominio.com] {"<" goes back, "!"
    exits}:
    Server Root Information
    Server Root: : /var/mps/serverroot
    Choose the type of installation you prefer from the following choices:
    Express - Installation option choices are made automatically. The easiest
    installation and recommended for evaluating the product.
    Typical - Software will be installed with the most common options. Recommended
    for most deployments.
    1. Express
    2. Typical
    What would you like to do [2] {"<" goes back, "!" exits}? 2
    Choose the system user and group names under whose identity
    the Sun Java(TM) System Server will run.
    System User [root] {"<" goes back, "!" exits}:
    System Group [other] {"<" goes back, "!" exits}:
    Configuration Directory Server
    Host [] {"<" goes back, "!" exits}: server
    Port [] {"<" goes back, "!" exits}: 389
    Configuration Directory Server Administrator
    Administrator ID [admin] {"<" goes back, "!" exits}: cn=directory manager
    Password:*******
    Administration Domain
    Administration Domain [dominio.com] {"<" goes back, "!" exits}:
    The Administration Server runs on a different network port from other servers.
    Specify the number of the port.
    Administration Port [390] {"<" goes back, "!" exits}:
    Installing Administration Server
    |-1%--------------25%-----------------50%-----------------75%--------------100%|
    Checking connection to the Configuration Directory Server... failed.
    The Admininistration Server cannot be configured.
    :(.... where the error?
    thanks....

    This is a typical error when the fully qualified hostname of the machine cannot be properly resolved.
    Said differently, can a client on the network connect to the machine server.dominio.com ? Is this machine known in DNS ?
    Regards,
    Ludovic.

  • Problem with Weblogic Commerce Server 3.1

    I am currently evaluating the Weblogic Commerce server 3.1 product. I have
    installed the Weblogic server 5.1 and the service pack 6 along with the
    Commerce Server. I can get into the WLCS Commerce Server Templates and can
    navigate the store categories and search for items but when I try to add to
    the shopping cart or view the shopping cart I get taken to the 'servererror'
    template. I have included at the bottom of this message the message from
    the log file. Does anyone have any idea why I am getting this error?
    Thanks in advance,
    Barry Childs
    Manager Knowledgebase Applications
    Xactsites
    <<<<<<< weblogic.log >>>>>>>
    Fri Nov 10 14:00:16 MST 2000:<E> <WebAppServletContext-wlcs> Servlet failed
    with Exception
    weblogic.servlet.jsp.JspException: (line -1): Error in tag library at: 'wl':
    For tag 'repeat', cannot load extra info class
    'weblogicx.jsp.tags.RepeatTagInfo'
    at
    weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
    at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java,
    Compiled Code)
    at
    weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java,
    Compiled Code)
    at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
    at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java,
    Compiled Code)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java, Compiled
    Code)
    at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java, Compiled Code)
    at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
    at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
    at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled Code)
    at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
    at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
    at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
    at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
    at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
    Compiled Code)
    at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
    at
    weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
    Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
    l.java:154)
    at
    com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestinat
    ion(ServletDestinationHandler.java:51)
    at
    com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:376
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:761)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:708)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:252)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

    I am currently evaluating the Weblogic Commerce server 3.1 product. I have
    installed the Weblogic server 5.1 and the service pack 6 along with the
    Commerce Server. I can get into the WLCS Commerce Server Templates and can
    navigate the store categories and search for items but when I try to add to
    the shopping cart or view the shopping cart I get taken to the 'servererror'
    template. I have included at the bottom of this message the message from
    the log file. Does anyone have any idea why I am getting this error?
    Thanks in advance,
    Barry Childs
    Manager Knowledgebase Applications
    Xactsites
    <<<<<<< weblogic.log >>>>>>>
    Fri Nov 10 14:00:16 MST 2000:<E> <WebAppServletContext-wlcs> Servlet failed
    with Exception
    weblogic.servlet.jsp.JspException: (line -1): Error in tag library at: 'wl':
    For tag 'repeat', cannot load extra info class
    'weblogicx.jsp.tags.RepeatTagInfo'
    at
    weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
    at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java,
    Compiled Code)
    at
    weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java,
    Compiled Code)
    at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
    at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java,
    Compiled Code)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java, Compiled
    Code)
    at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java, Compiled Code)
    at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
    at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
    at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled Code)
    at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
    at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
    at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
    at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
    at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
    Compiled Code)
    at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
    at
    weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
    Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
    l.java:154)
    at
    com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestinat
    ion(ServletDestinationHandler.java:51)
    at
    com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:376
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:761)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:708)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:252)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

  • OIM 9101 with Weblogic 10.3.0 - basic query

    Hi All
    I am trying to install OIM 9101 with Weblogic 10.3.0 and Oracle DB 11.1.0.6 on Windows 2003 (64-bit) and Sun JDK 1.6.0_10 (Oracle certified configuration).
    The problem is that my weblogic fails to start-up as soon as I enter the weblogic user-name on the command prompt. It says that the weblogic is not able to use some binary to pick-up the userID. This may be some issue related to Win 64bit environment.
    To overcome this issue, I hard coded the userID and password for weblogic in Weblogic's SetDomainEnv.cmd file.
    I want to know whether including the userID and password in the weblogic's file can result in OIM installation failure.
    Please help.

    I personally don't think your OIM installation will fail because of that as OIM installation only execute some of the WLS configuration script to install OIM applications into WLS.

  • Problems with weblogic clustering in 6.1 sp3

    We have spent a lot of time trying to get our application deployed to
              a cluster using weblogic 6.1 sp3 and we consistently receive a failure
              when we attempt to start the managed server. This was not a problem
              with weblogic sp1--we got our application to deploy to the cluster
              successfully; although there was another weblogic bug there with
              clients accessing EJB clusters--we won't go into that here...
              We have tried this on both a Windows 2000 machine and an HP machine
              running weblogic sp3. The same error occurs on both platforms.
              The error in deploying our application to the cluster against weblogic
              sp3 looks to have to do with our custom security realm. Inside our
              custom realm we make use of a configurable providerUrl which we set to
              the cluster address/port. The custom realm makes a call where it
              passes in the providerUrl to:
                   weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
              When we have our providerUrl set to the cluster address/port--e.g.,
                   t3://clustermember1:7001
              and attempt to start the managed server we get the error:
              Starting WebLogic Server ....
              Connecting to http://adminserver:7117...
              The WebLogic Server did not start up properly.
              Exception raised:
              weblogic.management.configuration.ConfigurationException:
              clustermember1 not found
                   at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
                   at weblogic.management.Admin.initialize(Admin.java:340)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
                   at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              When we have our providerUrl set to the admin server address--e.g.,
                   t3://adminserver:7117
              everything starts up fine.
              Does anyone know why this would work on sp1 and not sp3 of weblogic
              6.1?
              We verified that all passwords are correct and everything else we
              could determine--any ideas would be helpful.
              We don't want the providerUrl to point at our admin server, we want it
              to point at the cluster address/port.
              When we get the managed server error, we received this error on the
              AdminServer:
              2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
              'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
              Caught naming exception null; throwing RuntimeException.
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
              unreachable; nested exception is:
                   java.net.ConnectException: Connection refused; No available router to
              destination
                   at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
                   at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
                   at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
                   at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
                   at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
                   at javax.naming.InitialContext.init(InitialContext.java:222)
                   at javax.naming.InitialContext.<init>(InitialContext.java:198)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
                   at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
                   at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
                   at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
                   at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
                   at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
                   at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
              <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
              Servlet failed with Exception
              java.lang.RuntimeException
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
                   at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
                   at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
                   at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
                   at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
                   at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Thanks for any help.
              Rich
              

    Bottom line:
              In our custom realm we were not handling user guest correctly. Even if you
              have guest user disabled, Weblogic seems to have hard-coded guest to
              send messages to the cluster every-so-often. Not sure there--couldn't get
              an answer out of bea as to exactly why we see guest still being used...
              It seems that with sp3, the user guest interaction started happening earlier
              than it did with sp1, consequently making our realm code fail when trying to
              retrieve the guest user like someone we knew about in our system.
              Hence, our getUser and authUserPassword methods now return null for both
              users guest and system, making the secondary realm (file realm) be used to
              authenticate and resolve guest & system. BEA helped get our code fixed;
              however, we still don't have a lot of depth in understanding Weblogic
              server's use of guest...
              Apparently, in 7.x the guest & system user behavior and configuration is
              different also... We'll see when we start digging into that migration.
              Rich
              [email protected] (Rich Koch) wrote in message news:<[email protected]>...
              > Thanks for the responses--we're working with weblogic support now. We
              > think that the custom realm that we have [the developer that wrote it
              > left the company] is the problem.
              >
              > The original developer was told by someone to check:
              > weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
              >
              > In order to determine if the JNDI was available/ready for the whole
              > cluster.
              >
              > It seems that the meaning/setting of THE_ONE changed with this respect
              > from
              > sp1 to sp3--i.e., this is no longer a valid test to tell us if the
              > JNDI is
              > ready for the cluster.
              >
              > We believe this was used because the 'system' user has to be
              > authenticated before the custom realm is up. Originally, before this
              > check was in place, an exception was received when authenticating
              > 'system'. This appears to be a weblogic limitation/issue. Support
              > has told us that this is different in weblogic 7.0. Unfortunately, we
              > can't upgrade from 6.1 yet.
              >
              > We'll post the solution when this gets figured out.
              >
              > Rak
              >
              > "Sabha" <[email protected]> wrote in message news:<[email protected]>...
              > > There was a security restriction enforced from sp2/sp3 onwards in terms of
              > > looking up mbeans from admin server.
              > >
              > > This might cause things to fail if you are attempting to lookup Mbeans with
              > > guest priviliges from admin server. Also, can you try doing the following:
              > >
              > > Run " java weblogic.Admin -url adminServer -username system -password
              > > .... -GET -pretty -type Server" and check whether the named clustermember1
              > > is available in the list or not.
              > >
              > > Also you seem to be getting some security exception - can you check that.
              > >
              > > t3://tomtate.msais.com:7119: Destination
              > > unreachable; nested exception is:
              > >
              > > --- Try running weblogic.Admin PING on this one and see whether you are
              > > able to reach this server upon the error message.
              > >
              > > --Sabha
              > >
              > > "Rich Koch" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > We have spent a lot of time trying to get our application deployed to
              > > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
              > > > when we attempt to start the managed server. This was not a problem
              > > > with weblogic sp1--we got our application to deploy to the cluster
              > > > successfully; although there was another weblogic bug there with
              > > > clients accessing EJB clusters--we won't go into that here...
              > > >
              > > > We have tried this on both a Windows 2000 machine and an HP machine
              > > > running weblogic sp3. The same error occurs on both platforms.
              > > >
              > > > The error in deploying our application to the cluster against weblogic
              > > > sp3 looks to have to do with our custom security realm. Inside our
              > > > custom realm we make use of a configurable providerUrl which we set to
              > > > the cluster address/port. The custom realm makes a call where it
              > > > passes in the providerUrl to:
              > > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
              > > >
              > > > When we have our providerUrl set to the cluster address/port--e.g.,
              > > > t3://clustermember1:7001
              > > >
              > > > and attempt to start the managed server we get the error:
              > > >
              > > > Starting WebLogic Server ....
              > > > Connecting to http://adminserver:7117...
              > > >
              > ***************************************************************************
              > > > The WebLogic Server did not start up properly.
              > > > Exception raised:
              > > > weblogic.management.configuration.ConfigurationException:
              > > > clustermember1 not found
              > > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
              > > > at weblogic.management.Admin.initialize(Admin.java:340)
              > > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
              > > > at weblogic.Server.main(Server.java:35)
              > > > Reason: Fatal initialization exception
              > > >
              > ***************************************************************************
              > > >
              > > > When we have our providerUrl set to the admin server address--e.g.,
              > > > t3://adminserver:7117
              > > >
              > > > everything starts up fine.
              > > >
              > > > Does anyone know why this would work on sp1 and not sp3 of weblogic
              > > > 6.1?
              > > > We verified that all passwords are correct and everything else we
              > > > could determine--any ideas would be helpful.
              > > >
              > > > We don't want the providerUrl to point at our admin server, we want it
              > > > to point at the cluster address/port.
              > > >
              > > > When we get the managed server error, we received this error on the
              > > > AdminServer:
              > > >
              > > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
              > > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
              > > > Caught naming exception null; throwing RuntimeException.
              > > > javax.naming.CommunicationException. Root exception is
              > > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
              > > > unreachable; nested exception is:
              > > > java.net.ConnectException: Connection refused; No available router to
              > > > destination
              > > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > > at
              > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > > at
              > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > > at
              > > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > > at
              > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
              > > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
              > > > at javax.naming.InitialContext.init(InitialContext.java:222)
              > > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
              > > Realm.java:416)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
              > > lm.java:347)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
              > > java:51)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
              > > 225)
              > > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
              > > Realm.java:578)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
              > > a:221)
              > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
              > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
              > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
              > > > at
              > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
              > > ava:356)
              > > > at
              > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
              > > tSecurityManager.java:205)
              > > > at
              > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > > ntext.java:2518)
              > > > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > > :2260)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
              > > >
              > > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
              > > al2)]
              > > > Servlet failed with Exception
              > > > java.lang.RuntimeException
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
              > > a:260)
              > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
              > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
              > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
              > > > at
              > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
              > > ava:356)
              > > > at
              > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
              > > tSecurityManager.java:205)
              > > > at
              > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > > ntext.java:2518)
              > > > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > > :2260)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > >
              > > >
              > > > Thanks for any help.
              > > >
              > > > Rich
              

  • Problem with the new server UCS C220 for set IP to CIMC

    Hi
    We’ve a problem with the new server UCS C220.
    We bought two servers UCS C220 M3 for CallManager 8.6 with High Availability.
    When we turn on the server during the boot and when it tells us, oppress F8 to enter at the CIMC and set the IP. But it never enters at the CIMC.
    Then, we configure our DHCP server and our switch, we connect the three gigabyte ports to our switch to give him an IP to the CIMC, so and then can enter via browser, but neither works.
    Note. The dedicated management NIC does not link, the other two ports do make link.
    What do you suggest to put an IP to CIMC and start installing our applications?
    regards

    You may have noticed that there is no DVD rom on the c220. What you need to do is:
    Login into the CIMC from your browser
    Luanch the KVM
    Insert the VMware DVD in your machines drive
    On the KVM pop up there should be a tab to mount the drive, after mounting it click on Macros and choose ctrl_alt+delete to restart.
    After the VMware OS installs press F2 to enter IP.
    Browse to the VMware ip to download the Vsphere client
    Open the Vsphere client, enter the ip of the vmware and the username will be root and no password if you did not set one.
    You can now upload OVA templates or manually create virtua machine from this enviroment.
    Hope this help

  • Why do I get an "unable to connect - There may be a problem with the mail server or network." message from iCloud.  I have verified the settings.  I can access my iCloud account online but can't send or receive e-mail via the mail account.

    Text limits to the "Question" link prevents a full explanation:
    This is a long-time problem.  I have tried to resolve it with Apple but their "Customer Support" is merely a name.
    I can go online and access my e-mail but when I try to send or receive e-mail via iCloud through my internet server (Google fiber now but the same situation existed with my prior service), I receive "There may be a problem with the mail server or network.  Verify the settings for 'Apple Email' and try again.
    "The server returned the error:  The server 'p0-imap.mail.me.com' refused to allow a connection on port 143."
    Well, I have verified the setting and tried again and again and …
    Well, you get the idea …

    JungleTaxi Cabbie wrote:
    Csound1: iCloud: Configuring Mail with Mac OS X v10.6 or iOS 4
    Enter your Incoming Mail Server, User Name, and Password using the following settings:
    Incoming Mail Server: mail.me.com
    User Name: Your iCloud email address (excluding @me.com)
    Password: Your password
    Last Modified: Jun 27, 2013
    Maybe you should test these things before calling people out, because these settings do function perfectly well.
    iCloud is not supported on Snow Leopard or lower, why bother to mention it?
    The OP has an iCloud account, and that can not be opened without Lion or Mountain Lion (on a Mac), IOS5 or 6 (on an iPhone/iPad)
    The document I linked to is Apples documentation for iCloud on current devices,I don't care whether you believe that you know better than they do, but it will affect the people who follow your advice as it won't work
    JungleTaxi Cabbie wrote:
    Also, if you're not running Lion or Mountain Lion, there is no "Mail, Contacts & Calendars" prefpane.
    I never said that there was, perhaps you imagined it.

  • OAM (10.1.4.3) Integration with WebLogic App Server (10.3.0 or below)

    Hi All,
    Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
    OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
    And
    OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.

    Hi,
    This is how the integration goes with different versions of WLS and OAM.
    There is oamAuthnProvider.jar available with OAM 10.1.4.3 downloads. So it provides the assertion functionality.
    Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
    Mahendra: Yes
    OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
    Mahendra: Yes, this is the recommended and easy approach.
    OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.
    Mahendra: Yes, older version of OAM uses SSPI connector installation.
    HTH.
    Mahendra.

  • Having problems starting Weblogic Managed Server

    Hi,
    I am new to WebLogic and I was looking at the webservices examples in samples dir and I took the example and just moved it to one of my currently deployed Web Application folder and changed the dir strutcure instead of the samples dir strutcure, compiled and deployed as standalone Application(not as part of my currently deployed Web App). It worked fine.
    Then since there would be a need for reuse of lot of the current Web App. in the web services we are trying to implement, I tried to put the ear that got created in the WEB-INF/lib of the currently deployed exploded dir. It was pretty dumb to put the ear there, just thought, worst case it wont work, I thought I could pull the ear out of there. But seems like this changed the entire config.xml and ever since that my admin server got changed to myserver, I corrected all the problems with the admin server and admin server and node server they come up just fine. When trying to bring up Managed server, I get the following excpetion
    Jul 16, 2004 4:00:37 PM EDT> <Debug> <HTTP> <BEA-101158> <Exception thrown while loading epic_dev: java.lang.NullPointerException
    java.lang.NullPointerException
         at weblogic.utils.enumerations.FileEnumeration.getNextFile(FileEnumeration.java:155)
         at weblogic.utils.enumerations.FileEnumeration.hasMoreFiles(FileEnumeration.java:102)
         at weblogic.utils.enumerations.FileEnumeration.hasMoreElements(FileEnumeration.java:134)
         at weblogic.utils.jars.ExplodedJarFile$1.hasNext(ExplodedJarFile.java:112)
         at weblogic.utils.classloaders.ExtractionHelper.extractClassFiles(ExtractionHelper.java:117)
         at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5119)
         at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:4991)
         at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:560)
         at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:511)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:594)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:623)
         at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:2896)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
         at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
         at weblogic.Server.main(Server.java:32)
    >
    <Jul 16, 2004 4:00:37 PM EDT> <Info> <Deployer> <BEA-149061> <Module epic_dev of application appsdirepic_dev_dir failed to transition from unprepared to prepared on server betsy_dev.>
    <Jul 16, 2004 4:00:37 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application appsdirepic_dev_dir due to error weblogic.management.ApplicationException: prepare failed for epic_dev
    Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
    weblogic.management.ApplicationException: prepare failed for epic_dev
    Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
         at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
         at weblogic.Server.main(Server.java:32)
    >
    Could someone help me with resolving this.(This is only the dev machine, I played thannkfully!).
    And also would like to get suggestions on setting up the new webserverces that we are trying to do. If I need to reuse lot of class files from current appl., how do i go about implementing this webservice? Should this be part of the existing application? or Web service could be a separate application and somehow we could look at the web app which is in the same domain.
    Any help is appreciated.
    Thanks
    Anna

    There was an access problem in the application I was trying to deploy and it had nothing to do with EAR file, once the access problem is taken care of, I could deploy the app just fine.

  • Problem with Weblogic Builder SP1

    I have a problem with Weblogic Builder SP1. I basically re-used my EJB deployment
    descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loading my EJB
    in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
    I re-attempted by jarring my EJB with WL5.1 descriptors and used my friend's WB
    (not SP1) to export new descriptors which I used to re-jar. This new EJB is again
    not recognised by WB SP1?
    What is wrong?

    The exception is as follows:
    Opening module myproj.jar
    java.lang.NullPointerException
         at java.util.Arrays.sort(Arrays.java:1181)
         at weblogic.marathon.model.EJBJarCMBean.initRelations(EJBJarCMBean.java:1212)
         at weblogic.marathon.model.EJBJarCMBean.initBeans(EJBJarCMBean.java:1098)
         at weblogic.marathon.model.EJBJarCMBean.setup(EJBJarCMBean.java:1144)
         at weblogic.marathon.tasks.OpenModuleTask.getEJBModule(OpenModuleTask.java:156)
         at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:191)
         at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:230)
         at weblogic.marathon.tasks.OpenModuleTask.runBackground(OpenModuleTask.java:89)
         at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)
         at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)
    Module myproj.jar descriptors failed to load
    The EJB has no problem deploying.
    Rob Woollen <[email protected]> wrote:
    You'll have to at least show us the error you get from marathon.
    Does your application deploy to the server?
    -- Rob
    Robin Tan wrote:
    I have a problem with Weblogic Builder SP1. I basically re-used myEJB deployment
    descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loadingmy EJB
    in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
    I re-attempted by jarring my EJB with WL5.1 descriptors and used myfriend's WB
    (not SP1) to export new descriptors which I used to re-jar. This newEJB is again
    not recognised by WB SP1?
    What is wrong?

  • Use case of FQDN parameter in CPPM -- Administration -- Server Configuration

    Q: What is the difference between 'FQDN' & 'Hostname' parameter available in the ClearPass Server configuration?
    A: The FQDN parameter is primarily used for SSO functionality with any external IDP servers. We can configure the VIP hostname of a ClearPass cluster to be the FQDN.
     'Hostname' parameter in the Administration --> Server Configuration, does not need to be an FQDN. We can specify any user defined names. If we need to join the ClearPass cluster members to the same Active directory domain, then hostname should be different. Otherwise, it will create duplicate computer/machine accounts for ClearPass Server in the Domain Controller and may lead to PEAP-EAP-MSCHAPv2 authentication issues/failures for the clients against Active Directory.

    You could use regular expressions to try to strip the "+" from your form variables but wouldn't it be easier to just have the select field display +5 and then just pass "5"  and not use the plus character in your database or in your passed variables?  Special characters in your passed variables is always a potential headache.
    Lawrence   *Adobe Community Expert*
    www.Cartweaver.com
    Complete Shopping Cart Application for
    Dreamweaver, available in ASP, PHP and CF
    www.twitter.com/LawrenceCramer

  • Unable to connect to Oracle Weblogic Administration Server

    Hi Folks,
    As part of installation steps, I am facing error with " Unable to connect to Oracle Weblogic Administration Server"
    Below is AdminServer Log, So please guide me reolving this impending issue.
    ####<12 Jun, 2014 2:46:01 PM IST> <Info> <Deployer> <obia111171w64> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KQFMukk5yW^5xV_AiW1JaMxv000002> <1402564561284> <BEA-149059> <Module adminservicesmbeans of application biadminservices [Version=11.1.1] is transitioning from STATE_ADMIN to STATE_PREPARED on server AdminServer.>
    ####<12 Jun, 2014 2:46:05 PM IST> <Info> <Deployer> <obia111171w64> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KQFMukk5yW^5xV_AiW1JaMxv000002> <1402564565300> <BEA-149061> <Module adminservicesmbeans of application biadminservices [Version=11.1.1] failed to transition from STATE_ADMIN to STATE_PREPARED on server AdminServer.>
    ####<12 Jun, 2014 2:46:11 PM IST> <Error> <Deployer> <obia111171w64> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KQFMukk5yW^5xV_AiW1JaMxv000002> <1402564571861> <BEA-149231> <Unable to set the activation state to true for the application 'biadminservices [Version=11.1.1]'.
    weblogic.management.DeploymentException: Unexpected error encountered
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.getOrCreateDeploymentException(AppContainerInvoker.java:299)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:84)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
      at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
      at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
      at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
      at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
      at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
      at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
      at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: java.lang.OutOfMemoryError: PermGen space
      at weblogic.j2ee.J2EELogger.logIgnoringUndeploymentError(J2EELogger.java:2902)
      at weblogic.application.internal.BaseDeployment$2.logRollbackError(BaseDeployment.java:682)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:65)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
      at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
      at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
      at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
      at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
      at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
      at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
      at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    Thanks,
    Wj

    Did you manage to solve this issue?
    I'm running into the exact same error, but installing 11.1.1.7.0 on Windows 2003
    Haven't found anything on MOS yet :(
    Kind regards,
    Rob
    Edited by: rgouw on 10-apr-2013 1:10

  • Problem with SAP XI server

    Hi guys
    I got a problem with the XI server,the status do not change to wait,they are always in run,i can send you the screen shots to there mail id if anyone is able to slove.I think it is the oracle problem,not sure though.I am unable to log on to the server
    thanks
    [email protected]

    I am looking for
    ADM100 SAP Web AS Administration I,
    ADM102 SAP Web AS Administration II
    ADM200 SAP Web AS Java Administration )
    If any one of you has this or any xi material,
    Can you please mail me to [email protected]
    Thanks in Advance,
    jaya

  • Problems with AOL IMAP server connection on my BlackBerry Z10 STL100-3, and BB PlayBook 64GB WiFi

    Problems with AOL IMAP server connection on my BlackBerry Z10 STL100-3, and BB PlayBook 64GB WiFi
    Thursday 4:20am EST, 02-19-2015
    Hi, My connection to the AOL IMAP server has suddenly failed - Says "Not Connected" on Accounts page
    I haven't changed anything and this just started failing this morning.
    I've saw same issue on my Blackberry PlayBook 64GB.
    Is anyone else recently experiencing AOL IMAP Errors?
    Solved!
    Go to Solution.

    Yes! Same thing happened suddenly to my Z10 this morning. No AOL. 

  • HT4864 I am getting a triangle with an exclamation point next to my inbox...it says: There may be a problem with the mail server or network. Verify the settings for account "MobileMe" or try again.  The server returned the error: Mail was unable to log in

    I can send but cannot recieve email
    This is the messege I am gewtting:
    There may be a problem with the mail server or network. Verify the settings for account “MobileMe” or try again.
    The server returned the error: Mail was unable to log in to the IMAP server “p02-imap.mail.me.com” using “Password” authentication. Verify that your account settings are correct.
    The server returned the error: Service temporarily unavailable

    Also if I go to system preferences accounts and re-enter the password it fixes the glitch sometimes.

Maybe you are looking for