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

Error executing iwextattr commands from servlet

DarkSide

Hi,

I have an issue running iwextattr commands from a servlet on Solaris 9 (TeamSite 6.7.1 SP1).

If i execute the following command:

iwextattr -u -s TeamSite/Metadata/ea_name="hello there" //localhost/default/main/WORKAREA/wa_name/test.txt

This command returns "ERROR locating: there". As soon as i have spaces within the value, It splits the ea value into several parameters?!?!? If there is no spaces within the value it works fine.

If i execute this command from the command line directly, it works fine.
If i move the servlet to a Windows box, it also works fine.

any ideas? Does the iwui user who execute java code (like servlets) needs to be setup with a specific shell? or need any specific configuration on Solaris?

Thanks,
Pat

Find more posts tagged with

Comments

RonaldV

Pat,

try this:

iwextattr -u -s "TeamSite/Metadata/ea_name=hello there" //localhost/default/main/WORKAREA/wa_name/test.txt

Note the location of the first double-quote.

sumitk

I dont think double or single quote is required. Also, have you given full path for $iwhome/bin/iwextattr in your code?

ISCBorisB

I dont think double or single quote is required...

In this case it absolutely is. Read "DarkSide" post one more time, you'll see something like "As soon as i have spaces within the value, It splits..."
Of course nothing really *splits*, shell just (correctly) evaluates space as a parameter's delimiter. Double Quoting is the correct syntax in such case.

DarkSide

Pat,

try this:

iwextattr -u -s "TeamSite/Metadata/ea_name=hello there" //localhost/default/main/WORKAREA/wa_name/test.txt

Note the location of the first double-quote.

Thanks RonaldV,
This works well if i copy the servlet on the Windows box or if i run it from the command line on the Solaris server but it does not work from the servlet on Solaris Smiley Sad

it still returns "ERROR unable to locate there".

I've also changed the iwui user shell to the same one as i'm using with my user to run it from the command line but no luck.

I dont think double or single quote is required. Also, have you given full path for $iwhome/bin/iwextattr in your code?

Thanks sumitk,
Without double quotes or single quotes it also doesn't work.... Still same error message.
Yes, i use the full path within the code.

Thanks for your help,
Pat

Adam Stoller

Hi,

I have an issue running iwextattr commands from a servlet on Solaris 9 (TeamSite 6.7.1 SP1).

If i execute the following command:

iwextattr -u -s TeamSite/Metadata/ea_name="hello there" //localhost/default/main/WORKAREA/wa_name/test.txt

This command returns "ERROR locating: there". As soon as i have spaces within the value, It splits the ea value into several parameters?!?!? If there is no spaces within the value it works fine.

If i execute this command from the command line directly, it works fine.
If i move the servlet to a Windows box, it also works fine.

any ideas? Does the iwui user who execute java code (like servlets) needs to be setup with a specific shell? or need any specific configuration on Solaris?

Thanks,
Pat

How, exactly, are you coding this attempt to run the command?
It is possible that you may need to escape the double-quotes around "hello there" to get them through one-level of interpolation so that they remain in place for a second level of interpolation - but without seeing the exact code you are using it is difficult to tell.

Migrateduser

If using a servlet, a better design would be to use CSSDK classes to set Metadata or EA's using the CSExtendedAttribute class.

ISCBorisB

If using a servlet, a better design would be to use CSSDK classes to set Metadata or EA's using the CSExtendedAttribute class.

What does it mean, "better"? Better for what? By what metric?

For couple EAs it won't even be that much faster. Development efforts though are probably order of magnitude higher
than for a single command, perhaps more if you count required configurational changes.

This efforts may pay off if you have massive EAs setting, multiple EAs per each File in a branch, stuff like that.
Commands' shell forking overhead accumulates really fast so dedicated CSSDK Servlet *may* provide serious performance gain.

DarkSide

Thanks,
Updating the class to use CSSDK is what i did yesterday, everything works fine now.

What i was trying to do is something like the following

 
Process p;
p = Runtime.getRuntime().exec("/apps/iw-home/bin/iwextattr -u -s \"TeamSite/Metadata/ea_name=hello there\" //localhost/default/main/WORKAREA/wa_name/test.txt");

But it is fix now,
Thanks all for your help.
Pat

Migrateduser

What does it mean, "better"? Better for what? By what metric?

For couple EAs it won't even be that much faster. Development efforts though are probably order of magnitude higher
than for a single command, perhaps more if you count required configurational changes.

This efforts may pay off if you have massive EAs setting, multiple EAs per each File in a branch, stuff like that.
Commands' shell forking overhead accumulates really fast so dedicated CSSDK Servlet *may* provide serious performance gain.

"Better" - coz' using Runtime.exec craps out by default implementation if the stdin & stdout exceeds 255 bytes. You need supporting classes to handle the buffered i/o operations. Again, using runtime.exec fires off child process thread & the exception handling is not possible for the command "iwextattr" itself.

ISCBorisB

"Better" - coz' using Runtime.exec craps out by default implementation if the stdin & stdout exceeds 255 bytes. You need supporting classes to handle the buffered i/o operations. Again, using runtime.exec fires off child process thread & the exception handling is not possible for the command "iwextattr" itself.

Ah, wonders of Java again... I agree with you now, it is better to use right Classes for the task than wrong ones - much.

Btw, who (except you) said anything about Runtime? Runtime.exec does not work like a shell interpreter. In other words,
'command' parameter is not evaluated prior to execution. And yes, if you want to use streams you must do so with java.io, so what?