PeerGoneException sending large JMS messages using T3.

Hello,
          I'm using WL 7.0 SP4 on the backend. I have clients that send JMS messages to this WL server using T3. Some of the messages are ~1MB in size, and sometimes the clients use dial-up connections with a maximum speed of 54 Kbps. (Yes, I know we are living in the dark ages...)
          Anyway, sometimes the WL server throws a PeerGoneException. I realize this is because the CompleteT3MessageTimeout has expired. I have already set it to the maximum of 480 seconds, but sometimes that's not enough. Is there a way to disable this timeout or set it to be infinite?
          Does anyone have any suggestions?
          thanks in advance,
          matt

sorry for answering myself...
          if you set 480 seconds on client and on server side, you will get a time
          range of 480 seconds.
          you will never be able to get more then 480 seconds. (And yes, there
          only existe the T3MessageTimout, which should be fine to my point of view.
          Another point might be the jta transaction timeout server-side.
          Regards
          Klaas
          Klaas Hagemann schrieb:
          > Hi Matt,
          >
          >
          > the settings have to be the same, client- and serverside. The whole t3
          > connection times out.
          > I only tested it with 8.1, so i cannot give you any advice concerning 7.0.
          > Maybe you should contact BEA Support, they should easily be able to
          > check whether there exists a patch for 7.0
          >
          >
          > Sorry...
          >
          >
          > Klaas
          >
          >
          > Matt Hill schrieb:
          >
          >>Thanks for the reply, Klaus.
          >>
          >>We are using WL 7.0 (not 8.1), so we do not have the CompleteMessageTimeout attribute. WL 7.0 only has the CompleteT3MessageTimeout attribute, which I set to the maximum of 480 secs, but unfortunately it sometimes takes longer to transfer our messages.
          >>
          >>I tried your suggestion of setting the client-side java property, but it did not help. I believe my problem is that the server times out - not the client.
          >>
          >>Any other ideas would be greatly appreciated.
          >>
          >>thanks,
          >>matt

Similar Messages

How to send a JMS message to a server ....

Hi
I want to know how to send a jms message to a Queue and that is in a different server...
How to send A message using a application client to a Message queue That is in another Machine(Server is in another machine )
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL, "iiop://127.0.0.1:3700/");
InitialContext initialContext = new InitialContext(env);
connectionFactory = (ConnectionFactory) initialContext.lookup("jms/ConnectionFactory");
queue = (Queue) initialContext.lookup("jms/Queue");
get a NameNotFoundException
Anyone have an Idea
thanks
Ishkmi
Message was edited by:
ishkmi

ok..try this..insert the ip address of the server where ur app server is
running . i understand ur client and server is running on diff machines.
ip address 127.0.0.1 is for local host. it tries to look for the server in
same system as the client.
substitue ip address of server in below line instead of 127.0..0.1
env.put(Context.PROVIDER_URL, "iiop://127.0.0.1:3700/");
best of luck ..lemme know..

MDB sending a JMS message to a queue (WLS 8.1.4)

We are trying to implement a MDB to send a JMS message to a dynamically created JMS queue. Is this possible? We have found documentation stating the JMS Queue destination needs to be in the deployment descriptor, but in our case it changes so this is not an option. Any help would be appreciated.

Sorry I didn't address the answers more clearly. You were correct on the answers except with:
          Switch from using a resource-reference to a direct reference for a send? Answer: No. We are only trying a direct send, not utilizing the resource-reference.
          We are already using "false" for the connection.create[Queue]Session code.
          Should we be trying something else because of transactional behavior of not utilizing the resource-reference for the send as you thought?
          We have tried the queue as XA and non-XA and neither work.

Sending/Receiving JMS message to WMQ from Automated Task

Hi All,
I am new to OSM and working on a POC for the implementation of OSM in our company. We have WebSphere MQ for messaging and want to use same for OSM implementation. We don't want to create bridges, foreign server etc configuration in weblogic, rather just connect with MQ objects over JNDI (as supported) from OSM automated task. Having said that, we have following two scenarios:
1- JMS message is received at OSM
2- JMS message initiated from OSM (automated task)
Now our requirement is to create a sort of JMS inbound gateway for first scenario i.e. reading a message from a Queue and CreateOrder and then reply back to caller using JMSReplyTo header.
Second as JNDI support is available for automated task, can we send JMS message using direct JNDI look up for MQ JNDI objects i.e. using .bindings file (JNDI URL for MQ objects).
Thanks

