dev@glassfish.java.net

Odd behavior while creating jdbc-connection-pool in admin GUI

From: Shalini Muthukrishnan <Shalini.Muthukrishnan_at_Sun.COM>
Date: Mon, 28 Apr 2008 15:56:21 +0530

Hi All,

With the tp2 branch, I start the domain using "java -jar
modules/glassfish-10.0-tp-2-SNAPSHOT.jar, logged into the admin GUI
and tried to create a new connection pool with JavaDB.
When i click on finish after entering all the reqd properties, i get a
message on the console in the same page as
"An error has occurred Queue full"

In the logs :
SEVERE: Caused by: java.lang.Exception: Queue full
28 Apr, 2008 12:17:26 PM SEVERE: ... 86 more
28 Apr, 2008 12:17:26 PM SEVERE: Caused by:
java.lang.IllegalStateException: Queue full
28 Apr, 2008 12:17:26 PM SEVERE: at
java.util.AbstractQueue.add(AbstractQueue.java:64)
28 Apr, 2008 12:17:26 PM SEVERE: at
org.jvnet.hk2.config.Transactions.addTransaction(Transactions.java:107)
28 Apr, 2008 12:17:26 PM SEVERE: at
org.jvnet.hk2.config.Transaction.commit(Transaction.java:102)
28 Apr, 2008 12:17:26 PM SEVERE: at
org.jvnet.hk2.config.ConfigSupport.apply(ConfigSupport.java:171)
28 Apr, 2008 12:17:26 PM SEVERE: ... 85 more

After this, when i click on Finish again, it complains saying "An error
has occurred Object name cannot be null".

In the logs:
javax.management.InstanceAlreadyExistsException:
"amx:j2eeType=X-JDBCConnectionPoolConfig,name=oneMoreTest"
com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)

com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)

com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)

com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)

com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)

org.glassfish.admin.mbeanserver.AppserverMBeanServer.registerMBean(AppserverMBeanServer.java:238)

org.glassfish.admin.amx.config.AMXConfigLoader.createAndRegister(AMXConfigLoader.java:692)

org.glassfish.admin.amx.config.AMXConfigLoader._registerConfigBeanAsMBean(AMXConfigLoader.java:624)

org.glassfish.admin.amx.config.AMXConfigLoader.registerConfigBeanAsMBean(AMXConfigLoader.java:558)

org.glassfish.admin.amx.config.AMXConfigLoader.access$000(AMXConfigLoader.java:73)

org.glassfish.admin.amx.config.AMXConfigLoader$AMXConfigLoaderThread.registerOne(AMXConfigLoader.java:482)

org.glassfish.admin.amx.config.AMXConfigLoader$AMXConfigLoaderThread.doRun(AMXConfigLoader.java:535)

org.glassfish.admin.amx.config.AMXConfigLoader$AMXConfigLoaderThread.run(AMXConfigLoader.java:501)

|#]

When i check the list of connection pools in the connections pools page,
the pool that i just tried to create is there already.

I try creating a JDBC resource and all i observe is 100% CPU with
nothing happening. The process just hangs.

Any ideas? Or am i missing something here?

Thanks,
Shalini.