JCA Inbound adapter error

Hi everybody,
I have an ESB project which reads a file from a folder and writes it into another folder. The issue is that sometimes it works ok, but some others the in adapter fails and I get this error:
JCA inbound adapter service listener for "SUBIRA.INM.LeerCarpetaINM_RS.LeerINM" with endpoint ID "[LeerINM_ptt::LeerINM(opaque)]" has
been requested to shutdown by Resource Adapter due to fatal error. Reason : ORABPEL-11004
Error al publicar el mensaje.
Se ha producido un error al publicar el mensaje del archivo C:\FTPINM\20070402221542_82AVC00001540.dat
Compruebe la pila de errores y corrija la causa del error. Póngase en contacto con los Servicios de Soporte Oracle si no se puede
corregir el error.
Resuming it in english it would be: Error trying to publish the message. An error has occurred while publishing the file message. Check the error stack and fix it. Contact Oracle Support Services if you are not able to fix the error.
This error appears randomly, I mean, I haven't change anything in the project. Any suggestions?

Hi alex,
Cause of problem
Both OC4J running BPEL and the database adapter reached the maximum number of connections and were unable to establish new ones.
The reason for the problem is a database adapter Bug 5595347.
According to Bug 5595347, the database adapter might leave open connections behind.
The fix for Bug 5595347 is included in Patch 5638122.
Solution
To implement the solution, please execute the following steps:
Apply Patch 5638122.
References
Bug 5595347 - ORIONCMTCONNECTION NOT CLOSED IN ORABPEL~OC4J_BPEL~DEFAULT_ISLAND~1
Note 314422.1 - Remote Diagnostic Agent (RDA) 4 - Getting Started
Patch 5638122 - MERGE LABEL REQUEST ON TOP OF 10.1.2.0.2 FOR BUGS 5149866 5595347 5205630
Cheers,
Abhi...

Similar Messages

Error Using JCA AQ adapter OSB11g

Hi
i'm using aqAdapter with jca in osb11g. I followed the manual Oracle Service Bus (OSB) 10.3.1 – JCA Transport with AQ Adapter Tutorial
http://www.oracle.com/technology/sample_code/products/osb/index.html
with some little diferences, I got the service up and it is created without any problem
but when i'm going to test the service the next error is given:
<jca-transport-application-error xmlns="http://www.bea.com/wli/sb/transports/jca" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<jca-transport-error-message>Invoke JCA outbound service failed with application error</jca-transport-error-message>
<jca-runtime-fault-detail>
<eis-error-code xsi:nil="true"/>
<eis-error-message xsi:nil="true"/>
<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/nuevoAQ/AQServicio [ Enqueue_ptt::Enqueue(MESSAGE_TYPE) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
; nested exception is:
BINDING.JCA-11982
AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
Use DataSourceName property instead.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invokeOneWay(JCATransportOutboundOperationBindingServiceImpl.java:114)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendOneWay(JCATransportEndpoint.java:191)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:168)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy133.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:377)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
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.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
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(SecurityManager.java:147)
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.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/nuevoAQ/AQServicio [ Enqueue_ptt::Enqueue(MESSAGE_TYPE) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
; nested exception is:
BINDING.JCA-11982
AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
Use DataSourceName property instead.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.post(JCABindingReferenceImpl.java:201)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invokeOneWay(JCATransportOutboundOperationBindingServiceImpl.java:109)
... 36 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/nuevoAQ/AQServicio [ Enqueue_ptt::Enqueue(MESSAGE_TYPE) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
; nested exception is:
BINDING.JCA-11982
AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
Use DataSourceName property instead.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:667)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:357)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:316)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:295)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:354)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.post(JCABindingReferenceImpl.java:199)
... 37 more
Caused by: BINDING.JCA-11982
AQ_INVALID_TRANSACTION_STATE.
Unsupported adapter configuration.
XADataSourceName property is only supported for adapter usage from within a global transaction.
Use DataSourceName property instead.
at oracle.tip.adapter.aq.v2.jca.AQLocalTransaction.begin(AQLocalTransaction.java:78)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:513)
... 42 more</exception>
</jca-runtime-fault-detail>
</jca-transport-application-error>.
I really need to know what is wrong.
Any help would be apreciated
Thanks in advance.
Gustavo.

