Anyways I did solve the issue by bypassing the JNDI lookup and instead directly giving the actual destination name of my Topic/Queue configured at the Solace.
Cool, yeah just using the “physical” name of the destination rather than JNDI. Probably a better way to go anyhow, especially if you want to use Solace features like Topic-to-Queue mapping and dynamic hierarchical topics… can’t be publishing to a static topic, won’t take advantage.
The external JNDI works perfectly for establishing the connection and session objects however the topic or queue does not seem to work with weblogic’s implementation for some reason.
In your external JNDI, have you imported some/all the various Solace messaging-specific parameters that we expose in our connection factory? Otherwise, I’m guessing it would just be the Solace defaults for everything.