[AG-TECH] beacon crashes all the time
Ivan R. Judson
judson at mcs.anl.gov
Thu Apr 3 07:49:52 CST 2003
I don't think you've lost your mind. But that probably doesn't have to do
with the beacon :-).
I do think we need to figure out a more scalable solution for the beacon (if
only at the UI level, but perhaps deeper than that).
Is there anyone from the beacon group on ag-tech that can answer this?
--Ivan
> -----Original Message-----
> From: owner-ag-tech at mcs.anl.gov
> [mailto:owner-ag-tech at mcs.anl.gov] On Behalf Of Bob Riddle
> Sent: Wednesday, April 02, 2003 9:56 PM
> To: ag-tech at mcs.anl.gov
> Subject: [AG-TECH] beacon crashes all the time
>
>
> I think there are too many beacons running for me to get the beacon
> client running on my linux box. I always see the following after I
> start it up:
>
> Beacon is running with :
> localhost = vrvs-ag.internet2.edu
> group = 233.2.171.1
> port = 56464
> ttl = 127
> user = beacon
> beacon server = beaconserver.accessgrid.org:9997
>
> java.lang.ArrayIndexOutOfBoundsException: 8192
> at Report.createReportBuffer(Report.java:253)
> at Report.run(Report.java:60)
>
>
> this seems similar to the problem reported in:
> http://www-unix.mcs.anl.gov/web-mail-archive/lists/ag-tech/200
> 0/05/msg00002.html
>
> I tried to change the "final static int maxReportPacketSize =
> 8192; //
> approximately enough for 80 beacons" in the Beacon.java file
> to 16384 -
> but I still get the same message. For my final experiment, I strated
> the beacon using the following shell script from nlanr:
>
> #!/bin/sh
> #
> # Multicast Beacon startup script for non-AG beacons
> #
> multicast_group=233.4.200.18
> multicast_port=10100
> beacon_server=dast.nlanr.net
> server_port=9999
> time_to_live=127
> user_name=beacon
>
> # this version runs under Java1.1 and Java1.2
> # compile the program using a stable java implementation on
> your platform cd /usr/local/ag/apps/beacon_v0.63/beacon
> /usr/local/ag/jre1.2.2/bin/java Beacon \
> -group $multicast_group \
> -port $multicast_port \
> -server $beacon_server \
> -serverport $server_port \
> -ttl $time_to_live \
> -name $user_name
>
>
> it ran forever ... which makes me think I need to find some
> way to make
> the 8192 value in Beacon.java larger ... so how come when I
> change it to
> 16384 in Beacon.java it still reports 8192 in the error message? Is
> there any hope that I can fix this (without convincing my friends to
> quite running their beacons long enough for me to get mine
> running ...
> of course one of them will then be punished ...)
>
> Have I lost my mind?
>
>
>
> --
> Bob Riddle (bdr at internet2.edu) Technologist,Internet2
> 3025 Boardwalk, Suite 100 Ann Arbor, Michigan 48108
> Business Phone: 734.913.4257 Fax Number: 734.913.4255
>
> "Opportunity is missed by most people because it is dressed
> in overalls
> and looks like work" Thomas Edison
>
More information about the ag-tech
mailing list