This is a remote deploy, which I don't believe QL tests will ever check
since they run locally only, correct?
The command I tried (against both b55 and b56) was this:
($host = papaya2.sfbay.sun.com, $archive = name of my WAR file)
asadmin deploy --host $host --port 4848 $archive (B55 and B56)
asadmin --host $host --port 4848 deploy $archive (B56 only -- new syntax)
All of the above failed the same way.
-Peter
Hong Zhang wrote:
> Hi, Peter
> No, the archive deploy should work, otherwise all the QL tests
> would fail. ;-)
>
> Can you provide the details of the cli commands you tried to use?
>
> Tim: can you follow up with Peter on this as you are more familiar
> with the upload part of the deploy?
>
> Thanks,
>
> - Hong
>
>> I tried to deploy with CLI (old and new syntax) and I get
>>
>> com.sun.enterprise.cli.framework.CommandException: remote failure:
>> Invalid chunk header
>> Command deploy failed.
>>
>> So archive deploy is not working? Or I made a mistake, in which case
>> this error message is not very helpful.
>>
>> -Peter
>>
>> Peter Williams wrote:
>>
>>>
>>> Hong Zhang wrote:
>>>
>>>> Hi, Peter
>>>> What kind of error did you get? Did this just stop working
>>>> recently or it has never worked?
>>>
>>> I don't know. I've never tried it before.
>>>
>>> Can you comment on my interpretation of requirements? I guess I can
>>> look at CLI client if this works there (I haven't tried that, but I
>>> presume it does).
>>>
>>>> We don't have an upload option in the DeployCommandParameters
>>>> in the server side (the upload option for admin cli case is handled
>>>> by the client side).
>>>
>>> That's fine. Given that it can be inferred from the POST request
>>> type, it would be redundant anyway.
>>>
>>> -Peter
>>>
>>>> This is probably why the url with the upload option does not work.
>>>>
>>>> Thanks,
>>>>
>>>> - Hong
>>>>
>>>> Peter Williams wrote:
>>>>
>>>>> I'm working on remote (or just archive) deploy to V3 from NetBeans
>>>>> and having trouble with the deploy command
>>>>>
>>>>> I've been given the impression that the format is as follows -- is
>>>>> correct?
>>>>>
>>>>> URL - no rules - I'm guessing at this point but I would have
>>>>> thought something like
>>>>> "http://$server:$port/__asadmin/deploy?name=$name&upload=true"
>>>>> would have been sufficient. And since it's a POST request,
>>>>> perhaps even upload is redundant.
>>>>> Request type - POST
>>>>> Content type - application/zip
>>>>> Body - binary zip file containing the archive to be deployed (e.g
>>>>> war file, ear file, etc).
>>>>>
>>>>> I haven't been able to get this to work --
>>>>>
>>>>> The CLI deploy command has a "upload" option documented, but
>>>>> including this over the HTTP api causes an error.
>>>>> The HTTP api is requiring a path parameter though what that could
>>>>> possibly mean for remote deployment escapes me. If I refer to a
>>>>> valid local (to the server) file, the server cheats but if I refer
>>>>> to an invalid file, the command is failed.
>>>>>
>>>>> Does anyone know if this works and/or what the requirements are?
>>>>>
>>>>> -Peter
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>