Not really a jBoss bug, but possibly worth while fixing: When sending a non-parsable bmp SQL statement, the transaction it uses seems to never get closed. I wrote a simple load test which just creates entity beans and invokes a method on it. It worked fine for about 16,000 beans - about 100 or so queries where unparsable (I read the data from another table containing names and forgot to escape quotes). Then the client freezes when invoking a remote method (well, I assume the remote method never returns). It still shows up in the log. Other clients against the same server also hang on method invokation - find methods still work fine. After a long time, the server spits out the following error message (multiple times) Transaction XidImpl [ID=257, Global=robertpc/113256, Branch=] timed out. Status = STATUS_ACTIVE but the client's are still dead. As I said, not sure whether this is worth fixing (btw, this is jBoss-2.0FINAL). Also, is there some documentation about jBoss specific performance tuning anywhere? Stuff like - transaction timeouts - cache configurations Any experiences / stuff which made a difference would be nice as well. We run on Linux with postgres as the backend and resin as the client. Cheers, Robert. -- Robert Schulz [EMAIL PROTECTED] -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED]
