Detail datastore

I am using a detail datastore as described in the Oracle Text Reference guide (standard master/detail relationship). When a search is executed, I am looking at ways of returning only the detail line(s) where the hits were found. Any suggestions would be apprecieated.
thanks

http://technet.oracle.com:89/ubb/Forum27/HTML/000315.html

Similar Messages

  • Problems with the detail datastore

    I am trying to create a context index using detail datastore.
    My detail table contains the column called
    TEXT of type
    ORDSYS.ORDSOURCE and I am trying to index a blob inside this type.
    When I specify a preferences I use
    ctx_ddl.set_attribute('my_detail_pref', 'detail_text',
    'text.localdata');
    When I try to create an index using these preferences I get the following error from Oracle:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: interMedia Text error:
    DRG-10582: column TEXT.LOCALDATA does not exist in table DOCTABLE
    If I create an index using default datastore everything works fine,
    example:
    SQL> create index ind_new on doctable(text.localdata) indextype is ctxsys.context;
    Index created.
    Help appreciated.
    Leonid
    null

    pagination for tables on Pages is not working properly... for 5.5 version... Any solution???

  • Performance of detail_datastore

    Hi everybody,
    I am planning to set up an article archive.
    The articles consist of different parts (title,headline,synopsis,bodytext...).
    I think about two different methods to solve the problem.
    1. Use a Master Detail Realtion for the Article (Master contains Title..., Detail
    contains body Parts). To create the context index I use the detail_Datastore preference.
    2. I use also the Master Detail Relation,
    create a dummy XML File out of the article content with a trigger and index the dummy File with a direct datastore.
    Solution 2 is more work, but what about query performance? Is the query performance of the detail datastore ok?
    Indexing is not the Problem.
    Anybody any experience??
    Thanks
    Detlev

    Hi everybody,
    I am planning to set up an article archive.
    The articles consist of different parts (title,headline,synopsis,bodytext...).
    I think about two different methods to solve the problem.
    1. Use a Master Detail Realtion for the Article (Master contains Title..., Detail
    contains body Parts). To create the context index I use the detail_Datastore preference.
    2. I use also the Master Detail Relation,
    create a dummy XML File out of the article content with a trigger and index the dummy File with a direct datastore.
    Solution 2 is more work, but what about query performance? Is the query performance of the detail datastore ok?
    Indexing is not the Problem.
    Anybody any experience??
    Thanks
    Detlev

  • IS validation rule export to Data Services invalidates datastore logon details

    I am exporting an Information Steward 4.2 SP1 validation rule to Data Services 4.2 SP1; a part of the rule is a database table lookup. In the export process, IS creates a new datastore with that table I'm doing the lookup against.
    The problem is that every time I re-export the rule after changing it, I have to maintain db server logon details in that generated datastore again.
    Have I missed a configuration step, or it's just an error to raise through OSS?

    Hi Apurva ,
    Now I got Variable Id  and Varibale Value i have give From Data Fields of VC  .
    When i click on Button Export To  Excel it gives
    SET_VARIABLES_STATE is Correctly placed For
    VARIABLE_VALUES VARIABLE_VALUE
    if give 
    VARIABLE_VALUES VARIABLE_VALUE instead of SET_VARIABLES_STATE it is giving  No MetaData  is available for VARIABLE_VALUES VARIABLE_VALUE
    it throws like .
    please help in this regard.
    I Have given The Formuls AS Below
    "pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?QUERY=zmp_prodn_mtef_ccp_1&BI_COMMAND_1-BI_COMMAND_TYPE=VARIABLE_VALUES VARIABLE_VALUE&BI_COMMAND_1-VARIABLE_VALUES VARIABLE_VALUE_1-VARIABLE_TYPE=VARIABLE_INPUT_STRING&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE_TYPE-VARIABLE_INPUT_STRING="&2009&"&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE=0P_FYEAR&BI_COMMAND_3-BI_COMMAND_TYPE=EXPORT&BI_COMMAND_3-EXPORT_FORMAT=XLS&BI_COMMAND_3-null="
    Regards ,
    venkat p

  • Error: License File Exception (check the log file for details): ENT_PE_NODE not found in datastore

    Hi;
    i have install 2 MCS 7816 (publisher and suscriber) with call manager version 6.1, i have load the files licenses for the publisher and the phones, but when i load the file license for the suscriber in publisher server i had the error messeage :
    Error : License File Exception (check the log file for details): ENT_PE_NODE not found in datastore
    what s the solution.
    Thanks for your help

    Hello,
    I seen this issue before, all you have to do is Contact Cisco Licensing team. In order to generate new licenses for your server.
    Thanks,

  • Host, Cluster and Datastore Details

    Hello,
    Kindly seeking help in combine the scripts in the attached text file. We have a requirement to find the below details of a collection of VMs. VM Names are in a text file.
    VMName, VMHost, ClusterName, Datastore Location.
    Also we need to have the list is sorted with VMNames
    Thanks in Advance
    Rajesh

    Is there any way to use autosize, as the long datastore names trunctes.
    Try Autosize
    Get-VM (Get-content c:\temp\vms.txt) | Select-Object -Property @{Name='VMName';Expression={$_.Name}},VMHost,@{Name='ClusterName';Expression={$_.VMHost.Parent}}, @{"Name"="Datastore"; expression={($_.DatastoreIDList | %{(Get-View -Property Name -Id $_).Name}) -join ", "}} | FT -AutoSize
    Try wrapping?
    Get-VM (Get-content c:\temp\vms.txt) | Select-Object -Property @{Name='VMName';Expression={$_.Name}},VMHost,@{Name='ClusterName';Expression={$_.VMHost.Parent}}, @{"Name"="Datastore"; expression={($_.DatastoreIDList | %{(Get-View -Property Name -Id $_).Name}) -join ", "}} | FT -Wrap
    If possible, can we use sort-object with VM Names ?
    Yep, just pipe to Sort-Object
    Get-VM (Get-content c:\temp\vms.txt) | Select-Object -Property @{Name='VMName';Expression={$_.Name}},VMHost,@{Name='ClusterName';Expression={$_.VMHost.Parent}}, @{"Name"="Datastore"; expression={($_.DatastoreIDList | %{(Get-View -Property Name -Id $_).Name}) -join ", "}} | Sort VMName
    Also, can we use export-csv to export the out put to excel ?
    Yep, Just pipe to Export-CSV
    Get-VM (Get-content c:\temp\vms.txt) | Select-Object -Property @{Name='VMName';Expression={$_.Name}},VMHost,@{Name='ClusterName';Expression={$_.VMHost.Parent}}, @{"Name"="Datastore"; expression={($_.DatastoreIDList | %{(Get-View -Property Name -Id $_).Name}) -join ", "}} | Export-CSV -NoTypeInformation C:\temp\VMExport.csv

  • Can not set up Web Service datastore using HTTPS WSDL DS 4.1

    I have been trying to configure a Web services data store to connect to an HTTPS Wsdl file
    Here is some background.
    DS Version: 14.1.1.210
    Job Server Windows 2008
    if i configure the datastore and leave the field for Keystore path empty, i get the following error:
    Error loading [https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CorporateRecruitmentSourceService&wsdl]:
    org.apache.xmlbeans.XmlException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CorporateRecruitmentSourceService&wsdl
    If i put the path C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\mds\DSJavaKeyStore.keystore for the keystone path,
    I get the following different error:
    An error ocurred while importing metadata: WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'https://stgbbaaviation.taleo.net/enterprise/soap?ServiceName=CandidateService&wsdl':javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building faild: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (BODI-1111469) (BODI-1112446)
    I have recreated the DSJavaKeyStore.keystore and added in additional certificates but nothing seems to work.
    As a workaround i saved the wsdl file down to the local machine (I'm currently running designer on the job server machine)
    i can then save the web service datastore and import the wsdl function.  but at runtime I get the following error:
    There is no response for the web service <getMessageByIdentifier>. Ensure that the network, web server, and service are running
    properly. Also ensure that the service client call time out is set properly.
    I have edited the
    C:\Program Files (x86)\SAP BusinessObjects\Data Services\ext\webservice-c\axis2.xml file as follows for the sections that are listed in the documentation:
        <transportReceiver name="https" class="axis2_http_receiver">
            <parameter name="port" locked="false">6060</parameter>
            <parameter name="exposeHeaders" locked="true">false</parameter>
        </transportReceiver>
    <!-- Uncomment the following with appropriate parameters to enable the SSL transport sender.
             Also make sure that the appropriate transport receiver is enabled above.-->
        <transportSender name="https" class="axis2_http_sender">
            <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
            <parameter name="xml-declaration" insert="false"/>
        </transportSender>
        <parameter name="SERVER_CERT">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_cert.crt</parameter>
        <parameter name="KEY_FILE">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_privatekey.pem</parameter>
        <parameter name="SSL_PASSPHRASE">C:\Program Files (x86)\SAP BusinessObjects\Data Services\ssl\server\DS_server_privatekey_password.txt</parameter>
    I'm not sure what i'm doing wrong.  Not much detail in the documentation on what to enter for the Keystore path in the Datastore config.
    also it is unclear if i don't have the correct certifications added to the keystore.
    Please help

    Hi Prashant,
    Please refer the below KBA related to BODI-1111469 issue in SAP Data Services 4.1 Support Pack 1 Patch 1 (Version 14.1.1.284).
    ADAPT01664699
    An importing operation from a WSDL that has a recursive import of a schema would fail with the error:  "An error occurred while importing metadata: Unknown JNI error... (BODI-1111469)”. This issue has been fixed in this release.
    1804623 - Release Notes for SAP BusinessObjects Data Services 4.1 Support Pack 1 Patch 1 (Version 14.1.1.284)
    https://service.sap.com/sap/support/notes/1804623
    Thanks,
    Daya

  • Error during activation of DSO - Activation of M records from DataStore obj

    Hi All,
    Below is the error i am getting while activating the DSO, Even though similar post on this topic, solution not mentioned, any solution greatly appreciable.
    When -
    During Activation of DSO
    State of DSO -
    Request become "RED", It is available for reporting, some records in Active table, some in new table and some in new table.
    Job Log -
    Error when inserting the data record for data package
    Process 000105 returned with errors
    Error when inserting the data record for data package
    Process 000106 returned with errors
    Process 000107 returned with errors
    Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
    Log for activation request ODSR_4GXKRYHMY97R9U62M6U52XXXY data package 000001...000001
    Errors occured when carrying out activation
    Analyze errors and activate again, if necessary
    Activation of M records from DataStore object Z_DSPO terminated
    Report RSODSACT1 ended with errors
    Job cancelled after system exception ERROR_MESSAGE
    Detail log -
    Error when inserting the data record for data package                                                  106
    Message no. RSODSO_PROCESSING002
    Diagnosis
    Failed to store data records persistently. Possible causes are:
    You tried to save a record that is already stored in the database.
    This error only occurs with DataStore objects with option "Unique Data Records".
    A unique index was created for the table of active data.
    You can check this in the Data Warehousing Workbench by choosing "Display" for the DataStore object and opening the "Indexes" folder.
    There is a technical problem on the database.
    Thanks,

    HI PT,
    I am also getting the same error like i have loaded the data into DSO and tried to activate the init request but it has become red and checked in log found that there are some SID Generation errors so please give me the step by step solution.
    SID Generation
    Data Package 000056
    Data Package 000064.
    Thanks in advance,
    Jay

  • 11g issue in handling file datastore from different server

    Hi All,
    In ODI 11g we have standalone agent as well as weblogic server agent. In our case master/workrep and weblogic server agent is installed in one of the linux server Say (A).
    We have a scenario to pick the file from one of the different linux box SAY (B). We have child agent running on that box and it is associated with the main weblogic agent under load balancing.
    While setting the topology information for file datastore it just need the driver name and path. At run time how odi will pick the respective file from that server
    Eg:File in location: /app/soa/uo1/testfile/test.txt(B)
    File path:/app/soa/uo1/testfile/test.txt(B)
    ODI Client will start the execution using the Server A weblogic agent. How ODI will route the control to child agent and try to find the file in ServerB and not in server A.
    in my case it is going to server A and saying file doesnot exist......
    Is it really possible to assign the proper server detail, so that we can make sure that execution will happen properly. I am not sure about the weblogic agent and how it control the execution. I think in my case its weblogic agent which is trying to look for the file in server A, where it is installed and thus failing.
    Control is not passing to the proper child agent as expected?
    Any idea?

    There is a difference in your understanding of the load balancing and the way it is implemented in ODI agents.
    In your case, the weblogic agent exists on Server A and hence it expects that the file also be visible to the agent and be local to server A.
    Load balancing comes into picture when there are too many connections for Agent A and it shares its load with other agents. This logic of passing control is within the agent and when file systems come into picture, the filesystem should be visible to all the agents.
    There is no concept of parent-child agents. The agents are simply load-share agents.
    So, Load balancing is not going to give you what you want.
    In your case, you should execute the job using Agent on server B so that appropriate filesystem can be accessed.

  • Updating Physical Length of Datastore in Models

    How to update, the physical length of any datastore in models.
    Used Column.Setlength(length), Its updating only the Logical Length. Need to update the physical aswell
    Thanks in advance

    We are doing a Reverse Engineering on Models, when we are going in that way, Datatype, physical length and logical length is setting to default value. To update those details we are using ODI SDK.
    Its updating only the datatype and logical length. Physical length remains the default value.
    If there is no separate method to update physical length, Is there any other way of doing this ? either in reverse engineering models without setting it to default values?
    Thanks

  • Invalid DataStore object name /BIC/B0000173: Reason: No valid entry in tabl

    Hi gurus,
         I recently transported the 0FI_GL_10 datasource to preproduction. when i am trying to load the data in PrePod we are getting this error message.
    <b>Invalid DataStore object name /BIC/B0000173: Reason: No valid entry in table RSTS</b>
    Any help is appreciated with points.

    any more detailed messages,sm21 or st22??
    did you try doing RSRV on the datastore object??
    are you using the nw2004s data flow??
    if using 3.x data flow ,skip PSA and try reloading it.
    Hope it Helps
    Chetan
    @CP..

  • Problem with Datastore Tier Rate Factors

    Hi all,
    I have problem with Chargeback Datastore Tiers. I have three different datastore types and
    I want to charge them seperately. To do this, I created three datastore tiers and moved that datastores to them.
    For all three datastore tiers, I assigned different rate factors For example;
    Datastore Tier 1 : 3.00
    Datastore Tier 2 : 2.00
    Datastore Tier 3 : 1.00
    I expect to see different storage costs for VMs but nothing changes.
    Then I moved all datastores to the folder ungrouped and assigned rate factors to datastores one by one according to tier structure.
    After doing that I have got expected cost reports for some of the VMs but some of the datastores didn't reflect the rate factors to the cost report again.
    What can the problem be? Is there any known issue for that?
    If you can help me, I will be glad.
    Best regards,

    Hi,
       There should not be an issue. Could you please let us know more details about cost configuration and report generation?
    1. What is the duration of the cost configuration? (start time and end time).
    2. What is the duration of the report generation?
    The rate factors for datstores/tiers store historical changes as well as tier to datstore mappings also store historical changes.. If a datastore is part of a tier for some time, the rate factor of tier will be applicable for the datastore for that time. If its moved out of tier, the specific rate factor set on the datastore will be applicable.
    For example, if a datastore is part of tier 1 from time lines t1 and t2.
    and its in ungrouped from t2 to t3.
    If you generate a report from t1 to t3, tier 1 rate factor is applied for t1 to t2 and datastore rate factor is applied from t2 to t3.
    One thing to ensure that is you have not set any rate factors in the chargeback hierarchy for the VM or its ancestors.
    The precedence order is
    1. if a rate factor is set at VM level in the hierarchy for Storage computing resource, it will be taken.
    2. If its not set on the VM, the ancestors are looked from the immediate parent to root of the Chargeback hierarchy.
    3. If the both are not set, the datastore or tier rate factor is looked into based on whether datastore is tiered or not.
    One more thing is to generate report using a cost model which has usage based billing policy.
    Regards,
    Hemanth

  • In ODI_DEMO model, couldn't find trg_customer table and the parameters_FILES datastore

    I'm following the odi-12c-getting-started-guide-2032250. But after I imported the demo environment, I couldn't find the parameters_FILES datastore. and under the Sales Administrator datastore, I couldn't find the trg_Customer table that I already created. Can anybody tell me why? thanks in advance.

    Hi
    First of all, drag and drop odisqlunload tool in package
    1) select odisqlunload > in property window enter below details
    Target File: provide any .txt or .xls file with location (in my case I given .xls file which i created already in d:\Error_records location)
    JDBC Driver: oracle.jdbc.driver.OracleDriver
    JDBC URL: jdbc:oracle:thin:@hoostname:port:sid (provide you DB hostname / port and SID details)
    User: provide target DB username
    Password: enter terget Db password
    File Format: Delimited (as per requirement choose the format, I choosen as Delimited type)
    SQL Query: select * from E$_TRG_CUSTOMER (Don't give double quotes for E$ table)
    and keep rest of the parameter as it is.
    For more info..
    http://gerardnico.com/doc/odi/webhelp/en/ref_tools/snpssqlunload.html
    Hope this may helps you
    Regards,
    Phanikanth

  • Could not create/access the TopLink Session. This session is used to connect to the datastore.

    We are getting the below error in our production server & also other servers(UAT, Staging). Only option is to restart the OSB server.
    Test connection is working fine and able to connect the database without any issue. We have enabled connection leak profiling and also, provided the inactive time outs , still does not work. Need your suggestion for the below error.
    ***endpoint***:https://extzwsdev.zurichna.com/services/RiskAnalysis-v1***
    Payload<soapenv:Envelope    xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/"    xmlns:ris = "http://webservices.zurich.com/zsoa/nac/underwritingmanagement/riskanalysis-v1_0"    xmlns:zsoa = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/zsoa"    xmlns:com = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/common"    xmlns:con = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/contractandspecification"    xmlns:fin = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/financialservicesagreement"    xmlns:par = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/party"    xmlns:act = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/activityconditionplace">    <soapenv:Header/>    <soapenv:Body>        <ris:calculateTargetPolicyRateChangeByProductGroup>            <ris:insurancePolicySearchCriteria>                <con:externalReference>1151638</con:externalReference>            </ris:insurancePolicySearchCriteria>        </ris:calculateTargetPolicyRateChangeByProductGroup>    </soapenv:Body></soapenv:Envelope>
    ***RTOneService Output Response*** <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-380001: [invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            ... 32 more
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:152)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            ... 1 more
    Caused by: BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.db.exceptions.DBResourceException.createRetriableException(DBResourceException.java:676)
            at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:645)
            at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:314)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:918)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            ... 38 more
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(Unknown Source)
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.getMetaData(Unknown Source)
            at weblogic.jdbc.wrapper.Connection.getMetaData(Connection.java:479)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:122)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:92)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.&lt;init>(NameEnquoter.java:59)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:705)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            ... 1 more
    .</faultstring><detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>[invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            ... 32 more
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:152)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            ... 1 more
    Caused by: BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.db.exceptions.DBResourceException.createRetriableException(DBResourceException.java:676)
            at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:645)
            at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:314)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:918)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            ... 38 more
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(Unknown Source)
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.getMetaData(Unknown Source)
            at weblogic.jdbc.wrapper.Connection.getMetaData(Connection.java:479)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:122)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:92)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.&lt;init>(NameEnquoter.java:59)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:705)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            ... 1 more
    .</con:reason><con:location><con:node>RouteNode1</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
    !!! Exception occurred <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-380001: [invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            ... 32 more
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkMa

    Its hard to say what is going on.  Though the message says the error is in obtaining a TopLink session, the exception stack has nothing to do with TopLink, and the error seems to be coming from oracle.tip.adapter.db.toplinkext.NameEnquoter.init() directly calling weblogic.jdbc.wrapper.Connection.getMetaData() on what must be a stale or closed connection.  This looks like a DB adapter application, so you might want to post this question there as they might be able to help configure your datasource appropriately for the application.
    Best Regards,
    Chris

  • Query SQL datastore with XML where clause source

    Hope I am in the right place.  New to Bus Obj Data Services Designer....I have cerated xml schemas, added it to the page as an xml source in.  Mapped a test xml file and all is well there.  I have added a query that grabs the xml.
    I need to then query the MS SQL datastore ans use  the data form the xml query as the where clause.  How is this done?  Or do I put a query on the datastore for all the data in a table then do anotehr query filtering one with the other?  seems like that would be rather heavy and low performance.  The results will then be sent back out as xml (schema and test file already set up as an xml out)
    Thanks!

    Thanks for the tips.
    I'm trying to implement this option, using your ViewDefHelper.
    I´m running into a problem though. After I create my dynamic View Object using a ViewDef, I need to create some view links.
    So I get the AttributeDefs of the columns (source, and destination) from the method findAttributeDef (which is the whole purpose of performance in my post). This method is returning the correct Attribute Def, but when I create the view Link with the method createViewLinkBetweenViewObjects(java.lang.String vlName,
    java.lang.String accessorName,
    ViewObject master,
    AttributeDef[] srcAttrs,
    ViewObject detail,
    AttributeDef[] destAttrs,
    java.lang.String assocClause)
    My destination query is generating the where clause as:
    null = ?
    Any Ideas what I'm doing wrong ?
    Thanks again.
    John.

Maybe you are looking for