agents on w2k

M

my53lf

New Member
Could someone tell me why when I start a broker the agents don't do it. I thought it was a problem with the JRE, but I solved installing the Java Devaloper Kit and my problem persist.
My operative system is windows 2000, but I don't think that's the problem cuz on a slower machine didn't appear that problem.

I'd appreciate your suggestions6
 
Hi all running win 2000 advanced server with webspeed 3.1C. If you have websped 3.1B or below you cannot use the Progress Explorer to start up agents, its buggy. It seems to be fixed with webspeed 3.1C its a java to C issue,. The familar console doesnt jive so well with webspeed until 3.1C.

To start your agents, first set your connection and propath for a defined broker (wsbroker) for example.

Also make sure you specify the nameserver.

With 3.1B or below to start agents, I could do two things:

1. In the Progress explorer, specify to have the broker start up automatically when the Progress 3.1" service starts. Then stop and start the service in the windows services.

2. The direct method is to use the wtbman command This command can be used at the command line to stop, start, trim agents etc. First, you must make sure the wtbman command is in your windows path. Once you do this, then go to the command line and type the following:

to start a broker:

c:\wtbman -i (name of broker) -start
example: c:\wtbman -i wsbroker -start

TO STOP THE BROKER

c:\wtbman -i (name of broker) -stop
example: c:\wtbman -i wsbroker -stop

Warning: The Brokers do not start up quickly. If you start a broker, wait a couple seconds before trying to pull up workshop. Our admin and I had that issue thinking our broker wasnt starting, because we would immediately try pulling up workshop after starting a broker and getting the familiar websped error. start it, wait for the confirmation that its strated at the command line, then wait a few seconds before starting up workshop.
 
I thank your suggestions...
I finally solved my problem, what I did was replace the JVM called "jvmStart.exe" by the one called "jvmStartw.exe" only a f@☼╚{~® W !!!

Now, if somebody could explain me...
 
Thanks for all suggestions but, recently i discovered my problem...

I made a query on the progress knowledge base with my error code (8171):


When Progress Version 9.1B is run on the Intel Win32 platform (Windows
NT, Windows 2000) with the Pentium IV processor,
AdminService can create the following error message when you try to
start any broker/agent that is defined in ubroker.properties. The
error shows in the admserv.log file:

[AdminServer]
SvcControlCmd.connectToService() failure:
Unable to connect to the service process at
rmi://pchost:20931/NS1(after 10 retries) (8171)

EXPLANATION:

The problem is produced by the just-in-time (JIT) compiler that is
provided with JDK 1.1.8. It does not handle the Pentium IV set of
instructions.

SOLUTION:

There are two solutions to the problem:

- You can disable the JIT if you change the Windows
Registry entries
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\9.1B\JAVA
and
HKEY_CURRENT_USER\Software\PSC\PROGRESS\9.1B\JAVA:

1) Edit the JVMARGS key (JVMARGS -ms1m) to add the -nojit
parameter:

JVMARGS -ms1m -nojit

2) Find the $DLC\bin\ubutil.bat and change the last line to:

"%JVMSTRT%" -o stderr -s -m silent "%JVM%" -nojit -classpath "%JCP%"
-DInstall.Dir="%DLC%" -DWork.Dir="%WRK%" %UBUTILPKG%.%UBUTILCLASS%
%PARMS%

3) Make the same change to the ubconfig.bat.

(Notice the newly added -nojit parameter.)

- Download the Intel Pentium 4 Processor support for JDK/JRE
1.1.x for Windows.

The upgrade for Pentium 4 systems is included with JDK/JRE
1.1.8_006 for Windows.

Alternatively, Pentium 4 systems are also supported by the Java 2
Platform, Standard Edition (J2SE) Version 1.3.0 and later.

http://java.sun.com/products/jdk/1.1/jre/download-jre-windows.html

NOTE: Some of the JDK/JRE versions might not be supported by
Progress.




Here's the URL for KBase error codes
 
You must log in or register to reply here.
Back
Top