<< Back to previous view

[SAILFIN-2006] [online docs] Document reuseClientFEConnection property for CLB Created: 30/Sep/09  Updated: 13/Oct/09

Status: Open
Project: sailfin
Component/s: doc
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: kshitiz_saxena Assignee: chinmayee_srivathsa
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 2,006
Tags:
Participants: chinmayee_srivathsa, kshitiz_saxena and prasads

 Description   

This issue is related to issue 1934. A new property "reuseClientFEConnection" is
added for CLB. This need to be documented.



 Comments   
Comment by chinmayee_srivathsa [ 06/Oct/09 12:23 AM ]

To be fixed in the HA Admin guide

Comment by prasads [ 13/Oct/09 03:34 AM ]

Temporarily marking these issues as P4, for the Sailfin 2.0 release. The
priority will be restored for the next release.





[SAILFIN-1967] [RN] NFS Port 2049 should not be used as heartbeat port - failover fails Created: 08/Sep/09  Updated: 13/Oct/09

Status: Open
Project: sailfin
Component/s: doc
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: jimdumont Assignee: Joe Fialli
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,967
Status Whiteboard:

RN

Tags:
Participants: chinmayee_srivathsa, jimdumont, Joe Fialli, prasads and shreedhar_ganapathy

 Description   

When testing new MMAS and new LOTC together, we found that MMAS is using nfs
port (2049) as its heartbeat port in the cluster, and this prevents the
controllers failover from a failure one to another.

----------------------------

When testing the following combination of applications, the failover
functionality of the controllers does not working properly. Failure of the
active SC could result a complete cluster reboot.

LOTC R3A02, MMAS R12A03

DESCRIPTION:

When the failover is taking place, on stand by SC, we can see this error in
/var/log/messages file:
Sep 4 11:31:54 SC_2_2 logger: LOTC alarm cache lost (supposing restart).
Sep 4 11:31:54 SC_2_2 confd[11764]: - Starting ConfD vsn: 2.8
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file confd_cfg.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file confd.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file config.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file netconf.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file netconf_notification.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file netconf_actions.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file netconf_transactions.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file netconf_partial_lock.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file netconf_forward.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file tailf_netconf.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file /home/tspsaf/etc/confd.conf
Sep 4 11:31:54 SC_2_2 confd[11764]: - Consulting daemon configuration file
/home/tspsaf/etc/confd.conf
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/SAF_OAM_x86_64-CXP9013625_3-P2D97_saf_fm_main.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/JAVA_CAF_x86_64-CXP9013050_2-R7B01_JavaCaf_Classes.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/CONFIGPKG-CXP9013822_1-R12A03_MMAS_Model_PM_Classes.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/CONFIGPKG-CXP9013822_1-
R12A03_MMAS_Model_MMAS_Classes.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/CONFIGPKG-CXP9013822_1-
R12A03_MMAS_Model_Licensing_Classes.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/SAF_SWM_x86_64-CXP9013626_3-P2B25_swm.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/SAF_OAM_x86_64-CXP9013625_3-P2D97_saf_top_main.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/SAF_OAM_x86_64-CXP9013625_3-P2D97_aaa.fxs
Sep 4 11:31:54 SC_2_2 confd[11764]: - Loading file
/home/tspsaf/var/lib/cm/SAF_OAM_x86_64-CXP9013625_3-P2D97_netconf_rpc.cnc
Sep 4 11:31:54 SC_2_2 confd[11764]: - CDB load: processing file:
/opt/saf_oam/cm/confd-cdb/aaa_init.xml
Sep 4 11:31:54 SC_2_2 confd[11764]: - CDB: Operational DB re-initialized
Sep 4 11:31:54 SC_2_2 confd[11764]: - Starting to listen for NETCONF SSH on
0.0.0.0:2022
Sep 4 11:31:54 SC_2_2 confd[11764]: - Starting to listen for NETCONF TCP on
192.168.0.249:2023
Sep 4 11:31:54 SC_2_2 confd[11764]: - Starting to listen for CLI SSH on
0.0.0.0:2024
Sep 4 11:31:54 SC_2_2 confd[11764]: - ConfD started
Sep 4 11:31:55 SC_2_2 kernel: TIPC: Lost link <1.1.2:bond0-1.1.1:bond0> on
network plane A
Sep 4 11:31:55 SC_2_2 kernel: TIPC: Lost contact with <1.1.1>
Sep 4 11:31:56 SC_2_2 fmexec: NO : snmpTargetAddress changed to
'134.138.126.54:5000'.
Sep 4 11:31:56 SC_2_2 fmexec: NO : Changed state to Active.
Sep 4 11:31:59 SC_2_2 kernel: drbd0: Secondary/Primary --> Secondary/Secondary
Sep 4 11:31:59 SC_2_2 kernel: drbd0: meta connection shut down by peer.
Sep 4 11:31:59 SC_2_2 kernel: drbd0: drbd0_asender [4718]: cstate Connected -->
NetworkFailure
Sep 4 11:31:59 SC_2_2 kernel: drbd0: asender terminated
Sep 4 11:31:59 SC_2_2 kernel: drbd0: sock was shut down by peer
Sep 4 11:31:59 SC_2_2 kernel: drbd0: drbd0_receiver [4717]: cstate
NetworkFailure --> BrokenPipe
Sep 4 11:31:59 SC_2_2 kernel: drbd0: short read expecting header on sock: r=0
Sep 4 11:31:59 SC_2_2 kernel: drbd0: worker terminated
Sep 4 11:31:59 SC_2_2 kernel: drbd0: drbd0_receiver [4717]: cstate BrokenPipe
--> Unconnected
Sep 4 11:31:59 SC_2_2 kernel: drbd0: Connection lost.
Sep 4 11:31:59 SC_2_2 kernel: drbd0: drbd0_receiver [4717]: cstate Unconnected
--> WFConnection
Sep 4 11:31:59 SC_2_2 failoverd: DRBD: Connected, Secondary/Primary, Consistent
-> WFConnection, Secondary/Unknown, Consistent
Sep 4 11:31:59 SC_2_2 failoverd: Switching Secondary -> Primary
Sep 4 11:31:59 SC_2_2 failoverd: Task started (/sbin/drbdadm primary drbd0)
Sep 4 11:31:59 SC_2_2 kernel: drbd0: Secondary/Unknown --> Primary/Unknown
Sep 4 11:31:59 SC_2_2 failoverd: Task completed (/sbin/drbdadm primary drbd0)
Sep 4 11:31:59 SC_2_2 failoverd: DRBD: WFConnection, Secondary/Unknown,
Consistent -> WFConnection, Primary/Unknown, Consistent
Sep 4 11:31:59 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:31:59 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:31:59 SC_2_2 kernel: kjournald starting. Commit interval 5 seconds
Sep 4 11:31:59 SC_2_2 kernel: EXT3 FS on drbd0, internal journal
Sep 4 11:31:59 SC_2_2 kernel: EXT3-fs: mounted filesystem with journal data
mode.
Sep 4 11:31:59 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:31:59 SC_2_2 kernel: Installing knfsd (copyright (C) 1996
okir@monad.swb.de).
Sep 4 11:31:59 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:31:59 SC_2_2 primary: Starting NFS server
Sep 4 11:31:59 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:31:59 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:31:59 SC_2_2 nfsd[12821]: nfssvc: Address already in use
Sep 4 11:31:59 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:31:59 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:31:59 SC_2_2 failoverd: Panic situation emerging (1/10)
Sep 4 11:32:00 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:00 SC_2_2 syslog-ng[4592]: Connection broken to
AF_INET(192.168.0.1:514), reopening in 10 seconds
Sep 4 11:32:00 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:00 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:00 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:00 SC_2_2 primary: Starting NFS server
Sep 4 11:32:00 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:00 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:00 SC_2_2 nfsd[12835]: nfssvc: Address already in use
Sep 4 11:32:00 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:00 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:00 SC_2_2 failoverd: Panic situation emerging (2/10)
Sep 4 11:32:01 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:01 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:01 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:01 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:01 SC_2_2 primary: Starting NFS server
Sep 4 11:32:01 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:01 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:01 SC_2_2 nfsd[12848]: nfssvc: Address already in use
Sep 4 11:32:01 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:01 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:01 SC_2_2 failoverd: Panic situation emerging (3/10)
Sep 4 11:32:02 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:02 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:02 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:02 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:02 SC_2_2 primary: Starting NFS server
Sep 4 11:32:02 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:02 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:02 SC_2_2 nfsd[12862]: nfssvc: Address already in use
Sep 4 11:32:02 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:02 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:02 SC_2_2 failoverd: Panic situation emerging (4/10)
Sep 4 11:32:02 SC_2_2 kernel: nfs: server 192.168.0.103 not responding, still
trying
Sep 4 11:32:03 SC_2_2 kernel: nfs: server 192.168.0.103 not responding, still
trying
Sep 4 11:32:03 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:03 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:03 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:03 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:03 SC_2_2 primary: Starting NFS server
Sep 4 11:32:03 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:03 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:03 SC_2_2 nfsd[12874]: nfssvc: Address already in use
Sep 4 11:32:03 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:03 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:03 SC_2_2 failoverd: Panic situation emerging (5/10)
Sep 4 11:32:04 SC_2_2 coordinatordwrapper: Dispatching callback
Sep 4 11:32:04 SC_2_2 coordinatordwrapper: I am in amfHealthcheckCallback for
safComp=CompT_MMAS_COORDINATOR,safSu=SuT_MMAS_COORDINATOR,safNode=SC_2_2!
Sep 4 11:32:04 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:04 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:04 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:04 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:04 SC_2_2 primary: Starting NFS server
Sep 4 11:32:04 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:04 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:04 SC_2_2 nfsd[12907]: nfssvc: Address already in use
Sep 4 11:32:04 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:04 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:04 SC_2_2 failoverd: Panic situation emerging (6/10)
Sep 4 11:32:04 SC_2_2 coordinatordwrapper_init: wrapper_health
Sep 4 11:32:04 SC_2_2 coordinatordwrapper: Health check OK
Sep 4 11:32:05 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:05 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:05 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:05 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:05 SC_2_2 primary: Starting NFS server
Sep 4 11:32:05 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:05 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:05 SC_2_2 nfsd[12929]: nfssvc: Address already in use
Sep 4 11:32:05 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:05 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:05 SC_2_2 failoverd: Panic situation emerging (7/10)
Sep 4 11:32:06 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:06 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:06 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:06 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:06 SC_2_2 primary: Starting NFS server
Sep 4 11:32:06 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:06 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:06 SC_2_2 nfsd[12941]: nfssvc: Address already in use
Sep 4 11:32:06 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:06 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:06 SC_2_2 failoverd: Panic situation emerging (8/10)
Sep 4 11:32:07 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:07 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:07 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:07 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:07 SC_2_2 primary: Starting NFS server
Sep 4 11:32:07 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:07 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:07 SC_2_2 nfsd[12953]: nfssvc: Address already in use
Sep 4 11:32:07 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:07 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:07 SC_2_2 failoverd: Panic situation emerging (9/10)
Sep 4 11:32:08 SC_2_2 failoverd: Task started (/etc/init.d/primary start)
Sep 4 11:32:08 SC_2_2 primary: Mounting DRBD filesystem
Sep 4 11:32:08 SC_2_2 primary: Mounting NFS server filesystem
Sep 4 11:32:08 SC_2_2 primary: Exporting NFS filesystem
Sep 4 11:32:08 SC_2_2 primary: Starting NFS server
Sep 4 11:32:08 SC_2_2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4
state recovery directory
Sep 4 11:32:08 SC_2_2 kernel: NFSD: starting 90-second grace period
Sep 4 11:32:08 SC_2_2 nfsd[12969]: nfssvc: Address already in use
Sep 4 11:32:08 SC_2_2 primary: Failed to start NFS daemon
Sep 4 11:32:08 SC_2_2 failoverd: Task terminated (/etc/init.d/primary start),
exit code 1
Sep 4 11:32:08 SC_2_2 failoverd: Panic situation emerging (10/10)
Sep 4 11:32:09 SC_2_2 failoverd: PANIC!
Sep 4 11:32:09 SC_2_2 failoverd: SYSTEM REBOOTING IN 5 SECONDS
Sep 4 11:32:10 SC_2_2 failoverd: SYSTEM REBOOTING IN 4 SECONDS
Sep 4 11:32:11 SC_2_2 failoverd: SYSTEM REBOOTING IN 3 SECONDS
Sep 4 11:32:12 SC_2_2 agentwrapper: Dispatching callback
Sep 4 11:32:12 SC_2_2 agentwrapper: I am in amfHealthcheckCallback for
safComp=CompT_MMAS_AGENT,safSu=SuT_MMAS_OAM_PAYLOAD,safNode=SC_2_2!
Sep 4 11:32:12 SC_2_2 agentwrapper_init: wrapper_health
Sep 4 11:32:12 SC_2_2 agentwrapper: Health check OK
Sep 4 11:32:12 SC_2_2 failoverd: SYSTEM REBOOTING IN 2 SECONDS
Sep 4 11:32:13 SC_2_2 rsyncdwrapper: Dispatching callback
Sep 4 11:32:13 SC_2_2 rsyncdwrapper: I am in amfHealthcheckCallback for
safComp=CompT_MMAS_RSYNCD,safSu=SuT_MMAS_RSYNCD,safNode=SC_2_2!
Sep 4 11:32:13 SC_2_2 rsyncdwrapper_init: wrapper_health
Sep 4 11:32:13 SC_2_2 rsyncdwrapper: Health check OK
Sep 4 11:32:13 SC_2_2 failoverd: SYSTEM REBOOTING IN 1 SECONDS
Sep 4 11:32:14 SC_2_2 failoverd: SYSTEM REBOOTING NOW
Sep 4 11:32:16 SC_2_2 kernel: md: stopping all md devices.

Then the whole cluster restarted.

When issuing netstat command, we know that it was MMAS who uses nfs ports
mistakenly.
SC_2_1:~ # netstat -tulp | grep nfs
udp 0 0 :nfs *:
12383/java.orig
udp 0 0 :nfs *:
10129/java.orig

SC_2_1:~ # ps -ef | grep java
mmas 1624 12383 21 10:53 ? 00:04:12
/opt/jdk1.6.0_12/jre/../bin/java.orig -Djava.net.preferIPv4Stack=true
Dcom.sun.aas.instanceRoot=/opt/sailfin-v2
b23/nodedata/nodeagents/SC_2_1/oam_instance_SC_2_1
-DHTTP_LISTENER_PORT=28080 -DHTTP_SSL_LISTENER_PORT=28181
-DIIOP_LISTENER_PORT=33700 -DIIOP_SSL_LISTENER_PORT=33821
-DIIOP_SSL_MUTUALAUTH_PORT=33920 -DINTERNAL_IP=192.168.0.1
-DJMS_PROVIDER_PORT=37676 -DJMX_SYSTEM_CONNECTOR_PORT=38686
-DLifecycleModuleService.submitType=sync -DNET_DEVICE=134.138.83.13
-DSIP_PORT=25060 -DSIP_SSL_PORT=25061 -DSIP_SS_PORT=25062
-Dcom.sun.aas.ClassPathPrefix=/opt/sailfin-v2-b23/lib/comms-appserv-rt.jar
-Dcom.sun.aas.ClassPathSuffix= -Dcom.sun.aas.ServerClassPath=
-Dcom.sun.aas.classloader.appserverChainJars.ee=
Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli
ee.jar,j2ee-svc.jar
Dcom.sun.aas.classloader.excludesList=admin-cli.jar,appserv-upgrade.jar,sun
appserv-ant.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
Dcom.sun.aas.classloader.optionalOverrideableChain=webservices
rt.jar,webservices-tools.jar
Dcom.sun.aas.classloader.serverClassPath.ee=/lib/hadbjdbc4.jar,/opt/sailfin-v2
b23/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,/lib/dbstate.jar,/lib/hadbm.jar,/lib/hadbmgt
.jar,/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar
Dcom.sun.aas.classloader.serverClassPath=/opt/sailfin-v2
b23/lib/install/applications/jmsra/imqjmsra.jar,/opt/sailfin-v2-
b23/imq/lib/jaxm-api.jar,/opt/sailfin-v2-b23/imq/lib/fscontext.jar,/opt/sailfin-
v2-b23/imq/lib/imqbroker.jar,/opt/sailfin-v2-
b23/imq/lib/imqjmx.jar,/opt/sailfin-v2-b23/lib/ant/lib/ant.jar,/opt/sailfin-v2-
b23/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv
ee.jar,jesmf-plugin.jar,/lib/dbstate.jar,/lib/hadbjdbc4.jar,jgroups-
all.jar,/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar
-
Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,/opt/jdk1.6.0_12/jre/../lib/
tools.jar,install/applications/jmsra/imqjmsra.jar,com-sun-commons-
launcher.jar,com-sun-commons-logging.jar,/opt/sailfin-v2-b23/imq/lib/jaxm-
api.jar,/opt/sailfin-v2-b23/imq/lib/fscontext.jar,/opt/sailfin-v2-
b23/imq/lib/imqbroker.jar,/opt/sailfin-v2-b23/imq/lib/imqjmx.jar,/opt/sailfin-
v2-b23/imq/lib/imqxm.jar,webservices-rt.jar,webservices-
tools.jar,mail.jar,appserv-jstl.jar,jmxremote_optional.jar,/opt/sailfin-v2-
b23/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,activation.jar,appserv-rt.jar,appserv-
admin.jar,appserv-cmp.jar,/opt/sailfin-v2-
b23/updatecenter/lib/updatecenter.jar,/opt/sailfin-v2-
b23/jbi/lib/jbi.jar,/opt/sailfin-v2-b23/imq/lib/imqjmx.jar,/opt/sailfin-v2-
b23/lib/ant/lib/ant.jar,dbschema.jar
-Dcom.sun.aas.configName=oam-config
-Dcom.sun.aas.configRoot=/opt/sailfin-v2-b23/config
Dcom.sun.aas.defaultLogFile=/opt/sailfin-v2
b23/nodedata/nodeagents/SC_2_1/oam_instance_SC_2_1/logs/server.log
-Dcom.sun.aas.domainName=domain1 -Dcom.sun.aas.installRoot=/opt/sailfin-v2-b23
-Dcom.sun.aas.instanceName=oam_instance_SC_2_1 -Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.promptForIdentity=true
-
Dcom.sun.appserv.pluggable.extensions.amx=org.jvnet.glassfish.comms.admin.manage
ment.extensions.SIPAMXSupport
-
Dcom.sun.appserv.pluggable.features=org.jvnet.glassfish.comms.server.pluggable.e
xtensions.sip.SipEEPluggableFeatureImpl
-
Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.c
onfig.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
-Dcom.sun.enterprise.server.logging.max_history_files=10
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.updatecenter.home=/opt/sailfin-v2-b23/updatecenter
-Ddomain.name=domain1 -Djava.endorsed.dirs=/opt/sailfin-v2-b23/lib/endorsed
-
Djava.ext.dirs=/opt/jdk1.6.0_12/jre/../lib/ext:/opt/jdk1.6.0_12/jre/../jre/lib/e
xt:/opt/sailfin-v2-
b23/nodedata/nodeagents/SC_2_1/oam_instance_SC_2_1/lib/ext:/opt/sailfin-v2-
b23/javadb/lib:/opt/sailfin-v2-b23/lib/jdbcdrivers
Djava.library.path=/opt/sailfin-v2-b23/lib:/opt/sailfin-v2
b23/lib:/opt/sailfin-v2-b23/lib
-Djava.security.auth.login.config=/opt/sailfin-v2-b23/nodedata/nod

mmas 1869 1624 0 10:53 ? 00:00:00 /bin/sh
/opt/sailfin-v2-b23/imq/bin/imqbrokerd -javahome /opt/jdk1.6.0_12
-Dimq.log.file.rolloverbytes=2000000
-Dimq.cluster.masterbroker=mq://SC_2_2:37676/
-Dimq.cluster.brokerlist=mq://SC_2_1:37676/,mq://SC_2_2:37676/
-Dimq.cluster.nowaitForMasterBroker=true -varhome
/opt/sailfin-v2-b23/nodedata/nodeagents/SC_2_1/oam_instance_SC_2_1/imq
-startRmiRegistry -rmiRegistryPort 37776 -Dimq.imqcmd.user=admin -passfile
/tmp/asmq4893742025607423753.tmp -save -name oamoaminstanceSC21 -port 37676
-bgnd -silent

mmas 1889 1869 0 10:53 ? 00:00:01 /opt/jdk1.6.0_12/bin/java.orig
-Djava.net.preferIPv4Stack=true -cp
/opt/sailfin-v2-b23/imq/bin/../lib/imqbroker.jar:/opt/sailfin-v2-
b23/imq/bin/../lib/imqutil.jar:/opt/sailfin-v2-
b23/imq/bin/../lib/jsse.jar:/opt/sailfin-v2-
b23/imq/bin/../lib/jnet.jar:/opt/sailfin-v2-
b23/imq/bin/../lib/jcert.jar:/usr/lib/audit/Audit.jar:/opt/sun/mfwk/share/lib/jd
mkrt.jar:/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar:/opt/SUNWhadb/4/lib/hadbjdb
c4.jar:/opt/SUNWjavadb/derby.jar:/usr/share/java/postgresql.jar:/opt/sailfin-v2-
b23/imq/bin/../lib/ext:/opt/sailfin-v2-b23/imq/bin/../lib/ext
-Xms192m -Xmx192m -Xss128k -XX:MaxGCPauseMillis=5000
-Dimq.home=/opt/sailfin-v2-b23/imq/bin/..
Dimq.varhome=/opt/sailfin-v2
b23/nodedata/nodeagents/SC_2_1/oam_instance_SC_2_1/imq
-Dimq.etchome=/opt/sailfin-v2-b23/imq/bin/../etc
-Dimq.libhome=/opt/sailfin-v2-b23/imq/bin/../lib
com.sun.messaging.jmq.jmsserver.Broker -javahome /opt/jdk1.6.0_12
-Dimq.log.file.rolloverbytes=2000000
-Dimq.cluster.masterbroker=mq://SC_2_2:37676/
-Dimq.cluster.brokerlist=mq://SC_2_1:37676/,mq://SC_2_2:37676/
-Dimq.cluster.nowaitForMasterBroker=true -varhome
/opt/sailfin-v2-b23/nodedata/nodeagents/SC_2_1/oam_instance_SC_2_1/imq
-startRmiRegistry -rmiRegistryPort 37776 -Dimq.imqcmd.user=admin -passfile
/tmp/asmq4893742025607423753.tmp -save -name oamoaminstanceSC21 -port 37676
-bgnd -silent

mmas 10129 1 11 10:50 ? 00:02:41
/opt/jdk1.6.0_12/jre/../bin/java.orig -Djava.net.preferIPv4Stack=true
-Dcom.sun.aas.instanceRoot=/cluster/home/mmas/nodes/DAS/domains/domain1
-DLifecycleModuleService.submitType=sync
-Dcom.sun.aas.ClassPathPrefix=/opt/sailfin-v2-b23/lib/comms-appserv-rt.jar
-Dcom.sun.aas.ClassPathSuffix= -Dcom.sun.aas.ServerClassPath=
-Dcom.sun.aas.classloader.appserverChainJars.ee=
Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli
ee.jar,j2ee-svc.jar
Dcom.sun.aas.classloader.excludesList=admin-cli.jar,appserv-upgrade.jar,sun
appserv-ant.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
Dcom.sun.aas.classloader.optionalOverrideableChain=webservices
rt.jar,webservices-tools.jar
Dcom.sun.aas.classloader.serverClassPath.ee=/lib/hadbjdbc4.jar,/opt/sailfin-v2
b23/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,/lib/dbstate.jar,/lib/hadbm.jar,/lib/hadbmgt
.jar,/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar
Dcom.sun.aas.classloader.serverClassPath=/opt/sailfin-v2
b23/lib/install/applications/jmsra/imqjmsra.jar,/opt/sailfin-v2-
b23/imq/lib/jaxm-api.jar,/opt/sailfin-v2-b23/imq/lib/fscontext.jar,/opt/sailfin-
v2-b23/imq/lib/imqbroker.jar,/opt/sailfin-v2-
b23/imq/lib/imqjmx.jar,/opt/sailfin-v2-b23/lib/ant/lib/ant.jar,/opt/sailfin-v2-
b23/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv
ee.jar,jesmf-plugin.jar,/lib/dbstate.jar,/lib/hadbjdbc4.jar,jgroups-
all.jar,/opt/sun/mfwk/share/lib/mfwk_instrum_tk.jar
-
Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,/opt/jdk1.6.0_12/jre/../lib/
tools.jar,install/applications/jmsra/imqjmsra.jar,com-sun-commons-
launcher.jar,com-sun-commons-logging.jar,/opt/sailfin-v2-b23/imq/lib/jaxm-
api.jar,/opt/sailfin-v2-b23/imq/lib/fscontext.jar,/opt/sailfin-v2-
b23/imq/lib/imqbroker.jar,/opt/sailfin-v2-b23/imq/lib/imqjmx.jar,/opt/sailfin-
v2-b23/imq/lib/imqxm.jar,webservices-rt.jar,webservices-
tools.jar,mail.jar,appserv-jstl.jar,jmxremote_optional.jar,/opt/sailfin-v2-
b23/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,activation.jar,appserv-rt.jar,appserv-
admin.jar,appserv-cmp.jar,/opt/sailfin-v2-
b23/updatecenter/lib/updatecenter.jar,/opt/sailfin-v2-
b23/jbi/lib/jbi.jar,/opt/sailfin-v2-b23/imq/lib/imqjmx.jar,/opt/sailfin-v2-
b23/lib/ant/lib/ant.jar,dbschema.jar
-Dcom.sun.aas.configName=server-config
-Dcom.sun.aas.configRoot=/opt/sailfin-v2-b23/config
-
Dcom.sun.aas.defaultLogFile=/cluster/home/mmas/nodes/DAS/domains/domain1/logs/se
rver.log
-Dcom.sun.aas.domainName=domain1 -Dcom.sun.aas.installRoot=/opt/sailfin-v2-b23
-Dcom.sun.aas.instanceName=server -Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.promptForIdentity=true
-
Dcom.sun.appserv.pluggable.extensions.amx=org.jvnet.glassfish.comms.admin.manage
ment.extensions.SIPAMXSupport
-
Dcom.sun.appserv.pluggable.features=org.jvnet.glassfish.comms.server.pluggable.e
xtensions.sip.SipEEPluggableFeatureImpl
-
Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.c
onfig.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.updatecenter.home=/opt/sailfin-v2-b23/updatecenter
-Ddomain.name=domain1 -Djava.endorsed.dirs=/opt/sailfin-v2-b23/lib/endorsed
-
Djava.ext.dirs=/opt/jdk1.6.0_12/jre/../lib/ext:/opt/jdk1.6.0_12/jre/../jre/lib/e
xt:/cluster/home/mmas/nodes/DAS/domains/domain1/lib/ext:/opt/sailfin-v2-
b23/javadb/lib:/opt/sailfin-v2-b23/lib/jdbcdrivers
Djava.library.path=/opt/sailfin-v2-b23/lib:/opt/sailfin-v2
b23/lib:/opt/sailfin-v2-b23/lib
-
Djava.security.auth.login.config=/cluster/home/mmas/nodes/DAS/domains/domain1/co
nfig/login.conf
-
Djava.security.policy=/cluster/home/mmas/nodes/DAS/domains/domain1/config/server
.policy
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-
Djavax.management.builder.initial=com.sun.enterprise.ee.admin.AppServerMBeanServ
erBuilder
-
Djavax.net.ssl.keyStore=/cluster/home/mmas/nodes/DAS/domains/domain1/config/keys
tore.jks
-Djavax.net.ssl.trustStore=/cluster/home/mmas/nodes/DAS/domains/domain1/c

root 12005 31121 0 11:13 pts/0 00:00:00 grep java
mmas 12383 1 1 10:50 ? 00:00:17
/opt/jdk1.6.0_12/jre/../bin/java.orig -Djava.net.preferIPv4Stack=true
-Dcom.sun.aas.instanceRoot=/opt/sailfin-v2-b23/nodedata/nodeagents/SC_2_1/agent
-Dcom.sun.aas.configRoot=/opt/sailfin-v2-b23/config
Dcom.sun.aas.defaultLogFile=/opt/sailfin-v2
b23/nodedata/nodeagents/SC_2_1/agent/logs/server.log
-Dcom.sun.aas.instanceName=SC_2_1 -Dcom.sun.aas.isNodeAgent=true
-Dcom.sun.aas.promptForIdentity=true
-
Dcom.sun.appserv.admin.pluggable.features=com.sun.enterprise.ee.admin.pluggable.
EEClientPluggableFeatureImpl
Dcom.sun.appserv.nss.db=/opt/sailfin-v2
b23/nodedata/nodeagents/SC_2_1/agent/config
-
Dcom.sun.appserv.pluggable.features=com.sun.enterprise.ee.server.pluggable.EEPlu
ggableFeatureImpl
-Djava.endorsed.dirs=/opt/sailfin-v2-b23/lib/endorsed
Djava.library.path=/opt/sailfin-v2-b23/lib:/opt/sailfin-v2
b23/lib:/opt/sailfin-v2-b23/lib
Djava.security.auth.login.config=/opt/sailfin-v2
b23/nodedata/nodeagents/SC_2_1/agent/config/login.conf
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Djmx.invoke.getters=true -XX:+UnlockDiagnosticVMOptions
-XX:LogFile=/opt/sailfin-v2-b23/nodedata/nodeagents/SC_2_1/agent/logs/jvm.log
-XX:+LogVMOutput -cp
/opt/sailfin-v2-b23/lib/comms-appserv-rt.jar:/opt/sailfin-v2-b23/lib/appserv-
launch.jar:/opt/sailfin-v2-b23/lib/appserv-se.jar:/opt/sailfin-v2-
b23/lib/appserv-admin.jar:/opt/sailfin-v2-b23/lib/javaee.jar:/opt/sailfin-v2-
b23/lib/appserv-rt.jar:/opt/sailfin-v2-b23/lib/appserv-ext.jar:/opt/sailfin-v2-
b23/lib/shoal-gms.jar:/opt/sailfin-v2-b23/lib/jxta.jar:/opt/sailfin-v2-
b23/lib/appserv-ee.jar
com.sun.enterprise.ee.nodeagent.NodeAgentMain start
startInstancesOverride=false syncInstances=true monitorInterval=5
restartInstances=true

