[esb-issues] [JBoss JIRA] Commented: (JBESB-2313) Handle wise pooling/concurrency

[Kevin Conner (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12451733#action_12451733 ] 

Kevin Conner commented on JBESB-2313:
-------------------------------------

I spent a lot of time over the weekend trying to tidy up the integration but am no longer confident that it is correct.  Given the timescales involved for the release I have decided to roll wise back to the configuration as of 4.4CP2.

> Handle wise pooling/concurrency
> -------------------------------
>
>                 Key: JBESB-2313
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2313
>             Project: JBoss ESB
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 4.5
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 4.5
>
>
> We need to look at the current wise integration and make sure that we are controlling all aspects that could impact classloading/concurrency.
> The previous version contains a factory that creates clients using the first client classloader, sharing that with other deployments that may use the same.  We need to make sure that each deployment has access to a client using the correct classloader.
> We also need to take control over the wise configuration as the factory singleton is initialising itself using wise-core.properties obtainable from the first deployment which invokes the factory, ignoring all other properties.  As well as making sure that the right properties are used in the right deployment we should also be overriding the temporary directory, if we are within the context of a server, so that the temporary directory is automatically under the server directory and is unique per deployment.
> The concurrency issues identified in JBESB-2301 should also be checked, as well as checking the current Port access.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira