Topic Send and Topic Receive demo on JBoss Application Server

1 )Create a topic Add the following in the \deploy\messaging\destinations-service.xml file   <mbean code="org.jboss.jms.server.destination.TopicService" name="jboss.messaging.destination:service=Topic,name=Topic1" xmbean-dd="xmdesc/Topic-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> <depends>jboss.messaging:service=PostOffice</depends> </mbean> 2) Copy the TopicSend and TopicReceive programs to a folder. TopicSend import java.io.*; import java.util.*; import javax.transaction.*; import javax.naming.*; import javax.jms.*; import javax.rmi.PortableRemoteObject; public class TopicSend { // Defines the

Continue reading »

Weblogic JMS Test plan using Apache JMETER

With the ever growing business needs, today’s companies need their web applications to be robust and  highly scalable. Before deploying the JMS resources in production environment, companies do performance testing. This post provides a brief insight about how we can load test to measure performance of a Weblogic Server JMS

Continue reading »

JMS Based Webservice on Weblogic Server

By default, client applications use HTTP/S as the connection protocol when invoking a WebLogic Web Service. You can, however, configure a WebLogic Web Service so that client applications can also use JMS as the transport when invoking the Web Service.When a WebLogic Web Service is configured to use JMS as

Continue reading »

Unit Of Order with Distributed Destinations

The below post gives a good understanding of need of Unit Of Order with Distributed Destinations and ways to configure the same. Message Unit-of-Order is a WebLogic Server value-added feature that enables a stand-alone message producer, or a group of producers acting as one, to group messages into a single unit

Continue reading »

Uniform Distributed Destinations (UDD) feature in WebLogic

The below post depicts a sample configuration of a Uniform Distributed Destination (Queue/ Topic) for the WebLogic JMS feature. A Distributed Destination represents a group of physical queues, or topics, whose members are hosted by JMS servers in a WebLogic cluster. The distributed destination is bound to a logical JNDI

Continue reading »

Working with JMS and the Standard Issues in JMS

Java Messaging Service acronymised as JMS is popular in both development and administration world. Different vendors have got different implementations for this JMS API. Oracle Weblogic Server implements this JMS for communication between two different weblogic server domains. This implementation although looks simple but its usage is very high (especially

Continue reading »

WebLogic JMS feature using Topic

WebLogic JMS feature using Topic

Continue reading »

WebLogic JMS (Point to Point) feature using a Queue

The article shows a simple usage of WebLogic JMS feature using a Queue.

Continue reading »

Large Message Processing Issues In JMS Transactions

When there is a distributed transaction involved in message processing, it is very important that all the resources involved in the transaction are reachable without any latency. When this is not the case and there is an issue with the communication between the resources, there can be issues of message

Continue reading »

Weblogic Foreign JMS Server Configuration With MQ Series

–    Create a JMS server target it to the admin server as below: –    Create a JMS module and add the resource Foreign Server as below: – Go to the ForeignServer-> Configuration-> General and edit it as below: JNDI Initial Context Factory: com.sun.jndi.fscontext.RefFSContextFactory JNDI Connection URL: file:/C:/JNDI-Directory It looks like:

Continue reading »