Automated MDM Server restart

Hello.
We currently have an MDM server running on a Windows environment (32 bit). We have weekly automated reboots of the server and have come across a problem with the reboots in that even though the Oracle and MDM Server services are set to automatic, it seems they are not starting in the correct order. After the reboot, we go to the MDM Console and try to connect to the Repository of the started MDM Server but receive an error. We restart the MDM Server and then are able to log on.
Does anyone know of a way to not have this happen and make sure that the Server and Oracle are started in the correct order? Also, it appears as though the Repository does not automatically load upon a restart. Is there a way to make this happen, as well? We are looking to fully automate these processes so that we do not have to manually check these items for the weekly reboots.
Thanks,
Nicole

Hi Nicole,
Apart from above answer i am sure following URLs will add more insights:
[http://help.sap.com/saphelp_mdm550/helpdata/en/f7/f11270ef3b4590bd4d0e1fc875bda7/content.htm]
[http://help.sap.com/saphelp_mdm550/helpdata/en/34/a2e71ecec8402ab31c7618ea80c5f5/content.htm]
[http://help.sap.com/saphelp_mdm550/helpdata/en/21/5540c3cc6e4d82a4804d74b2cd1421/content.htm]
Hope it will suffice to hint you.
With Warm Regards,
Krutarth

Similar Messages

  • Repositories are invalid after restarting the MDM Server in MDM 7.1

    Hi SDNers,
    After I restarted the MDS server I am not able to logon to the repository. When I tried to connect to repository I am getting an error like "Repository Connect Failed and The MDM Repository is Invalid"
    I tired to delete but I am not able to delete also. While deleteing it is giving an error like  "MDM Repository is in Read Only Mode".
    So I am not able to Delete the repository also to create a new Repository.
    Any Help or Solution
    Thanks
    Kiran
    Edited by: Kiran on Apr 6, 2011 6:40 AM

    Kiran -
    some of the below ways you can check
    1. Check your mds.ini settings. and do unmount nad then mount the MDM server again. Try to Monitor the Authentication for Particular repositry which you want to connect to your MDM 7.1 server
    2. after checking the note 1325833. try restart database server first then MDM server.
    3. also try to check with Appropriate repository option once.
    HTH
    thx
    Deep

  • Unable to restart MDM Server

    Hi All,
    I am using MDM SP4. We have a repository Z_ATLAS_MATERIAL_P_TST in SP4. Yesterday I tried to rename this repository but I was not aware that in SP4 we can't rename repository...it's a bug. So, when I renamed this repository to Z_ATLAS_MATERIAL_P_TST1 it gave me error "MDM Repository is invalid" and after 2-3 mins the console window get closed.
    Then I tried several times to mount that MDM server in new console session but everytime console gets terminated.
    But in the background MDM server and SQL server were running.
    Today, when I restarted the MDM server,it ran for 1-2 mins then it got terminated abrubtly.
    Can any one of please suggest what could be the reason and how to resolve it.
    Thanks,
    Varun

    Hi Varun,
    We also faced with such problem. First try to re install MDM Console client, even though if it doesnt start then try to restart your services through services.msc in the RUN. Restart your MDM server, Listeners and Database Services.
    Hope this solves your problem.
    Reward points if helpful.
    Prasad......

  • Missing data after server restart

    Hi,
    We restarted our MDM server at the OS level last night. Everything seemed okay after the restart. However, when our users came in this morning, they found that some data was missing from a table. We have a Material repository with 3 main tables. Some data which have previously been populated was not appearing in our Products Detail table, the largest of the three. A large number of rows in the table had columns that failed to load with data on the repository auto-start that occured after the server restart. The auto start value in the mds.ini file was set at 300 (5 minutes) as we had seen this iisue happen once before, and thought that may help.
    A stop and restart of the repository corrected the issue. Is there anything we could have done to prevent this? Is it worthwhile to try increasing the auto start delay again? Validating detail data after every server restart is not an effective option.  
    MDM version: 7.1 SP08
    OS: AIX  DB: Oracle 11g
    Thanks!
    Dave

    Hi Dave,
    I meant that when you load repository using Immediate data is loaded from .acl files (accelerator files) in a async manner.
    Whereas when you load by Update Indices new acl files are generated.
    Below men6tioned is a comparision between the 2 ways of laoding repository:
    Load Repository Immediate
    o Loads indexes from accelerator files instead of being regenerated by reading the data them from the DB and creating the index.
    o Automatically builds indexes stored in out-of-date accelerator files.
    o Is usually fast.
     Load Repository with Update Indices
    o Rebuilds all MDM indexes files by reading and indexing data stored in the DB. The results are flushed on disk as accelerator files.
    o Necessary by repository schema changes or if any error occurs.
    o Might take significant amount of time to complete.
    So when you observe some visual data impact in your repository it is good idea to rebuild indexes.
    I guess we cannot schedule this as default behavior is to load by immediate even through the inin parameter.
    as a best practice one can do this by fixing a time frame eg monthly depending on data/schema changes.
    Thanks,
    Ravi

  • MDM 7.1 Portal Connectivity to MDM server

    Hi all
    I was running the MDM 7.1 ramp up version so far with full connectivity from the portal to MDM. I had configured both the standard business partner and a custom repository using the Portal Business Content . Now that I have migrated to the just released MDM 7.1 (GA ) , I am encountering the following error at the portal level . I am using the standard "Using Mapping" to connect to the MDM server from the portal and not the newly introduced "Trusted Connection" . Any body has any clue as to whats going wrong ..
    com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
    at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
    at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)... [see details]
    DETAILED MESSAGE
    com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
    at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
    at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)
    at com.sap.mdm.admin.utils.MdmConnectionProvider.createBlobObjectCache(MdmConnectionProvider.java:308)
    at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.initContexts(MdmeBaseDynPage.java:364)
    at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.doProcessBeforeOutput(MdmeBaseDynPage.java:154)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)
    at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
    at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:126)
    at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:56)
    ... 38 more
    Thanks
    Ray

    Hi Ray,
    This is a trusted connection problem. For this you need to create allow.ip and deny.ip files in your server. In allow.ip you need to give those ip address through which you would be connecting to MDM server executable file(mds.exe) like in your case your portals ip address. And in deny.ip you need to specify those ip which you feel shouldnt connect to MDM server. After assigning this ip remember to restart your mds.
    Also the users through which you are trying to connect to an MDM repository, their usernames must exist on the MDM repositoryu2019s Users table.
    For more details please see page 299 from MDM 7.1 Console refernece guide
    I hope I am able to solve your problem
    Thans & Regards
    Dilmit Chadha

  • Problem while creating JCA connection to MDM server

    Hi All,
    I have restarted my mdm connector(com.sap.mdm.tech.connector) along with the applications related to Enrichment Controller. All applications restarted successfully. After that I tried accessing the URL
    http://MDMSERVER:50000/MDM_EnrichmentController/WorkflowPolling?process=Monitor
    but I am getting following exception in this page
    Polling Repository
        name=Vijaybabu_Repo_on_MDMSERVER, status=No repository connection, error description=com.sap.mdm.net.ConnectionException: Problem while creating JCA connection to MDM server MDMSERVER
            Enrichment Request Threads
    Could somebody help me pointing if something I have missed..
    Thanks and Regards,
    Manoj

    hi Swarna,
    I have verified the repository and found 0 fatal errors, 0 non-fatal erros and 0 warnings. I also checked the MDM Factory and Connector service is running fine.
    The detailed exception is
    Sep 2, 2008 12:49:40 PM com.sap.mdm.logging.MdmLogger error
    SEVERE: Problem while creating JCA connection to MDM server 'KOLAPON'
    com.sap.mdm.net.ConnectionException: Can not resolve JCA connection
         at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:119)
         at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnectionAccessor(JcaConnectionUtil.java:62)
         at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:70)
         at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:59)
         at com.sap.mdm.repository.commands.GetRepositoryStatusCommand.execute(GetRepositoryStatusCommand.java:67)
         at com.sap.mdm.enrichment.common.ECAdminUtils.getRepositoryStatus(ECAdminUtils.java:125)
         at com.sap.mdm.enrichment.common.EnrichmentUtils.validateRepostiryConfiguration(EnrichmentUtils.java:889)
         at com.sap.mdm.enrichment.common.EnrichmentUtils.getCatalogManager(EnrichmentUtils.java:144)
         at com.sap.mdm.enrichment.workflowpolling.PollingThread.getCatalogManager(PollingThread.java:166)
         at com.sap.mdm.enrichment.workflowpolling.PollingThread.run(PollingThread.java:102)
    Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
         at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:223)
         at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:108)
         ... 9 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
         at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:122)
         at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:213)
         ... 10 more
    Regards,
    Manoj
    Edited by: Manoj Kumar Nanda on Sep 2, 2008 9:21 AM

  • MDM Server doesn't start after upgrade to SP 5

    hi,
    i'm not used to sap services on windows hosts.
    After the Update from 7.1.04 to 7.1.05 the mdm server doesn't start. I found only a few logs (unter c:/usr/sap/SID/MDS00/work). Most of them from sapcpe (without errors or warnings). Only the sapstart.log contains a bit information:
    SAP-R/3-Startup Program
    Starting at 2010/08/16 21:29:18
    Startup Profile: "C:\usr\sap\MDM\SYS\profile\MDM_MDS00_mdmtest"
    Starting Programs
    (1684) Execute: C:\usr\sap\MDM\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=C:\usr\sap\MDM\SYS\profile\MDM_MDS00_mdmtest list:C:\usr\sap\MDM\SYS\exe\uc\NTAMD64/mds.lst
    (976) Execute: C:\usr\sap\MDM\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=C:\usr\sap\MDM\SYS\profile\MDM_MDS00_mdmtest list:C:\usr\sap\MDM\SYS\exe\uc\NTAMD64/shared.lst
    (3632) Execute: C:\usr\sap\MDM\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=C:\usr\sap\MDM\SYS\profile\MDM_MDS00_mdmtest list:C:\usr\sap\MDM\SYS\exe\uc\NTAMD64/sapinstance.lst
    (2172) Execute: C:\usr\sap\MDM\MDS00\exe\mdmcpc.bat C:\usr\sap\MDM\SYS\profile\MDM_MDS00_mdmtest.INI C:\usr\sap\MDM\MDS00\config\mds.ini
    (3652) CreateProcess: C:\usr\sap\MDM\MDS00\exe\mds.EXE
    Process 3652 died unexpectedly, restarting process
    (3612) Restart CreateProcess: C:\usr\sap\MDM\MDS00\exe\mds.EXE
    Process 3612 died unexpectedly, restarting process
    (2364) Restart CreateProcess: C:\usr\sap\MDM\MDS00\exe\mds.EXE
    Process 2364 died unexpectedly, restarting process
    (3576) Restart CreateProcess: C:\usr\sap\MDM\MDS00\exe\mds.EXE
    Process 3576 died unexpectedly, restarting process
    (3588) Restart CreateProcess: C:\usr\sap\MDM\MDS00\exe\mds.EXE
    Process 3588 died unexpectedly, final process restart.
    Process will not be restated in the future because of frequent failure.
    (1396) Restart CreateProcess: C:\usr\sap\MDM\MDS00\exe\mds.EXE
    This isn't really much I can work with. In the sapmmc I found the Option Developer Trace. I try to 'switch it on', but there is no difference.
    With 7.1.04 the server was running well.
    I happy for any suggestions

    Hi,
    Please check out Note 1482822 - MDM Server not starting after MDM 7.1 SP05 was installed.
    hope it helps you.
    Best regards,
    sudhanshu

  • When mount MDM server on MDM console...MDM Console hangs.

    Hi,
    when i try to mount MDM server on MDM console, MDM Console hangs and then i have to stop MDM console with task manager.
    For this i have tried with restarting  MDM server - then also issue was not resolved, then i have rebooted the server, then issue resolved.
    But rebooting the server is not permanent solution, this problem occurs everything next 3-4 days.
    Please let me know the cause and it's solution if anyone has faced the similar issue.
    ---------------Server details----------------
    SAP MDM 7.1SPS11
    OS - Suse Linux
    DB - MaxDB
    MDM Console is also SPS11
    Thanks and Regards,
    Murtaza Najmi

    Hi Murtaza,
    This may be due to the memory full issue. It is advisable to allocate appropriate memory in the RAM where server is running. Generally it will be done by the DB team or Linux/unix team. Raise this ticket to your concerned teams.
    Thanks,
    Vinoth

  • MDM Server is responding very slow

    Hi,
    I am working with only 21,695 records and MDM Server is responding very slow.
    MDM Server is running on Intel(R)Xeon(TM) 2.40Ghz 2.39Ghz, 3.89 GB of RAM.
    System: Microsoft Windows Server 2003 Standard Edition Service Pack 2.
    The hard disk partition F: has 43.7 GB Freespace.
    It is impossible to do MDM Workflow matching and Merging with this slow speed.
    Regards
    Kaushik Banerjee

    Hi Kaushik,
    Please try to stop and restart the database server.
    You can check the below:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_mdm/~form/handler7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31303132373435%7d
    Re: MDM Server is very slow and locks users out
    Hope it helps.
    Thank you,
    Priti

  • EP not see MDM server

    Hi Gurus
    When I create a new MDM system in a Portal Content -> MDM Connection Wizard on step 4 (Select Repository) I cannot select any MDM repository because the drop-down empty. So I cannot finish the wizard and create a new MDM system reference in EP.
    My EP (NW 7.00 SP13) and MDM Server (5.5 SP6) are running on the same host. In MDM Console I can connect to my MDM server and see the MDM repository mounted to it.
    What is the problem with the MDM Connection Wizard? Maybe I specified the wrong properties on steps 1-3?
    Please, help!
    Thanks and Regards,
    Sergei

    >1. Verify that you have deployed the correct SCA files i.e. of compatible version with that of MDM Server
    >2. Only running repositories would be visible in the drop down
    >3. Try passing Server IP instead of Server Name
    1. How can I check this? I deployed the following SCAs: BP_MDM_TECHNOLOGY (5.50.6.0), MDM_JAVA_API (5.50.6.0) & MDM_WEB_UI. My MDM server seems a little bit newer: it's version is 5.5.64.92. Can it cause the problem?
    2. Yes, MDM server is running and the remote repository is loaded too.
    3. I've tried this. No any changes in behavior.
    In general when I come to the step Select Repository I do not see any delays. It seems the EP's wizard does not even try to connect to MDM server host which I specified on step 3. If, for example, I specify any unreachable wrong MDM Server host and go to step Select Repository it'll appear immediately without any connection attempts to the wrong host.
    Maybe something need to be configured additionally? What I did was I installed MDM Server + Console, started the MDM server, created and mounted MDM repository located on the remote MS SQL Server, then I deployed the SCAs mentioned before and restarted my J2EE server.
    Thanks and Regards,
    Sergei

  • Error mounting MDM Server

    Hi,
    Error mounting MDM Server
    We are unable to mount the MDM server, the error message saying
    (The specified SAP instance does not exist on server mdm-sr)
    mdm-sr :  hostname of mdm server
    FYI: The mdm server and mdm console running on the same host .
    Thanks
    Faris

    Hi Deep,
    restarted both DB and then MDM server, but still not working, giving same error message
    (Error mounting MDM Server, The specified SAP instance does not exist on server mdm-srv)
    FYI: The mdm server and mdm console running on the same host .
    But the DB instance is runing on the diffrent server
    Tx,
    FSS

  • Error in starting MDM Server from MDM Console

    Hi,
    I have installed SAP MDM 5.5 SP05 on Windows 2003 Server.
    When i try to start the MDM Server (i.e. MDM Service) from the MDM console it gives me the following error:
    <i>Error Starting apmdmd(MDM Server): The machine 'apmdmd' is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead. </i>
    But if i start the MDM Service manually and then mount the server, it works fine.
    Kindly help.
    Regards,
    Chintan Sheth

    It sounds to me like a problem potentially with either the permissions of the Windows user or perhaps a software firewall. The Console uses a low-level Windows API function to determine if the target machine on which MDS is installed is Windows-based. This function may be blocked by some OS or firewall-level setting. This may be the case even if you are able to use the same client machine to connect to the target machine via the Service Control Manager and start MDS from there.
    I would like to help with this problem, but I need to know a few more things:
    When the problem occurs, is the Console running on the same Windows machine as MDS?
    You mentioned Windows 2003 Server... when you run the Console on this machine, are you logged in as an Administrator of the machine? And do you still get the error when you attempt to start MDS from within the Console?
    Once MDS is started, and you mount it within the Console, are you having any other problems, such as logging in to a repository, or viewing logs?
    Is there a firewall installed on the machine or machines that the software is installed on? We may have to review the settings of the firewall, or try temporarily disabling it (on both ends, or at least on the machine running MDS), to see if the problem goes away -- then we'll know the problem is with the firewall settings.
    CLIX is a fine workaround if you can use it, but clearly this problem needs to be rectified.
    -cleo

  • Error Message in MDM Server Log

    Hi Experts,
    Can anybody tell me what could be the problems if we have the following scenario ?
    For an example: Our MDM Server is based on 5.5 SP06, MDM Server name is DFM and our repository name is MDMQ110.
    1) Checking the Reports from this Repository MDMQ110 from MDM Console, no errors and no warning. This repository can be loaded successfully and completed.
    2) Server Log has an error in message:
    Error: Service 'DFM', Schema 'MDMQ110_m000', ERROR CODE = 0,
    SELECT LENGTH(Data) FROM A2i_Misc_Blobs WHERE Id=1000
    Thanks very much for your help in advance
    Regards,
    WD

    Hi Kanstantsin,
    Thanks for your reply. I have done the stop and repair but It did not help any. By repair, there are no errors and warnings that have been fixed which I can see in the repository reports.
    The Assertion Log has come up first with the messages like:
    6426            2010/01/12 09:07:08.500               Error: Data_2 accelerator does not exist in A2i_CM_Accelerator_Status
    6426            2010/01/12 09:07:08.683               Error: Data_53 accelerator does not exist in A2i_CM_Accelerator_Status
    4884 2010/01/12 09:43:30.335   Error: KeyWord_2_F4_Leng_USA accelerator does not exist in A2i_CM_Accelerator_Status
    As soon as I run into MDM, the Server Log has come up the same messages:
    It looks like not only happened to this repository. As I can see if I load any other repository, there are the same messages in Server Log but only the repository name in the message is different.

  • 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                                                                                                                                                                                                                                                                                                                                                                       

Maybe you are looking for