Rollback fault thrown while invoking a Proxy Service

Hi,
I am getting strange problem while invoking a proxy service.
the operation on the service takes a list of customer numbers in the input.
When the number of customer numbers is 10-20 it works fine but when I increase the customer numbers in the list to 200 it starts failing with the below error.
*<<BaseCubeSessionBean::logError > Error while invoking bean "cube delivery": Rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown from the BPEL code.
This exception was caused by a bpelx:rollback fault being thrown. The user had directed the BPEL engine to roll back the current JTA transaction.
There is no action recommended.
ORABPEL-02180
Rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown from the BPEL code.
This exception was caused by a bpelx:rollback fault being thrown. The user had directed the BPEL engine to roll back the current JTA transaction.
There is no action recommended.*
The cause for this error is as below
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds
I am clueless why the service is behaving different in both the cases.
the endpoint of the webservice is the same in both the case and below is the sample request which I am sending.
<v001:CustomerRequest>
<v0011:CustomerNumberList>
<v0011:CustomerNumber>12802582</v0011:CustomerNumber>
<v0011:CustomerNumber>612391615</v0011:CustomerNumber>
<v0011:CustomerNumber>189322879</v0011:CustomerNumber>
<v0011:CustomerNumber>251524232</v0011:CustomerNumber>
<v0011:CustomerNumber>208522415</v0011:CustomerNumber>
<v0011:CustomerNumber>812603453</v0011:CustomerNumber>
<v0011:CustomerNumber>12068921</v0011:CustomerNumber>
<v0011:CustomerNumber>252053284</v0011:CustomerNumber>
<v0011:CustomerNumber>191672097</v0011:CustomerNumber>
<v0011:CustomerNumber>248131656</v0011:CustomerNumber>
<v0011:CustomerNumber>8513869</v0011:CustomerNumber>
</v0011:CustomerNumberList>
<!--Optional:-->
<v001:SynchToA>false</v001:SynchToA>
<!--Optional:-->
<v001:SynchToB>false</v001:SynchToB>
<!--Optional:-->
<v001:SynchToC>false</v001:SynchToC>
<!--Optional:-->
<v001:SynchToR>true</v001:SynchToR>
</v001:CustomerRequest>
Can anybody provide any pointers please... :|

Hi-
Can you try by increasing your JTA time out parameter, it seems to be a time out exception not sure if this could fix the issue. Anyways give a try and let us know the result.
To increase the JTA parameter login to console --> Home --> Click on Domain under Domain Configuration -- > JTA and set the parameter Timeout Seconds to 1000 and then give a try.
Let us know the result

