1:16 p.m.
Port SOA-3001 changes to 44CP5
------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:16 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3679) Port SOA-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-3679:
----------------------------------
Component/s: Transports
Port SOA-3001 changes to 44CP5
------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3679) Port SOA-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3679.
-----------------------------------
Resolution: Done
Made a tag for this patch : GSS-SOA-3365
tcunning@localhost:GSS-SOA-3365]$ svn commit
Sending product/rosetta/src/org/jboss/soa/esb/listeners/jca/EndpointProxy.java
Sending qa/junit/src/org/jboss/soa/esb/server/MyRedeliveryAction.java
Transmitting file data ..
Committed revision 37459.
tcunning@localhost:GSS-SOA-3365]$
Port SOA-3001 changes to 44CP5
------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-3679) Port SOA-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham closed JBESB-3679.
---------------------------------
Port SOA-3001 changes to 44CP5
------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:33 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-3679) Port SOA-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham reopened JBESB-3679:
-----------------------------------
Port SOA-3001 changes to 44CP5
------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:33 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3679) Port JBESB-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3679.
-----------------------------------
Resolution: Done
Port JBESB-3001 changes to 44CP5
--------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:33 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3679) Port JBESB-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-3679:
----------------------------------
Summary: Port JBESB-3001 changes to 44CP5 (was: Port SOA-3001 changes to 44CP5)
Port JBESB-3001 changes to 44CP5
--------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:33 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-3679) Port JBESB-3001 changes to 44CP5
[
https://issues.jboss.org/browse/JBESB-3679?page=com.atlassian.jira.plugin...
]
Tom Cunningham closed JBESB-3679.
---------------------------------
Port JBESB-3001 changes to 44CP5
--------------------------------
Key: JBESB-3679
URL: https://issues.jboss.org/browse/JBESB-3679
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4 CP5
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: non-project
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5238
days inactive
5238
days old
7 comments
1 participants
participants (1)
-
Tom Cunningham (JIRA)