I think you have created non-XA datasource and while creating connection factory you provided the datasource name in "XADataSourceName" property. Please provide the datasource name in "DataSourceName" property instead, save and update the aqadapter deployment and try again.
Regards,
Anuj

OSB Error in deploying a project with jca file adapter

Hi,
I am facing an issue where I am getting an error when deploying a service from Eclipse. I am using OSB/SOA 11.1.1.5 2 node cluster. I have an OSB service where I am writing to a file and am using file adapater. I created a composite with file adapter to write a file then imported .jac, .wsdl and composite into eclipse and generated a business service out of .jca file. When I deploy the project from eclipse I am getting the below error and am not able to deploy the project.
Conflicts found during publish.
Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
I have FileAdapter deployed and pointed to OSB manage servers cluster. Here is a snippet of config.xml.
<app-deployment>
    <name>FileAdapter</name>
    <target>SOA_Cluster,OSB_Cluster</target>
    <module-type>rar</module-type>
    <source-path>/app/oracle/fmw/Oracle_SOA1/soa/connectors/FileAdapter.rar</source-path>
    <deployment-order>321</deployment-order>
    <plan-dir xsi:nil="true"></plan-dir>
    <plan-path>/app/oracle/shared/SOA_Cluster/dp/FileAdapterPlan.xml</plan-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
</app-deployment>
Also inside console -> deployments -> FileAdapter -> Targets and OSB_Cluster is checked also.
Here is the .jca file
<adapter-config name="writeFile" adapter="File Adapter" wsdlLocation="writeFile.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/HAFileAdapter"/>
<endpoint-interaction portType="Write_ptt" operation="Write">
    <interaction-spec className="oracle.tip.adapter.file.outbound.FileInteractionSpec">
      <property name="PhysicalDirectory" value="C:\ORACLE"/>
      <property name="Append" value="false"/>
      <property name="FileNamingConvention" value="a_%SEQ%.doc"/>
      <property name="NumberMessages" value="1"/>
    </interaction-spec>
</endpoint-interaction>
</adapter-config>
Any idea what might be wrong.
Thanks.

I already have the fileAdapter JNDI is already configured in console. The error I am getting is during the deployment
Conflicts found during publish.
Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
Thanks

BINDING.JCA-12510 JCA Resource Adapter location error in SOA 11g Suite

Hi,
I am just testing one simple SOA Application in SOA 11g Suite. Created a SOA Composite Application with one DB Adapter at designtime all worked fine with DB Adapter. But when I deploy the Application on the server I get the following error:
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/soademoDatabase'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/soademoDatabase. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ".Do I need to jndi-name in weblogic-ra.xml if so what is the exact location. Any help is appreciated.
Thanks

I did but still not able to connect now getting the following error. I went to the Weblogic Console, clicked on deployments, selected DBAdapter, clicked on configuration ,
and then I don't see outbound configurations instead it shows Outbound Connection Pools, Under Outbound Connection Pools tab I clicked on New and it asked to select Outbound Connection Group I selected the one that was already there (with JNDI eis/DB/SOADemo) and then created my JNDI which was added to the default Outbound Connection Group and in the end it asked to save the Plan.xml which I saved it under a new directory created under soa directory. But still am not able to connect.
How do I create my own Connection Group as don't want to use the defualt one out there.
After creating the JNDI Name it asks for saving the Plan.xml file. Where exactly we save this file. Are there any standards.
Why can't I update any properties when I click on the new JNDI name it takes to Settings for javax.resource.cci.ConnectionFactory --> Outbound Connection Properties but there I see a save buttn but I can't make any changes.
BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception. Missing Property: [DBManagedConnectionFactory.userName]. You may have set a property (in _db.jca) which requires another property to be set also. Make sure the property is set in the interaction (activation) spec by editing its definition in _db.jca. . ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. Is there any documentation that lists all these steps as I couldn't find it anywhere. The guide only talks abou DBAdapter but how to configure etc can't find any info. Any help is appreciated.
Thanks.

