Frank Morton wrote: >>Wait. Are you using JAWS? I only ask that because all of the log stuff >>is from JAWS. >> >>If you are using JAWS, I can't help, because I don't know anything about >>the JAWS optimized loading process. >> >>-dain >> > > Well, I'm using 3.0 as distributed. I assumed if I set cmp-version to "2.x" > that I would be using the persistence-manager for Standard CMP 2.x > EntityBean, which in standardjboss.xml is org....JDBCStoreManager. > So, to answer your question as best I can, I don't think so > and I'm thinking if I am, it is by accident and shouldn't be the case. > JAWS is for pre-2.0, right? Can you shed light on this? > > Frank >
Hmm. Well I can help with JAWS: JAWS really should be removed from the 3.0 codebase because even if you deploy a vanilla 1.1 CMP bean, Dain's JDBCStoreManager should be handling it (uh, right, Dain?). To paraphrase Monty Python, "JAWS is dead! it is deceased! it is no more!" From the trace, JAWS isn't trying to do read-ahead. For the historic record, read-ahead defaulted off in JAWS. Does your ejb-jar have a jbosscmp-jdbc.xml, or a jaws.xml? It should be only jbosscmp-jdbc.xml (although any jaws.xml should be ignored by JBoss 3.0 or later). Trying to use jaws.xml with JBoss 3.x is getting to be a FAQ issue, but I know Dain's been trying to help you with this so I imagine you've got this right. I'll try to take a look tonight and see why 3.0 would use JAWS at all. -danch _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
