Bugs item #596355, was opened at 2002-08-17 05:52
Message generated for change (Settings changed) made by ejort
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=596355&group_id=22866
Category: JBossServer
Group: v2.4 (stable)
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Shinya Kasatani (kasatani)
Assigned to: Nobody/Anonymous (nobody)
Summary: XADataSourceLoader fails when maxSize=0
Initial Comment:
JBoss version: 2.4.8
OS: Red Hat Linux 7.3 (kernel
2.4.18-3smp)
JDK: 1.4.0_01 Hotspot server
VM
When using XADataSouceLoader with
setting
maxSize=0 and startup JBoss,
it causes an error like
this:
[2002-08-17 14:41:37,296] [INFO,DefaultDS]
XA Connection pool DefaultDS bound to
java:/DefaultDS
[2002-08-17 14:41:37,301]
[ERROR,DefaultDS]
Stopped
java.lang.RuntimeException: No
ManagedConnections Available!
at
org.jboss.pool.ObjectPool.getObject(ObjectPool.java:687)
at
org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:227)
at
org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.java:415)
at
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103)
at
sun.reflect.GeneratedMethodAccessor6.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967)
at $Proxy0.start(Unknown Source)
at
org.jboss.util.ServiceControl.start(ServiceControl.java:79)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.Main.<init>(Main.java:209)
at
org.jboss.Main$1.run(Main.java:110)
at
java.security.AccessController.doPrivileged(Native
Method)
at
org.jboss.Main.main(Main.java:106)
[2002-08-17
14:41:37,309] [ERROR,ConfigurationService]
Unexpected error
java.lang.RuntimeException: No
ManagedConnections Available!
at
org.jboss.pool.ObjectPool.getObject(ObjectPool.java:687)
at
org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:227)
at
org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.java:415)
at
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103)
at
sun.reflect.GeneratedMethodAccessor6.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967)
at $Proxy0.start(Unknown Source)
at
org.jboss.util.ServiceControl.start(ServiceControl.java:79)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.Main.<init>(Main.java:209)
at
org.jboss.Main$1.run(Main.java:110)
at
java.security.AccessController.doPrivileged(Native
Method)
at
org.jboss.Main.main(Main.java:106)
The bug
appeared when I upgraded
from 2.4.7 to 2.4.8.
----------------------------------------------------------------------
Comment By: Wolfgang Kaltz (jwkaltz)
Date: 2002-12-03 07:22
Message:
Logged In: YES
user_id=387111
Actually, what is worse is that you get a similar error when
you don't set a maxSize attribute at all.
And, in the examples in older JBoss versions maxSize was not
necessarily set. So anybody upgrading to JBoss 2.4.8 or
later is bound to have problems.
My opinion: this is a bug, because of the error handling. If
a connection pool cannot be set because a mandatory
attribute is missing, you should throw an appropriate
exception - and not a RuntimeException
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=596355&group_id=22866
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