MEASURES:

We found that in our domain.xml file, in cluster section, the 2049 port has been
assigned as the heartbeat-port of traffic cluster:

<cluster config-ref="traffic-config" heartbeat-address="228.8.22.9"
heartbeat-enabled="true" heartbeat-port="2049" name="traffic">
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_7"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_10"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_9"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_6"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_8"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_5"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_4"/>
<server-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="true" ref="traffic_instance_PL_2_3"/>
<resource-ref enabled="true" ref="jdbc/__CallFlowPool"/>
<resource-ref enabled="true" ref="jca/Licensing"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="__ejb_container_timer_app"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="__JWSappclients"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="MEjbApp"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="WSTXServices"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="JBIFramework"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="WSTCPConnectorLCModule"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="SipContainerLifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="cluster-traffic-CAF-lifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="cluster-traffic-MMAS-Logging-lifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="cluster-traffic-MMAS-Monitoring-lifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="cluster-traffic-MMAS-PM-lifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="cluster-traffic-MMAS-DNS-lifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="cluster-traffic-MMAS-Statistics-lifecycle"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="MMASLMF"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="InviteServlet-ear-1.0"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="OptionsServlet-ear-1.0"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="PmServlet-ear-1.0"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="PresenceServlet-ear-1.0"/>
<application-ref disable-timeout-in-minutes="30" enabled="true"
lb-enabled="false" ref="SimpleHTTPServlet-ear-1.0"/>
</cluster>

This might be the reason of the problem.

However, since this configuration is not set by anyone manually in MMAS teams.
Seems it was SGCS who decide to use this port when creating the cluster.
Therefore, a patch from SUN is needed for SGCS to avoid using this kind of ports
in the future.



 Comments   
Comment by prasads [ 10/Sep/09 09:23 AM ]

Re-assigning to Joe for further action

Comment by Joe Fialli [ 11/Sep/09 01:14 PM ]

Workaround:

If automated cluster creation configuration selects a heartbeat-port that
coonflicts with another services use of that port, a system administrator needs
to update the cluster heartbeat-port to a port that is not being used by the system.

***************

Analysis of reported issue:

Executive Summary:
The cluster heart beat port is a random number selected between 1026 to 45556.
(configuration generation code is below.) For "default-cluster",
the heartbeat port is a random number selected between 0 to 45556.
To minimize collisions with densely populated reserved ports, proposal is
to generate a port between 8193-45556. So collisions would still be possible
but not as likely as now.
Even if the configuration code was updated to check if the port was available
at the time the cluster is created, that does not mean that a
service/application to be started later would not need the port. Services using
a port that is inconflict may not be running when the cluster is created.
Thus, it really is not possible to eliminate all conflict even with techniques
that perform more enhanced port availability checks.

While the proposed change will not avoid all conflicts, it will decrease
collisions generated by selecting the
heartbeat port randomly over the densely pre-reserved ports occuring under 8192.

Relevant code from glassfish/admin-ee
com.sun.enterprise.ee.admin.configbeans.ClustersConfigBean.java

private static final long MAX_HB_PORT_RANGE = 45556;
private static final int DEFAULT_HB_PORT= 1025; // change to 8192

private void setHeartbeatAddressAndPort ( final Cluster cluster )
throws ConfigException {
String heartbeatAddress = DEFAULT_HB_ADDRESS;
while(addrAlreadyAssigned( heartbeatAddress )){ heartbeatAddress = getHeartbeatAddress(); }
cluster.setHeartbeatAddress( heartbeatAddress, true);
// for address we search thru other clusters to get a unique
// address. Since that is being done we dont try to get a
// unique port number given that each cluster will be in a unique
// heartbeat address.
int port = DEFAULT_HB_PORT;
while(port <= DEFAULT_HB_PORT){ port = getHeartbeatPort(); }

cluster.setHeartbeatPort(Integer.toString( port));
}

private int getHeartbeatPort () { return (new Long( Math.round( Math.random()*MAX_HB_PORT_RANGE))) .intValue(); }

relevant code from sailfin administration for default-cluster
File: sailfin/administration
org/jvnet/glassfish/comms/admin/mbeans/extensions/SipConfigMBean.java

method addDefaultCluster(ConfigContext)

cl.setHeartbeatPort(Integer.toString((new
Long(Math.round(Math.random()*45556))).intValue()));

Comment by Joe Fialli [ 16/Sep/09 10:32 AM ]

Downgraded to P4 since the following workaround can be released noted for
current release.

Workaround:

If automated cluster creation configuration selects a heartbeat-port that
coonflicts with another services use of that port, a system administrator needs
to update the cluster heartbeat-port to a port that is not being used by the system.

Will check in proposed change stated on Sept 11 comment for next release.

Comment by Joe Fialli [ 16/Sep/09 12:20 PM ]

This issue needs to be release noted for sailfin 2.0, glassfish v2.1.1.

Downgraded to P4 since the following workaround can be released noted for
current release.

Workaround:

If automated cluster creation configuration selects a heartbeat-port that
coonflicts with another services use of that port, a system administrator needs
to update the cluster heartbeat-port to a port that is not being used by the system.

After this issue has been release noted by doc, please reassign the issue back
to me so the proposed fix will be checked in.

Comment by shreedhar_ganapathy [ 16/Sep/09 12:23 PM ]

assigned to chinmayee for release note capture.

Comment by Joe Fialli [ 16/Sep/09 12:47 PM ]

This issue is being release noted and a fix will be checked into the
next version of platform released after sailfin 2.0/gf v2.1.1.

Comment by Joe Fialli [ 16/Sep/09 02:06 PM ]

Additional info to release note:

One could assume that the automated heartbeat-port selection is always invalid
and part of starting up the cluster is to set the heartbeat-port (using asadmin
CLI or admin GUI) to a port that is known to be okay to use on the system.

Here is how to do it for asadmin CLI for a cluster named
"application-create-cluster".

${SF_HOME}/bin/asadmin set application-created-cluster.heartbeat-port=48991

Comment by prasads [ 20/Sep/09 08:06 PM ]

Adding to a release note

Comment by prasads [ 13/Oct/09 03:34 AM ]

Temporarily marking these issues as P4, for the Sailfin 2.0 release. The
priority will be restored for the next release.

Comment by chinmayee_srivathsa [ 13/Oct/09 04:42 AM ]

Release Noted as follows:
Communications Server does not detect conflicts with the heartbeat port of a
cluster (Issue number 1967)
Description
When a cluster is created, Communications Server randomly assigns a heartbeat port
between 1026 to 45556. For default-cluster, which is the default cluster created
by a Communications Server installation, a random number selected between 0 to
45556. The cluster creation process does not accurately detect if the heartbeat
port is already being used by another service.

Solution
If automated cluster creation configuration selects a heartbeat port that is in
conflict with another service that is already using that port, update the
cluster heartbeat port to a port that is not being used by the system.
To change the heartbeat port of a cluster, use the following asadmin command:
asadmin set <cluster-name>.heartbeat-port=<newportnumber>

Comment by Joe Fialli [ 13/Oct/09 01:23 PM ]

Fix is to allocate cluster heartbeatport from a random number in unused IANA
port range of 34380-34961.
(Doc: http://www.iana.org/assignments/port-numbers.)

Just awaiting code review.





[SAILFIN-1961] [RN] Building process blocked while creating the domain Created: 02/Sep/09  Updated: 18/Oct/09

Status: Open
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: eerieelf Assignee: srinik
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Sun


Issuezilla Id: 1,961
Status Whiteboard:

RN

Tags:
Participants: chinmayee_srivathsa, eerieelf, prasads, srinik and srinik76

 Description   

Sailfin: v1 b60g (also found in v2)
JDK : 64-bit 1.6.0 update 16
OS : 64-bit GNU/Linux

The building process was blocked on the following screen.

(...Information omitted...)

create.domain:
[exec] Using port 4848 for Admin.
[exec] Using port 8080 for HTTP Instance.
[exec] Using port 7676 for JMS.
[exec] Using port 3700 for IIOP.
[exec] Using port 8181 for HTTP_SSL.
[exec] Using default port 3820 for IIOP_SSL.
[exec] Using default port 3920 for IIOP_MUTUALAUTH.
[exec] Using default port 8686 for JMX_ADMIN.
[exec] Domain being created with profile:developer, as specified by variable
AS_ADMIN_PROFILE in configuration file.
[exec] Using default port 5060 for SIP Instance.
[exec] Using default port 5061 for SIP_SSL.
[exec] ------ Using Profile [developer] to create the domain ------
[exec] XML processing for profile: Base document
[/mnt/sys/thor-02/huangyi7/sailfin/lib/install/templates/default-domain.xml.template].
Profile name [developer]. Processing property [domain.xml.style-sheets].

(...Blocked here. No more information...)

The thread dump at the blocking point is followed.

(...Begin of thread dump...)

[exec] 2009-09-02 09:00:08
[exec] Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.2-b01 mixed mode):

[exec] "Low Memory Detector" daemon prio=10 tid=0x00002aaaeee94000
nid=0x2d05 runnable [0x0000000000000000]
[exec] java.lang.Thread.State: RUNNABLE

[exec] "CompilerThread1" daemon prio=10 tid=0x00002aaaeee91000 nid=0x2d04
waiting on condition [0x0000000000000000]
[exec] java.lang.Thread.State: RUNNABLE

[exec] "CompilerThread0" daemon prio=10 tid=0x00002aaaeee8d000 nid=0x2d03
waiting on condition [0x0000000000000000]
[exec] java.lang.Thread.State: RUNNABLE

[exec] "Signal Dispatcher" daemon prio=10 tid=0x00002aaaeee8b800 nid=0x2d02
waiting on condition [0x0000000000000000]
[exec] java.lang.Thread.State: RUNNABLE

[exec] "Finalizer" daemon prio=10 tid=0x00002aaaeec8e800 nid=0x2d01 in
Object.wait() [0x000000004072f000]
[exec] java.lang.Thread.State: WAITING (on object monitor)
[exec] at java.lang.Object.wait(Native Method)
[exec] - waiting on <0x00002aaadacd11e0> (a
java.lang.ref.ReferenceQueue$Lock)
[exec] at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
[exec] - locked <0x00002aaadacd11e0> (a java.lang.ref.ReferenceQueue$Lock)
[exec] at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
[exec] at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

[exec] "Reference Handler" daemon prio=10 tid=0x00002aaaeec8c800 nid=0x2d00
in Object.wait() [0x000000004062e000]
[exec] java.lang.Thread.State: WAITING (on object monitor)
[exec] at java.lang.Object.wait(Native Method)
[exec] - waiting on <0x00002aaadacd1048> (a java.lang.ref.Reference$Lock)
[exec] at java.lang.Object.wait(Object.java:485)
[exec] at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
[exec] - locked <0x00002aaadacd1048> (a java.lang.ref.Reference$Lock)

[exec] "main" prio=10 tid=0x0000000040112000 nid=0x2cfc runnable
[0x000000004022a000]
[exec] java.lang.Thread.State: RUNNABLE
[exec] at java.io.UnixFileSystem.delete0(Native Method)
[exec] at java.io.UnixFileSystem.delete(UnixFileSystem.java:251)
[exec] at java.io.File.delete(File.java:904)
[exec] at
com.sun.enterprise.admin.servermgmt.pe.ProfileTransformer.transform(ProfileTransformer.java:116)
[exec] at
com.sun.enterprise.admin.servermgmt.pe.PEDomainsManager.invokeGenericXmlTemplateProcessing(PEDomainsManager.java:685)
[exec] at
com.sun.enterprise.admin.servermgmt.pe.PEDomainsManager.createDomainXml(PEDomainsManager.java:344)
[exec] at
com.sun.enterprise.admin.servermgmt.pe.PEDomainsManager.createDomain(PEDomainsManager.java:157)
[exec] at
com.sun.enterprise.ee.admin.servermgmt.EEDomainsManager.createDomain(EEDomainsManager.java:170)
[exec] - locked <0x00002aaadb1ddde0> (a
com.sun.enterprise.ee.admin.servermgmt.EEDomainsManager)
[exec] at
com.sun.enterprise.cli.commands.CreateDomainCommand.create(CreateDomainCommand.java:489)
[exec] at
org.jvnet.glassfish.comms.admin.cli.extensions.commands.CreateSIPDomainCommand.createTheDomain(CreateSIPDomainCommand.java:153)
[exec] at
org.jvnet.glassfish.comms.admin.cli.extensions.commands.CreateSIPDomainCommand.runCommand(CreateSIPDomainCommand.java:113)
[exec] at
com.sun.enterprise.cli.framework.CLIMain.invokeCommand(CLIMain.java:171)
[exec] at com.sun.enterprise.cli.framework.CLIMain.main(CLIMain.java:79)

[exec] "VM Thread" prio=10 tid=0x00002aaaeec86000 nid=0x2cff runnable

[exec] "GC task thread#0 (ParallelGC)" prio=10 tid=0x000000004011c800
nid=0x2cfd runnable

[exec] "GC task thread#1 (ParallelGC)" prio=10 tid=0x000000004011e800
nid=0x2cfe runnable

[exec] "VM Periodic Task Thread" prio=10 tid=0x00002aaaeee96800 nid=0x2d06
waiting on condition

[exec] JNI global references: 729

[exec] Heap
[exec] PSYoungGen total 17664K, used 12409K [0x00002aaadacd0000,
0x00002aaadc080000, 0x00002aaaee820000)
[exec] eden space 15168K, 81% used
[0x00002aaadacd0000,0x00002aaadb8ee5d8,0x00002aaadbba0000)
[exec] from space 2496K, 0% used
[0x00002aaadbe10000,0x00002aaadbe10000,0x00002aaadc080000)
[exec] to space 2496K, 0% used
[0x00002aaadbba0000,0x00002aaadbba0000,0x00002aaadbe10000)
[exec] PSOldGen total 40320K, used 0K [0x00002aaab3620000,
0x00002aaab5d80000, 0x00002aaadacd0000)
[exec] object space 40320K, 0% used
[0x00002aaab3620000,0x00002aaab3620000,0x00002aaab5d80000)
[exec] PSPermGen total 21248K, used 10535K [0x00002aaaae220000,
0x00002aaaaf6e0000, 0x00002aaab3620000)
[exec] object space 21248K, 49% used
[0x00002aaaae220000,0x00002aaaaec69fb8,0x00002aaaaf6e0000)

(...End of thread dump...)



 Comments   
Comment by srinik76 [ 09/Sep/09 11:47 PM ]

Deleing the intermediate files after closing the stream
Issue number: 1961
Obtained from:
Submitted by:
Reviewed by: Kedar

Tests Run: Sailfin Cluster QL

Checking in ProfileTransformer.java;
/cvs/glassfish/admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/pe/ProfileTransformer.java,v
<-- ProfileTransformer.java
new revision: 1.3.6.3; previous revision: 1.3.6.2
done

Assigning to docs team for release noting this.

Comment by srinik76 [ 09/Sep/09 11:50 PM ]

The release note should mention

There may be blocking of create domain when we try to create a domain on a nfs
mounted file system with the NFS server running on 64-bit GNU/Linux.

Comment by srinik76 [ 10/Sep/09 04:51 AM ]

Checked into the FCS Branch.

Checking in ProfileTransformer.java;
/cvs/glassfish/admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/pe/ProfileTransformer.java,v
<-- ProfileTransformer.java
new revision: 1.3.6.2.8.1; previous revision: 1.3.6.2
done
Tag: SGES211_FCS_BRANCH

Comment by prasads [ 20/Sep/09 08:03 PM ]

Marked for release note

Comment by prasads [ 13/Oct/09 03:34 AM ]

Temporarily marking these issues as P4, for the Sailfin 2.0 release. The
priority will be restored for the next release.

Comment by chinmayee_srivathsa [ 13/Oct/09 04:49 AM ]

Release Noted as follows:
Domain creation stops on NFS server running 64-bit Linux (Issue Number
1961)
Description
The asadmin create domain command may fail while attempting to create a domain
on a Network File System (NFS) mounted file system with the NFS server running
on 64-bit Linux.

Solution
No known solution.

Re-assigning to Srini for review and further action

Comment by prasads [ 18/Oct/09 08:00 PM ]

Moving this issue to the started state





[SAILFIN-1954] Possible deadlock if a converged application uses SAS object as synchronization lock. Created: 02/Sep/09  Updated: 27/Oct/09

Status: Open
Project: sailfin
Component/s: sip_container
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: sonymanuel Assignee: sankara
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Other


File Attachments: Text File instance101-jstack.out    
Issuezilla Id: 1,954
Tags:
Participants: chinmayee_srivathsa, sankara and sonymanuel

 Description   

The converged conference application having http and sip servlets uses SAS as a
lock to synchronize access between SIP and Http worker threads when updating
attribute values stored in the SAS object. We observed the following deadlock in
one of the instances.

Found one Java-level deadlock:
=============================
"httpSSLWorkerThread-38080-9":
waiting to lock monitor 0x00002aac37fc9470 (object 0x00002aac29e31780, a
java.lang.Class),
which is held by "SipContainer-serversWorkerThread-5060-7"
"SipContainer-serversWorkerThread-5060-7":
waiting to lock monitor 0x00002aac45aa4e78 (object 0x00002aaad00ecd48, a
java.lang.Object),
which is held by "httpSSLWorkerThread-38080-2"
"httpSSLWorkerThread-38080-2":
waiting to lock monitor 0x00002aac37fc89f0 (object 0x00002aaaf92bb670, a
org.jvnet.glassfish.comms.replication.sessmgmt.FullHASipApplicationSession),
which is held by "SipContainer-serversWorkerThread-5060-7"

Java stack information for the threads listed above:
===================================================
"httpSSLWorkerThread-38080-9":
at com.sun.asqe.systemtest.conference.util.Util.getAndSetAttribute(Util.java:62)

  • waiting to lock <0x00002aac29e31780> (a java.lang.Class for
    com.sun.asqe.systemtest.conference.util.Util)
    at
    com.sun.asqe.systemtest.conference.http.ConferenceHTTPServlet.processLinkSessions(ConferenceHTTPServlet.java:142)
    at
    com.sun.asqe.systemtest.conference.http.ConferenceHTTPServlet.processRequest(ConferenceHTTPServlet.java:40)
    at
    com.sun.asqe.systemtest.conference.http.ConferenceHTTPServlet.doPost(ConferenceHTTPServlet.java:262)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at
    org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
    at
    org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at
    com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
    at
    com.sun.enterprise.ee.web.sessmgmt.SessionLockingStandardPipeline.invoke(SessionLockingStandardPipeline.java:120)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at
    org.jvnet.glassfish.comms.clb.proxy.portunif.ClbProxyPipeline$PUTask.doTask(ClbProxyPipeline.java:532)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
    at
    com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
    "SipContainer-serversWorkerThread-5060-7":
    at
    com.ericsson.ssa.sip.SipApplicationSessionBase.getAttribute(SipApplicationSessionBase.java:185)
  • waiting to lock <0x00002aaad00ecd48> (a java.lang.Object)
    at com.sun.asqe.systemtest.conference.util.Util.getAndSetAttribute(Util.java:63)
  • locked <0x00002aaaf92bb670> (a
    org.jvnet.glassfish.comms.replication.sessmgmt.FullHASipApplicationSession)
  • locked <0x00002aac29e31780> (a java.lang.Class for
    com.sun.asqe.systemtest.conference.util.Util)
    at
    com.sun.asqe.systemtest.conference.sip.ConferenceSipServlet.doAck(ConferenceSipServlet.java:72)
    at javax.servlet.sip.SipServlet.doRequest(SipServlet.java:59)
    at javax.servlet.sip.SipServlet.service(SipServlet.java:46)
    at
    com.ericsson.ssa.container.sim.SipServletFacade.service(SipServletFacade.java:121)
    at com.ericsson.ssa.sip.INVITESession.dispatch(INVITESession.java:1365)
    at com.ericsson.ssa.sip.UA.dispatch(UA.java:657)
    at
    com.ericsson.ssa.container.sim.ApplicationDispatcher.dispatchViaStatelessProxy(ApplicationDispatcher.java:638)
    at
    com.ericsson.ssa.container.sim.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:178)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:53)
    at
    com.ericsson.ssa.container.sim.ApplicationDispatcher.next(ApplicationDispatcher.java:697)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at com.ericsson.ssa.sip.LocalRouteManager.next(LocalRouteManager.java:98)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at com.ericsson.ssa.sip.DialogManager.next(DialogManager.java:568)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at com.ericsson.ssa.sip.dns.ResolverManager.next(ResolverManager.java:169)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    com.ericsson.ssa.sip.persistence.ReplicationManager.next(ReplicationManager.java:102)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    com.ericsson.ssa.sip.transaction.TransactionManager.next(TransactionManager.java:283)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    org.jvnet.glassfish.comms.clb.core.sip.SipLoadBalancerManagerBackEnd.next(SipLoadBalancerManagerBackEnd.java:193)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    org.jvnet.glassfish.comms.clb.core.sip.SipLoadBalancerManager.next(SipLoadBalancerManager.java:157)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    com.ericsson.ssa.container.OutboundFlowManager.processOutboundRequest(OutboundFlowManager.java:183)
    at com.ericsson.ssa.container.OutboundFlowManager.next(OutboundFlowManager.java:98)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    com.ericsson.ssa.container.GrizzlyNetworkManager.next(GrizzlyNetworkManager.java:1331)
    at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)
    at
    com.ericsson.ssa.container.MessageProcessorFilter.processMessage(MessageProcessorFilter.java:416)
    at
    com.ericsson.ssa.container.MessageProcessorFilter.execute(MessageProcessorFilter.java:315)
    at
    com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:136)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
    at
    com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
    at com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
    at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
    "httpSSLWorkerThread-38080-2":
    at
    com.ericsson.ssa.sip.SipApplicationSessionBase.lockForeground(SipApplicationSessionBase.java:1222)
  • waiting to lock <0x00002aaaf92bb670> (a
    org.jvnet.glassfish.comms.replication.sessmgmt.FullHASipApplicationSession)
    at
    com.ericsson.ssa.sip.SipApplicationSessionBase.lockForegroundWithRetry(SipApplicationSessionBase.java:1176)
    at com.sun.appserv.ha.uow.ReplicationUnitOfWork.add(ReplicationUnitOfWork.java:123)
  • locked <0x00002aaad2803828> (a
    com.ericsson.ssa.sip.persistence.ReplicationUnitOfWork)
    at
    org.jvnet.glassfish.comms.replication.sessmgmt.HASipApplicationSession.addToUnitOfWork(HASipApplicationSession.java:676)
    at
    org.jvnet.glassfish.comms.replication.sessmgmt.HASipApplicationSession.setShouldBePersisted(HASipApplicationSession.java:576)
    at
    com.ericsson.ssa.sip.SipApplicationSessionImpl.addPFieldHttpProtocolSession(SipApplicationSessionImpl.java:767)
    at
    org.jvnet.glassfish.comms.replication.sessmgmt.HASipApplicationSession.addPFieldHttpProtocolSession(HASipApplicationSession.java:634)
    at
    com.ericsson.ssa.sip.SipApplicationSessionBase.addSession(SipApplicationSessionBase.java:719)
  • locked <0x00002aaad00ecd48> (a java.lang.Object)
    at
    com.ericsson.ssa.sip.ConvergedHttpSessionFacade.getApplicationSession(ConvergedHttpSessionFacade.java:198)
    at
    com.ericsson.ssa.config.ConvergedContextImpl.beginPipelineInvoke(ConvergedContextImpl.java:606)
    at
    com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:96)
    at
    com.sun.enterprise.ee.web.sessmgmt.SessionLockingStandardPipeline.invoke(SessionLockingStandardPipeline.java:120)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at
    com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at
    org.jvnet.glassfish.comms.clb.proxy.portunif.ClbProxyPipeline$PUTask.doTask(ClbProxyPipeline.java:532)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
    at
    com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)

Found 1 deadlock.



 Comments   
Comment by sonymanuel [ 02/Sep/09 04:56 AM ]

Created an attachment (id=1104)
jstack

Comment by sonymanuel [ 10/Sep/09 05:08 AM ]

Workaround suggested by Sankar/Bhavani.

Locking SAS may not be good idea as spec doesn't mention any session locking
semantics and it is not guaranteed to work. See the below snippet for more
information. Unfortunately there is no easy way to achieve the same, but how
this has to be achieved is out side the scope. A good container implementation
should support to achieve this functionality.
You can achieve this functionality by doing the following snippet of code

SAS Listener.sessionCreate() {

sas.setAttribute("lock", mySASLocak);
}

in your servlet:

synchronized(sas.getAttribute("lock")) {
sas.setAttribute(..., ...);
}

The test is running fine after following the suggested approach.

Comment by sankara [ 15/Oct/09 03:19 AM ]

Scheduling it for next release.

Comment by chinmayee_srivathsa [ 27/Oct/09 10:05 PM ]

This issue is documented in the SailFin 2.0 Release Notes as a known issue.





[SAILFIN-1906] Need new 2.0 help screens Created: 10/Aug/09  Updated: 10/Aug/09  Resolved: 10/Aug/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Task Priority: Major
Reporter: chinmayee_srivathsa Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 1,906
Tags:
Participants: chinmayee_srivathsa

 Description   

Need new help screens for 2.0



 Comments   
Comment by chinmayee_srivathsa [ 10/Aug/09 11:25 PM ]

adding prasad to CC list

Comment by chinmayee_srivathsa [ 10/Aug/09 11:41 PM ]

New 2.0 help screens checked in.

RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationgeneral.html,v
done
Checking in diameterserviceapplicationgeneral.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationgeneral.html,v
<-- diameterserviceapplicationgeneral.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationlist.html,v
done
Checking in diameterserviceapplicationlist.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationlist.html,v
<-- diameterserviceapplicationlist.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationnew.html,v
done
Checking in diameterserviceapplicationnew.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationnew.html,v
<-- diameterserviceapplicationnew.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationslist.html,v
done
Checking in diameterserviceapplicationslist.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationslist.html,v
<-- diameterserviceapplicationslist.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationsnew.html,v
done
Checking in diameterserviceapplicationsnew.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterserviceapplicationsnew.html,v
<-- diameterserviceapplicationsnew.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicegenral.html,v
done
Checking in diameterservicegenral.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicegenral.html,v
<-- diameterservicegenral.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicelistener.html,v
done
Checking in diameterservicelistener.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicelistener.html,v
<-- diameterservicelistener.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicepeer.html,v
done
Checking in diameterservicepeer.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicepeer.html,v
<-- diameterservicepeer.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicepeernew.html,v
done
Checking in diameterservicepeernew.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicepeernew.html,v
<-- diameterservicepeernew.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicepeers.html,v
done
Checking in diameterservicepeers.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/diameterservicepeers.html,v
<-- diameterservicepeers.html
initial revision: 1.1
done

Checking in dservice.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/dservice.html,v
<-- dservice.html
initial revision: 1.1
done

RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/opservice.html,v
done
Checking in opservice.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/opservice.html,v
<-- opservice.html
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/overloadprotectionservice.html,v
done
Checking in overloadprotectionservice.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/overloadprotectionservice.html,v
<-- overloadprotectionservice.html
initial revision: 1.1
done





[SAILFIN-1889] Need to update bundled HTML pages Created: 04/Aug/09  Updated: 04/Aug/09  Resolved: 04/Aug/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: chinmayee_srivathsa Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 1,889
Tags:
Participants: chinmayee_srivathsa

 Description   

Need to update bundled HTML pages in sailfin/docs directory.



 Comments   
Comment by chinmayee_srivathsa [ 04/Aug/09 11:16 PM ]

Fixed.
Checking in QuickStart.html;
/cvs/sailfin/docs/QuickStart.html,v <-- QuickStart.html
new revision: 1.5; previous revision: 1.4
done
Checking in about.html;
/cvs/sailfin/docs/about.html,v <-- about.html
new revision: 1.6; previous revision: 1.5
done
Checking in copyright.html;
/cvs/sailfin/docs/copyright.html,v <-- copyright.html
new revision: 1.7; previous revision: 1.6
done
Checking in features.html;
/cvs/sailfin/docs/features.html,v <-- features.html
new revision: 1.7.2.2; previous revision: 1.7.2.1
done
/cvs/sailfin/docs/index.html,v <-- index.html
new revision: 1.3; previous revision: 1.2
done





[SAILFIN-1887] [online docs] Document authPassthroughEnabled and proxyHandler for CLB Created: 03/Aug/09  Updated: 13/Oct/09

Status: Open
Project: sailfin
Component/s: doc
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: kshitiz_saxena Assignee: chinmayee_srivathsa
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,887
Tags: sf20-hcf-na
Participants: chinmayee_srivathsa, kshitiz_saxena and prasads

 Description   

Converged load balancer documentation in SailFin should include details of
authPassthroughEnabled and proxyHandler properties. It will be same as
documentation for them in GlassFish @
http://docs.sun.com/app/docs/doc/820-4341/gbwwx?a=view



 Comments   
Comment by prasads [ 03/Sep/09 01:40 AM ]

Making these bugs NA for HCF

Comment by chinmayee_srivathsa [ 03/Sep/09 02:08 AM ]

Needs to be fixed in the online docs.

Comment by prasads [ 13/Oct/09 03:34 AM ]

Temporarily marking these issues as P4, for the Sailfin 2.0 release. The
priority will be restored for the next release.





[SAILFIN-1854] [Rolling Upgrade] Descriptions missing for backup,restore,reconcile-session-store commands Created: 14/Jul/09  Updated: 18/Aug/09  Resolved: 18/Aug/09

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: varunrupela Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,854
Tags:
Participants: chinmayee_srivathsa, srinik76 and varunrupela

 Description   

