Hi blackandwhite,
I'm quite sure I've read somewhere that this is a known bug in 3.2.1, but I
don't know where. You should perhaps upgrade to the latest version.
Regards,
Stefan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886788#3886788
Reply to the post
Hi Ravi,
one possibility of tuning CMP permormance is the definition of load groups
read-ahead strategies. Example from the docs (it's from jboss 3.2 so I don't
know if it is exactly the same in jboss 4)
Define load group for the entity bean:
|
|
| basic
| name
| nickName
| badne
Hi,
I solved the problem by adding the line
true
to my entity bean container configuration (which is included in the "Standard
CMP 2.x EntityBean" configuration by default in jboss 3.2.7, but I used my old
standardjboss.xml in which it was missing).
Best Regards,
Stefan
View the ori
Hi all,
I have the following problem with JBoss 3.2.7:
When I create a new instance of an entity bean, it is written to the database
without the ejbStore() method being called. I verified this by inserting debug
messages in my ejbCreate() and ejbStore() method. As I'm setting the value of
one
Dear chaman4110,
the first thing to do is putting the names of the remote and home interfaces
inside the proper xml-tags and wrap all the tags concerning your bean with a
session-tag:
http://java.sun.com/xml/ns/j2ee"; version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:sc
Hi Urs,
did you remember to add the
* @ejb.pk-field
tag to the get-method of your primary key field?
Regards,
Stefan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879472#3879472
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&
Hi all,
I'm experiencing a problem on my stateful session beans in jboss 3.2.7. The
session beans seem to time out after 80 seconds (I'm getting an "Object not
found"). It did not configure this in any special way and it did not happen
with 3.2.1. I'm using the Standard Stateful SessionBean co
Hey All,
has anyone of you ever overcome this error? Is it fixed in the latest JBoss
version? Unfortunately we're still using 3.2.1 and haven't found a workaround
for it yet.
Thanks,
Stefan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875609#3875609
Repl
