| Stephen Cocks 2006-09-28, 1:22 pm |
| You will need a correctly configured Provider Endpoint setting on the
connection factory to allow the standalone client program to find a server
through which it can locate a messaging engine for the requested bus. When
you run the same code within a JSP the provider endpoint setting is ignored
if information about the requested bus is known to that server's
environment. Thus getting the code to work from within a JSP doesn't prove
that all the configuration is correct.
It's quite common for servers created within RAD not to have the default
ports, especially if you have multiple servers or a full runtime
installation on the same machine. How many installations, profiles, and
servers do you have on your machine? Are you sure that the server in the UTE
is using 7276 for its messaging support (SIB_ENDPOINT_ADDRESS) [check the
server details via the admin console to see the port settings]?
--
Stephen Cocks
WESB/WPS System Administration
<xgr3@yahoo.com> wrote in message
news:10734640.1159459539812.JavaMail.wassrvr@ltsgwas010.sby.ibm.com...
>I am able to get the connection with the same client code and able to put
>message in the queue when using the JSP. It seems problem is when running
>standalone JMS Client (Outside of the app server, two different JVMs).
> I am not sure why it is blowing up with the standalone code ????
> Any expert ??
|