Using "asadmin help backup-session-store" needs to provide description of the
command. Same fore restore-session-store and reconcile-session-store.



 Comments   
Comment by srinik76 [ 20/Jul/09 11:47 PM ]

Reassigning to docs team

Comment by chinmayee_srivathsa [ 18/Aug/09 05:23 AM ]

New man pages checked in.

RCS file: /cvs/sailfin/administration/src/main/sman/man1/backup-session-store.1,v
done
Checking in backup-session-store.1;
/cvs/sailfin/administration/src/main/sman/man1/backup-session-store.1,v <--
backup-session-store.1
initial revision: 1.1
done
RCS file: /cvs/sailfin/administration/src/main/sman/man1/reconcile-session-store.1,v
done
Checking in reconcile-session-store.1;
/cvs/sailfin/administration/src/main/sman/man1/reconcile-session-store.1,v <--
reconcile-session-store.1
initial revision: 1.1
done
RCS file: /cvs/sailfin/administration/src/main/sman/man1/restore-session-store.1,v
done
Checking in restore-session-store.1;
/cvs/sailfin/administration/src/main/sman/man1/restore-session-store.1,v <--
restore-session-store.1
initial revision: 1.1
done

RCS file: /cvs/sailfin/administration/src/main/sman/cat1/backup-session-store.1,v
done
Checking in backup-session-store.1;
/cvs/sailfin/administration/src/main/sman/cat1/backup-session-store.1,v <--
backup-session-store.1
initial revision: 1.1
done
RCS file: /cvs/sailfin/administration/src/main/sman/cat1/reconcile-session-store.1,v
done
Checking in reconcile-session-store.1;
/cvs/sailfin/administration/src/main/sman/cat1/reconcile-session-store.1,v <--
reconcile-session-store.1
initial revision: 1.1
done
RCS file: /cvs/sailfin/administration/src/main/sman/cat1/restore-session-store.1,v
done
Checking in restore-session-store.1;
/cvs/sailfin/administration/src/main/sman/cat1/restore-session-store.1,v <-- r
estore-session-store.1
initial revision: 1.1
done





[SAILFIN-1748] Man page change for the addition of new attributes for sip-listener and http-listener. Created: 29/Apr/09  Updated: 18/Aug/09  Resolved: 18/Aug/09

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: swethadn Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 1,748
Tags:
Participants: chinmayee_srivathsa and swethadn

 Description   

1] create-sip-listener command in CLI , three new attributes "type",
"external-sip-address" and "external-sip-port" are added.
type
This can take values of "internal", "external" or "default".
An "internal" listener denotes that it will be used strictly
for the purpose of proxying by the clb.An "external" listener
will be used only by UAs and not by the clb.A "default" type
can be used by UAs as well as clb, and is the default type
for a listener.
external-sip-address
This is an optional attribute. It is effective only when the
attribute "external" is set to true. This should be the
address of the client facing network entity (e.g the load
balancer).
external-sip-port
This is an optional attribute. It is effective only when the
attribute "external" is set to true. This should be the port
of the client facing network entity ( e.g the load balancer).

2]create-http-listener one new attribute "type" is added .
type
This can take values of "internal", "external" or "default".
An "internal" listener denotes that it will be used strictly
for the purpose of proxying by the clb.An "external" listener
will be used only by UAs and not by the clb.A "default" type
can be used by UAs as well as clb, and is the default type
for a listener.

This new attribute for http-listener is added only for sailfin and not present
on pure-glassfish.



 Comments   
Comment by chinmayee_srivathsa [ 18/Aug/09 05:25 AM ]

Checked in the changes:
Checking in create-sip-listener.1;
/cvs/sailfin/administration/src/main/sman/man1/create-sip-listener.1,v <--
create-sip-listener.1
new revision: 1.7; previous revision: 1.6
done
RCS file: /cvs/sailfin/administration/src/main/sman/man1/create-http-listener.1,v
done
Checking in create-http-listener.1;
/cvs/sailfin/administration/src/main/sman/man1/create-http-listener.1,v <--
create-http-listener.1
initial revision: 1.1
doneChecking in create-sip-listener.1;
/cvs/sailfin/administration/src/main/sman/cat1/create-sip-listener.1,v <--
create-sip-listener.1
new revision: 1.5; previous revision: 1.4
done
RCS file: /cvs/sailfin/administration/src/main/sman/cat1/create-http-listener.1,v
done
Checking in create-http-listener.1;
/cvs/sailfin/administration/src/main/sman/cat1/create-http-listener.1,v <--
create-http-listener.1
initial revision: 1.1
done





[SAILFIN-1717] Help text for start-instance command is not in correct format Created: 13/Apr/09  Updated: 19/Oct/09  Resolved: 19/Oct/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: dpk Assignee: tcfujii
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,717
Tags:
Participants: chinmayee_srivathsa, dpk, prasads, tcfujii and Yamini K B

 Description   

Sailfin-b09

Steps to reproduce:

  • asadmin start-instance --help

The above command returns the help text in this following format:

./asadmin start-instance --help
<!DOCTYPE REFENTRY PUBLIC "-//Sun Microsystems//DTD DocBook
V3.0-Based SolBook Subset V2.0//EN" [ <!-ArborText, Inc., 1988
1999, v.4002--> <!ENTITY metainfo SYSTEM "metainfo.sgm"> <!ENTITY
options-common SYSTEM "options-common.sgm"> <!ENTITY synopsis-
common SYSTEM "synopsis-common.sgm"> <!ENTITY % commonents SYSTEM
"smancommon.ent"> %commonents; <!ENTITY % booktitles SYSTEM
"booktitles.ent"> %booktitles; <!ENTITY Dash "–"> ]> <?Pub
UDT _bookmark _target> <?Pub Inc> <refentry id="start-instance-
1"> <refmeta><refentrytitle>start-
instance</refentrytitle><manvolnum>1</manvolnum>&metainfo;
</refmeta> <refnamediv><indexterm><primary sortas="start-
instance">start-instance — starts a server
instance</primary></indexterm><indexterm><primary sortas="starts
a server instance"> starts a server instance — start-
instance</primary></indexterm><refname> start-
instance</refname><refpurpose>starts a server
instance</refpurpose> </refnamediv>
<refsynopsisdiv><title>&synp-tt;</title>
<cmdsynopsis><command>start-instance</command>&synopsis-common;
<arg
choice="plain"><replaceable>instance_name</replaceable></arg>
</cmdsynopsis></refsynopsisdiv> <refsect1><title>&desc-
tt;</title> <para>The <command>start-instance</command> command
starts an instance with the instance name you specify.</para>
</refsect1> <refsect1><title>OPTIONS</title> <variablelist
termlength="medium">&options-common; </variablelist></refsect1>
<refsect1><title>OPERANDS</title> <variablelist



 Comments   
Comment by Yamini K B [ 08/Oct/09 08:44 AM ]

Appears to be a GlassFish docs issue. Some of the man pages
(start/stop-instance, jbi commands) seem to be corrupted.

Comment by chinmayee_srivathsa [ 08/Oct/09 09:50 PM ]

I have no idea how this can happen. I handed off GlassFish man pages for SGES
2.1 and the JAR file containing the correct man pages is at:
http://swpubs.sfbay/writing/appserver/CommsAS911/glassfish-help-20081218.jar

Terena staged this JAR file for SGES 2.1 (see email below). The (SailFin or
GlassFish) build should be picking up this staged JAR file called
glassfish-help-20081218.jar.

Reassigning to CLI engineer.

Thanks, Chinmayee

-----------------------------------

Hi Chinmayee,

I've just staged and integrated this.

It will go in for the 12/20/2008 PST
nightly build.

Terena

Chinmayee Srivathsa wrote:
> Hi,
>
> Thanks, Harpreet.
>
> Terena, issue 6939 against SGES 2.1 man pages is approved and the new JAR
file is at
http://swpubs.sfbay/writing/appserver/CommsAS911/glassfish-help-20081218.jar.
> Please stage the new man pages JAR file and point the properties file to this JAR.
> Thank you,
> Chinmayee
>
> On 12/19/08 14:56, Harpreet Singh wrote:
>> Chinmayee - please go ahead and integrate this with Terena's help. I have
approved the issue.
>> - Harpreet
>>
>> Chinmayee Srivathsa wrote:
>>> Hi Harpreet,
>>>
>>> Yes, I really think this is very important. The user sees garbled output in
some man pages.
>>>
>>> The risk for fixing this bug is low because I will not be checking man pages
directly into the build.
>>> Terena needs to stage the new JAR file (on the external site) and she will
make only one change in a properties file in the build to point to the new JAR file.
>>> The JAR file with the fixes is at:
http://swpubs.sfbay/writing/appserver/CommsAS911/glassfish-help-20081218.jar
>>>
>>> Thanks,
>>> Chinmayee
>>>
>>> On 12/18/08 18:42, Harpreet Singh wrote:
>>>> Chinmayee
>>>> Is this absolutely required? The next build is RC2 for dec 22.
>>>> - Harpreet
>>>>
>>>> Chinmayee Srivathsa wrote:
>>>>> Hi,
>>>>>
>>>>> There is a new bug on one of the SGES 2.1 man pages.
>>>>>
>>>>> Is there another promoted build of SGES 2.1 planned? I would like to
update the man page JAR file.
>>>>>
>>>>> Thanks,
>>>>> Chinmayee
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: [Issue 6939] [docs] man-page for asadmin recover-transactions
prints garbage
>>>>> Date: Wed, 17 Dec 2008 16:46:15 +0000
>>>>> From: pauldavies@dev.java.net
>>>>> To: cs194067@dev.java.net
>>>>>
>>>>>
>>>>>
>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=6939
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>

Comment by prasads [ 18/Oct/09 08:00 PM ]

Moving this issue to the started state

Comment by tcfujii [ 19/Oct/09 07:54 AM ]

The fix is to integrate glassfish-help-20081218.jar.

Comment by tcfujii [ 19/Oct/09 07:57 AM ]

Updated appserv-docs/bootstrap/project.properties in the SAILFIN20_FCS_BRANCH
for glassfish-help-20081218.jar.





[SAILFIN-1571] [online docs] SGCS Port Allocation Created: 18/Jan/09  Updated: 03/Sep/09

Status: Open
Project: sailfin
Component/s: admin
Affects Version/s: 2.0
Fix Version/s: milestone 1

Type: Improvement Priority: Blocker
Reporter: eralsad Assignee: chinmayee_srivathsa
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,571
Tags: ocean
Participants: chinmayee_srivathsa, eralsad, sanandal, srinik76, swethadn and Yamini K B

 Description   

All ports that are used by SGCS shall be clearly documented. The documentation
shall contain information about which ports are used, how they are configured
and any mechanisms used if the configured port is unavailable (example:
scanning for the next port that is available).
It shall be possible to either configure the specific ports or the port ranges
used by SGCS.

This is important when applications start to co-locate other processes with
SGCS, since there may be port clashes. Also this information is needed if
multiple server instances (or JVM) should be located on the same host.



 Comments   
Comment by Yamini K B [ 19/Jan/09 01:51 AM ]

Port allocation and conflict checking happens during domain creation and is
taken care of automatically meaning, domain creation will fail if specified port
is in use. Similarly, during instance creation, only free ports are chosen.

However, if port was free during the creation but is in use while starting the
server, then there is a problem. start-domain incorrectly lists the SIP port(s)
as open and startup continues in spite of failure (issue #998)

For listeners created on the fly, server will log the failure (port in use)

I don't see the significance of port ranges since conflicts are checked
automatically, we don't have port ranges for HTTP, IIOP etc.

This is more of a documentation issue.

Comment by sanandal [ 05/Mar/09 02:59 AM ]

Added keyword ocean to track new RFEs

Comment by sanandal [ 05/Mar/09 03:00 AM ]

Added keyword ocean to track new RFEs

Comment by sanandal [ 05/Mar/09 03:00 AM ]

Added keyword ocean to track new RFEs

Comment by srinik76 [ 15/May/09 02:55 AM ]

The fix agreed is to clearly document all the ports used in SGCS. Will post the
details

Comment by swethadn [ 23/Jun/09 12:30 AM ]

The ports that are open for both glassfish and sailfin when DAS is started.

9701 – For TCP ports shoal specifies a port range internally from 9701 to 9999.
The first free port in this range will be used and it is not
configurable.
37776 - Enterprise server supplies an additional port to the broker , which is
used by it to start the RMI registry.
This is 100 + JMS port (7676) and it can be reconfigured.
3700 - In domain.xml the server.iiop-service.iiop-listener.orb-listener-1.port
is configured to 3700.
3820 - In domain.xml the server.iiop-service.iiop-listener.SSL.port is
configured to 3820
3920 - In domain.xml the server.iiop-service.iiop-listener.SSL_MUTUALAUTH.port
is configured to 3920
8686 - In domain.xml the server.admin-service.jmx-connector.system.port is
configured with port 8686.
8080 - In domain.xml the server.http-service.http-listener.http-listener-1.port
is configured to 8080.
8181 - In domain.xml the server.http-service.http-listener.http-listener-2.port
is confugured to the port 8181 with security-enabled.
5060 - The server.sip-service.sip-listener.sip-listener-1.port in the domain.xml
is configured with the port 5060 in both TCP and UDP.
5061 - The server.sip-service.sip-listener.sip-listener-2.port is configured to
the port 5061 with security enabled in domain.xml.
4848 - In domain.xml server.http-service.http-listener.admin-listener.port is
configured to 4848.
7676 - In domain.xml the server.jms-service.jms-host.default_JMS_host.port is
configured to the port 7676.

Comment by chinmayee_srivathsa [ 03/Sep/09 02:07 AM ]

Needs to be fixed in online documentation.





[SAILFIN-1562] Admingui OLH should include converged load balancer in contents pane Created: 12/Jan/09  Updated: 16/Aug/09  Resolved: 16/Aug/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: b28

Type: Bug Priority: Minor
Reporter: ogino Assignee: sumasri
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,562
Tags:
Participants: chinmayee_srivathsa, ogino and sumasri

 Description   

When I try to read about converged load balancer in admingui online help, I can
see pages like following.
Managing Converged Load Balancers
To Edit Converged Load Balancer Policy Details
Configuring Converged Load Balancer Targets

However, those above be reached through Contents tab on left side pane and only
HTTP Load Balancer contents are accessible. This incompleteness of help should
be fixed.



 Comments   
Comment by ogino [ 12/Jan/09 11:17 PM ]

Correction to above original report.

However, those above cannot be reached through Contents tab on left side pane
and only HTTP Load Balancer contents are accessible. This incompleteness of help
should be fixed.

Comment by chinmayee_srivathsa [ 17/Feb/09 08:34 PM ]

needs to be fixed

Comment by chinmayee_srivathsa [ 10/Aug/09 11:34 PM ]

The TOC of the Online help needs to be fixed. Re-assigning to Suma.

I have checked in the relevant XML files:
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/toc.xml,v
done
Checking in toc.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/toc.xml,v
<-- toc.xml
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/index.xml,v
done
Checking in index.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/index.xml,v
<-- index.xml
initial revision: 1.1
done

Comment by sumasri [ 10/Aug/09 11:53 PM ]

The TOC of the Online help is fixed.

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/overloadProtectionService.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/overloadProtectionService.jsf,v
<-- overloadProtectionService.jsf
new revision: 1.3; previous revision: 1.2
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf,v
<-- sipContainerAvailability.jsf
new revision: 1.5; previous revision: 1.4
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationGeneral.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationGeneral.jsf,v
<-- diameterServiceApplicationGeneral.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationList.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationList.jsf,v
<-- diameterServiceApplicationList.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationNew.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationNew.jsf,v
<-- diameterServiceApplicationNew.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationsList.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationsList.jsf,v
<-- diameterServiceApplicationsList.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationsNew.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceApplicationsNew.jsf,v
<-- diameterServiceApplicationsNew.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceGeneral.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceGeneral.jsf,v
<-- diameterServiceGeneral.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceListener.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServiceListener.jsf,v
<-- diameterServiceListener.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServicePeer.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServicePeer.jsf,v
<-- diameterServicePeer.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServicePeerNew.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServicePeerNew.jsf,v
<-- diameterServicePeerNew.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServicePeers.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/diameterService/diameterServicePeers.jsf,v
<-- diameterServicePeers.jsf
new revision: 1.2; previous revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/resources/Helplinks.properties;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/resources/Helplinks.properties,v
<-- Helplinks.properties
new revision: 1.9; previous revision: 1.8
done

Comment by sumasri [ 16/Aug/09 10:10 PM ]

Updated the milestone.





[SAILFIN-1530] [online docs] Design documentation: SAS key contstraints Created: 18/Dec/08  Updated: 03/Sep/09

Status: Open
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Task Priority: Major
Reporter: erikvandervelden Assignee: chinmayee_srivathsa
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,530
Tags:
Participants: chinmayee_srivathsa and erikvandervelden

 Description   

A long time ago the following page was written that describes some of the
limitations on accessing a specific SAS from an arbitrary instance in the cluster.

http://wiki.glassfish.java.net/Wiki.jsp?page=SakConstr

I've just updated it with some possible workarounds when you find yourself in a
situation where you need to target such a SAS.

I think it would be good if this kind of information makes it into the design
documentation.



 Comments   
Comment by erikvandervelden [ 18/Dec/08 10:02 AM ]


added CC

Comment by chinmayee_srivathsa [ 03/Sep/09 02:08 AM ]

Needs to be added to online documentation.





[SAILFIN-1516] Release Note of issues Created: 15/Dec/08  Updated: 12/Jan/09  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: rampsarathy Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


File Attachments: PDF File SJSASEERN.pdf    
Issuezilla Id: 1,516
Tags:
Participants: chinmayee_srivathsa and rampsarathy

 Description   

Please release note issue 1294 and 1169 , the notes that have to be put are
updated in the issue, this is a marker issue for this task



 Comments   
Comment by chinmayee_srivathsa [ 12/Jan/09 07:21 AM ]

Created an attachment (id=909)
release notes

Comment by chinmayee_srivathsa [ 12/Jan/09 07:22 AM ]

See page 15 in attached file for issue 1294.
See page 12 for 169.





[SAILFIN-1515] [RN] For issue 998: Server starts up fine even if SIP ports are not bound Created: 15/Dec/08  Updated: 12/Jan/09  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: Yamini K B Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


File Attachments: PDF File SJSASEERN.pdf    
Issuezilla Id: 1,515
Tags:
Participants: chinmayee_srivathsa and Yamini K B

 Description   

Please release note issue 998 as follows:

Server starts up fine even if SIP/SIPS ports are not bound. Please ensure that
ports are free before starting server instance(s). Also double check the logs to
ensure that there haven't been any errors/exceptions during the startup.



 Comments   
Comment by chinmayee_srivathsa [ 12/Jan/09 07:22 AM ]

Created an attachment (id=910)
release notes

Comment by chinmayee_srivathsa [ 12/Jan/09 07:23 AM ]

See page 11 in attached file.





[SAILFIN-1514] [RN] Release note for issue 1489 and 1494 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: ehsroha Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
depends on SAILFIN-1489 Node not fully compliant with RFC 326... Resolved
depends on SAILFIN-1494 Index out of range when sending SIP Resolved
Issuezilla Id: 1,514
Tags:
Participants: chinmayee_srivathsa, ehsroha and prasads

 Description   

Release note for issue 1489.

Workaround is to always use <> in Contact.



 Comments   
Comment by ehsroha [ 15/Dec/08 07:41 AM ]

Update dependency.

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by ehsroha [ 16/Dec/08 03:26 AM ]

Please use also this release note for issue 1494.

Comment by ehsroha [ 16/Dec/08 03:27 AM ]

Please use also this release note for issue 1494.

Comment by ehsroha [ 16/Dec/08 03:29 AM ]

Updated summary field

Comment by chinmayee_srivathsa [ 12/Jan/09 07:25 AM ]

Created an attachment (id=911)
release notes

Comment by chinmayee_srivathsa [ 12/Jan/09 07:25 AM ]

See page 15 in attached file.





[SAILFIN-1513] [RN] Release not for issue 1466 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: ehsroha Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
depends on SAILFIN-1466 bekey parameter not correctly escaped Resolved
Issuezilla Id: 1,513
Tags:
Participants: chinmayee_srivathsa, ehsroha and prasads

 Description   

Release not for issue 1466.

Current release will have the limitation as specified in issue 1466.



 Comments   
Comment by ehsroha [ 15/Dec/08 07:30 AM ]

Updated dependency.

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 12/Jan/09 07:26 AM ]

See page 12 in attached file

Comment by chinmayee_srivathsa [ 12/Jan/09 07:28 AM ]

Created an attachment (id=912)
release notes





[SAILFIN-1512] [RN] Release note for issue 1432 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: ehsroha Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
depends on SAILFIN-1432 UAS then proxy generates NOP Open
Issuezilla Id: 1,512
Tags:
Participants: chinmayee_srivathsa, ehsroha and prasads

 Description   

Release note for issue 1432.

This exception trace does not affect the functionality of the virtual proxy branch.



 Comments   
Comment by ehsroha [ 15/Dec/08 07:27 AM ]

Updated dependency.

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Dec/08 12:26 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 09/Jan/09 04:47 AM ]

Can you provide more details for release noting this issue?

"The application server first acts as a UAS and sends a 1xx response on an
incoming Invite from A. Then, it proxies the Invite to B, which responds with a
200 (OK). The 1xx creates an internal virtual branch while the 200 from B
creates a real branch. "

Is this accurate?
Thanks!

Comment by chinmayee_srivathsa [ 12/Jan/09 07:26 AM ]

See page 14 in attached file

Comment by chinmayee_srivathsa [ 12/Jan/09 07:28 AM ]

Created an attachment (id=913)
release notes





[SAILFIN-1511] [online docs] Design documenation: application handling of zombies Created: 15/Dec/08  Updated: 03/Sep/09

Status: Open
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Task Priority: Major
Reporter: erikvandervelden Assignee: chinmayee_srivathsa
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,511
Tags:
Participants: chinmayee_srivathsa, erikvandervelden and prasads

 Description   

Due to failures in the replication (e.g., lost replication messages) it can
happen that an SipApplicationSession that is already removed still survives.
Typically, this will result in a sessionExpires being called later on an
restored (older) version of the SipApplicationSession.
The application should be aware of this and if possible should handle a
sessionExpired on a SAS it already did invalidate gracefully. I.e., if it has
any way of checking that the SAS is already invalidated (e.g., by correlating
against a database), it should just let the SAS expire.

Jan, Larry, do you have anything to add to this?
I do not see any general way that application can detect whether this is a
duplicate expiration...



 Comments   
Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Dec/08 12:20 AM ]

Problem: Due to failures in the replication process, an SipApplicationSession
could survive even after it is removed. As a result, the sessionExpired method
could get called on a restored (older) version of the SipApplicationSession.

Workaround: The application needs to be verify that the SipApplicationSession
is invalidated (for example, by correlating against a database) and then let the
SipApplicationSession expire.

Please review if this explanation is sufficient and provide more information as
necessary.

Comment by chinmayee_srivathsa [ 17/Dec/08 12:24 AM ]

adding RN] to the description.

Comment by erikvandervelden [ 18/Dec/08 10:09 AM ]

I updated the summary, since it was not intended as release notes, but more as
design documentation.

After some sparring with Peter we came up with the following text proposal.
Feel free to modify it in any way you see fit.

Problem:
Due to the asynchronous nature of replication it can happen that some
replication messages get lost during an instance failure.

Possible effects:
If the lost replication message is a delete message, it can happen that an
artifact survives in the replica cache even after the active copy has been
invalidated.
A stale version of such artifacts might be activated later before the timeout is
invoked on it (since the timer semantics are preserved for replicas).
Such an artifact is called a zombie.

If the lost replication message is an update message, it can mean that in later
a stale replica is activated and used in subsequent communication in this session.

If the lost replication message is a create message, then the session can be
considered lost.

Possible solutions:
Staleness detection
If possible, the application should detect whether an artifact is stale or a
zombie when it is restored after a failure.
When the an object is restored after a failure the sessionDidActivate() callback
is invoked on the listener.
Because of this problem it is recommended to implement logic that discovers
stale sessions.
For example for some applications it may be possible to call the
lastAccessTime() method on the SipApplicationSession and/or SipSession to
determine whether the session is stale or not. If the session is stale it
should be explicitly invalidated.
For some applications this detection may not be possible without storing (or
removing) state information from a database when a session is invalidated.

Lifetime limitation

In general it is good practice to limit the life time of a SipApplicationSession
and a SipSession. Also in case that incoming messages get lost (e.g., an
incoming BYE gets lost), there is a chance that a SipSession and corresponding
SipApplicationSession will survive indefinitely. This also constitutes a memory
leak.
Therefore, the application should have an upper limit to the time an artifact
can live in the absence of external triggers.
This is specifically important if the application can do no staleness detection.

There are several ways to do this. The easiest way is to use the
SipApplicationSession's expiry time as defined in JSR289 section 6.1.2.1.

  • SAS timer based
    One pattern could be to set this to the maximum time you are prepared to wait
    for some external trigger and only in the presence of that trigger extend the
    lifetime.
    Then if the trigger does not arrive on time, let the SAS expire. This will
    invalidate the SAS and its children.
    In this pattern the SAS is never extended as part of the sessionExpired() callback.
    Even if the application has good reason to extend the SAS in the
    sessionExpired(), it should never do so indiscriminately, and thereby
    effectively create an endless SAS.
  • ST timer based
    Another possibility is that the application uses the Servlet Timer as a lifetime
    guard.
    E.g., a servlet timer can be started to guard the lifetime of a specific SipSession.

Summary
The main thing that we want to convey here is that an application must be very
careful to avoid endless sessions as they constitute memory leaks.
And if possible the application should do a staleness check on any restored
artifact in the sessionDidActivate callback.

Comment by chinmayee_srivathsa [ 03/Sep/09 02:07 AM ]

Needs to be fixed in online documentation.





[SAILFIN-1510] [RN] relnote issue 1351 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: erikvandervelden Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
depends on SAILFIN-1351 getLastAccessedTime() not implemented... Open
Issuezilla Id: 1,510
Tags:
Participants: chinmayee_srivathsa, erikvandervelden and prasads

 Description   

The following can be added to the release notes for issue 1351.

The application should NOT rely on the getLastAccessedTime() to return accurate
results. First of all the lastAccessedTime of a SipSession is not updated for
outgoing requests or incoming responses. Furthermore, the lastAccessedTime()
only gives expected results when invoked from within the application triggered
by the request that update of the lastAccessedTime (i.e., requesting the
lastAccessedTime of the any of the sibling sessions of of the
SipApplicationSession parent might not give the correct times).
Finally, in the calculation of the lastAccessedTime invalidated child sessions
of the SipApplicationSession are not taken into account.

As a workaround, applications that need to keep accurate track of the
lastAccessedTime should store it themselves into the SipApplicationSession, e.g.:
synchronized (sas) {
Long last = (Long) sas.getAttribute("myLastAccessedTime");
if (last == null) {last = 0};
// do something with the last one
// and...
// set the new one.
sas.setAttribute("myLastAccessedTime", System.currentTimeMillis());
}



 Comments   
Comment by erikvandervelden [ 15/Dec/08 07:11 AM ]

added dependancy

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Dec/08 12:08 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 17/Dec/08 12:21 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 12/Jan/09 07:29 AM ]

see pages 14 and 15 in the attached file

Comment by chinmayee_srivathsa [ 12/Jan/09 07:30 AM ]

Created an attachment (id=914)
release notes





[SAILFIN-1509] [RN] Release note for issue 1265 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: ehsroha Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf     PDF File SJSASEERN.pdf    
Issue Links:
Dependency
depends on SAILFIN-1265 Session still lives after container c... Open
Issuezilla Id: 1,509
Tags:
Participants: chinmayee_srivathsa, ehsroha and prasads

 Description   

Doc dependency issue 1265

This is a negative test case and the problem will not occur if the client always
sends the refresh SUBSCRIBE with a good margin before the subscription expires.



 Comments   
Comment by ehsroha [ 15/Dec/08 07:09 AM ]

Update dependency.

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Dec/08 12:05 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 12/Jan/09 07:29 AM ]

see page 14 in the attached file.

Comment by chinmayee_srivathsa [ 12/Jan/09 07:32 AM ]

Created an attachment (id=915)
release notes

Comment by chinmayee_srivathsa [ 12/Jan/09 08:10 AM ]

Created an attachment (id=916)
release notes





[SAILFIN-1508] [RN] relnotes issue 1180 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: erikvandervelden Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on SAILFIN-1180 SAS expiry timer is not relative to t... Open
Issuezilla Id: 1,508
Tags:
Participants: chinmayee_srivathsa, erikvandervelden and prasads

 Description   

The release notes could say something like this:

The extension of the lifetime of the SipApplicationSession works the same as it
did in JSR-116. This means that the application is in control over the duration
of the SipApplicationSession, subject to approval by the container. In the
setExpires the application indicates the time when the SipApplicationSession
should expire relative to the moment the setExpires is called. The container can
modify, reject or accept the duration indicated in the setExpires. If the
session is not invalidated, then x minutes after the last setExpires was invoked
the sessionExpired callback is performed. In this callback the application can
try to extend the duration of the SipApplicationSession by invoking a new
setExpires(), again subject to modification, rejection or acceptance by the
container.

This model is different from the HTTP expiration time logic. In HTTP the session
is automatically extended, outside of the control of the application, whenever a
new HTTP request is received in that HTTP session.
For this reason, converged applications that start out with the same expiration
time of the SipApplicationSession and on the HTTP session will notice that the
SAS might timeout before the HTTP session if new requests were received on the
HTTP session.

The best way to deal with the different expiration time handling of the
SipApplicationSession and the HTTPSession is to start with a large enough
SipApplicationSession expiration time, i.e., the total time that the application
session is expected to live (which might include several HTTP requests).
The SipApplicationSession lifetime might even be set to infinite, specifically
if there invalidateWhenReady semantics are used, in which case the
SipApplicationSession will be invalidated when the last protocol child session
becomes invaldated.
The initial expiration time for the SipApplicationSession can be configured in
the deployment descriptor.

