We are running WAS 5.0 and Websphere Commerce 5.6. Commerce requires that version 1.1 EJB- which means we do not have the ability to do MDBs. Another requirement is that commerce db connections are not XA enabled. Without doing some serious hacking- How can I execute JMS code so that it is not considered transactional by the EJB container? I'm currently getting "An illegal attempt to use multiple resources that have only on-phase capabiity has occurred within a global transaction." When I attempt to run the JMS code from within a session bean. I am simply trying to put a message to the queue, NOT listen to the queue.
I already tried setting transaction attribut to "Not supported"- but to no avail.