web server - Borland Technical Publications

More documents

Recommendations

Info

Error Recovery Error Recovery That said, it is possible to deploy MDBs in more than one Partition with the Messaging Server pushing messages to only one, switching to the other in case of failure. Most JMS products allow queues to behave in load-balancing or fault-tolerant modes. That is, MDB replicas can register to the same queue and the messages are distributed to them using a load-balancing algorithm. Alternately, messages may all go to one consumer until it fails, at which point delivery shifts to another. The connection established to the JMS service provider from the MDB can also provide a loadbalancing and/or fault-tolerant node. JMS service providers may provide fault-tolerance features. For specific information on clustering and fault tolerance features, refer to JMS Provider Pluggability. Keep in mind that only one MDB instance in a container that subscribes to a topic will consume any given message. This means that, for all parallel instances of an MDB to concurrently process messages, only one of the instances will actually receive any particular message. This frees up the other instances to process other messages that have been sent to the topic. Note that each container that binds to a particular topic will consume a message sent to that topic. The JMS subsystem will treat each messagedriven bean in separate containers as a separate subscriber to that message! This means that if the same MDB is deployed to many containers in a cluster, then each deployment of the bean will consume a message from the topic to which it subscribes. If this is not the behavior you desire, and you require exactly one consumption of a message, then you should consider deploying a queue rather than a topic. The following section deals with JMS <strong>server</strong> connection failures and setting connection rebind attempt properties. It also covers the redelivery of messages to the JMS service when an MDB fails to consume a message. The section on redelivery covers setting the redeliver attempt property as well as two properties for delivering messages to a dead queue. Rebinding A connection failure usually occurs after you deploy your bean, causing a need for rebind attempt. You also receive an error if you are trying to deploy your bean and a connection to the JMS <strong>server</strong> was never established. Whether a failure occurs post deployment or no connection was found during deployment, the container will transparently attempt to rebind the JMS service provider connection when you set the rebind attempt properties. This ensures even greater fault-tolerance from an MDB instance. The two bean-level properties that control the number of rebind attempts made and the time interval between attempts are: ■ ■ ejb.mdb.rebindAttemptCount: this is the number of times the EJB Container tries to re-establish a failed JMS connection for this MDB. The default value is 5 (five). To make the container attempt to rebind infinitely you need to explicitly specify ejb.mdb.rebindAttemptCount=0. ejb.mdb.rebindAttemptInterval: the time in seconds between successive retry attempts. The default value is 60. Chapter 20: Message-Driven Beans and JMS 187
Error Recovery Redelivered messages Should the MDB fail to consume a message for any reason, the message will be redelivered by the JMS service. The message will only be re-delivered five times. After five attempts, the message will be delivered to a dead queue (if one is configured). There is one bean-level property that controls the re-deliver attempt count: ■ ejb.mdb.maxRedeliverAttemptCount: the max number of times a message will be redelivered by the JMS service provider if an MDB is unable to consume it. The default value is 5. There are two bean-level properties for delivering a message to a dead queue: ■ ejb.mdb.unDeliverableQueueConnectionFactory: looks up JNDI name for the connection factory to create connection to the JMS service. ■ ejb.mdb.unDeliverableQueue: looks up the JNDI name of the queue. The XML example for unDeliverableQueueConnectionFactory and unDeliverableQueue is shown here: MyMDB serial://jms/q serial://jms/xaqcf 20 0 jms/QueueConnectionFactory jms/xaqcf ejb.mdb.maxRedeliverAttemptCount String 3 ejb.mdb.unDeliverableQueueConnectionFactory String serial://jms/qcf ejb.mdb.unDeliverableQueue String serial://jms/q2 ejb-designer-id String MyMDB 188 BES Developer’s Guide
Page 1 and 2:
Developer’s Guide Enterprise Serv
Page 3 and 4:
Contents Chapter 1 Introduction to
Page 5 and 6:
Entity beans . . . . . . . . . . .
Page 7 and 8:
Chapter 23 Using JMS 209 Configurin
Page 9 and 10:
Entity Bean Properties (applicable
Page 11 and 12:
Figures 0.1 Borland Enterprise Serv
Page 13 and 14:
BES Products and Editions overview
Page 15 and 16:
Documentation conventions Important
Page 17 and 18:
Contacting Borland support World Wi
Page 19 and 20:
BES services overview Figure 0.1 Bo
Page 21 and 22:
The Partition and its services ■
Page 23 and 24:
Borland Enterprise Server and J2EE
Page 25 and 26:
14 BES Developer’s Guide
Page 27 and 28:
Creating Partitions Creating Partit
Page 29 and 30:
Running Partitions Table 3.1 Option
Page 31 and 32:
Configuring Partitions You can also
Page 33 and 34:
JMX support in Partitions ■ ■ A
Page 35 and 36:
JMX support in Partitions Figure 3.
Page 37 and 38:
Thread pools Partition properties r
Page 39 and 40:
Page 41 and 42:
Apache web server implementation Fo
Page 43 and 44:
Borland web container implementatio
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Smart Agent implementation Smart Ag
Page 51 and 52:
Page 53 and 54:
Apache web server to Borland web co
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Large data transfer Downloading lar
Page 61 and 62:
Large data transfer Uploading large
Page 63 and 64:
IIS web server to Borland web conta
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Session management with JSS If an i
Page 71 and 72:
Managing and configuring the JSS Co
Page 73 and 74:
The Borland IIOP connector BES supp
Page 75 and 76:
Setting up your web container with
Page 77 and 78:
Page 79 and 80:
Web-enabling your CORBA server Impo
Page 81 and 82:
Configuring your Apache web server
Page 83 and 84:
Configuring your Apache web server
Page 85 and 86:
Web Services and Partitions ■ ■
Page 87 and 88:
Web Service providers Java:RPC prov
Page 89 and 90:
How Borland Web Services work
Page 91 and 92:
Packaging Web Service Application A
Page 93 and 94:
Tools Overview Java2WSDL tool Note
Page 95 and 96:
Page 97 and 98:
Client view of an enterprise bean L
Page 99 and 100:
Client view of an enterprise bean E
Page 101 and 102:
Managing transactions Managing tran
Page 103 and 104:
Support for JNDI Support for JNDI T
Page 105 and 106:
EJB to CORBA mapping A CORBA progra
Page 107 and 108:
Page 109 and 110:
Application Client architecture Pac
Page 111 and 112:
Document Type Definitions (DTDs) my
Page 113 and 114:
Support of references and links The
Page 115 and 116:
Use of Manifest files Use of Manife
Page 117 and 118:
Page 119 and 120:
Sessions in secondary storage If yo
Page 121 and 122:
Page 123 and 124:
Container-managed persistence and R
Page 125 and 126:
Implementing an entity bean Generat
Page 127 and 128:
Container-Managed Persistence in Bo
Page 129 and 130:
Page 131 and 132:
Setting Properties Setting Properti
Page 133 and 134:
Setting Properties into a BLOB. The
Page 135 and 136:
Setting Properties Automatic table
Page 137 and 138:
Page 139 and 140:
Container-managed persistence and R
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148: Container-Managed Persistence in Bo
Page 153 and 154: 142 BES Developer’s Guide
Page 155 and 156: Setting Properties J2EE 1.3 Entity
Page 157 and 158: Setting Properties Figure 16.2 Edit
Page 159 and 160: Setting Properties Table 16.1 ejb.m
Page 161 and 162: Setting Properties Table 16.3 Table
Page 163 and 164: Setting Properties Security Propert
Page 165 and 166: Aggregate Functions in EJB-QL Selec
Page 167 and 168: Support for ORDER BY Support for OR
Page 169 and 170: Overriding SQL generated from EJB-Q
Page 171 and 172: Container-managed data access suppo
Page 175 and 176: Generating primary keys from a cust
Page 177 and 178: Implementing primary key generation
Page 179 and 180: Transaction manager services Consis
Page 181 and 182: Transaction manager services When t
Page 183 and 184: Transaction manager services Follow
Page 185 and 186: Declarative transaction management
Page 187 and 188: Declarative transaction management
Page 189 and 190: JDBC API Modifications JDBC API Mod
Page 191 and 192: Handling of EJB exceptions Applicat
Page 195 and 196: Client View of an MDB Client View o
Page 197: Clustering of MDBs This is yet anot
Page 203 and 204: JNDI Definitions Module Important s
Page 205 and 206: Disabling and Enabling a Deployed D
Page 207 and 208: Configuring JDBC Datasources In the
Page 209 and 210: Configuring JDBC Datasources To add
Page 211 and 212: Defining the Connection Pool Proper
Page 213 and 214: Defining the Connection Pool Proper
Page 215 and 216: Descriptions of Borland Enterprise
Page 217 and 218: Advanced Topics for Defining JDBC D
Page 219 and 220: Connecting to JDBC Resources from J
Page 221 and 222: Configuring JMS Connection Factorie
Page 223 and 224: Defining Connection Pool Properties
Page 225 and 226: Obtaining JMS Connection Factories
Page 227 and 228: JMS and Transactions and its accomp
Page 229 and 230: JMS and Transactions For instance:
Page 233 and 234: Configuring JMS administered object
Page 235 and 236: Tibco Creating Clustered JMS Servic
Page 237 and 238: Sonic serverUrl String localhost:72
Page 239 and 240: Sonic Creating Clustered JMS Servic
Page 241 and 242: OpenJMS Even though OpenJMS can be
Page 243 and 244: OpenJMS Important If you use OpenJM
Page 245 and 246: OpenJMS openjms.clean_messages_on_s
Page 247 and 248: OpenJMS Table 24.1 Property Name De
Page 249 and 250:
Other JMS providers The following a
Page 251 and 252:
Page 253 and 254:
Creating the Interceptor Class For
Page 255 and 256:
Creating the JAR file Creating the
Page 257 and 258:
Components Components The Connector
Page 259 and 260:
System Contracts Connection Managem
Page 261 and 262:
System Contracts Security Managemen
Page 263 and 264:
Common Client Interface (CCI) Conne
Page 265 and 266:
Packaging and Deployment Figure 26.
Page 267 and 268:
Resource Adapters Resource Adapters
Page 269 and 270:
Connection management Connection ma
Page 271 and 272:
Security management with the Securi
Page 273 and 274:
Security management with the Securi
Page 275 and 276:
Resource Adapter overview Note Reso
Page 277 and 278:
Deployment Descriptors for the Reso
Page 279 and 280:
Developing the Resource Adapter Con
Page 281 and 282:
Deploying the Resource Adapter Pack
Page 283 and 284:
Application development overview 8
Page 285 and 286:
Application development overview //
Page 287 and 288:
Application development overview
Page 289 and 290:
Other Considerations Other Consider
Page 291 and 292:
Other Considerations To illustrate,
Page 293 and 294:
Other Considerations } } { cf = new
Page 295 and 296:
General syntax and usage General sy
Page 297 and 298:
Syntax and usage for iastool Table
Page 299 and 300:
Syntax and usage for java2iiop Exam
Page 301 and 302:
Syntax and usage for appclient Tabl
Page 303 and 304:
Building and running the BES exampl
Page 305 and 306:
Using the iastool command-line tool
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Executing iastool command-line tool
Page 335 and 336:
Page 337 and 338:
element ■ ■ ■ element The
Page 339 and 340:
element The Partition statistics ag
Page 341 and 342:
element element The services eleme
Page 343 and 344:
element element The archive elemen
Page 345 and 346:
EJB Container-level Properties Tabl
Page 347 and 348:
EJB Container-level Properties Tabl
Page 349 and 350:
EJB Customization Properties: Deplo
Page 351 and 352:
Complete Index of EJB Properties Co
Page 353 and 354:
Complete Index of EJB Properties Ta
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Java Session Service (JSS) Properti
Page 361 and 362:
Java Session Service (JSS) Properti
Page 363 and 364:
Partition Transaction Service (Tran
Page 365 and 366:
Borland-specific web DTD 33, 36 bra
Page 367 and 368:
ejb.mdb.maxMessagesPerServerSession
Page 369 and 370:
J J2EE VisiClient 97 VisiClient env
Page 371 and 372:
optimistic concurrency 130 SelectFo
Page 373 and 374:
Sonic clustered service 228 SonicMQ
Page 375:
X XML DTD 99 VisiClient 98 grammar
show all

web server - Borland Technical Publications

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?