Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
(back to JavaTips) Example database datasource configs are in docs/example/jca. | ||||||||
Line: 9 to 9 | ||||||||
Pay attention to the pool sizes in standardjboss.xml , especially the Stateless Session Bean pool size, which is 100 by default. This seems pretty low, at least if you have methods that take a while to perform. If you're using MDB's you'll want to bump the MaximumSize in the Message Driven Bean container-invoker-conf to something larger than the default (which is 15). | ||||||||
Added: | ||||||||
> > | A strange error in jboss happened when I had the same ejb-jar declared twice in the application.xml. It caused strange errors that looked like classloader problems. For example, one error was an access violation error when one class tried to access a package-protected method of a class in the same package. Another had to do with a class not being able to call a method in another class because it couldn't find the appropriate signature, even though everything appeared to match. | |||||||
-- TobyCabot - 14 Nov 2002 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > | (back to JavaTips)
Example database datasource configs are in docs/example/jca.
JBoss and Oracle's jdbc driver don't play nice unless you turn on "TrackConnectionByTx".
Give jboss more memory than the java default - you'll be glad you did (or sorry if you don't)!
Pay attention to the pool sizes in standardjboss.xml , especially the Stateless Session Bean pool size, which is 100 by default. This seems pretty low, at least if you have methods that take a while to perform. If you're using MDB's you'll want to bump the MaximumSize in the Message Driven Bean container-invoker-conf to something larger than the default (which is 15).
-- TobyCabot - 14 Nov 2002 |