fastdev not end up the processing

dhaval soni
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 29, 2013

Hi,
When i execute fastdev link - "http://localhost:2990/jira/plugins/servlet/fastdev"
and use - click link there then it follows below processing. and continue processing.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building activeobjects-plugin
[INFO] task-segment: [com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:4.1.2:cli]
[INFO] ------------------------------------------------------------------------
[INFO] [amps-dispatcher:cli]
[INFO] [jira:cli {execution: virtual-execution}]
[INFO] [cli:execute]
[INFO] Opening port 4330 for socket cli access
[INFO] Waiting for commands...
maven2>
BUILD SUCCESSFUL
Can you please let me know , what action is expecting in this waiting event ? As processing is not end up.
Please let me know all steps to resolve this issue.
Thanks

8 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

6 votes
Answer accepted
dhaval soni
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 3, 2013

I do follow as below steps and it works:

1. open new command prompt and execute - "atlas-cli" and follow by "pi". (not to touch the command prompt where executed "atlas-run" command, keep it as running mode)

2. changes get updated over jira.

3. Now, on each change, have to refresh the browser screen and it will show "fastdev" screen with processing and then apply only "Pi" command at second command prompt which will end up as "maven2> "

so, further each changes, just need to give "pi" and it works.

dhaval soni
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 19, 2013

if "atlas-cli" shows error for port is used then use,

atlas-cli --cli-port 1025 or any unused port... and follow by pi. it will work.

1 vote
Logan G Hawkes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2013

Another possible cause/solution: I was using FastDev through the web interface and I saw the same behavior. FastDev would start installing and never complete. I found that there were about 7 java processes running that I couldn't account for. I stopped Jira by killing atlas-run, closed my SDK (Eclipse) and there were still 4 java processes referencing maven that I couldn't account for. I killed all the processes manually, restarted Jira and Eclipse, cleared my browser cache and FastDev worked perfectly. Before disabling FastDev in your pom.xml, try killing off any java processes that may be lurking in the background and retry.

Tony Filipe October 9, 2013

This is the exact same behaviour that I've observed too.

Tony Filipe November 3, 2013

I've found shutting down Jira and restarting takes a long time (on my machine about 10 minutes), so when this happens to me I disable the fastdev plugin in the Jira admin console then re-enable it and it starts working again.

0 votes
Johannes Moser June 24, 2015

Adding 

<useFastdevCli>false</useFastdevCli>

in the config like described in https://ecosystem.atlassian.net/browse/AMPS-1151 worked for me

0 votes
Royce Wong
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 5, 2015
0 votes
scayla May 20, 2013

[edit]after reviewing, you're talking about Jira dev, not confluence... the same procedure might apply since I had the same symptoms and it worked[/edit]

I kind of found another workaround for fastdev to work, don't know if all these steps are really required:

- add <useFastdevCli>false</useFastdevCli> in the maven-confluence-plugin configuration in your pom.xml (this part I'm just not sure if it's really needed but don't "have time" to try it out.)

- launch atlas-run

- configure the path to confluence (general config. The config was http://mycomputername:1990, I changed it to localhost:1990

- launch atlas-cli (I need to launch atlas-cli --cli-port 1025)

- now upon each modification, I hit ctrl-f5 and fastdev just works. If it works, you see the progress bar moving. If it doesn't work, you see the commands in the window but no progress and it will end up hanging up.

0 votes
Joe Clark
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 28, 2013

We've had quite a few reports of this problem and still don't quite understand the root cause. I've created https://ecosystem.atlassian.net/browse/AMPS-940 to investigate.

dhaval soni
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 28, 2013

Hi,

Yes it's right.

Now as an alternative i follow as below steps and it works quiet easy for me.

1. start the jira server - "atlas-run"

2. make any changes in code files.

3. open another command prompt and execute - "atlas-cli --cli-port 1025" (any port between 1024 to 65535 in case port already used error shows).

and follow by "pi" while prompt for waiting for command input.

Now, refreshing browser page, redirect to fastdev processing but , as we have already done for compiling and plugin install through (atlas-cli, pi) commands so, just refresh again then we can see the new changes over jira.

(now on every change, just need to follow same way atlas-cli,pi and jira will have update).

(make sure, atlas-run command prompt should not be close and we need to follow these commands into another command prompt window).

Thanks

Dhaval Soni

0 votes
Eric Kim February 3, 2013

Try clearing browser cache. I had few issues with fastdev and most of them were fixed after cache clearing.

0 votes
leonizm January 31, 2013

I'm having a similar issue with Confluence with using fastdev with skd 4.1.2 but fastdev says it's complete eventually but it's not taking the changes i made to the plugin.

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events