Hi Guys,
I'm using Sun's 1.4.1 JDK on Debian unstable:
$> java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
The instrument client works fine for me, of course it takes 10
seconds or so for all my instrumentables to be loaded (during
this time 'not connected' is displayed in the tab), but once they
are all loaded the tab label is updated and it works fine.
This is all latest code from CVS, compiled with the same jdk, and the
altrmi server is on the same host as the client.
Hope that helps.
Cheers,
Marcus
On Tue, Nov 05, 2002 at 11:59:50AM +0900, Leif Mortenson wrote:
> Can anyone else confirm this in a linux system? I have been using Sun's
> 1.4 JDK for
> win32 without any problems. Unfortunately, Altrmi does not contain any
> logging code,
> so it makes it difficult to track down problems. I assume you are using
> the latest
> code from CVS?
>
> I went in and added a little more debug code when a connection can not
> be opened
> for any reason.
>
> >From the command line run build -debug and will enable debugging. Not
> sure if the
> current shell script will allow this, the bat file works.
>
> When debugging is enabled, you should see something like this. It will
> now display a
> stack trace if there are any connection problems. Post what you get and
> maybe I
> will have an idea what is going on.
>
> [DEBUG] Attempt to open a new connection to localhost:16000
> [DEBUG] Connection refused. Server not running?
> [DEBUG] Attempt to open a new connection to localhost:16000
> [DEBUG] Connection refused. Server not running?
> [DEBUG] Attempt to open a new connection to localhost:16000
> [DEBUG] Connection refused. Server not running?
> [DEBUG] Attempt to open a new connection to localhost:16000
> [DEBUG] Connected. Listing Published Altrmi Objects At Server...
> [DEBUG] [0]:InstrumentManagerClient
> [DEBUG] update client(vidcap-server) state new=66, old=-1
> [DEBUG] update instrumentable(component-manager) state new=0, old=-1
> [DEBUG] update instrumentable(instrument-manager) state new=15, old=-1
> [DEBUG] update instrument(instrument-manager.active-thread-count) state
> new=3, old=-1
> [DEBUG] update instrument(instrument-manager.free-memory) state new=3,
> old=-1
>
> Cheers,
> Leif
>
> Adam Rossi wrote:
>
> >After experimenting with various JDK's, I have found that the
> >instrumentation client does not seem to be compatible with the Sun 1.4*
> >JDK's. My experience on a Dell laptop running RedHat 7.3 is as follows:
> >
> >Sun 1.4.0_01 - Does not work
> >Sun 1.4.1_01 - Does not work
> >Blackdown-1.4.1-beta - Works! but only on the first try...
> >
> >With the Sun JDK's, I try to connect to the default port, the
> >instrumentation client connection tab reads "Not Connected", and never
> >updates. However, the connection does seem to be made, as killing the
> >app server causes a crash with a stack trace in the instrumentation
> >client. Similarly, pressing the garbage collection button does seem to
> >cause activity in the JVM.
> >
> >The blackdown JDK works like a charm the first time I use the
> >instrumentation client after booting up. I get the connection, can run
> >the cool graphs, etc. However, if i exit the client and then try to
> >reconnect, I get the "Not Connected" behavior and nothing happens.
> >
> >Are there any workarounds for the Sun JDK? Is this a known issue with
> >the instrumentation client, or with AltRMI?
> >
> >Thank you for your help.
> >
> >Regards,
> >
> >Adam
> >
> >
> >
>
>
>
> --
> To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
>
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