IDoc adapter inbound channel: Error Fehler beim Le

Hello,
I have a BIG problem. I want to use IDOC - XI - IDOC. I have configured the connections. But when I send the Idoc to the XI. it returns a code in the SM58 "IDoc adapter inbound channel: Error Fehler beim Le" The Message comes cut, it doesn't return all the message. In the XI doesn't give me any error, nothing. The IDOC says thta it has been sent correctly (Code 3). How can I trace the IDOC from de sender to the XI?
I wanted to use the IDOC HRMD_A06 but now i'm trying with SYIDOC to see if it passes.
Can Someone help me?
Caller Function module Target system Date Time Status text
SRGEN13 IDOC_INBOUND_ASYNCHRONOUS RHXCLNT013 07.04.2006 10:06:46 IDoc adapter inbound channel: Error Fehler beim Le
Thank you
PM

I want to know if the Connections have to have SNC?
I have read this in the note http://help.sap.com/saphelp_nw04/helpdata/en/ca/fafaf6dbc8b240b1cf4a88c40379b2/frameset.htm
Inbound and outbound connections should be secured by Secure Network Communication (SNC).
Is that correct? maybe that's why it says the that error
PM

IDoc adapter inbound channel: Error Error when reading Exchange Profile

Hello Experts,
Currently i am working on an IDOC to file scenario, in which Data will be sent from ECC server (IDOC) to an FTP server via SAP PI, but when i try to send IDOC to PI, i am getting the following error
in Transaction SM58:-
'IDoc adapter inbound channel: Error Error when reading Exchange Profile for system XID and
client 401 occurred in the IS pipeline' .
Can anyone please help me on this.
Thanks & Regards,
Amit Naik

Hello Experts,
Let me explain to you the whole scenario, We have two servers of PI, 7.1 & 7.0. Now the Java Stack of 7.0 is not working & Cache update of 7.1 is not happening.
Thats why we have linked ABAP stack of 7.0 with Java stack of 7.1. Now we can see the objects created under Java 7.1 in ABAP stack of 7.0 (SXI_CACHE).
Now we have done all the settings to create an IDOC to file scenario. All the RFCs are working fine, but when we send an IDOC from the ECC system to ABAP 7.0, we are getting the following error 'Error while reading exchange profile for system NW' in SM58 .
Now can anyone tell me what exact settings i have to change in the Exchange profile (Java stack of 7.1), so that the Java 7.1 & ABAP 7.0 connection is setup or do i need to change anything else.
Thanks & Regards,
Amit Naik

IDoc adapter inbound channel: Error Error while read

Dear All
I am sending idoc from SAP 4.6C to PI. But on SM58 I am getting an error
IDoc adapter inbound channel: Error Error when reading
Which is not complete because field length is 50 characters , double clicking on this message is asking for message class. How can i see the complete message.
Can any one send me configuration detail of receiving IDOC at PI end , I don't want send to it forward from PI.

Please clear these points.
In PI system:
1. Create RFC destination of type 3 pointing to R/3 system.
2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.
3. Using IDX2 import the IDOC meta data in to your PI system.
RFC destination to which direction , towards sender of IDOC ?
Port of which system sender system or receiver system?
What about configuration in Integration Directory , is there any configuration required on integration repository and on integration directory.
What will be the procedure of seeing complete message on SM58.
-->In PI system while ur creating the RFC destination of type 3 give the hostname and system number of ur R/3 system ie SAP 4.6 c.
-->In PI create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system and in that RFC destination option, maintaine the destinatination name which we created using sm59.
-->coming to IR you need to create the:
                    1. Receiver data type.
                    2. receiver message type
                    3. receiver message interface. No need to create the above 3 for sender.
                   4.while mapping source is your Idoc and target is your receiver message type.
                   5. while interface mapping source is Idoc and target is receiver interface.
