You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Dave Sowerby (JIRA)" <de...@tuscany.apache.org> on 2008/08/07 23:20:44 UTC

[jira] Created: (TUSCANY-2539) File handle on composite affecting behaviour of tuscany deployments in websphere.

File handle on composite affecting behaviour of tuscany deployments in websphere.
---------------------------------------------------------------------------------

                 Key: TUSCANY-2539
                 URL: https://issues.apache.org/jira/browse/TUSCANY-2539
             Project: Tuscany
          Issue Type: Bug
         Environment: Websphere 6.1 Windows
            Reporter: Dave Sowerby
             Fix For: Java-SCA-1.3.1


During development of an EJB component, I'm having trouble when I wish to redeploy an ejb which contains a composite which has been used to initialise an SCA node.  Once this has happened, when I redeploy, the same code which previously worked now presents the following exception:

java.io.FileNotFoundException: JAR entry service.composite not found
in C:\Program Files\IBM\WebSphere\AppServer\profiles\tuscany\installedApps\soa\simple-ear.ear\simple-ejb.jar

Despite the fact that the file is present....

I believe that Tuscany has a file handle upon the composite file and upon the redeploy that file handle causes this stack....

The only means of successful redeploy is:

1) Uninstall application
2) Stop application server
3) Remove installedApps files for application
4) Start application server
5) Reinstall application

Once these steps are complete the application once again proceeds as normal.  

The application attached in mail thread http://markmail.org/message/rpjlc5iaal6neabj can be used to demonstrate this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (TUSCANY-2539) File handle on composite affecting behaviour of tuscany deployments in websphere.

Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
    [ https://issues.apache.org/jira/browse/TUSCANY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622481#action_12622481 ] 

Simon Laws commented on TUSCANY-2539:
-------------------------------------

Solution committed to 1.3.1 at r685821

> File handle on composite affecting behaviour of tuscany deployments in websphere.
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2539
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2539
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Websphere 6.1 Windows
>            Reporter: Dave Sowerby
>            Assignee: Simon Laws
>             Fix For: Java-SCA-1.3.1
>
>
> During development of an EJB component, I'm having trouble when I wish to redeploy an ejb which contains a composite which has been used to initialise an SCA node.  Once this has happened, when I redeploy, the same code which previously worked now presents the following exception:
> java.io.FileNotFoundException: JAR entry service.composite not found
> in C:\Program Files\IBM\WebSphere\AppServer\profiles\tuscany\installedApps\soa\simple-ear.ear\simple-ejb.jar
> Despite the fact that the file is present....
> I believe that Tuscany has a file handle upon the composite file and upon the redeploy that file handle causes this stack....
> The only means of successful redeploy is:
> 1) Uninstall application
> 2) Stop application server
> 3) Remove installedApps files for application
> 4) Start application server
> 5) Reinstall application
> Once these steps are complete the application once again proceeds as normal.  
> The application attached in mail thread http://markmail.org/message/rpjlc5iaal6neabj can be used to demonstrate this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (TUSCANY-2539) File handle on composite affecting behaviour of tuscany deployments in websphere.

Posted by "Raymond Feng (JIRA)" <de...@tuscany.apache.org>.
    [ https://issues.apache.org/jira/browse/TUSCANY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621363#action_12621363 ] 

Raymond Feng commented on TUSCANY-2539:
---------------------------------------

It's probably related to URL.openStream().close() which doesn't close the enclosing jar file if the URL represents a jar entry. As a result, the jar file cannot be overwritten during redeploy. We have a utility class in tuscany code that works around the issue by disabling the jar file cache but it's not used for all the place.

> File handle on composite affecting behaviour of tuscany deployments in websphere.
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2539
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2539
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Websphere 6.1 Windows
>            Reporter: Dave Sowerby
>             Fix For: Java-SCA-1.3.1
>
>
> During development of an EJB component, I'm having trouble when I wish to redeploy an ejb which contains a composite which has been used to initialise an SCA node.  Once this has happened, when I redeploy, the same code which previously worked now presents the following exception:
> java.io.FileNotFoundException: JAR entry service.composite not found
> in C:\Program Files\IBM\WebSphere\AppServer\profiles\tuscany\installedApps\soa\simple-ear.ear\simple-ejb.jar
> Despite the fact that the file is present....
> I believe that Tuscany has a file handle upon the composite file and upon the redeploy that file handle causes this stack....
> The only means of successful redeploy is:
> 1) Uninstall application
> 2) Stop application server
> 3) Remove installedApps files for application
> 4) Start application server
> 5) Reinstall application
> Once these steps are complete the application once again proceeds as normal.  
> The application attached in mail thread http://markmail.org/message/rpjlc5iaal6neabj can be used to demonstrate this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (TUSCANY-2539) File handle on composite affecting behaviour of tuscany deployments in websphere.

Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws reassigned TUSCANY-2539:
-----------------------------------

    Assignee: Simon Laws

