This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 30th, when you will be able to use this site as normal.

    Forum Stats

  • 3,890,039 Users
  • 2,269,775 Discussions
  • 7,916,823 Comments

Discussions

DBAdapter fails to poll with Caused by BINDING.JCA-11630 Incompatible Features Exception. The follow

1048955
1048955 Member Posts: 1
edited Apr 22, 2014 5:57AM in SOA Suite Discusssions

DBAdapter fails to poll with Caused by BINDING.JCA-11630 Incompatible Features Exception. The following combination of features: NumberOfThreads>1, xADataSourceName!=null, dataSourceName=null is not supported.

==================

exception stack trace

=====================

####<Jan 18, 2014 10:46:28 PM PST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <sdclnap177> <stg01_osb_server02> <[ACTIVE] ExecuteThread: '101'

for queue: 'weblogic.kernel.Default (self-tuning)'> <osbadmin> <> <60b41741115644c9:47e9f253:143a702cf6a:-7ff0-000000000005adeb> <1390

113988116> <BEA-000000> <<oracle.tip.adapter.db.InboundWork handleException> Encountered a fatal exception while polling. Will continu

e polling but with minimal logging. Please investigate the fault and manually stop polling from the console if in development and this

appears to be a modeling mistake. BINDING.JCA-11624

DBActivationSpec Polling Exception.

Query name: [PollRecordsCalInterfaceEventsSelect], Descriptor name: [PollRecordsCalInterfaceEvents.EdrcCwRtThrottleVw]. Polling the dat

abase for events failed on this iteration.

Caused by BINDING.JCA-11630

Incompatible Features Exception.

The following combination of features: NumberOfThreads>1, xADataSourceName!=null, dataSourceName=null is not supported.

Caused by configuring incompatible features.

Please try dataSourceName!=null. As a warning this combination may still work but not in all use cases, the implementation may be limi

ted, or possible interactions have not been fully tested.

.

This exception is considered not retriable, likely due to a modelling mistake. This polling process will shut down, unless the fault

is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).

at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:690)

at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:656)

at oracle.tip.adapter.db.exceptions.DBResourceException.inboundReadException(DBResourceException.java:491)

at oracle.tip.adapter.db.InboundWork.handleException(InboundWork.java:983)

at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:568)

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:545)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused by: BINDING.JCA-11630

Incompatible Features Exception.

The following combination of features: NumberOfThreads>1, xADataSourceName!=null, dataSourceName=null is not supported.

Caused by configuring incompatible features.

Please try dataSourceName!=null. As a warning this combination may still work but not in all use cases, the implementation may be limi

ted, or possible interactions have not been fully tested.

===========================================================================================================

We tried various combinations for the dataSourceName but none works..Urgent response would be appreciated.

Tagged:

Answers

  • ydes
    ydes Member Posts: 14

    Hello,

    did you find any solution for your problem? We face the same issue, and I cannot find anything in Oracle Support

  • Raj__K
    Raj__K Member Posts: 412 Silver Badge

    I think the DB JCA connection factory is not proper(xADataSourceName!=null, dataSourceName=null). Try recreating the JCA connection factory with either XA or NonXA datasource.

  • ydes
    ydes Member Posts: 14

    Thanks for the reply,

    in my setup

    1. get the error, but the poller still works!

    2. the settings in JCA adapter are : xADataSourceName set, and not dataSourceName (so the values are clear, only one type of DS is defined)

    3. (in our design) we need an XA datasource as we have a transaction in place.

    any other ideas?

    cheers

    Yannis

This discussion has been closed.