Bug 1149621 - (6.3.z) Upgrade org.jboss.remoting3 from 3.3.3.Final-redhat-1 to 3.3.4.Final
Summary: (6.3.z) Upgrade org.jboss.remoting3 from 3.3.3.Final-redhat-1 to 3.3.4.Final
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.3
Assignee: Vaclav Tunka
QA Contact: Jitka Kozana
URL:
Whiteboard:
: 1149623 (view as bug list)
Depends On: 1139197 1149618
Blocks: 1031692 1123505 1147635 eap633-payload
TreeView+ depends on / blocked
 
Reported: 2014-10-06 09:25 UTC by Ivo Studensky
Modified: 2019-08-19 12:42 UTC (History)
13 users (show)

Fixed In Version:
Clone Of: 1149618
Environment:
Last Closed: 2019-08-19 12:42:00 UTC
Type: Component Upgrade
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1181740 0 unspecified CLOSED RHEL6 RPMs: Upgrade jboss-remoting3 to 3.3.4.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1181741 0 unspecified CLOSED RHEL5 RPMs: Upgrade jboss-remoting3 to 3.3.4.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1181742 0 unspecified CLOSED RHEL7 RPMs: Upgrade jboss-remoting3 to 3.3.4.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker REM3-192 0 Major Resolved Expose the SSLSession from the Connection 2018-01-03 00:54:42 UTC
Red Hat Issue Tracker REM3-193 0 Major Resolved RemoteReadListener skips receive equal to -1 sometimes 2018-01-03 00:54:42 UTC
Red Hat Issue Tracker WFCORE-112 0 Major Resolved Long server shut-dow with unresponsive client with opened JNDI Context 2018-01-03 00:54:42 UTC

Internal Links: 1181740 1181741 1181742

Description Ivo Studensky 2014-10-06 09:25:30 UTC 
+++ This bug was initially created as a clone of Bug #1149618 +++

Upgrade jboss-remoting to resolve the linked issues
Comment 1 Ivo Studensky 2014-10-06 09:34:55 UTC 
*** Bug 1149623 has been marked as a duplicate of this bug. ***
Comment 4 JBoss JIRA Server 2014-10-09 12:38:01 UTC 
David Lloyd <david.lloyd> updated the status of jira REM3-192 to Resolved
Comment 7 Rostislav Svoboda 2014-10-14 10:10:53 UTC 
https://github.com/jboss-remoting/jboss-remoting/compare/3.3.3.Final...3.3 shows 11 commits right now, 7 of them are without reference to any JIRA or BZ

Adding qa_nack because I prefer new version based on current tag (3.3.3.Final-redhat-1) + just fixes we want - something like 3.3.3.SP1-redhat-1
Comment 8 David M. Lloyd 2014-10-14 12:46:52 UTC 
You mean six.  Of the six, three relate specifically to extra trace logging.  You want those (I added them specifically to help debug customer problems with GSS).  Two plug memory leaks so you want those too.  The only one that may not matter to you is one which fixes tests which leak memory.

But at that stage, wouldn't it make more sense to just take them all?
Comment 9 Rostislav Svoboda 2014-10-15 11:36:49 UTC 
Commit https://github.com/jboss-remoting/jboss-remoting/commit/d2de3549fa44a01e19896e233a6fbc20575407bd is the one we need EAP 6.3.3 CP.

That's why we want 3.3.3.SP1 - to have just this small add-on to limit risks for regressions.


On the other hand there is still question mark on BZ 1123505 - Darran is super busy and it's not clear he will be able to have fix for 6.3.x. My guess is that it will be for 6.4.0 ... :) When looking at this BZ I noticed it will need REM3-192 from my point of view it's feature and https://issues.jboss.org/browse/REM3-192 confirms it - Type: Feature Request
Comment 16 Dominik Pospisil 2014-11-11 09:46:30 UTC 
https://github.com/jboss-remoting/jboss-remoting/tree/3.3.4.Final
Comment 17 Enrique Gonzalez Martinez 2014-11-11 11:02:08 UTC 
PR sent for this upgrade:

https://github.com/jbossas/jboss-eap/pull/1933
Comment 19 Ladislav Thon 2015-01-20 08:43:55 UTC 
Verified with EAP 6.3.3.CP.CR1.
Note You need to log in before you can comment on or make changes to this bug.