Hide Forgot
Created attachment 827938 [details] server.log JMS API does not work, no processes are started, see the relevant error message (whole is attached): 19:01:15,852 ERROR [org.jboss.as.ejb3.invocation] (Thread-3 (HornetQ-client-global-threads-1428642534)) JBAS014134: EJB Invocation failed on component KieSessionRequesMessageBean for method public abstract void javax.jms.MessageListener.onMessage(javax.jms.Message): javax.ejb.EJBException: java.lang.RuntimeException: org.kie.services.remote.exception.KieRemoteServicesInternalError: Unknown serialization type: 1 To reproduce: 1.) Download BPMS 6 ER5 and merge it with EAP 6.1.1 distribution. 2.) Add user guest, password guest into EAP config files: application-users.properties: guest=b5d048a237bfd2874b6928e1f37ee15e application-roles.properties: guest=kie-user,admin standalone.xml: make sure that JMS subsystem queue roles include role 'admin' 3.) Setup datasource for BPMS, I used PostgreSQL. Make sure the db is empty before the test. Do not use the default H2. 4.) Start the server and go to http://localhost:8080/business-central. 5.) Clone repository git://git.app.eng.bos.redhat.com/bpms-assets.git to your BPMS installation. 6.) Build&Deploy a project bpms-perf from the bpms-assets.git repo. 7.) Run perf scenario: git clone git://git.app.eng.bos.redhat.com/jbossqe-process-flood.git cd jbossqe-process-flood/bpms-6.x ./execute_scenario.sh -Dscenario=HumanTask_pcJMS This issue is serious. It's a regression as the same scenario was already fixed in ER4 and also this issue prevents to create a complete performance report for ER5. My env: BPMS 6 ER5 EAP 6.1.1 PostgreSQL 9.1.9 postgresql-9.1-902.jdbc4.jar
This is not a bug ... the serialization type has changed so it's enough to change it to 0 or to not set it at all. https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-remote/kie-services-client/src/main/java/org/kie/services/client/serialization/JaxbSerializationProvider.java#L30
Thanks Ivo. It was enough both to set message property 'serialization' to 0 or to omit the property. Previous configuration required value 1 to be set. Now raw (no kie client) JMS API works with ER5. So this is not a bug, but just a configuration change.