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

Bug 1155629

Summary: JMS messages are declined due to unexpected element "command-request"
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Business CentralAssignee: Shelly McGowan <smcgowan>
Status: CLOSED EOL QA Contact: Ivo Bek <ibek>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: ibek, mbaluch, rrajasek
Target Milestone: ER2Keywords: TestBlocker
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:37:30 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:
Attachments:
Description Flags
server log none

Description Ivo Bek 2014-10-22 13:47:46 UTC
Created attachment 949400 [details]
server log

Description of problem:

When I send a JMS message to start a process, I get the following exception:

javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"command-request"). Expected elements are ....

I tried to send the JMS messages with JaxbCommandsRequest myself and I also tried the Java remote client for JMS with the same result.

I attached the server log with full stacktrace of the exception.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Marco Rietveld 2014-10-22 15:09:57 UTC
Hi Ivo, 

If possible, could you include a reproducer? 

Thanks!

Comment 3 Marco Rietveld 2014-10-23 12:27:04 UTC
Ivo, 

I've confirmed that the test succeeds on the current build. Could you confirm whether or not this is sufficient to close this bug? 

I've done the following: 
1. Built kie-wb-distribution-6.2.0-SNAPSHOT-eap6_3.war using the current 6.2.x branch (which will be used for the CR2 tag). 
2. Installed a clean jboss-eap-6_3 server
3. Added the ibek user to the server (with correct password) and added the proper permissions so that the ibek user can send/receive JMS messages.
4. Installed the above kie-wb-distribution war as "business-central.war" on the eap 6.3 server. 
5. Started the eap server. 
6. Changed the ( ) TestConfig.jmsSSLEnabled field to false. 
7. Run the StartProcessTest test

The tests then pass. 

As far as I can tell, this confirms that the bug is not present on the current build.

Comment 4 Ivo Bek 2014-10-23 12:48:46 UTC
Alright, I believe the way you tested the current build is sufficient, thank you. Do you have any idea what caused that the command-request was declined by the unmarshaller in the previous build? Did you change anything there recently?

However I would not close this bug because the problem is present in the DR4 build though it is fixed in the upstream. Instead you may change the status of BZ to modified and I will verify it in the next build, BPMS 6.1.0.ER1.

Thanks

Comment 5 Marco Rietveld 2014-10-23 13:43:27 UTC
Thanks, setting it to modified.

Comment 6 Ivo Bek 2014-11-20 09:26:43 UTC
Verified in BPMS 6.1.0.ER2