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; } } }

Running EA in Bulk Causing Teamsite to go down

Reghunath

Hi,
I'm working on T.S 6.5 in Windows 2003.

We have to migrate Documents(around 500-600) from one server to another. Each document has 20-30 EAs tied to them. We have written a script to rip the EA from the source server and stored them as text with customized format(Embedded with CLT iwextattr). Then we move the Text file to destination server and run another program which reads the text and runs the commands in it.

Problem Statement:
----------------------
The issue is, after running 3500-4000 CLT commands the server stops responding. The error we are getting is "Couldnot connect to teamsite Server".

After some analysis we found that 3500 CLT(iwextattr) commands can be executed at single shot, and need to wait for 5-10 mins and execute the another batch of 3500 commands...(This 3500 differs with server. In our QA server its around 3000, so please don't go with the number).

We suspect the thread count that CLT spawns, which is exceeding the max count which Operating System/Teamsite can support. This is merely a theoritical assumption.

Help:
---------
* I would like to get help regarding the reason behind this issue.
* If you have any pre-solution, that would be more helpful.

Thanks,
Reghu.

Find more posts tagged with

Comments

ISCBorisB

Hi,
I'm working on T.S 6.5 in Windows 2003.

We have to migrate Documents(around 500-600) from one server to another. Each document has 20-30 EAs tied to them. We have written a script to rip the EA from the source server and stored them as text with customized format(Embedded with CLT iwextattr). Then we move the Text file to destination server and run another program which reads the text and runs the commands in it.

Problem Statement:
----------------------
The issue is, after running 3500-4000 CLT commands the server stops responding. The error we are getting is "Couldnot connect to teamsite Server".

After some analysis we found that 3500 CLT(iwextattr) commands can be executed at single shot, and need to wait for 5-10 mins and execute the another batch of 3500 commands...(This 3500 differs with server. In our QA server its around 3000, so please don't go with the number).

We suspect the thread count that CLT spawns, which is exceeding the max count which Operating System/Teamsite can support. This is merely a theoritical assumption.

Help:
---------
* I would like to get help regarding the reason behind this issue.
* If you have any pre-solution, that would be more helpful.

Thanks,
Reghu.

With the use of iwextattr's -x switch you may assign all 20-30 of your EAs in one call, look for example [thread=23246]here[/thread].
Alternatively you may use Java/CSSDK to access TSServer and set all EAs of all Files in the single thread.

nipper

As to why, you will need to ask IWOV, however to make this less likely to crash, you can use the XML form to set all EAs at once on a file rather than one at a time. That will drop by a large amount the work you are doing and you should be good to go.

This is what I run to set 3 at once

[html]

sub setDCREAs
{
my($file, $name1, $value1, $name2, $value2, $name3, $value3) = @_;

my $iwextattr = "$iwhome/bin/iwextattr";

my $EA_xml = qq(

$name1
$value1

$name2
$value2

$name3
$value3

);
if (open(PIPE, "|$iwextattr -s -x $file")){
print PIPE $EA_xml;
close(PIPE);
} else {
debug($debugFile, "EAs failed on $file ") ;
}
}

[/html]

nipper

With the use of iwextattr's -x switch you may assign all 20-30 of your EAs in one call, look for example [post=23246]here[/post].
Alternatively you may use Java/CSSDK to access TSServer and all of it in the single thread.

Bo, that link was not to what I was expecting, you may want to recheck the link. I think I know which thread you were referencing.

ISCBorisB

Bo, that link was not to what I was expecting, you may want to recheck the link. I think I know which thread you were referencing.

Thanks Andy. Fixed it

Reghunath

Thanks a lot for your quick response.
This looks to be a perfect solution...

I will execute this approach and let you guys know about the improvements...

Thanks a ton,
Reghu.

Reghunath

Hi,
This is one great improvement related to performance...
One thing annoying is , EA XML has to be fed as String argument rather than File reference.

Thanks,
Reghu.

nipper

Hi,
This is one great improvement related to performance...
One thing annoying is , EA XML has to be fed as String argument rather than File reference.

Thanks,
Reghu.

It will take STDIN so if you have it in a file, then you can pipe it to iwextattr, but if you are scripting you WANT it to use STDIN rather than a file, performance, esp in a bulk import will be soooo much better.

ISCBorisB

you can pipe it to iwextattr...

Or you can redirect STDIN to a File, either way will work. Thou shalt know and love thy Command shell

Reghunath

When I tried to use EA XML file reference(File Path) in the place of $EA_xml, it didn't work.
As I mentioned, if the file contents are provided as string its working...

if (open(PIPE, "|$iwextattr -s -x $file")){
print PIPE $EA_xml;
close(PIPE);
} else {
print("EAs failed on $file ") ;
}

When you meant use STDIN to PIPE it to iwextattr, is it something different from above? Providing XML file reference in the Command prompt?
Please advise...

Thanks for your time...

Thanks,
Reghu.

ISCBorisB

When I tried to use EA XML file reference(File Path) in the place of $EA_xml, it didn't work.
As I mentioned, if the file contents are provided as string its working...

if (open(PIPE, "|$iwextattr -s -x $file")){
print PIPE $EA_xml;
close(PIPE);
} else {
print("EAs failed on $file ") ;
}

When you meant use STDIN to PIPE it to iwextattr, is it something different from above? Providing XML file reference in the Command prompt?
Please advise...

Thanks for your time...

Thanks,
Reghu.

Of course it is different.
Code Piping interpretes the filename as a command to which output is to be piped. Perl fragment above illustrates this technique.

Shell Piping is the Command syntax that allows to *pipe* command_A output as commnad_B input.
For example, in Windows you can "pipe" using something like the following:
  type YourXMLFilePath | C:\iwhome\bin\iwextattr -s -x vpath
Or in UNIX:
  cat YourXMLFilePath | /iwhome/bin/iwextattr/iwextattr -s -x vpath

Alternatively, instead of piping you can redirect command's STDIN to the File:
  iwextattr -s -x vpath <YourXMLFilePath

Kapish?

Reghunath

Thanks a lot for the information...

I will try and update the status...

Thanks,
Reghu.

Reghunath

Hi,
This works great...

Thanks for the help...

Regards,
Reghu.