When defining a connection factory for a JNDI binding the default value for Transport is:
-
Client
-
Bindings
-
No default. The transport has to be defined explicitly
-
None of the above
When defining a JNDI connection factory for IBM WebSphere MQ, the default transport type is 'Bindings' mode. This provides direct in-memory communication when client and queue manager are on the same machine. 'Client' transport (TCP/IP) must be explicitly specified for remote connections.
When a JNDI connection factory binding doesn't explicitly specify a transport, the messaging system falls back to the in-VM "Bindings" transport, which is optimized for clients running in the same JVM/container as the resource. This avoids the overhead of a network-based transport when the client and destination are co-located.