Hi, thanks for the response.
Yes, I have tested this before. I think that was when I called the entity beans directly rather than via my stateless session bean. It worked then. I�m actually beginning to wonder wether this might have something to do with my session bean. I get these messages when refreshing: ================= POOL ERROR ? ======================== 2002-05-20 16:56:40,209 DEBUG [org.jboss.ejb.plugins.EntityInstancePool] The Pool for com.morelogs.guestbook.beans.gbEntryCMP has been overloaded. You should change pool parameters. ====================================================== and the follwing which may or may not be normal?? Does anyone have an idea? =============== WHY QUESTION MARKS ? ================== 2002-05-20 16:56:40,170 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.guestbook/gbEntry] Executing SQL: SELECT entry_id,author_id, entry_subject, entry_text, entry_date, entry_views FROM gbEntries WHERE (entry_id=?) OR (entry_id=?) OR (entry_id=?) 2002-05-20 16:56:40,179 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.guestbook/gbEntry] Executing SQL: SELECT entry_id,author_id, entry_subject, entry_text, entry_date, entry_views FROM gbEntries WHERE (entry_id=?) OR (entry_id=?) OR (entry_id=?) 2002-05-20 16:56:40,189 DEBUG ======================================================= I don�t understand why there are question marks in the where clause. Could that be the cause? Having said that, I�m still getting data and no exception. I know this may not be a struts issue but I posted to the jboss list some time ago and have not yet received an answer. Has anyone experienced this? Thanks, Michael ----- Original Message ----- From: "JM" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 7:36 PM Subject: RE: Reloading data... > Have you tried using a single servlet client to test the jboss db call? > One that uses the same interface to your ejb but simply displays the data > "as is"??? > This might be a quicker way to debug container(s)/caching issues. > > ....just a snack for thought. > > > JM > > > -----Original Message----- > > From: Michael Delamere [mailto:[EMAIL PROTECTED]] > > Sent: Monday, May 20, 2002 10:41 AM > > To: Struts Users Mailing List > > Subject: Re: Reloading data... > > > > > > thanks, > > > > I will try that. > > > > Michael > > > > > > ----- Original Message ----- > > From: "Adam Hardy" <[EMAIL PROTECTED]> > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > Sent: Monday, May 20, 2002 4:26 PM > > Subject: Re: Reloading data... > > > > > > > It could be phpMyAdmin not releasing the connection & so not letting any > > > other queries see the new data (I've no experience with php) > > > It could be the page is being cached in your browser > > > It could be the list bean is being stored in your session and recycled > > > instead of replaced > > > > > > Try updating the data through two different browser windows and see if > > > the windows show each other's new data. > > > Or try updating a record manually instead of inserting and see if that > > > gets show. > > > > > > Michael Delamere wrote: > > > > > > >Hi, > > > > > > > >no I haven�t done anything to stop this from happening. I thought that > > > >there might have been an obvious answer to this. > > > > > > > >Basically what happens is: > > > > > > > >1) start at form > > > >2) fill form and press submit > > > >3) list of entries from DB is shown > > > >4) I go into phpMyAdmin and add another record > > > >5) I hit refresh but no new record is shown > > > >6) I press the back button to get to the form (the old data is still > > there > > > >which is normal) > > > >7) I hit refresh and the old data is still there > > > >8) I restart server (jboss) and start again at step 1 (now _all_ the > > records > > > >are shown) > > > > > > > >I�m not sure if this is a struts issue. I was hoping that > > someone might > > > >have experienced this before. Here�s the output I get in jboss3.0.RC2: > > > > > > > >===================================================== > > > >15:45:20,400 INFO [Engine] oreilly: Processing a POST for /saveGBEntry > > > >15:45:20,400 INFO [Engine] oreilly: Looking for ActionForm bean under > > > >attribute 'gbEntryForm' > > > >15:45:20,401 INFO [Engine] oreilly: Recycling existing > > ActionForm bean > > > >instance of class 'com.morelogs.guestbook.forms.GBEntryForm' > > > >15:45:20,401 INFO [Engine] oreilly: Populating bean properties from > > this > > > >request > > > >15:45:20,402 INFO [Engine] oreilly: Validating input form properties > > > >15:45:20,402 INFO [Engine] oreilly: No errors detected, accepting > > input > > > >15:45:20,403 INFO [Engine] oreilly: Looking for Action instance for > > class > > > >com.morelogs.guestbook.actions.SaveGBEntryAction > > > >====================================================== > > > >So it does seem to be doing something but why is the newly added entry > > > >missing. > > > > > > > >Thanks for your time, > > > > > > > >Michael > > > > > > > > > > > > > > > >----- Original Message ----- > > > >From: "Adam Hardy" <[EMAIL PROTECTED]> > > > >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > > >Sent: Monday, May 20, 2002 3:24 PM > > > >Subject: Re: Reloading data... > > > > > > > > > > > > > > > > > > > >>Just because the formbean is in the session and the values in > > it will be > > > >>redisplayed, it doesn't mean the action won't be executed completely, > > > >>along with the DB query, unless you specifically checked that the data > > > >>was in the formbean already in order to switch the query off. > > > >> > > > >>I couldn't say why the data you added to the database doesn't show up. > > > >>Perhaps it didn't meet the query where clause? Try updating > > the record > > > >>that does show up, and seeing if your manual update shows up this way. > > > >> > > > >>I'm not quite sure what scenario you are doing. You say "go > > back to the > > > >>form and hit refresh" - presumably you mean going back to the > > form with > > > >>the back button after you have submitted the form once? > > > >> > > > >>Adam > > > >> > > > >> > > > >> > > > >>Michael Delamere wrote: > > > >> > > > >> > > > >> > > > >>>Hi, > > > >>> > > > >>>it works now, there�s no problem iterating through my beans. There�s > > > >>> > > > >>> > > > >just > > > > > > > > > > > >>>_one_ other thing though. I added another gbEntry manually > > into my DB > > > >>> > > > >>> > > > >but > > > > > > > > > > > >>>when refreshing the browser the new entry doesn�t show up. > > > >>> > > > >>>When I go back to the form and refresh, the data that I entered > > > >>> > > > >>> > > > >previously > > > > > > > > > > > >>>is still there. I presume that all the data is coming from the > > session. > > > >>>Does this mean that when I hit refresh, no db-query is repeated. > > > >>> > > > >>> > > > >Instead > > > > > > > > > > > >>>the gbEntries are retrieved from the session? How can I best > > avoid this > > > >>> > > > >>> > > > >kind > > > > > > > > > > > >>>of behaviour. > > > >>> > > > >>>Thanks, > > > >>> > > > >>>Michael > > > >>> > > > >>> > > > >>>-- > > > >>>To unsubscribe, e-mail: > > > >>> > > > >>> > > > ><mailto:[EMAIL PROTECTED]> > > > > > > > > > > > >>>For additional commands, e-mail: > > > >>> > > > >>> > > > ><mailto:[EMAIL PROTECTED]> > > > > > > > > > > > >>> > > > >>> > > > >>> > > > >>> > > > >> > > > >>-- > > > >>To unsubscribe, e-mail: > > > >> > > > >> > > > ><mailto:[EMAIL PROTECTED]> > > > > > > > > > > > >>For additional commands, e-mail: > > > >> > > > >> > > > ><mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > >-- > > > >To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > >For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
