Hi, all!
2 issues, 2 answers...
1) CAJ and JCA do not read environment variables
When CAJ was written reading env. variables was obsolete in Java (1.4). Now is back.
I got a request from SLAC to implement reading env. variables for CAJ and also for JCA.
It can be enabled with a special switch (for backward compatibility). Default is not to use env. variables.
If you all agree, I can change the default.
2) CAJ is broadcasting to 255.255.255.255.
Prior Java 1.6 it was not possible to introspect all network interfaces. So I was forced to use 255.255.255.255 as auto address.
Still I want CAJ to run on older Java version than 1.6. (Anyway, what do you use?)
What to do (options)?
1) detect java version and if 1.6 use introspection to get broadcast address of each network interfaces (might not be best solution since behavior is not the same)
2) I got one proposal from APS to use special env. variable that determines netmask; this would allow me to change 255.255.255.255 to e.g. 192.168.0.255 (but still only one network IF!)
3) ... any suggestion from you :)
I guess I should go 1) and for older versions non-auto address list should be used.
Cheers,
Matej
- Replies:
- RE: CAJ or PV gateway problem? Chu, Paul
- Re: CAJ or PV gateway problem? J. Lewis Muir
- References:
- RE: CAJ or PV gateway problem? Mark Rivers
- Navigate by Date:
- Prev:
RE: Revision tracking on vendor supplied updates? nick.rees
- Next:
ca_pend_event fails to return Chris Slominski
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: CAJ or PV gateway problem? Mark Rivers
- Next:
RE: CAJ or PV gateway problem? Chu, Paul
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|