> File handle on composite affecting behaviour of tuscany deployments in websphere.
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2539
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2539
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Websphere 6.1 Windows
>            Reporter: Dave Sowerby
>            Assignee: Simon Laws
>             Fix For: Java-SCA-1.3.1
>
>
> During development of an EJB component, I'm having trouble when I wish to redeploy an ejb which contains a composite which has been used to initialise an SCA node.  Once this has happened, when I redeploy, the same code which previously worked now presents the following exception:
> java.io.FileNotFoundException: JAR entry service.composite not found
> in C:\Program Files\IBM\WebSphere\AppServer\profiles\tuscany\installedApps\soa\simple-ear.ear\simple-ejb.jar
> Despite the fact that the file is present....
> I believe that Tuscany has a file handle upon the composite file and upon the redeploy that file handle causes this stack....
> The only means of successful redeploy is:
> 1) Uninstall application
> 2) Stop application server
> 3) Remove installedApps files for application
> 4) Start application server
> 5) Reinstall application
> Once these steps are complete the application once again proceeds as normal.  
> The application attached in mail thread http://markmail.org/message/rpjlc5iaal6neabj can be used to demonstrate this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TUSCANY-2539) File handle on composite affecting behaviour of tuscany deployments in websphere.

Posted by "Dave Sowerby (JIRA)" <de...@tuscany.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Sowerby updated TUSCANY-2539:
----------------------------------

    Affects Version/s: Java-SCA-1.3

> File handle on composite affecting behaviour of tuscany deployments in websphere.
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2539
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2539
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Websphere 6.1 Windows
>            Reporter: Dave Sowerby
>             Fix For: Java-SCA-1.3.1
>
>
> During development of an EJB component, I'm having trouble when I wish to redeploy an ejb which contains a composite which has been used to initialise an SCA node.  Once this has happened, when I redeploy, the same code which previously worked now presents the following exception:
> java.io.FileNotFoundException: JAR entry service.composite not found
> in C:\Program Files\IBM\WebSphere\AppServer\profiles\tuscany\installedApps\soa\simple-ear.ear\simple-ejb.jar
> Despite the fact that the file is present....
> I believe that Tuscany has a file handle upon the composite file and upon the redeploy that file handle causes this stack....
> The only means of successful redeploy is:
> 1) Uninstall application
> 2) Stop application server
> 3) Remove installedApps files for application
> 4) Start application server
> 5) Reinstall application
> Once these steps are complete the application once again proceeds as normal.  
> The application attached in mail thread http://markmail.org/message/rpjlc5iaal6neabj can be used to demonstrate this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (TUSCANY-2539) File handle on composite affecting behaviour of tuscany deployments in websphere.

Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws resolved TUSCANY-2539.
---------------------------------

    Resolution: Fixed

Committed to trunk at revision: 686185  


> File handle on composite affecting behaviour of tuscany deployments in websphere.
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2539
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2539
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Websphere 6.1 Windows
>            Reporter: Dave Sowerby
>            Assignee: Simon Laws
>             Fix For: Java-SCA-1.3.1
>
>
> During development of an EJB component, I'm having trouble when I wish to redeploy an ejb which contains a composite which has been used to initialise an SCA node.  Once this has happened, when I redeploy, the same code which previously worked now presents the following exception:
> java.io.FileNotFoundException: JAR entry service.composite not found
> in C:\Program Files\IBM\WebSphere\AppServer\profiles\tuscany\installedApps\soa\simple-ear.ear\simple-ejb.jar
> Despite the fact that the file is present....
> I believe that Tuscany has a file handle upon the composite file and upon the redeploy that file handle causes this stack....
> The only means of successful redeploy is:
> 1) Uninstall application
> 2) Stop application server
> 3) Remove installedApps files for application
> 4) Start application server
> 5) Reinstall application
> Once these steps are complete the application once again proceeds as normal.  
> The application attached in mail thread http://markmail.org/message/rpjlc5iaal6neabj can be used to demonstrate this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.