Tuesday, January 5, 2010

Oracle BPEL & ESB - Error & Resolution

I think its better to start my blogging with the errors that I have faced during development and their resolutions which worked for me. I am very excited to bring forth the first blog of my life. Your positive response will encourage me to share more and more of my knowledge with you. Sometimes for an error there are more than one resolution, I'll be highly thankful to you if you can share the other resolutions which are not present in this blog.

Error 1: XML-22036: (Error) Cannot convert result tree fragment to NodeSet
Detail: This error comes in the transformation file. This is due to the version mismatch of stylesheet.
Resolution: Change the version of stylesheet from '1.0' to '2.0' . Now redeploy your process.

Error 2: Invalid xml document.
According to the xml schemas, the xml document is invalid.
Please make sure that the xml document is valid against your schemas.
Resolution: One cause of this error could be when you set “validateXML” property “true”.
Please make it false and then retry.
Goto BPELConsole-> ManageBPELDomain ->Set validateXML =false.

Error 3: oracle.xml.parser.v2.XMLParseException: PI with the name 'xml' can occur only in the beginning of the document.
Resolution: Check the transformation file and ensure that "<?xml version="1.0" encoding="UTF-8" ?>" is the first line in all the XSL file.

Error 4: failed due to: null; nested exception is: javax.resource.ResourceException
Resolution: Add <property name="cacheWSIFPort">false</property>
in the partnerlink binding in bpel.xml of the partnerlink invoking which this error is coming.
Another resolution is to try clearing the wsdl cache at BPELConsole->BPEL Process-> Clear the wsdl cache.

Error 5:The Method 'commit' Cant Be Called When a Global Transaction is Active Displayed in log.xml
Resolution: Amend ESBDataSource to local in the $ORACLE_HOME/j2ee//config/data-sources.xml
i.e. <managed-data-source name="ESBDataSource" connection-pool-name="ESBPool"
jndi-name="jdbc/esb" tx-level="local" /><managed-data-source name="ESBDataSource" level="local">

Error 6:ESB Services disappeared
Check for "connection pool is full" in $OracleHome/opmn/logs/*soa*
Error 7:Unable to delete or register ESB on ESB console
Resolution: Login to EM console
Goto Cluster Topology -> Application Server ->oc4j_soa -> Application:default -> ResourceAdapter:OracleASjms ->Edit Connection Factory: OracleASjms/MyXATCF -> ConnectionPool:private
Increase Maximum Connections to 100.
Posted by at

9 comments:

  1. SuryaJanuary 6, 2010 at 12:23 AM

    Hi Shanatanu ,

    Can you pls elaborate the reasons for applying the above fixes for the above errors ?

    Regards
    Surya

    ReplyDelete
  2. AnonymousAugust 24, 2011 at 1:13 AM

    Thanks for this excellent post on errors in Oracle XSLT. It really helped.

    ReplyDelete
  3. AnonymousNovember 16, 2011 at 7:09 AM

    XML-22036: (Error) Cannot convert result tree fragment to NodeSet - This is not always resolved by your solution of changing the stylesheet version from 1.0 to 2.0.

    In my case, I had refactored (renamed) a scheme type I was using as a flow variable. The refactor was not picked up in the xsl file's metadata

    ReplyDelete
  4. Shantanu SrivastavaNovember 20, 2011 at 10:46 PM

    Thanks for sharing the information. Can you please share the steps you performed so that refractor can be picked by XSL?

    ReplyDelete
    Replies
    1. AnonymousMarch 20, 2012 at 4:52 AM

      Error 1: XML-22036: (Error) Cannot convert result tree fragment to NodeSet
      Detail: This error comes in the transformation file. This is due to the version mismatch of stylesheet.

      When ever i have this problem is because a variable has changed..either its namespace or something else.
      Solution: create again the transformation with a new xsl name, even if test, build and deployment at jdeveloper seems fine.

      Delete
    2. Shantanu SrivastavaJuly 19, 2012 at 8:40 AM

      Thanks a lot for sharing this information :)

      Delete
  5. AnonymousOctober 24, 2012 at 8:09 PM

    very helpful..Thanks.

    ReplyDelete
  6. RameshJanuary 31, 2013 at 3:49 PM

    Thanks you so much.
    I was struggling with Error 1: XML-22036: and your blog helped me in resolving the isssue.

    ReplyDelete
  7. Ankit ChhabraFebruary 16, 2013 at 7:15 PM

    Hi Shantanu,

    Thanks for the providing this resolution for Error1: XML-22036, but may i know why this happens, as i was able to test my XSL in jdev, but getting error in server.

    I am using SOA 11g, 11.1.1.5

    Thakns.
    Ankit

    ReplyDelete

Subscribe to: Post Comments (Atom)