Hi All,
I am new to OSM and working on a POC for the implementation of OSM in our company. We have WebSphere MQ for messaging and want to use same for OSM implementation. We don't want to create bridges, foreign server etc configuration in weblogic, rather just connect with MQ objects over JNDI (as supported) from OSM automated task. Having said that, we have following two scenarios:
1- JMS message is received at OSM
2- JMS message initiated from OSM (automated task)
Now our requirement is to create a sort of JMS inbound gateway for first scenario i.e. reading a message from a Queue and CreateOrder and then reply back to caller using JMSReplyTo header.
Second as JNDI support is available for automated task, can we send JMS message using direct JNDI look up for MQ JNDI objects i.e. using .bindings file (JNDI URL for MQ objects).
Thanks

Is it possible to send a text message using the UDP protocol?

Support doc
http://www.adobe.com/support/director/multiuser/using_udp/using_udp02.html
says to use the following format with connectToNetServer:
errCode =
gMultiuserInstance.connectToNetServer([#remoteAddress:
"chatServer.myCompany.com", #logonInfo: [#userID: "Bob",
#password:
"MySecret", #movieID: "Tech Chat"], #mode: #smus,
#localUDPPort: 1627,
#localAddress: "123.45.67.89", #remoteTCPPort: 1626])
But if I change the mode to #text, it still sends out
messages as smus.
In fact, if I leave out the UDP parameters altogether but
still use the
list parameters for connectToNetServer, it still always sends
as smus.
Sends as smus:
errCode =
gMultiuserInstance.connectToNetServer([#remoteAddress:
"chatServer.myCompany.com", #logonInfo: [#userID: "Bob",
#password:
"MySecret", #movieID: "Tech Chat"], #mode: #text,
#localUDPPort: 1627,
#localAddress: "123.45.67.89", #remoteTCPPort: 1626])
Sends as smus:
errCode =
gMultiuserInstance.connectToNetServer([#remoteAddress:
"chatServer.myCompany.com", #logonInfo: [#userID: "Bob",
#password:
"MySecret", #movieID: "Tech Chat"], #mode: #text])
Only the string parameter method can be made to send text
messages.
Sends as text:
errCode = gMultiuserInstance.connectToNetServer("Bob",
"MySecret",
"chatServer.myCompany.com", 1626, "Tech Chat", 1)
Am I missing something? Is this a known issue? Anyone have a
work around?
-Jeremy

Drat!
Thanks for the answer though.
alchemist wrote:
> The multiuserXtra supports either tcp text or tcp smus
connections.
> The ability to send udp messages was an expansion to the
original mus
> protocol/xtra and is valid only for muXtra instances
already connected in
> smus mode.
> So, if you are asking if you can create a udp instance
and use it at will
> (exchange udp messages with some remote udp socket),
then the answer is no.
>
>
> "Jeremy Aker" <[email protected]> wrote in message
> news:[email protected]...
>> I'm really sorry that I wasn't clear enough. I'll
repeat the questions
>> more concisely.
>> Is it possible to send a text message using the UDP
protocol? If so, how?
>> Is the bug I described in my original message (see
below) really a bug or
>> am I doing something wrong?
>> If it's a bug, does anyone have a work around?
>>
>> alchemist wrote:
>>> And the question is?
>>>
>>> "Jeremy Aker" <[email protected]> wrote in
message
>>> news:[email protected]...
>>>> Support doc
>>>>
http://www.adobe.com/support/director/multiuser/using_udp/using_udp02.html
>>>> says to use the following format with
connectToNetServer:
>>>> errCode =
gMultiuserInstance.connectToNetServer([#remoteAddress:
>>>> "chatServer.myCompany.com", #logonInfo:
[#userID: "Bob", #password:
>>>> "MySecret", #movieID: "Tech Chat"], #mode:
#smus, #localUDPPort: 1627,
>>>> #localAddress: "123.45.67.89",
#remoteTCPPort: 1626])
>>>>
>>>> But if I change the mode to #text, it still
sends out messages as smus.
>>>> In fact, if I leave out the UDP parameters
altogether but still use the
>>>> list parameters for connectToNetServer, it
still always sends as smus.
>>>>
>>>> Sends as smus:
>>>> errCode =
gMultiuserInstance.connectToNetServer([#remoteAddress:
>>>> "chatServer.myCompany.com", #logonInfo:
[#userID: "Bob", #password:
>>>> "MySecret", #movieID: "Tech Chat"], #mode:
#text, #localUDPPort: 1627,
>>>> #localAddress: "123.45.67.89",
#remoteTCPPort: 1626])
>>>>
>>>> Sends as smus:
>>>> errCode =
gMultiuserInstance.connectToNetServer([#remoteAddress:
>>>> "chatServer.myCompany.com", #logonInfo:
[#userID: "Bob", #password:
>>>> "MySecret", #movieID: "Tech Chat"], #mode:
#text])
>>>>
>>>> Only the string parameter method can be made
to send text messages.
>>>> Sends as text:
>>>> errCode =
gMultiuserInstance.connectToNetServer("Bob", "MySecret",
>>>> "chatServer.myCompany.com", 1626, "Tech
Chat", 1)
>>>>
>>>> Am I missing something? Is this a known
issue? Anyone have a work
>>>> around?
>>>>
>>>> -Jeremy
>

Sending a JMS message inside a PostPersist entity listener method

Hi to all,
I have an entity called "Batch" that I want to persist. After the persist, I want to send a JMS message to notify batch insertion to the other clients.
So I created the "Batch" entity as following :
@Entity
@EntityListeners({BatchServiceBean.class})
@Table(name = "batch")The "BatchServiceBean" is a session bean which persists the batch and sends the JMS notification message.
Inside this class we have the following method :
@PostPersist
    private void sendInsertMessage(Batch insertedBatch) throws JMSException {
        AddBatchMessage message = new AddBatchMessage();
        message.setBatch(insertedBatch);
        try {
            messageSenderServiceBean.sendRefreshMessage(message);
        } catch (Exception oups) {
            oups.printStackTrace();
    }In the previous code, I recuperate the inserted batch and the "messageSenderServiceBean" facade to send a refresh message.
My problem is that I can get the inserted batch, but the object "messageSenderServiceBean" is null knowing that I have the following annotation to get the "messageSenderServiceBean" facade.
@EJB
    private MessageSenderServiceLocal                   messageSenderServiceBean;Whyhe object "messageSenderServiceBean" is null ??
Can any one help me ??
Thanks in advance.

Hello,
Injection only occurs on server managed objects, not JPA managed entities or other java objects such as the listeners registered with JPA. So your Listener class will need to look up the server objects or other resources directly from the context rather than rely on them being injected. I don't have any good examples handy, but similar to how you would look up an ejb/datasource etc before injection.
Best Regards,
Chris

Using ipad2 wifi,cannot send or receive messages using messages , running ios5

ipad2 wifi,cannot send or receive messages using messages , running ios5

Problem solved
Changed DNS settings to google public settings
8.8.8.8

How to send a JMS message to a remote Queue?

Hi,
I know how to create a JMS message and send it to an MDB that listens to a topic in the same container in which the JMS is created.
In other words, if I have the following MDB:
@MessageDriven(mappedName = "jms/MyQueue", ...)
public class MyMDB implements MessageListener {
Elsewhere in my JEE app I can create a Queue like this:
@Resource(mappedName = "jms/MyQueue")
Queue queue;
and use it to send a message to the MDB.
But How can I send a message to an MDB that's deployed in another app server on another machine in the network? Both of the app servers are Glassfish.
Thanks in advance.
Edited by: EJP on 9/08/2011 21:49: fixed your meaningless title

Hi,
The first thing I would like to suggest is, we never/can't send message directly to MDB. We always send/receive message(s) to/from the destination. In case of MDB, the application server register the MDB as message listener against particular destination, and invoked the onMessage() method when message arrives on particular destination.
If I am not wrong, what you want to achieve is asynchronous communication between two applications deployed in two different machine. In your case, you want your one application works as message producer and other act as an message consumer, and both are deployed in different machine.
In this situations, you only need to configure the JMS administration object, connection factories and destinations, on one Application server and configure other application server to use those configuration using JMS resource adapter. you can well achieve this by configuring the JMS Resource Adapter. you need to check the Glassfish documentation.
If you don't want to break the JMS specification, always communicate with Messaging Provider through Resource Adapter.
I hope this helps.

Browsing JMS messages using selector

Requirement
I want to browse for messages, using a selector.
SENDER
I'm sending messages in my Queue, with a property PARAMETER_ID set in it as.
message.setStringProperty("PARAMETER_ID",param_id);
Assume there are 4 messages sent in my Queue.
1. Text=Message1,PARAMETER_ID=1233
2. Text=Message2,PARAMETER_ID=4566
3. Text=Message3,PARAMETER_ID=1233
4. Text=Message4,PARAMETER_ID=4566
RECEIVER
I want to browse messages that have a certain PARAMETER_ID property set in it.
So here's what I'll do.
String myselector = "PARAMETER_ID=1233";
QueueBrowser qb=session.createBrowser(queue,myselector );
The QueueBrowser instance returned, should have 2 messages in it, that can be browsed.
But I dont get any results and there's no exception.
What am I doing wrong?
btw - If I set the myselector to "", it returns me all 4 messages to browse.
I'm using JBOSS with JMS 1.1
Thanks

4. Text=Message4,PARAMETER_ID=4566
What is this ? is this msg in queue? what is
PARAMETER_ID?that jms implementation appears to use PARAMETER_ID to identify its messages
Header {
jmsDestination : QUEUE.TMSQueueRemote
jmsDeliveryMode : 2
jmsExpiration : 0
jmsPriority : 4
jmsMessageID : ID:6-11824034000315
jmsTimeStamp : 1182403400031
jmsCorrelationID: null
jmsReplyTo : null
jmsType : null
jmsRedelivered : true
jmsProperties : {JMS_JBOSS_REDELIVERY_COUNT=1}
jmsPropertiesReadWrite:false
msgReadOnly : true
producerClientId: ID:6
Body {
TEsf
}MQ message implementation is different (but JMS-compliant)
if you want to use message selectors by identifier, try jmsMessageID='123'

JMS/AQ: Setting properties for JMS message using PL/SQL

I have created a procedure in PL/SQL that uses JMS messages, and now I need to include a property so that the subscriber can use a message selector to filter out unwanted messages. Is this possible using PL/SQL?
A previous post said: "... But you can have properties in the message payload itself and also define selectors on the message content ...". But I looked at Sun's tutorial and there it said: "A message selector cannot select messages on the basis of the content of the message body."
I have 300 different screens and messages apply only to one screen at a time. When the user is looking at screen 'A' I want him to only recieve messages that apply to screen 'A'. I thought I would do this with message selector, but is there any other way?
Here is my code(borrowed from an earlier post)
PROCEDURE ENQUEUE_JMS_MESSAGE AS
BEGIN
DECLARE
Enqueue_options DBMS_AQ.enqueue_options_t;
Message_properties DBMS_AQ.message_properties_t;
Message_handle RAW(16);
User_prop_array SYS.AQ$_JMS_USERPROPARRAY;
Agent SYS.AQ$_AGENT;
Header SYS.AQ$_JMS_HEADER;
Message SYS.AQ$_JMS_TEXT_MESSAGE;
Message_text VARCHAR2(100);
BEGIN
Agent := SYS.AQ$_AGENT('',NULL,0);
User_prop_array := SYS.AQ$_JMS_USERPROPARRAY();
Header := SYS.AQ$_JMS_HEADER( Agent, '', 'aq1', '', '', '', User_prop_array);
Message_text := 'Message 1 from PL/SQL';
Message := SYS.AQ$_JMS_TEXT_MESSAGE(Header, LENGTH(Message_text), Message_text, NULL);
DBMS_AQ.ENQUEUE(queue_name => 'tstopic',
Enqueue_options => enqueue_options,
Message_properties => message_properties,
Payload => message,
Msgid => message_handle);
END;
END;
-Christer

Thanks for the answer. I managed to set the Correlation id and retrieve it using getJMSCorrelationID(). But I did not manage to use the MessageSelector on it. I have used the Topicbrowser which is not part of the JMS standard? I tried to enqueue the messages using Java too and tried to use the topicbrowser on both JMSCorrelationID and user defined properties withou success. Is there some special requirements of the TopicBrowser?
Enumeration messages;
oracle.jms.TopicBrowser browser =tsess.createBrowser(topic, "TS", "JMSCorrelationID = 'TST'");
int count = 0;
messages = browser.getEnumeration();
if(messages.hasMoreElements())
System.out.println("message"); //never executed
dtxtmsg = (TextMessage)(tsub1.receiveNoWait()) ; //returns a message
String corrID = dtxtmsg.getJMSCorrelationID(); //returns: TST
Thanks for your help so far...it would really save my day if you have some ideas on this too!
-Christer

Send custom error message using IDoc conversion rule?

Hello,
I am using an Idoc conversion rule in BD79 to load cost centers. In my conversion rule I use a conversion exit function module to concatenate 2 specific characters and sending cost center value together and then this output value placed in the receiving cost center field. This works fine, but now I want to send a custom error message to the idoc and fail the idoc if the sending cost center value is greater than 8 digits.
Does anyone know how to send an error message or update an idoc with an error message using a conversion rule (bd79)?
Thank you,
Rhonda

Hi Rhonda,
Any luck on the below.. i have a similar issue...
Sorry to hijack your thread...

Sending a jms message from one server to another in a cluster fails..

Hi,
          My platform is wl6.1 sp7 two servers in a cluster...
          I have problems sending jms messages from one server to the other. When sending to a destination on the same server it works fine, but sending to the other server do not work. I get no exceptions when I send the message. The "Monitor all Active JMS Destinations..."->"Messages Received" column increase number of received messages for the remote server. But the onMessage method in the bean is not called(I am logging all calls to a file...)
          Any suggestions?
          And..
          My understanding is that the JNDINameReplicated default value is set to true? But when I don't set this value to true the jndi name is not replicated too the other server.
          (The state for both servers are Running in the admin console and listed servers in the cluster is 2....
          Server names:
          * bluej, biztalk-lab
          JMS connection factory:
          * xlink.jms.factory.commerceFactory, deplyed on both servers and for the cluster
          Destinations:
          * xlink.jms.service.report.biztalk-lab.Report for the biztalk-lab server active on 'biztalk-labJMSServer' JMS-server
          * xlink.jms.service.report.bluej.Report for the bluej server active on 'bluejJMSServer' JMS-server)
          ~b

Deployed to the bluej server:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.bluej.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.bluej.Report</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>xlink.jms.service.report.bluej.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.bluej.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <ejb-class>no.xlink.server.service.report.engine.jms.ReportBean</ejb-class>
          <transaction-type>Bean</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          </ejb-jar>
          Deployed to the biztalk-lab server:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <ejb-class>no.xlink.server.service.report.engine.jms.ReportBean</ejb-class>
          <transaction-type>Bean</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          </ejb-jar>

Is it possible to send encrypted email messages using cfmail ?

Does anyone know of a way to send an encrypted email message
using CF?

Sending an encrypted message is easy. The hard part is
enabling the recipient to decrypt it.

Can the AQ Adapter send a JMS Message?

I'm trying to use the AQ adapter to enqueue an XML message into a queue who's payload type is AQ$JMS_TEXT_MESSAGE so that it can be consumed by a Message Driven Bean in OC4J.
Simply sending the XML reults in:
"AQ Adapter: ** Error ** Can not enqueue messages to queue PLEDGE. ADT Payload defined for Queue PLEDGE does not match with OAI Message. Please check attribute "Pledge". In order for the AQ Adapter to enqueue OAI messages to the queue, the queue payload must match the ADT imported through iStudio."
I tried importing the AQ%JMS_TEXT_MESSAGE but can't see any easy way to construct it.
Is this even possible?
-Doug

Doug,
the AQ$JMS_TEXT_MESSAGE is an object type. So you'll need to import that type as your application view.
The problem with this JMS objecttype is how to populate it.
When your text (XML) is more than 4000 characters in length, the TEXT_LOB attribute should get the text. If less, the TEXT_VC attribute should get the text. In any case, the TEXT_LEN should be set to the length of the XML.
AFAIK, you can't currently do this with InterConnect directly.
The most popular solution is to have InterConnect deliver this message to a simple non-JMS queue and have some PL/SQL or java code convert it to a proper JMS text message and put it in the JMS text queue.
There are some features in the DBMS_AQ package to register a plsql procedure to be triggered when a message arrives (dbms_aq.register). That could be a procedure which converts the message for you.
In ProcessConnect (coming soon) there is a dedicated JMS adapter available.
HTH, Marc

Sending a JMS message from a Servlet

Hello All
I�m using the Sun Java Sysytem Application Server and have been trying to implement a servlet which on receipt of a Post message, takes the message and sends it using JMS to a message queue. I�m developing my first web application so all is fairly new to me but I desparately need to know if this scenario is viable. I have worked through relevant sections of the Java EE5 tutorial and so have the required ConnectionFactory and Queue resouces in place. I located the code below which the author implemented in Eclipse 3.2 and have tried to run it to establish that messages can be successfully sent. The code compiles ok but after the post message has been sent the server appears to lock up.
The servlet is as follows:
import java.io.IOException;
import javax.annotation.Resource;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class NewServlet extends javax.servlet.http.HttpServlet implements javax.servlet.Servlet {
@Resource(mappedName = "jms/Queue")
private Queue queue;
@Resource(mappedName = "jms/connectionFactory")
private ConnectionFactory jmsConnectionFactory;
//private Connection connection;
public NewServlet() {
super();
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
public void service(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
Connection connection = null;
Destination dest = (Destination) queue;
try {
connection = jmsConnectionFactory.createConnection();
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(dest);
TextMessage message = session.createTextMessage();
message.setText("Hello");
response.getOutputStream().println("Sending message: " + message.getText());
System.out.println("Sending message: " + message.getText());
producer.send(message);
producer.send(session.createMessage());
} catch (JMSException e) {
e.printStackTrace();
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
// TODO Auto-generated method stub
Please could someone point me in the right direction.
Many Thanks

Hello All
I�m using the Sun Java Sysytem Application Server and have been trying to implement a servlet which on receipt of a Post message, takes the message and sends it using JMS to a message queue. I�m developing my first web application so all is fairly new to me but I desparately need to know if this scenario is viable. I have worked through relevant sections of the Java EE5 tutorial and so have the required ConnectionFactory and Queue resouces in place. I located the code below which the author implemented in Eclipse 3.2 and have tried to run it to establish that messages can be successfully sent. The code compiles ok but after the post message has been sent the server appears to lock up.
The servlet is as follows:
import java.io.IOException;
import javax.annotation.Resource;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class NewServlet extends javax.servlet.http.HttpServlet implements javax.servlet.Servlet {
@Resource(mappedName = "jms/Queue")
private Queue queue;
@Resource(mappedName = "jms/connectionFactory")
private ConnectionFactory jmsConnectionFactory;
//private Connection connection;
public NewServlet() {
super();
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
public void service(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
Connection connection = null;
Destination dest = (Destination) queue;
try {
connection = jmsConnectionFactory.createConnection();
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(dest);
TextMessage message = session.createTextMessage();
message.setText("Hello");
response.getOutputStream().println("Sending message: " + message.getText());
System.out.println("Sending message: " + message.getText());
producer.send(message);
producer.send(session.createMessage());
} catch (JMSException e) {
e.printStackTrace();
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
// TODO Auto-generated method stub
}Please could someone point me in the right direction.
Many Thanks

PeerGoneException sending large JMS messages using T3.

Similar Messages

Maybe you are looking for