[jbosstools-issues] [JBoss JIRA] (JBIDE-19328) wf8.2 in fs+rse mode with strange publish behavior (cmd line)
Rob Stryker (JIRA)
issues at jboss.org
Thu Feb 19 07:33:49 EST 2015
Rob Stryker created JBIDE-19328:
-----------------------------------
Summary: wf8.2 in fs+rse mode with strange publish behavior (cmd line)
Key: JBIDE-19328
URL: https://issues.jboss.org/browse/JBIDE-19328
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.3.0.Alpha1
Reporter: Rob Stryker
1) Start with a clean wf8.2
{code}
rm -rf wildfly-8.2.0.Final.zip.expanded/
cd ../zipped
ls -1 wildfly-8.2.0.Final.zip | ./unzipAndMove.sh
cd ../unzipped/wildfly-8.2.0.Final.zip.expanded/bin/
./add-user.sh
{code}
2) Start server in eclipse. filesystem + rse, defaults, localhost, no changes, all standard
Process command line appears to be as follows:
22608 pts/1 Sl+ 0:10 java -Dprogram.name=JBossTools: WildFly 8.x -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Dorg.jboss.logmanager.nocolor=true -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
3) Copy a simple exploded web project into your deployments folder with a cp -R command. Then, touch WebProjectName.war.dodeploy to ensure it is picked up by server
4) Observe following sysout from server:
07:23:49,973 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
07:23:53,921 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
07:23:54,990 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "WebApp1.war" (runtime-name: "WebApp1.war")
07:23:55,295 INFO [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017534: Registered web context: /WebApp1
07:23:55,347 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "WebApp1.war" (runtime-name : "WebApp1.war")
07:24:00,366 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017535: Unregistered web context: /WebApp1
07:24:00,381 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-14) HV000001: Hibernate Validator 5.1.3.Final
07:24:00,413 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment WebApp1.war (runtime-name: WebApp1.war) in 51ms
07:24:00,448 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "WebApp1.war" (runtime-name: "WebApp1.war")
07:24:05,451 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
If we repeat but instead of starting from eclipse, we start from cmd line (standalone.sh) it seems to work, which may indicate a problem in how we're launching (?). Process details when started via standalone are as follows:
23536 pts/3 Sl+ 0:10 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/server.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules org.jboss.as.standalone -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list