Not Seeing Complete Log Message

[mduffy_lists]

I do agree it is impossible to help somebody that doesn't give ANY
useful information. This usually shows a lack of a understanding of the problem.

See... this is what I am saying... not only jboss is slow "by default" but support always gives grumpy answers... what are your politics on customer service? I mean ok, its free but if you want users don't frighten away.....
Now here is the info you requested would you mind taking a look please?:

Windows XP Dell Optiplex P4 2.6 Hyperthreading enabled 512 RAM
Java 1.4.2
Oracle 8.1.7 running on solaris 450 4processors 4Gb of RAM
Jboss 3.2.4

On Jboss 3.2.4 the same page takes 3 times longer 2.4.4. Default configuration (excep read ahead) on 2.4.4 and the following tweaks on 3.2.4:
- Read Only Getters on al beans.
- Commit Option A
- run .bat modified for more memory and Server Hotsopot -Xms256m -Xmx512m -server
- Services deployed:
client-deployer-service.xml
cache-invalidation-service.xml
hsqldb-ds.xml
iiop-service.xml
jboss-jca.sar
jboss-local-jdbc.rar
jboss-xa-jdbc.rar
mail-service.xml
properties-service.xml
sqlexception-service.xml
transaction-service.xml
user-service.xml
uuid-key-generator.sar

DS file

<xa-datasource>
false
<jndi-name>XAfxokDS</jndi-name>
<track-connection-by-tx>true</track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<xa-datasource-property name="URL">jdbc:oracle:oci:@myTNS</xa-datasource-property>

<xa-datasource-property name="User">myUser</xa-datasource-property>
<xa-datasource-property name="Password">myPassword<xa-datasource-property>
<!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
<!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
<!-- Checks the Oracle error codes and messages for fatal errors -->
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa -->
<no-tx-separate-pools/>
<!--<track-statements>true</track-statements>-->
<prepared-statement-cache-size>500</prepared-statement-cache-size>

</xa-datasource>


<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager




- PAD = true on jboss-service.xml to make oracle connection work.
- All logs to INFO in log4j.xml
- Web service running on 8080 disabled.
- Both Jboss are connected using mod_jk2 to an Apache 2.0.48 running on the same machine.

I have used the jmx console and I see the getters take long time to execute, specially on varchar2 fields. The pages shows a list of trades. an each line takes 1 second while on jboss 2.4.4 takes 300 ms....

Let me know if you need any more information

guix