Deployment from a single BEA server to a cluster

Hi,
          We have developed a Web application on a single BEA server while we
          want to deploy the Web application on a cluster of 3 servers.
          1. Do you think we will need to change the code? since we have
          referenced the single server port in our code/properties files.
          2. Can I configure the single server as an admin server in a cluster.
          3. Would appreciate pointers to documentation.
          Thanks,
          

Hi Ethan,
          As for source code changes, it depends on your app. We often do this type of
          consulting on clustering with Weblogic, and the common problems that we've
          seen are:
          --> session attributes must be serializable
          --> code that relies on globals (such as static fields or servlet context
          attributes)
          --> web processing that is not idempotent (makes seamless failover
          impossible)
          --> code that assumes the app server is the exposed address (i.e. the user
          types "http://www.myco.com" but that is just the address of the proxy -- the
          app server is hidden maybe inside a firewall on a machine whose name isn't
          visible to the end users)
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "Ethan" <[email protected]> wrote in message
          news:[email protected]..
          > Hi,
          >
          > We have developed a Web application on a single BEA server while we
          > want to deploy the Web application on a cluster of 3 servers.
          > 1. Do you think we will need to change the code? since we have
          > referenced the single server port in our code/properties files.
          > 2. Can I configure the single server as an admin server in a cluster.
          > 3. Would appreciate pointers to documentation.
          >
          > Thanks,
          

