12:36 p.m.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:02 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3651:
---------------------------------------
Fix Version/s: 3.0.0.GA
Assignee: John Graham
Needs fixing/looked into this and figure out what is the cause of it before we simply just
change the default ordering - maybe the client projects shouldn't use the server
runtime directly ?
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: John Graham
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:12 p.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian reassigned JBIDE-3651:
--------------------------------
Assignee: Feng Qian (was: John Graham)
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
I think these examples are for SOA platform. So we should set the JBoss server and JBoss
ESB runtime are both from SOA-P. If we do this, we can't get this issue.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Jeff DeLong commented on JBIDE-3651:
------------------------------------
The libraries are from SOA-P, that is what causes the problem.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:40 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
And the client project is a ESB project too. So it use the server runtime.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
When you import these example projects into your workspace. These projects will get their
JBoss server and ESB runtime from your workspace preference. And these projects are set to
the server and esb runtime are both the same and from jboss-as of soa-p. So you should be
sure your workspace preference are correct. If you did this, you need not add any jar to
project classpath.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:10 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
I did some changes for this and other issues. Now we can support a jboss server that must
support esb.(for example: jbossesb-server-4.4GA, jboss-as server from SOA-P)
After you import these examples into your workspace, maybe some issues. But don't
worry, you only need to do some steps to fix them:
1 set your jboss server and jboss esb runtime and remember the esb runtime name. The
server must support esb.
2 right-click on the project, and select the properties action.
3 In the opened wizard, choose Java Build Path, then click Libraries Tab, then you can
correct the jboss server and jboss esb runtime in the opened page.
4 rebuild the project, I believe you will get a correct project.
Except said as above, you need not do anything.
So, jeff, you must not add any jars to your classpath by yourself. Please test again, if
any question, please let me know
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:27 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3651:
--------------------------------------------
Feng, arent the imported projects supposed to pick up the server names/esbruntime names
the projects are created with in the first place ?
i.e. Why does the default setting affect the import ?
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
Max, yes. these imported projects will remain the the server names/esbruntime names that
were created by me in their classpath.
When you imported these projects, the server names/esbruntime names are not changed. But
maybe your workspace do not have
these server and esb runtime whose name are same to these names of these imported
projects. So you should correct them according
to your workspace.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian resolved JBIDE-3651.
------------------------------
Resolution: Done
done
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:51 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3651:
--------------------------------------------
Ok - got it ;)
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Jeff DeLong commented on JBIDE-3651:
------------------------------------
I found another jar conflict; this time with the scout jar. The JbossAS client libraries
contain scout.jar, while the esb libraries contain scout-1.0rc2.aop.jar. If scout jar is
picked up first in the runtime classpath of the client, it results in an exception using
the following property from jbossesb.properties:
<property name="org.jboss.soa.esb.registry.queryManagerURI"
value="jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire"/>
It appears the scout.jar does not understand jnp.
I think having all these jars on the classpath is a bad idea. They clearly are not all
needed, and some of them have conflicts between what is in
jboss-soa-p.4.3.0/jboss-as/server/default/deploy/jbossesb.sar/lib and
jboss-soa-p.4.3.0/jboss-as/client
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
Hi Jeff,
You are right. All the jars on the classpath is a bad way. But I do not know which jars
we need. Maybe runtime guys know that.
For this issue, I have done some changes. If you use the nightly build of jboss tools and
do the steps as above, you need not
add any jar by yourself.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3651:
--------------------------------------------
This worries me - this tells me that SOA-P has a complete inconsistent set of jars....how
can we *ever* provide a classpath container that will be useful ?
The jars we pick up from AS is what is visible to all apps on the server so how can users
that does not use the IDE figure out which jars to use ?
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:14 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Feng Qian commented on JBIDE-3651:
----------------------------------
to Jeff,
Sorry, you need not to use the nightly build of jboss tools, you only need to import the
example again. And do the steps as above.
to Max,
When all apps run on the server, they will find the class in the web-inf's lib folder
at first, secondly is the server lib. But when the apps in our tools, these jars are all
in the project's classpath, so maybe have some conflict. As jboss ws module, when we
will generate jboss ws client, we need to remove two jars from the project classpath. But
for this issue, I think we need not to care this problem because now the example can run
and we need not to add any jar by ourself.
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:56 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Jeff DeLong updated JBIDE-3651:
-------------------------------
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK 1.5.0.11,
SOA-P 4.3 (soa-4.3.0.GA). (was: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL
5, JDK 1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).)
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.3.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3651:
--------------------------------------------
if ESB would register it self to AS runtime wouldn't the AS runtime be able to
calculate the proper classloading ?
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.3.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-3651) Runtime classpath on ESB Client example results in exception
[
https://jira.jboss.org/jira/browse/JBIDE-3651?page=com.atlassian.jira.plu...
]
Anton Klimkovich closed JBIDE-3651.
-----------------------------------
Verified on 2.0.0.GA-N200902282101-H1483
Runtime classpath on ESB Client example results in exception
------------------------------------------------------------
Key: JBIDE-3651
URL: https://jira.jboss.org/jira/browse/JBIDE-3651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK
1.5.0.11, SOA-P 4.3 (soa-4.3.0.GA).
Reporter: Jeff DeLong
Assignee: Feng Qian
Fix For: 3.0.0.GA
Problem occurs when running helloworld_testclient. The following exception occurs:
Exception in thread "main"
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message
[header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
I can get the exception to go away and the client to run successfully if I add
jbossall-client to the FRONT of the Eclipse client application Run Configuration
classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB
Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there
is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime
is from SOA-P 4.3).
Not sure how to change the order of the libraries. The Run Configuration classpath uses
the project default classpath, however the libraries, etc. are listed in the reverse order
of how they are listed in the Properties - > Java Build Path -> Libraries, which
appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before
JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5697
days inactive
5731
days old
jbosstools-issues@lists.jboss.org
18 comments
4 participants
participants (4)
-
Anton Klimkovich (JIRA) -
Feng Qian (JIRA)
-
Jeff DeLong (JIRA)
-
Max Rydahl Andersen (JIRA)