Websphere Deployment Failing through Nolio

[Legacy User]

Hi,

I am using Nolio Websphere actions for deploying EAR on Websphere Server. I am attaching the screenshot here.

So what I am doing is, I am checking the application status. If the application is not installed I am installing it and then starting it,

If it is installed, I am updating it and then again starting it.

 

I tested it on dummy ears and it was working fine. It showed no errors.

 

With the actual EARs I am facing issues.

Get application status is working fine.

Update Application is working fine. -> Application is getting updated.

 

But it is failing to start. It gives an error such as , application state unknown.

 

Please guide me here.

 

Regards,

Gautam

[James Panetti]

Could you share the exact errors?  Errors found in the agent logs would be of particular interest, to begin with.

[Legacy User]

Hi James,

 

Please find the error log snapshot as under :

From Nolio:

 

From nimi.log:

 

From nolio-all.log

[Sachin.Ambulkar]

Hi Gautam,

 

Just want to understand if you try doing this same deployment manually from the WAS console , is working fine. Also can you confirm that the user account which you are using for the deployment have equal rights/permission to start application.

Looking at error messages application seems unreachable and I suspect the deployment of EAR file is not happening in expected way , may be missing some configuration steps.

I would advice try doing deployment manually and then replicate same steps in RA and see if this helps.

 

Thank You

Sachin

[Legacy User]

Hi Sachin,

 

Yes manual deployment is running without any issues. Also there is no concerns with the user account.

 

Regards,

Gautam

[Sachin.Ambulkar]

Hi Gautam,

 

If manual deployment works fine I suspect you are missing some steps , the flow for Web sphere app would be like below:

 

1. Get Status of application

2. Stop application

3. Synchronize Nodes

4. Update application for existing application.

5. Synchronize nodes

6. Start Application

 

Please check if this helps , more you can review the WAS server logs so you can get more idea the reason for this issue.

 

Thank You

Sachin

[Legacy User]

Hi Sachin,

 

In my case, I have standalone servers. This is where I am trying to deploy. So I don't think Synchronizing nodes is needed here.

 

I tried this above sequence and it is failing. We don't have node managers for these servers.

 

One observation I will let you know :

In our setup , the application update is working fine. It fails while starting giving the errors as already described above.
When I cancel the job and run the independent job just to start the server, it works fine. So just a time delay.

 

 

I tried another test case: get app status -> stop -> uninstall -> install -> start. Still no luck.

 

Regards,

Gautam

[Legacy User]

Sry I missed to attach the screenshot.

[Sachin.Ambulkar]

Can you please confirm if the manual synchronization of nodes work from WAS console. We may need to review the WAS server logs and Agent logs to see what is causing this issue.

 

Thank You

Sachin

[Anon Anon]

hi Gautam,

              could you please try synchronising the nodes in the flow using the actions (WAS - Synchronize xxxx) after the install/update action and then starting the application, see if that works.

thanks,

nagesh

[Legacy User]

Hi Nagesh,

 

Sure I will try and post my finding here with you.

 

Regards,

gautam

[James Panetti]

Hi Gautam, just wanted to check in since we haven't seen a post here since the 11th.  Are you still stuck on this issue?

[Legacy User]

Hi James,

 

Yes the issue is still there. Just to confirm we are not facing any issue doing the deployment manually.

But when doing from nolio we are.

I have provided all the log snapshot earlier.

 

Regards,Gautam

[James Panetti]

You mentioned last time you were going to try manually synchronizing nodes and/or testing the "WAS - Synchronize" action.  Could you please share your results with us?

[Legacy User]

Hi James,

There are no issues running the deployments manually.

The issue is resolved. I have changed the design of the flow. So it is get application status -> Stop -> Uninstall -> Install (in first loop) and then again get application status -> start in (second loop). This solves the issue.

I have tested it multiple times, it is a success.

Thank you all for helping me out here with this issue.

Regards,

Gautam

[James Panetti]

Great news!  And I can totally relate -- I've spent too much time scratching my head on some of my own flows when the solution was to just rearrange the order of some actions.