Managed server start very slowly

Hi All,
We are currently facing issues in starting a managed weblogic server.
We have 2 machines, say MAC1 and MAC2.
MAC1 contains the admin server and 5 managed servers.
MAC2 contains only 5 managed servers with the same name as that of the 5 managed servers which are on MAC1.
We faced some issues starting the managed servers on MAC2.
So we decided to use pack and unpack.
We were able to start the managed servers on MAC2 however each server tooks about 25 minutes to start.
This is some what unexpected behaviour.
I had a look at the logs of one of the managed server.
It appears that its waits most of its time on :
<Log Management> <BEA-170019> <The server log file xyz.log is opened. All server side log events will be written to this file.>
The next log after this appears after about 20 minutes.
So i feel that its stuck reading or writing the logs.
Any pointers!!
Regards,
Stacey.

Hi All,
After taking the thread dumps , I am suspecting the following two threads which might be causing the issue :
"Thread-3" daemon prio=10 tid=0x73939800 nid=0x6784 waiting on condition [0x72530000]
java.lang.Thread.State: WAITING (parking)
     at sun.misc.Unsafe.park(Native Method)
     - parking to wait for <0x76610450> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
     at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1735)
     at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:452)
     at weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:19)
     at weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
     at weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:175)
     at weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java233)
"ExecuteThread: '7' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=0x7391ec00 nid=0x6789 waiting for monitor entry [0x73344000]
java.lang.Thread.State: BLOCKED (on object monitor)
     at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:95)
     - waiting to lock <0x765902f0> (a weblogic.socket.PosixSocketMuxer$1)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Any pointers !!
Regards,
Stacey.

