By Following tutorial Example ,I successfully created jar,war and ear files also ,by following each and every instruction specified in the tutorial
Here the problem is When i deploy ear file The server is generating the following error msg
17:35:40,828 INFO [EARDeployer] Init J2EE application: file:/D:/jboss-4.0.0RC1/server/default/deploy/FiboApp.ear
17:35:40,828 ERROR [MainDeployer] Could not initialise deployment: file:/D:/jboss-4.0.0RC1/server/default/deploy/FiboApp.ear
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at $Proxy7.deploy(Unknown Source)
But I placed application.xml file in META-INF only, and I checked generated ear file also,in that also file is there
Thanks in advance
Use thread dumps to validate the deadlock. If you think you have found one, test it with the latest jboss version (3.2.6 on the 3.2.x branch currently) and open a bug report in jira:
It won't be a deadlock. It will be the pool filler competing with another thread
to construct a connection in the pool.
Most likely you have a hit the bug from 3.2.3 relating to destroyed connections
and the semaphore counting.
Of course, if you'd bother to use search, read the change notes or tried the latest
version you wouldn't be bothering us with your redundant post.
Thanks for your infomation!
Because i am using jbossNukes1.1 which can only works under jboss-3.2.3, any workaround such as rebuilding jboss-3.2.3 myself?
Thanks for ur help!
I searched the changes between Jboss-3.2.3(revision 188.8.131.52 ) and revision 184.108.40.206, i noticed the following information.
"When flushing the pool we need to shutdown the discarded otherwise the pool filler could refill it with unreachable connections - a connection leak."
What does this mean?
Thanks a lot!
Can i disable the timeout for this connection pool?
I noticed that in jboss-3.2.3 and for HSQLDB, following configuration is there to disable idle connection removal. Can i set the same value for my connection also?
<!-- The time before an unused connection is destroyed -->
<!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
<!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connect