-->Coming to ID no need to create sender communication channel and no need to create sender agreement.
-->create receiver communication channel and receiver agreement.
--->create Interface determination.
-->create receiver determination.
-->If message got stuck in SM58, unlock it by using double click or activate the selected message.
Thanks

IDoc adapter inbound channel: Error Connection err

Hi,
We are trying to push an IDoc from R3, it's status is green in WE02. However, the IDoc is not reaching PI.
In tcode SM58 in R3 we are getting an error "IDoc adapter inbound channel: Error Connection err". I have gone through the SAP note 940313 but was not able to figure out the exact cause of error.
Any help would be appreciated.
Regards
Pravesh

Hi,
Please check the steps for Idoc posting to SAP PI system from R/3. Probably you are missing some configuration.
Few Checks -
1. did you created Logical System using BD54?
2. Create RFC destination Type 3 for PI
3. create partner profile using we20
In Pi
Check following
1. Create RFC destination of type 3 pointing to R/3 system.
2 . create Port using the IDX1
3. Using IDX2 import the IDOC meta data
Regards
Aashish Sinha

Inbound adapter exception/error management

I was wandering is there any best practice for handling inbound adapter exceptions ? For example if I have inbound MQ-adapter and MQ-server is down how can I get some kind of exception catched from this? Only thing I've found out that it SOA Suite writes these exceptions to server log. Is the only way to catch these exception to poll the server log (using for example grep...)?
Thank you
Best Regards Tuomas

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

Error getting VARCHAR2 in an object using JCA DB Adapter.