Similar Messages

  • Accessing many databases with HTML DB from a single Apache Server

    Hello;
    I am planning the install of 10g and HTML DB on a HPUX server with many databases running out of many Oracle Homes 9.2.0, 9.0.1 and 8.1.7. I will be upgrading a number of the existing databases to 10g and want to access them with HTML DB.
    My question is how can I install HTML DB on many databases and use a single Apache Server to access them?

    Where would I find the DADs? a default installation of htmldb puts the modplsql DAD, "pls/htmldb", in a marvel.conf file located in $OHS_HOME/Apache/modplsql/conf/marvel.conf
    What would the URLs look like? not sure what you're asking. if you're asking about how the change in DAD's would affect the URLs you're calling, though, you should consider looking over the OHS (oracle http server) doc some more before making these types of customizations.
    And how would I install the HTML DB in the different databases?
    Would I use the installer or scripts?the only supported way to install htmldb is via the 10g Companion CD. just use that installer to point to your different db's.
    regards,
    raj

  • Error Connecting or Deploying from JDEV to BPEL Server

    Hi,
    I am using BPEL PM 10.1.2 installed on a UNIX box.
    I am unable to connect from JDEV to the BPEL server installed in a UNIX server. I get the following error when trying to test the connection
    org.apache.soap.SOAPException:Unsupported response content type "text/plain", must be: "text/xml". Response was:
    <html><head><title>Error instantiating web-application</title></head><bodyError instantiating web-application
    No application named &apos;hw_services&apos; found in the server<br>
    java.lang.InstantiationException: No application named &apos;hw_services&apos; found in the server<br>     at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:705)<br>     at com.evermind.server.http.HttpSite.getApplication(HttpSite.java:426)<br>     at com.evermind.server.http.AJPRequestHandler.initAJP(AJPRequestHandler.java:694)<br>     at com.evermind.server.http.AJPRequestHandler.initRequest(AJPRequestHandler.java:430)<br>     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:188)<br>     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:127)<br>     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)<br>     at java.lang.Thread.run(Thread.java:534)<br>
    </body></html>
    This has been working fine until recently.
    I am still able to test processes from the BPEL console.
    Please let me know if anyone has come across this error earlier.

    Hi,
    change the named connection in JDeveloper to not use localhost reference but the data server host reference. The data sources are created from the available named connections.Alternatively you can switch off the automatic datasource creation in Jdeveloper and create them manually
    Frank

  • Deploying pinned service to Managed Server in a cluster

    Hi:
              WLS8.1 SP4
              I have a cluster of 4 managed servers.
              I deploy a pinned service (in an EAR) to one of the cluster members.
              Usign weblogic.Deployer:
              weblogic.Deployer -adminUrl .. -name ExampleMDB -nostage -source c:\...\ExampleMDB.ear -deploy
              The EAR seems to be targetted at all other 3 servers, and fails in prep for those other servers.
              I also get this error if i use STAGE.
              I suspect that it has something to do with deploying a pinned EAR to a clustered server.
              If I frig config.xml (bypass Deployer or console), and restart the servers, it is deployed fine.
              Any comments apprec.
              g.

    Hi Rob,
              Yes, I targetted the EAR at the 1 managed server:
              -targets WLS05
              weblogic.Deployer -name ExampleMDB -nostage -source ... -targets WLS05 -deploy
              When i last tried this, the console reported success. However, when I checked config.xml, EXAMPLEMDB.ear was targetted at WLS05 and WLS08. When I saw this discrepancy, I raised a case with support.
              I noticed in the release notes for SP4 that there were some resolved issues with cluster deployment when given less info than I have given. I'll update this thread with the support results.
              g.

  • Migrating single file server to failover cluster file server

    Hi,
    Currently we have one file server which is our Domain controller also. File Server data stored in SAN storage lun. Users home folders also resides at file server.Now we want to create 2 node failover cluster file server.
    Questions:
    1)Can we assign same storage lun to failover cluster?
    2)Do we need to assign all permissions and storage quota again?
    What is the best option to achieve this goal.                                                                            

    Hi,
    if you attach the same LUN to the failover cluster the NTFS permission (security tab) are retained because they are stored in the LUN itself
    Share permission are lost because they are stored in the registry of the file server. If you have few share with a simple share permission structure, simply recreate them in the cluster. If you have a lot of shares and complex permission tree, you have to
    export registry hives related to lanmanserver\shares

  • Deploy to single managed server checked and greyed out while performing upgrade to EPM 11.1.2.4

    Hi Gurus,
    We are trying to upgrade EPM from 11.1.2.2 to EPM 11.1.2.4 and have applied the maintenance release successfully.
    Issue:
    When we are trying to configure EPM 11.1.2.4 and are providing the same Shared Service database details, at the summary screen, we are not able to uncheck the option "Deploy to Single Managed server" which is checked and is greyed out.
    We have tried the following:
    1. We updated the HSS_COMPONENT_PROPERTY_VALUE table  and updated the PROPERTY_NAME "isCompact" to false.
    2. Modified the config.xml file located at EPMSystem/config and epmsystem1/config to remove the property for compactState.
    We are still having the issue where we are not able to uncheck the option for Compact Deployment. Any help would be appreciated.
    Thanks in advance.

    As it is a maintenance release and it deployed as a single managed server then you will not be able to change the deployment type when applying the maintenance release.
    There is a procedure to change a deployment type from compact to single managed server that I created as an internal document.
    you may want to give it a go but you would need to test this first as this was an in house test that I carried out.
    Hyperion Planning - Version 11.1.2.2.300 and later
    Information in this document applies to any platform.
    Goal
    The scenario:
    EPM system 11.1.2.3 was configured and deployed as a single managed server compact deployment so that only one JVM was used for all products EPMServer0.
    Later on, due to performance issues, the decision was made to go for using a JVM for each product and get rid of the compact deployment.
    The administrator went ahead and redeployed the application servers individually into their own JVM.
    However everytime the webserver is reconfigured, the weblogicCluster entry in the OHS file mod_wl_ohs has 2 servers, one for EPMSserver running on port 9000 and another server running on the product default port (as if it was being load balanced)
    The aim:
    It is clear that initial compact deployment has not been cleared from the EPM environment and the aim in this exercise is to clear the registry and the file system so that the compact deployment is removed fromthe EPMenvironment and we are left with the desired configuration Single JVM deployment for earch web application.
    Solution
    Caution:
    Make sure that you take a backup of the following:
    - TheFoundation Services database schema backup
    - Take a backup of the following folders:
    \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
    \Oracle\Middleware\user_projects\domains\EPMSystem\servers
    \Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
    Disclaimer:
    This was tested in House and it worked for this specific environment and it may not work for your environment. So the suggestion is to test first in a development environment and make sure that you take the appropriate backups in case it does not go according to plan.
    Use at your own discretion.
    Procedure:
    1- Run the epmsys_registry to generate the Registry report
    2- Search through the report for the word applicationServerDeployment with a corresponding value of configured and take the ObjectID number down for any entry of applicationServerDeployment that has a value of Configured
    i.e:
    Instance Tasks Configuration (INSTANCE_TASKS_CONFIGURATION)
    Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7adf
    3- use the object ID of each entry you have taken down throughout the Registry HTML Report to manually set it back to Pending using the following procedure:
                    Start a command prompt and set the working directory to
                     \Oracle\Middleware\user_projects\epmsystem1\bin
                    run the command:
                     epmsys_registry.bat updateproperty #e4b3a86a82c26941S32ef81a1455fe48473S7adf/@applicationServerDeployment=Pending
                    Repeat this command for each ObjectID that has its applicationServerDeployment
                     property set to Configured
    4- rerun the epmsys_registry.bat to generate the Registry HTML report and search for applicationServerDeployment in the newly generated report to make sure that they are all set to Pending and there none missed (very Important).
    5- Search the registry HTML report this time for EPMServer0 which is the default serverName given to the single managed server deployment (there will be multiple entries)
    Take note of the first ObjectID entry in the section header: for example
    WORKSPACE_WEBAPP (WORKSPACE_WEBAPP)
    Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Start a command prompt and set the working directory to
                     \Oracle\Middleware\user_projects\epmsystem1\bin
    - run the command:
                     epmsys_registry.bat view #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    -Note the Parents ID in the output:
    For example:
    Parent 1
    NAME -  WORKSPACE_LWA
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    TYPE -  LOGICAL_WEB_APP
    Parent 2
    NAME -  HOST:BACHVMPS3TR
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7ffe
    TYPE -  HOST
    - Note the single child ID:
    For Example:
    Child 1
    NAME -  WebLogic 10
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7fd6
    TYPE -  APP_SERVER
    Now run the following command to remove the Link between Parent and child:
    epmsys_registry removelink #parentObjectID #childObjectID
    In this example that would translate to:
    To remove the single child1 link to the WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ):
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd3 #e4b3a86a82c26941S32ef81a1455fe48473S7fd6
    And do the following To remove the link between WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ) and Parent1 and Parent2:
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7ffe
    #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Now that the link has been removed, delete the WORKSPACE_WEBAPP component using its ObjectID :
    epmsys_registry deletecomponent #parentObjectID
    In this example:
    epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Delete also the Parent representing the WORKSPACE_LWA
    epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    Note:So we have now deleted the WEBAPP and LWA for workspace.
    6- Repeat steps in section No 5 for every WEBAPP with EPMServer0
    7- Start the Weblogic admin console and login
    Then go to the left panel and Expand Environment -> Server
    Click on Lock & Edit -> Select EPMServer0 -> click on Delete and confirm
    Activate Changes and Log off
    8- Stop the weblogic admin console server
    9- Go to the following location and delete the folder EPMServer0:
    \Oracle\Middleware\user_projects\domains\EPMSystem\servers
    Delete also EPMServer0 from the following location:
    \Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
    10- Start a command prompt and delete the Windows service that was created for EPMServer0 (if using Microsoft Windows Operating System):
    Right click on the service 'OracleHyperion EPM Server - Java Web Application (epmssystem1)' and get its service name i.e: HyS9EPMServer_FOUNDATION1
    Run the following command: sc delete HyS9EPMServer_FOUNDATION1
    11- Launch the EPMSystem configurator and redeploy the web application server to their own JVM
    12- Go to the following location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component and rename the file mod_wl_ohs.conf to mod_wl_ohs.conf.old.
    13- Copy the unconfigured mod_wl_ohs.conf file from the location C:\Oracle\Middleware\ohs\ohs\conf to the location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
    14- Run the EPM System Configurator again and configure the WebServer to reconfigure the OHS configuration file mod_wl_ohs.conf.
    Once done then open the mod_wl_ohs.conf file and make sure that there are no servers configured with Port 9000.
    15- Start the services and test the workspace

  • Deploy() and undeploy() for a single managed server do not work properly

    i tried undeploying an application using the following command undeploy('app_name','managed_server1') which in the WebLogic documentation states that this can undeploy the application from the single managed server, but this untargets the application from ALL managed servers.
    Is the command being invoked properly for a single managed server deployment?
    For the deploy() command, the same issue exists but for deployments. It either deploys to a single vm but cannot be later updated to be re-targeted.

    hi,
    Is managed servers are in cluster or stand-alone servers? pls check it properly,if so there is no chance to undeploy the application from all servers even if try to undeploy from onr server.
    regards,
    abhi

  • Deploying adf application to WebLogic Server Version: 10.3.6.0

    hi i have develope application in adf using jdeveloper 11.1.1.6.0 i have deploy the application to weblogic 10.3.6.0
    this is what i have done
    1. i have created a new Managed server in my weblogic=under Environment->Servers
    2.the state of my new server is shutdown
    3.deployment method
    -in my jdeveloper i click application->Application properties->Deployment->new->Archive Type->EAR FILE->applicationName->OK
    TO deploy from jdeveloper to weblogic server
    in my jdeveloper i click application APPLICATION->Deploy->applicationName->Deploy to Application Server-applicationserver i choose the new server i created in my weblogic->weblogic Option->deploy to selected instance->i select the name of the server i created in my weblogic->next->finish
    after that the deployment configuration screen pop up than i click deploy then screen MDS CONFIGURATION invalid pop up with message MDS CONFIGURATION information appear invalid metadata Repository not found in target server.deploy anyway then i click yes
    i got this meaasge in my deployment log
    [08:33:46 AM] Entering Oracle Deployment Plan Editor
    [08:38:56 AM] Deploying Application...
    [08:38:57 AM] [Deployer:149195]Operation 'deploy' on application 'UAMOrganisation' has been deferred since 'UamOrganisation' is unavailable
    [08:38:57 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application UAMOrganisation on UamOrganisation.: .
    [08:38:57 AM] Application Deployed Successfully.
    [08:38:57 AM] Elapsed time for deployment:  5 minutes, 21 seconds
    [08:38:57 AM] ----  Deployment finished.  ----than i go to my weblogic under deployment there i found my deploy application with a state=new and type=Enterprise application
    than i click start->Servircing all request->start application assistance->yes->Start requests have been sent to the selected Deployments.
    but now i what to test my application am geting this Internet Explorer cannot display the webpage,do i need to start my Managed server how do i do that,i try to click server start but it does not start how can i start my new created Managed server
    the listern port of my new created server is 8003
    my problem is am not able to test the application i have deploy
    Edited by: adf009 on 2013/01/30 11:26 AM
    Edited by: adf009 on 2013/01/30 11:39 AM
    Edited by: adf009 on 2013/01/30 11:41 AM
    Edited by: adf009 on 2013/01/30 12:33 PM

    i did this,am in window 7 64 bit
    start startNodeManager.cmd
    C:\Oracle\weblogic\wlserver_10.3\server\bin>set CLASSPATH=.;C:\Oracle\weblogic\p
    atch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracl
    e\weblogic\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.j
    ar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\weblogic\WLSERV~1.3\serve
    r\lib\weblogic_sp.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic.jar;C:\O
    racle\weblogic\modules\features\weblogic.server.modules_10.3.6.0.jar;C:\Oracle\w
    eblogic\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\weblogic\modules\ORGAPA~
    1.1/lib/ant-all.jar;C:\Oracle\weblogic\modules\NETSFA~1.0_1/lib/ant-contrib.jar;
    C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl.jar
    C:\Oracle\weblogic\wlserver_10.3\server\bin>if not "" == "" set CLASSPATH=;.;C:\
    Oracle\weblogic\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_p
    atch.jar;C:\Oracle\weblogic\patch_ocp371\profiles\default\sys_manifest_classpath
    \weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\weblogic
    \WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\
    weblogic.jar;C:\Oracle\weblogic\modules\features\weblogic.server.modules_10.3.6.
    0.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\weblogi
    c\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\weblogic\modules\NETSFA~1.0_1/lib
    /ant-contrib.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl.jar
    C:\Oracle\weblogic\wlserver_10.3\server\bin>if not "C:\Oracle\MIDDLE~1\WLSERV~1.
    1\server\lib\xqrl.jar" == "" set CLASSPATH=.;C:\Oracle\weblogic\patch_wls1036\pr
    ofiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\weblogic\patc
    h_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MI
    DDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic_
    sp.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\weblogic\
    modules\features\weblogic.server.modules_10.3.6.0.jar;C:\Oracle\weblogic\WLSERV~
    1.3\server\lib\webservices.jar;C:\Oracle\weblogic\modules\ORGAPA~1.1/lib/ant-all
    .jar;C:\Oracle\weblogic\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDL
    E~1\WLSERV~1.1\server\lib\xqrl.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl
    .jar
    C:\Oracle\weblogic\wlserver_10.3\server\bin>cd C:\Oracle\weblogic\WLSERV~1.3\com
    mon\NODEMA~1
    C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>if not "" == "" if not "" == "" go
    to runNMWithListenAddressAndPort
    C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
    enAddress
    C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
    enPort
    C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>"C:\Oracle\MIDDLE~1\JDK160~1\bin\j
    ava.exe" -server -Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Dcohere
    nce.home=C:\Oracle\weblogic\COHERE~1.7 -Dbea.home=C:\Oracle\weblogic  -Dweblogic
    .ProductionModeEnabled=true   -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.1
    -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.1\server -Dweblogic.home=C:\Oracle\MIDDLE
    ~1\WLSERV~1.1\server   -Dweblogic.management.discover=true  -Dwlw.iterativeDev=f
    alse -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false "-Djava.security.pol
    icy=C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic.policy" "-Dweblogic.nodema
    nager.javaHome=C:\Oracle\MIDDLE~1\JDK160~1" weblogic.NodeManager -v
    <30 Jan 2013 1:14:37 PM> <INFO> <Loading domains file: C:\Oracle\weblogic\WLSERV
    ~1.3\common\NODEMA~1\nodemanager.domains>
    30 Jan 2013 1:14:37 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
    INFO: Loading domains file: C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1\nodema
    nager.domains
    <30 Jan 2013 1:14:38 PM> <INFO> <Loading identity key store: FileName=C:\Oracle\
    MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
    30 Jan 2013 1:14:38 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig
    INFO: Loading identity key store: FileName=C:\Oracle\MIDDLE~1\WLSERV~1.1\server\
    lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true
    <30 Jan 2013 1:14:38 PM> <SEVERE> <Fatal error in node manager server>
    weblogic.nodemanager.common.ConfigException: Identity key store file not found:
    C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks
            at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
    va:153)
            at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
            at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
            at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
            at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
            at weblogic.NodeManager.main(NodeManager.java:31)
    30 Jan 2013 1:14:38 PM weblogic.nodemanager.server.NMServer main
    SEVERE: Fatal error in node manager server
    weblogic.nodemanager.common.ConfigException: Identity key store file not found:
    C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks
            at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
    va:153)
            at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
            at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
            at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
            at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
            at weblogic.NodeManager.main(NodeManager.java:31)
    C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>goto finish
    C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
    C:\Oracle\weblogic\wlserver_10.3\server\bin>can i test my application without manged server started
    link is http://italianknows.blogspot.com/2011/02/weblogic-1034-ps3-nodemanager-wont.html
    Edited by: adf009 on 2013/01/30 1:43 PM
    Edited by: adf009 on 2013/01/30 1:56 PM
    Edited by: adf009 on 2013/01/30 1:57 PM
    Edited by: adf009 on 2013/01/30 2:14 PM
    Edited by: adf009 on 2013/01/30 2:15 PM
    Edited by: adf009 on 2013/01/30 2:16 PM

  • Windows 8.1 Update - issues deploying printers via GPO from a 2012R2 Print Server

    Hi,
    I am trying to deploy a single printer to Windows 8.1 clients in a K-12 environment. We have about 1200 laptops and about 25% of those laptops are installing the printer. Several different users can log on and the printer may or may not be there. The printer
    is being deployed to the Computer not the User. If the printer was successfully installed shouldn't the printer be available immediately after logging in with different AD accounts? Sometimes it shows up 10mins later as if it needed to install it again. I
    read the changes from v3 to v4 printing in Windows 8, Ive checked the event log errors, printer shares, etc. Deploying Printers to Windows 8.1 clients is poor at best even when it supposed to be easier for IT to manage. Also I was under the impression that
    Windows 8.1 clients do not attempt to downloads drivers from a windows print server anymore as they opt to use a v4 print class driver.
    Environment Details:
    Windows 2012R2 Printer Server all patched, Windows 8.1 all patched, AD users are identical as well as the computers (reside in the same OUs) Printer is deployed to the computers, Point and print restrictions is completely disabled. Restarting the print spooler
    on the client has little to no effect. Computers connect wirelessly to the network and print server is in the same building. Started pushing to the user as well to see if it helps. Windows 7 clients are unaffected and get the printer consistently.
    Errors:
    The print spooler failed to download and import the printer driver from \\Server into the driver store for driver KONICA MINOLTA C652SeriesPS. Error code= 800f0242.
    The print spooler failed to import the printer driver that was downloaded from \\Server\print$\x64\PCC\koazca__.inf_amd64_664b51505681ff6d.cab into the driver store for driver KONICA MINOLTA C652SeriesPS. Error code= 800f0242. This can occur if there is
    a problem with the driver or the digital signature of the driver.
    The default printer was changed to \\Server\Konica_Copier,winspool,Ne05:. See the event user data for context information.

    error from event id 600?
    http://technet.microsoft.com/en-us/library/dd393207(v=ws.10).aspx
    did install this hotfix?
    http://support.microsoft.com/kb/2961042/en-us
    those maybe helpful...
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/4de0cf6f-3e05-4de4-b1f5-349d27b97234/windows-server-2008-r2-trouble-updating-client-kyocera-drivers?forum=winserverprint
    http://download.microsoft.com/download/5/8/1/581A3BB7-503D-48DA-B898-2BF80FA2A7E7/Understand_and_Troubleshoot_Printing_in_Windows_Server_8_Beta.docx
    Best,
    Howtodo

  • HLP:Serving forms in 2 distinct envirs from a single machine

    We would like to set up the forms and report server on a SINGLE
    machine in such a way that the OAS
    can serve forms to 2 distinct groups of users: Developpers and
    production users. Is this
    possible ? If so, how do we do it ?
    For example, say we have a form called 'A' that is used in
    production. Now we have to modify and
    test it in development. We only have 1 physical machine
    available. Is there a way on only ONE
    machine to serve Development form A to developpers and
    production form A to production users ?
    Of course we could have two versions of the forms and report and
    use different names, but this
    solution is not really easy to manage....
    What about the libraries (PLL) and icons (and all other
    attachable objects in FORMS)
    Say I have 2 directories:
    /disk1/dev/forms
    containting FORMA.FMX
    MYLIB.PLL (Used by FORMA) (Actually, my cartridge
    and forms server is set up to use these directories)
    /disk2/prod/forms
    contaning FORMA.FMX (Production version)
    MYLIB.PLL (Used by formA)
    Do I have to set up 2 virtual directories ? 2 different forms
    cartridges. 2 different forms server (on different ports)
    For now, I only deploy in a single environment (DEV). The UNIX
    environement from which I start the FORMS
    server contains stuff like:
    FORMS60_PATH=/disk1/dev/forms
    + setting specific to this environment (TK60_ICON, etc...)
    How do I set it up to run forms in 2 distinct enviroments ?
    What about reports variables (We are using the cartridge as well)
    Thanks
    null

    Thanks wilfred,
    yes I've read that manual. Probably not every single page ;-)
    I agree that High-Availability is a very broad and complex topic, but my question is (although it was difficult to explain what i mean) only on a small part of it:
    I understand that I can have mutiple instances on each level OC4J, HTTP, WEB-Cache, LBR But where or who excepts one single URL and leads the requests to the available AS
    As mentioned in my post before, we may etst the Microsoft NLB-Cluster to divide the requests to the WEB-Cache Instances on the 2 AS and then the 2 Web-Cache proceed to the 2 HTTP and so on.
    The Idea of that is that Windows offers a virtual IP-Adress from those 2 Windows-Server and somehow the requests will be transferred to a running WEB-Cache.
    Does that work correctly with session-Binding ...
    We'll see
    thanks,
    Mark

  • EPM 11.1.2.x deployment to single managed server

    Hi Gurus,
    I have 2 questions:
    1) If we install some applications on single port number:9000(deploy to single managed server), after that if we deploy some applications to individual ports. is this installation work?
    2) for example we have installed and configured all applications to single managed server:9000. Now can we change this to individual port numbers??
    I mean can we configure all application to individual port numbers??
    Just asking with curiosity to know about this scenarios.
    Thanks,
    mady

    Hi Pablo,
    Hope you are doing good. In Starting of Carrer on Hyperion, JohnGoodwin and Your replies on the Forum was very helpful to me.  Nowadays,you are busy i think, and we are not getting more responses from you .
    Pablo wrote:
    If what you're trying to do is deploy everything to 9000, test that and then deploy everything to its own managed server, the answer is yes you can but you need to re-run the OHS configuration at the end everytime as it will need to update the mod_wl_ohs.conf file to update the ports/# of managed servers.
    Pablo
    In the response, Can we get any conflict between services if we do reconfigure to the Own managed server.?
    (why i am asking this question is, at the time of configuration to single managed server, we get EPM Server Service, then some more services only. But if we do reconfigure to the Own managed server, we will get more services in Services.msc)
    I didn't test this yet, just i got this doubt if we do like this what will happens. is it work or not?
    Thanks for your valuable time Pablo.
    Thanks,
    mady

  • Multiple ESS access to single EP server from two backend servers.

    Hi Experts,
    I have one concern regarding ESS.
    Can we do or can we make   two ESS access (R3 server1 and R3 Server2)  from one Portal server.
    I heard  that from one portal server (ESS)  we can connect multiple clients which are from backend R3 (example client 100 and client 200)
    My requirement is  :
    We have two R3 backend servers and one EP(ESS) server.
    Can we access two backend systems from one EP server with Two ESS tabs.
    I am expecting Multiple jco settings, multiple SSo, Multiple SLD, Multiple SPRO Menu settings, UWL settings.
    Multiple service specific settings to be access  by using  single EP server(Multiple ESS Tabs)
    Please help me for doing this.
    Regards
    Kumar.

    yes you can do so As Pooja indicated also refer
    Please have a look  at the Note 596698
    Thanks for clearing that up, Now if I understand the issue
    correctly :
    1 Portal, Two backend R/3 System, This can be done, Now then
    if you dont want the particular application disable that
    r/3 as you are aware that the links appear from V_T7XSSSERRES.
    Here you can also make sure some applications appear or no.
    Accessing multiple Backends in WebDynpro:
    How it can be done?
    1) Define different JCO Destinations
      The logical System names have to be defined in the Web Dynpro Content
    Administrator.
      Different clients or completely different Systems can be accessed
    given that the function modules called exist in those systemsThe logical System to be used can be passed to the Web Dynpro
    Application by using a URL Parameter
      The URL Parameter can be easily maintained in the iView Property when
    using the portal.
    The standard way to handle this is to create copies (via delta-link) of
    all the business package iviews and change the 'System' property in the
    newly created iviews to point to the correct system Alias. From the
    portal point of view this is all that is required in order to point an
    view to a different system
    Refer these links for further information:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.
    docs/library/webas/webdynpro/How%20to%20Use%20the%20Web%20Dynpro%20Conte
    nt%20Administrator.pdf

  • Migrate osb deployment from Admin Server to Managed Server

    Hi,
    I had create the OSB Development environment.
    Configuration was such that OSB was deployed to Admin Server.
    However, I have a new requirement, wish to deploy OSB to a Managed Server and no longer Admin Server, to reduce the load on Admin Server and for future high availability plans.
    I have created a Managed Server for OSB deployment. I was of the opinion that I should just simply use the console for deploying OSB to the newly created Managed Server.
    However, I seemed to have missed some steps and therefore OSB was not working.
    Kindly help me.
    Lammeki

    bobm53 wrote:
    Hi,
    look at this:
    http://www.oracle.com/technetwork/database/migration/sqlserver-095136.html
    About expected results from such db migration, I can only say that because all IDM objects (forms, wf, customizations etc) are stored on its waveset db, at the end of db migration, you should have same functionalities. Obviously you need to change (with lhconsole) the db iDM should refer to. This information is stored in a special (encrypted) xml file.
    HTHAnd don't forget that you also need to replace your JDBC driver (jar file) with the oracle JDBC driver and ensure it is in the classpath that LH and the appserver need.

  • MDT images deploying from wrong server

    So the MDT 2013 server at my office has been deploying Windows 7 images flawlessly for a couple months. I just setup a secondary one at a branch site, on a 1gig imaging VLAN. This VLAN can talk
    to my office's imaging VLAN via 50mbit MPLS for replication.
    Linked deployment shares has been configured on my server to the branch office, and the Replicate Content function completes successfully. However imaging at the branch office server takes NINE
    HOURS, as opposed to a half hour at my office. So it must be pulling the images and applications from my office's server over the 50mbit link. The weird thing is that it gets DHCP IPs and PXE boots from the branch office's WDS server (on same box as MDT).
    I don't see any options to force a branch office PXE client to deploy from the branch office's local MDT server, what I am missing??

    Your boot images (USB or CD or PXE Boot) will have been created from the first Deployment Share. As such they will always point to that share until you update them.
    To test: In WinPE press f8 and type net use to see where the Z: drive is pointing.
    Fix #1: Edit the bootstrap.ini on your new deployment share and ensure it is pointing to your new deployment server. Then use deployment workbench to connect to that share and update your deployment share. This will recreate the boot image (found in the
    boot folder).
    Fix #2: Create a LocationServer.xml file that lists
    all your servers and remove the build server entry from your bootstrap.ini and update your boot disk as above.
    Hope this helps.
    Blog: http://scriptimus.wordpress.com

  • Cant deploy composite application on soa server environment

    hi,
    Both managed server and admin server in running statusl thati could see in weblogic console by selecting servers. But while deploying my composite application i could not find soa server option there. i could sucessfuly established the connection with application server with JDevloper,
    its my soa log file during deployment,
    uildfile: C:\Oracle\Middleware\wls_11gR1\jdeveloper\bin\ant-sca-compile.xml
    scac:
    [scac] Validating composite "E:\purchase\CreditCardValidation\ValidationForCC\composite.xml"
    BUILD SUCCESSFUL
    Total time: 29 seconds
    Deployment log file,
    01:56:38 PM] ---- Deployment started. ----
    [01:56:38 PM] Target platform is (Weblogic 10.3).
    [01:56:38 PM] Running dependency analysis...
    [01:56:38 PM] Building...
    [01:57:00 PM] Deploying profile...
    [01:57:00 PM] Updating revision id for the SOA Project 'ValidationForCC.jpr' to '1.0'..
    [01:57:01 PM] Wrote Archive Module to E:\purchase\CreditCardValidation\ValidationForCC\deploy\sca_ValidationForCC_rev1.0.jar
    [01:57:01 PM] #### Deployment incomplete. ####
    [01:57:01 PM] No SOA configured servers found for deploying the archive file:/E:/purchase/CreditCardValidation/ValidationForCC/deploy/sca_ValidationForCC_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    [01:59:25 PM] ---- Deployment started. ----
    [01:59:25 PM] Target platform is (Weblogic 10.3).
    [01:59:25 PM] Running dependency analysis...
    [01:59:25 PM] Building...
    [01:59:58 PM] Deploying profile...
    [01:59:58 PM] Wrote Archive Module to E:\purchase\CreditCardValidation\ValidationForCC\deploy\sca_ValidationForCC_rev1.0.jar
    [02:00:10 PM] #### Deployment incomplete. ####
    [02:00:10 PM] No SOA configured servers found for deploying the archive file:/E:/purchase/CreditCardValidation/ValidationForCC/deploy/sca_ValidationForCC_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer).
    also included the soa server log file,
    ####<Jul 28, 2010 1:03:30 PM IST> <Info> <WebLogicServer> <skynetmu> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1280302410875> <BEA-000000> <WebLogic Server "soa_server1" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Notice> <Log Management> <skynetmu> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1280302411078> <BEA-170019> <The server log file C:\Oracle\Middleware\home_11gR1\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.log is opened. All server side log events will be written to this file.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Log Management> <skynetmu> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1280302411078> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Diagnostics> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411171> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "http" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "https" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411515> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411546> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411546> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411546> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <RJVM> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411734> <BEA-000570> <Network Configuration for Channel "soa_server1"
    Listen Address          :8001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411937> <BEA-002609> <Channel Service initialized.>
    ####<Jul 28, 2010 1:03:31 PM IST> <Info> <Socket> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302411984> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
    >
    ####<Jul 28, 2010 1:12:12 PM IST> <Info> <Common> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1280302932031> <BEA-000628> <Created "1" resources for pool "SOADataSource", out of which "1" are available and "0" are unavailable.>
    ####<Jul 28, 2010 1:12:23 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302943312> <BEA-149059> <Module weblogic.xml.registry.XMLModule of application DefaultToDoTaskFlow is transitioning from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:12:23 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302943312> <BEA-149060> <Module weblogic.xml.registry.XMLModule of application DefaultToDoTaskFlow successfully transitioned from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:12:23 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302943312> <BEA-149059> <Module empty.jar of application DefaultToDoTaskFlow is transitioning from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:12:23 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302943312> <BEA-149060> <Module empty.jar of application DefaultToDoTaskFlow successfully transitioned from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:12:23 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302943312> <BEA-149059> <Module /DefaultToDoTaskFlow of application DefaultToDoTaskFlow is transitioning from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:12:23 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302943312> <BEA-149060> <Module /DefaultToDoTaskFlow of application DefaultToDoTaskFlow successfully transitioned from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:13:06 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302986203> <BEA-149059> <Module weblogic.xml.registry.XMLModule of application composer is transitioning from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:13:06 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302986250> <BEA-149060> <Module weblogic.xml.registry.XMLModule of application composer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:13:06 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302986250> <BEA-149059> <Module empty.jar of application composer is transitioning from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:13:06 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302986250> <BEA-149060> <Module empty.jar of application composer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:13:06 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302986250> <BEA-149059> <Module soa/composer of application composer is transitioning from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    ####<Jul 28, 2010 1:13:06 PM IST> <Info> <Deployer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1280302986250> <BEA-149060> <Module soa/composer of application composer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server soa_server1.>
    can anyone tell me why i cant view the soa server while deploying my composite application
    regards
    ashok.v

    hi anuj,
    i have tried many times started the soa server as you mentioned , but this time i can view the soa_server1 in unknown status in summary of servers page in weblogic console and then soa server disconnected from the admin server.
    ####<Jul 30, 2010 2:00:25 PM IST> <Notice> <WebLogicServer> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000d> <1280478625718> <BEA-000332> <Started WebLogic Managed Server "soa_server1" for domain "soa_bpm_domain" running in Development Mode>
    ####<Jul 30, 2010 2:00:28 PM IST> <Info> <J2EE> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478628312> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Jul 30, 2010 2:00:30 PM IST> <Info> <WebService> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478630812> <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.>
    ####<Jul 30, 2010 2:00:32 PM IST> <Info> <WebService> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478632203> <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.>
    ####<Jul 30, 2010 2:00:32 PM IST> <Info> <WebService> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478632281> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService 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.>
    ####<Jul 30, 2010 2:00:32 PM IST> <Info> <WebService> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478632437> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms 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.>
    ####<Jul 30, 2010 2:00:32 PM IST> <Info> <WebService> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478632562> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 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.>
    ####<Jul 30, 2010 2:00:32 PM IST> <Info> <WebService> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000c> <1280478632593> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https 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.>
    ####<Jul 30, 2010 2:00:33 PM IST> <Info> <Server> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000e> <1280478633687> <BEA-002635> <The server "AdminServer" connected to this server.>
    ####<Jul 30, 2010 2:00:42 PM IST> <Info> <JMX> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000e> <1280478642843> <BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.1.3:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
    ####<Jul 30, 2010 2:00:59 PM IST> <Info> <Health> <skynetmu> <soa_server1> <weblogic.GCMonitor> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000b> <1280478659843> <BEA-310002> <39% of the total memory in the server is free>
    OraSDPM/Queues/OraSDPMWSRcvQ1.>
    ####<Jul 30, 2010 2:01:26 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478686000> <BEA-010060> <The Message-Driven EJB: PeopleQueryMDB has connected/reconnected to the JMS destination: jms/bpm/PeopleQueryTopic.>
    ####<Jul 30, 2010 2:01:27 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478687109> <BEA-010060> <The Message-Driven EJB: DriverDispatcherBean has connected/reconnected to the JMS destination: OraSDPM/Queues/OraSDPMDriverDefSndQ1.>
    ####<Jul 30, 2010 2:01:29 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478689031> <BEA-010060> <The Message-Driven EJB: NotificationSender has connected/reconnected to the JMS destination: jms/Queue/NotificationSenderQueue.>
    ####<Jul 30, 2010 2:01:31 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478691515> <BEA-010060> <The Message-Driven EJB: TaskNotificationSender has connected/reconnected to the JMS destination: jms/Queue/NotificationSenderQueue.>
    ####<Jul 30, 2010 2:01:32 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478692375> <BEA-010060> <The Message-Driven EJB: MessageDispatcherBean has connected/reconnected to the JMS destination: OraSDPM/Queues/OraSDPMAppDefRcvQ1.>
    ####<Jul 30, 2010 2:01:34 PM IST> <Warning> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478694437> <BEA-010081> <The message-driven bean CubeActionMDB was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
    ####<Jul 30, 2010 2:01:35 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478695093> <BEA-010060> <The Message-Driven EJB: CubeActionMDB has connected/reconnected to the JMS destination: jms/bpm/MeasurementTopic.>
    ####<Jul 30, 2010 2:01:35 PM IST> <Info> <EJB> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000015> <1280478695734> <BEA-010060> <The Message-Driven EJB: BAMActionMDB has connected/reconnected to the JMS destination: jms/bpm/MeasurementTopic.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Info> <JMS> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000018> <1280478696218> <BEA-040010> <JMSServer "BPMJMSServer" configured no session pools.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Info> <JMS> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000018> <1280478696218> <BEA-040109> <JMSServer "BPMJMSServer" is started.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Info> <JMS> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000018> <1280478696218> <BEA-040010> <JMSServer "SOAJMSServer" configured no session pools.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Info> <JMS> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000018> <1280478696250> <BEA-040109> <JMSServer "SOAJMSServer" is started.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Info> <JMS> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000018> <1280478696250> <BEA-040010> <JMSServer "UMSJMSServer_auto_2" configured no session pools.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Info> <JMS> <skynetmu> <soa_server1> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000018> <1280478696296> <BEA-040109> <JMSServer "UMSJMSServer_auto_2" is started.>
    ####<Jul 30, 2010 2:01:36 PM IST> <Notice> <WebLogicServer> <skynetmu> <soa_server1> <main> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000008> <1280478696562> <BEA-000365> <Server state changed to RUNNING>
    ####<Jul 30, 2010 2:01:36 PM IST> <Notice> <WebLogicServer> <skynetmu> <soa_server1> <main> <<WLS Kernel>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000008> <1280478696640> <BEA-000360> <Server started in RUNNING mode>
    ####<Jul 30, 2010 2:01:59 PM IST> <Info> <Health> <skynetmu> <soa_server1> <weblogic.GCMonitor> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000000b> <1280478719843> <BEA-310002> <51% of the total memory in the server is free>
    ####<Jul 30, 2010 2:02:12 PM IST> <Info> <Common> <skynetmu> <soa_server1> <MDSPollingThread-[soa-infra, jdbc/mds/MDS_LocalTxDataSource]> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000001> <1280478732250> <BEA-000628> <Created "1" resources for pool "mds-soa", out of which "1" are available and "0" are unavailable.>
    ####<Jul 30, 2010 2:18:32 PM IST> <Warning> <JDBC> <skynetmu> <soa_server1> <Thread-46> <<anonymous>> <BEA1-02CCF2FFF3E759141385> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000001a> <1280479712562> <BEA-001129> <Received exception while creating connection for pool "mds-owsm": Socket read timed out>
    ####<Jul 30, 2010 2:18:32 PM IST> <Warning> <JDBC> <skynetmu> <soa_server1> <MDSPollingThread-[owsm, jdbc/mds/owsm]> <<anonymous>> <> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-0000000000000003> <1280479712656> <BEA-001129> <Received exception while creating connection for pool "mds-owsm": Socket read timed out>
    ####<Jul 30, 2010 2:18:32 PM IST> <Info> <JDBC> <skynetmu> <soa_server1> <Thread-46> <<anonymous>> <BEA1-02CCF2FFF3E759141385> <871ba2ae9678192d:4dd50b24:12a2272d6a9:-7ffd-000000000000001a> <1280479712937> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: Socket read timed out
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:135)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:203)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:489)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:439)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:640)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:205)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:554)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:327)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:227)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:427)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:322)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:438)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:317)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
         at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:342)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:360)
         at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.fetchConnection(JNDIConnectionManagerImpl.java:91)
         at oracle.mds.internal.persistence.db.ConnectionManager.getConnection(ConnectionManager.java:347)
         at oracle.mds.internal.persistence.db.BaseReposAccess.<init>(BaseReposAccess.java:347)
         at oracle.mds.internal.persistence.db.shredded.ShreddedReposAccess.<init>(ShreddedReposAccess.java:274)
         at oracle.mds.internal.persistence.db.shredded.ShreddedDBMSConnection.createReposAccess(ShreddedDBMSConnection.java:444)
         at oracle.mds.internal.persistence.db.BaseDBMSConnection.getOrCreateReposAccess(BaseDBMSConnection.java:2072)
         at oracle.mds.internal.persistence.db.BaseDBMSCVersionSupport.getDocument(BaseDBMSCVersionSupport.java:286)
         at oracle.mds.persistence.DelegatingMSConnectionVersionSupport.getDocument(DelegatingMSConnectionVersionSupport.java:72)
         at oracle.mds.internal.persistence.PManagerVersionSupportImpl.getDocument(PManagerVersionSupportImpl.java:255)
         at oracle.mds.core.MOState.getTipPDocument(MOState.java:981)
         at oracle.mds.core.MOState.checkStaleVersion(MOState.java:893)
         at oracle.mds.core.MOState.checkStalenessDocFromBuilder(MOState.java:723)
         at oracle.mds.core.MOState.getIsStaleLastModified(MOState.java:537)
         at oracle.mds.core.MOContent.getIsStaleLastModified(MOContent.java:267)
         at oracle.mds.core.MetadataObject.isStale(MetadataObject.java:721)
         at oracle.wsm.mds.MDSAccessor.getLatestMOCopy(MDSAccessor.java:1388)
         at oracle.wsm.mds.MDSAccessor.getMetadataObjectAsMO(MDSAccessor.java:1506)
         at oracle.wsm.mds.MDSAccessor.getStoreLastUpdatedDate(MDSAccessor.java:1629)
         at oracle.wsm.policymanager.impl.PolicyAccessService.getStoreTimestamp(PolicyAccessService.java:242)
         at oracle.wsm.policymanager.impl.PolicyAccessService.getStoreTimestampAsDate(PolicyAccessService.java:252)
         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.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
         at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
         at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy297.getStoreTimestampAsDate(Unknown Source)
         at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl.getStoreTimestampAsDate(PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl.java:58)
         at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl_1033_WLStub.getStoreTimestampAsDate(Unknown Source)
         at oracle.wsm.policymanager.client.PolicyAccessServiceDelegate.getStoreTimestamp(PolicyAccessServiceDelegate.java:242)
         at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$PolicyCacheRefreshThread.run(PolicyCacheImpl.java:801)
    Caused By: oracle.net.ns.NetException: Socket read timed out
         at oracle.net.ns.Packet.receive(Packet.java:333)
         at oracle.net.ns.NSProtocol.connect(NSProtocol.java:267)
         at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1076)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:303)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:640)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:205)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:554)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:327)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:227)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:427)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:322)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:438)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:317)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
         at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:342)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:360)
         at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.fetchConnection(JNDIConnectionManagerImpl.java:91)
         at oracle.mds.internal.persistence.db.ConnectionManager.getConnection(ConnectionManager.java:347)
         at oracle.mds.internal.persistence.db.BaseReposAccess.<init>(BaseReposAccess.java:347)
         at oracle.mds.internal.persistence.db.shredded.ShreddedReposAccess.<init>(ShreddedReposAccess.java:274)
         at oracle.mds.internal.persistence.db.shredded.ShreddedDBMSConnection.createReposAccess(ShreddedDBMSConnection.java:444)
         at oracle.mds.internal.persistence.db.BaseDBMSConnection.getOrCreateReposAccess(BaseDBMSConnection.java:2072)
         at oracle.mds.internal.persistence.db.BaseDBMSCVersionSupport.getDocument(BaseDBMSCVersionSupport.java:286)
         at oracle.mds.persistence.DelegatingMSConnectionVersionSupport.getDocument(DelegatingMSConnectionVersionSupport.java:72)
         at oracle.mds.internal.persistence.PManagerVersionSupportImpl.getDocument(PManagerVersionSupportImpl.java:255)
         at oracle.mds.core.MOState.getTipPDocument(MOState.java:981)
         at oracle.mds.core.MOState.checkStaleVersion(MOState.java:893)
         at oracle.mds.core.MOState.checkStalenessDocFromBuilder(MOState.java:723)
         at oracle.mds.core.MOState.getIsStaleLastModified(MOState.java:537)
         at oracle.mds.core.MOContent.getIsStaleLastModified(MOContent.java:267)
         at oracle.mds.core.MetadataObject.isStale(MetadataObject.java:721)
         at oracle.wsm.mds.MDSAccessor.getLatestMOCopy(MDSAccessor.java:1388)
         at oracle.wsm.mds.MDSAccessor.getMetadataObjectAsMO(MDSAccessor.java:1506)
         at oracle.wsm.mds.MDSAccessor.getStoreLastUpdatedDate(MDSAccessor.java:1629)
         at oracle.wsm.policymanager.impl.PolicyAccessService.getStoreTimestamp(PolicyAccessService.java:242)
         at oracle.wsm.policymanager.impl.PolicyAccessService.getStoreTimestampAsDate(PolicyAccessService.java:252)
         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.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
         at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
         at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy297.getStoreTimestampAsDate(Unknown Source)
         at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl.getStoreTimestampAsDate(PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl.java:58)
         at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at oracle.wsm.policymanager.ejb.impl.PolicyAccessService_elx95s_IStringPolicyAccessServiceRemoteImpl_1033_WLStub.getStoreTimestampAsDate(Unknown Source)
         at oracle.wsm.policymanager.client.PolicyAccessServiceDelegate.getStoreTimestamp(PolicyAccessServiceDelegate.java:242)
         at oracle.wsm.policyaccess.impl.cache.PolicyCacheImpl$PolicyCacheRefreshThread.run(PolicyCacheImpl.java:801)
    >
    what can be done in order to resolve this issue, is it required once again create domain? can you give me some idea?
    regards
    ashok.v

Maybe you are looking for