Title: RE: Using a Message Driven Bean to put in another Queue does not work with 1.5.2 / OC4J
We figured out what the problem is.
The beans are being deployed before the JNDI tree is initialized or something.
As long as the QueueConnectionFactory is gotten in the onMessage() it works.
I
Title: RE: EJB pool management
I am sure there is a way, it is just not documented as the orionconsole.jar
has provisions for invalidating the pools, and adjusting their sizes.
it will probably be an ormi: call of some sort?
-Original Message-
From: Sergey G. Aslanov
Title: RE: loadbalancer.jar: what does it do, really?
sticky loadbalancing is not such a good idea for orion as it will cause errors if the server is down and the loadbalancer tries to route to that instance. This is a MAJOR problem if another web server is in front of the orion instance and
Title: Oracle AQ / JMS as Message Driven Bean source. ( ResourceProviders )
does anyone have an example of using the JMS wrapper around Oracle AQ?
Seeing as OC4J is Orion, this should be something that is either on the Oracle site or the Orion site, but is neither place?
I need to be able
Title: RE: Announcement
This is great these issues are holding us back from sophisticated deployments right now.
My 2 cents worth is this is the order of importance of documentation that is
needed right now to do REAL professional deployments and developements with Orion/OC4J
1) Orion
Title: RE: Course Grained Entity Beans...your thoughts
you have some points for small projects but with a few caveats that apply even to the smallest and
most trival of projects.
1. Writing DAO style code and not leveraging it INSIDE you BMP EJB's as delegates
is BAD. It just creates
Title: RE: Deployment Exception
shutdown the server
delete the .ear file in applications
delete the directory in applications
delete the directory(ies) in application-deployments
startup the server ( it should complain about not finding the ear )
shut it down
copy .ear file to applications
Title: RE: Deadlock in a session
if I understand you correctly you are storing
ejb references in the servlet and then passing them to
an ejb which is BAD, the ejbs should look up their own instances
of the remote handles and use them, NOT reuse the ones in the servlet.
-Original
