nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Resetting UI Services incredibly slow

System

Hey guys,

I'm moving slowly from a lead dev role into some system administration, and as such I'm a bit out of my depth on my current issue. I've got a copy of 7.3.1 set up on a virtual Win7 box, and my rebuilds are really dragging.

The main culprit seems to be the resetting of Interwoven UI. I'm not really sure why, and the times for resets can vary wildly, but on this tiny content store and nearly brand new install, reset times of 3 minutes (pretty common) seem atrocious.

Where can I start digging to find out what the problem is? I'm aware that I could just be suffering from resource over-allocation on the virtualization server, but if there is anywhere else to look, I'd really like to clear this up.

Especially as I'm writing some hairy servlets at the moment, and having to do rebuilds roughly every 5 minutes...

Thanks!

EDIT: While I'm being all needy and everything, can anyone tell me how I might be able to edit servlets and see the changes live without doing a rebuild? I know the changes in iw-cc.war would be wiped out on a rebuild, but I can handle that, I'm just going nuts having to do a 3-5 minute rebuild every time I misspell a javascript function.

Find more posts tagged with

Comments

nipper

Define slow. When the UI moved to jboss, there was a 2 minute delay inserted to make certain everything was stopped before it starts.

When I run a UI build, it takes about 6 minutes before the task completes, however, they UI is not completely up by then. I watch server.log for the complete message which typically takes another minute.

Migrateduser

Sorry, I should have put the average time right up top on the post. It's taking an average of 3 minutes.

I guess that's not really slow in this context, then. I was concerned there were errors that were hitting a timeout or something.

Cheers.

nipper

Sorry, I should have put the average time right up top on the post. It's taking an average of 3 minutes.

I guess that's not really slow in this context, then. I was concerned there were errors that were hitting a timeout or something.

Cheers.

Quick bragging. Smiley Very Happy

Everything looks fine

Adam Stoller

I'm moving slowly from a lead dev role into some system administration, and as such I'm a bit out of my depth on my current issue. I've got a copy of 7.3.1 set up on a virtual Win7 box, and my rebuilds are really dragging. .

The fact that it works at all is questionable - since Windows 7 is not a supported OS on which to run TeamSite 7.3.1. Read the Release Notes for a list of what is supported.

mart2001

If your rebuild takes only 3 mins, that is an accomplishment! I usually have to wait for 5-6 minutes before the UI would come up. And yes, building java program is a main on the TeamSite server where you have to do rebuild every now and then taking down the TS UI with it, and hoping that it actually comes up!

You can try to look at the last message of this thread:
http://devnet.interwoven.com/forums_vb/showthread.php?t=34855&page=3&pp=10&highlight=testing+java

Where they are deploying directly into the tomcat itself instead of going through the build process (unsupported), but you'll need to change that to apply to jboss in the 7.x release.

Migrateduser

I've seen a hack (errr, workaround) floating on the net about configuring the war to only check for and restart on certain changes. But I believe this was pre-JBoss.

And yeah, I can tell you that setting this up on Win7 wasn't the greatest thing ever, but it works!

Thanks for all the input guys... I guess the title of this thread should be changed, haha.