LDAP enteries not showing. Fails to establish connection to broker.

I have 2 questions: I would very much appreciate your support.

Question 1

My client and broker are installed on the same box with windows XP.(this is a new network) I have created ldap and configured the client application to access the ldap on the broker locally( to avoid any firewall problems).

Now when I run the GUI admin tool for the broker I am not seeing any entries in the object store. Whatcan be I doing wrong?. It seems that the GUI admin tool does not know about the LDAP.

So basically the GUI tool does not show any broker or object store entries. I have installed an LDAP browser and can view the entries that way to check LDAP is properly setup as expected.

Are there any associated settings to tell the broker where to get the object store details from?

Also when I stop the IMQ BROKER service and restart it fails to restart. So when I try to run broker in DOS mode it displays a message saying there is already and instance of this broker running on port 7676. So to temporarily sort this out is to reboot the server and the broker starts to run on port 7676 again.

So why as soon as I restart the service the port is taken up by another instance of broker or some other application? I am not loading any applications either .

Question 2.

My client is running on windows XP and the broker is on a separate box on windows 2000. This box was taken of live setup we had as there was no need to for 2 brokers anymore. Now what we have done is configured this broker to run on a new network (in question 1) and point all the old clients (running on XP ) to this box. The old clients can talk to broker and send messages. This is fine.

BUT when I try and connect my new client (running on XP) to this broker it fails to establish connection to broker.

Please advise what I can do to solving this problem.

Thank you for help.

[1924 byte] By [JMSMAN] at [2007-11-25 17:40:09]
# 1

For the LDAP object store question, please read MQ Administration

Guide on "LDAP Server Object Store" in Managing Administered

Objects. There is a set of attributes you need to specify. In

imqadmin console, please see the online help on Add Object Store

>Also when I stop the IMQ BROKER service and restart it fails to restart. So when I try to run broker in DOS mode it displays a message saying there is already and instance of this broker running on port 7676. So to temporarily sort this out is to reboot the server and the broker starts to run on port 7676 again.

So why as soon as I restart the service the port is taken up by another instance of broker or some other application? I am not loading any applications either .

The 'restart' may not actually completely fail therefore the broker

process is running while you try to run broker in DOS mode which

leads to port 7676 in use.I'v tried stop then start IMQ BROKER

service several times in Windows XP and don't see any start

failure after stopped. You may want to check the Event Viewer

on your Windows system to see if any information regarding your

'restart' failure. You can also check the broker log to see if the

broker is actually shutdown or started.

>BUT when I try and connect my new client (running on XP) to this broker it fails to establish connection to broker.

Have you configured the new client's ConnectionFactory to

connect to the broker ? What is the Exception message

and stacktrace ? You should be able to get some

information from that

http://wwws.sun.com/software/products/message_queue/

amy.kang at 2007-7-3 14:34:57 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...