If the maximum total duration can be estimated in advance, no further code is
needed, as it is then alright to invalidate both the SipApplicationSession and
the HTTPSession when the SipApplicationSession expires.

If maximum the duration can not be estimated in advance, then the
SipApplicationSession can be extended when it expires, as shown in the code
snippet below.
In the SipApplicationSessionListener implementation do something like this:

public void sessionExpired(SipApplicationSessionEvent sasEvent) {
// check if the SAS needs to be extended first, if so:
int granted = sasEvent.getApplicationSession().setExpires(2);
if (granted <= 0) { System.out.println("extension rejected"); } else if (granted < 2) { System.out.println("extension granted with lower value " + granted); } // else allowed
}



 Comments   
Comment by erikvandervelden [ 15/Dec/08 06:49 AM ]

added dependancy

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Dec/08 12:04 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 12/Jan/09 07:32 AM ]

see page 13 in the attached file





[SAILFIN-1507] [RN] Release note for issue 712 Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: ehsroha Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
depends on SAILFIN-712 Unable to handle CANCEL when 100 resp... Open
Issuezilla Id: 1,507
Tags:
Participants: chinmayee_srivathsa, ehsroha and prasads

 Description   

Doc dependency issue 712.

Workaround:
The application should send a provisional response (1xx) so the remote side is
able to CANCEL the INVITE request.



 Comments   
Comment by ehsroha [ 15/Dec/08 06:48 AM ]

Release not for issue 712.

Comment by prasads [ 15/Dec/08 08:45 AM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Dec/08 12:02 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 12/Jan/09 08:17 AM ]

See page 13 in attached file.

Comment by chinmayee_srivathsa [ 12/Jan/09 08:18 AM ]

Created an attachment (id=918)
release notes





[SAILFIN-1506] [RN] SEVERE message from CLB during dynamic reconfig after app deployment Created: 15/Dec/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: srinik76 Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
blocks SAILFIN-1161 SEVERE message from CLB during dynami... Open
Issuezilla Id: 1,506
Tags:
Participants: chinmayee_srivathsa and srinik76

 Description   

When CLB is configured and an application is redeployed, SEVERE messages will be
seen in Instance Logs. This message does not cause any harm to the functionality
and it can be ignored.



 Comments   
Comment by chinmayee_srivathsa [ 17/Dec/08 12:03 AM ]

Needs to be release noted

Comment by chinmayee_srivathsa [ 12/Jan/09 08:23 AM ]

Created an attachment (id=920)
RN

Comment by chinmayee_srivathsa [ 12/Jan/09 08:24 AM ]

see pages 12 and 13 in attachment





[SAILFIN-1454] Remove "repair-during-failure" attribute from <sip-container-availability> Created: 01/Dec/08  Updated: 04/Dec/08  Resolved: 04/Dec/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: jluehe Assignee: sumasri
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 1,454
Tags: sf10-fcs-approved
Participants: binod, chinmayee_srivathsa, irfanahmed, jluehe, prasads, sumasri and Yamini K B

 Description   

As can be seen from the updates to

https://sailfin.dev.java.net/issues/show_bug.cgi?id=1434

there has been some confusion on how to disable repair on an instance that is
being stopped.

The correct way of doing this is by adding

<property name="repair_during_failure_enabled" value="false"/>

under

<availability-service>

and not by setting the "repair-during-failure" of the
<sip-container-availability> element to false (default: true), which has no effect.

After consulting with Binod, it sounds like there is still an opportunity to
remove the "repair-during-failure" attribute from <sip-container-availability>
in time for FCS, to avoid any confusion.

This attribute will need to be removed from the relevant DTD(s).

It was also suggested that this issue be assigned to Yamini.



 Comments   
Comment by binod [ 01/Dec/08 08:15 PM ]

I think, we should deprecate the attribute (add a comment in the DTD). We can also remove from the GUI.
I dont think, we can change the DTD.

Comment by Yamini K B [ 02/Dec/08 08:10 PM ]

SAILFIN10_FCS_BRANCH:
Checking in common/src/main/config-api/build.properties;
/cvs/sailfin/common/src/main/config-api/build.properties,v <-- build.properties
new revision: 1.4.2.1; previous revision: 1.4
done
Checking in common/src/main/resources/rng/sip-container-availability.rng;
/cvs/sailfin/common/src/main/resources/rng/sip-container-availability.rng,v <--
sip-container-availability.rng
new revision: 1.1.4.1; previous revision: 1.1
done
Checking in administration/src/main/resources/dtds/sun-domain_1_4.dtd;
/cvs/sailfin/administration/src/main/resources/dtds/sun-domain_1_4.dtd,v <--
sun-domain_1_4.dtd
new revision: 1.3.2.1; previous revision: 1.3
done

TRUNK:

Checking in common/src/main/config-api/build.properties;
/cvs/sailfin/common/src/main/config-api/build.properties,v <-- build.properties
new revision: 1.5; previous revision: 1.4
done
Checking in common/src/main/resources/rng/sip-container-availability.rng;
/cvs/sailfin/common/src/main/resources/rng/sip-container-availability.rng,v <--
sip-container-availability.rng
new revision: 1.2; previous revision: 1.1
done
Checking in administration/src/main/resources/dtds/sun-domain_1_4.dtd;
/cvs/sailfin/administration/src/main/resources/dtds/sun-domain_1_4.dtd,v <--
sun-domain_1_4.dtd
new revision: 1.4; previous revision: 1.3
done

Re-assigning to Irfan to fix GUI screen.

Comment by irfanahmed [ 02/Dec/08 09:09 PM ]

Assigned to Suma.

The property needs to be removed from the Screen.

Comment by irfanahmed [ 03/Dec/08 09:50 PM ]

checked in the code fix to the tunk:
Issue number: 1454
Reviewed by: irfanahmed
Tests Run: SF QL
Summary: Remove "repair-during-failure" attribute from <sip-container-availability>
----------------------------------------------------------------------
Modified Files:
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf
.... removed repair-during-failover property from the screen.

src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/SipContainerHandler.java
.... updated code to remove the getting/setting of repair-during-failure
property for sip container availability.
----------------------------------------------------------------------
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf,v
<-- sipContainerAvailability.jsf
new revision: 1.4; previous revision: 1.3
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/SipContainerHandler.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/SipContainerHandler.java,v
<-- SipContainerHandler.java
new revision: 1.7; previous revision: 1.6
done

Comment by irfanahmed [ 03/Dec/08 09:55 PM ]

Fix checked in to the SIALFIN10_FCS_BRANCH:
Issue number: 1454
Reviewed by: irfanahmed
Tests Run: SF QL
Summary: Remove "repair-during-failure" attribute from <sip-container-availability>
----------------------------------------------------------------------
Modified Files:
Tag: SAILFIN10_FCS_BRANCH
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf
....removed propery repair-during-failover from the sip conatiner availability
screen.

src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/SipContainerHandler.java
.... removed the repair-during-failover settin/getting from the handlers.
----------------------------------------------------------------------
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/configuration/availability/sipContainerAvailability.jsf,v
<-- sipContainerAvailability.jsf
new revision: 1.3.2.1; previous revision: 1.3
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/SipContainerHandler.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/SipContainerHandler.java,v
<-- SipContainerHandler.java
new revision: 1.6.2.1; previous revision: 1.6
done

Comment by chinmayee_srivathsa [ 03/Dec/08 11:55 PM ]

Removed reference to this attribute from the Online help as well.

Checking in sipcontaineravailability.html;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/html/sipcontaineravailability.html,v
<-- sipcontaineravailability.html
new revision: 1.2.2.1; previous revision: 1.2
done

Comment by prasads [ 04/Dec/08 12:20 AM ]

Approving them for SF1.0 FCS





[SAILFIN-1406] CLI --help needs to pick up sailfin-specific deploy man page. Created: 12/Nov/08  Updated: 12/Nov/08  Resolved: 12/Nov/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: chinmayee_srivathsa Assignee: swethadn
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 1,406
Tags:
Participants: chinmayee_srivathsa and swethadn

 Description   

CLI --help needs to pick up sailfin-specific deploy man page.



 Comments   
Comment by chinmayee_srivathsa [ 12/Nov/08 11:09 PM ]

adding yamini and prasad to the cc list

Comment by swethadn [ 12/Nov/08 11:19 PM ]

Requires a change in build.xml to pick sailfin specific man pages.

Comment by swethadn [ 12/Nov/08 11:46 PM ]

//Requires a change in build.xml
Issue number: 1406
Obtained from:
Submitted by:
Reviewed by: Srini

Checking in build.xml;
/cvs/sailfin/administration/build.xml,v <-- build.xml
new revision: 1.46; previous revision: 1.45
done





[SAILFIN-1388] [RN] CLB Commands will make domain status to require restart even though it is not the case Created: 11/Nov/08  Updated: 12/Jan/09  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: srinik76 Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,388
Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, prasads and srinik76

 Description   

This is the docs tracker bug for Issue 333. This needs to be release noted.

Using clb commands will make the user misleading in the domain status. The
functionality is fine. The following needs to be documented.

'Using CLB Related commands will make the domain status to Requires Restart even
though it is not required'.



 Comments   
Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by chinmayee_srivathsa [ 05/Dec/08 12:57 AM ]

Release Notes bug

Comment by chinmayee_srivathsa [ 12/Jan/09 08:22 AM ]

See page 12 in attachment





[SAILFIN-1384] The links to docs in the Admin Console are outdated. Created: 10/Nov/08  Updated: 11/Nov/08  Resolved: 11/Nov/08

Status: Resolved
Project: sailfin
Component/s: admin_gui
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: chinmayee_srivathsa Assignee: irfanahmed
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 1,384
Tags:
Participants: chinmayee_srivathsa and irfanahmed

 Description   

The links to docs in the SGCS Admin Console are outdated (They still link to
Application Server 9.1 books).

Here are the correct links for SGCS 1.5 (some of these docs are not yet published -
but they will be published before the GA release in december)

SGCS 1.5 QuickStart guide: http://docs.sun.com/app/docs/doc/820-4280
Administration guide: http://docs.sun.com/app/docs/doc/820-4281
Developer's guide: http://docs.sun.com/app/docs/doc/820-4282
Application Deployment guide: http://docs.sun.com/app/docs/doc/820-4283
Deployment Planning guide: http://docs.sun.com/app/docs/doc/820-4288



 Comments   
Comment by irfanahmed [ 10/Nov/08 03:35 AM ]

started working on this

Comment by irfanahmed [ 11/Nov/08 04:00 AM ]

Following Fix has been checked in
Issue number: 1384
Reviewed by: irfanahmed
Tests Run : SF QL
Summary: The links to docs in the Admin Console are outdated.
----------------------------------------------------------------------
Added Files:
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/clusterCommonTask.jsf
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/commonTask.jsf
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/includes/sipCommonTaskDoc.inc
....The above three files are the commonTasks pages for developer profile and
cluster profile.
----------------------------------------------------------------------
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/clusterCommonTask.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/clusterCommonTask.jsf,v
<-- clusterCommonTask.jsf
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/commonTask.jsf,v
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/commonTask.jsf;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/commonTask.jsf,v
<-- commonTask.jsf
initial revision: 1.1
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/includes/sipCommonTaskDoc.inc,v
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/includes/sipCommonTaskDoc.inc;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/docroot/sip/includes/sipCommonTaskDoc.inc,v
<-- sipCommonTaskDoc.inc
initial revision: 1.1





[SAILFIN-1373] [online docs[ Incorrect /etc/hosts entry may result in issue 1330 Created: 05/Nov/08  Updated: 25/Nov/10  Resolved: 16/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: kshitiz_saxena Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on SAILFIN-1330 Log files littered with "No BERoute o... Resolved
Issuezilla Id: 1,373
Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, cs194067, kshitiz_saxena and prasads

 Description   

All instances in a cluster should have similar view for each other IP address.
For example: say there are two instances in cluster, say instance1 and instance2.
When instance1 lookup instance2's ip address, it gets address a.b.c.d. Similarly
when instance2 looks up its own ip address, it must get back same address, i.e.,
a.b.c.d. If that is not the case, then it may result in issue 1330. Please refer
to issue 1330 for more details.



 Comments   
Comment by kshitiz_saxena [ 05/Nov/08 10:58 PM ]

Assigning to doc team.

Comment by kshitiz_saxena [ 05/Nov/08 11:07 PM ]
      • Issue 1372 has been marked as a duplicate of this issue. ***
Comment by chinmayee_srivathsa [ 10/Nov/08 01:16 AM ]

Needs to be documented in the HA guide and the troubleshooting guide.

Does not affect bundled docs.

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by chinmayee_srivathsa [ 07/Jan/09 01:57 AM ]

Added to the HA Admin guide.

Comment by cs194067 [ 16/Jan/09 07:18 AM ]

Fixed in the HA guide.





[SAILFIN-1372] need to document network configuration issue from 1330 Created: 05/Nov/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: lwhite Assignee: chinmayee_srivathsa
Resolution: Duplicate Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,372
Tags:
Participants: chinmayee_srivathsa, kshitiz_saxena and lwhite

 Description   

The following information turned out to be key to resolving issue 1330
which involved seeing error messages that looked like this:
Failed to route incoming response:
org.jvnet.glassfish.comms.clb.core.sip.SipRoutingException: No BERoute on
response, shall never happen; drop the response

Machines in the cluster had multiple interfaces and were using /etc/hosts

There are constraints we need to document on how to do this to avoid this
problem - see below.

Contact Kshitiz for more details if needed.

Steve was able to get a clean run thanks to assist from Kshitiz.
We are resolving this issue as WORKSFORME.
It turned out there were inconsistencies among the /etc/hosts files
on the test machines. Here is Kshitiz note including explanation.

Some of this may be important to document for users.

Issue is with setup itself.

Below is /etc/hosts on machine gf-ha-dev-5.sfbay.sun.com
10.4.113.143 gf-ha-dev-5.sfbay.sun.com
10.5.221.52 gf-ha-dev-5.sfbay.sun.com gf-ha-dev-5

/etc/hosts on machine gf-ha-dev-4.sfbay.sun.com
10.4.113.142 gf-ha-dev-4.sfbay.sun.com
10.5.221.50 gf-ha-dev-4.sfbay.sun.com gf-ha-dev-4

However on machine gf-ha-dev-2.sfbay.sun.com /etc/hosts entry is
10.5.221.48 gf-ha-dev-2.sfbay.sun.com gf-ha-dev-2
10.4.113.140 gf-ha-dev-2.sfbay.sun.com

Please change the order of entry in /etc/hosts on machine
gf-ha-dev-5.sfbay.sun.com and gf-ha-dev-4.sfbay.sun.com similar to entry on
machine gf-ha-dev-2.sfbay.sun.com

The issue is due to below fact :
InetAddress lookup for gf-ha-dev-5.sfbay.sun.com on gf-ha-dev-2.sfbay.sun.com
will give result in 10.5.221.52. However InetAddress lookup for
gf-ha-dev-5.sfbay.sun.com on gf-ha-dev-5.sfbay.sun.com will give result in
10.4.113.143. This result in different id generated for same instance on
different instances, thus resulting in mismatch. This is root cause for issue 1330.



 Comments   
Comment by kshitiz_saxena [ 05/Nov/08 11:07 PM ]

Issue 1373 is filed for same issue. Closing this one a duplicate.

      • This issue has been marked as a duplicate of 1373 ***




[SAILFIN-1344] [onlinedocs] : OLP. Solaris. According to Sailfin CPU usage was more than 100% Created: 31/Oct/08  Updated: 12/Jan/09  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: easarina Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Solaris X86
Platform: All


File Attachments: PDF File SJSASEERN.pdf    
Issuezilla Id: 1,344
Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, easarina, erikvandervelden, prasads, rampsarathy and sanandal

 Description   

Solaris 10 x86 machines, b58, 4 inst in a cluster. One inst per the machine.
Each machine had 4 CPUs. I've created CPU overload protection setting:

<property name="CpuOverloadRegulation" value="true"/>
<property name="SampleRate" value="5"/>
<property name="olpInserted" value="true"/>
<property name="SrThreshold" value="10"/>
<property name="IrThreshold" value="10"/>
<property name="MmThreshold" value="100"/>

In the server.log files of the instances I saw such messages, for example:

[#|2008-10-31T15:37:29.782-0700|WARNING|sun-glassfish-comms-server1.0|javax.ente
rprise.system.container.sip|_ThreadID=21;_ThreadName=Thread-35;measured load: 23
5;_RequestID=4580925e-9acf-47b2-88d0-3da235f24d2a;|"ALARM RAISED: CPU load has e
xceeded the defined threshold: measured load: 235"|#]

It means that CPU load was more than 100%. I saw a lot of such values of CPU
loading, more than 100%.

I believe that it doesn't make sense and CPU loading has to be not more than 100%.

Also I want to mention that according to other measurements such as ps -ef
-pcpu , top, the CPU loading on this machine was about 30%.

So I believe that something wrong with values of CPU loading that were created
by OverloadProtectionMansager.class.



 Comments   
Comment by rampsarathy [ 31/Oct/08 08:29 PM ]

reassign

i will investigate this,platform mbeans are used on Solaris to retrieve the cpu
utilization, so

Comment by rampsarathy [ 31/Oct/08 08:30 PM ]

bringing to started

Comment by erikvandervelden [ 03/Nov/08 07:15 AM ]

The calculation is based on the MBeans in such a way:
long currentProcessCpuTime = _mxbean.getProcessCpuTime();
double busyPercent = (100 * (currentProcessCpuTime -
_lastProcessCpuTime))
/ (1000000 * (now - _lastTime));
// save for next access.
_lastTime = now;
_lastProcessCpuTime = currentProcessCpuTime;

I'm not sure how the platform MBeans deal with this, but I can imagine that in a
quad-core system, you can spend 4 periods the processCPUtime in one period of
real time.
Reaulting in values that are upto 'nr-of-cores' times too high

Comment by rampsarathy [ 10/Nov/08 12:10 AM ]

We have the option of finding out the number of available processors and finding
the per-core cpu usage . But this has a downside because it the
availableProcessors (Runtime) only returns the static value of number of cores
installed and not the number of cores that can be used by the vm, so this may
not work correctly if a user binds the jvm to one or more cores out of the N
available


Erik's update


I see we have several possibilities:

  • no change anything and document this. Make it the responsibility of the
    operator to set the thesholds correctly taking into account the multiple-cores
  • make the change that you suggest.
    Still document this and say that if you do not use all the cores you have to
    adjust your threshold appropriately.
  • Go to the J2SE people and ask whether there is a way to get the actual
    available cores to theJVM.
    ---------

We would be assuming that all cores are being used, and go ahead with the fix,
this would be documented and if a user is binding the process to one of the
cores then he should modify the threshold appropirately

Will check in the fix before 11/12

Comment by rampsarathy [ 11/Nov/08 03:04 AM ]

Checking in OSUtilSunspecific.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/util/os/OSUtilSunspecific.java,v
<-- OSUtilSunspecific.java
new revision: 1.8; previous revision: 1.7

Assigning to docs so that this can be updated.

Comment by sanandal [ 13/Nov/08 08:20 PM ]

Modified the subcomponent to docs

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by chinmayee_srivathsa [ 05/Dec/08 12:59 AM ]

Needs to be documented

Comment by chinmayee_srivathsa [ 12/Jan/09 08:12 AM ]

Created an attachment (id=917)
release notes

Comment by chinmayee_srivathsa [ 12/Jan/09 08:14 AM ]

See page 12 in attached file.





[SAILFIN-1329] Detailed help (--help) missing for enable/disable-converged-lb-server Created: 29/Oct/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sonymanuel Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


Issuezilla Id: 1,329
Tags:
Participants: chinmayee_srivathsa, sonymanuel and Yamini K B

 Description   

asadmin --help for these commands just print the usages.

sony@nila:~/workspace/as-telco-sqe/system-tests/test-repository/clb$ asadmin
disable-converged-lb-server --help
Usage: disable-converged-lb-server [--terse=false] [--echo=false]
[--interactive=true] [--host localhost] [--port 4848] [--secure|-s=true] [--user
admin_user] [--passwordfile file_name] [--timeout 30] target
sony@nila:~/workspace/as-telco-sqe/system-tests/test-repository/clb$ asadmin
enable-converged-lb-server --help
Usage: enable-converged-lb-server [--terse=false] [--echo=false]
[--interactive=true] [--host localhost] [--port 4848] [--secure|-s=true] [--user
admin_user] [--passwordfile file_name] target
sony@nila:~/workspace/as-telco-sqe/system-tests/test-repository/clb$



 Comments   
Comment by Yamini K B [ 29/Oct/08 09:33 PM ]

Chinmayee, haven't you checked in the missing man pages yet?

Comment by chinmayee_srivathsa [ 30/Oct/08 10:05 PM ]

The fix is available.

Will mark this bug as fixed once the man pages are integrated into the build.

Comment by chinmayee_srivathsa [ 03/Nov/08 01:45 AM ]

Fixed man pages checked in on 10/31.





[SAILFIN-1326] asadmin --help does not list any clb commands. Created: 29/Oct/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sonymanuel Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


Issuezilla Id: 1,326
Tags:
Participants: chinmayee_srivathsa, sonymanuel and Yamini K B

 Description   

Using build 57. None of the CLB commands are listed. Since the clb commands are
specific to SailFin just wondering if only the GlassFish commands are listed by
'asadmin --help'



 Comments   
Comment by Yamini K B [ 29/Oct/08 09:28 PM ]

asadmin main help page needs to be updated with all the new (SailFin) commands.

Comment by chinmayee_srivathsa [ 30/Oct/08 10:04 PM ]

The fixed man page is ready but the updated man pages are not yet checked in,

Will mark this bug as fixed once the man pages are integrated into the build.

Comment by chinmayee_srivathsa [ 03/Nov/08 01:48 AM ]

Man pages checked in on 10/31

Comment by chinmayee_srivathsa [ 03/Nov/08 01:57 AM ]

Checked in man fixed man page on 10/31





[SAILFIN-1315] Translation of English into corresponding language is not unique at all places Created: 25/Oct/08  Updated: 08/Oct/09

Status: Open
Project: sailfin
Component/s: L10n
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: sayali2306 Assignee: gmurr
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: Text File Issue.doc    
Issuezilla Id: 1,315
Tags:
Participants: chinmayee_srivathsa, gmurr, irfanahmed, prasads and sayali2306

 Description   

When Nevigating to SailFIN documentation section if we click in You can see
this in other languages part ; some section is lacking translation of English
into corresponding languae offered as an wxample see this link:

http://docs.sun.com/app/docs/doc/820-4604?l=ja

here Java Business Integration is not translated into corresponding language.

THAnk You,
Sayali Dharmadhikari
SJSU

only . is in english its corresponding translation is missing



 Comments   
Comment by sayali2306 [ 25/Oct/08 12:38 PM ]

Created an attachment (id=790)
File ontent gives screen shot of the error found

Comment by irfanahmed [ 27/Oct/08 09:49 PM ]

This has nothing to do with the Admin GUI. This is a documentation bug and hence
I am assigning to the doc sub-group.

Comment by chinmayee_srivathsa [ 30/Oct/08 10:36 PM ]

Re-assigning to l10n category.

820-4604 is a application server 9.1 doc.

Comment by prasads [ 14/Dec/08 10:42 PM ]

Re-assigning to Georges

Comment by gmurr [ 08/Oct/09 09:01 AM ]

need to reassign to l10n doc.





[SAILFIN-1271] add --properties option for AR deployment Created: 16/Oct/08  Updated: 12/Nov/08  Resolved: 12/Nov/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Improvement Priority: Major
Reporter: erikvandervelden Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,271
Tags:
Participants: chinmayee_srivathsa, erikvandervelden, swethadn and Yamini K B

 Description   

The JSR289 spec opens up the possibility to pass initialisation properties to
Application Routers, but does not define how these properties should be provided
to the container.
The proposal here is to support these configuration properties for Application
Routers expliclity deployed using an asadmin deploy command. The --properties
parameter can be used for this. These properties should then be stored in the
domain.xml file, since it is not known upfront which of the (potentially many)
deployed ARs is actually selected. The application can even switch between ARs
by setting a system property.

PS.Please also provide some advice on how to access the properties for a given
AR from the code of the application dispatcher that does the actual
instantiation and initialisation of the AR.



 Comments   
Comment by Yamini K B [ 16/Oct/08 10:38 PM ]

Need to add support for --properties option to 'deploy' command. These
properties should be applicable for the extension-module element.

Comment by swethadn [ 04/Nov/08 01:06 AM ]

The code for the property option is not implemented for the extension module.

Comment by swethadn [ 11/Nov/08 09:51 PM ]

//The property option is sent as a Map in the request from
PEDeploymentService.java and implemented for the extension module in
DeploymentServiceUtils.java
Issue number: 1271
Obtained from:
Submitted by:
Reviewed by: Prasad, Yamini
Tests Run : Sailfin QL,
Sailfin Cluster QL,
Glassfish QL,
Dev tests for deployment :
simpleSipApp_startup,
simpleSipApp_deploy,
simpleSipApp_undeploy.

Checking in
admin-cli/commands/src/java/com/sun/enterprise/cli/commands/CLIDescriptor.xml;
/cvs/glassfish/admin-cli/commands/src/java/com/sun/enterprise/cli/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.70.2.3; previous revision: 1.70.2.2
done
Checking in
admin-cli/commands/src/java/com/sun/enterprise/cli/commands/DeployCommand.java;
/cvs/glassfish/admin-cli/commands/src/java/com/sun/enterprise/cli/commands/DeployCommand.java,v
<-- DeployCommand.java
new revision: 1.11.6.1; previous revision: 1.11
done
Checking in
appserv-commons/src/java/com/sun/enterprise/deployment/util/DeploymentProperties.java;
/cvs/glassfish/appserv-commons/src/java/com/sun/enterprise/deployment/util/DeploymentProperties.java,v
<-- DeploymentProperties.java
new revision: 1.13.6.1; previous revision: 1.13
done
Checking in
appserv-core/src/java/com/sun/enterprise/deployment/phasing/DeploymentServiceUtils.java;
/cvs/glassfish/appserv-core/src/java/com/sun/enterprise/deployment/phasing/DeploymentServiceUtils.java,v
<-- DeploymentServiceUtils.java
new revision: 1.36.2.5; previous revision: 1.36.2.4
done
Checking in
appserv-core/src/java/com/sun/enterprise/deployment/phasing/PEDeploymentService.java;
/cvs/glassfish/appserv-core/src/java/com/sun/enterprise/deployment/phasing/PEDeploymentService.java,v
<-- PEDeploymentService.java
new revision: 1.21.2.3; previous revision: 1.21.2.2
done

Comment by swethadn [ 12/Nov/08 09:31 PM ]

Reassigning the issue to docs .

Comment by swethadn [ 12/Nov/08 09:36 PM ]

This issue needs to be documented as new --property option is added to the
deploy command .

Comment by chinmayee_srivathsa [ 12/Nov/08 11:07 PM ]

Created new sailfin-specific deploy man page.

RCS file: /cvs/sailfin/administration/src/main/sman/cat1/deploy.1,v
done
Checking in deploy.1;
/cvs/sailfin/administration/src/main/sman/cat1/deploy.1,v <-- deploy.1
initial revision: 1.1
done

RCS file: /cvs/sailfin/administration/src/main/sman/man1/deploy.1,v
done
Checking in deploy.1;
/cvs/sailfin/administration/src/main/sman/man1/deploy.1,v <-- deploy.1
initial revision: 1.1
done





[SAILFIN-1208] [online doc]Dynamic Reconfiguration does not work for SIP Access Logging Created: 29/Sep/08  Updated: 29/Mar/09  Resolved: 29/Mar/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: srinik76 Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,208
Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, jagadesh, prasads, srinik76 and Yamini K B

 Description   

If the access log is enabled/disabled under sip-service, the admin server needs
to be restarted for changes to be active.

Also log rotation needs to be implemented for sip access logging. Currently only
5 fields are supported in the access logging format. Needed support for some
more parameters.



 Comments   
Comment by srinik76 [ 29/Sep/08 02:56 AM ]

The sip access log enabled parameter is read in the SIP container code. Dynamic
reconfiguration feature needs to be reimplemented in the sip container level.

Comment by Yamini K B [ 30/Sep/08 07:49 AM ]

Dynamic reconfig support changes completed:

RCS file:
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLog.java,v
done
Checking in
integration/src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLog.java;
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLog.java,v
<-- AccessLog.java
initial revision: 1.1
done
Checking in
integration/src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLogReporter.java;
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLogReporter.java,v
<-- AccessLogReporter.java
new revision: 1.2; previous revision: 1.1
done
Checking in
integration/src/main/java/org/jvnet/glassfish/comms/startup/SipContainer.java;
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/startup/SipContainer.java,v
<-- SipContainer.java
new revision: 1.5; previous revision: 1.4
done
Checking in
integration/src/main/java/org/jvnet/glassfish/comms/startup/lifecycle/SipContainerLifecycle.java;
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/startup/lifecycle/SipContainerLifecycle.java,v
<-- SipContainerLifecycle.java
new revision: 1.12; previous revision: 1.11
done
Checking in
integration/src/main/java/org/jvnet/glassfish/comms/startup/stack/StackConfig.java;
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/startup/stack/StackConfig.java,v
<-- StackConfig.java
new revision: 1.13; previous revision: 1.12
done
Checking in
sip-stack/src/java/com/ericsson/ssa/container/GrizzlyNetworkManager.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/ssa/container/GrizzlyNetworkManager.java,v
<-- GrizzlyNetworkManager.java
new revision: 1.93; previous revision: 1.92
done

Comment by srinik76 [ 24/Oct/08 12:37 AM ]

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLog.java;
/cvs/sailfin/integration/src/main/java/org/jvnet/glassfish/comms/admin/callflow/reporter/AccessLog.java,v
<-- AccessLog.java
new revision: 1.2; previous revision: 1.1
done
Implemented Log Rotation based on time and size and also added some headers to
be printed in the Sip Access Log.
Issue number: 1208
Obtained from:
Submitted by:
Reviewed by: Yamini

Tests Run: Sailfin QL, Cluster QL

Comment by srinik76 [ 30/Oct/08 11:58 PM ]

This issue needs to be documented for the possible formats that can be access
logged.

Comment by srinik76 [ 31/Oct/08 12:00 AM ]

Apart from the default format that is available from the time of installation
the following can be logged.

"%via% %call.id% %to% %from% %cseq% %max.forwards% %contact% %content.type%"

The above needs to be documented.

Comment by srinik76 [ 31/Oct/08 12:18 AM ]

Also Log Rotation Feature needs to be documented. A new property is added under
sip-service 'accessLogSize' which is used for log rotation based on file size.

Comment by Yamini K B [ 31/Oct/08 06:15 PM ]

Changing category. SIP access logging needs to be documented in detail.

Comment by chinmayee_srivathsa [ 03/Nov/08 03:04 AM ]

Does not impact bundled docs.

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by jagadesh [ 16/Jan/09 07:47 AM ]

Downgrading to a P4 since these bugs are not targeted for Sailfin 1.0. will be
upgraded back to the original priority for Sailfin 2.0

Comment by prasads [ 26/Mar/09 12:56 AM ]

Resetting the priority back to the original one.

Comment by chinmayee_srivathsa [ 29/Mar/09 10:13 PM ]

The fix is available in the SailFin 1.0 Administration guide at:

http://docs.sun.com/app/docs/doc/820-4281/gicaf?a=view





[SAILFIN-1183] [online docs] Installation instructions are incorrect Created: 18/Sep/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: erwinharkink Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All
URL: https://sailfin.dev.java.net/downloads/instructions.html


File Attachments: PDF File SJSASEEIG.pdf    
Issuezilla Id: 1,183
Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, erwinharkink, prasads and sanandal

 Description   

The installation instructions described on the web page
https://sailfin.dev.java.net/downloads/instructions.html are incorrect.

The line
% java -jar filename.jar
is missing the "-Xmx256m" option. Furthermore, it describes a "step 4", though
this is not there anymore (as it was with older descriptions,
seehttps://sailfin.dev.java.net/downloads/v1-b51.html)



 Comments   
Comment by sanandal [ 14/Oct/08 05:09 AM ]

Assigned to Chinmayee

Comment by chinmayee_srivathsa [ 16/Oct/08 12:04 AM ]

Needs to be fixed on the download webpage on sailfin.dev.java.net and in the
installation guide.

Comment by chinmayee_srivathsa [ 30/Oct/08 09:23 PM ]

Does not affect bundled docs.

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by chinmayee_srivathsa [ 23/Nov/08 08:35 PM ]

Fixed in the instructions page:
https://sailfin.dev.java.net/downloads/instructions.html

Fixed in the Installation guide also. With more details about the -Xmx feature

Comment by chinmayee_srivathsa [ 23/Nov/08 09:07 PM ]

Created an attachment (id=842)
SGCS install guide with fix





[SAILFIN-1124] [online docs] Building a app with a Custom Application Router requires ant version 1.7 Created: 02/Sep/08  Updated: 25/Nov/10  Resolved: 12/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: varunrupela Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


File Attachments: PDF File SJSASEERN.pdf    
Issue Links:
Dependency
blocks SAILFIN-1092 [BLOCKING] With proxy-uas chaining, A... Resolved
Issuezilla Id: 1,124
Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, jagadesh, lwhite, naman_mehta, prasads and varunrupela

 Description   

Sailfin build 48

To build an application with a Custom Application Router the <service> element
of the "jar" ant task needs to be used. The <service> element is only available
with ant 1.7. The issue is that such an app cannot be built with sailfin since
sailfin is currently is on version 1.6.5. Discussed this with Prasad; the
solution at this point seems to be to update sailfin's "asant" to support the
<service> element of the "jar" task ?

<jar destfile="${dist.dir}/application-chaining-ar.jar" basedir="${build.dir}"
includes="*/ar/.class" >
<service type="javax.servlet.sip.ar.spi.SipApplicationRouterProvider"
provider="<provider-implementation-class-information>" />
</jar>

A sample app (with source) is attached with issue 1092.



 Comments   
Comment by lwhite [ 05/Sep/08 12:59 PM ]

Assigning to Prasad. This has nothing to do with replication.
Changing subcomponent to build system.

Comment by prasads [ 06/Oct/08 10:13 AM ]

Re-assigning this to Naman.

Please see if this needs to be fixed in the Sailfin build system ? I am not sure
this is an issue in the build system.

Comment by naman_mehta [ 06/Oct/08 10:58 PM ]

We are not planning to upgrade ant version from 1.6.5 to 1.7.0. So please find
work around for <service> element.

Comment by varunrupela [ 14/Oct/08 03:31 AM ]

Need to doc that:

  • Ant 1.7 is required to build a Custom Application Router app
  • User will need to separately download Ant 1.7.

Sample ant target to build the Custom AR:
<target name="package-ar">
<mkdir dir="${dist.dir}" />
<jar destfile="${dist.dir}/application-chaining-ar.jar"
basedir="${build.dir}" includes="*/ar/.class" >
<service
type="javax.servlet.sip.ar.spi.SipApplicationRouterProvider"

provider="com.sun.asqe.sessionreplication.applicationchaining.ar.Select_B_AR_Provider"
/>
</jar>
<antcall target="publish" >
<param name="application.archive" value="application-chaining-ar.jar"/>
</antcall>
</target>

Along with this the following class is required that would define the Service
Provider (where CustomApplicationRouter is your AR implementation):

**********

package com.sun.asqe.sessionreplication.applicationchaining.ar;

import javax.servlet.sip.ar.SipApplicationRouter;
import javax.servlet.sip.ar.spi.SipApplicationRouterProvider;

public class Select_B_AR_Provider extends SipApplicationRouterProvider {

@Override
public SipApplicationRouter getSipApplicationRouter() { return new CustomApplicationRouter(); }

}

Comment by naman_mehta [ 14/Oct/08 03:48 AM ]

Need to document this as per the comment by Varun.

Comment by varunrupela [ 14/Oct/08 03:52 AM ]

cc'ing Erik for any further doc input / corrections.

Comment by chinmayee_srivathsa [ 30/Oct/08 09:21 PM ]

This bug will be documented in the Release Notes (as a known issue) or in the
Developer's guide and Application Deployment guide

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by jagadesh [ 09/Dec/08 09:20 PM ]

Varun,

I think this is not a bug in the server code. But upgrading to 1.7.x can go as
RFE. I think there is one ANT upgrade RFE for glassfish.

It is only the application packaging part. Means, it is up to the user what to use.

Here is the modified target that can work with ant 1.6.5. Please try. If you are
satisfied, then I would say please make it RFE or close it.

<target name="package-ar">
<mkdir dir="${dist.dir}" />
<mkdir dir="${build.dir}/META-INF/services/"/>
<echo
file="${build.dir}/META-INF/services/javax.servlet.sip.ar.spi.SipApplicationRouterProvider">com.sun.asqe.sessionreplication.applicationchaining.ar.Select_B_AR_Provider
</echo>

<jar destfile="${dist.dir}/application-chaining-ar.jar"
basedir="${build.dir}" includes="*/ar/.class, */services/" >
</jar>
<antcall target="publish" >
<param name="application.archive" value="application-chaining-ar.jar"/>
</antcall>
</target>

Comment by chinmayee_srivathsa [ 12/Jan/09 08:13 AM ]

See "Ant version" section on page 9 in the attached file.

Comment by chinmayee_srivathsa [ 12/Jan/09 08:22 AM ]

Created an attachment (id=919)
release notes





[SAILFIN-1072] Admin. Ref. guide: Missing SIP/Converged-sip modules deployment ifo. Created: 01/Aug/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sujatha_chintalapati Assignee: chinmayee_srivathsa
Resolution: Incomplete Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All
URL: https://sailfin.dev.java.net/documentation/documents/SJSASEEAREF.pdf


Issuezilla Id: 1,072
Tags:
Participants: chinmayee_srivathsa, prasads and sujatha_chintalapati

 Description   

Sailfin 1.0
Admin reference guide

  • Information SIP/Converged-sip modules deployment is missing from Admin
    reference documentation.


 Comments   
Comment by sujatha_chintalapati [ 01/Aug/08 11:46 AM ]

Only information about SIp/Converged modules deployment is missing. All other
application module deployment info. is there in admin reference guide

Comment by prasads [ 03/Aug/08 09:17 PM ]

Re-assign to Chinmayee. These need to be evaluated ASAP.

Comment by chinmayee_srivathsa [ 03/Aug/08 09:24 PM ]

Sujatha,

The Admin Reference guide lists and describes the elements in the domain.xml.
For deployment information, see the Application Deployment guide at:

http://sailfin.dev.java.net/documentation/documents/SJSASEEADG.pdf

I have marked the bug invalid for now.
Please re-open if I have misundertood something or if some properties in the
domain.xml have not been documented in the Admin Reference.





[SAILFIN-1071] Admin.Ref.Guide:Missing info. for SIP Service screen Created: 01/Aug/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sujatha_chintalapati Assignee: chinmayee_srivathsa
Resolution: Duplicate Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All
URL: https://sailfin.dev.java.net/documentation/documents/SJSASEEAREF.pdf


Issuezilla Id: 1,071
Tags:
Participants: chinmayee_srivathsa, jagadesh, prasads, Rebecca Parks and sujatha_chintalapati

 Description   

Sailfin 1.0

The following Info. for SIP Service is missing from Admin reference documentation:

Configuration->SIP Service:
Access Logging: enabled (by default)
Access Log BufferSize: 5200 (by default)
Access Log Write Interval: 11 (by default
Propery:

How to reproduce:
=================
1) In glassfish communication server, go to Configuration->SIP Service.
The above information for Accesslogging, Access Log buffer size etc... will be
displayed.
2) Go to the following documentation
https://sailfin.dev.java.net/documentation/documents/SJSASEEAREF.pdf
3)

  • On page 149, no information about sip service page attributes except the
    following lines and info. about sip service sub-elements.
    "sip-service
    Defines the SIP service."


 Comments   
Comment by prasads [ 03/Aug/08 09:17 PM ]

Re-assign to Chinmayee. These need to be evaluated ASAP.

Comment by chinmayee_srivathsa [ 03/Aug/08 09:54 PM ]

re-assigning to June Parks.

Comment by jagadesh [ 06/Aug/08 11:27 AM ]

"This bug will be scrubbed and will be upgraded for next relevant milestone builds".

Comment by Rebecca Parks [ 07/Aug/08 11:01 AM ]

1. The engineers should have told the writing team about these properties when
they were first created. Filing a bug after the fact is not efficient.

2. If these had been attributes rather than properties, the writing team may
have seen them in the domain DTD earlier. This is why creating attributes, not
properties, is a best practice.

3. The exact property names do not appear in this report, and the parent
element in the DTD is only implied. More specific information is needed.
Again, if these were attributes, a simple pointer to the DTD would have been
sufficient.

Reassigning to the reporting engineer to get more specific info.

Comment by prasads [ 14/Aug/08 11:38 AM ]

Marking all of them as P3

Comment by prasads [ 28/Aug/08 11:23 PM ]

Re-assigning to Chinmayee

Comment by chinmayee_srivathsa [ 17/Sep/08 04:23 AM ]

started

Comment by chinmayee_srivathsa [ 13/Oct/08 02:15 AM ]

Will be fixed as part of fix for 637.

      • This issue has been marked as a duplicate of 637 ***




[SAILFIN-1068] Admin. Ref. guide: Documenation doesn't exists in the above URL Created: 31/Jul/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sujatha_chintalapati Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All
URL: http://docs.sun.com/app/docs/coll/1343.8


Issuezilla Id: 1,068
Tags:
Participants: chinmayee_srivathsa, prasads and sujatha_chintalapati

 Description   

SGCS Administration Reference guide:

Appserver documantion doesn't exists in the URL:
http://http://docs.sun.com/app/docs/coll/1343.8
How to reproduce:
==================

  • Click on the link for the errors "http://docs.sun.com/app/docs/coll/1343.8".

"Error: The requested item has been deleted.

Sun Java System Communications Application Server 1.0 was deleted on 2008-04-15"



 Comments   
Comment by prasads [ 03/Aug/08 09:17 PM ]

Re-assign to Chinmayee. These need to be evaluated ASAP.

Comment by chinmayee_srivathsa [ 03/Aug/08 09:53 PM ]

To be fixed

Comment by chinmayee_srivathsa [ 06/Aug/08 10:05 AM ]

Fixed





[SAILFIN-1066] Comments to the Quick start guide Created: 30/Jul/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: easarina Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


Issuezilla Id: 1,066
Tags:
Participants: chinmayee_srivathsa and easarina

 Description   

Please see bellow my comments to the Quick start guide:
https://sailfin.dev.java.net/documentation/documents/SJSASEEQSG.pdf

1) p. 7
Java ES Solaris installations: /var/opt/SUNWappserver/domains/
Java ES Linux installations: /var/opt/sun/appserver/domains/

These domain paths are valid only for pkg based AS from JES. Also, I'm not
sure that "Java ES " is a valid name.

2) p. 17
"In a terminal window, type this command: asadmin create-node-agent --user admin
nodeagentname
The create-node-agent command uses the default value localhost for --host and
4848 for --port to identify the Domain Administration Server (DAS) or target
domain on which the node agent is created. Provide appropriate values for the
--host option and --port option, to specify a target domain for the node agent. "

