JBDS 7 slow deployment

[daxxy]

Version: 7.0.0.Alpha2

Build id: Alpha2-v20130424-2146-B202

I've been using JBDS 7 for awhile now.  It is very slow to start up. I don't like that,  but it doesn't prevent me from working.

Starting today it has become impossible to deploy my app.  I haven't made any radical changes to it, but suddenly it deploys SO SLOWILY sometimes it doesn't seemt o finish at all. It's painful working in this environment.

First it hangs at Hibernate Validator, then at Solder 3.1.1 and now it's stuck on Initializing Mojarra.

This started while trying to debug an issue having to do with this [#AS7-5310] javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored - JBoss Issue Tracker. Hopefully that's irrelevant.

and..  it's still on "Initializing Mojarra" (where it was when I typed it 2 paragraphs ago.

Finally finished.

Deployment started at 14:13 and finished at 14:19. See log below.

I downloaded the latest update site as a zip file, but installing updates were a problem. I got messages about how the module couldn't be installed only updated....only the Next button was grayed out so really the modules couldn't be updated either. (tease)

Help! I can't work like this.

TDR

14:13:47,095 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "dne-web.war" (runtime-name: "dne-web.war")

14:13:49,686 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for dacdev

14:13:49,907 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.dne-web.war" is using a private module ("org.jboss.security.negotiation:main") which may be changed or removed in future versions without notice.

14:13:51,027 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016002: Processing weld deployment dne-web.war

14:13:52,018 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named DeviceTagService in deployment unit deployment "dne-web.war" are as follows:

java:global/dne-web/DeviceTagService!gov.ssa.dne.nmst.service.DeviceTagService

java:app/dne-web/DeviceTagService!gov.ssa.dne.nmst.service.DeviceTagService

java:module/DeviceTagService!gov.ssa.dne.nmst.service.DeviceTagService

java:global/dne-web/DeviceTagService

java:app/dne-web/DeviceTagService

java:module/DeviceTagService

14:13:52,038 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named CiscoFailingSshService in deployment unit deployment "dne-web.war" are as follows:

java:global/dne-web/CiscoFailingSshService!gov.ssa.dne.nmst.service.CiscoFailingSshService

java:app/dne-web/CiscoFailingSshService!gov.ssa.dne.nmst.service.CiscoFailingSshService

java:module/CiscoFailingSshService!gov.ssa.dne.nmst.service.CiscoFailingSshService

java:global/dne-web/CiscoFailingSshService

java:app/dne-web/CiscoFailingSshService

java:module/CiscoFailingSshService

14:13:52,059 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SegmentListService in deployment unit deployment "dne-web.war" are as follows:

java:global/dne-web/SegmentListService!gov.ssa.dne.nmst.service.SegmentListService

java:app/dne-web/SegmentListService!gov.ssa.dne.nmst.service.SegmentListService

java:module/SegmentListService!gov.ssa.dne.nmst.service.SegmentListService

java:global/dne-web/SegmentListService

java:app/dne-web/SegmentListService

java:module/SegmentListService

14:13:52,089 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named DeviceListService in deployment unit deployment "dne-web.war" are as follows:

java:global/dne-web/DeviceListService!gov.ssa.dne.nmst.service.DeviceListService

java:app/dne-web/DeviceListService!gov.ssa.dne.nmst.service.DeviceListService

java:module/DeviceListService!gov.ssa.dne.nmst.service.DeviceListService

java:global/dne-web/DeviceListService

java:app/dne-web/DeviceListService

java:module/DeviceListService

14:13:59,089 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: dne-web.war

14:13:59,920 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.13 (redhat)

14:14:01,620 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 48) JBAS011402: Starting Persistence Unit Service 'dne-web.war#dacdev'

14:14:01,961 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016008: Starting weld service for deployment dne-web.war

14:14:04,611 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 48) HCANN000001: Hibernate Commons Annotations {4.0.1.Final-redhat-2}

14:14:04,712 INFO [org.hibernate.Version] (ServerService Thread Pool -- 48) HHH000412: Hibernate Core {4.2.0.Final-redhat-1}

14:14:04,772 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 48) HHH000206: hibernate.properties not found

14:14:04,822 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 48) HHH000021: Bytecode provider name : javassist

14:14:05,272 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 48) HHH000204: Processing PersistenceUnitInfo [

name: dacdev

...]

14:14:16,602 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 48) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider

14:14:18,823 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 48) HHH000400: Using dialect: org.hibernate.dialect.MySQLInnoDBDialect

