[jboss-jira] [JBoss JIRA] Closed: (JBAS-6617) Server failure when including aop metadata inside a sar inside a zip

Stale Pedersen (JIRA) jira-events at lists.jboss.org
Wed Apr 15 04:53:36 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stale Pedersen closed JBAS-6617.
--------------------------------

    Fix Version/s: JBossAS-5.1.0.CR1
       Resolution: Done


> Server failure when including aop metadata inside a sar inside a zip
> --------------------------------------------------------------------
>
>                 Key: JBAS-6617
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6617
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>    Affects Versions: JBossAS-5.0.1.GA
>         Environment: Linux, JBoss 5.0.1, 1.5 jdk
>            Reporter: Matt Wringe
>            Assignee: Stale Pedersen
>             Fix For: JBossAS-5.1.0.CR1
>
>         Attachments: test.zip
>
>
> If a sar includes an aop metadata file, and that sar is within a zip file then the server will fail when it gets deployed.  The server cannot be shutdown using normal means (crtl-c, shutdown.sh, or have the processed normally killed), the process must be forcibly killed in an unsafe manner.
> There are no error messages displayed on the console or the logs, the output to the console and logs just stop as the server hangs.
> Tail of output to console:
> 19:42:03,847 INFO  [ProfileServiceImpl] Loaded profile: ProfileImpl at 1f2e95f{key=org.jboss.profileservice.spi.ProfileKey at 143b82c3[domain=default,server=default,name=default]}
> 19:42:06,491 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
> 19:42:21,196 INFO  [NativeServerConfig] JBoss Web Services - Stack Native Core
> 19:42:21,197 INFO  [NativeServerConfig] 3.0.5.GA
> Tail of output to server.log:
> 2009-03-12 19:42:31,493 DEBUG [org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer] (main) Extracting aop bean metadata factories for  AbstractVFSDeploymentContext at 14562017{vfszip:/data/temp/jbossas/jboss-5.0.1.GA/server/default/deploy/test.zip/test.sar/test-aop.xml}
> 2009-03-12 19:42:31,493 DEBUG [org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer] (main) Got AspectManager attachment org.jboss.aop.AspectManager at 26efd3 for AbstractVFSDeploymentContext at 14562017{vfszip:/data/temp/jbossas/jboss-5.0.1.GA/server/default/deploy/test.zip/test.sar/test-aop.xml}
> If the sar is deployed outside of the zip, then it will work properly. If the aop metadata is moved from the sar to the root of the zip then it will also work.
> Situation:
> test.zip/test.sar/test-aop.xml -> server failure
> test.sar/test-aop.xml -> works
> test.zip/test-aop.xml -> works

-- 
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

        



More information about the jboss-jira mailing list