Topic
  • 2 replies
  • Latest Post - ‏2013-05-30T17:58:11Z by Rahul_K
Rahul_K
Rahul_K
2 Posts

Pinned topic CDJAI Node constructor "slow"

‏2013-04-15T18:06:39Z |

We have an application that has been running fairly smoothly for months now (W2K8, Connect Direct v4.5.01)

Suddenly the "Node" constructor has started taking several minutes (average 3) to execute

 

import com.sterlingcommerce.cd.sdk.*; 

........

Node cdNode = null; 

......

try 

File lcuFile = new File("user@pnode.lcu"); 

cdNode = new Node(lcuFile.getCanonicalPath()); 

......

......

 

In short bursts (maybe every hour or so) a bunch of times it works "normally" with no delay passing through this section of code. And then as unpredictably as it started flowing quickly, it goes back to being a pain. We've done warm, cold restarts, even bounced the box itself to no avail.

Any pointers? 

  • VolkerFriedrich
    VolkerFriedrich
    178 Posts
    ACCEPTED ANSWER

    Re: CDJAI Node constructor "slow"

    ‏2013-05-28T13:18:40Z  

    Some ideas:

    The Node constructor will establish a TCP/IP connection to the API port of your C:D node and attempt a logon locally on the C:D server.

    A first step might be to investigate those areas.  Does the delay occur in the Java client, on the network or on the server side?
    For example, if your Java application writes a log file, you could compare timestamps against an CMGR trace captured on the C:D node.

    Any changes to the user authentication on the server?  Is your ActiveDirectory having hick-ups or responding slow?

    Another idea is to try running the CLI (Direct.exe) at a time when your Java application is going slow.  Does it show the same delay?

     

  • VolkerFriedrich
    VolkerFriedrich
    178 Posts

    Re: CDJAI Node constructor "slow"

    ‏2013-05-28T13:18:40Z  

    Some ideas:

    The Node constructor will establish a TCP/IP connection to the API port of your C:D node and attempt a logon locally on the C:D server.

    A first step might be to investigate those areas.  Does the delay occur in the Java client, on the network or on the server side?
    For example, if your Java application writes a log file, you could compare timestamps against an CMGR trace captured on the C:D node.

    Any changes to the user authentication on the server?  Is your ActiveDirectory having hick-ups or responding slow?

    Another idea is to try running the CLI (Direct.exe) at a time when your Java application is going slow.  Does it show the same delay?

     

  • Rahul_K
    Rahul_K
    2 Posts

    Re: CDJAI Node constructor "slow"

    ‏2013-05-30T17:58:11Z  

    Some ideas:

    The Node constructor will establish a TCP/IP connection to the API port of your C:D node and attempt a logon locally on the C:D server.

    A first step might be to investigate those areas.  Does the delay occur in the Java client, on the network or on the server side?
    For example, if your Java application writes a log file, you could compare timestamps against an CMGR trace captured on the C:D node.

    Any changes to the user authentication on the server?  Is your ActiveDirectory having hick-ups or responding slow?

    Another idea is to try running the CLI (Direct.exe) at a time when your Java application is going slow.  Does it show the same delay?

     

    Thanks for these ideas - in case it ever happens again. The problem disappeared as mysteriously as it appeared, which was several months ago.

    We suspected it may have had something to do with our remote partner. In exasperation we mentioned our troubles to them one evening, and magically everything was fine early the next morning so we moved on to other things, assuming they had done something, recycled their service, or whatever.

    Thinking aloud, I'm wondering if there any interaction with any snode partners (defined in the netmap) that could have contributed? I suppose we could capture a "normal" trace, to compare with if it ever occurs again ...