[jboss-jira] [JBoss JIRA] Commented: (JBAS-6104) AS behaves strangely when deploying Seam projects
Jay Balunas (JIRA)
jira-events at lists.jboss.org
Fri Oct 17 10:20:21 EDT 2008
[ https://jira.jboss.org/jira/browse/JBAS-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12434239#action_12434239 ]
Jay Balunas commented on JBAS-6104:
-----------------------------------
Here is the console logging related to this. You'll notice that the time goes from "08:56:37,914" to "09:06:05,790". This 10 minutes saw a large amount of disk usage and and memory consumption. I will also attach a subset of the server.log that corresponds to this time.
08:56:37,314 INFO [EJBContainer] STOPPED EJB: com.jboss.dvd.seam.AuthenticatorAction ejbName: AuthenticatorAction
08:56:37,381 INFO [SessionSpecContainer] Stopping jboss.j2ee:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,name=AcceptAction,service=EJB3
08:56:37,381 INFO [EJBContainer] STOPPED EJB: com.jboss.dvd.seam.AcceptAction ejbName: AcceptAction
08:56:37,453 INFO [PersistenceUnitDeployment] Stopping persistence unit persistence.unit:unitName=jboss-seam-dvd.ear/jboss-seam-dvd.jar#dvdDatabase
08:56:37,454 INFO [SessionFactoryImpl] closing
08:56:37,454 INFO [SchemaExport] Running hbm2ddl schema export
08:56:37,510 INFO [SchemaExport] exporting generated schema to database
08:56:37,513 INFO [SchemaExport] schema export complete
08:56:37,513 INFO [SessionFactoryObjectFactory] Unbinding factory from JNDI name: persistence.unit:unitName=jboss-seam-dvd.ear/jboss-seam-dvd.jar#dvdDatabase
08:56:37,513 INFO [NamingHelper] JNDI InitialContext properties:{}
08:56:37,513 INFO [SessionFactoryObjectFactory] Unbound factory from JNDI name: persistence.unit:unitName=jboss-seam-dvd.ear/jboss-seam-dvd.jar#dvdDatabase
08:56:37,914 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader repository config: seam.jboss.org:loader=seam-dvd for vfszip:/jboss/projects/seam/2.1.0.GA/jboss-5.0.0.CR2/server/default/deploy/jboss-seam-dvd.ear use classloading metadata not loader repository config
09:06:05,790 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean ShowOrdersAction
09:06:05,790 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean AuthenticatorAction
09:06:05,790 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean CheckoutAction
09:06:05,790 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean FullTextSearchAction
09:06:05,791 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean EditCustomerAction
09:06:05,791 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean ShoppingCartBean
09:06:05,791 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean AcceptAction
> 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
More information about the jboss-jira
mailing list