I am facing a problem with the JCA db Adapter and i am not able to solve.
I have created an Oracle Object like:
CREATE OR REPLACE TYPE FACTURAE AS OBJECT
( MODALIDAD VARCHAR2(1),--I
TipoEmisorfactura VARCHAR2(2),--EM
Then i have created a procedure which returns the mentioned type;
FUNCTION FUsorgen_obtenerdatosFactura (IDFACTURA IN NUMBER,strTipoFactura IN VARCHAR2)RETURN FACTURAE
IS
Then i have created a JCA db Adapter in Jdeveloper obtaining an wsdl and a xsd schema. Both files are valid
Finally i have created a business service based on this wsdl. When i have tested this y get an xml like:
<OutputParams>
<MODALIDAD>???</MODALIDAD>
<TipoEmisorfactura>12</TipoEmisorfactura>
</OutputParams>
I have checked that executing the procedure with the same parameters the field "MODALIDAD" has value "I" so it is not null nor "???".
Have anybody an idea what is happening? Is there a known bug with personaliced objects and DB Adapter?
Best Regards.

Perhaps you could post your XSD and the instance XML that you provide for the input parameters.
The generated XML for the output parameters should look something like the following.
<OutputParameters ...>
    <FUsorgen_obtenerdatosFactura>
        <MODALIDAD> ... </MODALIDAD>
        <TipoEmisorfactura> ... </TipoEmisorfactura>
    </FUsorgen_obtenerdatosFactura>
</OutputParameters>Notice that the function name is the name of pseudo-parameter encapsulating the attributes of your object type.

Error getting VARCHAR2 in a object using JCA DB Adapter.

I am facing a problem with the JCA db Adapter and i am not able to solve.
I have created an Oracle Object like:
CREATE OR REPLACE TYPE FACTURAE AS OBJECT
( MODALIDAD VARCHAR2(1),--I
TipoEmisorfactura VARCHAR2(2),--EM
Then i have created a procedure which returns the mentioned type;
FUNCTION FUsorgen_obtenerdatosFactura (IDFACTURA IN NUMBER,strTipoFactura IN VARCHAR2)RETURN FACTURAE
IS
Then i have created a JCA db Adapter in Jdeveloper obtaining an wsdl and a xsd schema. Both files are valid
Finally i have created a business service based on this wsdl. When i have tested this y get an xml like:
<OutputParams>
<MODALIDAD>???</MODALIDAD>
<TipoEmisorfactura>12</TipoEmisorfactura>
</OutputParams>
I have checked that executing the procedure with the same parameters the field "MODALIDAD" has value "I" so it is not null nor "???".
Have anybody an idea what is happening? Is there a known bug with personaliced objects and DB Adapter?
Best Regards.

Perhaps you could post your XSD and the instance XML that you provide for the input parameters.
The generated XML for the output parameters should look something like the following.
<OutputParameters ...>
    <FUsorgen_obtenerdatosFactura>
        <MODALIDAD> ... </MODALIDAD>
        <TipoEmisorfactura> ... </TipoEmisorfactura>
    </FUsorgen_obtenerdatosFactura>
</OutputParameters>Notice that the function name is the name of pseudo-parameter encapsulating the attributes of your object type.

Jca Ftp Adapter - XA support

Hi,
I have requirement to move files between two ftp servers. I have implemented this using OSB services configured with jca ftp adapter. After reading the files from the source system the adapter is configured to delete the file from source directory. While moving the files if the target system is unreachable the transaction should roll back and the file should remain in the source directory.
Can this be achievable using jca ftp adapter. Does ftp adapter have XA capability?
Thanks,
Sai.

OSB's ftp transport is transactional on the inbound side ( proxy service side) .. So you could use this.. Make sure you are not configuring any reply actions in any of the error handlers.. When route error occurs make sure the error is allowed to propagate back to the system error handler.. .
By default osb's ftp transport will retry only once and then move the file to the error directory. If you want to change this behaviour say retry infinitely or retry after a delay , you have to change the dleivery failure settings for the internal JMS queue WLSAdmin Console --> JMSModules --> jmsResources --> wlsb.internal.transport.task.queue.ftp_auto_2 ( wlsb.internal.transport.task.queue.ftp_auto_3 and so on) Delivery Failure and change redelivery delay and redelivery limit.
Note OSB's ftp transport is not transactional outbound(business service) , so you might get only "At-least once" (and not "exactly-once") quality of service using this ..

BEA-381951 JCA inbound request only invocation failed

Hi there,
I'm using OSB to create a series of interfaces between a couple of applications.
Since this Monday for some reason whenever I try to test my application on the server I'm getting the error <BEA-381951> JCA inbound request only invocation failed (I'll post the stack trace on the end of the post).
I'm using the OEPE to create the OSB services and publish them... The publish functions OK and the OEPE says that it is synchronized with the server, but when I try to do Run on server to test my Services it takes long time without anything happening and at the end appears a message saying that there was an unknown error. If I try again to Run on Server nothing happens. After this I can't even access the web sbconsole, it stays loading and nothing happens...
I don't know if it is relevant but I have 3 kinds of services, some are listening to a Table in a Data Base, other are Webservices and other listen to a Topic.
Can anybody help me?
Best Regards,
Daniel Alves
The stack trace of the error is the following:
<Error> <JCATransport> <SERVER NAME> <AdminServerOsb> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-002646A254E4F8C4A298> <a7acfb4f5f216892:-40aaf1d3:12a130eb503:-8000-000000000001fa2f> <1280220202417> <BEA-381951> <JCA inbound request only invocation failed, exception: java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportException: com.bea.wli.sb.pipeline.PipelineException
java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportException: com.bea.wli.sb.pipeline.PipelineException
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.sendMessage(JCATransportInboundOperationBindingServiceImpl.java:411)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.invokeOneWay(JCATransportInboundOperationBindingServiceImpl.java:126)
     at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.post(JCAInboundRequestListener.java:40)
     at oracle.tip.adapter.sa.impl.inbound.JCAInboundListenerImpl.onMessage(JCAInboundListenerImpl.java:171)
     at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:462)
     at oracle.tip.adapter.db.InboundWork.onMessageImmediately(InboundWork.java:2008)
     at oracle.tip.adapter.db.InboundWork.onMessageDirectly(InboundWork.java:1957)
     at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1849)
     at oracle.tip.adapter.db.InboundWork.transactionalUnitDirectly(InboundWork.java:1569)
     at oracle.tip.adapter.db.InboundWork.processDeliveryException(InboundWork.java:1810)
     at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1523)
     at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:720)
     at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:581)
     at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:44)
     at weblogic.work.ContextWrap.run(ContextWrap.java:41)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: com.bea.wli.sb.transports.TransportException: com.bea.wli.sb.pipeline.PipelineException
     at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:197)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:390)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl$4.run(JCATransportInboundOperationBindingServiceImpl.java:407)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl$4.run(JCATransportInboundOperationBindingServiceImpl.java:405)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.sendMessage(JCATransportInboundOperationBindingServiceImpl.java:405)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.invokeOneWay(JCATransportInboundOperationBindingServiceImpl.java:126)
     at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.post(JCAInboundRequestListener.java:39)
     at oracle.tip.adapter.sa.impl.inbound.JCAInboundListenerImpl.onMessage(JCAInboundListenerImpl.java:171)
     at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:462)
     at oracle.tip.adapter.db.InboundWork.onMessageImmediately(InboundWork.java:2008)
     at oracle.tip.adapter.db.InboundWork.onMessageDirectly(InboundWork.java:1957)
     at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1849)
     at oracle.tip.adapter.db.InboundWork.transactionalUnitDirectly(InboundWork.java:1569)
     at oracle.tip.adapter.db.InboundWork.processDeliveryException(InboundWork.java:1810)
     at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1523)
     at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:720)
     at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:581)
     at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
     at weblogic.work.ContextWrap.run(ContextWrap.java:41)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: com.bea.wli.sb.pipeline.PipelineException
     at com.bea.wli.sb.pipeline.PipelineContextImpl$SynchronousListener.onError(PipelineContextImpl.java:1345)
     at com.bea.wli.sb.transports.LoadBalanceFailoverListener.onError(LoadBalanceFailoverListener.java:439)
     at com.bea.wli.sb.transports.CoLocatedMessageContext.sendResponse(CoLocatedMessageContext.java:305)
     at com.bea.wli.sb.transports.CoLocatedMessageContext.close(CoLocatedMessageContext.java:285)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.wli.sb.transports.Util$4.invoke(Util.java:351)
     at $Proxy166.close(Unknown Source)
     at com.bea.wli.sb.pipeline.MessageProcessor.finishProcessing(MessageProcessor.java:422)
     at com.bea.wli.sb.pipeline.RouterCallback.onReceiveResponse(RouterCallback.java:108)
     at com.bea.wli.sb.pipeline.RouterCallback.run(RouterCallback.java:183)
     at weblogic.work.ContextWrap.run(ContextWrap.java:41)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>

