Skip to main content

JMS Exception

3 replies [Last post]
Anonymous

Hi,

I have a standalone JMS Client which has to be integrated with a business
process in WebLogic. When I try invoking JMS Client during the run time I
get the following error

com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection
creation [localhost:7676]. - cause: java.net.ConnectException: Connection
refused: connect
Caused by: java.net.ConnectException: Connection refused: connect

I am new to JMS. Any thoughts would be really useful.

Thanks,
Anusha
--
View this message in context: http://www.nabble.com/JMS-Exception-tp22224754p22224754.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Jon Faldmo

It sounds like you want to connect to the MQ broker started by WebLogic, is
that correct?

If so, you need to know the server name and port the broker is listening on
(like Chris mentioned in his reply.)

Port 7676 is the default address for the broker the domain admin server
(DAS) starts up. If you are installing the JMS client to the DAS then I
would suggest you create a new instance and deploy the JMS client to the new
instance. Then configure the JMS settings on the new instance to connect to
a remote broker with the server name and port of that remote broker. Is you
JMS client a consumer, producer, or both?

I haven't connected to a broker other than Sun's Message Queue but if you
can give me some more details and let me know if what I described above is
what you want to do then I might be able to help you get it setup you need
additional help.

Jon

On Thu, Feb 26, 2009 at 7:02 AM, acs wrote:

>
> Hi,
>
> I have a standalone JMS Client which has to be integrated with a business
> process in WebLogic. When I try invoking JMS Client during the run time I
> get the following error
>
> com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection
> creation [localhost:7676]. - cause: java.net.ConnectException: Connection
> refused: connect
> Caused by: java.net.ConnectException: Connection refused: connect
>
> I am new to JMS. Any thoughts would be really useful.
>
> Thanks,
> Anusha
> --
> View this message in context:
> http://www.nabble.com/JMS-Exception-tp22224754p22224754.html
> Sent from the java.net - glassfish users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
[att1.html]

acs

Hi,

Thanks a lot for replying back.

Looks like the IMQ Borker was not started and thats why the JMSException was
coming.

I was using the MQ broker of Solaris as the JMS client is built on Solaris
Platform.

Thanks,
Anusha

Jon Faldmo wrote:
>
> It sounds like you want to connect to the MQ broker started by WebLogic,
> is
> that correct?
>
> If so, you need to know the server name and port the broker is listening
> on
> (like Chris mentioned in his reply.)
>
> Port 7676 is the default address for the broker the domain admin server
> (DAS) starts up. If you are installing the JMS client to the DAS then I
> would suggest you create a new instance and deploy the JMS client to the
> new
> instance. Then configure the JMS settings on the new instance to connect
> to
> a remote broker with the server name and port of that remote broker. Is
> you
> JMS client a consumer, producer, or both?
>
> I haven't connected to a broker other than Sun's Message Queue but if you
> can give me some more details and let me know if what I described above is
> what you want to do then I might be able to help you get it setup you need
> additional help.
>
> Jon
>
> On Thu, Feb 26, 2009 at 7:02 AM, acs wrote:
>
>>
>> Hi,
>>
>> I have a standalone JMS Client which has to be integrated with a business
>> process in WebLogic. When I try invoking JMS Client during the run time I
>> get the following error
>>
>> com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection
>> creation [localhost:7676]. - cause: java.net.ConnectException: Connection
>> refused: connect
>> Caused by: java.net.ConnectException: Connection refused: connect
>>
>> I am new to JMS. Any thoughts would be really useful.
>>
>> Thanks,
>> Anusha
>> --
>> View this message in context:
>> http://www.nabble.com/JMS-Exception-tp22224754p22224754.html
>> Sent from the java.net - glassfish users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>>
>
>

--
View this message in context: http://www.nabble.com/JMS-Exception-tp22224754p22240062.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

chrjohn
Offline
Joined: 2008-03-11

Hi,

it seems the JMS broker is not listening on port 7676.
When you start Glassfish, it logs where the JMS broker is listening. E.g.:

JMS Service Connection URL is :mq://hostname:10076/

Cheers
Chris.