JBoss
Application server that implements the Java Platform, Enterprise Edition (Java EE) http://en.wikipedia.org/wiki/Jboss.
Message driven bean (JBoss)
A message-driven bean is an enterprise bean that allows J2EE applications to process messages asynchronously.
Annotations, MDB Properties Provided by the JCA Specification
Name |
Type |
Default value |
Remarks |
destination |
java.lang.String |
none |
This property is Mandatory The JNDI name of the Queue or Topic. |
destinationType |
java.lang.String |
none |
The type of destination valid values are javax.jms.Queue or javax.jms.Topic |
messageSelector |
java.lang.String |
none |
The message selector of the subscription |
acknowledgeMode |
int |
AUTO_ACKNOWLEDGE |
The type of acknowledgement when not using transacted jms - valid values AUTO_ ACKNOWLEDGE or DUPS_OK_ ACKNOWLEDGE |
clientID |
java.lang.String |
|
The client id of the connection |
subscriptionDurability |
String |
Whether topic subscriptions are durable. Valid values are Durable or NonDurable |
||subscriptionName||String||none||The subscription name of the topic subscription||
MDB Properties Provided as JBoss Extensions
Name |
Type |
Default value |
Remarks |
isTopic |
boolean |
false |
Sets the destinationType |
providerAdapterJNDI |
java.lang.String |
DefaultJMSProvider |
The JNDI name of the JMS provider. |
user |
java.lang.String |
none |
The user ID used to connect to the JMS server |
pass |
java.lang.String |
none |
The password of the user |
maxMessages |
int |
1 |
Read this number of messages before delivering messages to the MDB. Each message is delivered individually on the same thread in an attempt to avoid context excessive context switching |
minSession |
int |
1 |
The minimum number of JMS sessions that are available to concurrently deliver messages to this mdb |
maxSession |
int |
15 |
The maximum number of JMS sessions that are available to concurrently deliver messages to this mdb |
reconnectInterval |
long |
10 seconds |
The length of time in seconds between attempts to (re-)connect to the JMS provider |
keepAlive |
long |
60 seconds |
The length of time in milliseconds that sessions over the minimum are kept alive |
sessionTransacted |
boolean |
true |
Whether the sessions are transacted |
useDLQ |
boolean |
true |
Whether to use a Dead Letter Queue (DLQ) handler. |
dLQJNDIName |
java.lang.String |
queue/DLQ |
The JNDI name of the DLQ |
dLQHandler |
java.lang.String |
org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler |
The org.jboss.resource. adapter.jms.inflow. DLQHandler implementation class name. |
dLQUser |
java.lang.String |
none |
The user id used to make the dlq connection to the JMS server |
dLQPassword |
java.lang.String |
none |
The password of the dLQUser |
dLQClientID |
java.lang.String |
none |
The client id of the DLQ connection |
dLQMaxResent |
int |
5 |
The maximum number of times a message is redelivered before it is sent to the DLQ. |
redeliverUnspecified |
boolean |
true |
Whether to attempt to redeliver a message in an unspecified transaction context |
transactionTimeout |
int |
Default is the timeout set for the resource manager |
Time in seconds for the transaction timeout |
boolean |
true |
Whether the MDB should make the subscription at initial deployment or wait for start() or stopDelivery() on the corresponding MBean. You can set this to false if you want to prevent messages from being delivered to the MDB (which is still starting) during server start up. |
Timers annotations
Creating Calendar-Based Timer Expressions http://docs.oracle.com/cd/E19226-01/820-7627/giqlk/index.html
Examples:
Every five minutes, @Schedule(minute = "*/5" , hour="*")
Every twenty minutes from 5 to 21, @Schedule(minute="*/20" , hour = "5-21")
At one AM, @Schedule(hour = "1")
At two AM and five PM, @Schedule(hour = "2,17")
== JAAS security JBoss AS7== JAAS (Java Authentication and Authorization Service).
Read http://amatya.net/blog/implementing-security-with-jaas-in-jboss-as-7/