Server1 canot start on weblogic integration cluster

I can not start server1 on weblogic integration cluster, out and logs are:
<> <1345403377689> <BEA-000000> <Error in startup class com.bea.wli.management.configfile.ConfigFileManager Method: initialize:
java.lang.AssertionError: MBeanHome lookup failedjavax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management';
remaining name 'adminhome'
at weblogic.management.Admin.lookupMBeanHome(Admin.java:245)
at weblogic.management.Admin.getAdminMBeanHome(Admin.java:260)
at com.bea.wli.management.MBeanHelper.getMBeanHome(MBeanHelper.java:161)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:100)
at com.bea.wli.management.configfile.ManagedRepAgent.<init>(ManagedRepAgent.java:83)
at com.bea.wli.management.configfile.ManagedConfigFileManager.<init>(ManagedConfigFileManager.java:53)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:101)
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:597)
at com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:287)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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:597)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Aug 19, 2012 4:09:37 PM BRT> <Critical> <WebLogicServer> <adriana> <server1> <Main Thread> <<WLS Kernel>> <> <> <1345403377696> <BEA-000362> <Server failed. Reason
There are 1 nested errors:
java.lang.AssertionError: MBeanHome lookup failedjavax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management';
remaining name 'adminhome'
at weblogic.management.Admin.lookupMBeanHome(Admin.java:245)
at weblogic.management.Admin.getAdminMBeanHome(Admin.java:260)
at com.bea.wli.management.MBeanHelper.getMBeanHome(MBeanHelper.java:161)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:100)
at com.bea.wli.management.configfile.ManagedRepAgent.<init>(ManagedRepAgent.java:83)
at com.bea.wli.management.configfile.ManagedConfigFileManager.<init>(ManagedConfigFileManager.java:53)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:101)
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:597)
at com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:287)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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:597)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

Hi Alex,
That's weird, I have WLI installed here in some of the servers, but there is no ConfigFileManager startup class...
Go to the config.xml file and comment out all startup and shutdown classes and see if that helps to start the server at least... You may have to reinstall WLI though...
Hope this helps...
Cheers,
Vlad

