You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Dain Sundstrom (JIRA)" <ji...@apache.org> on 2008/03/16 18:52:24 UTC
[jira] Created: (OPENEJB-778) Application in apps dir are some
times not loaded at startup
Application in apps dir are some times not loaded at startup
------------------------------------------------------------
Key: OPENEJB-778
URL: https://issues.apache.org/jira/browse/OPENEJB-778
Project: OpenEJB
Issue Type: Bug
Components: deployment
Affects Versions: 3.0-beta-2
Reporter: Dain Sundstrom
Priority: Blocker
Fix For: 3.0
If I deploy the itests using the command line deployment tool, stop the server and restart it. The itests application is not loaded in the new server.
My guess is this is cause by the deployment identification code. When the deployment tool installs an application, it unpacks it directly into the apps dir. When the server restarts, the startup code does not know what kind of module the unpacked directory is since it can not see the file extension of the original archive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENEJB-778) Application in apps dir are some
times not loaded at startup
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins reassigned OPENEJB-778:
-------------------------------------
Assignee: David Blevins
> Application in apps dir are some times not loaded at startup
> ------------------------------------------------------------
>
> Key: OPENEJB-778
> URL: https://issues.apache.org/jira/browse/OPENEJB-778
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: 3.0-beta-2
> Reporter: Dain Sundstrom
> Assignee: David Blevins
> Priority: Blocker
> Fix For: 3.0
>
>
> If I deploy the itests using the command line deployment tool, stop the server and restart it. The itests application is not loaded in the new server.
> My guess is this is cause by the deployment identification code. When the deployment tool installs an application, it unpacks it directly into the apps dir. When the server restarts, the startup code does not know what kind of module the unpacked directory is since it can not see the file extension of the original archive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENEJB-778) Application in apps dir are some times
not loaded at startup
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-778.
---------------------------------
Resolution: Fixed
> Application in apps dir are some times not loaded at startup
> ------------------------------------------------------------
>
> Key: OPENEJB-778
> URL: https://issues.apache.org/jira/browse/OPENEJB-778
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: 3.0-beta-2
> Reporter: Dain Sundstrom
> Assignee: David Blevins
> Priority: Blocker
> Fix For: 3.0
>
>
> If I deploy the itests using the command line deployment tool, stop the server and restart it. The itests application is not loaded in the new server.
> My guess is this is cause by the deployment identification code. When the deployment tool installs an application, it unpacks it directly into the apps dir. When the server restarts, the startup code does not know what kind of module the unpacked directory is since it can not see the file extension of the original archive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.