Mindblown: a blog about philosophy.

Problem: unknown failed. Descriptor name: [unknown].Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed..; nested exception is: BINDING.JCA-11616DBWriteInteractionSpec Execute Failed Exception.unknown failed. Descriptor name: [unknown].Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed..Please see the logs for the full DBAdapter logging output prior to this exception.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value “0” to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers. Workaround: Uncheck Support global transaction option in data source Transaction section as shown below: Best Camping Cot

Sometimes when we create SOA BPEL with define service interface later, we get the below error even if we add the receive activity. Error(52): There is not an activity (receive/pick) to start the process Error(52): Initial activity is invalid. An initial activity must be of a receive or pick activity. Error: there is no receive…