we call a Natural Programm from Java and get more and more a ‘Callee not found’ Error. Broker is up and Running. Natural Services (3 Running Natural Threads) is Registerd to Broker and other Services wouldn’t give an Error. The called Natural Programm is at the called Library. Sometimes a fresh generated Testprogram (A IDL generated from Natural IDL-Generater using the Workbench; Generate and run Test) would heal the Error and then the Service would answer normaly for a time but then one after one of the 3 Running Naturalserverprocesses would return the ‘Callee not found’ Problem again.
Natural is 3.1.6 - BS2000, Broker is 7.1.2 - BS2000, Client is a Javaprogramm (Java 1.4.2) using EntireX Runtime 7.1.1.60.
Does anyone have a hint to what i have to change or would it better to open a Request at Servline24?
Greetings Sascha
/Edit: We always have to use conversational Mode becauce of the Size of the Parameters the Natural Programm gets back. And we always use NaturalLogon. (setNaturalLogon, setRPCUserId and setPRCPassword). We don’t use EntireX Security but Natural Security
What about adding ENTIREX to the steplib of the RPC-server ?
If this doesn’t do the trick perhaps you should make a support request for this to clear up all the technical details versions/other products (like Natural security etc).
BTW you should/could use a different setup for your production RPC.
For instance you won’t need the SYSIDL there (unless you access your sources from prod
Finn
We don’t use Sources at Prod but good to know I’ll have a look if the next days the Error comes again. But you have to agree this Solution sounds crazy
have look in broker attribute file, check timeouts for conversations and server non activity
check, that your Natural rpc server is not confugured also as a client (AUTORPC must not be ON)
keep in mind, that in conversational rpc (after client opened conversation) the rpc server is listening only THIS client and will not
get freed if client does not call “close conversation” at the end…
Use SMH to identify all server replicates which have registered to the same server name. Check their Natural configurations, maybe there is a bad guy with a wrong configuration.
Run the Natural RPC Servers with trace enabled to see what’s going on when the error occurs.
SMH is only running on non-BS2000 Systems AFAIK. So i use Broker Controll Center but i get displayed all RPC-Servers normaly.
I belive i should send such a trace at the next days to my Support Request (Few Minutes ago i had to send a Javatrace)
@Aldo we have to logon to the User-called Library. We wrote a Wrapper for USR1057N so we could get Sources to Java and use External Tools like WinMerge to show the Developer a good Programmdiff. And some more like that.