Bug 780570 (SOA-3006) - Potential version and code mismatch between JBoss Messaging and JBoss ESB
Summary: Potential version and code mismatch between JBoss Messaging and JBoss ESB
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3006
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB, JBoss Messaging
Version: 4.3 cp05 ER1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3 CP05,4.3 CP05 ER2
Assignee: tcunning
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-05 11:32 UTC by Jiri Pechanec
Modified: 2011-05-04 23:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
4.3 CP05 ER1
Last Closed: 2011-05-04 23:18:13 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778038 0 high CLOSED ESB clients hang because of JBoss Messaging background threads 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-3006 0 None None None Never

Internal Links: 778038

Description Jiri Pechanec 2011-04-05 11:32:39 UTC 
project_key: SOA

Release details says
SOA-4.3.0.GA_CP5_CR1 for JBoss ESB and 1.4.0.SP3_CP11 for JBoss Messaging. The problem is as follows
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/platform/soa_tags/SOA-4.3.0.GA_CP5_CR1/product/rosetta/src/org/jboss/internal/soa/esb/rosetta/pooling/SessionExecutorInit.java contains line sessionState.getExecutor().restart()

According to this http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_SP3_CP11/src/main/org/jboss/messaging/util/CompatibleExecutor.java there is no such method on the interface in question.
Comment 1 Julian Coleman 2011-04-06 15:44:07 UTC 
Revision 8868 of:

  branches/4.3/build-tools/builders/eap/build.xml

updates the ESB build to use the jars provided by the EAP base.

This now causes the ESB build to fail.

With the removal of the restart() method, it looks like the whole of:

  product/rosetta/src/org/jboss/internal/soa/esb/rosetta/pooling/SessionExecutorInit.java

is redundant.
Comment 2 Julian Coleman 2011-04-07 10:25:40 UTC 
Link: Added: This issue is related to SOA-563
Comment 3 Julian Coleman 2011-04-07 11:07:45 UTC 
The original problem (messaging creates non-daemon threads) is fixed.  See:

  .../src/main/org/jboss/messaging/util/JBMThreadFactory.java

in:

  http://fisheye.jboss.org/changelog/Messaging?cs=4937
Comment 4 Julian Coleman 2011-04-07 11:16:06 UTC 
Link: Added: This issue is a dependency of JBESB-3598
Comment 5 Len DiMaggio 2011-04-07 11:32:14 UTC 
Affects Testing: Added: [Regression, Blocks Testing]
Blocked Tests: Added: Blocks running JBossESB *project* tests against *platform* bits
Comment 6 Anne-Louise Tangring 2011-04-08 14:13:32 UTC 
Approved for SOA 4.3 CP05.
Comment 7 tcunning 2011-04-11 20:53:18 UTC 
Removed the contents of SessionExecutorInit.initExecutor.     Wasn't sure if anything else was using this internal yet public method.
Comment 8 Julian Coleman 2011-04-12 14:26:17 UTC 
Resolved with revision 8929 (4.3 branch) of:

  build-tools/dependencies.properties

Commit message:

  SOA-3006
  Use ESB JBESB_4_4_GA_CP5_CR2 tag to fix JBESB-3598.
Comment 9 Jiri Pechanec 2011-04-20 09:53:18 UTC 
Verified in ER2 code

But to avoid any further dependency on JBM I would remove even import definitions
Comment 10 David Le Sage 2011-05-04 23:17:29 UTC 
Temporarily reopening to update release note info.
Comment 11 David Le Sage 2011-05-04 23:18:04 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Note You need to log in before you can comment on or make changes to this bug.