Similar Messages

  • Error while executing the proxy service

    Hi,
    I have a procedure which uses a database link to access my tables. And business service will invoke this procedure through JCA.
    We have created a datasource (Driver : non - XA for Service connections). However, while executing the proxy service it gives me below error.
    Do i need to change the type of driver. Can anybody please help me on this.
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header xmlns:com1="com:gm:vehicleengineering:engineeringworkorder:ewostatus:types:ewostatusschema:1:0" xmlns:com="com:gm:common:utilities:types:servicecontrol:1:0">
    <com:ServiceControl>
    <com:Service>EWOStatus</com:Service>
    <com:Version>1.0</com:Version>
    <com:ConsumerID>CID</com:ConsumerID>
    <com:MessageID>MID</com:MessageID>
    <com:SentTimeStamp>2008-09-28T21:49:45</com:SentTimeStamp>
    </com:ServiceControl>
    </soapenv:Header>
    <soapenv:Body>
    <soapenv:Body>
    <com:ServiceFault xmlns:com="com:gm:common:utilities:types:servicefault:1:0">
    <com:FaultCode>SOAFLT-999</com:FaultCode>
    <com:FaultString>GeneralError</com:FaultString>
    <com:FaultActor>Server</com:FaultActor>
    <com:FaultDetail>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/VehicleEngineering/EngineeringWorkOrder/EWOStatus/V1/WSDL/jcaEWOStatus_1_0_0 [ GetEWOStatus_ptt::GetEWOStatus(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'GetEWOStatus' failed due to: Interaction processing error.
    Error while processing the execution of the SP_GETEWOSTATUS API interaction.
    An error occurred while processing the interaction for invoking the SP_GETEWOSTATUS API. Cause: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Internal error: Cannot obtain XAConnection java.lang.ClassCastException: oracle.jdbc.driver.T4CConnection
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1684)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
         at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:126)
         at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94)
         at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:327)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:295)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.reconnect(DatasourceAccessor.java:558)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1437)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.incrementCallCount(DatasourceAccessor.java:303)
         at oracle.tip.adapter.db.DBConnection.getTopLinkSQLConnection(DBConnection.java:335)
         at oracle.tip.adapter.db.transaction.DBTransaction.beginInternal(DBTransaction.java:126)
         at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:93)
         at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:248)
         at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:534)
         at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:257)
         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:572)
         at sun.reflect.GeneratedMethodAccessor771.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 $Proxy142.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.CoLocatedMessageContext$1.run(CoLocatedMessageContext.java:164)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.util.security.SecurityUtils.runAs(SecurityUtils.java:58)
         at com.bea.wli.sb.transports.CoLocatedMessageContext.send(CoLocatedMessageContext.java:157)
         at com.bea.wli.sb.transports.http.wls.HttpTransportProvider.sendMessageAsync(HttpTransportProvider.java:215)
         at sun.reflect.GeneratedMethodAccessor771.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 $Proxy122.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:151)
         at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
         at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:25)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Thanks,
    Chandana

    Make sure that you are using non-xa datasources and in DBAdapter outbound connection pool configuration provide the data source JNDI in "dataSourceName" property instead of "xADataSourceName" property. Update the DBAdapter after changing configuration.
    Regards,
    Anuj

  • How to invoke ALSB proxy service externaly

    Hello,
    I.m trying to understand the ALSB and stumble across an issue and hope one of you guys (from BEA) can help out?
    I've created the services from the Mortgage services tutorial successfully and now I'm trying to invoke the proxy services externally. By externally I mean as a partner link from within Oracle BPEL. So far this does not work. The error message states a missing protocol in the service URL. I checked this and it is true: the wsdl of the proxy service contains only a relative path (/loan/gateway1), so the protocol and server name and port are missing. Further, I tried to change the URI of the proxy service, but ALSB does only allow a relative URI.
    My question is: what am I missing so the proxy service can be invoked externally?
    I am on the right solution path to invoke a proxy service instead of a business service, right!?
    Thank in advance.
    Regards,
    Harm Verschuren

    I tracked down the problem. The proxy service and the business service it routes to use rpc encoded. The RPC encoded message comes to the proxy service from BPEL which transmits it without modification to the business service. The WLS web service that impements the business service is unable to decode the message persumably because it did not like the way BPEL encoded the message. Below is the message part that BPEL sent: All the xsitype attributes are part of RPC encoding.If you use the alsb test console to pass this message directly to the business service, you will see the decoding error thrown by wls.
    <loanRequest xmlns:pns0="java:normal.client"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:ns0="http://example.org"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <pns0:Name xsi:type="xsd:string">Joe</pns0:Name>
    <pns0:SSN xsi:type="xsd:string">123456789</pns0:SSN>
    <pns0:Rate xsi:type="xsd:double">3</pns0:Rate>
    <pns0:Amount xsi:type="xsd:long">50000</pns0:Amount>
    <pns0:NumOfYear xsi:type="xsd:int">20</pns0:NumOfYear>
    <pns0:Notes xsi:type="xsd:string">test</pns0:Notes>
    </loanRequest>

  • Using SAML policy while invoking a web service

    I have to invoke a webservice which is secured using the policy wss10_saml_token_client_policy.
    In order to achieve the above i have creates a stub using JAX-WS and while invoking the web service I pass the policy as a SecurityFeature.Code snippet given below:
    SecurityPolicyFeature[] securityFeatures = new SecurityPolicyFeature[] { new SecurityPolicyFeature(
                        getValueFromPropertyFile("oracle/wss10_saml_token_client_policy"))};
    SomeStub stub =(UserManagementPortTypev1_0)SomeService.getPort("...","....",securityFeatures );
    Once deployed in weblogic and when i invoke the service, the soap request formed is correct. It creates for me the soap header with the correct security nodes. The header formed is like below:
    <S:Header>
    <work:WorkContext xmlns:work="http://oracle.com/weblogic/soap/workarea/">rO0ABXoAAAJDADBvcmFjbGUuZG1zLmNvbnRleHQuaW50ZXJuYWwud2xzLldMU0NvbnRleHRGYW1pbHkAAAFPAAAAKXdlYmxvZ2ljLndvcmthcmVhLlNlcmlhbGl6YWJsZVdvcmtDb250ZXh0AAABSaztAAVzcgAxd2VibG9naWMud29ya2FyZWEuU2VyaWFsaXphYmxlV29ya0NvbnRleHQkQ2Fycmllcv1CAh9z5wpPAwACWgAHbXV0YWJsZUwADHNlcmlhbGl6YWJsZXQAFkxqYXZhL2lvL1NlcmlhbGl6YWJsZTt4cHcEAAAAAXNyAEFvcmFjbGUuZG1zLmNvbnRleHQuaW50ZXJuYWwud2xzLldMU0NvbnRleHRGYW1pbHkkU2VyaWFsaXphYmxlSW1wbAAAAAAAAAAAAwABTAARbVdMU0NvbnRleHRGYW1pbHl0ADJMb3JhY2xlL2Rtcy9jb250ZXh0L2ludGVybmFsL3dscy9XTFNDb250ZXh0RmFtaWx5O3hwdykAJzEuMDAwMEl6T0lYQ0swam9PTE1pcDJpZTFEbUNMdjAwMDAwMjt2MHh3AQF4ACZ3ZWJsb2dpYy5kaWFnbm9zdGljcy5EaWFnbm9zdGljQ29udGV4dAAAAX8AAAAyd2VibG9naWMuZGlhZ25vc3RpY3MuY29udGV4dC5EaWFnbm9zdGljQ29udGV4dEltcGwAAAAiMDAwMEl6T0lYQ0swam9PTE1pcDJpZTFEbUNMdjAwMDAwMgAAAAAAAAAAAAAA</work:WorkContext>
    <wsse:Security S:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <saml:Assertion AssertionID="SAML-L0r20MS5CV0y7B6zHnGX5w22" IssueInstant="2011-05-10T05:03:49Z" Issuer="www.oracle.com" MajorVersion="1" MinorVersion="1" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">
    <saml:Conditions NotBefore="2011-05-10T05:03:49Z" NotOnOrAfter="2011-05-10T05:08:49Z"/>
    <saml:AuthenticationStatement AuthenticationInstant="2011-05-10T05:03:49Z" AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password">
    <saml:Subject>
    *<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">anonymous</saml:NameIdentifier>* <saml:SubjectConfirmation>
    <saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
    </saml:SubjectConfirmation>
    </saml:Subject>
    </saml:AuthenticationStatement>
    </saml:Assertion>
    </wsse:Security>
    </S:Header>
    The node NameIdentifier is supposed to be populated with the logged in user id, which will be picked up from JAAS principal.
    Now I am invoking the service hosted in weblogic from outside using JSON protocol, I do not have a portal ready to invoke the service.
    My question is, is there any way in which i can replicate/ simulate the JAAS principal such that the nameidentifier is populated even when invoked from outside. THis is a requirement from testing perspective.

    Hi,
    Thanx it is working now.
    BTW can you give me some urls with info of this kind of setting which i need to do for other kind of integarions in J2EE platform.Sorry if i am asking too much as i am a starter in this technology.

  • Catching and rethrowing a SOAP Fault from an OSB 11g Proxy service

    Hello,
    We have a chain of proxy services (that last one of which calls a business service) in our 11.1.1.6 OSB project.  At one of the lower levels, we successfully throw a fault like this:
    <soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Fault xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
        <soap:faultcode>SOAP-ENV:Client</soap:faultcode>
        <soap:faultstring>Non-Existent User</soap:faultstring>
        <soap:faultActor>Client who consumed this Web Service operation</soap:faultActor>
        <soap:detail>
          <sc:UserNonExistentFault xmlns:sc="http://xmlns.sc.com/Services/V1">
            <sc:CustomerNumber>12345</sc:CustomerNumber>
          </sc:UserNonExistentFault>
        </soap:detail>
      </soap:Fault>
    </soapenv:Body>
    In the proxy service which calls this proxy service, I tried to catch this fault in an Error Handler so that I could confirm that it's available for me to re-throw back up the chain.  Curiously, the proxy service which calls that proxy service cannot see that fault.  But rather it sees what appears to be an OSB-overridden fault:
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
      <con:errorCode>BEA-380000</con:errorCode>
      <con:reason>com.bea.wli.sb.pipeline.PipelineException</con:reason>
      <con:details>
        <err:ErrorResponseDetail xmlns:err="http://www.bea.com/wli/sb/errors">
          <err:response-metadata xsi:type="sb:SBResponseMetaDataXML" xmlns:sb="http://www.bea.com/wli/sb/transports/sb" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <tran:headers xsi:type="sb:SBResponseHeadersXML" xmlns:tran="http://www.bea.com/wli/sb/transports"/>
            <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
            <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
          </err:response-metadata>
        </err:ErrorResponseDetail>
      </con:details>
      <con:location>
        <con:node>PipelinePairNode</con:node>
        <con:pipeline>PipelinePairNode_request</con:pipeline>
        <con:stage>GetCustomerByNumber</con:stage>
        <con:path>request-pipeline</con:path>
      </con:location>
    </con:fault>
    I have tried printing out the values of $body, $fault, $outbound and $inbound from the calling proxy service's Error Handler just to see if our <sc:UserNonExistentFault> is nested anywhere therein.  Unfortunately, it is nowhere to be found.
    How can we force OSB to NOT override our faults with OSB-framework faults and, instead, just throw our custom fault all the way up the chain and back to the consumer?
    Thank you,
    Michael

    I think I figured this out.
    In proxyService-2, build the <soap:Fault> and assign it to the body, then Reply with Failure (as you mentioned above).
    When proxyService-1 receives this, it will still be in the $body variable.  But the $fault variable is now populated with a BEA-38000 error.  It seems that as long as the $fault variable has data in it, then the OSB system will throw that instead of my fault (ignoring the <soap:Fault> I put into the body).
    So what I did was to Delete the $fault variable in the error handler of proxyService-1, then Reply with Failure (again).
    It would seem as if the inner workings of OSB has some logic like:
    if $fault is not null, throw the BEA-####### fault.  Otherwise, return the contents of the $body.
    By removing the fault, I effectively got to that "else/otherwise" condition.
    Of course, the Reply with Failure is still needed to ensure that an HTTP 500 error is passed with the fault (per the SOAP specification).
    Cheers!
    Michael

  • How to invoke a proxy service from a java client

    Hi all,
    how could I invoke a proxy service from a java client ?
    The proxy service type is 'any xml service' with http protocol.
    For a proxy with web service type I can export the related WSDL and generate the java client source.
    With 'any xml service' there is no associated wsdl and I'm wondering how to do that.
    Thanks
    ferp

    Hi Ferp,
    I used ClientGEN to generate client files from WSDL deployed in ALSB. You can also use Axis for client file generation.
    You need to know the WSDL URL. Generate Client files from WSDL URL.
    Sample ANT Script
    <project name="simple-web" default="mytask" basedir=".">
    <taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" classpath="C:\bea92\weblogic92\server\lib\weblogic.jar"/>
    <target name="mytask" description="Generate web service client">
              <clientgen wsdl="http://<hostname>:<port>/URL?WSDL"
         destDir="src"
         packageName="com.client.mytask"
         classpath="${java.class.path}" />
         </target>
    </project>
    Use the following JAVA Code,
    try {
         ActivationService service = new ActivationService_Impl("http://<hostname>:<port>/url?WSDL");
    client = service.getActivationServicePort();
    } catch (Exception ex) {
    // Handle Exception
    client.activateNumber();
    Let me know if you need any more information.
    Thanks,
    Suman.

  • Custom WS Policy with Service account in OSB while invoking a https service

    Hi,
    I need your help on one of my issue in invoking an https service from OSB. I read through various posting and tried the below steps in this forum
    -Added the certificate for the https site to soa domain
    -Registered the https webservice as a Business service
    -Registerd a proxy service on top of this Business service
    -In the service call out on Proxy service I did a replace operation on the entire soap header with the below string
    <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsse:UsernameToken wsu:Id="UsernameToken-4" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
              <wsse:Username>sysuser@yahoo</wsse:Username>
              <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ABIHAIKLPLKLPMLERLER</wsse:Password>
         </wsse:UsernameToken>
    </wsse:Security>
    </soapenv:Header>
    -After doing all the above steps my call out worked from the test console, If you see closely the userid(sysuser@yahoo) and password(ABIHAIKLPLKLPMLERLER) is hard coded here.
    I need a way to mask the credentials and have the user pass them when they invoke the proxy service. I read through some posting and it was listed that we can create a custom policy and attach that custom policy to the Business service. But my problem here is the userid has an extra char @, so I wasn't able to create the user account with those credentials in OSB, but I was able to create the userid and password using a service account. Iam not sure how I can use this service account along with the custom policy.
    Can you please provide me a suitable approach, which will solve my issue. I appreciate your time and help
    Thanks
    Jagan.

    Hi,
    Below are the steps followed
    - OSB Proxy service has 'oracle/wss_username_token_service_policy' attached to it.
    - Iam invoking this from BPEL. BPEL process has 'oracle/wss_username_token_client_policy' attached.
    - I can invoke the osb proxy from bpel by passing credentials - No Issues.
    Now I need to put some authorization restriction to the proxy service, so only specific users can access that.
    -I used Role=Admin as a policy condition restriction under security in Proxy service.
    -Then I went to proxy test console and I added the 'oracle/wss_username_token_client_policy' credentials and weblogic/xxxxx at Transport section and I was able to invoke the process. Here weblogic has a Admin Role.
    -I cannot invoke the same proxy service from BPEL in Jdeveloper now.
    All Iam trying to do is to protect my proxy by authrorization policy.
    Thanks
    Jagan.

  • Detail; The fault returned when invoking the web service operation

    Hi,
    We are getting below errors from Coldfusion, I am not a coldfusion expert engg. so unable to trace it futher..kindly suggest some move to get this resolve.
    Detail; The fault returned when invoking the web service operation is:<br> <pre>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server faultSubcode: faultString: java.lang.reflect.UndeclaredThrowableException faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.lang.reflect.UndeclaredThrowableException at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221) at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:10 87) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch( Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(U... ''</pre>
    Message: Cannot perform web service invocation getStudentByNRIC.
    StackTrace: coldfusion.xml.rpc.ServiceProxy$ServiceInvocationException: Cannot perform web service invocation getStudentByNRIC. at coldfusion.xml.rpc.ServiceProxy.invokeImpl(ServiceProxy.java:230) at coldfusion.xml.rpc.ServiceProxy.invoke(ServiceProxy.java:143) at 

    I expected something like:
    http://localhost:8500/opensource/QBWC_Shell.cfc?wsdl
    Apart from that, your code looks right.

  • 'owspe:PolicyAccess' error while invoking ADF BC Service Interface

    Hi,
       I have deployed a custom ADF BC Service Interface application to a standalone weblogic server. On invoking the service interface i get the following error in response.
    <env:Envelope
      xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
      <env:Fault
        xmlns:owspe="http://schemas.oracle.com/ws/policy-enforcement-2007-06">
       <faultcode>owspe:PolicyAccess</faultcode>
       <faultstring>PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(@appliesTo~="WS-Service()")(policysets:global/%)" is queued for later retrieval. </faultstring>
       <faultactor/>
      </env:Fault>
    </env:Body>
    </env:Envelope>
    I have deployed the same .ear file to my local weblogic server and got no error while invoking the WS.
    Please suggest if any configuration needs to be done at weblogic server or to the ADF application.
    Regards,
    Himanshu

    Hi Timo,
               No Luck.. Still getting same error. My ADF BC Custom Service Interface deployed on integrated weblogic server works fine.When i deploy the same EAR to Standalone weblogic server then i'm getting following error on invoking WS method.
    <env:Envelope
      xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
      <env:Fault
        xmlns:owspe="http://schemas.oracle.com/ws/policy-enforcement-2007-06">
       <faultcode>owspe:PolicyAccess</faultcode>
       <faultstring>PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(@appliesTo~="WS-Service()")(policysets:global/%)" is queued for later retrieval. WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/wss_http_token_service_policy" is queued for later retrieval. </faultstring>
       <faultactor/>
      </env:Fault>
    </env:Body>
    </env:Envelope>
    Could it be related to some Security: Roles or policies ?
    Regards,
    Himanshu

  • Could not create/access the TopLink Session.While invoking OSB proxy.

    Hi,
    While testing an OSB proxy ,which uses a multi datasource to connect to a remote database, from the sbconsole.I am getting exceptions and it is not able to create/access the TopLink Session.
    I have checked the multi datasource jndi name ,which is correct.
    The stack trace which I am getting while invoking the service is posted below:
    oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/CRN_CommonServices/SaveTransactionBSV2 [ SaveTransactionBSV2_ptt::SaveTransactionBSV2(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'SaveTransactionBSV2' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    ; nested exception is:
    JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception.
    Missing Property: [DBManagedConnectionFactory.userName].
    Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
    at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:225)
    at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundBindingServiceImpl.invoke(JCATransportOutboundBindingServiceImpl.java:136)
    at com.bea.wli.sb.transports.jca.JCAOutboundMessageContext.sendRequestResponse(JCAOutboundMessageContext.java:152)
    at com.bea.wli.sb.transports.jca.JCAOutboundMessageContext.send(JCAOutboundMessageContext.java:113)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:464)
    at sun.reflect.GeneratedMethodAccessor249.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:82)
    at $Proxy76.sendMessageAsync(Unknown Source)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:543)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:478)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:544)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:422)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:583)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatchSync(PipelineContextImpl.java:466)
    at stages.transform.runtime.WsCalloutRuntimeStep$WsCalloutDispatcher.dispatch(WsCalloutRuntimeStep.java:1401)
    at stages.transform.runtime.WsCalloutRuntimeStep.processMessage(WsCalloutRuntimeStep.java:236)
    at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
    at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
    at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:866)
    at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:866)
    at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
    at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:866)
    at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:191)
    at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
    at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:508)
    at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:506)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
    at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:505)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:263)
    at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:68)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:125)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:123)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:128)
    at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:441)
    at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:169)
    at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:136)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:572)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/CRN_CommonServices/SaveTransactionBSV2 [ SaveTransactionBSV2_ptt::SaveTransactionBSV2(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'SaveTransactionBSV2' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    ; nested exception is:
    JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception.
    Missing Property: [DBManagedConnectionFactory.userName].
    Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
    at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:619)
    at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:331)
    at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:220)
    ... 57 more
    Caused by: JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception.
    Missing Property: [DBManagedConnectionFactory.userName].
    Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
    at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:473)
    at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:216)
    at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:638)
    at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:457)
    at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:222)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:1001)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:232)
    at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:463)
    ... 59 more
    Caused by: javax.resource.spi.InvalidPropertyException: Missing Property Exception.
    Missing Property: [DBManagedConnectionFactory.userName].
    Make sure the property is set in the interaction (activation) spec by editing its definition in the wsdl.
    at oracle.tip.adapter.db.exceptions.DBResourceException.missingPropertyException(DBResourceException.java:348)
    at oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:932)
    at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:413)
    ... 64 more
    Looking forward for your help.
    Thanks a lot in advance.
    Sumit

    Have you created XA data source? If yes then make sure that in connection factory you are assigning the JNDI name of data-source in XAdataSource property (NOT in datasource property). Also make sure that your datasource is up and running and you are updating the dbadapter after creating connection factory.
    Regards,
    Anuj

  • Extra Tag Getting Added while invoking a Web service

    Hi all,
    We are facing an issue while trying to invoke a web service. We are assigning values to invoke input variable of the invoke. The issue is that while invoking an Extra element named “input” is getting added.
    For Eg: The required one is
    <messages>
    <invoke_Webservice_Input>
    Payload
    </invoke_Webservice_Input>
    </messages>
    But what is getting passed is :
    <messages>
    *<input>*
    <invoke_Webservice_Input>
    Payload
    </invoke_Webservice_Input>
    *</input>*
    </messages>
    Due to this, the invoke is failing and we are not able to proceed. The error which we are getting is "*exception on JaxRpc invoke: unexpected null*"
    If any has faced similar issues, please share your experience.
    PS: The same wsdl is working in other environments. only thing we changed is the Endpoint URI and that endpoint URI is also accessible.
    Thanks
    Mohan

    can u re import the wsdl into the process and then change the endpoint uri... undeploy the previous process.. bounce the server and then deploy the new process and try

  • Client Authentication error while invoking portal web service.

    Hi All,
    I have created a java portal web service from portal service using NWDS, I am getting client authentication error while invoking the service.
    Please tell me where to enter client authenticity details.
    regards
    Santosh

    hi,
      check whether you have the UME permissions for accessing this webservice.
    Rdgs,
    Guru

  • User Name and Password in weblogic realm while invoking a web service

    Hi,
    I deployed a rpc web service using WLS 7.0 SP2 in HP-UX 11 environment. When I
    invoke the web service through my browser (IE 6.0) using the web services url,
    it brings my service method correctly. From there, if I click the invoke button
    it asks me for a network user name and password under "weblogic" realm??? If I
    provide the admin user credentials (which I supplied while creating my domain)
    it is not accepting that it keeps popping up this network user password window
    over and over. Not sure which username/password I have to provide here to see
    the result of my service.
    If I try to invoke the web service through my client (static) I am getting a connection
    refused exception. I guess either way, I am not able to access my web service.
    In the attached file, I have cut and pasted the client stack trace as well as
    the server log trace from weblogic.
    Any ideas would be highly appreciated.
    Thanks,
    Ganesh
    [errorstacktrace.txt]

    I think the client is not able to do a HTTP POST
    to the WLS server but it can do a HTTP GET.
    I dont know why.
    http://manojc.com
    "Ganesh" <[email protected]> wrote in message
    news:3eba91bc$[email protected]..
    >
    Hi,
    I deployed a rpc web service using WLS 7.0 SP2 in HP-UX 11 environment.When I
    invoke the web service through my browser (IE 6.0) using the web servicesurl,
    it brings my service method correctly. From there, if I click the invokebutton
    it asks me for a network user name and password under "weblogic" realm???If I
    provide the admin user credentials (which I supplied while creating mydomain)
    it is not accepting that it keeps popping up this network user passwordwindow
    over and over. Not sure which username/password I have to provide here tosee
    the result of my service.
    If I try to invoke the web service through my client (static) I am gettinga connection
    refused exception. I guess either way, I am not able to access my webservice.
    In the attached file, I have cut and pasted the client stack trace as wellas
    the server log trace from weblogic.
    Any ideas would be highly appreciated.
    Thanks,
    Ganesh

  • XA Exception while invoking the Web Service

    I'm getting the following exception frequently while invoking the webservice hosted in OC4J:
    -4972682009633467115com.evermind.server.rmi.OrionRemoteException: Transaction was rolled back: Error in transaction: javax.transaction.xa.XAException: Commit (onePhase) failed.
    at ProvisionCBCMRemote_StatelessSessionBeanWrapper2206.setObjectDetails(ProvisionCBCMRemote_StatelessSessionBeanWrapper2206.java:151)
    at ae.co.etisalat.cbcm.web.soh.provisioncbcm.ProvisionCBCMController.ProvisionCBCM(ProvisionCBCMController.java:76)
    at ae.co.etisalat.cbcm.web.soh.provisioncbcm.__ProvisionCBCMControllerStatelessWrapper.invokeMethod(__ProvisionCBCMControllerStatelessWrapper.java:100)
    at oracle.j2ee.ws.InvocationWrapper.invoke(InvocationWrapper.java:121)
    at oracle.j2ee.ws.RpcWebService.doPost(RpcWebService.java:342)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:792)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    at java.lang.Thread.run(Thread.java:534)
    Nested exception is:
    javax.transaction.xa.XAException: Commit (onePhase) failed.
    at com.evermind.sql.DriverManagerXAResource.ThrowXaErr(DriverManagerXAResource.java:249)
    at com.evermind.sql.DriverManagerXAResource.commit(DriverManagerXAResource.java:73)
    at com.evermind.server.TransactionEnlistment.commit(TransactionEnlistment.java:251)
    at com.evermind.server.ApplicationServerTransaction.singlePhaseCommit(ApplicationServerTransaction.java:746)
    at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:691)
    at com.evermind.server.ApplicationServerTransaction.end(ApplicationServerTransaction.java:1036)
    at ProvisionCBCMRemote_StatelessSessionBeanWrapper2206.setObjectDetails(ProvisionCBCMRemote_StatelessSessionBeanWrapper2206.java:147)
    at ae.co.etisalat.cbcm.web.soh.provisioncbcm.ProvisionCBCMController.ProvisionCBCM(ProvisionCBCMController.java:76)
    at ae.co.etisalat.cbcm.web.soh.provisioncbcm.__ProvisionCBCMControllerStatelessWrapper.invokeMethod(__ProvisionCBCMControllerStatelessWrapper.java:100)
    at oracle.j2ee.ws.InvocationWrapper.invoke(InvocationWrapper.java:121)
    at oracle.j2ee.ws.RpcWebService.doPost(RpcWebService.java:342)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:792)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    at java.lang.Thread.run(Thread.java:534)
    Anyone can help fixing this issue will be highly appreciated. thanks in advance !!

    Please help me on this !!!

  • How to specify file name while invoking the GET_ZIP_BUNDLE service

    Hello.
    The GET_ZIP_BUNDLE service by default generate zip file with name "Bundle". I wanted to change this name runtime, that is while invoking this service. How can I do it?
    The class ziprenditions.ZipRenditionsHandler most probably handle this service by the method createRenditionBundle.
    There I saw a line:
    downloadName = LocaleResources.getString("csZipRenditionBundleName", this.m_service);I have tried to print the value of csZipRenditionBundleName and I got "Bundle". I am wondering is there any way to set a value to this message key?
    I have tried this idoc function:
    <$createRenditionBundle='some_name'$>before invoking the service. But this didn't work.
    Also I have tried to change it from Java class, and for that I have defined a custom service and did:
    LocaleUtils.encodeMessage("csZipRenditionBundleName", null, "JYM");But this also not working.
    What I want is to get the zip file with the name which is the same to the files it is archiving.
    For more information, here is how I am invoking the GET_ZIP_BUNDLE service:
    I have defined a form element:
    <form action="/cs/idcplg" method="POST" id="zipBundleForm" name="zipBundleForm">
       <input type="hidden" value="GET_ZIP_BUNDLE" name="IdcService">
       <input type="hidden" value="pkg:dDocName,pkg:dID,pkg:Rendition,pkg:RevisionSelectionMethod,pkg:AuxRenditionType" name="bundleKeys">                            
    </form>And I have a button with id downloadContent and I have attached the following JavaScript with it:
    $('#downloadContent').click(function (event){
       event.preventDefault();
       var formId = "zipBundleForm";
       var counter = 0;
       var renditionType = "";
       $("#zipBundleForm").find(":hidden").each(function() {
          if($(this).attr("name").startsWith("pkg:"))
             $(this).remove();     
       $("#downloadContentForm").find('input:checkbox:checked').each(function() {
          renditionType = $(this).val();
          $(".thumbnails").find('input:checkbox:checked').each(function() {
             if($(this).attr('data-type') == 'image'){
                createHiddenInputElement(formId, "pkg:dDocName" + counter, $(this).attr("name"));
                createHiddenInputElement(formId, "pkg:dID" + counter, $(this).attr("id"));
                createHiddenInputElement(formId, "pkg:Rendition" + counter, renditionType)
                createHiddenInputElement(formId, "pkg:RevisionSelectionMethod" + counter, "Specific");                                             
                counter++;     
       $("#zipBundleForm").submit();     
    var createHiddenInputElement = function(formId, elementName, elementValue){
       var newElement = document.createElement("input");
       newElement.setAttribute("type", "hidden");
       newElement.setAttribute("name", elementName);
       newElement.setAttribute("value", elementValue);
       $("#"+formId).append(newElement);
    }Thanks in advance.

    if you want a fixed bundle name other than "bundle", you can override the localization string entry 'csZipRenditionBundleName' in a component.

Maybe you are looking for