Bugs item #1058402, was opened at 2004-11-01 21:05
Message generated for change (Comment added) made by boesler
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1058402&group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: goeboe (boesler)
Assigned to: Nobody/Anonymous (nobody)
Summary: persistance problem

Initial Comment:
Hi,

I developing an project with JBoss AS 3.0 and it was 
running fine (based on the xpetstore project). Now I 
changed in this project to AS 4.0 (Windows XP, JDK 
1.4). This was no problem without one thing:
When a new user logged in, a new account is generated 
for him. This is realized by an create of an Login-Bean.
In my application the ejbCreate and the ejbPostCreate 
Method are called by a session bean in this case (I see 
two times output lbpc after passing on console), but 
then the process does not turn back to the calling 
session bean. I get no further information (black screen, 
no exception), but Timer-Beans are still running. Then 
after a timeout a rollback is initiated. The data, which 
are set in a value-Object as parameter are set in the 
Login-Bean, but not set in the database (sometimes 
values are set, sometimes not. I could not find out a 
systematic). In an other part of my software I use an 
similar mechanism to create beans and there it's always 
fine. I searched now already some days for a difference, 
but I could not find one. Perhaps you have an idear, 
why I have this mysthic error. 



----------------------------------------------------------------------

>Comment By: goeboe (boesler)
Date: 2004-11-13 21:19

Message:
Logged In: YES 
user_id=1150522

Hello,

this problem is solved, but I do not understand why???
I use a default entry in database as base for new users with 
an userId = 0 (find by findByPrimaryKey(0)). From the found 
default bean I take the value, fill up all other attributes with 
new data and create an new Bean with it (see attached file). 
When I looked now for the error again I take off this 
mechanism and created the base bean value with "new 
LoginValue()" directly and set the id = 0 and the other data 
afterwards and created the bean. Then the error does not 
come again. After that I changed back to the origin 
mechanism (same code as before) and the error does not 
come again (i have no idear why the error does not come 
again).

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2004-11-07 18:47

Message:
Logged In: YES 
user_id=175228

We need something in the way of an example which illustrates
the problem your seeing.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1058402&group_id=22866


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to