org.objectweb.celtix.bus.transports.jms

Java Source Code / Java Documentation
1. 6.0 JDK Core
2. 6.0 JDK Modules
3. 6.0 JDK Modules com.sun
4. 6.0 JDK Modules com.sun.java
5. 6.0 JDK Modules sun
6. 6.0 JDK Platform
7. Ajax
8. Apache Harmony Java SE
9. Aspect oriented
10. Authentication Authorization
11. Blogger System
12. Build
13. Byte Code
14. Cache
15. Chart
16. Chat
17. Code Analyzer
18. Collaboration
19. Content Management System
20. Database Client
21. Database DBMS
22. Database JDBC Connection Pool
23. Database ORM
24. Development
25. EJB Server geronimo
26. EJB Server GlassFish
27. EJB Server JBoss 4.2.1
28. EJB Server resin 3.1.5
29. ERP CRM Financial
30. ESB
31. Forum
32. GIS
33. Graphic Library
34. Groupware
35. HTML Parser
36. IDE
37. IDE Eclipse
38. IDE Netbeans
39. Installer
40. Internationalization Localization
41. Inversion of Control
42. Issue Tracking
43. J2EE
44. JBoss
45. JMS
46. JMX
47. Library
48. Mail Clients
49. Net
50. Parser
51. PDF
52. Portal
53. Profiler
54. Project Management
55. Report
56. RSS RDF
57. Rule Engine
58. Science
59. Scripting
60. Search Engine
61. Security
62. Sevlet Container
63. Source Control
64. Swing Library
65. Template Engine
66. Test Coverage
67. Testing
68. UML
69. Web Crawler
70. Web Framework
71. Web Mail
72. Web Server
73. Web Services
74. Web Services apache cxf 2.0.1
75. Web Services AXIS2
76. Wiki Engine
77. Workflow Engines
78. XML
79. XML UI
Java
Java Tutorial
Java Open Source
Jar File Download
Java Articles
Java Products
Java by API
Photoshop Tutorials
Maya Tutorials
Flash Tutorials
3ds-Max Tutorials
Illustrator Tutorials
GIMP Tutorials
C# / C Sharp
C# / CSharp Tutorial
C# / CSharp Open Source
ASP.Net
ASP.NET Tutorial
JavaScript DHTML
JavaScript Tutorial
JavaScript Reference
HTML / CSS
HTML CSS Reference
C / ANSI-C
C Tutorial
C++
C++ Tutorial
Ruby
PHP
Python
Python Tutorial
Python Open Source
SQL Server / T-SQL
SQL Server / T-SQL Tutorial
Oracle PL / SQL
Oracle PL/SQL Tutorial
PostgreSQL
SQL / MySQL
MySQL Tutorial
VB.Net
VB.Net Tutorial
Flash / Flex / ActionScript
VBA / Excel / Access / Word
XML
XML Tutorial
Microsoft Office PowerPoint 2007 Tutorial
Microsoft Office Excel 2007 Tutorial
Microsoft Office Word 2007 Tutorial
Java Source Code / Java Documentation » ESB » celtix 1.0 » org.objectweb.celtix.bus.transports.jms 
org.objectweb.celtix.bus.transports.jms
Java Source File NameTypeComment
JMSBrokerSetup.javaClass
JMSClientTransport.javaClass
JMSClientTransportInstrumentation.javaClass
JMSConfigTest.javaClass
JMSConstants.javaClass
JMSContextTest.javaClass
JMSInputStreamContext.javaClass
JMSInputStreamContextTest.javaClass
JMSOutputStreamContext.javaClass
JMSOutputStreamContextTest.javaClass
JMSProviderHub.javaClass This class acts as the hub of JMS provider usage, creating shared JMS Connections and providing access to a pool of JMS Sessions.
JMSServerTransport.javaClass
JMSServerTransportInstrumentation.javaClass
JMSSessionFactory.javaClass This class encapsulates the creation and pooling logic for JMS Sessions. The usage patterns for sessions, producers & consumers are as follows ...

client-side: an invoking thread requires relatively short-term exclusive use of a session, an unidentified producer to send the request message, and in the point-to-point domain a consumer for the temporary ReplyTo destination to synchronously receive the reply if the operation is twoway (in the pub-sub domain only oneway operations are supported, so a there is never a requirement for a reply destination)

server-side receive: each port based on requires relatively long-term exclusive use of a session, a consumer with a MessageListener for the JMS destination specified for the port, and an unidentified producer to send the request message

server-side send: each dispatch of a twoway request requires relatively short-term exclusive use of a session and an indentified producer (but not a consumer) - note that the session used for the recieve side cannot be re-used for the send, as MessageListener usage precludes any synchronous sends or receives on that session

So on the client-side, pooling of sessions is bound up with pooling of temporary reply destinations, whereas on the server receive side the benefit of pooling is marginal as the session is required from the point at which the port was activated until the Bus is shutdown The server send side resembles the client side, except that a consumer for the temporary destination is never required. Hence different pooling strategies make sense ...

client-side: a SoftReference-based cache of send/receive sessions is maintained containing an aggregate of a session, indentified producer, temporary reply destination & consumer for same

server-side receive: as sessions cannot be usefully recycled, they are simply created on demand and closed when no longer required

server-side send: a SoftReference-based cache of send-only sessions is maintained containing an aggregate of a session and an indentified producer

In a pure client or pure server, only a single cache is ever populated.

JMSTransportBase.javaClass
JMSTransportFactory.javaClass
JMSTransportTest.javaClass
JMSUtils.javaClass
JMSUtilsTest.javaClass
PooledSession.javaClass Encapsulates pooled session, unidentified producer, destination & associated consumer (certain elements may be null depending on the context).
PooledSessionTest.javaClass
www.java2java.com | Contact Us
Copyright 2009 - 12 Demo Source and Support. All rights reserved.
All other trademarks are property of their respective owners.