Hide Forgot
Patch Instructions: PATCH NAME: SOA-3365 PRODUCT NAME: SOA-P VERSION: 4.3.0CP5 SHORT DESCRIPTION: Resolve could not find file error. LONG DESCRIPTION: There was definitely a change in the JCA integration at some point, for which JBESB-3001 was the fix. The problem was that the inflow was no longer being associated with the correct context classloader. This results in an error 'Could not find file'. MANUAL INSTALL INSTRUCTIONS: Replace the .jar jbossesb-rosetta.jar with the supplied version. Please replace them in your servers in the following directories: deploy/soapui-client.sar/jbossesb-rosetta.jar, jbossesb.sar/lib/jbossesb-rosetta.jar COMPATIBILITY: N/A DEPENDENCIES: N/A SUPERSEDES: None SUPERSEDED BY: None CREATOR: Rick Wagner DATE: 09/14/2011 Patch Repository Link: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=8513 Support Case Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007s4vM&sfdc.override=1 project_key: SOA There was definitely a change in the JCA integration at some point, for which JBESB-3001 was the fix. The problem was that the inflow was no longer being associated with the correct context classloader. This is causing the following error: WARNING: org.jboss.soa.esb.services.routing.MessageRouterException: Could not locate file [from_tid.drl], neither as a file on the local filesystem, on the classpath nor as a URL. org.jboss.soa.esb.actions.ActionProcessingException: org.jboss.soa.esb.services.routing.MessageRouterException: Could not locate file [from_tid.drl], neither as a file on the local filesystem, on the classpath nor as a URL.
Link: Added: This issue relates to JBESB-3679
jbossesb-rosetta.jar built from SOA-P 4.3 CP05 CR2 plus ESB .../tags/GSS-SOA-3365/
Attachment: Added: jbossesb-rosetta.jar
reproducer
Attachment: Added: helloworld.zip
QE finished testing of the patch. Regression test suit before the patch: job 1281 Regression test suit after the patch: job 1282 MD5 sum of patched file: 624f83c84728b20024d318fbb2b44ba7 jbossesb-rosetta.jar I attached reproducer. The reproducer is helloworld quickstart configured with jms-jca provider and action in action pipeline outputs contextclassloader. Before the patch output is: 11:27:16,342 INFO [STDOUT] Classloader: org.jboss.mx.loading.UnifiedClassLoader3@5ba88001{ url=file:/home/fnguyen/work/soaplatform/products/esb/jboss-as/server/production/tmp/deploy/tmp2165187439273570232jms-ra.rar ,addedOrder=41} After applying the patch: 11:31:00,882 INFO [STDOUT] Classloader: org.jboss.mx.loading.UnifiedClassLoader3@5549f0e{ url=file:/home/fnguyen/work/soaplatform/products/esb/jboss-as/server/production/tmp/deploy/tmp8532767073507318566Quickstart_helloworld.esb ,addedOrder=51} This verifies that fix indeed sets correct classloader.
Patch Instructions: Added: PATCH NAME: SOA-3365 PRODUCT NAME: SOA-P VERSION: 4.3.0CP5 SHORT DESCRIPTION: Resolve could not find file error. LONG DESCRIPTION: There was definitely a change in the JCA integration at some point, for which JBESB-3001 was the fix. The problem was that the inflow was no longer being associated with the correct context classloader. This results in an error 'Could not find file'. MANUAL INSTALL INSTRUCTIONS: Replace the .jar jbossesb-rosetta.jar with the supplied version. Please replace them in your servers in the following directories: deploy/soapui-client.sar/jbossesb-rosetta.jar, jbossesb.sar/lib/jbossesb-rosetta.jar COMPATIBILITY: N/A DEPENDENCIES: N/A SUPERSEDES: None SUPERSEDED BY: None CREATOR: Rick Wagner DATE: 09/14/2011
This patch is applicable to JBoss SOA-P 4.3.0 CP05 . It is available for download from the following location: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=8513
Patch Repository Link: Added: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=8513
Resolved.