Protocol Handler ?

All of a sudden deployments to LSCS preview are failing, 7.2.1 on Linux.

The deployment log says

lscsRuntimeProtocolHandler=${StartDeploy_LscsRuntimeProtocolHandler} (File name too long)

What is this ? I cannot find where that variable is set

Andy

Find more posts tagged with

Comments

Adam Stoller

...
lscsRuntimeProtocolHandler=${StartDeploy_LscsRuntimeProtocolHandler} (File name too long)

Just shooting in the dark:

Is it at all possible that you somewhere exceeded the MAXPATHLEN? Like:

nipper

That is the rub. I am using the OOTB LSCS deployment, which is an area diff.

No files are being reported as failed, there is no file at all listed near this error (I expect it is a DNR like step after the regular deployment)

Rick Poulin

It's not a DNR, it's a payload adapter... not that it helps to understand why it's crapping out on you.

tec_iwov

might want to file something with support.

nipper

I did open a support case.

Doing more digging I see that I am getting the error: got 500 for URL http://localhost:8080/lscs/v1/import

lscs diags work on 8080

Rick Poulin

Ah, that one I've seen before. You'll get more detailed error messaging from the lscs.log of the instance you're deploying to.

session var.zip

Rohan_t1

In our case, we have seen more conclusive information in Websphere logs. Check if App server log help you in anyway.