Configuring and Managing WebLogic Store-and-Forward
|
 |
 |
|
 |
 |
Troubleshooting WebLogic SAF
The following sections explain how to troubleshoot WebLogic SAF.
Frequently Asked Questions About JMS SAF
This section answers commonly asked questions about how JMS SAF operates in a WebLogic domain.
Q. Which sending agent is picked by SAF for a JMS producer?
A. WebLogic Sever's cluster load balancing is used to pick a sending agent for a given JMS producer. Once a SAF agent is picked, it is used for the life of the JMS producer.
Q. How do JMS clients find a SAF destination?
A. A SAF destination can be found the same way a non-SAF JMS destination is found.
- JMS clients can look up a SAF Destination in JNDI
createDestinationAPIJMS clients can also use the
createDestinationAPI to find JMS Destination. JMS clients have to use the SAF destination name in a JMS module. TheNamemust be a fully-qualified name delimited by exclamation points (!). For example:<EAR Name>!<JMS Module Name>!<ImportedDestinationsName>!<SAFQueue or SAFTopic Name>
Q. Can a JMS producer sending messages to a JMS SAF imported destination be associated with a JMS Unit-of-Order?
A. Yes. For information about the Unit-of-Order feature, see For more information about configuring a Path service, see "Using Message Unit-of-Order" in Programming WebLogic JMS.
Q. Why does my JMS producer associated with a JMS Unit-of-Order fail to send messages if the sending-side is a cluster?
A. In order to use JMS Unit-of-Order with SAF, you must configure the Path Service for the sending-side cluster. For information about the Path Service feature, see "Using the WebLogic Path Service" in Configuring and Managing WebLogic JMS.
Q. Do different JMS producers in the same Unit-of-Order pick up the same Sending Agent?
A. Yes. JMS SAF uses the Path Service to route to the same Sending Agent.
Q. Can a consumer be attached to a JMS SAF Imported Destination?
A. No. JMS consumers can only be attached to actual JMS destinations.
Q. Can a distributed destination be imported?
A. Yes, it can be imported using its JNDI name.
Q. Where do I configure Server Affinity, Load Balancing Enabled, and Forward Delay for a distributed destination that is imported in a sending cluster?
A. Server Affinity and Load Balancing Enabled are configured in the JMS connection factory on which the JMS producer was created. A JMS connection factory creates a JMS connection; a JMS connection creates a JMS session; a JMS session creates a JMS producer. Forward Delay is configured on the JMS distributed destination.
Q. Are the Server Affinity and Load Balancing parameters configured on a JMS connection factory in the sending cluster or server honored on the receiving cluster or server where the JMS Destination resides?
A. Yes. These attributes on the sending cluster or server are honored on the receiving cluster or server. For information about Server Affinity and Load Balancing for distributed destinations, see "Configuring Distributed Destinations" in Configuring and Managing WebLogic JMS
Q. Do XA transactions on the sending-side of a cluster ever cross the JMS SAF boundary? In other words, can the receiving-side participate with a transaction from the sending- side?
A. No. Messages are not forwarded until the transaction is committed.
Q. Does JMS SAF preserve the order of messages sent in a JMS session from a sending-side to a JMS destination?
Q. In the SAF Remote Context, should I configure a Principal Name or a Username/Password?
A. You can configure the Remote SAF Context anyway you want. Username and Passwords are stored in the JMS module, and the principal name is stored in a Credential Mapper configured in the sending-side domain.
