.win before Christmas, I heard from the Secret Service that they had received an email from China, urging them to stay vigilant about counterintelligence threats directed against the United States. China’s agents, they had been told, were in the United States and it wasn’t clear where they were. It’s not clear how the email was delivered, though the agency obviously has a means of doing it. The Chinese government has a special effort within its military known as the Fifth Directorate, a.k.a. the Office 39. But while Office 39 might not be top secret, its agents are known to be seeking to break into American technology companies, and it’s not very clear what that kind of spying would be good for. China is a growing threat, and one that is seeking to build a large, highly interconnected network of connected technologies, often called the “internet of things,” that would allow it to control everything from submarines to shipping containers. It’s easy to imagine the vast amounts of information that an office like Office 39 could obtain that could be used for spying. It would certainly help Beijing influence American politics and policies. This, of course, is why the Chinese would be concerned.Q:
What does JMS guarantee about persistence?
I'm developing a Java EE6 application with an embedded glassfish server. I'm using the jms transactional API and I've read that it guarantees that if I make a call to a method which has the transaction attribute, the transaction will be committed or rolled back at the end of the method. But if I take out the transaction attribute, what does JMS guarantee about the persistence of the message on the server?
I'm using the java 1.7 JMS library version 1.7.
A:
JMS does not guarantee that the message is persisted to the server. This is the responsibility of the server that you're using to implement the jms transactional API.
You can consider using a message broker instead of glassfish.
If you are using a message broker like activemq or vqmq, it will guarantee that the message is persisted to the server.
Otherwise, if you are using some kind of message queue, like JBoss MQ, you can take a look at this question on how to work with JMS + message queue.
The
Related links:
Opmerkingen