Hi Anissa,
Thanks for the response.
>I have never heard about this problem with GlassFish v2.1.1.
This is the first time I ever encountered it with two years of experience
with Glassfish.
>You are saying that even if you deploy the war to "server", it still
>puts "server" as "Available Targets" instead of showing it is selected?
No, it puts it in the correct location "Selected Targets" and runs fine. But,
if I move it to "Available Targets" and then attempt to move it back to its
original position in "Selected Targets", the GUI quickly pops it back to
"Available Targets". (This happens whether I pick the server, cluster or
all.)
>How about the target listing page ? does that page show the info
>correctly ?
>Can you use the command "create-application-ref" to add the target ?
I'll try that.
>> "It appears to deploy successfully, but when I look at the status of
the
>> application using the admin GUI, it tells me I need to redeploy. "
>Where does it give you the status of "need to redeploy", I don't
>remember such a feature/screen in GlassFish v2.1.1
Actually, it is in the "Web Applications" table. The right most column
labeled "Action" only contains "Redeploy" for the application that was
deployed to the "domain" rather than having "Launch" and "Redeploy". (Its not
really a status, but there is something going on that is telling the GUI to
not display the "Launch" action for that particular application. When I look
at:
Applications [1]> Web Applications [2]> myapplication / Target, there are no
"Selected Targets" shown even though I deployed to the domain (which has
always worked in the past)
Also, I'm certain that it has nothing to do with this particular application
since if I move any currently deployed application from the "Selected
Targets" to the "Available Targets" and attempt to move them back, I get the
same "snap back" to "Available Targets" column.
One thing I failed to mention is that I did get a deployment error the
first time I attempted to deploy to the cluster, but it went away after I
restarted the cluster and redeployed. I wonder if some configuration file
got corrupted during the first failed deployment? I know sometimes Glassfish
doens't clean up after itself very well when there is a failed deployment. I
did attempt to remove all references to the failed application deployment,
but that did not cure the problem this time.
Do you know which component would be controlling this behavior so I can turn
on Fine loging on that component?
Thanks,
Rob
[1]
https://mtops.ticom-geo.com:4848/applications/applications.jsf
[2]
https://mtops.ticom-geo.com:4848/applications/webApplications.jsf
--
[Message sent by forum member 'rrr6399']
View Post: http://forums.java.net/node/809995