Logger.getLogger(()).log(Level.SEVERE, null, ex) Īnd the truncated version of the server.log file now looks like this (removing the stack traces for brevity): Throw new RuntimeException("Dummy Exception") Logger.getLogger(()).log(Level.SEVERE, "Throwing a dummy runtime exception") } catch (NamingException | JMSException e) ", msg) TextMessage message = session.createTextMessage() MessageProducer producer = session.createProducer(dest) Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE)
The 2 parameters passed here do not make any difference in GF!
#Glassfish blogspot code#
Then add the following code to the processRequest() method.ĬonnectionFactory connectionFactory = null ĬonnectionFactory = (ConnectionFactory) jndiContext.lookup("jms/testQueueFactory") ĭest = (Destination) jndiContext.lookup("jms/testQueue") Ĭonnection = connectionFactory.createConnection() In NetBeans create a new servlet, named something like JMSOne. We’re going to use JMS 1.1 for this example, before then doing JMS 2.0 which will hopefully show some of the simplifications that have been made. Now return to NetBeans and lets create a servlet to send the first message. (I’ve subsequently discovered there is no need for the Connection Factory, GF4 provides a default one that would be used if no others have been created!).ġ.2 Sending First Message (using JMS 1.1) Thats us got the infrastructure for the queue to function. Then create the Connection Factory by going to Resources –> JMS Resources –> Destination Resources, and enter the following parameters: Next up, create the queue by navigating to Resources –> JMS Resources –> Destination Resources, and click New. We’re then going to create our Queue and Connection Factory to handle the queue. This blog post is really to expand my knowledge, test some of the things mentioned, and to act as reference to my future self.Īll examples in this blog post are going to be using GlassFish 4.0 and NetBeans 7.3.įirst of all start the GlassFish server, and then log into the Admin Console (localhost:4848). I was recently fortunate enough to attend the inaugural London GlassFish Users Group earlier this week where Nigel Deakin from Oracle was presenting the latest features and developments. As part of the latest Java EE release (version 7), the JMS component has been reviewed and revamped.
0 kommentar(er)
