[GLASSFISH-12223] Session Persistence BackingStore SPI port from v2 to 3.1 workspace Created: 13/Jun/10  Updated: 13/Jun/10  Resolved: 13/Jun/10

Status: Resolved
Project: glassfish
Component/s: failover
Affects Version/s: 3.1
Fix Version/s: 3.1_ms01

Type: New Feature Priority: Blocker
Reporter: Mahesh Kannan Assignee: Mahesh Kannan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 12,223

 Description   

This is a feature request for HA-1 mentioned in the In memory replication one
pager: http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFish3.1HAOnePager



 Comments   
Comment by Mahesh Kannan [ 13/Jun/10 ]

This feature is now available. The backing store SPI is available in glassfish
V3.1 workspace (under ha module)





[GLASSFISH-11910] list-domains very broken Created: 14/May/10  Updated: 21/May/10  Resolved: 21/May/10

Status: Resolved
Project: glassfish
Component/s: admin
Affects Version/s: 3.1
Fix Version/s: 3.1_ms01

Type: Bug Priority: Critical
Reporter: Byron Nevins Assignee: Tom Mueller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,910

 Description   

~/glassfishv3/glassfish/domains/domain1>asadmin list-domains
null
Command list-domains failed.



 Comments   
Comment by Tom Mueller [ 17/May/10 ]

This command appears to be working on Windows.

Confirmed seeing the problem on Solaris 10.

Comment by Tom Mueller [ 17/May/10 ]

It is broken on Windows too.

The problem is that the LocalDomainCommand.getDomainsDir method is being called
while the "dd" field is still null. So an NPE is being thrown.

The method that initializes "dd" is LocalDomainCommand.initDomain, but this is
overridden by ListDomainCommand to do nothing.

Proposed fix: remove the ListDomainCommand.initDomain method, since
LocalDomainCommand.initDomain properly handles the case where a domain name is
not passed on the command line.

Comment by Tom Mueller [ 17/May/10 ]

Proposed solution works when there is only one domain. But as soon as there is
more than one domain, the initDomain method can't decide which one to use to it
throws on IOException, which is probably why the call to initDomain was
overridden in the first place.

Comment by Byron Nevins [ 17/May/10 ]

A Domain is a universe. This command works at one level up from a universe.

What it is supposed to do is to go to the domains directory and get a listing of
all domains based simply on each domain being a sub-directory in there.

Now you need to iterate through each domain and find the adminport by parsing
domain.xml.
Once you have all the admin-ports you can call _localdirectories(sp?) on each
such das and then compare the returned dir path with the one you have to confirm
you have the right server. At that point you can say the domain is running.
I.e. you can easily have 2 domains that use the same port 4848 – I do it all
the time. We can conclusively tell them apart by host:port AND the directories
location.

I.e. This command is a TON of work to do properly. If you don't find the
running state of the DAS' it is very trivial – just print the list of domains.

Comment by Tom Mueller [ 21/May/10 ]

Fixed. However there is still an annoying warning message when running the
command with a running DAS about the telnet port for OSGi being in use, but that
is another bug.





Generated at Sat Apr 18 12:00:44 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.