Hi,
Did you find a solution for this? I am stuck with this error. can you please help

UMS Adapter Error during ums adapter endpoint activation

Hi,
I have well configured the usermessagingdriver-email on SOA11g driver for both imam/stmp protocols, but on deploying process with UMS Adapter (Reciving Notification) i got the error "UMS Adapter Error during ums adapter endpoint activation" with following
javax.resource.ResourceException
at oracle.tip.adapter.ums.inbound.UmsEndpoint.registerUmsAccessPoints(UmsEndpoint.java:212)
at oracle.tip.adapter.ums.inbound.UmsEndpoint.registerApplication(UmsEndpoint.java:99)
at oracle.tip.adapter.ums.inbound.UmsEndpoint.<init>(UmsEndpoint.java:92)
at oracle.tip.adapter.ums.inbound.UmsPollerEndpoint.<init>(UmsPollerEndpoint.java:47)
at oracle.tip.adapter.ums.UmsResourceAdapter.endpointActivation(UmsResourceAdapter.java:183)
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:492)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:649)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:633)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:387)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:593)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:445)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:409)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:334)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:140)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:103)
at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:348)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:824)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:773)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Also when I have received email in my mailbox nothing is happened, no new istance has created, but on start soa server 11g all messages which are currently located in mailbox had been processed and ( on usermessagingdriver-email I can saw Messages Received Successfully)
Thanks,
Milos

