FindByPrimaryKey(String problem), please help

Question

Hi everybody.
I'm stuck for two days on this problem, and it's so weird I simply cannot find the solution. Here's the thing:
I have an entity EJB ProductBean with a String as a primary key (on Weblogic 8.1 server and Oracle 10g database btw). Everything mapped succesfully, everything works nicely. I made an MDB and did this
ProductHomeLocal productHome=(ProductHomeLocal)
jndiContext.lookup("java:comp/env/ejb/ProductHomeLocal");          
ProductLocal pl=productHome.findByPrimaryKey("ABC");Everything works nicely. Then I changed the last line so that the search parameter isn't hardcoded but sent by a JMS message parameter, like this:
TextMessage tm = (TextMessage) msg;
String productId=tm.getStringProperty("productId");
ProductHomeLocal productHome=(ProductHomeLocal)
jndiContext.lookup("java:comp/env/ejb/ProductHomeLocal");
ProductLocal pl=productHome.findByPrimaryKey(productId); This results in a message:
Bean with primary key 'ABC' was not found by 'findByPrimaryKey'...Why? The table data is there, if it's hardcoded it gets found no problem, why doesn't it work like this? What am I doing wrong?
I appreciate any kind of help. Thanks in advance.

Answer 1

I thought of leading and trailing spaces, it's not
that.
It seems that the problem isn't in JMS message, but
in the fact that the entity bean somehow doesn't get
"commited". The scenario is like this:
- session bean creates the entity bean
- session bean puts the entity bean's ID in JMS
message
- MDB bean gets the message and tries to get the
entity bean with findByPrimaryKey(ID), fails.
I know that this has something to do with
transactions, but I really don't know how to solve
it..Hmmm... assumming these 2 steps are in the same method in the session bean, then here's a possible scenario that can cause your problem,
- session bean creates the entity bean
- session bean puts the entity bean's ID in JMS
messagesession bean method ( <------- start of transaction boundary or join an existing one)
create entity bean
send message to JMS
// some other things you want to do
end of method ( <--- For CMT, container will commit transaction or continue with joined transaction and commit at the end )
So mebbe your MDB is trying to locate the entity bean before the transaction is commited? How about you try this,
1. Put the entity bean creation in its own method, say createMyEntity() and make it return the primary key on success.
2. Set this method's tx attribute to RequiresNew.
3. Now in your original method, call the createMyEntity method and use the returned primary key value to create your JMS message.
4. Make the MDB tx attribute as RequiresNew also.
Hope this helps.
Cheers.