I think that it is better to mention here that if a node agent will be created
on another, not DAS machine, then this asadmin create-node-agent command has to
be executed on that, not DAS, machine.

3) p. 18
"Product details at install-dir/docs-ee/about.html". Really at
install-dir/docs/about.html . Directory docs-ee doesn't exist.

4) p. 26
Upload text box, and navigate to
install-dir/samples/ee-samples/highavailability/apps/clusterjsp/clusterjsp.ear

Really ee-samples directory doesn't exist and clusterjsp.ear in all cases
under install-dir/samples/quickstart/clusterjsp



 Comments   
Comment by easarina [ 30/Jul/08 12:40 PM ]

cc Jagadesh

Comment by chinmayee_srivathsa [ 31/Jul/08 03:11 AM ]

Reassigning to myself.
1) Fixed
2) Instead of providing all information here, I have instead provided a link to
the Node Agents chapter on the High-Availability Admin guide.
3) Fixed
4) Fixed

Comment by chinmayee_srivathsa [ 31/Jul/08 03:19 AM ]

Fixed version of the guide is re-posted at:
http://sailfin.dev.java.net/documentation/documents/SJSASEEQSG.pdf





[SAILFIN-1038] Default header size of SIp message needs to be documented Created: 15/Jul/08  Updated: 25/Nov/10  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: rampsarathy Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issue Links:
Dependency
blocks SAILFIN-1036 Looping of request causing Parsing is... Resolved
blocks SAILFIN-1029 UnsupportedOperationException (issue ... Resolved
Issuezilla Id: 1,038
Tags: shark-approved
Participants: chinmayee_srivathsa, rampsarathy and sanandal

 Description   

An outbound SIP message from sailfin cannot have headers of more than 8K in
size, this is a limitation and needs to be documented. The default value of the
header size is 8K and can be modified using the property
<config>.sip-service.connection-pool.send-buffer-size-in-bytes=

This has to be documented, please refer to Issues 1029 and 1036 for problems
because of this setting



 Comments   
Comment by sanandal [ 15/Jul/08 11:43 PM ]

Adding keyword shark-approved

Comment by chinmayee_srivathsa [ 16/Jul/08 04:37 AM ]

To be fixed in the Release Notes.

Comment by chinmayee_srivathsa [ 23/Jul/08 02:25 AM ]

Fixed in the Release Notes.

See: http://sailfin.dev.java.net/documentation/documents/SJSASEERN.pdf





[SAILFIN-1015] asadmin command set-dcr-file does not support --echo option Created: 04/Jul/08  Updated: 06/Aug/08  Resolved: 06/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sonymanuel Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


Issuezilla Id: 1,015
Tags:
Participants: chinmayee_srivathsa, sonymanuel, swethadn and Yamini K B

 Description   

sony@nila:~/workspace/ql/sailfin/sailfin-tests$ asadmin set-dcr-file --echo=true
--clbconfig sqe-cluster-clb-config config/sf-ql-dcr.xml
Usage: set-dcr-file --clbconfig clbconfig | --clbname clbname [--terse=false]
[--echo=false] [--interactive=true] [--host localhost] [--port 4848]
[--secure|-s=true] [--user admin_user] [--passwordfile file_name] dcr_file_name
CLI013 Option echo does not apply to set-dcr-file.

sony@nila:~/workspace/ql/sailfin/sailfin-tests$ asadmin set-dcr-file
--echo=false --clbconfig sqe-cluster-clb-config config/sf-ql-dcr.xml
Usage: set-dcr-file --clbconfig clbconfig | --clbname clbname [--terse=false]
[--echo=false] [--interactive=true] [--host localhost] [--port 4848]
[--secure|-s=true] [--user admin_user] [--passwordfile file_name] dcr_file_name
CLI013 Option echo does not apply to set-dcr-file.



 Comments   
Comment by Yamini K B [ 04/Jul/08 12:22 AM ]

echo option is missing in the descriptor

Comment by swethadn [ 04/Jul/08 02:22 AM ]

echo option has to be included for set-dcr-file in descriptor.

Comment by swethadn [ 04/Jul/08 05:51 AM ]

//echo option is included for set-dcr-file in CLIDescriptor.xml.

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.36; previous revision: 1.35
done

Comment by chinmayee_srivathsa [ 06/Aug/08 09:20 AM ]

re-opening for dcos fix

Comment by chinmayee_srivathsa [ 06/Aug/08 09:22 AM ]

re-assigning to myself

Comment by chinmayee_srivathsa [ 06/Aug/08 09:25 AM ]

fixed in the reference manual





[SAILFIN-1013] Logger names should have smaller keys. Created: 03/Jul/08  Updated: 13/Oct/08  Resolved: 13/Oct/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: binod Assignee: srinik76
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 1,013
Tags: shark-na
Participants: binod, chinmayee_srivathsa, prasads, Rebecca Parks, sanandal, srinik76 and Yamini K B

 Description   

Please see the comment about logger names in the evaluation blog here.

http://technfun.wordpress.com/2008/07/03/evaluation-of-sailfin/



 Comments   
Comment by Yamini K B [ 03/Jul/08 10:05 PM ]

Wondering if the loggers should be changed to attributes, but this would mean
DTD change.

Comment by prasads [ 04/Jul/08 01:43 AM ]

Can we retain them as properties and use a smaller key such as clb, sip, ar etc
, instead of javax.enterprise ......

Comment by Yamini K B [ 04/Jul/08 03:46 AM ]

Eltjo introduced those names to be consistent with the GlassFish logger domain
conventions.

Comment by binod [ 04/Jul/08 04:27 AM ]

Let me clarify...

The internal name of the logger that gets printed in the server.log could still follow the usual naming
conventions. However, it is pretty clear that for administrators (especially for CLI) the long name is
difficult. This issue is to investigate the possibility of providing an aliasing as we provide for normal
glassfish loggers.

Comment by Yamini K B [ 04/Jul/08 04:36 AM ]

ok.. I think it should be doable.

Comment by Yamini K B [ 07/Jul/08 10:13 PM ]

assigning to Srini

Comment by prasads [ 09/Jul/08 03:08 AM ]

Marking as candidates for shark

Comment by srinik76 [ 10/Jul/08 12:18 AM ]

Property element keys in domain.xml need to be changed to smaller values and in
the LogUtil code level needs to be resetted using the value from property element.

Comment by binod [ 13/Jul/08 10:47 PM ]

IMO, this can be marked as shark-na

Comment by sanandal [ 14/Jul/08 01:24 AM ]

Updated keywords as shark-na

Comment by srinik76 [ 15/Jul/08 03:01 AM ]

Modified the sailfin logger property names in domain.xml

javax.enterprise.system.container.clb to clb
javax.enterprise.system.container.sip to sip
javax.enterprise.system.container.ar to ar
javax.enterprise.system.container.ssr to ssr
javax.enterprise.system.container.sip.smi to smi

Checking in common/src/main/java/org/jvnet/glassfish/comms/util/LogUtil.java;
/cvs/sailfin/common/src/main/java/org/jvnet/glassfish/comms/util/LogUtil.java,v
<-- LogUtil.java
new revision: 1.13; previous revision: 1.12
done
Checking in administration/src/main/resources/templates/developer/sipdomain.xml.xsl;
/cvs/sailfin/administration/src/main/resources/templates/developer/sipdomain.xml.xsl,v
<-- sipdomain.xml.xsl
new revision: 1.25; previous revision: 1.24
done
Checking in administration/src/main/resources/templates/cluster/sipdomain.xml.xsl.4;
/cvs/sailfin/administration/src/main/resources/templates/cluster/sipdomain.xml.xsl.4,v
<-- sipdomain.xml.xsl.4
new revision: 1.13; previous revision: 1.12
done

Comment by chinmayee_srivathsa [ 04/Aug/08 12:59 AM ]

Adding June to the interest list.

June, please check if this change affects the Admin Reference guide,

Comment by chinmayee_srivathsa [ 04/Aug/08 01:05 AM ]

Adding June to the interest list.

June, please check if this change affects the Admin Reference guide,

Comment by Rebecca Parks [ 07/Aug/08 10:19 AM ]

This change has already been made in the Administration Reference.

Comment by srinik76 [ 07/Aug/08 10:09 PM ]

This needs to be documented for SGCS 1.5 only, since this fix is not available
in SGCS 1.0.

If the documentation happens for SGCS 1.0, it will confuse the user.

Comment by Rebecca Parks [ 08/Aug/08 09:08 AM ]

The Admin Reference is already out the door. I made this change a while back.
By the way, no one was interested in reviewing this doc when they could.

I suggest adding an entry to the Release Notes about the "temporarily long"
logger names.

Comment by chinmayee_srivathsa [ 13/Oct/08 02:36 AM ]

Documented at: http://sailfin.dev.java.net/documentation/documents/SJSASEEAREF.pdf





[SAILFIN-998] [online docs] Server startup ok even if SIP/SIPS ports are not bound Created: 30/Jun/08  Updated: 03/Sep/09

Status: Open
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: sonymanuel Assignee: chinmayee_srivathsa
Resolution: Unresolved Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: Text File server.log    
Issuezilla Id: 998
Tags: shark-na
Participants: chinmayee_srivathsa, jagadesh, prasads, sonymanuel, srinik76, swethadn and Yamini K B

 Description   

During instance startup if the SIP(s) ports are not started properly the server
startup doesn't stop. Only when we run sip traffic we realize that the ports are
not up. Probably the instance startup should fail if its not able to bind to the
specified ports. This is what I have observed with other containers (EJB , web
jms etc). This is on a cluster with CLB enabled. I have not checked this with
standalone instance.



 Comments   
Comment by sonymanuel [ 30/Jun/08 07:12 AM ]

Created an attachment (id=516)
server log

Comment by sonymanuel [ 30/Jun/08 07:13 AM ]

Add Ramesh to cc.

Comment by prasads [ 30/Jun/08 09:52 PM ]

Re-assigning this issue to Yamini KB

Comment by Yamini K B [ 09/Jul/08 01:32 AM ]

This issue will require changes in container startup which might be risky to do
now, hence marking this issue as shark-na

However, we will need to release note the fact that administrator has to make
sure that there are no exceptions during the sip container startup and that it
has started up fine by looking at the server.log

Comment by Yamini K B [ 09/Jul/08 01:44 AM ]

This issue will require changes in container startup which might be risky to do
now, hence marking this issue as shark-na

However, we will need to release note the fact that administrator has to make
sure that there are no exceptions during the sip container startup and that it
has started up fine by looking at the server.log

Comment by jagadesh [ 06/Aug/08 11:24 AM ]

"This bug will be scrubbed and will be upgraded for next relevant milestone builds".

Comment by prasads [ 14/Aug/08 11:38 AM ]

Marking all of them as P3

Comment by sonymanuel [ 11/Sep/08 08:58 AM ]

Raising priority as this is causing errors when starting system tests runs. Also
see issue 1127.

Comment by Yamini K B [ 15/Oct/08 03:29 AM ]

Changing the category..

Comment by Yamini K B [ 31/Oct/08 02:55 AM ]

Checking in sip-stack/src/java/com/ericsson/ssa/container/SipBindingResolver.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/ssa/container/SipBindingResolver.java,v
<-- SipBindingResolver.java
new revision: 1.19; previous revision: 1.18
done
Checking in administration/src/main/resources/templates/cluster/sipdomain.xml.xsl.0;
/cvs/sailfin/administration/src/main/resources/templates/cluster/sipdomain.xml.xsl.0,v
<-- sipdomain.xml.xsl.0
new revision: 1.11; previous revision: 1.10
done
Checking in administration/src/main/resources/templates/developer/sipdomain.xml.xsl;
/cvs/sailfin/administration/src/main/resources/templates/developer/sipdomain.xml.xsl,v
<-- sipdomain.xml.xsl
new revision: 1.31; previous revision: 1.30
done

Comment by Yamini K B [ 04/Nov/08 09:51 PM ]

Backing out the fix since it is causing instance(s) startup to fail in cluster
setup.

Checking in src/java/com/ericsson/ssa/container/SipBindingResolver.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/ssa/container/SipBindingResolver.java,v
<-- SipBindingResolver.java
new revision: 1.20; previous revision: 1.19
done

Comment by prasads [ 11/Nov/08 04:43 AM ]

Marking it as a P4, since this was deemed to risky to fix or it was a code
change that was too late to be made at this point of the release.

Comment by Yamini K B [ 10/Mar/09 08:33 PM ]

Checking in src/java/com/ericsson/ssa/container/SipBindingResolver.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/ssa/container/SipBindingResolver.java,v
<-- SipBindingResolver.java
new revision: 1.21; previous revision: 1.20
done

Comment by Yamini K B [ 10/Mar/09 11:28 PM ]

backed out the change since it causes problem in dynamic reconfig

Comment by srinik76 [ 15/May/09 02:55 AM ]

The fix agreed is to clearly document all the ports used in SGCS. Will post the
details

Comment by swethadn [ 23/Jun/09 12:29 AM ]

The ports that are open for both glassfish and sailfin when DAS is started.

9701 – For TCP ports shoal specifies a port range internally from 9701 to 9999.
The first free port in this range will be used and it is not
configurable.
37776 - Enterprise server supplies an additional port to the broker , which is
used by it to start the RMI registry.
This is 100 + JMS port (7676) and it can be reconfigured.
3700 - In domain.xml the server.iiop-service.iiop-listener.orb-listener-1.port
is configured to 3700.
3820 - In domain.xml the server.iiop-service.iiop-listener.SSL.port is
configured to 3820
3920 - In domain.xml the server.iiop-service.iiop-listener.SSL_MUTUALAUTH.port
is configured to 3920
8686 - In domain.xml the server.admin-service.jmx-connector.system.port is
configured with port 8686.
8080 - In domain.xml the server.http-service.http-listener.http-listener-1.port
is configured to 8080.
8181 - In domain.xml the server.http-service.http-listener.http-listener-2.port
is confugured to the port 8181 with security-enabled.
5060 - The server.sip-service.sip-listener.sip-listener-1.port in the domain.xml
is configured with the port 5060 in both TCP and UDP.
5061 - The server.sip-service.sip-listener.sip-listener-2.port is configured to
the port 5061 with security enabled in domain.xml.
4848 - In domain.xml server.http-service.http-listener.admin-listener.port is
configured to 4848.
7676 - In domain.xml the server.jms-service.jms-host.default_JMS_host.port is
configured to the port 7676.

Comment by chinmayee_srivathsa [ 03/Sep/09 02:05 AM ]

Needs to be fixed in online docs.





[SAILFIN-951] [online docs] totalsipdialogs count doesn't increase with failedsipdialogs count Created: 10/Jun/08  Updated: 30/Mar/09  Resolved: 30/Mar/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: sankarpn Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 951
Tags: sf10-fcs-approved sf10-na shark-na
Participants: chinmayee_srivathsa, jagadesh, prasads, sankarpn and Yamini K B

 Description   

SailFin B36,

server.sip-service.session-manager.concurrentsipdialogs-count = 100
server.sip-service.session-manager.concurrentsipdialogs-description = Concurrent
SIP dialogs
server.sip-service.session-manager.concurrentsipdialogs-lastsampletime =
1213139135795
server.sip-service.session-manager.concurrentsipdialogs-name = ConcurrentSipDialogs
server.sip-service.session-manager.concurrentsipdialogs-starttime = 1213135761002
server.sip-service.session-manager.concurrentsipdialogs-unit = count
server.sip-service.session-manager.dotted-name = server.sip-service.session-manager
server.sip-service.session-manager.expiredsipdialogs-count = 0
server.sip-service.session-manager.expiredsipdialogs-description = Expired SIP
dialogs
server.sip-service.session-manager.expiredsipdialogs-lastsampletime = 1213139135805
server.sip-service.session-manager.expiredsipdialogs-name = expiredSipDialogs
server.sip-service.session-manager.expiredsipdialogs-starttime = 1213135761002
server.sip-service.session-manager.expiredsipdialogs-unit = count
server.sip-service.session-manager.failedsipdialogs-count = 100
server.sip-service.session-manager.failedsipdialogs-description = Failed SIP dialogs
server.sip-service.session-manager.failedsipdialogs-lastsampletime = 1213139135800
server.sip-service.session-manager.failedsipdialogs-name = FailedSipDialogs
server.sip-service.session-manager.failedsipdialogs-starttime = 1213135761002
server.sip-service.session-manager.failedsipdialogs-unit = count
server.sip-service.session-manager.successfulsipdialogs-count = 1
server.sip-service.session-manager.successfulsipdialogs-description = Successful
SIP dialogs
server.sip-service.session-manager.successfulsipdialogs-lastsampletime =
1213139135804
server.sip-service.session-manager.successfulsipdialogs-name = successfulSipDialogs
server.sip-service.session-manager.successfulsipdialogs-starttime = 1213135761002
server.sip-service.session-manager.successfulsipdialogs-unit = count
server.sip-service.session-manager.totalsipdialogcount-count = 1
server.sip-service.session-manager.totalsipdialogcount-description = Total SIP
dialog count
server.sip-service.session-manager.totalsipdialogcount-lastsampletime =
1213139135802
server.sip-service.session-manager.totalsipdialogcount-name = totalSipDialogCount
server.sip-service.session-manager.totalsipdialogcount-starttime = 1213135761002
server.sip-service.session-manager.totalsipdialogcount-unit = count
server.sip-service.session-manager.totalsipdialoglifetime-count = 4160
server.sip-service.session-manager.totalsipdialoglifetime-description = Total
SIP Dialog life time
server.sip-service.session-manager.totalsipdialoglifetime-lastsampletime =
1213139135799
server.sip-service.session-manager.totalsipdialoglifetime-name =
totalSipDialogLifeTime
server.sip-service.session-manager.totalsipdialoglifetime-starttime = 1213135761002
server.sip-service.session-manager.totalsipdialoglifetime-unit = count

In the above stats you can see that there are 100 failed sipdialogs and 1
successful sipdialog. But the totalsipdialogs count shows 1 which is equal to
the successful sipdialogs count. I think the totalsipdialogs count should be
equal to successful+failed sipdialogs count



 Comments   
Comment by prasads [ 16/Jun/08 03:53 AM ]

Mark as shark-na

Comment by jagadesh [ 06/Aug/08 11:22 AM ]

"This bug will be scrubbed and will be upgraded for next relevant milestone builds".

Comment by prasads [ 14/Aug/08 11:38 AM ]

Marking all of them as P3

Comment by Yamini K B [ 25/Sep/08 10:41 PM ]

Must fix for FCS.

Comment by Yamini K B [ 21/Oct/08 08:41 PM ]

On analyzing the dialog manager stats and looking at the code:

Concurrent dialogs: Refers to count of dialogs that are registered/stored.
Expired dialogs: Refers to count of timed out dialogs
Failed dialogs: Refers to count of >=400 <700 responses
Successful dialogs: Refers to count of >=200 <300 responses. This includes
retransmissions.
Total dialogs: Refers to count of successfully established dialogs.

So the stats would tally up as:
Total = Successful + Failed + Expired - Concurrent

Also, suppose you use 'sipp' client, you will observe that the total-calls will
match with total dialogs.

I've verified these stats under load and they add up fine. Assigning to docs to
update the above info in the admin guide.

Comment by chinmayee_srivathsa [ 30/Oct/08 09:26 PM ]

Does not affect bundled docs.

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by prasads [ 09/Jan/09 12:54 AM ]

"Reclassifying as P4 because these issues are not must fix for SailFin 1.0 release.
This issue will be scrubbed after this release and will be given the right
priority for SailFin 2.0 release."

Comment by prasads [ 26/Mar/09 12:47 AM ]

Reverting back the priority to the original priority

Comment by chinmayee_srivathsa [ 30/Mar/09 04:36 AM ]

The fix for this issue is available at:
http://docs.sun.com/app/docs/doc/820-4281/giejw?a=view





[SAILFIN-948] [online docs] asadmin stop-node-agent -stopinstances=false Created: 09/Jun/08  Updated: 05/Oct/09  Resolved: 05/Oct/09

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Improvement Priority: Minor
Reporter: andbur Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 948
Tags:
Participants: andbur, chinmayee_srivathsa, km, srinik76 and Yamini K B

 Description   

Should tell the NA to leave the SIs running. Maybe an open issue how NA can re-
establish any contact to the SIs if started with already running SIs.



 Comments   
Comment by km [ 13/Jun/08 06:29 AM ]

This is a major change in NA design. So, I think, this is really a "feature" not
an enhancement, mainly because NA was "designed" to take the instances down while
it shuts down. Provision of a simple flag on stop-node-agent does not allow us
make sweeping changes in the implementation.

Again, I agree with the spirit of this request, but it has implementation costs
that I am not sure of being able to fulfill in the short term. So, please let us
know which release (time frame) you are looking at, to get a fix for this.

Comment by andbur [ 16/Jun/08 03:43 AM ]

Ericsson will be using the "kill NA"-integration with SAF/AMF in our first
release. This issue effects our future design so the time frame would be Q4
2008.

Comment by Yamini K B [ 25/Sep/08 10:39 PM ]

Lowering the priority since it will not be fixed for 1.5

Comment by srinik76 [ 14/Apr/09 05:50 AM ]

Checked in the fix.

Added an option stopinstances to stop-node-agent to control the stop of
instances which is by default true

Issue number: 948
Obtained from:
Submitted by:
Reviewed by: Nandini

Tests Run: Glassfish Cluster QL

Modified Files:

admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/InstancesManager.java
admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/pe/PEDomainsManager.java
admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/pe/PEInstancesManager.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/BaseNodeAgent.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgentMain.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/ProcessInstanceInternal.java
admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/AgentManager.java
admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/EEInstancesManager.java
admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/ASShutdown.java
admin-core/util/src/java/com/sun/enterprise/admin/util/IAdminConstants.java
appserv-core/src/java/com/sun/enterprise/admin/event/ShutdownEvent.java
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/BaseNodeAgentCommand.java
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/StopNodeAgentCommand.java
appserv-core/src/java/com/sun/enterprise/server/PEMain.java

===================================================================
File: InstancesManager.java Status: Up-to-date

Working revision: 1.9.6.1
Repository revision: 1.9.6.1
/cvs/glassfish/admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/InstancesManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.9.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: PEDomainsManager.java Status: Up-to-date

Working revision: 1.22.2.3
Repository revision: 1.22.2.3
/cvs/glassfish/admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/pe/PEDomainsManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.22.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: PEInstancesManager.java Status: Up-to-date

Working revision: 1.22.2.2
Repository revision: 1.22.2.2
/cvs/glassfish/admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/pe/PEInstancesManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.22.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: BaseNodeAgent.java Status: Up-to-date

Working revision: 1.4.2.4
Repository revision: 1.4.2.4
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/BaseNodeAgent.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.4.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: NodeAgent.java Status: Up-to-date

Working revision: 1.28.2.6
Repository revision: 1.28.2.6
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.28.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: NodeAgentMain.java Status: Up-to-date

Working revision: 1.12.2.5
Repository revision: 1.12.2.5
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgentMain.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.12.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: ProcessInstanceInternal.java Status: Up-to-date

Working revision: 1.7.2.2
Repository revision: 1.7.2.2
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/ProcessInstanceInternal.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.7.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: AgentManager.java Status: Up-to-date

Working revision: 1.14.2.3
Repository revision: 1.14.2.3
/cvs/glassfish/admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/AgentManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.14.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: EEInstancesManager.java Status: Up-to-date

Working revision: 1.14.6.1
Repository revision: 1.14.6.1
/cvs/glassfish/admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/EEInstancesManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.14.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: ASShutdown.java Status: Up-to-date

Working revision: 1.1.8.1
Repository revision: 1.1.8.1
/cvs/glassfish/admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/ASShutdown.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.1.8)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: IAdminConstants.java Status: Up-to-date

