For mxosrvr debugging make sure you set the timeouts in your dcs-site.xml 
https://cwiki.apache.org/confluence/display/TRAFODION/Debugging+Tips#DebuggingTips-DebugginganmxosrvrProcess

Anu

-----Original Message-----
From: Anoop Sharma [mailto:[email protected]] 
Sent: Wednesday, January 24, 2018 1:51 PM
To: [email protected]
Subject: RE: mxosrvr debugging

yes, show remoteprocess can be used but only from trafci and not from a 
standalone jdbc program.

anoop

-----Original Message-----
From: Roberta Marton [mailto:[email protected]]
Sent: Wednesday, January 24, 2018 1:46 PM
To: [email protected]
Subject: RE: mxosrvr debugging

Couple other things.
If you have already started mxosrvr, you can:

  Set idletimeout 0;   - so your session doesn't timeout
  Show remote process;  - this tells you what mxosrvr you are running (remote 
process may be one word, don't remember)

     Roberta

-----Original Message-----
From: Dave Birdsall [mailto:[email protected]]
Sent: Wednesday, January 24, 2018 1:15 PM
To: [email protected]
Subject: RE: mxosrvr debugging

Hi,

Never mind... I found it. See 
http://trafodion.apache.org/docs/dcs_reference/index.html#_configuration_files, 
the section "Servers". Just edit the conf/servers file and you're all set.

Dave

-----Original Message-----
From: Dave Birdsall [mailto:[email protected]]
Sent: Wednesday, January 24, 2018 1:12 PM
To: [email protected]
Subject: mxosrvr debugging

Hi,

I'm doing some debugging on the executor side of a JDBC T4 program. A JDBC T4 
program of course connects to an mxosrvr process; the executor runs inside of 
that. On a workstation local_hadoop environment, there are four of these and 
you don't know which one you're going to get in advance. So you have to put all 
four of them into debug.

That's a hassle, of course.

I remember there was mention of a knob somewhere that controlled the number of 
mxosrvrs in your workstation instance. I'd like to set that to one.

Can anyone remind me of what the knob was?

Thanks,

Dave

Reply via email to