| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| What new plugins would you like to see in MQSI? |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Wed May 28, 2003 6:43 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't think it's recommended that you use JDBC from within a plug-in node. I think the preferred practice is to use the database access functions already provided with the Java plug-in interface.
If you have to access databases that are not supported, I think the best idea would be to use an RMI type call (perhaps an EJB) to a separate JVM, so you don't muck up your broker runtime or connection pooling or etc. |
|
| Back to top |
|
 |
| GYR |
| Posted: Wed May 28, 2003 7:08 am Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
| Thanks for the reply, I assume it is possible then to do an RMI call from within the node. Is the call expecting a response is it not then going to stall the broker until the job is finished?. Do you know why it is not recommended to use jdbc. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 28, 2003 1:05 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's not recommended to use JDBC directly because a) you could interfere with the broker's JDBC access, and b) you could interfere with the message flow transactionality. Both of these would be bad, in my book.
As to the RMI call, yeah, your message flow is going to block. But it's gonna block anyway. How much it will block is going to depend on a lot of things, and how much impact that has on the broker depends on how long it blocks (and a lot of other things).
In other words, try it, but run LOTS of performance testing - and make sure you can gracefully time out. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
