Is there a bug in jBoss or why is it giving this error? As anybody can see the
bean is defnied with exactly the same name on both xml descriptors.
-Tapani
12:22:28,250 ERROR [XmlFileLoader] failed to load jboss.xml. There could be a
syntax error.
| org.jboss.deployment.DeploymentException:
I changed read-ahead strategy to on-find in the of my jbosscmp-jdbc.xml. Now
JBoss executes a query, which finds the rows and selects all fields. But it
still retrieves the very same properties using separate SQL queries. As you can
see from the log dump the row is added to the preloaded data
Reading rows from the Collection is very slow. 1000 db rows takes 30 seconds
with one table and 6 seconds with another. The slower has about 5 times more
fields. With another A/S with the same db and JDBC driver no problems. Is this
normal JBoss performance?
JBoss 4.0.3SP1
Connector/J 3.1.11.
If I enable CMP debug then I get tons of SQL queries just for one findAll
finder call:
19:04:45,473 DEBUG [MyFooEntityBean] Executing SQL: SELECT xx_name,
xx_address,... FROM xx_foo WHERE (xx_foo_id=?)
| 19:04:45,504 DEBUG [MyFooEntityBean] Executing SQL: SELECT xx_name,
xx_address,... FROM
Why do I need to optimize when I have a very default bean in default JBoss
installation. I have not optimized the other A/S. Doesn't JBoss work at all
without optimization?
I tried changing the read-ahead settings in my jbosscmp-jdbc.xml, but that
didn't have any impact to the performance.
I get the following error while deploying. I can't understand what's wrong with
my jboss.xml. Both XML files are in the jar in META-INF directory. Without
jboss.xml I get no errors and the application works just fine. My JBoss version
is 4.0.3 SP1.
13:09:46,081 ERROR [XmlFileLoader] failed to