Similar Messages

  • SGD's Apache Start very Slowly

    hello everyone.
    my sgd's Apache start very Slowly, it costs several hours to start _*
    I have been annoyed by that for several weeks.so I reinstall My OS and install SGD.
    but I cannot believe sgd's Apache still start very Slowly.
    my environment:
    OS:Solaris 10 x86
    SGD Version:tta-4.41-907.sol-x86.pkg.gz
    Server: Sun Fire X4100
    Any help would be appreciated
    thank you

    I get the key after I post the message
    It is the same with http://forums.sun.com/thread.jspa?threadID=5341019&tstart=0
    my god!!!
    my several week's time

  • 3.0EA1 is started very slowly.

    SQL Developers started very slowly.
    I install SQL Developer 3 (no JDK included) and I am using it.
    Now both SQL Developers – 2.1.1 and 3 are starting slowly. I tried to change JRE by Java Console with no result.
    Any other application has no such problem.
    Konstantin

    There are lots of things that could be the source of this...let's try a few things:
    First, (assuming you have already tried a restart - if not, do that) quit all the applications you can (try going to Force Quit and checking there too), and find your Activity Viewer application (Spotlight search for it is the easiest thing to do but it's in Applications) and launch that. Select all processes, and then look around to see what the % load on the CPU is - Activity Viewer might be using %5 and everything else will be less, for a total load of 10-20% or so. If that's not true look around and see what is using a lot of CPU.
    Next, look at memory use...you should have at least 10%, preferably more like 20% "Free". Too many applications open can use up memory capacity.
    If the computer still seems slow, test internet speed; my favorite is speakeasy.net/speedtest but there are several others. There's some possibility your ISP is limiting speed. The speed test will tell you if you're actually getting what you pay for, but without knowing what service you have, I can't say what "normal" might be. If that doesn't seem right, you need to speak with your ISP.
    Try those and let us know how the results come out; not much the rest of us can do without a little more in the facts-and-data category.

  • TC backup starts very slowly & stops..."TM cldn't complete bkup to TC. The bkup disk is not available." The TC bkup disk shows up in sys pref with plenty of avail disk space. Suggestions

    TC backup starts very slowly & stops..."TM cldn't complete bkup to TC. The bkup disk is not available." The TC bkup disk shows up in sys pref with plenty of avail disk space. Suggestions?

    The best place to research this would be Time Machine - Troubleshooting, an excellent support document authored by Time Machine guru Pondini.
    See # C19
    http://pondini.org/TM/Troubleshooting.html

  • WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7

    We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
    <Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
    at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
    Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
    Thank You

    Same issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
    <Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            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.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
            at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            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)
    >
    So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
    Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
    Ladislav

  • Weblogic 10.3.5 Managed Server 추가 후 start 할 때 에러 나요...

    Windows 7(로컬 환경)에서 weblogic 10.3.5를 사용하고 있고, 관리자 콘솔(http://localhost:7001/)에서 Managed Server(서버 이름 :test_server)를 등록해주었습니다.
    그리고 배치에 디플로이 할 소스 경로를 체크하고 test_server targetting 한 후 start 했는데 에러가 납니다...ㅠㅠ
    두 가지 방법으로 start 했었는데..
    1. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin>startManagedWebLogic.cmd  test_server http://localhost:8001
    이렇게 입력하면, 로그가 잘 찍히다가
    Enter username to boot WebLogic server: test_name
    이게 표시됩니다. weblogic 처음 설치 할 때 설정한 username(어드민 콘솔 아이디)를 입력하니 password를 입력하라고 나오는게 아니라 아래와 같이 에러가 납니다. ㅠㅠ
    *<Error> <Security> <BEA-090783> <Server is Running in Development Mode and Native Library(terminalio) to read the password securely from commandline is not found.>*
    *<Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>*
    *<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
    두번 째 방법은
    2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic.cmd*
    여기서 startManagedWebLogic.cmd 를 카피하여 startManagedWebLogic_test.cmd 를 만든 후 if "%1"=="" ( 바로 아래
    set SERVER_NAME=test
    set ADMIN_URL=http://localhost:8001
    set WLS_USER=test_name
    set WLS_PW=test_password
    이렇게 만든 후 2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic_test.cmd* 로 Start 하였습니다.
    그러니 아주 크리티컬한 에러가............... ㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠ
    <Critical> <WebLogicServer> <BEA-000362> *<Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already* exists>
    <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    저 에러로그로 구글링을 엄청나게 해봤는데 별다른 성과가 없습니다..
    제발 아시는 분 도와주세요..ㅠㅠ
    글 수정: 889513

  • Weblogic Server does not show managed server started when I used the Windows service to start it.

    I created a windows service to start a managed server and the services was created successfully and stated.  WHen I go to the Weblogic Server Admn console, the server is still showing shutdown.  Whenm I try to start it, it returns with error that the the service is not able to start.  Has anyone ran into anything similar.  I am running on Windows Server 2008R2 and running Weblogic Server 10.3.6 and Fusion Middleware 11.1.6.
    C

    Hi,
    For starting managed server as windows service there is no need of nodemanager .
    Please follow the steps given in the below doc:
    How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
    Thanks,
    Sharmela

  • Managed Server started but reflected as Shutdown in Admin Console

    Hi,
    Our managed server is running as service (but the error log shows it is unable to contact the Admin server, thus running in independence mode). On our admin console, it shows the managed server as shutdown. How can we resolve this issue?
    We have tried to clear all the folders under \servers\<managedserver> except the security folder containing boot.properties. However it kept prompting that invalid username/password has been entered. If we restore the original folders, the managed server was able to startup, although in independence mode. Is it because of some ldap ldift file which we find in the managed server's subfolder? How can we resolve this??
    Please help, as this is a production environment and this issue just suddenly happened. It was running fine earlier

    Hi
    1) 10gR3
    2) The log for managed server shows it is started and running. However, it has the following lines of error:
    ####<Dec 28, 2012 6:43:42 PM SGT> <Emergency> <Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422536> <BEA-141151> <The admin server could not be reached at https://kimprddmapp:9002.>
    ####<Dec 28, 2012 6:43:42 PM SGT> <Info> <Configuration Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422552> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    It is also unable to deploy our application:
    ####<Dec 28, 2012 6:43:51 PM SGT> <Error> <Deployer> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356691431398> <BEA-149205> <Failed to initialize the application 'da' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
    weblogic.management.DeploymentException: Exception occured while downloading files
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         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.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.net.SocketException: Network is unreachable: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:525)
         at java.net.Socket.connect(Socket.java:475)
         at java.net.Socket.<init>(Socket.java:372)
         at java.net.Socket.<init>(Socket.java:273)
         at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:195)
         at javax.net.ssl.impl.SSLSocketImpl.<init>(Unknown Source)
         at javax.net.ssl.impl.SSLSocketFactoryImpl.createSocket(Unknown Source)
         at weblogic.socket.ChannelSSLSocketFactory.createSocket(ChannelSSLSocketFactory.java:78)
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:274)
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:502)
         at weblogic.net.http.HttpsClient.New(HttpsClient.java:566)
         at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:242)
         at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
         at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         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.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Dec 28, 2012 6:43:51 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691431991> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2012 6:43:52 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691432085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    Noticed that on my Admin Server, it has the following error message, could this be the cause? How can I fix it?
    ####<Dec 28, 2012 6:35:45 PM SGT> <Warning> <Security> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356690945499> <BEA-090482> <BAD_CERTIFICATE alert was received from KIMPRDDMAPP.pubnet.sg - 10.206.12.30. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    ####<Dec 28, 2012 6:35:45 PM SGT> <Error> <Console> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <kimdmweblogic> <> <> <1356690945499> <BEA-240003> <Console encountered the following error javax.help.HelpSetException: Could not parse
    Got an IOException ([Security:090477]Certificate chain received from docs.kim.pubnet.sg - 10.206.12.30 was not trusted causing SSL handshake failure.)
    Parsing failed for null
         at javax.help.HelpSet.<init>(HelpSet.java:146)
         at com.bea.help.utils.HelpSetHelper.getExtensionHelpSetMap(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.mergeExtensionHelpSet(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.createHelpSet(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.getHelpSet(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.ensureHelpSet(Unknown Source)
         at jsp_servlet._jsp.__tocview._jspService(__tocview.java:110)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
         at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._console.__nolayout._jspService(__nolayout.java:119)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._console.__twocollayout._jspService(__twocollayout.java:246)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
         at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
         at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
         at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:211)
         at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
         at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    3) Both Admin and managed servers are running on same host

  • Manage Server Start Problem (weblogic.store.io.jdbc.JDBCStoreException)

    I have a problem, when i start manage server.
    Could you please help me about this problem?
    Thanks
    Orhan YENER
    <Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "p13nJMSPersistenceStore" failed to open table "P13N_MESSAGING_WLStore".
    weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "p13nJMSPersistenceStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
    weblogic.store.io.jdbc.JDBCStoreException: open failed
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:37 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSPersistenceStore failed.
    weblogic.management.DeploymentException:
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:37 PM EEST> <Warning> <Store> <BEA-280076> <Database table "PF_PROLIFERATION_WLStore" for store "pfProliferationJMSStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102728280]". Trying to wait for ownership.>
    <Jun 19, 2012 1:45:57 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "pfProliferationJMSStore" in this server is not the owner of database table "PF_PROLIFERATION_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102748300]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=3276936988962983628:timestamp=1340102737578]".>
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "pfProliferationJMSStore" failed to open table "PF_PROLIFERATION_WLStore".
    weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
    weblogic.store.io.jdbc.JDBCStoreException: open failed
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
    weblogic.management.DeploymentException:
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "p13nJMSServer" due to weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server p13nJMSServer: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'p13n-security-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate p13n-security-jms!p13n.security.RDBMSSecurityStoreTopic
            at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
            at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:100)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
            at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel p13nJMSServer has not yet been opened
            at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
            at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
            at weblogic.messaging.kernel.internal.TopicImpl.activate(TopicImpl.java:97)
            at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
            at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:627)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
            at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
            at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
            at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
            at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
            at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
            at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1696)
            at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
            at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1872)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log00054. Log messages will continue to be logged in /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log.>
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerportal. Error - weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
    weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at java.util.zip.ZipFile.open(Native Method)
            at java.util.zip.ZipFile.<init>(ZipFile.java:114)
            at java.util.jar.JarFile.<init>(JarFile.java:133)
            at java.util.jar.JarFile.<init>(JarFile.java:97)
            at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerportal' due to error weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
    weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at java.util.zip.ZipFile.open(Native Method)
            at java.util.zip.ZipFile.<init>(ZipFile.java:114)
            at java.util.jar.JarFile.<init>(JarFile.java:133)
            at java.util.jar.JarFile.<init>(JarFile.java:97)
            at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerstaticweb. Error - weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
            at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
            at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerstaticweb' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
            at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
            at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            Truncated. see log file for complete stacktrace
    >
    >
    <Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jun 19, 2012 1:46:13 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Jun 19, 2012 1:46:14 PM EEST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 172.25.23.238:80 was shutdown.>

    It's the first couple of bits that are key here
    <Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
    It looks to me that your stores are incorrectly configured, targetted or or just simply messed up. First thing I would do here is check the configuration and targetting of the JDBC Stores and make sure that each JMS server is using it own store and database tables. You may find that it's a really simple thing like creating two sets of tables on the same database, but making sure that they have different prefixes ...

  • Starts very slowly, doesn't close, runs in background

    Firefox 3.6 opens very slowly, doesn't close but apparently runs in background prompting to either close it or restart . Have tried disabling several addons, to no avail.
    == This happened ==
    Every time Firefox opened
    == within the past couple weeks

    I've narrowed my problem down by chopping pieces of code until it works, and I think I have it narrowed down to the code that uses FlexGraphing but need to check a bit more...
    It's odd that it works in Flex3 builder though, and there are no errors when I run in as AIR. In fact, the app RUNS, since it is in the task manager, but it won't appear.

  • [SOLVED?] OpenGL apps start very slowly..

    Edit: After running a system update today and rebooting for a different reason everything seems to work again, guess it was a bad package? Strangely, I'm pretty sure the packages that updated were not related to the problem (Just mpd, ncmpc, wine, and orc). Oh well.
    I have an odd problem with OpenGL applications opening very slowly on my laptop. All other applications seem to work fine. My first thought was maybe direct rendering wasn't on, but it is. Oddly even to check that takes a while to run as seen below:
    [jamie@JPC ~]$ time glxinfo | grep direct
    direct rendering: Yes
    GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, GL_EXT_direct_state_access,
    real 1m23.231s
    user 1m23.068s
    sys 0m0.103s
    Strangely once the program actually opens it seems to run fine as evidenced by glxgears:
    [jamie@JPC ~]$ glxgears
    16753 frames in 5.0 seconds = 3350.586 FPS
    17516 frames in 5.0 seconds = 3503.158 FPS
    17828 frames in 5.0 seconds = 3565.519 FPS
    17751 frames in 5.0 seconds = 3550.056 FPS
    I had this problem a few weeks ago as well, but I somehow resolved it with just some tinkering with some conf files. Unfortunately, I can't seem to fix the issue again.
    I noticed this in the FAQ, but it doesn't seem to be my issue (Mainly pointing it out to avoid it as a suggestion). http://wiki.archlinux.org/index.php/FAQ … _at_all.21
    [root@JPC jamie]# cat /etc/rc.conf | grep HOSTNAME=
    HOSTNAME="JPC"
    [root@JPC jamie]# cat /etc/hosts | grep 127.0.0.1
    127.0.0.1 localhost.localdomain localhost JPC
    My kernel is 2.6.34-ARCH, straight from pacman. My video card, if it helps (Nvidia packages I'm using: nvidia 256.35-1 and nvidia-utils 256.35-4):
    [root@JPC jamie]# lspci -v -s 02:00.0
    02:00.0 VGA compatible controller: nVidia Corporation C77 [GeForce 8200M G] (rev a2) (prog-if 00 [VGA controller])
    Subsystem: Hewlett-Packard Company Device 360a
    Flags: bus master, fast devsel, latency 0, IRQ 19
    Memory at c1000000 (32-bit, non-prefetchable) [size=16M]
    Memory at d0000000 (64-bit, prefetchable) [size=256M]
    Memory at c4000000 (64-bit, prefetchable) [size=32M]
    I/O ports at 4000 [size=128]
    [virtual] Expansion ROM at c6000000 [disabled] [size=128K]
    Capabilities: [60] Power Management version 2
    Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
    Kernel driver in use: nvidia
    Kernel modules: nvidia, nouveau, nvidiafb
    My xorg.conf file is generated from nvidia-xconfig with only a few modifications:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 256.35 (buildmeister@builder101) Wed Jun 16 19:25:59 PDT 2010
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    # AC settings:
    Option "RegistryDwords" "PowerMizerLevelAC=0x3"
    # Battery settings:
    Option "RegistryDwords" "PowerMizerLevel=0x3"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    And lastly my /var/log/Xorg.0.log file warnings although they seem irrelevant (There were no errors):
    [jamie@JPC ~]$ cat /var/log/Xorg.0.log | grep "(WW)"
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 114.159] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 114.159] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 114.159] (WW) Disabling Keyboard0
    [ 114.159] (WW) Disabling Mouse0
    [ 114.168] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    On a final note, sorry if any of the stuff I posted is irrelevant, I'm just pretty confused as what the problem could be. If any other info is needed, please let me know. Also, thanks in advance for any help.
    Last edited by GeekyLink (2010-07-17 18:56:31)

    Repairing permissions isn't going to help. If you were having any disk based problem you would want to repair the hard drive, not permissions.
    Try a couple of things:
    1. Boot into Safe Mode by restarting the computer and after the chime press and hold down the SHIFT key until the startup screen appears (gray screen with dark gray Apple logo and spinning gear) then release SHIFT key. You will get a login window that should say Safe Mode. Run Pages without any other software except Activity Monitor and see what happens.
    2. Create a new user account and log out of your normal account and log into the new user account. Do the same as above and see what happens.
    This will help determine if you may have a problem with some third-party item that isn't loaded when in safe mode or if you have a preference file, logfile, or cachefile problem when in the new user account.

  • Portal starts very slowly

    I have 800MB of HTML+DOC+PDF files.
    I tried 2 senarios.
    A. place a webapp with the above files in a directory and start
    WLS6.1sp1, the server started within 2 mins.
    B. place a webapp with the above files in a directory and start stockportal
    WLS6.1sp1 + wlp 4.0 , the server started within 30 mins.
    Question:
    How can I make my startup faster?
    Thanks,

    Terry,
    You should post this to the general WLS groups as it is not a portal issue.
    Try weblogic.developer.interest.application.deployment), perhaps someone
    there can help. I don't have much experience with sites with 800 MB of
    static pages. ;-)
    Sincerely,
    Daniel Selman
    "Terry" <[email protected]> wrote in message
    news:[email protected]...
    >
    We have already written a large bundle of application on wlp4.0 already.We cannot
    afford to migrate everything to wls7.0 and perform regression again withour project
    schedule and budget.
    Can you tell me any method to config wlp4.0 to turn off the 'loading of800MB
    static pages' so as to make the start time faster(about 5 min)?
    Thanks,
    "Daniel Selman" <[email protected]> wrote:
    Terry,
    This is a 7.0 feature:
    http://e-docs.bea.com/wls/docs70/faq/deploy.html
    http://e-docs.bea.com/wls/docs70/config_xml/Application.html
    http://e-docs.bea.com/wls/docs70/programming/deploying.html
    Sincerely,
    Daniel Selman
    "Terry" <[email protected]> wrote in message
    news:[email protected]...
    I 'search' in the wls6.1 doc and cannot find the word 'nostage'.
    I pressed portalDomain->Deployments -> portal ->Configuration and
    cannot
    see
    the word 'stage'.
    Which part of the wls admin console can i turn off the 'stage' feature?
    Thanks,
    "Daniel Selman" <[email protected]> wrote:
    Terry,
    There is probably a difference in the deployment strategy between
    the
    two
    applications/WLS versions. In the console you can choose between
    "stage"
    and
    "no stage", if you chose the "stage" option then WLS will copy yourentire
    application into a staging directory before it is deployed. In 7.0you
    can
    also toggle between two-phase deployment and the 6.x deployment mode.
    Please refer to the WLS documentation for details.
    Sincerely,
    Daniel Selman
    "Terry" <[email protected]> wrote in message
    news:[email protected]...
    I have 800MB of HTML+DOC+PDF files.
    I tried 2 senarios.
    A. place a webapp with the above files in a directory and start
    WLS6.1sp1, the server started within 2 mins.
    B. place a webapp with the above files in a directory and startstockportal
    WLS6.1sp1 + wlp 4.0 , the server started within 30 mins.
    Question:
    How can I make my startup faster?
    Thanks,

  • Process Scheduler start very slowly

    Hi,
    Fscm90, tools 8.50 on Win 2003 DB Oracle 10 g
    PS takes about one hour to start :
    from Tuxedo log
    113150.MYSERVER!BBL.5624.2452.0: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit, Patch Level (none)
    113150.MYSERVER!BBL.5624.2452.0: LIBTUX_CAT:262: INFO: Standard main starting
    113152.MYSERVER!PSMSTPRC.7128.7648.-2: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
    113152.MYSERVER!PSMSTPRC.7128.7648.-2: LIBTUX_CAT:262: INFO: Standard main starting
    113202.MYSERVER!PSDSTSRV.7844.2476.0: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
    113202.MYSERVER!PSDSTSRV.7844.2476.0: LIBTUX_CAT:262: INFO: Standard main starting
    113206.MYSERVER!PSPRCSRV.628.6844.-2: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
    113206.MYSERVER!PSPRCSRV.628.6844.-2: LIBTUX_CAT:262: INFO: Standard main starting
    124223.MYSERVER!PSMONITORSRV.2032.8068.-2: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
    124223.MYSERVER!PSMONITORSRV.2032.8068.-2: LIBTUX_CAT:262: INFO: Standard main startingAnd :
    From Schedul log :
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](0)    Log Fence is set to 3 = Display detailed message
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3) Validating Application Engine Server Setup....
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)       Processes with Generic Process Type of Application Engine:
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)                XML Publisher            :    3
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)                Optimization Engine      :    2
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)                Total:                        5
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)    CPU Threshold Setting : 0  percent
    PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)    Memory Threshold Setting : 0 percent
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3)   Process Scheduler Server PSNT running in remote mode
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3) Process Scheduler Server PSNT registered
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3)    Server action mode: Initializing
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](2)   PSDaemon disabled
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3)    Checking Process cancels...
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](0)    Server Initialization Complete
    PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](0) Server started
    PSPRCSRV.628 (0) [10/29/10 12:42:37 VP1@MYSERVER](3)    Server: PSNT checking status...No probleme on database. No user connected yet.
    Can not understand.
    Thank for help.

    what are the hardware specifications on the server? When application servers and process schedulers run on the same machine, application servers consume more ram on the server to run the application, process schedulers may not had enough memory to run and wait for application servers on that.
    Having AS and PS on the same box is not a good design. usually PS is made on the db box (or) AS and PS go separately on different boxes.
    if you can move PS onto a different box, ur performance will grow in a big way.
    Thanks!

  • Cap5 starts very slowly

    Hello all!
    I have a very irritating problem when I (try) to open Captivate 5. At the moment it takes more than 10 minutes before I see the welcome screen and again some minutes before I can open or start a project. At 1 of 3 times it doesn't open at all. If I look at the task manager it of course uses more than 130 mb RAM but nothing happens.
    But if I open Captivate in an offline mode (I just close the network connection) I  can start using cap within 20 seconds. So I think the network connection or more the proxy and/or firewall blocks some communication with the adobe server (?). Due to the company policy I cannot modify any settings of firewall or proxy. Does anyone knows a workaround for this (except closing the network connection before each startup)?
    All others parts of the elearning suite are working well, it's only Captivate. Machine information: WinXP, 2GB DualCore, 4 GB RAM, elearning suite 2.
    I really appreciate any hint on this.
    Many thanks,
    Marco

    Hi,
    after nearly one week working only on local files Captivate starts much faster. Now it takes only 1 minute; that's ok for me.
    Many thanks for your tip.
    Best regards,
    Marco

  • My MacBook Pro is brand new but very slow. So disappointing. Why is it starting very slowly?

    My Macbook Pro 13' is brand new however, it does not serve me well compared to my old compaq laptop. It is so annoying and disppointing. I am also a new user of Mac than Windows. There's something going on especially when I am to start up my Mac, it takes so long. Very embarrasing even. Plus, I thought of adding a mcaffee anti-virus thinking it will solve any problem but it gotten worse. Nothing so disppointing like Macbook PRO! can't even uninstall completely the anti-virus. Can someone please assist a beginner in Mac like me? Thank you.

    Have a look here...
    macworld.com/mac-troubleshooting-what-to-do-when-your -computer-is-too-slow.
    theworkingmom2012 wrote:
    ...... anti-virus. ..
    In General 3rd Party AV Software is Not Required as Mac OS X tends to look after itself.
    Read Here  > https://discussions.apple.com/thread/4545776?tstart=0
    See Here  >  Antivirus Discussion
    The Safe Mac  >  http://www.thesafemac.com/mmg/
    theworkingmom2012 wrote:
    My Macbook Pro 13' is brand new
    If necessary.. Contact AppleCare.
    You have 90 days Free Telephone Support... 3 Years if you Purchases the AppleCare protection Plan.

Maybe you are looking for