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

Bug 1148067

Summary: JMS remote client does not work: HornetQException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jiri Svitak <jsvitak>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED NOTABUG QA Contact: Jiri Svitak <jsvitak>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: kverlaen, mbaluch, smcgowan
Target Milestone: ---Keywords: TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-23 13:48:37 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:    
Bug Blocks: 1104760    
Attachments:
Description Flags
client.log
none
server.log
none
Test reproducer scripts none

Description Jiri Svitak 2014-09-30 15:50:08 UTC 
Created attachment 942783 [details]
client.log

JMS remote client does not work: HornetQException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.

See the attached client.log with the stack trace.

To reproduce:
1.) Install BPMS 6.1.0.DR3 using the installer in order to setup SSL secured JMS.
http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.1.0-DR3/
Create user bpmsAdmin with password bpmsAdmin1!
Password for all keystores and truststores is bpmsAdmin1!
2.) Install there project bpms-perf from bpms-assets, you can use the following commands.
curl -X POST -u 'bpmsAdmin:bpmsAdmin1!' -H "Content-Type: application/json" -d '{"name":"bpms-assets","description":"","userName":"","password":"","requestType":"clone","gitURL":"git://git.app.eng.bos.redhat.com/bpms-assets.git"}' http://localhost:8080/business-central/rest/repositories/
curl -X POST -u 'bpmsAdmin:bpmsAdmin1!' -H "Content-Type: application/json" -d '{"name":"","value":""}' http://localhost:8080/business-central/rest/repositories/bpms-assets/projects/bpms-perf/maven/deploy/
3.) Run the client side scenario:
git clone git://git.app.eng.bos.redhat.com/jbossqe-process-flood.git
cd jbossqe-process-flood
mvn clean package exec:exec -Dscenario=HumanTask_all_kieJMS -DrunType=iteration -Dduration=1

I was able to start a business process on a business central only with raw JMS connections (pcJMS scenarios). This issue blocks test development. Please check also my code in http://git.app.eng.bos.redhat.com/git/jbossqe-process-flood.git/tree/src/main/java/org/perfcake/message/sender/remote/AbstractKieSender.java

My env:
BPMS 6.1.0.DR3
EAP 6.3.0
PostgreSQL 9.3.5
Comment 1 Jiri Svitak 2014-09-30 15:51:56 UTC 
Created attachment 942785 [details]
server.log

Attaching also whole server.log
Comment 2 Marco Rietveld 2014-10-21 13:19:10 UTC 
I've pushed the correct commits to the process-flood github so that those tests, at the very least, are able to correctly communicate via (SSL) JMS with BPMS.
Comment 3 Marco Rietveld 2014-10-21 13:21:31 UTC 
Created attachment 948959 [details]
Test reproducer scripts

Added the scripts I used to reproduce the issue. Others should be able to use them by modifying the variables at the top of the setup.sh script.
Comment 4 Jiri Svitak 2014-10-23 13:48:37 UTC 
Marco, thank you very much for your correcting commits.

I was able to use JMS with mandatory SSL security without any problems (in full-profile). Unfortunately only with DR3 build, DR4 JMS is broken due to issue found by Ivo:
https://bugzilla.redhat.com/show_bug.cgi?id=1155629

Closing the bug.