[GLASSFISH-15571] Create Resource Adapter Config is throwing an exception if jms is already started Created: 14/Jan/11 Updated: 21/Sep/15
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Tags:||3_1-next, 3_1-release-note-added, 3_1-release-notes, 3_1_2-exclude|
Start the JMS. In GUI, try to create a resource adapter config using jmsra and thread pool as "http-thread-pool".
Steps to reproduce the issue :
Exception in server log :
[#|2011-01-14T14:55:14.369+0530|SEVERE|glassfish3.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.work|_ThreadID=333;_ThreadName=Thread-2;|Thread-pool [ http-thread-pool ] not found|#]
[#|2011-01-14T14:55:14.370+0530|SEVERE|glassfish3.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.work|_ThreadID=333;_ThreadName=Thread-2;|An error occurred during instantiation of the work manager for resource-adapter [ jmsra ]
|Comment by Jagadish [ 14/Jan/11 ]|
ThreadPoolManager.getThreadPool() seems to throw the exception.
ThreadPoolManager only has "thread-pool-1" when the method "getThreadPool" is called.
Transferring to Ken for further investigation.
Steps to reproduce :
will show the reported exception in server.log
|Comment by Ken Cavanaugh [ 14/Jan/11 ]|
It looks like the issue may be in S1ASThreadPoolManager (which is in orb/orb-connector).
It is also not clear to me from the test case how you expect "http-thread-pool" to be created.
I am excluding this from 3.1 because I cannot investigate it or fix it before
|Comment by Jagadish [ 17/Jan/11 ]|
> It looks like the issue may be in S1ASThreadPoolManager (which is in orb/orb-connector).
Yes, whenever we create a thread-pool, we restart the server.
> It is also not clear to me from the test case how you expect "http-thread-pool" to be created.
> How does the http-thread-pool get created if it does not already exist?
> I am excluding this from 3.1 because I cannot investigate it or fix it before
I am able to create a new thread pool, restart server, configure the resource-adapter to use new thread pool successfully. However, I do not see http-thread-pool and admin-thread-pool in the list of thread pools of S1ASThreadPoolManager. Is this by design ?
eg: Following thread-pools are grizzly thread pools and will not be available for ORB thread pool clients/users.
I am adding '3_1-release-notes' tag to the issue so that it is documented/release-noted.
Could you please provide appropriate documentation changes for the same ?
|Comment by Jagadish [ 17/Jan/11 ]|
Update : I see that IIOPUtils exluding thread-pools that are used by http-listener (network-listener) while initializing ORB thread-pools.
|Comment by Scott Fordin [ 23/Mar/11 ]|
Need more info to add issue to 3.1 Release Notes.
|Comment by Jagadish [ 31/Mar/11 ]|
There are two thread pool implementations from GlassFish 3.0 ie., grizzly based thread-pool and ORB based thread-pool.
"create-resource-adapter-config" takes a thread-pool id as parameter which is based on ORB thread-pool.
ORB thread-pool, when initialized will verify whether an "thread-pool" is used by grizzly and will initialize the thread-pool only if grizzly is already not using the configuration.
So, there need to be a documentation stating that ORB thread pool manager will exclude any defined thread-pool configuration in the system if its already used by grizzly thread pool manager.
|Comment by Scott Fordin [ 13/Apr/11 ]|
Added issue to 3.1. Release Notes.
|Comment by Nazrul [ 21/Apr/11 ]|
It would be useful to look into this issue during 3.1.1
|Comment by scatari [ 25/Jun/11 ]|
Marking it as to be considered after 3.1.1.
|Comment by Tom Mueller [ 07/Feb/13 ]|
Targeting for 4.0.1 as bugs related to the orb do not need to be fixed for the RI/SDK.