Similar Messages

  • Weblogic Integration failed to build Cluster ENV

    Dear buddies,
    I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
    Here is the process how I created WLI cluster:
    ENV:RedHat9+ WL8.1_SP4
    Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
    BEA_HOME=/opt/bea/
    1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
    and I didn't create extra JDBC POOL except the standard one.
    2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
    Now I am having following problem.
    1.admin Server(cgServer) can startup without any problem
    2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
    3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
    but seems the pointbase only listen 9092!!
    4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
    below are detailed output when I startManagedServers:
    command:
    [root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
    ####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
    Listen Address          172.16.4.236:7001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
    Channel Weight          50
    Accept Backlog          50
    Login Timeout          5000ms
    Max Message Size     10000000
    Message Timeout     60s
    Idle Timeout          65s
    Tunneling Timeout     40s
    Tunneling Ping          45s>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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 weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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 weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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 weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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 weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)

    Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.

  • Problem on starting weblogic integration 2.1

    I would like to ask you for advise/information on the start-up of the
    weblogic integration 2.1.
    I have tried to setup the weblogic integration 2.1 (sp1) at home, but
    without any success yet.
    There was nothing helpful that I can found in the BEA knowledge base.
    My weblogic server 6.1 (sp2) starts up alone normally and working fine, and
    I have followed
    all the steps in the installation document, including create and setup the
    database.
    I have also executed the setenv.cmd and make sure the domain in use is
    "wlidomain".
    When I try to start up the weblogic integration 2.1, it give me the
    following exception.
    C:\bea\wlintegration2.1\config\wlidomain>startWeblogic.cmd
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.ArrayIndexOutOfBoundsException
    at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
    at com.bea.utils.misc.Process.validate(Process.java:1231)
    at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
    at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
    at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:286)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance, and looking forward for your reply soon.
    Best Regards,
    Matthew Ho

    Hi.
    Try posting this on either weblogic.integration.interest or
    weblogic.integration.developer.
    Thanks,
    Michael
    Matthew Ho wrote:
    I would like to ask you for advise/information on the start-up of the
    weblogic integration 2.1.
    I have tried to setup the weblogic integration 2.1 (sp1) at home, but
    without any success yet.
    There was nothing helpful that I can found in the BEA knowledge base.
    My weblogic server 6.1 (sp2) starts up alone normally and working fine, and
    I have followed
    all the steps in the installation document, including create and setup the
    database.
    I have also executed the setenv.cmd and make sure the domain in use is
    "wlidomain".
    When I try to start up the weblogic integration 2.1, it give me the
    following exception.
    C:\bea\wlintegration2.1\config\wlidomain>startWeblogic.cmd
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.ArrayIndexOutOfBoundsException
    at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
    at com.bea.utils.misc.Process.validate(Process.java:1231)
    at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
    at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
    at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:286)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance, and looking forward for your reply soon.
    Best Regards,
    Matthew Ho--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Starting Weblogic Server Cluster remotely via VPN

    We have a site-to-site VPN setup from our office to our ISP so we can
              control our system remotely. We can stop our Weblogic servers (in a
              cluster) remotely via the VPN no problem via the "stopweblogic.cmd" command
              where we just change the IP address of our remote server. We're having
              trouble starting them through the WebLogic console applet. We can bring the
              applet up & running, but no luck starting them.
              Is there another way to start your weblogic servers (besides using something
              like PC Anywhere).
              Or is there any documentation that could point to an answer here?
              Any suggestions?
              Mike Kendzierski
              B2BGalaxy.com
              

    1. "myserver" is the name of the server. It doesn't want the name of the
    machine the server is on.
    2. It is possible that something is wrong in the license file. I've made a
    typo when changing the license on my server that prevented weblogic from
    starting.
    Hope this helps.
    "Hilmar" <[email protected]> wrote in message
    news:[email protected]..
    >
    When I start WebLogic server using startweblogic.cmd everything seems tobe okay.
    Using the 'Start a new WebLogic server or cluster' command from WebLogicConsole
    5.1.0, I get the following error message:
    Attempting to start server on the machine running the console using
    C:\weblogic\jre1_2\jre\bin\java.exe -mx32m -ms32m -classpath"C:\weblogic\jre1_2\jre\lib\rt.jar;C:\weblogic\jre1_2\jre\lib\i18n.jar;C:\we
    blogic\lib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib
    \cloudscape.jar"
    -Dweblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib\weblogicaux.jar
    -Dweblogic.system.discardOutAndErr=true -Djava.security.manager -Djava.security.policy==C:\weblogic\weblogic.policy
    -Dweblogic.system.name=kenapp00111 -Dweblogic.system.home=C:\weblogic -Dweblogic.cluster.enable=false
    -Dweblogic.cluster.name=mycluster -Dweblogic.system.listenPort=7001 -Dweblogic.system.SSLListenPort=7002
    -Dweblogic.cluster.multicastAddress=237.0.0.1 weblogic.Server
    $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
    Loaded License : C:/weblogic/license/WebLogicLicense.xml
    However Unable to start because :
    No License found for WebLogic
    As well as the fact that: No License found for Tengah
    As well as the fact that: No License found for WebLogic/JDBC
    As well as the fact that: No License found for Tengah/JDBC
    As well as the fact that: No License found for jdbcKona/T3
    Is the 'server name' the name of the machine or 'myserver' ? Could therereally
    be something wrong with the licence file ?
    Thanks for helping !
    Hilmar

  • The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.

    I am just starting the JDEV and trying to start the weblogic server and then I get the following message.
    The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
    Can anybody help me to resolve this issue.

    932013 wrote:
    I am just starting the JDEV and trying to start the weblogic server and then I get the following message.
    The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
    Can anybody help me to resolve this issue.
    Try the WebLogic forum:  WebLogic Server - General

  • The Server Instance cannot be started because the Integrated Weblogic domai

    I am newbie to Jdeveloper .When i try to run my jsp file it gives me this error....
    The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
    and the log file shows..
    Log File: C:\Users\Jignesh\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\o.j2ee.adrs\CreateDefaultDomain.log
    Label: JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536
    Product Home: C:\Oracle\Middleware\jdeveloper\jdev\
    Domain: C:\Users\Jignesh\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain
    "C:\Oracle\Middleware\oracle_common\common\bin\wlst.cmd" "C:\Users\Jignesh\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\o.j2ee.adrs\CreateDefaultDomain.py"
    Process started
    wlst > The system cannot find the path specified.
    Elapsed time: 293 ms

    Before you delete the full system directory you try deleting just this one:
    C:\Users\Jignesh\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain
    and restart JDev
    If this doesn't help then delete the C:\Users\Jignesh\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\ and restart

  • Server Instance cannot be started because the Integrated WebLogic domain was not built successfully

    Hi,
    I am using a Linux X64 and running JDeveloper 11g R2, J2EE Edition Version 11.1.2.1.0.
    I am having an error when i Run my JSP Page. It says:
    The Server Instance cannot be started because the Integrated WebLogic domain was not built successfully.
    Error log:
    Jan 31, 2012 1:39:44 AM oracle.security.jps.util.JpsUtil disableAudit
    INFO: JpsUtil: isAuditDisabled set to true
    Compiling...
    Nothing to build.
    [1:39:59 AM] Appc compilation begin
    Compiling out of process...
    /usr/java/jdk1.7.0_02/jre/bin/java -Xms128m -Xmx512m -Xverify:none -client -classpath /usr/java/jdk1.7.0_02/lib/tools.jar:/scratch/tchoudhu/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.jsp.diagnosticWithAbsolutePath=true -Dweblogic.classloader.noJarSigners=true weblogic.appc "@/tmp/appcCommandList157371966291066996.txt"
    [1:40:01 AM] Appc compilation end
    [1:40:01 AM] Successful compilation: 0 errors, 0 warnings.
    [Application Test_Project1Application is bound to Server Instance IntegratedWebLogicServer]
    [Starting Server Instance IntegratedWebLogicServer]
    #### Server Instance IntegratedWebLogicServer could not be started: Error starting Server Instance.
    Compiling...
    Nothing to build.
    [2:12:30 AM] Appc compilation begin
    Compiling out of process...
    /usr/java/jdk1.7.0_02/jre/bin/java -Xms128m -Xmx512m -Xverify:none -client -classpath /usr/java/jdk1.7.0_02/lib/tools.jar:/scratch/tchoudhu/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.jsp.diagnosticWithAbsolutePath=true -Dweblogic.classloader.noJarSigners=true weblogic.appc "@/tmp/appcCommandList3807439261747014006.txt"
    [2:12:32 AM] Appc compilation end
    [2:12:32 AM] Successful compilation: 0 errors, 0 warnings.
    [Application Test_Project1Application is bound to Server Instance IntegratedWebLogicServer]
    [Starting Server Instance IntegratedWebLogicServer]
    #### Server Instance IntegratedWebLogicServer could not be started: Error starting Server Instance.
    Compiling...
    Nothing to build.
    [2:48:14 AM] Appc compilation begin
    Compiling out of process...
    /usr/java/jdk1.7.0_02/jre/bin/java -Xms128m -Xmx512m -Xverify:none -client -classpath /usr/java/jdk1.7.0_02/lib/tools.jar:/scratch/tchoudhu/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.jsp.diagnosticWithAbsolutePath=true -Dweblogic.classloader.noJarSigners=true weblogic.appc "@/tmp/appcCommandList2888192197450875810.txt"
    [2:48:16 AM] Appc compilation end
    [2:48:16 AM] Successful compilation: 0 errors, 0 warnings.
    [Application Test_Project1Application is bound to Server Instance IntegratedWebLogicServer]
    [Starting Server Instance IntegratedWebLogicServer]
    #### Server Instance IntegratedWebLogicServer could not be started: Error starting Server Instance.
    I am new to JDev. Can someone please help me with this?

    Use a supported JDK (1.6.something, not 1.7) is what the original poster didn't do.

  • Server Instance cannot be started because the Integrated Weblogic domain

    Hi All,
    I am using new version of Jdeveloper . i.e 11.1.1.6.0. I am getting "The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully." error whenever i am trying to run a simple jspx page.
    Please anyone help me out.

    Hi,
    Welcome to OTN.
    Can you try the following.
    1. Close JDev.
    2. Remove the DefaultDomain folder under your [url http://tompeez.wordpress.com/tag/system-folder/]System Folder.
    3. Start JDev
    4. Run your jspx page.
    -Arun

  • Failed to start Oracle Weblogic Server node in 11g

    Hello friends,
    I have a problem starting the Weblogic Server node Oracle 11g (10.3.5).
    Any suggestions to solve the problem
    Logs----------------------------------------------------------------------------------
    <Nov 3, 2011 12:33:03 PM> <INFO> <NodeManager> <Server output log file is '/opt/middleware/user_projects/domains/DomainOWL/servers/Server01/logs/Server01.out'>
    <Nov 3, 2011 12:33:07 PM PET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Nov 3, 2011 12:33:07 PM PET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Nov 3, 2011 12:33:11 PM PET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 19.1-b02 from Sun Microsystems Inc.>
    <Nov 3, 2011 12:33:18 PM PET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Nov 3, 2011 12:33:24 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 3, 2011 12:33:24 PM PET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Nov 3, 2011 12:33:25 PM PET> <Notice> <Log Management> <BEA-170019> <The server log file /opt/middleware/user_projects/domains/DomainOWL/servers/Server01/logs/Server01.log is opened. All server side log events will be written to this file.>
    <Nov 3, 2011 12:33:25 PM PET> <Warning> <NodeManager> <BEA-300043> <Node manager native library not found - server process id not saved.>
    <Nov 3, 2011 12:33:26 PM PET> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that a native performance library is in: '"/opt/jdk1.6.0/jre/lib/sparcv9/server:/opt/jdk1.6.0/jre/lib/sparcv9:/opt/jdk1.6.0/jre/../lib/sparcv9:/opt/middleware/patch_wls1035/profiles/default/native:/opt/middleware/patch_ocp360/profiles/default/native:/opt/middleware/wlserver_10.3/server/native/solaris/sparc64:/opt/middleware/wlserver_10.3/server/native/solaris/sparc64:/opt/middleware/wlserver_10.3/server/native/solaris/sparc64/oci920_8:/usr/jdk/packages/lib/sparcv9:/lib/64:/usr/lib/64"'
    >
    <Nov 3, 2011 12:33:37 PM PET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Nov 3, 2011 12:33:40 PM PET> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server01" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Nov 3, 2011 12:33:49 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Nov 3, 2011 12:33:49 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 3, 2011 12:33:56 PM PET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Nov 3, 2011 12:33:56 PM PET> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Nov 3, 2011 12:33:56 PM PET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of oimClusterT.>
    <Nov 3, 2011 12:34:26 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Nov 3, 2011 12:34:27 PM PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Nov 3, 2011 12:34:27 PM PET> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
    <Nov 3, 2011 12:34:31 PM PET> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file /opt/middleware/wlserver_10.3/server/lib/DemoIdentity.jks.>
    <Nov 3, 2011 12:34:31 PM PET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/middleware/wlserver_10.3/server/lib/DemoTrust.jks.>
    <Nov 3, 2011 12:34:31 PM PET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jdk1.6.0/jre/lib/security/cacerts.>
    <Nov 3, 2011 12:34:33 PM PET> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
    Version: V3
    Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: SunPKCS11-Solaris RSA public key, 512 bits (id 58638024, session object)
    modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
    public exponent: 65537
    Validity: [From: Thu Mar 21 15:12:27 PET 2002,
                   To: Tue Mar 22 15:12:27 PET 2022]
    Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
    SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]
    Certificate Extensions: 1
    [1]: ObjectId: 2.5.29.15 Criticality=true
    KeyUsage [
    Key_CertSign
    Algorithm: [MD5withRSA]
    Signature:
    0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
    0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
    0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
    0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
    ] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
    <Nov 3, 2011 12:34:33 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:33 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.1.10:7006 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.1.10:7005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Nov 3, 2011 12:34:34 PM PET> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "Server01" for domain "DomainOWL" running in Production Mode>
    Exception in thread "[STANDBY] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
         at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
         at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
         at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
         at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:217)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Exception in thread "[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 3, 2011 12:36:27 PM PET> <Error> <HTTP> <BEA-101020> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Servlet failed with Exception
    java.lang.OutOfMemoryError: PermGen space
    >
    Exception in thread "[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "Timer-1" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 3, 2011 12:36:53 PM PET> <Error> <HTTP> <BEA-101020> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Servlet failed with Exception
    java.lang.OutOfMemoryError: PermGen space
    >
    <Nov 3, 2011 12:36:24 PM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
    java.lang.OutOfMemoryError: PermGen space.
    java.lang.OutOfMemoryError: PermGen space
    >
    <Nov 3, 2011 12:36:33 PM PET> <Error> <JMX> <BEA-149501> <An exception occurred while registering the MBean com.bea:Name=idmAdminServerT,Type=Server at property WebService.
    java.lang.OutOfMemoryError: PermGen space
    >
    Exception in thread "[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 3, 2011 12:37:16 PM PET> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
    Exception in thread "[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 3, 2011 12:39:41 PM PET> <Error> <HTTP> <BEA-101216> <Servlet: "CoordinatorPortTypeServlethttp" failed to preload on startup in Web application: "wls-wsat.war".
    java.lang.OutOfMemoryError: PermGen space
    >
    <Nov 3, 2011 12:42:32 PM PET> <Error> <HTTP> <BEA-101017> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
    java.lang.OutOfMemoryError: PermGen space
    >
    <Nov 3, 2011 12:43:15 PM PET> <Error> <HTTP> <BEA-101017> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
    java.lang.OutOfMemoryError: PermGen space
    >
    <Nov 3, 2011 12:43:26 PM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
    java.lang.OutOfMemoryError: PermGen space.
    java.lang.OutOfMemoryError: PermGen space
    >
    Exception in thread "[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 3, 2011 12:45:53 PM PET> <Error> <HTTP> <BEA-101017> <[ServletContext@15375304[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
    java.lang.OutOfMemoryError: PermGen space
    >
    Exception in thread "[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "weblogic.timers.TimerThread" java.lang.OutOfMemoryError: PermGen space
    Thanks

    <Nov 4, 2011 11:42:08 AM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
    java.lang.OutOfMemoryError: PermGen space.
    java.lang.OutOfMemoryError: PermGen space
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
         at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
         at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
         Truncated. see log file for complete stacktrace
    >
    <Nov 4, 2011 11:42:34 AM PET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
         at java.lang.Class.getDeclaredMethods0(Native Method)
         at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
         at java.lang.Class.getDeclaredMethod(Class.java:1935)
         at java.io.ObjectStreamClass.getInheritableMethod(ObjectStreamClass.java:1349)
         at java.io.ObjectStreamClass.access$2200(ObjectStreamClass.java:52)
         Truncated. see log file for complete stacktrace
    >
    The WebLogic Server encountered a critical failure
    Reason: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 4, 2011 11:44:08 AM PET> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
    Exception in thread "[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    <Nov 4, 2011 11:44:43 AM PET> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
    java.lang.OutOfMemoryError: PermGen space.
    java.lang.OutOfMemoryError: PermGen space
    I made the change and continue with the same problem, you can tell me which file should make this change, very grateful

  • Not able to start the weblogic admin server

    Hi,
    I am getting the error while starting the weblogic admin server of OAM console.
    Below is the stack trace of the error
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834234> <BEA-000000> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834387> <BEA-000000> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834847> <BEA-000000> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
    ####<Sep 18, 2013 4:47:15 AM IST> <Info> <Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459835526> <BEA-000000> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    ####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the username attribute value of {AES}MCSBg4hMfpsECc7LXYV6gR52kLO5DHUWyo9I1UZXMaE= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    ####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the password attribute value of {AES}1hgzo9/RGaCoWQyFXIJEbYMqmz5gg9LQzjQ/J6DxbQM= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849081> <BEA-000000> <Server state changed to STARTING>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WorkManager> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849088> <BEA-000000> <Initializing self-tuning thread pool>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849138> <BEA-000000> <WebLogic Server "AdminServer" version:
    WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050  Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849208> <BEA-170019> <The server log file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849213> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Diagnostics> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849260> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "http" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "https" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849310> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849311> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849313> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <RJVM> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849325> <BEA-000570> <Network Configuration for Channel "AdminServer"
    Listen Address :7003
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 18, 2013 4:47:29 AM IST> <Critical> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849347> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
    java.lang.AssertionError: java.lang.reflect.InvocationTargetException
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
      at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
      at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
      at java.security.AccessController.doPrivileged(Native Method)
      at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      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.reflect.InvocationTargetException
      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:597)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
      at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
      at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
      at java.security.AccessController.doPrivileged(Native Method)
      at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      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: weblogic.security.internal.encryption.EncryptionServiceException
      at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
      at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
      at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
      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:597)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
      at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
      at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
      at java.security.AccessController.doPrivileged(Native Method)
      at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      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)
    >
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000365> <Server state changed to FAILED>
    ####<Sep 18, 2013 4:47:29 AM IST> <Error> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849411> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849412> <BEA-000236> <Stopping execute threads.>
    Kindly help me to solve this issue.
    Is anyone had faced this issue.....

    Hi,
    I had tried by putting the username and password in boot.properties but we are getting the same issue.
    we tried by editing the config.xml file of the domain.
    i.e. by
    Before:      <credential-encrypted>{AES}b3I7UhWtRyj4DuKMIDVtW4Ln2nzH+HiYRhhQw1H2qpU0qJMOaDlK8iFZ+LvlJu+iZs6pptFJgWz8ryyudL1Zyvf00Rg11z9Iib7hoDC8covMFuig8wx7iOGK88zeKH7U</credential-encrypted>
    After: <credential-encrypted>MyCredentialInPlainText</credential-encrypted>
    and restarted the admin server but shows the same error.
    kindly suggest us...

  • Problem starting managed server in cluster (The name of the managed server is same as admin server)

              We have the following setup.
              CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
              administrator. We start CLUSTER3 as a self-managed server and then try and start
              CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
              1 and 2 we get the following:
              D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
              03:7001
              D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
              D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              D:\bea\wlserver6.1>echo off
              * To start WebLogic Server, use the password *
              * assigned to the system user. The system *
              * username and password must also be used to *
              * access the WebLogic Server console from a web *
              * browser. *
              D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
              ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
              ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
              -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
              "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
              r
              <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
              Enter password to boot WebLogic server:
              Starting WebLogic Server ....
              Connecting to http://10.0.1.103:7001...
              The WebLogic Server did not start up properly.
              Exception raised: weblogic.management.configuration.ConfigurationException: The
              name of the managed server is same as admin server. The managed server will not
              be allowed to start up.
              weblogic.management.configuration.ConfigurationException: The name of the manage
              d server is same as admin server. The managed server will not be allowed to star
              t up.
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              D:\bea\wlserver6.1>goto finish
              D:\bea\wlserver6.1>cd config\CLUSTER1
              D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
              D:\bea\wlserver6.1\config\CLUSTER1>
              Many thanks in advance,
              Alex Burton
              http://www.e-plus.com.au/
              

    Don't start the admin server as managed. Removing
              -Dweblogic.management.server...
              from the command line should help.
              Alex Burton wrote:
              > We have the following setup.
              > CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
              > administrator. We start CLUSTER3 as a self-managed server and then try and start
              > CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
              > 1 and 2 we get the following:
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
              > 03:7001
              >
              > D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
              >
              > D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              >
              > D:\bea\wlserver6.1>echo off
              >
              > ***************************************************
              > * To start WebLogic Server, use the password *
              > * assigned to the system user. The system *
              > * username and password must also be used to *
              > * access the WebLogic Server console from a web *
              > * browser. *
              > ***************************************************
              >
              > D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
              > ".
              > ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
              > ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
              > -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
              > "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
              > r
              > <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
              > Enter password to boot WebLogic server:
              > Starting WebLogic Server ....
              > Connecting to http://10.0.1.103:7001...
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised: weblogic.management.configuration.ConfigurationException: The
              > name of the managed server is same as admin server. The managed server will not
              > be allowed to start up.
              > weblogic.management.configuration.ConfigurationException: The name of the manage
              > d server is same as admin server. The managed server will not be allowed to star
              > t up.
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > Reason: Fatal initialization exception
              > ***************************************************************************
              >
              > D:\bea\wlserver6.1>goto finish
              >
              > D:\bea\wlserver6.1>cd config\CLUSTER1
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>
              >
              > Many thanks in advance,
              > Alex Burton
              > http://www.e-plus.com.au/
              

  • JMS messages stuck in queue in weblogic v923 cluster

    Hi all,
    Enviornment details:
    In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
    There are 3 JMS queues and 1 error queue per managed node.
    All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
    High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
    The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
    The application exceptions are logged to a database table for futher reference.
    The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
    If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
    The auto_ack is true on the JMS message.
    It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
    99.9% of the time, the reprocessing of the messages from the error queue is a success.
    Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
    Problem:
    1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
    1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
    As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
    It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
    Any pointers/input is highly appreciated.
    Thanks in advance for your valuable input and time.

    Off the top of my head, I can only think of two reasons why a message might move from node to node:
    (A) An application is dequeueing them and enquening them elsewhere.
    (B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
    Regards,
    Tom

  • WLST and WebLogic Integration

    Hi all,
    I have installed WebLogic Integration 8.5 bundle. Meaning i have also installed weblogic server 8.1. on Windows XP
    I am now trying to use Weblogic Scripting Tool WLST. But there is no tools on the menu(tools->weblogic scripting tool) this was added in the 9.1 installation...
    How do I configure my installation weblogic server 8.1 with WLI8.5 to run WLST?
    after i run setELSEnv.cmd to set the environment. Then i try java weblogic.WLST and the error is "java.lang.NoClassDefFoundError: weblogic/WLST"
    Where are the libs, how do i configure WLST to run.
    I also tried starting the WLST from the 9.1 installation, but it cannot connect to 8.1 installation, tough connecting to 9.1 installation is no problem. If i try i get this error: "weblogic.management.ManagementRuntimeException: java.lang.NoSuchMethodError: isCachable"
    (I installed weblogic 9.1 and there the WLST was installed during installation and all works just fine. unfortenatly my system must run on 8.1->wli8.5)

    Hi
    I am trying to use WLST tool for configuring Weblogic domain in 9.1 OFFLINE.
    I have done with almost all except JTA configuration.
    Can you please give me smaples for the same.
    The following is part iof my script...
    readTemplate('F:/AuctionDoc/Installer/inDomain.jar')
    cd('/JDBCSystemResource/localNonTxPool/JdbcResource/localNonTxPool')
    create('myJdbcDataSourceParams','JDBCDataSourceParams')
    cd('JDBCDataSourceParams/NO_NAME_0')
    set('JNDIName', 'jdbc/NonTxDataSource')
    #JDBC settings and other JMS settings worked
    But the JTA settings dint work
    #=======================================================================================
    # Set JTA timeout
    #=======================================================================================
    cd("/JTA/inInstDomain")
    set("TimeoutSeconds", "1200")
    set("AbandonTimeoutSeconds", "1200")
    I have to do the above OFFLINE.
    I could not locate the JTA folder or any thing related with JTA configuration to do offline using WLST
    Can you please give an example of JTA settings
    Thanks
    Binu

  • When will WebLogic Integration 9.2 Certification will be available?

    Currently it seems only Integration Developer based on WLI 8.1 is available. Since I am using WLI 9.2 not is not suitable.
    Anyone know when BEA plan to have WLI 9.2 certification available

    T C wrote:
    I have also run into the "Run Database Scripts" dialog box after creation of a domain. When I started the domain I got the following error:
    <[Security:090737]An exception occured while getting connection to validate the configuration settings
    va.sql.SQLException: [Security:090735]The DBMS connection was not usable
    I have BEA 9.2 Platform running on Windows 2000 Professional Service pack 3.
    Incidentally, I started pointbase manually (startPointBase.cmd), started PointBase Console (startPointBaseConsole.cmd) in order to execute the SQLAuthenticator.sql script. This all failed because this SQL script refers to tables GROUPS and USERS, which did not exist in my PointBase schema.
    What worked for me was:
    1. Create a new domain, and only select Workshop for WebLogic, WebLogic Portal, and WebLogic Integration options.
    2. Select YES to Customize Environment and Services Settings tab.
    3. Take defaults until the Run Database Scripts dialog box.
    4. On the Run Database Scripts dialog box, run the scripts for p13nDatasource and cgDataSource-nonXA.
    5. Take default on the remaining steps, and after domain creation the "Run Database Scripts" dialog box shouldn't appear, and the domain should start properly.I'm curious though as what would one do if instead of PointBase DB, we use MS SQL 2000,
    for all the relevant databases in an Integration domain? Thanks.
    ---Nam

  • Understanding Weblogic Integration 9.2

    Hi All,
    I am very new to Weblogic Integration and we were asked to make our application use WLI. Our application has many source feeds and we also interface with SAP with Web Services calls. I am totally new to Weblogic Integration and I would appreciate if anyone can point me to the starting point. I want to learn how WLI works and how to write controls etc.
    I downloaded Weblogic platform and tried to follow through the tutorial that Bea provides, but could not find any help. Tried to search for books online but could not find any. Any help regarding resources i.e. books or online "free" tutorials/courses is greatly appreciated.
    Thank you,
    S

    Sarin,
    I have worked on an WLI project,where integration was with SAP.We used iWay adapter to integrate with SAP system.With respect to WLI, you need to learn JPD(Java Process Definition),Data Transformation,XQuery,Event generators,Channel file,need a very good understanding of XSD(Schema Definition).Also you need to work with WLI console(http://localhost:7001/wliconsole),where you can create your business calendars,event generators.The weblogic workshop help would be a good starting point.Again you can find lots of documents at http://www.edocs.bea.com.
    Let me know if you have any specific question.
    Regards
    Bishnu
    Edited by bishnu_kumar at 05/21/2007 1:29 AM

Maybe you are looking for

  • Change field from read only and override calculation based on radio button

    Hi, I have a form in which one of the fields has a simple sum calculation and is set to read only so the user can't change it as it sets a print amount as well. But if one of the radio buttons is ticked there is a chance that the print amount needs c

  • Airplay with Apple TV not what it used to be

    Before iOS 8 I was able to stream from the iphone to Apple TV without using the mirroring toggle. The icon used to show up in the video screen down on the bottom right corner. Ever since the update, its gone and I have to mirror the phone which doesn

  • Extended withholding tax deduction from customer credit

    hi all configured the extended withholding tax for deducting tds from customer credit line items. deduction is required only after the amount accumulation 2500/- (this is also configured) 1.is the recipient type and country is not required for the cu

  • Question about logon screen

    i have this weird problem - i searched the forums but couldnt find any answer - im on 10.7 Lion - sometimes my mac goes into a state where it goes back to the logon screen and i have to enter my password to unlock the mac - this interferes with some

  • BO XI3.1 Client tools connection with SAP BW

    Hello everyone, I have the following challenge: I have an installation with Businessobjects XI 3.1 which connects to SAP netweaver BW. When I use the client tools wich are installed on the server also, I can make a connection to Sap BW in the designe