Hi Saravana
Have you tried : http://technology.amis.nl/2012/05/18/proces-email-with-the-new-ums-adapter-of-soa-suite-ps5/ ?
Regards
A

Inbound Adapter / 'Sink' failing for Content Server on Subscription Client

I am running into an issue in configuring the Outbound - Inbound Adapters for Connection Server / Subscription Client against Content Server. The details are below. Would sincerely appreciate if anyone can help with this.
I have installed a Oracle UCM setup together with two Content Server instances (Contribution instance and Live instance), a Connection Server and a Subscription Client - all within the same virtual machine on top of Windows XP SP2 OS and Oracle 10g Database.
I have further configured the Outbound Adapter on the Connection Server and the Inbound Adapter on the Subscription Client. All installation and configuration has been done following the step-by-step process from the relevant installation guides.
We have tested the connectivity between the Connection Server and the Subscription Client for a simple file-based content source and it works fine - i.e., files added to a directory registered as a source on connection server are retrieved and sent to the subscription client and received there successfully / dropped in the specified target client directory.
However, this transfer fails for the Content Server Outbound-Inbound Adapter connectivity. We have an Archive in Content Server registered as a "CNSArchive" and exporting successfully to the CNS Server. The registered outbound adapter is successfully able to receive these updates and are visible through the Connection Server
interface. The subscription client is also apparently able to receive these updates
correctly and writes them to the specified folder/directory on the client;
however fails to "batch load" these and reports a failure writing to the
Content Sink.
What we would like is for the ability to establish end-to-end connectivity between the contribution content server instance and the live content server using the connection server + outbound adapter on the sending end together with the subscription client + inbound adapter together on the receiving end. This is failing.
I have double checked the cns.oracle.config (connection server config), siclone.config (subscription client config), and the source content server's configuration (config.cfg), and all seems to be well. Not really sure therefore what is causing this.
Here is a snippet of the error trace that keeps showing up in the subscription client logs ...
[May 18 21:18:34] VERBOSE: scheduler: waiting to run job ICE Connection in 0:00:33.000 ...
[May 18 21:18:34] VERBOSE: replicator: response: 200 OK for Url:http://192.168.131.65:8891/42/E%3a%2fapps%2foracle%2fucm%2fserver%2fweblayout%2fgroups%2fpublic%2fdocuments%2fucmdocs%2fcpseven.pdf
[May 18 21:18:34] INFO: replicator: opened connection http://192.168.131.65:8891/42/E%3a%2fapps%2foracle%2fucm%2fserver%2fweblayout%2fgroups%2fpublic%2fdocuments%2fucmdocs%2fcpseven.pdf in 0:00:00.130
[May 18 21:18:34] ERROR: replicator: ContentSink reported failure to add item.
[May 18 21:18:34] ERROR: replicator: Telling all sinks to rollback changes
[May 18 21:18:34] ERROR: replicator: crawl failed
[May 18 21:18:34] VERBOSE: scheduler: job completed:ICE Request: 43

Don't know if anyone is still having problems with this, but just in case...
I was getting a similar error. I had an Event Viewer record (It wasn't a Warning or an Error, just an Information) reading:You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with this version of Windows. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I installed SQL SP4 and it corrected the problem

JCA Inbound adapter error

Similar Messages

Maybe you are looking for