Server Restart Problem

We are using IBM AIX 5.3L OS on IBM Servers. Application is Oracle Database EE 10G 10.1.0.4 and
Oracle Applications Server 10G EE 10.1.2.0.2. JDBC Driver Version is 10.1.0.4.2.
We have been facing a problem with below errors:
JVMDG217: Dump Handler is Processing Signal 11 - Please Wait.
JVMDG305: Java core not written, unable to allocate memory for print buffer.
JVMDG215: Dump Handler has Processed Exception Signal 11.
The application server crashes very frequently and above errors are written. Can anyone suggest
how to resolve this issue ?
Thanks in Advance
Message was edited by:
Cool_Jr.DBA

Have you had a look at?
Would seem to indicate a memory error in the application
http://forums.sun.com/thread.jspa?messageID=2531538

Similar Messages

  • Message Server Restart Problem

    Hello. I've run into the following problem, and hope someone can help.
    Was adding a fourth mail partition, and I had problems with the start-msg after doing the stop-msg. Have done this before without any problems.
    The start-msg looked as follows:
    Starting ENS daemon
    /opt/email/server5: Starting STORE daemon ..... done: 14668
    /opt/email/server5: Starting POP3 daemon .... done: 14685
    /opt/email/server5: Starting IMAP4 daemon ...Cannot bind to port 143: Address already in use
    Did a stop/start a second time and the stop complained about no pidfile.imap. Indeed, there is not one. The other services (pop, etc) have
    pidfile's.
    After doing some reading, I'm thinking the imapd processes were not completely down after the first stop-msg? I see 4 processes now, which
    matches the service.imap.numprocesses = 4 config. I was not previously
    aware of this number of imapd processes.
    Tonight, I will try again. As for the procedure, I plan on waiting a few minutes
    to allow imapd processes for finish up so that port 143 can be bound on the
    next start. Can those processes be killed if they don't go away? Is there a
    method to ensure that the 143 port is ready for a start-msg?
    We are on Iplanet MS 5.2. Any help will be much appreciated.
    Thank you, Keith

    Hi,
    The start-msg looked as follows:
    Starting ENS daemon
    /opt/email/server5: Starting STORE daemon ..... done:
    14668
    /opt/email/server5: Starting POP3 daemon .... done:
    14685
    /opt/email/server5: Starting IMAP4 daemon ...Cannot
    bind to port 143: Address already in useSounds like one of the imapd processes didn't shut down cleanly - or was still in the process of shutting down when you attempted to restart, and the old process is still bound to port 143.
    After doing some reading, I'm thinking the imapd
    processes were not completely down after the first
    stop-msg? Yep - a fair assumption. That is why usually when shutting down/restarting iMS5.2 I used to make sure all the processes were dead (./stop-msg; ps -ef | grep server5). What can happen is that the process has been asked to 'gracefully' shut down... rather then just kill -9 the process. The graceful shutdown can take a bit of time.
    I see 4 processes now, which
    matches the service.imap.numprocesses = 4 config. I
    was not previously
    aware of this number of imapd processes.There should be 4 processes.
    Tonight, I will try again. As for the procedure, I
    plan on waiting a few minutes
    to allow imapd processes for finish up so that port
    143 can be bound on the
    next start. Yep sounds fair. It's pretty easy to just run a 'ps -ef | grep server5' and see if there are any processes remaining rather then just waiting.
    Can those processes be killed if they
    don't go away? Yes - but make sure you kill ALL of the messaging processes if they are stuck, don't just concentrate on the imapd process.
    Is there a
    method to ensure that the 143 port is ready for a
    start-msg?Already discussed.
    We are on Iplanet MS 5.2. Any help will be much
    appreciated.As usual.. iMS5.2 is soon to be out-of-support (may 2007) so you should look to upgrade to version 6.
    Regards,
    Shane.

  • Cisco B and C series server restart problem

    Hi,
    When upgrade Cisco Server's memory, The servers restart 4-5 times. Why is this restarts a lot of time ?

    Hello Mehmet,
    Please consider following issues :
    Please browse to following page for more infomation :
    http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/guide/UCSTroubleshooting.pdf
    Regards

  • JDBC Connection pool recovery after DB server restart

    I am finding that Kodo is throwing the following exception after I restart
    my database server (mysql). I am doing the database server restart while my
    application server is idle, so it is not during a transaction.
    Communication link failure: java.net.SocketException [code=0;state=08S01]
    NestedThrowables:
    com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
    This is presumably due to the JDBC connection pooling. Is there a
    configuration setting that allows Kodo to detect such failures and reconnect
    to the database server without exposing this problem to the application
    code? For example, WebLogic Server's JDBC connection pool has a setting that
    enables testing a connection and recovering from such failures before
    allocating it from the pool.
    Ben

    This is presumably due to the JDBC connection pooling. Is there a
    configuration setting that allows Kodo to detect such failures and reconnect
    to the database server without exposing this problem to the application
    code?Not right now. You can log an enhancement request with our bug database:
    http://bugzilla.solarmetric.com/

  • BPEL Server Restarts intermittently

    Hi All,
    I have got a strange problem with my BPEL Server. Every once in a while the BPEL Server restarts on its own. I do not know if it has to do something with memory leaks or performance or some other reason.
    I have made my logs to roll at every 2 GB. I also noticed that the BPEL Domains are reloaded everytime the logs are rolled. If during this restart there is some process on the go then i get erroneous results.
    I am not able to reproduce the issue but it does happen intermittently. Has anyone else faced this issue?

    Also check logs in $OAS_HOME/opmn/logs/ for "Restart" messages, then check the timeouts for the BPEL instance in $OAS_HOME/opmn/config/opmn.xml. These are maybe too low.
    --olaf                                                                                                                                                                                                                                                                                                                                                                       

  • PI 7.0 Production server restarts automatically

    Hi guys,
    We have installed and configured correctly a PI 7.0 system on Windows 2003 Standard Edition X64-bit with SQL Server 2005. We are on SP12. Everything, SLD, RFC connections work properly.
    The problem is that 4-5 days after the installation the Windows Server restarts automatically in unexpected time during the day (unexpected shutdown), even when anybody doesn't do anything in the system. In the Event Viewer we get the following message/error "System Error: Category 102 EventID 1003". There are no other messages/errors.
    This is a production system and we are supposed to go live within the next days! So I need your help ASAP.
    Any ideas?
    Thank you.
    Best Regards.
    Evaggelos

    1) update your network card drivers to the latest  and for all devices including your motherboard chipset drivers.
    2) Are you using  ethernet instead of USB?
    3) This URL  might help you
    http://www.pcreview.co.uk/forums/thread-1885463.php
    Regards
    Sangeetha

  • Server Admin Problem - File Sharing fails to load

    We recently switched over from a 10.4 server to an Intel Quad Core Xserve running 10.5.8. Things seemed to be working for about a week but now The File Sharing part of Server Admin fails to load. After spinning for a few minutes I get a kNetworkError on the File Sharing Service.
    I'm not totally through setting up all the share points so this is causing quite a problem. Otherwise the Sharepoints that are set up are working properly. The first time this happened a server restart cleared the problem. This time nothing seems to help.
    Anyone have a cure for this?

    The problem seems to be getting worse. Once the error occurs some of the other services are not available through SA either. Anybody have any suggestions, or is it a reformat and reinstall situation?

  • Jrun service restart problem

    I have began to get an error after installation of Java
    update 1.4.2_02 jre. (It was an auto update)
    It currently runs with 1.4.2_02 SDK as a service. After
    starting to get the error, I uninstall the update but it still
    continues.
    After restarting computer, it starts the server without
    problem.
    While tryign to restart server with Admin Tools->Services
    it gives the error (-2)
    Error reported in logs:
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    I have done some research but nothing is useful for my
    problem.
    jvm.config hasnot been changed. but here is the arguments.
    java.args=-Xms32m -Xmx128m -Duser.language=en-US
    -DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS
    -Dsun.io.useCanonCaches=false
    btw, it has 2gb ram.
    I have read using "-server" in the wrong place could result
    this situation but it doesnt use it.

    It seems the application uses another config file not to
    waste resources with admin application as it is explained here(
    http://mkruger.cfwebtools.com/index.cfm/2006/4/17/multiserver)
    here is the arguments it actually reads:
    java.args=-server -Xms1000M -Xmx1400M -XX:NewSize=256M
    -XX:MaxNewSize=256M -XX:MaxPermSize=140M -Xss128k -Xincgc
    -Dsun.io.useCanonCaches=false -Duser.language=en-US
    It does a lot more sense now, however I cant still figure it
    out, what has been changed because of the update?? It might not
    allocate the space -1540M max with MaxPermSize- because of lack of
    memory however there were not any of this a few days ago.
    thx for quick replies tzimmerman

  • 2008 R2 Server Time problems - Gaining/Losing 6s/min

    I'm having problems with a server on our network. I can go for days without a problem but then without warning the server will either gain or lose time at anywhere up to around 6 seconds per minute.  The server is running Server 2008 R2, member
    server, IIS running internal sites, SiteCore CMS v6.4.1.
    The w32time service is configured as follows
    PDC - retrieves it's time from uk.pool.ntp.org, all other DCs and member servers have the w32tm service configured to syncfromflags:domhier.
    The server in question is a virtual machine running on a server 2012 Hyper-V cluster.  All of the virtual servers on there have the Hyper-V time sync service enabled however we have edited the registry to set HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider\Enabled
    to 0.
    w32tm /query /source responds with a DC local to the server.
    I've been monitoring the server for a number of days by outputting  the following command to a file on the server w32tm /stripchart /computer:localdc /dataonly and on the whole the server has been within +-5 seconds of the reference computer.
    At approximate 13:06 this afternoon the server started to lose approximately 0.1s every second and is still doing so.  I've tried running the following command w32tm /resync /computer:localdc /nowait but to no avail.  I've had to manually change
    the time in order to get services available again.
    I've searched through the event logs on the server at or around 13:06 and can't find anything of any significance happening at that time.  I'm unable to restart the server during work hours as it's got key services running on it.
    Any help on how to keep the time in sync on the server would be appreciated.

    I would recommend that you read the Wiki I started here: http://social.technet.microsoft.com/wiki/contents/articles/18573.time-synchronization-in-active-directory-forests.aspx
    As I mentioned:
    Microsoft do not guarantee and do not support the accuracy of Windows Time Service between nodes on a network as this service is not a full-featured NTP solution that can meet time-sensitive application needs. Windows Time Service was not designated in such
    way that it maintains time synchronization to the range of one (1) or two (2) seconds.
    If you have an application that needs to have a high accuracy NTP solution then Windows Time Service should not be used in this case. Instead, third party software are available to satisfy this need.
    High Accuracy W32time Requirements: http://blogs.technet.com/b/askds/archive/2007/10/23/high-accuracy-w32time-requirements.aspx 
    Support boundary to configure the Windows Time service for high accuracy environments:http://support.microsoft.com/kb/939322/ 
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile
    Thanks for that Mr X, I have already been on that page and implemented the Windows time service in the manner described in the article and in the other articles relating to configuring the Windows time service in a Hyper-V environment.
    The issue is not relating to the configuration of the service as a whole as my other 72 server instances are working fine, it is just this one that is giving me a problem.  I have no need for a high accuracy environment, just one that keeps general
    time and doesn't lose or gain 6 seconds/minute at random intervals through out the day.
    I have been doing some further problem analysis since my original post with regards to the Hyper-V time sync service and my results are as follows.
    When the time is a long way out on the server restarting the Hyper-V time sync service resets the time to the correct time instantly.
    If you live migrate the VM to another host in the Hyper-v cluster when the time is incorrect, again the time resets to the correct time instantly.
    I have reinstalled the Hyper-V integration services but this has had no effect on the problem.
    As a last ditched attempt to resolve the issue I have re-enabled the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\w32time\TimeProviders\VMICTimeProvider
    registry key so that when you run a w32m /query /source command the result is "VM IC Time Synchronization Provider"
    I'll report back my findings.

  • Web Service from stateful Session Bean deleted after server restart

    Hi,
    i created a stateful session bean and from this a web service.
    I am able to deploy it and it works really fine.
    My problem is: after a server restart the web service is gone and i
    have to deploy it again.
    I have some other web services (but these are web services from stateless session beans)
    but they "survive" the server restart.
    I don't want to deploy the web service after every server restart, did I forget something or
    is it a general problem of stateful session beans or web services?
    Thanks in advance
    Jens

    Hello Björn,
    I am not quite sure what your problem is but did you have a look at these articles:
    http://help.sap.com/saphelp_nw04/helpdata/en/4d/993441c73cef23e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/be/2e2c4142aef623e10000000a155106/frameset.htm
    I hope they can give you some idea.
    Regads
    Vyara

  • Best Practice to troubleshoot a Crawler Issue after SQL Server restarts

    Hi Everyone
    I am after some general advice or a suggested place to start when troubleshooting crawler issues after an unplanned, out-of-sequence server restart.
    Specifically, the SQL Database in the SharePoint 2010 farm. Better yet, is there a standard practice way of resolving such issues?<o:p></o:p>
    So far articles I have found suggest options from reviewing the crawl logs, creating a new crawl component, right through to using fiddler to monitor the crawler.
    Are these sufficient places to start / methodologies to follow, what else should be considered?
    Any advice greatly appreciated.
    Thanks,
    Mike

    Well, as I said before, there are lots of different potential issues & resolutions for crawlers.  It really depends on the issue.  I would say that the base troubleshooting steps start the same no matter which service/feature you are looking
    at.  So, I'll try to keep this sort of generic, but beyond finding the details of the problem, the SOP or process will vary greatly based on what the error is.  I hope this helps, and sorry if it's not specific enough.
    1 - check the ULS logs
    2 - check the windows application logs
    3 - verify related services are running (get-spserviceinstance), possibly stop/start them to reprovision the instance on the affected server
    4 - clear the config cache (this alone will clear about 30% of your basic problems)
    6 - verify disk space & resource consumption on affected server (& SQL, SQL is always the potential to be the true "affected" server)
    7 - iisreset
    8 - verify connectivity between all servers in the farm and SP
    9 - verify requir3ed features activated
    10- check if any changes were made to environment recently (new hardware, updates to OS or apps, updates to GPOs, new solutions, etc)
    11- check if the issue is reproducible in another environment (only reliable if this is a similar environment, i.e. same patch level test farm or dr farm).  see if it occurs in other site collections within the web app, different web apps, different
    servers/browsers, etc, basically just try to nail down the scope of the problem
    There is a whole slew of thiings you could check from verifying certificates & perms, to rerunning psconfig, to checking registry keys, again I go back to it depends.  hopefully this can get you started though.  in the end ULS is where all
    the real info on the issue is going to be, so make sure you check there.  don't go in with tunnel vision either.  if you see other errors in ULS, check them out, they may or may not be related; SharePoint is an intricate product with way more moving
    parts than most systems.  fix the little quick ones that you know you can handle, this will help to keep the farm clean and healthy, as well as crossing them off the list of potential suspects for your root cause.
    Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

  • Composites in "Unknown" state after managed soa server restart

    Hi,
    I am using SOA suite 11.1.1.6 version on 64 bit OEL Linux. I am getting following error in managed server output log files:
    Feb 20, 2013 5:59:32 AM IST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
    oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/deployed-composites/WirelessEnterprise/svcEnrichSEARequest_rev1.0/svcEnrichSEARequest.wsdl: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/deployed-composites/WirelessEnterprise/svcEnrichSEARequest_rev1.0/svcEnrichSEARequest.wsdl does not exist.
    Though this composites gets loaded, the composites dependent on this composite goes into "Unknown" state. Other composites are properly loaded on server restart.
    Please let us know if anybody has any solution to this problem.

    Hi,
    Thanks for your help.
    we have narrowed down to problem now.
    The actual problem occurs while redeploying same composite on same revision.
    E.g 3 composites A, B and C are deployed on and in "Up" state.
    B And C composites depends on A.
    B composite composite.xml has following entry
    <import namespace="http://xmlns.oracle.com/A"
    location="oramds:/deployed-composites/Enterprise/A_rev1.0/A.wsdl"
    importType="wsdl"/>
    same entry exist for C composite.xml as well.
    Now whenever composite A is redeployed with same revision (1.0 in our case), and managed servers are restarted, B and C composites goes in to "Unknown" state.
    Moving A.wsdl to /apps/wsdl/* in MDS works but it duplicates the A.wsdl file beacause it also exists in MDS @ /deployed-composites/Enterprise/A_rev1.0/A.wsdl
    Please let us know if anyone has any solution.
    Thanks,
    Rupesh.

  • Composite with dependency not working after soa server restart

    Hello,
    I have composite application that invokes another composite application. After deploying those work fine. But after restarting soa server the one having dependency does not work any more. To soa server log I get following:
    <Jul 1, 2010 11:45:29 AM EEST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
    oracle.fabric.common.FabricException: Error in getting XML input stream: http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
    at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:276)
    Caused By: java.io.FileNotFoundException: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
    <Jul 1, 2010 11:45:30 AM EEST> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "POProcessing" failed: Unable to find a WSDL that has a definition for service {http://oracle.com/sca/soapservice/POProcessing/POProcessing/receivePO}receivePO and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..>
    So POProcessing does not work any more after server restart. validationForCC works fine also after server restart. Url http://...validationForCC/getStatusByCC?WSDL points to wsdl file and is visible by browser.
    I use soa suite 11g patch set 2 (11.1.1.3) running on redhat enterprise linux 5.
    Any idea what is the problem?
    Is it somehow possible to configure which composites are started first during server startup?
    regards, Matti
    Edited by: user10197965 on Jul 1, 2010 2:28 AM

    Yes, I did that. I'm not all that happy about this as a solution either, but it's better than making multiple copies.
    We have since found out that his is a known bug and that it is fixed in some, but not all, deployments.
    -------- see below -------------
    Composites With WSDL Dependencies Fail To Deploy Following SOA Server Restart [ID 1272070.1]          
    Modified:Jul 19, 2012 Type:PROBLEM Status:MODERATED Priority:3                         
    In this Document
         Symptoms
         Cause
         Solution
         References
    This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
    Applies to:
    Oracle SOA Platform - Version 11.1.1.3.0 and later
    Information in this document applies to any platform.
    Symptoms
    A SOA Project has an external reference to a Web Service or a reference to another Composite.
    When the SOA Server is started, the Composite is trying to access the WSDL of it's referenced Web Service in order to load data structures. If SOA can not find the WSDL then the Composite fails to load/deploy.
    Once this happens the Composite can not be started, or shutdown, from Enterprise Manager Fusion Middleware Control Application.
    Related Error Messages:
    [ERROR] [SOA-20020] ... Unable to find a WSDL that has a definition for service ... Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.]
    javax.wsdl.WSDLException: WSDLException: faultCode=INVALID_WSDL: Error reading import of oramds
    Cause
    When SOA Server is restarting the Composite can not access the WSDL of it's referenced Web Service (it is not available).
    In the first scenario there are two Composites on the same server: CompositeA and CompositeB.
    In SOA Suite 11g there is no possibility to specify the load order for the composites. If CompositeA references CompositeB and if CompositeA is firstly loaded then it can not access the WSDL from CompositeB and the issue occurs.
    In the second situation there is one Composite on the server (CompositeA) which references an external WebService (ExternalWS). If the ExternalWS is not available when the SOA Server is starting then this issue occurs.
    Solution
    Solution 1
    Redeploy the affected Composite into the SOA Server.
    You can do that but it is not advisable in a production environment and in a development environment it will take a lot of time to redeploy the composite manually
    Solution 2
    Copy the abstract WSDL locally into the project.
    This is documented in these articles in our Knowledge base:
    •     Document:1155033.1 Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
    •     Document:1151973.1 Boot Order Of The Composites Upon Soa Suite Restart
    Steps:
    o     a. Copy and use the WSDL file in the Project
    o     b. Edit the WebService Adapter
    o     c. Change the "WSDL URL" to point to the WSDL copied into the project
    o     d. Redeploy the Project
    o     e. Make this configuration with all the Projects that have a references with other Web Services
    Solution 3
    Use shared artifacts in Metadata Service (MDS). A WSDL used by more than one composite is a shared artifact per definition. If the WSDL structure is changed (that is not happening frequently in a production environment), you will normally deploy a composite with a new version because overwriting it will break your production environment. Moreover, in a development environment you will need a proper process in place where different developers access the same artifacts within MDS. In addition, when you use external WSDLs (owned by third parties), you will have a proper process/agreement in place to be notified about modifications affecting your applications.
    1.     In order to use shared artifacts a MDS connection must be configured in jDeveloper:
    http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85488
    2.     Deploy the shared artifacts:
    o     a. Create a JAR profile and include the artifacts to share
    o     b. Create a SOA bundle that includes the JAR profile
    o     c. Deploy the SOA bundle to the application server
    http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85472
    If the shared artifacts (WSDLs) needed are from other composites this step can be skipped
    3.     Create a new WebService
    o     a. When completing the "WSDL URL" click on "Find existing WSDL's"
    o     b. Select "Resource Palette"
    o     c. Go to the SOA-MDS
    o     d. Select a WSDL from a Composite or the one deployed at step 2.
    Known Restriction 1
    The port and the location for the WSDL reference is not completed automatically by jDeveloper in the composite.xml file. This information must be inserted manually. In Bug:10287325 is raised this issue and it is available for SOA 11gPS2+.
    Known Restriction 2
    Another issue regarding MDS caching is raised in Bug:10218147 - the MDS cache is not refreshed when an artifact is deployed or deleted.
    In order to refresh this cache the server must be restarted. This Bug resolves the issue but in a production environment the server restart will be the preferred option. The reason for that is because in a production environment you never deploy single composites under the same version after artifacts (WSDLs) have been modified.
    The fix for the Bug:10218147 can be an acceptable solution in development environment where redeployment would be quicker than restarting the server.
    Bug:10218147 is available for SOA 11gPS2+.
    To find out more information about how to use Shared Metadata check the following documentation:
    Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
    41 Deploying SOA Composite Applications
    41.7.3 Deploying and Using Shared Metadata Across SOA Composite Applications in Oracle JDeveloper
    URL:
    http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#CACFEAJJ
    Solution 4
    The last solution is to use an UDDI (Universal Description Discovery and Integration).
    Oracle recommends Oracle Service Registry 11g (OSR). The advantage is that you can use OSR and SOA Suite in a Shared WebLogic Domain.
    http://www.oracle.com/technetwork/middleware/registry/overview/index.html
    http://blogs.oracle.com/governance/2010/05/oracle_service_registry_11gr1.html
    To find out more information about Oracle Service Registry check the following documentation:
    Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite 11g
    33 Configuring Service and Reference Binding Components
    33.1.3 Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration
    http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10226/bc_config.htm#SOAAG37248
    Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
    A BPEL Process Activities and Services
    A.4 Publishing and Browsing the Oracle Service Registry
    http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_appx_ref.htm#SOASE85561
    Oracle Fusion Middleware Service Registry 11g
    http://download.oracle.com/otndocs/tech/soa/OSR11gR1ProductDocumentation.pdf
    Solution 5
    In case you have BPM Components in the Composites deployed check the following note:
    Document 1317803.1 Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
    The issue is caused by the Bug:11822470 SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
    References
    BUG:10218147 - WSDL CHANGES NEED SOA SUITE SERVER RESTART
    BUG:10278478 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
    BUG:10287325 - ABSTRACT WSDL NOT AVAILABLE WHEN COMPOSITE STARTED
    BUG:10311698 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES CAN NOT BE STARTUP / SHUTDOWN
    BUG:11822470 - SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
    @ BUG:9267312 - MDS ARTIFACTS ARE STILL CACHED AFTER DELETING
    @ BUG:9708488 - AFTER SOA RESTART, ALL PROCESSES HAVE TO BE REDEPLOYED
    @ BUG:9749845 - SCHEMA CACHE STARTS EMPTY AFTER RE-START, BUT NOT AFTER DEPLOYMENT
    NOTE:1151973.1 - Boot Order Of The Composites Upon Soa Suite Restart
    NOTE:1155033.1 - Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
    NOTE:1317803.1 - Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
    Bug 11822470 : SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER                    
                   Bug Attributes     
    Type     B - Defect     Fixed in Product Version     11.1.1.6
    Severity     2 - Severe Loss of Service     Product Version     11.1.1.4
    Status     80 - Development to QA/Fix Delivered Internal     Platform     912 - Microsoft Windows (32-bit)
    Created     Mar 1, 2011     Platform Version     2003
    Updated     Oct 12, 2012     Base Bug     N/A
    Database Version     N/A     Affects Platforms     Generic
    Product Source     Oracle          
    Abstract: SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
    *** 03/01/11 08:07 am ***
    Customer has a project consists of two services for interaction with the
    process and one reference to an external service.
    On deployment of the process to an Enterprise Environment, the process works
    as expected. However, upon a restart of the managed server, the process will
    then fail to deploy.
    Workaround used is to redeploy the project again.
    Bug 10278478 : WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED                    
                   Bug Attributes     
    Type     B - Defect     Fixed in Product Version     
    Severity     2 - Severe Loss of Service     Product Version     11.1.1.3.0
    Status     92 - Closed, Not a Bug     Platform     226 - Linux x86-64
    Created     Nov 10, 2010     Platform Version     RED HAT ENTERPRISE LINUX 5
    Updated     Dec 10, 2010     Base Bug     N/A
    Database Version     N/A     Affects Platforms     Generic
    Product Source     Oracle          
    Abstract: WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
    Detailed Problem Description
    ====================
    When a SOA composite get dependencies with other SOA composites located on the same server, if the dependency is still not loaded, the SOA composite will not be loaded, and there is no possibilities for Entreprise Manager console to restart it (EM crash). The only way to make it working is to redeployed the SOA composite from jDeveloper that is not acceptable in a production environment.
    The composite that has the issue cannot be start-up or shut-down, although the Enterprise Manager do not show any errors with it.

  • CS3 server startup problem

    Hello all,
         We are using this product since 2007, and we didn't have any problems until yesterday. After server restart, Communication  between clients and server was broken. When trying to establish communication between client and CPS server, error mesage is displayed that CPS server is down.
    So, I've vent to the server side, check in system services for Macromedia Contribute Publishing Server service state - it was Started. But still if I try to connect on the server's Administration page, I receive after 20 seconds empty web page. I've suspected that it is something wrong going on during starting of the service itself, so I've tried to start the server manually using Jrun. Following is extraction of the log file during startup of server using Jrun:
    09/28 13:39:16 info No JDBC data sources have been configured for this server (see jrun-resources.xml)
    09/28 13:39:17 info SSL Service listening on *:8900
    09/28 13:39:17 info Deploying enterprise application "JRun 4.0 Internal J2EE Components" from: file:/C:/Program Files/Macromedia/Contribute Publishing Server/jrun4/lib/jrun-comp.ear
    09/28 13:39:17 info Deploying EJB "JRunSQLInvoker" from: file:/C:/Program Files/Macromedia/Contribute Publishing Server/jrun4/lib/jrun-comp.ear
    09/28 13:39:17 info Deploying web application "Contribute Key Server" from: file:/C:/Program Files/Macromedia/Contribute Publishing Server/jrun4/servers/contribute-wps/contribute/
    09/28 13:39:17 user JSPServlet: init
    09/28 13:39:17 user no such classpath element: ./WEB-INF/cfusion/gateway/lib
    09/28 13:39:17 user FlashGateway: init
    09/28 13:39:17 user ColdFusionStartUpServlet: init
    09/28 13:39:17 user ColdFusionStartUpServlet: ColdFusion MX: Starting application services
    09/28 13:39:17 user ColdFusionStartUpServlet: ColdFusion MX: VM version = 1.4.2_05-b04
    09/28 13:39:18 user ColdFusionStartUpServlet: ColdFusion MX: application services are now available
    09/28 13:39:18 user CFCServlet: init
    When the last step is executed,  after 20 seconds on JRun Launcher window an error message is displayed:
    "An error occured while trying to start contribute-wps. Check Console log for more details."
    I've tried to contact Adobe Technical support, but the answer was that due to fact that CS3 is discontinued product at the momment there is no technical support for it. So guys you are my only hope.
    Best regards
    Boris

    Please check any other service is running on the same port.

  • Application server restarts

    Hi,
    Whenever a change is made to OAF application, the E-Business appserver needs to be restarted. This creates problem because from the perspective of business users this is a downtime however small the downtime may be.
    Even for profile changes to take effect, the app server has to be restarted.
    Is there any methods or techniques like server architecture that would avoid or
    circumvent the need to restart appserver whenever a small thing is changed in OAF? Or if this is not possible any other mechanism by which we can keep the users not kicked off of the system?
    Your thoughts on this would be helpful.
    Regards,
    Arun

    Arun,
    A server restart is not required always. It depends on a case to case basis. For the case that you've mentioned (i.e. profile changes), it is not required as the DB invalidation should take care of reflecting the changes to all the middle-tiers. Please check if this patch is available and cache invalidation is working in your system.
    If there are any other cases, do let us know.

Maybe you are looking for