14:14:19,084 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 48) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory

14:14:19,144 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 48) HHH000397: Using ASTQueryTranslatorFactory

14:14:19,744 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 48) HV000001: Hibernate Validator 4.3.1.Final-redhat-1

14:14:51,625 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-3) Solder Config XML provider starting...

14:14:51,686 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-3) Loading XmlDocumentProvider: org.jboss.solder.config.xml.bootstrap.ResourceLoaderXmlDocumentProvider

14:14:52,116 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-3) Reading XML file: vfs:/D:/work/software/jboss-eap-6.1/standalone/deployments/dne-web.war/WEB-INF/beans.xml

14:14:52,236 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-3) Reading XML file: vfs:/D:/work/software/jboss-eap-6.1/standalone/deployments/dne-web.war/WEB-INF/lib/ssa-identity-1.0.5-SNAPSHOT.jar/META-INF/beans.xml

14:14:52,296 INFO [org.jboss.solder.Version] (MSC service thread 1-3) Solder 3.1.1.Final (build id: 3.1.1.Final)

14:15:52,076 INFO [gov.ssa.dne.nmst.view.list.CarrierList] (MSC service thread 1-3) Creating the one and only CarrierList bean

14:15:52,167 INFO [gov.ssa.dne.nmst.view.list.StateSelectList] (MSC service thread 1-3) Creating the one and only StateList bean

14:15:52,267 INFO [gov.ssa.dne.nmst.view.list.YesNoList] (MSC service thread 1-3) Creating the one and only StateList bean

14:15:52,437 INFO [gov.ssa.dne.nmst.util.MaxResultsFactory] (MSC service thread 1-3) init() complete

14:15:54,267 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /dne-web

14:15:55,308 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 51) Initializing Mojarra 2.1.19-jbossorg-1 20130304-0420 for context '/dne-web'

14:19:49,209 INFO [org.richfaces.log.Cache] (ServerService Thread Pool -- 51) Selected fallback cache factory

14:19:49,250 INFO [org.richfaces.log.Cache] (ServerService Thread Pool -- 51) Creating LRUMap cache instance using parameters: {javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true, facelets.DEVELOPMENT=true, org.richfaces.skin=classic, javax.faces.PROJECT_STAGE=Development, org.richfaces.enableControlSkinning=true}

14:19:49,270 INFO [org.richfaces.log.Cache] (ServerService Thread Pool -- 51) Creating LRUMap cache instance of 512 items capacity

14:19:49,370 INFO [org.richfaces.log.Application] (ServerService Thread Pool -- 51) RichFaces Core Implementation by JBoss by Red Hat, version 4.3.3.Final

14:19:49,760 WARNING [org.richfaces.log.Application] (ServerService Thread Pool -- 51) JMS API was found on the classpath; if you want to enable RichFaces Push JMS integration, set context-param 'org.richfaces.push.jms.enabled' in web.xml

14:19:49,830 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 51) Monitoring jndi:/default-host/dne-web/WEB-INF/faces-config.xml for modifications

14:19:49,970 INFO [solder-servlet] (ServerService Thread Pool -- 51) Catch Integration for Servlets enabled

14:19:51,540 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dne-web.war" (runtime-name : "dne-web.war")

[daxxy]

It suddenly fixed itself. All day I've had a problem and now.....not.

I don't know what I changed. I removed a few things.  Brain tired.

[maxandersen]

Tany,

sorry for you having issues.

You seem to mention several issues and I assume the thing that is now fixed is the server specific issue giving errors when deploying (not related to tooling?)

Could you outline what slowness you are seeing ? how slow is it for you to start and compared to what ? JBDS 4,5,6 or plain eclipse ?

[daxxy]

Hiya Max - it was slow compared to the previous day.  I don't know whether the problem was related to the tools or eclipse.  It was a mystery, but since I was using JDBS this forum came to mind.

The slowness had purely to do with deploying -- and what struck me as odd is that deployment seemed to be hanging in the same place each time.

And then it went away -- I backtracked my steps for the day and undid them.  The only "unusual" thing I did was implement a phaselistener.  I re-added it after things sped up and the speed stayed.

It's one of those annoying and mysterious "fixed itself" problems.

[maxandersen]

Okey Tanya, again sorry for you slowness experience.

If it happens again try use jstack as described over here: https://community.jboss.org/wiki/TipsForReportingErrorsAgainstAnEclipsePlugin

Post that info and it could give an hint to what is 'stalling'/slowing JBDS down.