bug # 21830665.
Version 12.2.1.0.0
21830665: HEALTH CHECK RESULT OF JMS SERVERS ARE LEFT BLANK
JMS infrastructure on above versions of weblogic using OSB 12c will not work untill the patch 21830665 is applied.
Once the patch is applied , follow the configuration below to make it work.
Create a cluster.
A cluster will contain two managed servers ms1 and ms2 and cluster name is mycluster(select unicast mode of messaging)
Both ms have different ports and are started by going to domains/bin startManagedServer.cmd ms1 (press enter and username/pwd when asked)
Get your cluster up and running.
Now go to JMS servers and create two new jms servers pointing to both managed servers ms1 and ms2.
JMServer1 and JMServer2 both pointed to two managed servers.(JMS servers act as containers for the JMS infrastructure and are mapped directly to either managed servers or the clusters)
Use filestore for both of the jms servers.
Now go to JMS modules
Create a jms module called clusterjmsmodule, in targets select the cluster so that jms servers under that clusters are available for subdeployment mapping of other jms resources in this module.
Create a connection factory and map it to the cluster.
Create queue1 and create a sub-deployment and select the first jms server, similarly create another queue and map it to the other jmsserver.
JMS Server health should be green after this configuration is complete and you should be able to see monitoring tab in the queues.
Use a program in eclipse to send message to queueu and see the count of messages in monitoring tab of queue.
Use this link bottom line code , to find out how to send messages to a queue via code.
P.S File store statistics should be available if the JMS servers are up and running fine.
No comments:
Post a Comment