Working revision: 1.6.6.3
Repository revision: 1.6.6.3
/cvs/glassfish/admin-core/util/src/java/com/sun/enterprise/admin/util/IAdminConstants.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.6.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: ShutdownEvent.java Status: Up-to-date

Working revision: 1.4.6.1
Repository revision: 1.4.6.1
/cvs/glassfish/appserv-core/src/java/com/sun/enterprise/admin/event/ShutdownEvent.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.4.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: CLIDescriptor.xml Status: Up-to-date

Working revision: 1.24.2.3
Repository revision: 1.24.2.3
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.24.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: BaseNodeAgentCommand.java Status: Up-to-date

Working revision: 1.5.6.3
Repository revision: 1.5.6.3
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/BaseNodeAgentCommand.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.5.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: StopNodeAgentCommand.java Status: Up-to-date

Working revision: 1.5.6.1
Repository revision: 1.5.6.1
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/StopNodeAgentCommand.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.5.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: PEMain.java Status: Up-to-date

Working revision: 1.21.6.2
Repository revision: 1.21.6.2
/cvs/glassfish/appserv-core/src/java/com/sun/enterprise/server/PEMain.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.21.6)
Sticky Date: (none)
Sticky Options: (none)

Comment by srinik76 [ 15/Apr/09 02:23 AM ]

This needs to be documented. Assigning to docs team

Comment by srinik76 [ 15/Apr/09 02:29 AM ]

New option has been added to stop-node-agent, stopinstances. The default value
is true. If stop-node-agent is invoked with stopinstances as false, then the
instances will not be stopped by node agent.

-bash-3.00# ./asadmin stop-node-agent --option
Usage: stop-node-agent [--terse=false] [--echo=false] [--stopinstances=true]
[--interactive=true] [--secure=true] [--agentdir nodeagent_path] [nodeagent_name]

Comment by srinik76 [ 15/Apr/09 03:29 AM ]

This needs to be documented in glassfish also.

Comment by chinmayee_srivathsa [ 03/Sep/09 02:01 AM ]

Checked in the updated man page to SailFin build.

For GlassFish, will fix this issue in the Reference manual.

Marking as [online docs].

Comment by chinmayee_srivathsa [ 05/Oct/09 11:58 PM ]

Fixed in the Reference Manual for GlassFish and SailFin





[SAILFIN-947] [online docs] asadmin set-environment <SI> foo=bar Created: 09/Jun/08  Updated: 05/Oct/09  Resolved: 05/Oct/09

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Improvement Priority: Critical
Reporter: andbur Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 947
Tags:
Participants: andbur, chinmayee_srivathsa, km, srinik76 and Yamini K B

 Description   

Should tell the NA to set a defined environment variable when starting a SI.
Similar functionality exists for -D flags today so it should be easy to add it
for environment variables. java.lang.Runtime.exec() even has a standard way of
doing it today.



 Comments   
Comment by km [ 13/Jun/08 06:23 AM ]

Once I have some more time, I am going to take a look at it, but I am not sure if
we need a new command for this. This is generally a "startup only" task and one
should be able to specify an environment variable while starting up a server
instance via NA. Alternatively, we could persist this to domain.xml, but that
means a larger change that we should all agree upon and understand.

What release you are looking to have a support for this?

Comment by km [ 13/Jun/08 06:34 AM ]

...

Comment by andbur [ 16/Jun/08 03:48 AM ]

Implementing it as another flag to start-instace is okay, I just copied the
design for -D flags. This issue effects our future design so the time frame
would be Q4 2008.

Comment by srinik76 [ 05/Jan/09 01:05 AM ]

Before starting the instance we can use the create-jvm-options to set the
envrionment properties. Also after stopping the instance if the property is not
required we can use delete-jvm-options.

Comment by Yamini K B [ 29/Jan/09 12:11 AM ]

Re-assigning to Srini

Comment by srinik76 [ 25/Feb/09 08:36 PM ]

Working on this. Planning to add a property to start-instance --setenv. Below is
the mail from the customer.

Yes, that will be perfect.
.andreas

From: Srinivas.Krishnan@Sun.COM Srinivas.Krishnan@Sun.COM
Sent: den 23 februari 2009 12:04
To: Andreas Burmester
Cc: Yamini K B; Srikanth Anandal
Subject: Re: Update on Issue 947

Andreas,

Thanks for your reply. I will do the following change in the start-instance
command

start-instance command will now contain [--setenv
(name=value)[:name=value]*] as one more option. Is this change fine?

Thanks
Srinivas
Andreas Burmester wrote:

> Hello,
> This issue is not to set JVM parameters (ie. -Dflags and similar) but
environment variables (ie set foo=bar; echo $foo in tsch). Hope this clarifies
things.
> .andreas

Comment by srinik76 [ 15/Apr/09 02:15 AM ]

Checked in the fix.

Checking in
admin-ee/admin/src/java/com/sun/enterprise/ee/admin/mbeanapi/NodeAgentMBean.java;
/cvs/glassfish/admin-ee/admin/src/java/com/sun/enterprise/ee/admin/mbeanapi/NodeAgentMBean.java,v
<-- NodeAgentMBean.java
new revision: 1.5.6.1; previous revision: 1.5
done
Checking in
admin-ee/admin/src/java/com/sun/enterprise/ee/admin/mbeanapi/ServersConfigMBean.java;
/cvs/glassfish/admin-ee/admin/src/java/com/sun/enterprise/ee/admin/mbeanapi/ServersConfigMBean.java,v
<-- ServersConfigMBean.java
new revision: 1.4.2.1; previous revision: 1.4
done
Checking in
admin-ee/mbeans/src/java/com/sun/enterprise/ee/admin/configbeans/ServersConfigBean.java;
/cvs/glassfish/admin-ee/mbeans/src/java/com/sun/enterprise/ee/admin/configbeans/ServersConfigBean.java,v
<-- ServersConfigBean.java
new revision: 1.10.2.2; previous revision: 1.10.2.1
done
Checking in
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java;
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java,v
<-- NodeAgent.java
new revision: 1.28.2.7; previous revision: 1.28.2.6
done
Checking in
admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/launch/ASLauncher.java;
/cvs/glassfish/admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/launch/ASLauncher.java,v
<-- ASLauncher.java
new revision: 1.25.2.3; previous revision: 1.25.2.2
done
Checking in
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml;
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.24.2.4; previous revision: 1.24.2.3
done
Checking in
admin-ee/mbeans/src/java/com/sun/enterprise/ee/admin/mbeans/ServersConfigMBean.java;
/cvs/glassfish/admin-ee/mbeans/src/java/com/sun/enterprise/ee/admin/mbeans/ServersConfigMBean.java,v
<-- ServersConfigMBean.java
new revision: 1.4.2.1; previous revision: 1.4
done

Added an option setenv in start-instance to be used to set environment when
starting the instance by nodeagent
Issue number: 947
Obtained from:
Submitted by:
Reviewed by: Nandini

Tests Run: Glassfish Cluster QL

Modified Files:

admin-ee/admin/src/java/com/sun/enterprise/ee/admin/mbeanapi/NodeAgentMBean.java
admin-ee/admin/src/java/com/sun/enterprise/ee/admin/mbeanapi/ServersConfigMBean.java
admin-ee/mbeans/src/java/com/sun/enterprise/ee/admin/configbeans/ServersConfigBean.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java
admin/servermgmt/src/java/com/sun/enterprise/admin/servermgmt/launch/ASLauncher.java
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml
admin-ee/mbeans/src/java/com/sun/enterprise/ee/admin/mbeans/ServersConfigMBean.java

Comment by srinik76 [ 15/Apr/09 02:21 AM ]

This needs to be documented. Reassigning to chinmayee

Comment by srinik76 [ 15/Apr/09 02:26 AM ]

The following needs to be documented.

start-instance now has a new option (--setenv) which will be used to set the
environment when the instance is started by the node agent.

-bash-3.00# ./asadmin start-instance --option
Usage: start-instance [--terse=false] [--echo=false] [--interactive=true]
[--host localhost] [--port 4848|4849] [--secure|-s=true] [--user admin_user]
[--passwordfile file_name] [--setenv (name=value)[:name=value]*] instance_name
CLI013 Option option does not apply to start-instance.

Comment by srinik76 [ 15/Apr/09 03:28 AM ]

This needs to be documented in glassfish also.

Comment by chinmayee_srivathsa [ 18/Aug/09 05:31 AM ]

Checked in the updated man page to SailFin build.

For GlassFish, will fix this issue in the Reference manual.

Comment by chinmayee_srivathsa [ 20/Aug/09 05:02 AM ]

Marking as [online docs].

Comment by chinmayee_srivathsa [ 05/Oct/09 11:57 PM ]

Fixed in the Reference Manual for GlassFish and SailFin





[SAILFIN-919] [online docs] start-node-agent –startinstances=false still watchdogs the server instances Created: 27/May/08  Updated: 06/Oct/09  Resolved: 06/Oct/09

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: andbur Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All
URL: http://wiki.glassfish.java.net/attach/FunctionalSpecsOnePagers/SAF-AMF-One-Pager.htm


File Attachments: PDF File SJSASEEREFMAN.pdf    
Issuezilla Id: 919
Tags: shark-na
Participants: andbur, chinmayee_srivathsa, jagadesh, ocorbun, prasads, srinik76 and Yamini K B

 Description   

Node Agents (NA) started with asadmin start-node-agent –startinstances=false
still watchdogs the server instances (SI) if the SI is started at a later stage
via DAS. (http://wiki.glassfish.java.net/attach/FunctionalSpecsOnePagers/SAF-
AMF-One-Pager.htm chapter 4.1.1 bullet c).

As a suggested solution, it might be a good idea to add a new flag called -
watchdog=false to control this specific behavior rather then using one flag for
many things.

That's would create a final set of flags to control the NAs relationship to the
SIs to.

-startinstances - Enable or disable the initial start of any SIs defined in
the domain.
-stopinstance - Enable or disable the shutdown of any SIs when shutting down
the NA.
-watchdog - Enable or disable the watchdoging of any SIs.

Feel free to contact me regarding any of my suggestions.



 Comments   
Comment by prasads [ 29/May/08 04:44 AM ]

marking as shark-na

Comment by Yamini K B [ 01/Jun/08 09:35 PM ]

Assigning to Kedar

Comment by jagadesh [ 06/Aug/08 11:31 AM ]

"This bug will be scrubbed and will be upgraded for next relevant milestone builds".

Comment by prasads [ 14/Aug/08 11:35 AM ]

Marking these issues as P2 again

Comment by Yamini K B [ 25/Sep/08 10:42 PM ]

Will not fix for this release.

Comment by ocorbun [ 05/Mar/09 01:07 AM ]

The NA will always watchdog its belonging server instances according to the
Enhanced GMS Failure Notification
(http://wiki.glassfish.java.net/PageInfo.jsp?page=SFv2FunctionalSpecs/gmsWatchdog.doc).

The "-watchdog" flag does not have the appropriate name. It is meant to not
restart the server instances in case of a problem. Use "-restartinstances" instead.

More information available:
http://wiki.glassfish.java.net/attach/SFv2FunctionalSpecs/SAF-integration.html

Comment by Yamini K B [ 26/Mar/09 07:35 AM ]
      • Issue 1677 has been marked as a duplicate of this issue. ***
Comment by srinik76 [ 14/Apr/09 01:43 AM ]

Checked in the fix.

Added an restartinstances flag to start-node-agent command to toggle the
watchdog of instances by node agent

Issue number: 919
Obtained from:
Submitted by:
Reviewed by: Nandini

Tests Run: Glassfish Cluster QL

Modified Files:

admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/BaseNodeAgent.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgentMain.java
admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/ProcessManager.java
admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/AgentManager.java
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/BaseNodeAgentCommand.java
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml
admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/StartNodeAgentCommand.java
admin-core/util/src/java/com/sun/enterprise/admin/util/IAdminConstants.java

===================================================================
File: BaseNodeAgent.java Status: Up-to-date

Working revision: 1.4.2.3
Repository revision: 1.4.2.3
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/BaseNodeAgent.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.4.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: NodeAgent.java Status: Up-to-date

Working revision: 1.28.2.5
Repository revision: 1.28.2.5
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgent.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.28.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: NodeAgentMain.java Status: Up-to-date

Working revision: 1.12.2.4
Repository revision: 1.12.2.4
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/NodeAgentMain.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.12.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: ProcessManager.java Status: Up-to-date

Working revision: 1.5.6.3
Repository revision: 1.5.6.3
/cvs/glassfish/admin-ee/nodeagent/src/java/com/sun/enterprise/ee/nodeagent/ProcessManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.5.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: AgentManager.java Status: Up-to-date

Working revision: 1.14.2.2
Repository revision: 1.14.2.2
/cvs/glassfish/admin-ee/servermgmt/src/java/com/sun/enterprise/ee/admin/servermgmt/AgentManager.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.14.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: BaseNodeAgentCommand.java Status: Up-to-date

Working revision: 1.5.6.2
Repository revision: 1.5.6.2
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/BaseNodeAgentCommand.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.5.6)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: CLIDescriptor.xml Status: Up-to-date

Working revision: 1.24.2.2
Repository revision: 1.24.2.2
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/CLIDescriptor.xml,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.24.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: StartNodeAgentCommand.java Status: Up-to-date

Working revision: 1.8.2.2
Repository revision: 1.8.2.2
/cvs/glassfish/admin-cli-ee/commands/src/java/com/sun/enterprise/ee/cli/commands/StartNodeAgentCommand.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.8.2)
Sticky Date: (none)
Sticky Options: (none)

===================================================================
File: IAdminConstants.java Status: Up-to-date

Working revision: 1.6.6.2
Repository revision: 1.6.6.2
/cvs/glassfish/admin-core/util/src/java/com/sun/enterprise/admin/util/IAdminConstants.java,v
Sticky Tag: SJSAS91_FCS_BRANCH (branch: 1.6.6)
Sticky Date: (none)
Sticky Options: (none)

Comment by srinik76 [ 15/Apr/09 02:23 AM ]

This needs to be documented. Assigning to docs team

Comment by srinik76 [ 15/Apr/09 03:31 AM ]

Added an option restartinstances to start-node-agent. Default value is true. If
it is set to false then nodeagent will not restart the instances when the
instance is killed.

Usage: start-node-agent [--terse=false] [--echo=false] [--interactive=true]
[--user admin_user] [--passwordfile file_name] [--agentdir nodeagent_path]
[--startinstances=true] [--restartinstances=true] [--syncinstances=false]
[--monitorinterval=5] [--verbose=false] [nodeagent_name]

This needs to be documented in glassfish also.

Comment by chinmayee_srivathsa [ 03/Sep/09 01:56 AM ]

Documented in the start-node-agent man page for sailfin. For GF 2.1.1, this new
option will be documented in the Reference Manual on docs.sun.com

Comment by chinmayee_srivathsa [ 05/Oct/09 11:58 PM ]

Created an attachment (id=1129)
sailfin ref man

Comment by chinmayee_srivathsa [ 06/Oct/09 12:12 AM ]

Fixed.





[SAILFIN-789] [Online doc] [RN] JDK from -javahome was not presented in asenv.conf Created: 04/Apr/08  Updated: 30/Jun/08  Resolved: 30/Jun/08

Status: Resolved
Project: sailfin
Component/s: build_system
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: easarina Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 789
Tags:
Participants: chinmayee_srivathsa, cs194067, easarina, naman_mehta and prasads

 Description   

Sailfin 0.5 b03. I've installed this build using -javahome option, pointing to
the preinstalled JDK. But after the installation I found that in asenv.conf
AS_JAVA still pointed to <Sailfin _install_dir>/jdk. I believe that AS_JAVA
from asenv.conf has to point to the jdk that was used during the installation as
javahome.



 Comments   
Comment by prasads [ 07/Apr/08 09:14 AM ]

Moving these issues to STARTE state

Comment by naman_mehta [ 08/Apr/08 03:17 AM ]

When you install any glassfish or sailfin installer we need JAVA_HOME to be set
in your system.

If there is not JAVA_HOME set in your system installation fails by giving below
error:
Checking available disk space...
Checking Java(TM) 2 Runtime Environment...
Extracting Java(TM) 2 Runtime Environment files...
Error: Could not find the required version of the Java(TM) 2 Runtime Environment.
This application needs version 1.5 or higher of the Java(TM) 2 Runtime
Environment. If the required Java(TM) 2 Runtime Environment is not installed,
you can download it from the following website:
http://java.sun.com/j2se
Or if you already have the required Java(TM) 2 Runtime Environment
installed, try rerunning this application with the following usage:
'sjsas-9_1_1-fcs-bin-b29-linux-06_apr_2008.bin' -javahome <Java(TM)
installation directory>

Now if you pass -javahome option here installation starts without any error.

So -javahome has the significant for JAVA_HOME in your system. It is not used to
set AS_JAVA property in asenv.conf file.

Also sailfin installer needs specific version of java and it is alreday bundled
with installer so AS_JAVA is alway going to point that directory.

Comment by easarina [ 08/Apr/08 11:21 AM ]

The users may want to use not default bundled jdk 1.5, but, for example, jdk
1.6. In this case they can use -javahome option and they can expect that AS will
use this jdk. Otherwise I believe that we need to document somewhere that jdk
from -javahome will be used only by installer. But AS by itself will always use
jdk 1.5 from <sailfin_install_dir>/jdk. And if they want to use jdk 1.6 they
need manually to put the path to jdk 1.6 in asenv.conf.
It looks reasonable that 1.6 will be used. At least the testing of Sailfin was
done with 1.6 jdk.

Comment by naman_mehta [ 13/May/08 02:22 AM ]

I already started looking into this. Trying to make JDK 1.6 bundle as part of
installer.

Comment by naman_mehta [ 15/May/08 03:04 AM ]

Hi rajeev,
We need to document below details as part of Release note.

SailFin installer is alway coming with JDK Bundle. When user installs SailFin,
it uses bundled JDK so AS_JAVA always points to <Sailfin _install_dir>/jdk.

If user wants to use different JDK then they need to update asenv.conf file
manually and changed value for AS_JAVA.

Comment by prasads [ 22/May/08 10:17 PM ]

Marking it for being release noted

Comment by cs194067 [ 26/May/08 02:48 AM ]

Does not affect bundled documentation. Issue will be documented in the Release
Notes.

Comment by cs194067 [ 17/Jun/08 10:40 PM ]

Fixed in the Release Notes:

http://sailfin.dev.java.net/documentation/documents/SJSASEERN.pdf

Comment by chinmayee_srivathsa [ 30/Jun/08 12:57 AM ]

Fixed





[SAILFIN-677] No CLI command/option to unset a DCR file. Created: 07/Mar/08  Updated: 19/Aug/08  Resolved: 19/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sonymanuel Assignee: irfanahmed
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 677
Tags:
Participants: chinmayee_srivathsa, irfanahmed, sonymanuel and srinik76

 Description   

Once dcr file is set for CLB (either while creating or using set-dcr-file) there
is no way to remove/unset it. If we want to go back to default CLB settings we
need to delete and create CLB.



 Comments   
Comment by srinik76 [ 11/Mar/08 03:08 AM ]

Reassigning to myself

Comment by srinik76 [ 11/Mar/08 03:10 AM ]

Unsetting the dcr file includes the following to be done.

1. Set dcr file name to empty string in converged-lb-policy element of
particular clb config
2. Delete the dcr file from the cluster config directory

The above can be done using the following CLI command

set-dcr-file --reset

Comment by srinik76 [ 24/Mar/08 12:35 AM ]

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java,v
<-- ConvergedLbConfigsMBean.javanew revision: 1.21; previous revision: 1.20
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.23; previous revision: 1.22
done
Checking in build.xml;
/cvs/sailfin/administration/build.xml,v <-- build.xml
new revision: 1.27; previous revision: 1.26
done

New command (unset-dcr-file <clbname>) to unset the dcr file
Issue number: 677
Obtained from:
Submitted by:
Reviewed by: Yamini

Tests Run: Sailfin Cluster QL

Modified Files:

src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java

src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
build.xml

bash-3.00# cvs diff -u
src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
build.xml | more
Index:
src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java
===================================================================
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java,v
retrieving revision 1.20
diff -u -r1.20 ConvergedLbConfigsMBean.java

src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java
20 Mar 2008 06:21:30 -0000 1.20
+++
src/main/java/org/jvnet/glassfish/comms/admin/mbeans/extensions/ConvergedLbConfigsMBean.java
24 Mar 2008 07:27:22 -0000
@@ -1015,4 +1015,55 @@
}
return clbConfigUsed;
}
+
+ public void unsetDcrFile(String clbName) throws MBeanException {
+ try {
+ ConfigContext ctx = AdminService.getAdminService().getAdminContext()
+ .getAdminConfigContext();
+ Domain domain = (Domain) ctx.getRootConfigBean();
+ Configs configs = domain.getConfigs();
+
+ String clbCfgName = null;
+ String cfgName = null;
+ // check if provided clbName is valid
+ if (configs != null) {
+ boolean found = false;
+ Config[] configArray = configs.getConfig();
+ for (int i = 0, j = 0; i < configArray.length; i++) {
+ AvailabilityService avSvc =
configArray[i].getAvailabilityService();
+ if (avSvc != null) {
+ ConvergedLoadBalancer clb =
configArray[i].getAvailabilityService()
+
.getConvergedLoadBalancer();
+
+ if (clb != null && clb.getName().equals(clbName)) { + // get the clb config name and config name + clbCfgName = clb.getConvergedLbConfigName(); + cfgName = configArray[i].getName(); + found = true; + break; + }
+ }
+ }
+ if (!found) { + String msg = _strMgr.getString("ClbNameDoesNotExist"); + throw new MBeanException(new ConfigException(msg)); + }
+ }
+ ConvergedLbConfig lbCfg = getConvergedLbConfig(clbCfgName);
+ ConvergedLbPolicy clbLbPolicy = lbCfg.getConvergedLbPolicy();
+ String dcrFileName = clbLbPolicy.getDcrFile();
+ // Before unsetting dcr file delete the physical file
+ String iRoot =
System.getProperty(SystemPropertyConstants.INSTANCE_ROOT_PROPERTY);
+ String dcrFilePath = iRoot + File.separator + PEFileLayout.CONFIG_DIR
+ + File.separator + cfgName +
File.separator + dcrFileName;
+ File dcrFile = new File(dcrFilePath);
+ if (dcrFile.exists())
+ dcrFile.delete();
+ //setting dcr file to empty string
+ clbLbPolicy.setDcrFile("");
+ } catch (ConfigException ce) { + throw new MBeanException(ce); + }
+ }
+
}
\ No newline at end of file
Index:
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
===================================================================
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
retrieving revision 1.22
diff -u -r1.22 CLIDescriptor.xml

