Skip to Content
author's profile photo Former Member
0
Former Member

Deployment Stuck in NDS

Posted on Oct 05, 2005 at 02:05 PM 41 Views

Hello Folks,

I have a J2EE Enterprise App Project in NDS. I am able to create ear file, deploy to my local J2EE engine. But the last time I deployed, the "Deploy Output View" stuck at the log "<b>Created a temporary copy: ....ear[more]</b>" and doesn't move. However, when I try to access the application through browser, I am able to see my application deployed. This means, only NDS updated with deployment status? or something wrong with SDM?

But since, the deployment is stuck in NDS. I cannot right click on ear and say "Deploy to J2EE Engine" as its now shaded. So, I have to restart NDS and J

I tried restarting J2E engine but I still have the same problem, this time when I deploy, it fails with <b>Deployment Aborted</b> and details say

<b>

Deployment exception : Server localhost did not accept login request as apiadmin on port 50018 - Cannot log in. There are already active sessions:

Session id 0 / An administrator logged in via API /

Inner exception was :

Server Localhost did not accept login request as apiadmin on port 50018 - Cannot log in. There are already active sessions:

Session id 0 / An administrator logged in via API /

</b>

Any solutions?

Thanks and I appreciate ur time,

Kiran

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Oct 05, 2005 at 08:05 PM
    0

    I got it working after restart of NDS and J2E engine. But still haven't found a proper resolution to this problem.

    When I had the problem, I tried to open up SDM (RemoteGui.bat) and then it doesn't allow my to login, saying "Another session open... "

    Thanks,

    Kiran

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Oct 07, 2005 at 02:26 AM

      Hi Kiran,

      When you get this problem check the following.

      1) Is someone else is deploying their application on the same server?

      2) Has someone logged into SDM using remotegui or telnet?

      3) If you are sure that its not the case, then you can restart your SDM using NWDS. Goto J2EE engine view. Right click on SDM and say Restart Process.

      Now you should be able to Deploy Again.

      Regards,

      Shubham

    Comment on This Answer

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.