Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1104760

Summary:	Remote API client version mismatch: [AbstractRemoteCommandObject] Response received from server version [pre-6.0.3] while client is version [6.0.3.1]!
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Jiri Svitak <jsvitak>
Component:	Business Central	Assignee:	Shelly McGowan <smcgowan>
Status:	CLOSED EOL	QA Contact:	Marek Baluch <mbaluch>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.2	CC:	mbaluch
Target Milestone:	DR4
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 19:33:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1148067
Bug Blocks:

Description Jiri Svitak 2014-06-04 15:27:54 UTC

I have run a simple performance test, however official client prints the following error for each request, even when both client and server are the same version (BPMS 6.0.2.ER3):

2014-06-04 11:02:53,462 INFO  [AbstractRemoteCommandObject] Response received from server version [pre-6.0.3] while client is version [6.0.3.1]! This may cause problems.
2014-06-04 11:02:53,845 INFO  [AbstractRemoteCommandObject] Response received from server version [pre-6.0.3] while client is version [6.0.3.1]! This may cause problems.

My env:
BPMS 6.0.2.ER3
EAP 6.1.1
JMS transport

Comment 1 Marco Rietveld 2014-08-01 13:06:26 UTC

Thank you Jiri for catching this!! (And for making the jira). 

Fixed. Commits: 

master: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/0fb2a6b8

Comment 2 Jiri Svitak 2014-10-14 11:25:14 UTC

Cannot verify in DR2 nor DR3 due to:
https://bugzilla.redhat.com/show_bug.cgi?id=1148067

Comment 3 Jiri Svitak 2014-10-23 13:56:32 UTC

Verified in BPMS 6.1.0.DR3, although the current target version was set to DR4.

Unfortunately JMS is broken in DR4, so cannot verify with newer build:
https://bugzilla.redhat.com/show_bug.cgi?id=1155629

Test blocking issue for DR3 has been resolved thanks to Marco's contribution, which helped to setup complex JMS client using SSL mandatory encryption.
https://bugzilla.redhat.com/show_bug.cgi?id=1148067

QE does not have an automated test verify this issue, but possible regression would be easily found by regular analysis of server log, thus confirming qe test coverage.