Resolution:
The following stack trace is thrown when trying to start a process in Designer which has BE "Send Activity" and uses JMS as a channel.

java.lang.NoSuchMethodError: javax.jms.MessageProducer.send(Ljavax/jms/Destination;Ljavax/jms/Message;IIJ)V
    at com.tibco.cep.driver.jms.JMSDestination.send(JMSDestination.java:351)
    at com.tibco.cep.driver.jms.JMSDestination.send(JMSDestination.java:374)
    at com.tibco.be.bw.plugin.BESendEvent.eval(BESendEvent.java:137)
    at com.tibco.pe.plugin.Activity.eval(Activity.java:209)
    at com.tibco.pe.core.TaskImpl.eval(TaskImpl.java:540)
    at com.tibco.pe.core.Job.a(Job.java:712)
    at com.tibco.pe.core.Job.k(Job.java:501)
    at com.tibco.pe.core.JobDispatcher$JobCourier.a(JobDispatcher.java:249)
    at com.tibco.pe.core.JobDispatcher$JobCourier.run(JobDispatcher.java:200)

Resolution

=======

1). Designer by default uses "TIBCOjms.jar" located at "<TIBCO_HOME>/tra/<VERSION>lib" to connect to EMS.

2). Any other "jms. jar" file or any other JAR which contains JMS classes set in the classpath can conflict the proper functioning with EMS at runtime.

3). Check if the classpath mentioned in designer.tra contains any JAR file which contains JMS classes that is causing the conflict with "TIBCOjms.jar". If any of such JAR files are found in any of the folders in classpath, move them away from the classpath folder and restart Designer.

Note that even though there is a conflicting JAR file in the classpath, the "Test Connection" for JMS in Designer works but it gives the error mentioned while processing the messages with EMS at runtime.

Error java.lang.NoSuchMethodError: javax.jms.MessageProducer.send(Ljavax/jms/Destination;Ljavax/jms/Message;IIJ)V is thrown when trying to start a process in Designer which has TIBCO BusinessEvents "Send Activity" and uses JMS as channel.