[jboss-jira] [JBoss JIRA] Commented: (JBAS-6104) AS behaves strangely when deploying Seam projects

[Przemyslaw Sztoch (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12437368#action_12437368 ] 

Przemyslaw Sztoch commented on JBAS-6104:
-----------------------------------------

I can confirm this issue with Seam 2.1.0.SP1 and JBoss 5.0.0.CR2.
If I am using ear as ZIP-file, then I am waiting and waiting with heavy disk usage. And I have to kill -9 java...
If I am using ear as directory (uncompressed format), there is not heavy disk usage. And I can press CTRL-C, without kill -9 and stop JBoss.

> AS behaves strangely when deploying Seam projects
> -------------------------------------------------
>
>                 Key: JBAS-6104
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6104
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>    Affects Versions: JBossAS-5.0.0.CR2
>         Environment: JBoss AS 5.0.0.CR2
> Seam 2.0.3.CR1, Seam 2.1.0.CR1
>            Reporter: Jozef Hartinger
>            Assignee: Shane Bryzak
>         Attachments: partial_server.log
>
>
> I have encountered strange behaviour of AS when testing Seam 2.0.3.CR1 recently. To reproduce follow these steps:
> a) deploy Seam booking example
> b) some interaction is needed so book some hotel
> c) undeploy Seam booking example
> d) deploy Seam drools example
> example starts to deploy but at some point it hangs and looks like nothing is happening - no messages being appended in log not even debug messages however I noticed heavy disk usage. Usualy after waiting more than 10 minutes second example is still not deployed. It happens in both Seam 2.0.3.CR1 and Seam 2.1.0.CR1. Same situation with registration and itext example. Issue may be caused by problem with undeploying the first example. in some cases second example gets deployed after several minutes.

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