src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
19 Mar 2008 06:43:04 -0000 1.22
+++
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
24 Mar 2008 07:27:22 -0000
@@ -691,6 +691,33 @@
</property>
</properties>
</Command>
+ <Command name="unset-dcr-file"
classname="com.sun.enterprise.cli.commands.GenericCommand" numberofoperands="1"
usage-text="unset-dcr-file [--terse=false] [--echo=false] [--interactive=true]
[--host localhost] [--port 4848] [--secure|-s=true] [--user admin_user]
[--passwordfile file_name] load_balancer_name">
+ <ValidOption name="terse"/>
+ <ValidOption name="user"/>
+ <ValidOption name="password"/>
+ <ValidOption name="passwordfile"/>
+ <ValidOption name="host"/>
+ <ValidOption name="port"/>
+ <ValidOption name="secure"/>
+ <ValidOption name="interactive"/>
+ <properties>
+ <property name="objectname">
+
<value>com.sun.appserv:type=converged-lb-configs,category=config</value>
+ </property>
+ <property name="operation">
+ <value>unsetDcrFile</value>
+ </property>
+ <property name="params">
+ <value>{#1}</value>
+ </property>
+ <property name="paramtypes">
+ <value>java.lang.String</value>
+ </property>
+ <property name="returntype">
+ <value>java.lang.Void</value>
+ </property>
+ </properties>
+ </Command>
<Command name="create-ssl"
classname="com.sun.enterprise.cli.commands.SSLCommand" numberofoperands="?"
usage-text="create-ssl --type
[http-listener|sip-listener|iiop-listener|iiop-service] --certname cert_name
[--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port
4848] [--secure |
-s] [--user admin_user] [--passwordfile file_name] [--ssl2enabled=false]
[--ssl2ciphers ssl2ciphers] [--ssl3enabled=true] [--ssl3tlsciphers
ssl3tlsciphers] [--tlsenabled=true] [--tlsrollbackenabled=true]
[--clientauthenabled=false] [--target target(Default server)] [listener_id]">
<RequiredOption name="type"/>
<RequiredOption name="certname"/>
Index: build.xml
===================================================================
RCS file: /cvs/sailfin/administration/build.xml,v
retrieving revision 1.26
diff -u -r1.26 build.xml
— build.xml 12 Mar 2008 08:35:47 -0000 1.26
+++ build.xml 24 Mar 2008 07:27:22 -0000
@@ -216,7 +216,7 @@
</java>
<!-- package ONLY SailFin commands -->
<delete>

  • <fileset dir="${cli_serialize.dir}/cli" defaultexcludes="false"
    excludes=".create-sip-listener, .delete-sip-listener, .list-sip-listeners,
    .create-converged-lb-config, .delete-converged-lb-config,
    .list-converged-lb-configs, .create-converged-lb-ref, .delete-converged-lb-ref,
    .create-converged-lb, .delete-converged-lb, .list-converged-lbs,
    .create-trust-config, .delete-trust-config, .list-trust-configs,
    .create-trusted-entity, .delete-trusted-entity, .set-dcr-file, .create-ssl,
    .delete-ssl"/>
    + <fileset dir="${cli_serialize.dir}/cli" defaultexcludes="false"
    excludes=".create-sip-listener, .delete-sip-listener, .list-sip-listeners,
    .create-converged-lb-config, .delete-converged-lb-config,
    .list-converged-lb-configs, .create-converged-lb-ref, .delete-converged-lb-ref,
    .create-converged-lb, .delete-converged-lb, .list-converged-lbs,
    .create-trust-config, .delete-trust-config, .list-trust-configs,
    .create-trusted-entity, .delete-trusted-entity, .set-dcr-file, .unset-dcr-file,
    .create-ssl, .delete-ssl"/>
    </delete>
    </target>

Reassigning the bug to Irfan as this needs changes in GUI so that GUI also
supports unsetting the dcr file.

Comment by irfanahmed [ 27/Mar/08 04:35 AM ]

started

Comment by srinik76 [ 02/Apr/08 10:42 PM ]

Added Rajeev in the CC, it needs documentation to be added to this bug

Comment by irfanahmed [ 03/Apr/08 02:23 AM ]

The following changes have been checked in:
Issue number: 677
Reviewed by: irfanahmed
Tests Run: SF QL Tests
Synopsis: No CLI command/option to unset a DCR file.
----------------------------------------------------------------------
Modified Files:
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/CLBHandlers.java
....calling CLBHelper.unsetDCRFile to unset the DCR file.
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/util/CLBHelper.java
....added a utility function to call the backend MBean function unsetDcrFile to
unset the DCR file.
----------------------------------------------------------------------

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/CLBHandlers.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/handlers/CLBHandlers.java,v
<-- CLBHandlers.java
new revision: 1.10; previous revision: 1.9
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/util/CLBHelper.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/gui/extensions/util/CLBHelper.java,v
<-- CLBHelper.java
new revision: 1.13; previous revision: 1.12
done

Comment by chinmayee_srivathsa [ 19/Aug/08 11:31 PM ]

unset-dcr-file manpage created at:
http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf





[SAILFIN-637] [online docs] Docs need to be updated with recommended values for sip-service attributes Created: 29/Feb/08  Updated: 19/Dec/08  Resolved: 19/Dec/08

Status: Resolved
Project: sailfin
Component/s: sip_container
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: rampsarathy Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 637
Tags:
Participants: chinmayee_srivathsa, prasads, rampsarathy, Rebecca Parks and rj139419

 Description   

This issue (docs) is created to track the documentation of the following
attrbutes in domain.xml, the docs should include recommeded values (min and
max) so that the users dont provide in-appropriate values for these

sip-service.request-processing
    thread-count
    initial-thread-count
    thread-increment
    request-timeout-in-seconds
    header-buffer-length-in-bytes
sip-service.keep-alive
    thread-count
    max-connections
    * timeout-in-seconds
sip-service.connection-pool
    queue-size-in-bytes
    max-pending-count
    receive-buffer-size-in-bytes
    send-buffer-size-in-bytes

sip-service.sip-protocol.sip-link
    connection-alive-timeout-in-seconds
    max-queue-length
    write-timeout-in-millis
    write-timeout-retries



 Comments   
Comment by rj139419 [ 13/Mar/08 05:09 AM ]

Need the min and max values to update the online help pages for SIP Service
screens in the Admin Console.

Comment by rampsarathy [ 18/Jun/08 11:54 PM ]

reassign to chinmayee

Comment by chinmayee_srivathsa [ 30/Jun/08 09:50 PM ]

Will fix in the Admin guide and Admin reference for 1.0.

Will include fixes in the Admin Console for 1.5

Comment by chinmayee_srivathsa [ 05/Aug/08 03:53 AM ]

cing June because it affects the Admin Reference also.

Comment by prasads [ 14/Aug/08 11:38 AM ]

Marking all of them as P3

Comment by prasads [ 14/Aug/08 11:42 AM ]

Restoring them to P4

Comment by chinmayee_srivathsa [ 13/Oct/08 02:15 AM ]
      • Issue 1071 has been marked as a duplicate of this issue. ***
Comment by chinmayee_srivathsa [ 30/Oct/08 09:15 PM ]

This bug does not affect bundled docs.
This will be fixed in the Admin guide and Admin reference for 1.5.

Comment by Rebecca Parks [ 03/Dec/08 01:38 PM ]

The doc team can't fix this unless Engineering supplies the needed min and max
values. We cannot read code, or minds. Reassigning to the original reporter
because there is no way to mark this bug "incomplete."

Comment by rampsarathy [ 15/Dec/08 08:35 AM ]

thread-count - default is 10, and is sufficient for most of the scenarios

initial-thread-count - 10, all threads are created upfront so that delay
during request processing is less, should always be less than or equal to
thread-count. If load is low , then set it to a lesser values (half of thread-count)

thread-increment - should be greater than 1 if thread count is configured to
be a higher value (> 10)

request-timeout-in-seconds : duration for which the read operation on the
channel waits before timing out , 30 seconds is default. Depends on the network
and use cases

header-buffer-length-in-bytes : 8192 bytes, depends on the sip message
header size

sip-service.keep-alive
thread-count - not implemented
max-connections - not implemented

  • timeout-in-seconds - default is that the socket channel is always kept
    alive... -1 to max int values are allowed

queue-size-in-bytes - number of messages that can be queued after being
read from the socket channel, default queue size is unlimited, can take -1 to
max int values,.

max-pending-count not implemented

receive-buffer-size-in-bytes - the size of the byte buffer that will be
used to read from the socket channel, by defualt this will be tuned to the
socket channel receive buffer size, can take -1 to max int value.

send-buffer-size-in-bytes
maximium size of the sip message that can be written out from Sailfin, default
is 8192, should be configured based on the deployment environment.

sip-service.sip-protocol.sip-link
connection-alive-timeout-in-seconds not implemented
max-queue-length not implemented
write-timeout-in-millis not implemented
write-timeout-retries not implemented

Comment by Rebecca Parks [ 15/Dec/08 03:48 PM ]

Many of these defaults are different from existing values. Are the values
different depending on whether the parent element is http-service or sip-service?

Also, it appears that all sip-link attributes are not implemented, implying that
the entire element is not implemented. Since sip-link is an optional element,
should I just remove it?

Comment by rampsarathy [ 15/Dec/08 08:39 PM ]

All these are sip properties,
when i say default, i mean the values that are present when a domain is created,
they may be taken from the dtd or can be overridden in the domain template for
SailFin. These are the values that a user would see when he creates a domain.

since sip-link is present in the default domain.xml, it would be better if we
said not implemented currently, will be used in future. If we remove this from
documentation users might wonder what this is used for since its present in
domain.xml

Comment by Rebecca Parks [ 16/Dec/08 08:38 AM ]

My question remains unanswered. Are the default values different depending on
whether the parent element is http-service or sip-service?

Comment by rampsarathy [ 16/Dec/08 08:36 PM ]

yes, the default values are different for these attributes for the http-service
and the sip-service.
And i have explained their (attributes under sip-service) usage which could
also be different from the way the same attributes under http-service are used.

This issue is only to track attributes under sip-service, and what is being
explained is also for the same.

Comment by Rebecca Parks [ 19/Dec/08 12:56 PM ]

The info is in the doc, and now perfecting it becomes part of the normal review
process.





[SAILFIN-577] create-converged-lb command required parameters should come in first Created: 19/Feb/08  Updated: 06/Aug/08  Resolved: 06/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sankarpn Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 577
Tags:
Participants: chinmayee_srivathsa, sankarpn, srinik76, swethadn and Yamini K B

 Description   

asadmin create-converged-lb --target server
Usage: create-converged-lb [--clbconfig clbconfig] [--dcrfile file_name]
[--httplbpolicy policy] [--siplbpolicy policy] [--lbtarget lbtarget]
[--selfloadbalance] [--lbenableallinstances] --configfile file_name
[--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port
4848] [--secure|-s=true] [--user admin_user] [--passwordfile file_name]
[--property (name=value)[:name=value]*] [--autocommit] --target target
load_balancer_name
CLI014 configfile is a required option.

In the above command usage the --configfile option is in between the optional
and meta options. The CLI convention is to have the the required parameter to
come in first as opposed to the optional parameters.



 Comments   
Comment by srinik76 [ 19/Feb/08 10:48 PM ]

create-converged-lb CLI command usage needs to be changed to have required
options in the first

Comment by Yamini K B [ 11/Mar/08 10:01 PM ]

Reassigning to Swetha

Comment by swethadn [ 23/Mar/08 11:24 PM ]

CLIDescriptor.xml requires changes.
The required parameters are put first for create-converged-lb command.

Comment by swethadn [ 26/Mar/08 08:59 PM ]

required parameters config file and target are put first in create-converged-lb
command.

Issue number: 577
Obtained from:
Submitted by:
Reviewed by: Srini
Tests Run: Sailfin Cluster QL

Checking in CLIDescriptor.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
done

Comment by chinmayee_srivathsa [ 06/Aug/08 09:13 AM ]

re-opening the issue for docs fix

Comment by chinmayee_srivathsa [ 06/Aug/08 09:14 AM ]

re-assigning to myself

Comment by chinmayee_srivathsa [ 06/Aug/08 09:16 AM ]

Fixed at:

http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf





[SAILFIN-538] Usage options in CLI CLB commands needs to be corrected Created: 12/Feb/08  Updated: 19/Aug/08  Resolved: 19/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: srinik76 Assignee: srinik76
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 538
Tags:
Participants: chinmayee_srivathsa and srinik76

 Description   

Usage options in CLB cli commands needs to be corrected. The option
--lbenableallapplications is not a valid option in CLB commands and needs to be
removed from all CLB cli commands.



 Comments   
Comment by srinik76 [ 13/Feb/08 02:32 AM ]

Raisin the priority to P2 as it needs to be addressed before Beta

Comment by srinik76 [ 13/Feb/08 03:16 AM ]

In delete-converged-lb command, the target contains default server in option
this needs to be deleted as this is not supported.

Comment by srinik76 [ 13/Feb/08 03:34 AM ]

For benefit of capturing the changes, lowering the priroity of this bug to P3
and creating another bug with priority P2 which will keep track of cli usage
changes required for Beta.

Comment by srinik76 [ 13/Feb/08 04:03 AM ]

This needs to be addressed after beta

Comment by srinik76 [ 17/Mar/08 02:52 AM ]

As part of the fix for Issue 352, delete-converged-lb now takes
load-balancer-name as target which was earlier taking target as input. Now the
target option does not exist for delete-converged-lb command.

Comment by chinmayee_srivathsa [ 19/Aug/08 11:29 PM ]

This change is documented in the delete-converged-lb man page
at:http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf





[SAILFIN-511] Data Centric DTD missing in Sailfin Created: 07/Feb/08  Updated: 13/Oct/08  Resolved: 13/Oct/08

Status: Resolved
Project: sailfin
Component/s: load_balancer
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: ehsroha Assignee: srinik76
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: Text File dcr-1.0.dtd    
Issuezilla Id: 511
Tags:
Participants: chinmayee_srivathsa, ehsroha, joelbinn, pj126383, Satish Kumar and srinik76

 Description   

In the FSD, ConvergedLB-FSD, the following DTD is described but missing in
Sailfin. Verify with the source code that the DTD is correct otherwise update DTD.

2.4.1.3.1 Data Centric Rule DTD
<?xml version="1.0" encoding="UTF-8"?>
<!-- DTD for Data Centric Rules, DCR -->
<!ELEMENT user-centric-rules (sip-rules,http-rules)>
<!ELEMENT sip-rules (operator-condition)*>
<!ELEMENT http-rules (operator-condition)*>
<!ELEMENT operator-condition (operator|condition)>
<!ELEMENT operator (or|and|if)>
<!ELEMENT condition (header|request-uri|session-case|cookie) >
<!ELEMENT or (operator-condition)*>
<!ELEMENT and (operator-condition)*>
<!ELEMENT if (operator-condition,else?)*>
<!ELEMENT else EMPTY>
<!ATTLIST else return NMTOKEN #REQUIRED>
<!ELEMENT header (exist|notexist)>
<!ATTLIST header
name NMTOKEN #REQUIRED
return NMTOKEN #REQUIRED >
<!ELEMENT request-uri (exist|notexist|match)>
<!ATTLIST request-uri
parameter NMTOKEN #IMPLIED
return NMTOKEN #IMPLIED >
<!ELEMENT session-case (equal,session-case-type)>
<!ELEMENT session-case-type (INTERNAL|EXTERNAL|ORIGINATING|TERMINATING|
TERMINATING_UNREGISTERED) >
<!ELEMENT cookie (exist|notexist)>
<!ATTLIST cookie
name NMTOKEN #REQUIRED
return NMTOKEN #REQUIRED>
<!ELEMENT equal (#PCDATA)>
<!ELEMENT exist EMPTY>
<!ELEMENT notexist EMPTY>
<!ELEMENT match (#PCDATA)>

Not needed for Beta!



 Comments   
Comment by pj126383 [ 07/Feb/08 11:49 PM ]

Satish check with Joel as you proceed with the check-in of the DTD

Comment by Satish Kumar [ 20/Feb/08 05:58 AM ]

Communicating with Joel for inputs on this.

Comment by Satish Kumar [ 09/Apr/08 03:29 AM ]

The DCR DTD in the FS does not correspond to what has actually been
implemented. Reassigning this bug to Joel to change the implementation to be in
sync with the DTD.

Comment by joelbinn [ 10/Apr/08 07:17 AM ]

Just a comment: it is the other way around, the DTD shall be modified to
correspond to the implementation.

This is not a critical issue and I discussed this with Time and he suggested it
to be re-prioritized to P4.

Comment by joelbinn [ 17/Apr/08 08:33 AM ]

Created an attachment (id=410)
Corrected DTD for DCR.

Comment by joelbinn [ 17/Apr/08 08:54 AM ]

I have attached a corrected DTD. However, I am not sure how it should be
integrated in Sailfin. Maybe you can help me with that.

Once it is included we need to change the DcrConfigurableHashKeyExtractor to
validate the XML when it parses it.

Comment by pj126383 [ 18/Apr/08 06:05 AM ]

Satish, you can now proceed with integrating / check-in this. It would also
require the installer/packager to ensure that this resource is made available
under lib/dtds.

Regarding validation, clb configurator / admin-runtime should take care of this
as part of (a) CLB start-up and (b) upload of newer DCR file via CLI; when a DCR
update event is received.

Comment by Satish Kumar [ 28/Apr/08 03:47 AM ]

Added the sun-data-centric-rule_1_0.dtd to CVS... Reassigining the issue to
Srini to add validation support in the Admin infra.

Comment by srinik76 [ 02/May/08 03:56 AM ]

dcr xml needs to be validated with the DTD provided when the user provides it
using the set-dcr-file command.

Comment by srinik76 [ 07/May/08 12:31 AM ]

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java,v
<-- DCRCommand.java
new revision: 1.4; previous revision: 1.3
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties,v
<-- LocalStrings.properties
new revision: 1.3; previous revision: 1.2
done
Issue number: 511
Obtained from:
Submitted by:
Reviewed by: Yamini

Tests Run: Sailfin QL and Cluster QL
Index:
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java
===================================================================
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java,v
retrieving revision 1.3
diff -u -r1.3 DCRCommand.java

src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java
19 Mar 2008 06:43:05 -0000 1.3
+++
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java
7 May 2008 07:25:41 -0000
@@ -28,19 +28,21 @@
import com.sun.enterprise.cli.commands.*;
import com.sun.enterprise.admin.common.JMXFileTransfer;
import javax.management.MBeanServerConnection;
-import com.sun.enterprise.config.ConfigException;
-import com.sun.appserv.management.client.ProxyFactory;
-import com.sun.appserv.management.DomainRoot;
-import com.sun.appserv.management.config.WebServiceEndpointConfig;
-import com.sun.appserv.management.base.UploadDownloadMgr;
+import com.sun.enterprise.util.SystemPropertyConstants;
import javax.management.ObjectName;
-import java.util.Iterator;
import java.util.Vector;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;

-import java.io.FileNotFoundException;
+import javax.xml.parsers.DocumentBuilder;
+import javax.xml.parsers.DocumentBuilderFactory;
+import org.w3c.dom.Document;
+import org.xml.sax.EntityResolver;
+import org.xml.sax.InputSource;
+import org.xml.sax.SAXException;
+import org.xml.sax.SAXParseException;
+import org.xml.sax.helpers.DefaultHandler;

public class DCRCommand extends S1ASCommand
{
@@ -88,15 +90,58 @@
File file = new File(dcrFileLocation);
if (!file.exists()) { String msg = getLocalizedString("InvalidDcrFile"); - throw new IOException(msg); + throw new CommandException(msg); } else if (file.isDirectory()) { String msg = getLocalizedString("DcrFileIsDirectory"); - throw new IOException(msg); + throw new CommandException(msg); } else if (file.length() == 0) { String msg = getLocalizedString("EmptyDcrFile"); - throw new IOException(msg); + throw new CommandException(msg); }
+ try { + validateDCR(file); + } catch (Exception e) { + String msg = getLocalizedString("InvalidDcrDTDCheck"); + throw new CommandException(msg + " " + e.getMessage()); + }

return new JMXFileTransfer(mbsc).uploadFile(dcrFileLocation, "config");
}
-}
+
+ private void validateDCR(File dcrFile) throws Exception { + FileInputStream in = new FileInputStream(dcrFile); + + DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance(); + dbf.setValidating(true); + + DocumentBuilder db = dbf.newDocumentBuilder(); + db.setErrorHandler(new ErrorHandler()); + db.setEntityResolver(new ErrorHandler()); + + Document doc = db.parse(in); + }
+
+ class ErrorHandler extends DefaultHandler {
+
+ public InputSource resolveEntity(String publicId, String systemId)
+ throws SAXException, IOException { + + final String DCR_DTD_FILE = "lib" + File.separator + "dtds" + + File.separator + "sun-data-centric-rule_1_0.dtd"; + + String installDir = System.getProperty(SystemPropertyConstants.INSTALL_ROOT_PROPERTY); + String customSystemId = installDir + File.separator + DCR_DTD_FILE; + InputSource is = new InputSource(new FileInputStream(new File(customSystemId))); + return is; + }
+
+ public void error(SAXParseException e) throws SAXException { + throw new SAXException(e.getMessage()); + }
+
+ public void fatalError(SAXParseException e) throws SAXException {+ throw new SAXException(e.getMessage());+ } }
+
+ }
+}
\ No newline at end of file
Index:
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties
===================================================================
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties,v
retrieving revision 1.2
diff -u -r1.2 LocalStrings.properties

src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties
18 Mar 2008 06:38:55 -0000 1.2
+++
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties
7 May 2008 07:25:41 -0000
@@ -1,4 +1,4 @@
InvalidDcrFile=DCR file does not exist.
EmptyDcrFile=DCR file provided is empty. Please specify a valid file.
DcrFileIsDirectory=DCR file provided is a directory. Please specify a valid file.
-
+InvalidDcrDTDCheck=DCR file provided is not valid.

Comment by chinmayee_srivathsa [ 13/Oct/08 02:41 AM ]

This DTD file is documented in the High-availability Admin guide. See page 36 at
http://sailfin.dev.java.net/documentation/documents/SJSASEEHAAG.pdf





[SAILFIN-493] no --terse option in usage text of create-converged-lb-ref Created: 04/Feb/08  Updated: 04/Aug/08  Resolved: 04/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sankarpn Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 493
Tags:
Participants: chinmayee_srivathsa, sankarpn, srinik76, swethadn and Yamini K B

 Description   

asadmin create-converged-lb-ref
Usage: create-converged-lb-ref --clbconfig config_name [--echo=false]
[--interactive=true] [--host localhost] [--port 4848] [--secure|-s=true] [--user
admin_user] [--passwordfile file_name] [--selfloadbalance]
[--lbenableallapplications] [--lbenableallinstances] target
CLI020 Operand is required.



 Comments   
Comment by Yamini K B [ 05/Feb/08 01:42 AM ]

descriptor needs to be fixed

Comment by srinik76 [ 07/Feb/08 11:46 PM ]

CLI descriptor needs to be changed

Comment by Yamini K B [ 11/Mar/08 10:00 PM ]

transferring the issue to swetha

Comment by swethadn [ 18/Mar/08 12:06 AM ]

Index: CLIDescriptor.xml
===================================================================
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
retrieving revision 1.20
diff -u -r1.20 CLIDescriptor.xml
— CLIDescriptor.xml 18 Mar 2008 06:21:59 -0000 1.20
+++ CLIDescriptor.xml 18 Mar 2008 06:58:09 -0000
@@ -274,7 +274,7 @@
</property>
</properties>
</Command>

  • <Command name="create-converged-lb-ref"
    classname="com.sun.enterprise.cli.commands.GenericCommand" numberofoperands="1"
    usage-text="create-converged-lb-ref --clbconfig config_name | --clbname lb_name
    [--echo=false] [--interactive=true] [--host localhost] [--port 4848]
    [--secure|-s=true] [--user admin_user] [--passwordfile file_name]
    [--selfloadbalance=true] [--lbenableallinstances=false] target">
    + <Command name="create-converged-lb-ref"
    classname="com.sun.enterprise.cli.commands.GenericCommand" numberofoperands="1"
    usage-text="create-converged-lb-ref --clbconfig config_name | --clbname lb_name
    [--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port
    4848] [--secure|-s=true] [--user admin_user] [--passwordfile file_name]
    [--selfloadbalance=true] [--lbenableallinstances=false] target">
    <ValidOption name="clbconfig"/>
    <ValidOption name="clbname"/>
    <ValidOption name="selfloadbalance"/>
    added --terse option to create-converge-lb-ref

Issue number: 493
Obtained from:
Submitted by:
Reviewed by: Srini
Tests Run: Sailfin Cluster QL

Checking in CLIDescriptor.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.21; previous revision: 1.20
done

Comment by chinmayee_srivathsa [ 04/Aug/08 08:44 PM ]

reopening for docs fix.

Comment by chinmayee_srivathsa [ 04/Aug/08 08:44 PM ]

reassigning to myself

Comment by chinmayee_srivathsa [ 04/Aug/08 08:45 PM ]

Fixed in the reference manual at:
http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf

See create-converged-lb-ref man page





[SAILFIN-457] for developer profile extenal-sip-port and external-sips-port don't follow the (default) sip-listener config by default Created: 29/Jan/08  Updated: 05/Aug/08  Resolved: 05/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Improvement Priority: Major
Reporter: eltjoboersma Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


File Attachments: HTML File RE Error when changing listener ports.htm    
Issuezilla Id: 457
Tags:
Participants: chinmayee_srivathsa, eltjoboersma, srinik76 and Yamini K B

 Description   

For developer profile extenal-sip-port and external-sips-port don't follow the
(default) sip-listener config by default.

The developer profile is expected to be a single server instance solution
without a NAT or proxy involved. Therefore expected behaviour of the external-
sip-port and external-sips-port attributes defaults on the sip-container is to
follow the default sip-listeners settings (even when they are changed.
E.g.: A developer wants to set the port for udp_tcp to 5070 for the default sip-
listener-1 the extenal-sip-port should follow suit and use the 5070 port aswell.

Note that in a production setting the external-sip-port and external-sips-port
will most likely be set explicitly to the external visible port (at the ip-
sprayer i.e.) and will not need to follow the sip-listener port!

In addition the extenal-address when omitted currently defaults to an IP
address that is determined by a heuristic. Some concerns about the heuristic
exist as described in the mail discussion attached. These could be solved under
this issue aswell, but might be a seperate issue.

P2 as agreed with Binod, because of usability and frequent questions on the
devlist.



 Comments   
Comment by eltjoboersma [ 29/Jan/08 07:30 AM ]

Created an attachment (id=167)
Discussion on problem and proposal for heuristics update

Comment by eltjoboersma [ 29/Jan/08 07:32 AM ]

It is an enhancement, the only defect is that the usability is harmed for the
developer profile. Setting the ports explicitly can be done as work around.

Comment by Yamini K B [ 03/Feb/08 07:51 PM ]

Checking in src/main/resources/templates/developer/sipdomain.xml.xsl;
/cvs/sailfin/administration/src/main/resources/templates/developer/sipdomain.xml.xsl,v
<-- sipdomain.xml.xsl
new revision: 1.12; previous revision: 1.11
done

Partially addressed the issue by fixing the developer profile external ports.
The other part of the fix is to determine the external address/ports internally
if user hasn't specified these.

Lowering the priority (no longer a stopper since usability concern has been
addressed) and assigning to Eltjo.

Comment by Yamini K B [ 14/May/08 08:06 PM ]

Srini is working on this

Comment by srinik76 [ 19/May/08 02:27 AM ]

In the SipBindingResolver code, the resolving of external-address needs to be
resolved in the following ways as per Binod's comments:

  • If external-address is configured use that.
  • If external-address is not configured
    • Use the socket address of the incoming connection.
    • If the address configured in the listener is not 'loopback or local' use
      that as address.
    • If the address configured in the listener is ANY (0.0.0.0), then use the
      non-loopback
      network interface.
    • If the address configured in the listener is ANY and it is a multihome
      machine, then
      log a warning and pick up the first non-loopback address.
Comment by srinik76 [ 02/Jun/08 02:05 AM ]

Changed the heuristic in resolving the external address when it is not provided.

Checking in SipBindingResolver.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/ssa/container/SipBindingResolver.java,v
<-- SipBindingResolver.java
new revision: 1.14; previous revision: 1.13
done

Comment by srinik76 [ 05/Jun/08 03:24 AM ]

Revereted the changes as the fix to Prefer IPv6 over IPv4 is causing some tests
to fail on Mac OS.

Comment by srinik76 [ 08/Jun/08 11:07 PM ]

Some tests are failing in Mac

Comment by srinik76 [ 09/Jun/08 02:44 AM ]

The code is written for IPv4 address preferred over IPv6. But the test Mac
Machine resolves the IPv6 address. This needs to be investigated.

Comment by srinik76 [ 01/Jul/08 10:37 PM ]

Implemented the logic to resolve external sip address when it is not provided.

Checking in SipBindingResolver.java;
/cvs/sailfin/sip-stack/src/java/com/ericsson/ssa/container/SipBindingResolver.java,v
<-- SipBindingResolver.java
new revision: 1.16; previous revision: 1.15
done

Comment by srinik76 [ 04/Aug/08 03:16 AM ]

This bug needs to be released noted :

The SIP container has its own heuristic for determining external sip address
when not specified.

Comment by srinik76 [ 04/Aug/08 03:16 AM ]

This bug needs to be released noted :

The SIP container has its own heuristic for determining external sip address
when not specified.

Comment by srinik76 [ 04/Aug/08 03:18 AM ]

Assigning to docs team

Comment by chinmayee_srivathsa [ 05/Aug/08 03:52 AM ]

Fixed at:

https://sailfin.dev.java.net/documents_shark/SJSASEERN.pdf





[SAILFIN-372] asadmin command set-dcr-file usage is not consistent Created: 10/Jan/08  Updated: 19/Aug/08  Resolved: 19/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sonymanuel Assignee: srinik76
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 372
Tags:
Participants: chinmayee_srivathsa, sonymanuel, srinik76 and Yamini K B

 Description   

[root@eas-v20-8 sift]# asadmin set-dcr-file
Usage: set-dcr-file --dcrfile dcr_file_name [--echo=false] [--interactive=true]
[--host localhost] [--port 4848] [--secure|-s=true] [--user admin_user]
[--passwordfile file_name] clb_config_name
CLI014 dcrfile is a required option.

set-dcr-file seems to take the dcrfile as an option rather than the operand. I
think most asadmin commands follow this pattern

set-dcr-file --clbconfig <config-name> dcrfile



 Comments   
Comment by Yamini K B [ 25/Jan/08 01:28 AM ]

assigning to Srini

Comment by srinik76 [ 08/Feb/08 12:16 AM ]

Need to change the command format to accept dcrfile name as the operand

Comment by srinik76 [ 17/Mar/08 11:44 PM ]

Adding rajeev (docs) in CC. This bug fix also requires a document change.
set-dcr-file --dcrfile <file> clb-config-name is changed to the format
set-dcr-file --clbconfig <name> dcrfile

Comment by srinik76 [ 18/Mar/08 11:43 PM ]

set-dcr-file now gets operand as dcr file name
Issue number: 372
Obtained from:
Submitted by:
Reviewed by: yamini

Tests Run: Sailfin Cluster QL

Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.22; previous revision: 1.21
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java,v
<-- DCRCommand.java
new revision: 1.3; previous revision: 1.2
done

Index:
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
===================================================================
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
retrieving revision 1.21
diff -u -r1.21 CLIDescriptor.xml

src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
18 Mar 2008 07:03:52 -0000 1.21
+++
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml
19 Mar 2008 06:41:23 -0000
@@ -661,8 +661,7 @@
</property>
</properties>
</Command>

  • <Command name="set-dcr-file"
    classname="org.jvnet.glassfish.comms.admin.cli.extensions.commands.DCRCommand"
    numberofoperands="1" usage-text="set-dcr-file --dcrfile dcr_file_name
    [--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port
    4848] [--secure|-s=true] [--user admin_user] [--passwordfile file_name]
    clb_config_name">
  • <RequiredOption name="dcrfile"/>
    + <Command name="set-dcr-file"
    classname="org.jvnet.glassfish.comms.admin.cli.extensions.commands.DCRCommand"
    numberofoperands="1" usage-text="set-dcr-file --clbconfig clbconfig
    [--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port
    4848] [--secure|-s=true] [--user admin_user] [--passwordfile file_name]
    dcr_file_name">
    <ValidOption name="terse"/>
    <ValidOption name="user"/>
    <ValidOption name="password"/>
    @@ -671,6 +670,7 @@
    <ValidOption name="port"/>
    <ValidOption name="secure"/>
    <ValidOption name="interactive"/>
    + <ValidOption name="clbconfig"/>
    <properties>
    <property name="objectname">

<value>com.sun.appserv:type=converged-lb-configs,category=config</value>
@@ -679,8 +679,8 @@
<value>setDcrFile</value>
</property>
<property name="params">

  • <value>{$dcrfile}</value>
    <value>{#1}</value>
    + <value>{$clbconfig}</value>
    </property>
    <property name="paramtypes">
    <value>java.lang.String</value>
    Index:
    src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java
    ===================================================================
    RCS file:
    /cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java,v
    retrieving revision 1.2
    diff -u -r1.2 DCRCommand.java

    src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java
    18 Mar 2008 06:38:55 -0000 1.2
    +++
    src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/DCRCommand.java
    19 Mar 2008 06:41:23 -0000
    @@ -35,6 +35,7 @@
    import com.sun.appserv.management.base.UploadDownloadMgr;
    import javax.management.ObjectName;
    import java.util.Iterator;
    +import java.util.Vector;
    import java.io.File;
    import java.io.FileInputStream;
    import java.io.IOException;
    @@ -43,8 +44,6 @@

public class DCRCommand extends S1ASCommand
{

  • private static final String DCR_FILE_LOCATION = "dcrfile";
    -
    /**
  • An abstract method that Executes the command
  • @throws CommandException
    @@ -84,7 +83,8 @@
    private String uploadFileToServer(MBeanServerConnection mbsc)
    throws CommandException, IOException
    {
  • String dcrFileLocation = getOption(DCR_FILE_LOCATION);
    + Vector operands = getOperands();
    + String dcrFileLocation = (String) operands.get(0);
    File file = new File(dcrFileLocation);
    if (!file.exists()) {
    String msg = getLocalizedString("InvalidDcrFile");
Comment by chinmayee_srivathsa [ 19/Aug/08 11:17 PM ]

Fixed in the Reference manual
at:http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf





[SAILFIN-349] [doc] additional domainproperties undocumented Created: 03/Jan/08  Updated: 15/Dec/08  Resolved: 15/Dec/08

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone_3

Type: Bug Priority: Major
Reporter: vince kraemer Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 349
Tags: shark-na
Participants: chinmayee_srivathsa, km, prasads, Rebecca Parks, vince kraemer and Yamini K B

 Description   

The properties that allow the user to create a custom domain with non-default
SIP listeners are undocumented.

users that have multiple domains on a single/large server will need to be able
to customize these ports... and --domainproperties is the way to do it.



 Comments   
Comment by km [ 03/Jan/08 11:16 AM ]

admin issue. Not a defect per se. The port can be changed after the fact, which
I admit is suboptimal way of doing things.

Comment by km [ 03/Jan/08 11:17 AM ]

...

Comment by vince kraemer [ 06/Jan/08 09:20 PM ]

I don't understand your response. Documenting the names of the ports isn't an
enhancement... it is a defect in the documentation.

Are you implying that there aren't domainproperties that would allow the user to
create domains that do not have conflicting SIP ports?

What command/API would a user need to use to change these ports?

Comment by km [ 07/Jan/08 09:03 AM ]

You can definitely use set commands with proper dotted names for a particular
listener if you are to change its SIP port.

I still maintain that this is an enhancement because I think it is an extension
of existing mechanism for specifying ports at domain creation time.

If you feel strongly about this being a defect, please change it so.

Comment by vince kraemer [ 07/Jan/08 10:07 AM ]

What are the set commands that would need to be executed? What are the proper
dotted names for the two sip ports?

defect or enhancement doesn't matter. commitment to resolve... that matters.

Info about how to work-around the problems associated with:

create-domain testdomain1
create-domain testdomain2
start-domain testdomain1
start-domain testdomain2

for sailfin... that matters.

Comment by km [ 07/Jan/08 10:22 AM ]

It goes without saying that an open bug/RFE is a good enough commitment to fix it,
unless there is a change in priorities.

The dotted names of the listeners are not handy with me. You should probably
try: "asadmin list 'server.*' | grep -i sip" and see if something is revealed.
Let me know if this was useful.

Comment by vince kraemer [ 07/Jan/08 02:06 PM ]

asadmin get 'server.sip-service.sip-listener.sip-listener-1.port'

AND

asadmin get 'server.sip-service.sip-listener.sip-listener-2.port'

Comment by vince kraemer [ 08/Feb/08 03:30 PM ]

change back to defect so the doc update does not slip through the cracks

Comment by Yamini K B [ 25/Mar/08 09:30 PM ]

The following new domain properties have been introduced as part of issue 309
which needs to be documented:

sip.port - to specify SIP port
sip.ssl.port - to specify SIP ssl port

create-domain man page and the admin guide needs to be updated with this info.

Comment by Yamini K B [ 27/Mar/08 01:28 AM ]

assigning to Rajeev to fix the man pages and docs

Comment by prasads [ 07/Apr/08 09:14 AM ]

Moving these issues to STARTE state

Comment by prasads [ 19/May/08 09:57 PM ]

Marking these bugs as shark-na

Comment by Rebecca Parks [ 29/May/08 01:16 PM ]

In the Administration Reference, which documents the domain.xml file, there are
external-sip-port and external-sips-port attributes for the sip-container
element. I think these are the settings referred to in this issue. These
should probably be documented in the Administration Guide, online help, and man
pages as well.

Comment by chinmayee_srivathsa [ 15/Jun/08 10:34 PM ]

Will fix in the create-domain man page and in the admin guide and OLH.

Comment by Yamini K B [ 30/Jul/08 12:39 AM ]

changing the category

Comment by chinmayee_srivathsa [ 05/Aug/08 03:51 AM ]

Fixed at:

http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf





[SAILFIN-228] [online docs] start cluster and clb-creation-then-restart-cluster shows error messages on the command line Created: 05/Dec/07  Updated: 17/Jan/09  Resolved: 17/Jan/09

Status: Resolved
Project: sailfin
Component/s: doc
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Minor
Reporter: vr143562 Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


File Attachments: PDF File SJSASEETSG.pdf    
Issuezilla Id: 228
Status Whiteboard:

shark-na

Tags: sf10-fcs-approved
Participants: chinmayee_srivathsa, cs194067, jagadesh, prasads, rj139419, srinik76, vr143562 and Yamini K B

 Description   

Sailfin Build 11

Steps to reproduce the issue:

1. Install Build 11 as per instructions at
https://sailfin.dev.java.net/downloads/v1-b11.html using cluster mode (ant -f
setup-cluster.xml)
2. Create a domain, node-agents and a cluster of 3 instances.
3. Start the cluster. The following messages appear on the command line
(repeated for each instance). The messages are stated as errors but the actual
message marks them as warnings.
********
The clustered instance, instance1, was successfully started.
error 0
[#|2007-12-05T06:35:37.891+0530|WARNING|sun-appserver9.1|javax.enterprise.resource.resourceadapter|ThreadID=11;_ThreadName=main;_CallFlowPool;_RequestID=5b191a76-51d7-45bc-976a-cadb36e6c21c;|RAR5005:Error
in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]

error 1
[#|2007-12-05T06:35:40.164+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.sip|_ThreadID=12;_ThreadName=pool-1-thread-1;_RequestID=95249ce4-3e6f-4808-aee2-a77fafac7882;|"Sip
Module binding using any host: 0.0.0.0"|#]

error 2
[#|2007-12-05T06:35:40.994+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.sip|_ThreadID=12;_ThreadName=pool-1-thread-1;_RequestID=95249ce4-3e6f-4808-aee2-a77fafac7882;|Invalid
keyStore:null Using default.|#]

error 3
[#|2007-12-05T06:35:40.994+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.sip|_ThreadID=12;_ThreadName=pool-1-thread-1;_RequestID=95249ce4-3e6f-4808-aee2-a77fafac7882;|Invalid
trustStore:null Using default.|#]

********

4. Create CLB by using the following steps.
./asadmin create-converged-lb-config <config-name> Command
./asadmin create-converged-lb-ref --clbconfig <config-name> <cluster-name>
./asadmin create-converged-lb --clbconfig <config-name> --configfile
<configfile-name> --target <cluster-name> <lb-name>
5. Restart the cluster. As before, error messages appear on the command line
(repeated for each instance). The message though are different. errors 0 and 1
are gone from the above set and replace by 2 new messages.
*********
The clustered instance, instance1, was successfully started.
error 0
[#|2007-12-05T06:38:23.749+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.container.sip|_ThreadID=16;_ThreadName=pool-1-thread-5;_RequestID=6a96978c-732d-412c-a76c-cf68af971532;|ssr-lb.xml
(No such file or directory)|#]

error 1
[#|2007-12-05T06:38:24.531+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.sip|_ThreadID=16;_ThreadName=pool-1-thread-5;_RequestID=6a96978c-732d-412c-a76c-cf68af971532;|Invalid
keyStore:null Using default.|#]

error 2
[#|2007-12-05T06:38:24.531+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.sip|_ThreadID=16;_ThreadName=pool-1-thread-5;_RequestID=6a96978c-732d-412c-a76c-cf68af971532;|Invalid
trustStore:null Using default.|#]

error 3
[#|2007-12-05T06:38:24.552+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.clb|_ThreadID=16;_ThreadName=pool-1-thread-5;_RequestID=6a96978c-732d-412c-a76c-cf68af971532;|Controller
is null|#]
*********

6. Notice that "error 0" states that file ssr-lb.xml does not exist. ssr-lb.xml
is the <configfile-name> I used. So I copied
<as-install-location>/domains/<domain-name>/config/ssr-lb.xml.ssr-lb to
<as-install-location>/domains/<domain-name>/config/ssr-lb.xml. ssr-lb was the
<lb-name> that I used. On using command create-converged-lb, the admin had
created file <configfile-name>.<lb-name> and this step copied that to
<configfile-name>
7. Restart the cluster. The messages remain the same as from step 5.

Can these error message be stated as Warnings or better (if possible) - not
appear at all.



 Comments   
Comment by Yamini K B [ 06/Feb/08 10:25 PM ]

assigning to Srini to evaluate

Comment by srinik76 [ 08/Feb/08 02:15 AM ]

This happens because of clb xml is not available in the config directory because
auto-commit is set to false by default.

This needs to be documented in the
Administration Guide and Trouble shooting guide that after creating converged
load balancer, auto-commit needs to be set to true to generate clb xml and also
to avoid these unexpected errors/behaviour.

Need to reassing to docs so that this is documented.

Comment by srinik76 [ 21/Feb/08 01:54 AM ]

Re-assigning the bug to docs

Comment by rj139419 [ 03/Mar/08 09:43 PM ]

will be doc'ed in the Admin and Troubleshooting guides for beta

Comment by prasads [ 13/May/08 11:34 PM ]

Marking as shark-na

Comment by cs194067 [ 30/Jun/08 09:53 PM ]

reassigning to myself.

Comment by cs194067 [ 30/Jun/08 11:01 PM ]

Needs to be documented in the High availability guide and the Admin guide.

Comment by Yamini K B [ 30/Jul/08 12:40 AM ]

changing the category

Comment by jagadesh [ 06/Aug/08 11:03 AM ]

"This bug will be scrubbed and will be upgraded for next relevant milestone builds".

Comment by jagadesh [ 06/Aug/08 11:04 AM ]

"This bug will be scrubbed and will be upgraded for next relevant milestone builds".

Comment by prasads [ 14/Aug/08 11:38 AM ]

Marking all of them as P3

Comment by chinmayee_srivathsa [ 13/Oct/08 02:31 AM ]

This bug applies to unbundled docs/online docs on docs.sun.com

Comment by prasads [ 18/Nov/08 03:37 AM ]

Adding the key word for approval

Comment by jagadesh [ 16/Jan/09 07:47 AM ]

Downgrading to a P4 since these bugs are not targeted for Sailfin 1.0. will be
upgraded back to the original priority for Sailfin 2.0

Comment by chinmayee_srivathsa [ 17/Jan/09 07:58 PM ]

Fixed. see page 40 in attachment

Comment by chinmayee_srivathsa [ 17/Jan/09 08:00 PM ]

Created an attachment (id=934)
troubleshooting guide





[SAILFIN-7] asadmin start-domain does not list the SIP listener ports Created: 21/Jun/07  Updated: 12/Aug/08  Resolved: 12/Aug/08

Status: Resolved
Project: sailfin
Component/s: admin
Affects Version/s: 1.0
Fix Version/s: milestone 1

Type: Bug Priority: Major
Reporter: sm122304 Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7
Status Whiteboard:

shark-na

Tags:
Participants: chinmayee_srivathsa, eltjoboersma, jluehe, prasads, sm122304, srinik76 and Yamini K B

 Description   

When the domain starts it print all the ports the server is listening on. The
SIP listener ports are not listed.

Starting Domain domain1, please wait.
Log redirected to
/export/workspace/publish/glassfish/domains/domain1/logs/server.log.
Redirecting output to
/export/workspace/publish/glassfish/domains/domain1/logs/server.log
Domain domain1 is ready to receive client requests. Additional services are
being started in background.
Domain [domain1] is running [Sun Java System Application Server 9.1 (build
local)] with its configuration and logs at:
[/export/workspace/publish/glassfish/domains].
Admin Console is available at http://localhost:4848.
Use the same port [4848] for "asadmin" commands.
User web applications are available at these URLs:
http://localhost:8080 https://localhost:8181.
Following web-contexts are available:
[/web1 /__wstx-services ].
Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[service:jmx:rmi:///jndi/rmi://kochi:8686/jmxrmi] for domain management purposes.
Domain listens on at least following ports for connections:
[8080 8181 4848 3700 3820 3920 8686 ].
Domain does not support application server clusters and other standalone instances.



 Comments   
Comment by prasads [ 27/Sep/07 08:25 AM ]

Re-assigning to Yamini KB

Comment by Yamini K B [ 17/Dec/07 07:37 AM ]
      • Issue 28 has been marked as a duplicate of this issue. ***
Comment by jluehe [ 08/Jan/08 10:11 AM ]
      • Issue 361 has been marked as a duplicate of this issue. ***
Comment by Yamini K B [ 24/Jan/08 08:19 PM ]

Container should list the opened ports during startup.

Comment by eltjoboersma [ 20/Feb/08 10:01 AM ]

This may involve Glassfish ADMIN and/or Sailfin ADMIN impact. Backend currently
provides inteface to obtain port information.

As a work around currently on INFO level a list is logged that includes all sip-
listeners that were configured and the protocol, address and port information.

Comment by prasads [ 13/May/08 11:14 PM ]

Marking as shark-na

Comment by Yamini K B [ 14/May/08 08:05 PM ]

Srini is working on this.

Comment by srinik76 [ 15/May/08 05:35 AM ]

Fixed the issue. The following is the asadmin start-domain command output
Starting Domain domain1, please wait.
Log redirected to
/space/sailfin/may12/publish/glassfish/domains/domain1/logs/server.log.
Redirecting output to
/space/sailfin/may12/publish/glassfish/domains/domain1/logs/server.log
Domain domain1 started.
Domain [domain1] is running [Sun Java System Communications Application Server
1.0 (build local)] with its configuration and logs at:
[/space/sailfin/may12/publish/glassfish/domains].
Admin Console is available at http://localhost:4848.
Use the same port [4848] for "asadmin" commands.
User web applications are available at these URLs:
http://localhost:8080 https://localhost:8181.
Following web-contexts are available:
[/web1 /__wstx-services ].
Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[service:jmx:rmi:///jndi/rmi://caitanya:8686/jmxrmi] for domain management purposes.
Domain listens on at least following ports for connections:
[8080 8181 4848 3700 3820 3920 8686 null].
Domain supports application server clusters and other standalone instances.

Domain listens on at least following ports for SIP connections:
[SIP 0.0.0.0:5060, SIPS 0.0.0.0:5061].

Checking in build.xml;
/cvs/sailfin/administration/build.xml,v <-- build.xml
new revision: 1.32; previous revision: 1.31
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/CLIDescriptor.xml,v
<-- CLIDescriptor.xml
new revision: 1.31; previous revision: 1.30
done
RCS file:
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/ExtStartDomainCommand.java,v
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/ExtStartDomainCommand.java;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/ExtStartDomainCommand.java,v
<-- ExtStartDomainCommand.java
initial revision: 1.1
done
Checking in
src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties;
/cvs/sailfin/administration/src/main/java/org/jvnet/glassfish/comms/admin/cli/extensions/commands/LocalStrings.properties,v
<-- LocalStrings.properties
new revision: 1.4; previous revision: 1.3
done

Comment by chinmayee_srivathsa [ 12/Aug/08 10:47 PM ]

re-opening for doc fix.

Comment by chinmayee_srivathsa [ 12/Aug/08 10:48 PM ]

reassigning to myself

Comment by chinmayee_srivathsa [ 12/Aug/08 10:49 PM ]

Fixed in the start-domain man page in the reference manual at:
http://sailfin.dev.java.net/documentation/documents/SJSASEEREFMAN.pdf





[JAVAEETUTORIAL-92] Integrate CDI content from WebLogic Server 12c Developer's Guide into advanced CDI chapter in tutorial Created: 30/May/12  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-3
Fix Version/s: 6.0.8

Type: Improvement Priority: Major
Reporter: jendrock Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: 2 weeks
Time Spent: Not Specified
Original Estimate: 2 weeks

Tags:
Participants: chinmayee_srivathsa, jendrock and Kim Haase

 Description   

Add applicable content from Chapter 9, "Using Contexts and Dependency Injection for the Java EE Platform" in the Oracle® Fusion Middleware Developing Applications for Oracle WebLogic Server 12c Release 1 book to the "Contexts and Dependency Injection for the Java EE Platform: Advanced Topics" chapter in the tutorial. Some content, including information about contextual scopes, may need to be migrated to the basic CDI chapter. The plan discussed in the tutorial meeting sounded comprehensive and correct. Please outline it here in a comment, then implement it in the advanced topics chapter.



 Comments   
Comment by Kim Haase [ 31/May/12 08:18 PM ]

I have made the fixes involving dispose methods as part of the v2 index fixes – I added index entries for dispose on the appropriate paragraph, changed the section title, and made "dispose method" a term. The additional content from the WLS book remains to be added.

Comment by Kim Haase [ 11/Jul/12 04:03 PM ]

I believe that all the fixes from http://aseng-wiki.us.oracle.com/asengwiki/display/JavaDocumentation/CDI+Chapter+for+Java+EE+6+tutorial have now been made, so I think you can close this as fixed, Chinmayee. Thanks!

Comment by jendrock [ 05/Feb/13 09:28 PM ]

The issue has been fixed and is available online and in the javaeetutorial 6.0.8 package in the Update Center.





[JAVAEETUTORIAL-74] Make MDB work in mailconnector example Created: 21/Mar/12  Updated: 24/May/12  Resolved: 24/May/12

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.7-2
Fix Version/s: 6.0.7-3

Type: Improvement Priority: Major
Reporter: jendrock Assignee: chinmayee_srivathsa
Resolution: Works as designed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags:
Participants: chinmayee_srivathsa, jendrock and Kim Haase

 Description   

The endpoint activation method is never called in the mailconnector example. The MDB needs to be fixed so it can perform its function as a listener. This can be done by examining (and possibly reusing) the code in the original GlassFish Samples. An explanation of endpoint activation can be found on page 16 of the white paper by Alejandro Murillo and Binod P.G. entitled "Creating Resource Adapters with J2EE Connector Architecture 1.5" circa 2004.



 Comments   
Comment by Kim Haase [ 24/May/12 07:20 PM ]

Since the application now retrieves the messages synchronously through the managed bean rather than receiving them asynchronously through the MDB, the MDB exists only to activate the resource adapter.





[JAVAEETUTORIAL-43] Create a composite component example that shows how to use an action listener Created: 15/Jul/11  Updated: 05/Feb/13  Due: 15/Aug/11  Resolved: 05/Feb/13

Status: Closed
Project: javaeetutorial
Component/s: doc, examples
Affects Version/s: 6.0.7
Fix Version/s: 6.0.7-6

Type: Task Priority: Major
Reporter: jendrock Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: 4 weeks
Time Spent: Not Specified
Original Estimate: 4 weeks

Tags:
Participants: chinmayee_srivathsa and jendrock

 Description   

Create an additional composite component example that shows how to use an action listener. This requires a new example, not a mere rewrite of the customary composite component login example. Then, document how to build, deploy, and run the new example in the Advanced Composite Components chapter and also add a section that explains when to use "action" vs. "action listener".



 Comments   
Comment by jendrock [ 05/Feb/13 07:43 PM ]

We already have a composite component example. Although a better example could be created, we do not plan to do so in the forseeable future.





[JAVAEETUTORIAL-38] Change from DBAO to using JPA entity classes Created: 17/Jun/11  Updated: 16/Aug/12  Resolved: 14/Jul/11

Status: Closed
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.7-5
Fix Version/s: 6.0.7-5

Type: Task Priority: Major
Reporter: chinmayee_srivathsa Assignee: jendrock
Resolution: Fixed Votes: 0
Remaining Estimate: 2 weeks
Time Spent: Not Specified
Original Estimate: 2 weeks

Tags:
Participants: chinmayee_srivathsa and jendrock

 Comments   
Comment by jendrock [ 14/Jul/11 02:34 PM ]

Kim and I completed this task. We created and populated the database, ran the NetBeans Create Entities from Database wizard to create a new Book.java file in the dukesbookstore.entities package. We added the findbooks named query to it as well. We got rid of web/bookstore/src/java/com/sun/bookstore6/database/BookDBAO.java and migrated its functionality to dukes-bookstore/src/java/dukesbookstore/ejb/BookRequestBean.java, adding logging functionality and a named query.

Comment by jendrock [ 14/Jul/11 02:36 PM ]

The functionality has been ported to the revised example in web/dukes-bookstore. We tested it and it operates as before - no regressions.

Comment by jendrock [ 14/Jul/11 02:38 PM ]

It works as advertised, so I will close this issue. However, if further testing indicates a need to work on it again, the issue will have to be reopened.





[GLASSFISH-9416] JavaEE6:Web Beans:index.html: missing UserTroubleShooting.html link Created: 08/Sep/09  Updated: 27/Nov/10  Resolved: 23/Sep/09

Status: Resolved
Project: glassfish
Component/s: sample_apps
Affects Version/s: V3
Fix Version/s: V3

Type: Bug Priority: Critical
Reporter: davisn Assignee: Mike Fitch
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: All


Issuezilla Id: 9,416
Tags:
Participants: chinmayee_srivathsa, davisn and Mike Fitch

 Description   

When click troubleshooting document link in the index.html of the The JSF 2.0
Web Beans Sample Application, the "UserTroubleShooting.html" link page was missing.

Steps To Reproduce:
1. Install V3 SDK build java_ee_sdk-6-preview-b18-windows.exe
2. Install the servers
3. Go to
<install-server>\glassfish\samples\javaee6\webbeans\webbeans-guess\docs, open
index.html file
4. Click at the troubleshooting document link
BUG:
UserTroubleShooting.html page was missing - wrong path pointed to



 Comments   
Comment by davisn [ 08/Sep/09 01:53 PM ]

Reassign to doc owner

Comment by chinmayee_srivathsa [ 22/Sep/09 10:49 PM ]

Reassigning to Mike Fitch

Comment by Mike Fitch [ 23/Sep/09 11:58 AM ]

Corrected the troubleshooting link (and the common instructions link, which was
also wrong).





[GLASSFISH-8857] UserREADME.html should replace the Netbean IDE 6.7 text Created: 23/Jul/09  Updated: 27/Nov/10  Resolved: 01/Nov/09

Status: Resolved
Project: glassfish
Component/s: sample_apps
Affects Version/s: V3
Fix Version/s: V3

Type: Bug Priority: Critical
Reporter: davisn Assignee: Mike Fitch
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 8,857
Tags:
Participants: chinmayee_srivathsa, davisn, Mike Fitch and msreddy

 Description   

Since Netbean IDE 6.8 will be released by October and it's designed to fully
support GlassFish V3, UserREADME.html content should replace Netbean 6.7 by
Netbean 6.8



 Comments   
Comment by msreddy [ 20/Sep/09 05:42 PM ]

Requesting Chinmayee's help to update the doc.

Comment by chinmayee_srivathsa [ 22/Sep/09 10:49 PM ]

Re-assigning to Mike Fitch

Comment by Mike Fitch [ 23/Sep/09 11:56 AM ]

Updated javaee6/docs/UserREADME.html as follows:

  • Separated one-time and per-sample setup tasks
  • Updated NetBeans section for NetBeans 6.8, based on NetBeans IDE Build
    200909151512.
Comment by Mike Fitch [ 01/Nov/09 05:21 PM ]
      • Issue 9915 has been marked as a duplicate of this issue. ***




[GLASSFISH-8443] UserREADME.html: Missing GF Admin Guide link Created: 25/May/09  Updated: 22/Sep/09  Resolved: 22/Sep/09

Status: Resolved
Project: glassfish
Component/s: sample_apps
Affects Version/s: V3
Fix Version/s: V3

Type: Bug Priority: Critical
Reporter: davisn Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 8,443
Tags:
Participants: chinmayee_srivathsa, davisn and msreddy

 Description   

-This bug probably will be resolved when the "Extending Enterprise Server in Sun
GlassFish Enterprise Server v3 Administration Guide" document is posted online.
At the current promoted SDK b03d build, file UserREADME.html, when click at
"Extending Enterprise Server in Sun GlassFish Enterprise Server v3
Administration Guide" the lionk is missing.
-Please, close the bug when the document is posted. This is for the record



 Comments   
Comment by msreddy [ 26/May/09 10:42 AM ]

Assigining tp docs.

Comment by chinmayee_srivathsa [ 22/Sep/09 10:48 PM ]

The link is no longer broken.





[GLASSFISH-8382] UserREADME.html needs clear instruction for NB Created: 18/May/09  Updated: 19/May/09  Resolved: 19/May/09

Status: Resolved
Project: glassfish
Component/s: sample_apps
Affects Version/s: V3
Fix Version/s: V3

Type: Bug Priority: Blocker
Reporter: davisn Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: All


Issuezilla Id: 8,382
Tags:
Participants: chinmayee_srivathsa, davisn and msreddy

 Description   

The UserREADME.html does not have a clearer instruction for setting up and
running the samples with NB IDE 6.7

1. When I click at the Netbeans IDE link I was pointed to the netbeans.org page
which is currently posted Netbean 6.5 as default version for the page. That page
will cause confusion to the users because they might think the samples can run
with NB 6.5. It would be better if the link to netbeans.org page is removed.
This problem will be resloved itself when 6.7 is FCS, but it's still better to
have less confussion for now.

2. The NB6.7 Beta does not work with V3 Plugin. Please specifically states which
NB 6.7 version user should select to download.

3. Please also mention the step to install the V3 plugin (GlassFish V3 Enabler)
before register SDK V3 server. Please consult with Vince for the complete steps.



 Comments   
Comment by msreddy [ 18/May/09 07:09 PM ]

Request Chinmayee's help for documentation.

Comment by chinmayee_srivathsa [ 19/May/09 10:12 PM ]

Fixed in UserREADME.html on 5/19.

Checked in revised instructions with vince's review comments incorporated today
on 5/20.





[GLASSFISH-8361] sample 'javaee6/web/jsf/scrumtoys' does not exist in list.html Created: 15/May/09  Updated: 18/May/09  Resolved: 18/May/09

Status: Resolved
Project: glassfish
Component/s: sample_apps
Affects Version/s: V3
Fix Version/s: V3

Type: Bug Priority: Blocker
Reporter: msreddy Assignee: chinmayee_srivathsa
Resolution: Fixed Votes: 0
Remaining Estimate: