[GLASSFISH-18600] Document incorrectly states that 32-bit load-balancer plugin is support on Solaris and Linux Created: 06/Apr/12  Updated: 06/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: future release

Type: Bug Priority: Critical
Reporter: kshitiz_saxena Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Documentation link : http://docs.oracle.com/cd/E26576_01/doc.312/e24934/web-servers-for-http-load-balancing.htm#gldbq

As per above link, load-balancer plugin support exists for 32-bit webserver on Solaris and Linux. This information is incorrect. We only support 64-bit webserver on Solaris and Linux platform. For solaris, support is limited to Solaris 10.

Information with respect to windows, AIX and HP-UX is correct.






[GLASSFISH-9954] Improve create-transport man page (was: remove the not frequently used options in create-transport) Created: 02/Oct/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: sankarpn Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: PC


Issuezilla Id: 9,954
Tags: 3_1-exclude

 Description   

All the parameters used in transport is put as options in create-transport
command. We shouldn't have put all the attributes available as a command options
which makes the command more complex to type and use.

Like create-protocol command the minimal set of frequently used options must be
part of the command , rest of them can be omitted and put as defaults in config.

If one wants to modify those they can always to get/set

Usage: asadmin [asadmin-utility-options] create-transport [--acceptorthreads -1]
[--buffersizebytes 8192] [--bytebuffertype HEAP] [--classname
com.sun.grizzly.TCPSelectorHandler] [--displayconfiguration false]
[--enablesnoop false] [--idlekeytimeoutseconds 30] [--maxconnectionscount 4096]
[--readtimeoutmillis 30000] [--writetimeoutmillis 30000] [--selectionkeyhandler
<selectionkeyhandler>] [--selectorpolltimeoutmillis <selectorpolltimeoutmillis>]
[--tcpnodelay <tcpnodelay>] [-?|--help=false] transportname

Usage: asadmin [asadmin-utility-options] create-protocol [--securityenabled
<securityenabled>] [-?|--help=false] protocolname



 Comments   
Comment by Bill Shannon [ 02/Oct/09 ]

This sounds like an enhancement request.

Reassigning to Nandini.

Comment by sankarpn [ 03/Oct/09 ]

ok, made as RFE. But I request this to be fixed.

Comment by Tom Mueller [ 23/Jun/10 ]

Nandini no longer on project.

Comment by Bill Shannon [ 23/Jun/10 ]

Good or bad, we've already got all those options in v3, so removing them
would be a compatibility issue. Instead, the man page for this command
could use some improvement to describe which options are likely or unlikely
to be used, as well as giving more useful usage examples.

Comment by Mike Fitch [ 03/Jan/11 ]

Will investigate reorganizing the man page in a future release.

Comment by Paul Davies [ 27/May/11 ]

Under consideration for 3.1.1

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5261] [UB] ACC Should use JRE but not JDK Created: 05/Jul/08  Updated: 29/Apr/13

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 9.1peur2
Fix Version/s: 4.0

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,261

 Description   

When deploying to a lot of client computers, it is not fun to install more
megabytes than needed. Currently the ACC wants to have a complete JDK (not just
JRE) installed on each client computer:

http://docs.sun.com/app/docs/doc/819-3675/package-appclient-1m?a=view

Actually it seems that the only sense of having a JDK (instead of JRE) is that
the above documentation says one shall unjar appclient.jar on the client. It
seems, there is no other part of the JDK used besides jar.exe.

So I propose that the installation procedure gets changed: Do not pack the
appclient as a JAR but as a ZIP (virtually all target operating systems already
have ZIP installed, so no need for a complete JDK anymore), or do not pack it at
all but provide an installation image file system folder instead (can be copied
to the client without the need to unpack anything there).

This will reduce the footprint of the client installation by far.



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 07/Jul/08 ]

Moving to appropriate subcategory for evaluation.

Comment by Tim Quinn [ 08/Jul/08 ]

Because JAR files are ZIP files also, you could already use a local UNZIP
utility to unpack the appclient.jar.

Have you tried that and encountered problems?

Where the documentation mentions defining AS_JAVA to point to the JDK directory,
you can instead just define it to point to the JRE directory.

Would that meet your needs?

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by mkarg [ 14/Nov/12 ]

If I understand correctly, Tim agrees that the JRE is sufficient. So please modify the documentation.

Comment by Tim Quinn [ 16/Nov/12 ]

Changing component to documentation.

Comment by Mike Fitch [ 14/Mar/13 ]

Changed Fix Version to 4.0 so issue will show up on 4.0* queries. Actual commitment and build # TBD.

Comment by Mike Fitch [ 24/Mar/13 ]

Updated the manpage to mention that you can unzip the JAR file and to specify that you can point AS_JAVA to a JDK or JRE directory.

This update will become accessible in GlassFish when the next main-docs build is promoted and picked up by GlassFish builds.

Comment by Mike Fitch [ 01/Apr/13 ]

Correction: this manpage is not visible in GlassFish because package-appclient is not an asadmin subcommand.

Adding [UB] to the summary so this issue will get picked up by "unbundled" (book) doc queries. The material will appear in the Reference Manual.

Comment by mkarg [ 29/Apr/13 ]

As there is a Special "Server JRE" distribution available since JRE 7u21, I think it makes sense to modify the documentation that this "Server JRE" is sufficient to run GlassFish. So People don't need to download and install a fully-featured Oracle JRE (including things like ActiveX bridge etc.).





[GLASSFISH-4629] [UB]Some wrong MDB warnings at startup when attribute value is 0 Created: 06/Apr/08  Updated: 15/Mar/13

Status: Reopened
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: dinglemouse Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: PC


Issuezilla Id: 4,629

 Description   

There were a couple of observed WARNING messages during cluster startup when
some of the EJB attribute settings were 0:

For example,

error 3
[#|2008-03-27T13:32:19.175+1100|WARNING|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=10;_ThreadName=main;ejbtuning_server:MDB;0;max-pool-size;1;_RequestID=6dc41603-cc8f-44d9-85d5-75abf1fc7963;|MDB00060:
[ejbtuning_server:MDB]: Invalid value [0] for [max-pool-size] , use [1] instead|#]

...

error 3
[#|2008-03-27T15:55:07.433+1100|WARNING|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=10;_ThreadName=main;ejbtuning_server:MDB;0;idle-timeout-in-seconds;1;_RequestID=6dd3f8e6-6a6d-4945-b61c-c2f2b9b17f27;|MDB00060:
[ejbtuning_server:MDB]: Invalid value [0] for [idle-timeout-in-seconds] , use
[1] instead|#]

...

It seems to me that there may be a bug in the code for
MessageBeanContainer.validateValue method because the validation code is not
accounting for the fact that 0 has a special meaning for some of the MDB
attributes (accounting to the administration manual)



 Comments   
Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by ksak [ 28/Jan/09 ]

Reassigning bugs from Mahesh

Comment by Cheng Fang [ 03/Jun/11 ]

This issue exists in 3.x too.

With <mdb-container idle-timeout-in-seconds="0">

there is this warning in server.log when running mdb tests:

[#|2011-06-03T14:47:05.425-0400|WARNING|glassfish3.2|javax.enterprise.system.container.ejb.mdb.com.sun.ejb.containers|_ThreadID=14;_ThreadName=Thread-1;|MDB00060: [ejb-ejb30-hello-mdbApp:MessageBean]: Invalid value [0] for [idle-timeout-in-seconds] , use [600] instead|#]

According to dev guide:

Idle Timeout
Specifies the maximum time in seconds that a bean can remain idle in the pool. After this
amount of time, the bean is destroyed. The default is 600 (10 minutes). A value of 0 means a
bean can remain idle indefinitely.

Comment by Nigel Deakin [ 27/Jun/11 ]

This constraint is enforced in two places, both of which need to be changed to allow a value of 0.

com.sun.ejb.containers.MessageBeanContainer (part of the EJB container in GlassFish)

com.sun.messaging.jms.ra.ActivationSpec (part of JMSRA which is part of MQ)
MQ bug MQ-103 has been opened to cover this second change.

Comment by marina vatkina [ 27/Jun/11 ]

One more note from the email discussion, that will need to go into the docs when 0 is fixed: (Nigel adds: make clear that this applies only when JMSRA is used)

If endpointPoolMaxSize < max-pool-size then the maximum number of MDB instances used at any given time will be limited to endpointPoolMaxSize

If endpointPoolMaxSize > max-pool-size then JMSRA will attempt to create more MDBs than there are in the pool, and you will see lots of messages of the form:
INFO: MQJMSRA_MR1101: createEndpoint-UnavailableException:Sleeping for:1000

So generally, users should set endpointPoolMaxSize only (or set both to the same value) since settings them to different values either has no effect or generated errors.

Comment by Nigel Deakin [ 28/Jun/11 ]

MQ bug MQ-103 has been resolved in MQ 4.6 (which will be delivered in GlassFish 3.2).

Comment by Cheng Fang [ 17/Aug/11 ]

Fixed ejb-container MessageBeanContainer in 3.2 trunk
Committed revision 48856

Comment by Cheng Fang [ 17/Aug/11 ]

re-assign to docs team to adjust GlassFish dev guide, according to Nigel and Marina's comments above.

Comment by Rebecca Parks [ 28/Nov/11 ]

Does this apply to 3.1.2?

Comment by Paul Davies [ 20/Dec/11 ]

[UB]: Unbundled documentation

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.

Nigel & Cheng:
Given that GL 3.2 is now 4.0 and MQ 4.6 is now 5.0, am I right in assuming that this issue is applicable to GF 4.0 (which bundles MQ 5.0)?
Thanks,
--Mike





[GLASSFISH-15437] [UB]Cannot start DAS when custom container has a class called Domain Created: 04/Jan/11  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: chukmunnlee Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 10.04,
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Server VM (build 19.0-b09, mixed mode)


Tags: 3_1-exclude, 3_1-next, 3_1_1-scrubbed, 3_1_2-exclude

 Description   

I'm developing a custom container. It was working fine. I rename one of my class to Domain. I repackaged it. I then copied my container's jar to$GF_HOME/glassfish/modules.

When I tried to start GF, I got

Waiting for DAS to start.......

This goes on for a while then GF says it could not start my domain. Anyway I then renamed the Domain class to something else. Rebuild and recopied the file to modules directory and GF started.



 Comments   
Comment by Nazrul [ 05/Jan/11 ]

Jerome: Should this be documented?

Comment by Nazrul [ 10/Jan/11 ]

Excluding from 3.1 list.

Comment from Jerome:
Looks like folks should not use any of our [GlassFish] configuration names or should use a @configured(name="myspecialname") annotations to disambiguate.

Comment by scatari [ 11/Jun/11 ]

To be considered in the next release.

Comment by Tom Mueller [ 24/Dec/12 ]

Changing this to be a docs bug. The section on extending the configuration of the system should be modified to specify that any new config element must have a unique name, i.e., the name of just the class has to be unique, not just the name including the Java package name.

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.





[GLASSFISH-18195] [UB]Document the copying of jdbc drivers to appropriate locations for different modes of JMS Created: 13/Jan/12  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_dev
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: saradak Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Please document that
For EMBEDDED mode, the jdbc driver needs to be copied to the directory glassfish3/glassfish/lib/install/applications/jmsra/

For LOCAL/REMOTE modes, the jdbc driver needs to be copied to the directory glassfish3/mq/lib/ext/

-Sarada.



 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-19539] Link to Audit Callbacks in "Pluggable Audit Module Support" broken Created: 16/Jan/13  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: myfear Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

n/a


Tags: documentation

 Description   

The link to the "Audit Callbacks" (linked: http://developers.sun.com/appserver/reference/techart/ws_mgmt3.html)
on the "Pluggable Audit Modules Support" page (http://docs.oracle.com/cd/E18930_01/html/821-2418/beabu.html) in the Oracle GlassFish Server 3.1 Application Development Guide is broken.






[GLASSFISH-18045] [UB]Provide instructions to configure 64-bit usage of Webserver when on Solaris 11 (sparcv9) Created: 19/Dec/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: not determined

Type: Task Priority: Major
Reporter: varunrupela Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 312_qa

 Description   

Once Solaris 11 is added as a supported platform in the HA Admin Guide, instructions will be needed to configure usage of the 64-bit Webserver.
http://docs.oracle.com/cd/E18930_01/html/821-2426/gldbq.html#scrolltoc

On Solaris 11, extra steps are required to configure usage of the Webserver as 64-bit software. This is required since the lb configurator will install a 64-bit LB and would need the webserver to be running as 64-bit.

The extra steps are noted here:
http://docs.oracle.com/cd/E19146-01/821-1832/gdaem/index.html

***
Set the configuration property:
$ wadm set-config-prop --user=admin-user --host=host-name --port=admin-port
--config=config-name platform=64

Deploy the configuration:
$ wadm deploy-config config-name
****



 Comments   
Comment by Paul Davies [ 19/Dec/11 ]

[UB] - Affects unbundled documentation.

In addition to the HA Administration Guide, this issue might also affect the examples in the Quick Start Guide (if only to the extent of updating the assumptions to include an operating system other than Solaris 11).

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





Need to port the Nodes support to 4.0 (GLASSFISH-17961)

[GLASSFISH-17965] port help from 3.1.2 to 4.0 relates to Nodes Created: 09/Dec/11  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: future release

Type: Sub-task Priority: Major
Reporter: Anissa Lam Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_x-exclude, ee7ri_cleanup_deferred

 Description   

refer to main task






[GLASSFISH-18230] [UB]GlassFish "Typical" Install flow change. Domain Info screen has been added to allow a user to add a password Created: 19/Jan/12  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_dev
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Alex Pineda Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

System is OEL5 with JDK 1.6.0_30. GF 3.1.2 build18. Installation done through GUI using "typical" option with default settings.


Attachments: PDF File DomainInfo.pdf    
Tags: glassfish, installer

 Description   

The "Typical" Glassfish Installation process has been changed. A screen has been added (Domain Info) which basically allows a user to modify the Domain name, Admin port, Http port, admin user, admin password, and ability to set up DomainServices. This screen appears to be a similar or same screen that is part of the Custom Install process.

The explanation for adding this screen is based on a Security requirement noted in https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=12652057 . So, there's no possibility to revert the Install flow to what it was in GF 3.1.2 build 16 or the previous versions of Glassfish (3.1.1, 3.1, etc...).

So this report is basically to track the change and the affected areas. From a Test standpoint, this change affects our manual test procedure to include test cases that cover the "Domain Info" screen. Perhaps there's an impact to the Install Guide to add the additional screen.

Attached is a screenshot of the Domain Info page that is now added to the "Typical" install.



 Comments   
Comment by Joe Di Pol [ 24/Jan/12 ]

Assigning to docs to make sure this change is documented in the install guide.

Comment by Paul Davies [ 15/Feb/12 ]

[UB]: Affects unbundled documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





Solaris 11, create-jmsdest, list-jmsdest failed: No response from Domain Admin Server after 600 seconds. (GLASSFISH-18112)

[GLASSFISH-18210] [UB] MQ Administration Guide - loopback network address checking on Solaris Created: 19/Jan/12  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_dev
Fix Version/s: 4.0

Type: Sub-task Priority: Major
Reporter: David Zhao Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris 11



 Description   

Please decide if Solaris specific thing should be mentioned in MQ Administration Guide.

In the MQ Administration Guide which Amy pointed out, it has:

*************************************************
Network loopback IP address. You must make sure that no broker in the cluster is given an address that resolves to a loopback network (127...*) IP address. Any broker configured with such an address will be unable to connect to other brokers in the cluster.

In particular, some Linux installers automatically set the local host to a loopback network address, most commonly 127.0.0.1. On such systems, you must do the following: For each Linux system participating in the cluster, check the /etc/hosts file as part of cluster setup. If the system uses a static IP address, edit the /etc/hosts file to specify the correct address for the local host. If the address is registered with Domain Name Service (DNS), edit the file /etc/nsswitch.conf so that DNS lookup is performed before consulting the local hosts file.

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

On Solaris, except for /etc/hosts, /etc/inet/ipnodes should also be checked for not being loopback network address.



 Comments   
Comment by Mike Fitch [ 14/Mar/13 ]

Added [UB] to summary and set fix version to 4.0 so this issue would show up in 4.0 doc issue queries.





[GLASSFISH-16095] [UB]Doc: Update Tool section in Admin Guide needs to be improved. Created: 24/Feb/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Chris Kasso Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In the GF Admin Guide there is a section titled:

Tools for Extending and Updating GlassFish Server

This section needs:

1) An introduction to Update Center and then a breakdown of the tools which are available. That includes updatetool, software update/notifier and the pkg command.
2) A section that discusses the various GF repositories which are available and how to access packages on those repositories. This may include discussing how to change the preferred repository for a GF installation.
3) How to enable/disable the notifier post installation.



 Comments   
Comment by Paul Davies [ 03/Mar/11 ]

A conscious decision was taken not to replicate in the GlassFish Server documentation information that is available elsewhere. For example, the GlassFish Server documentation should not replicate information that is provided in the Update Tool online help. This decision was taken when Update Center was still independent of GlassFish Server.

WRT item 1) The cited section already provides a breakdown of the tools that are of interest to the system administrator (see http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gkcbv.html#gkcba ). Now that the sole reason for Update Center's existence is GlassFish, there might be value in adding some of the content in the cross-referenced wikis to the GlassFish documentation.

WRT item 2) This information is already provided in Preconfigured Repositories for GlassFish Server (http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gjzko.html )

WRT item 3) Now that the sole reason for Update Center's existence is GlassFish, there might be value in adding this information to the GlassFish documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16045] [UB]tx rollback/recover examples with --target Created: 18/Feb/11  Updated: 28/Aug/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: sherryshen Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris, Linux



 Description   

Administration Guide
Chapter 18, Administering Transactions
I provided a few examples of rollback/recover with --target as a reference.
Thanks for the consideration.

By the way, I also verified 6 doc bugs filed from my tests and
filed this p4 bug to track my review.



 Comments   
Comment by sherryshen [ 18/Feb/11 ]

Review of GFv3.1 tx docs
Updated on Feb. 17, 2011 by sherry.hill

1) rollback example with --target for a clustered instance
2) recovery example with --target for a clustered instance
3) verified the 6 doc bugs filed from my tests.
1) rollback example with --target for a clustered instance
transactions-ag.pdf
page 25 Managing the Transaction Service for Rollbacks
Examples are given for das so that no --target is used.
Here is another example for a clustered instance with the use of --target from my tests for reference.

% asadmin freeze-transaction-service --target clustered_instance_2
Command freeze-transaction-service executed successfully.
%

% asadmin get --monitor=true clustered_instance_2.transaction-service.activeids-current
clustered_instance_2:
clustered_instance_2.transaction-service.activeids-current =
Transaction Id Status ElapsedTime(ms) ComponentName ResourceNames
030000008A0A552A6A65642D617371652D32322C636C757374657265645F696E7374616E63655F322C503433373030 Active 7835 txn.recovery.cliweb2.MyBean jdbc/cliweb2DB1
%

% asadmin rollback-transaction --target clustered_instance_2 --transaction_id 030000008A0A552A6A65642D617371652D32322C636C757374657265645F696E7374616E63655F322C503433373030
Command rollback-transaction executed successfully.
%

% asadmin unfreeze-transaction-service --target clustered_instance_2
Command unfreeze-transaction-service executed successfully.
%

The details can be found in
http://agni-1.us.oracle.com/net/asqe-logs/export1/v3.1/Results/build43/core/clu_oel/amd64/output/txn_recovery_cliweb.output

2) recovery example with --target
transactions-ag.pdf
Page 29, "To Manually Recover Transaction" with 2.2, but without 2.1.
2.1) Example of admincli recover-transactions for delegated recovery
If an application server instance (e.g. clustered_instance_2) fails transactions,
the transaction of that instance is picked up by the other running instance (e.g. clustered_instance_1).
% asadmin recover-transactions --target clustered_instance_1 --transactionlogdir /txlog/clustered_instance_2/tx clustered_instance_2
Command recover-transactions executed successfully.
%

2.2) Example of admincli recover-transactions for self recovery
If a recourse such as a database server fails transactions, the transaction of that instance is recovered by this instance after the database is restarted.
% asadmin recover-transactions clustered_instance_2
Command recover-transactions executed successfully.
%
The details can be found in
http://agni-1.us.oracle.com/net/asqe-logs/export1/v3.1/Results/build43/core/clu_oel/amd64/output/txn_recovery_cliweb.output

3) verified the 6 doc bugs filed from my tests.
3.1) verified the fix in docs.
Administration Guide
Chapter 18, Administering Transactions
Oracle Setup for Transaction Recovery
http://java.net/jira/browse/GLASSFISH-13837 Oracle Setup
http://java.net/jira/browse/GLASSFISH-15561 Oracle Setup

3.2) verified the fix in docs.
Administration Guide
Chapter 18, Administering Transactions
General Recovery Limitations
http://java.net/jira/browse/GLASSFISH-14750 JMS Embedded
http://java.net/jira/browse/GLASSFISH-13818 Expectation of recovery
http://java.net/jira/browse/GLASSFISH-14086 MYSQL

3.3) verified the fix in docs.
Administration Guide
Chapter 18, Administering Transactions
Transaction Logging
http://java.net/jira/browse/GLASSFISH-13527 UID

(removed e-mail address)

Comment by sherryshen [ 18/Feb/11 ]

I will use this bug to add another point in review.
4) about connection validation for recover transaction.
transactions-ag.pdf
To Manually Recover Transaction

  • "Connection validation should be enabled so that the connecton pool is refreshed when the resource is accessed after the recovery".

Any example how to enable connection validation?

http://java.net/jira/browse/GLASSFISH-13818
It gives an error for incorrect validation setting, i.e.
[#|2010-10-06T09:34:39.358-0700|INFO|glassfish3.1|javax.enterprise.resource.resourceadapter.com.sun.gjc.spi|
_ThreadID=15;_ThreadName=Thread-1;|RAR5074 : Table based validation detected
invalid connection.
Querying the table sys.systables failed. Set resource-adapter log-level to FINE
for exception stack trace. |#]

I made a note in the test spec with the examples of validation setting.
http://agni-1.us.oracle.com/asqe-logs/export1/v3.1/docs/sqe/txn/GF31TXRecoveryTestSpec.html

  • 13818, JDBC resources are configured with validation setting
    o asadmin set resources.jdbc-connection-pool.<jdbc_pool_name>.is-connection-validation-required=true
    o asadmin set resources.jdbc-connection-pool.<jdbc_pool_name>.validation-table-name=<table_name>
    o asadmin set resources.jdbc-connection-pool.<jdbc_pool_name>.connection-validation-method=table
    o The <table_name> can be database system table or user created table, which must be different from the table used for rollback/recover-transactions.
    o The following system tables can be used, sys.systables for Derby, DUAL for oracle, dual for MySQL.

I hope that this examples can be adopted to docs if there are not in yet.

Comment by Rebecca Parks [ 23/Feb/11 ]

Changed Fix Version to 3.2. Bundled docs are frozen for 3.1.

Comment by Rebecca Parks [ 12/May/11 ]

I have addressed most of this issue in the 3.1.1 Administration Guide's transactions chapter. To address the connection validation aspect, however, is in the JDBC area, not the transactions area. There is nothing about setting up connection validation in the JDBC chapter of the Admin Guide, but there should be. After this section is added, I can change the link in the transaction recovery section to point to it.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16339] [UB]sun-acc.xml (and associated DTD) are now glassfish-acc.xml Created: 11/Apr/11  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Tim Quinn Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16302 Convert sun-application-client-contai... Resolved

 Description   

During 3.1 we converted Glassfish-specific descriptors and DTDs from "sun-xxx" names to "glassfish-xxx" but I did not do this for the sun-acc.xml and the sun-application-client-container_1_2.dtd files.

I have opened issue 16302 which is for the engineering changes to make this change.

The docs should change to change references to sun-application-client-container.dtd to glassfish-application-client-container_1_3.dtd and from sun-acc.sml to glassfish-acc.xml.

Note that customers might have scripts which refer to the sun-acc.xml that has historically been generated into $

{domainDir}

/config, so 3.2 will continue to provide that file as well as glassfish-acc.xml. Officially the use of sun-acc.xml will be deprecated as of 3.2. But the documentation should steer users toward glassfish-acc.xml instead of sun-acc.xml.



 Comments   
Comment by Tim Quinn [ 11/Apr/11 ]

Linking to 16302 - the issue covering the engineering changes.

Comment by Rebecca Parks [ 11/May/11 ]

Changed target release to 3.2 per Tim Quinn.

Comment by Rebecca Parks [ 11/May/11 ]

Build 3 is when Tim made the fix in the 3.2 code.

Comment by Tim Quinn [ 16/Nov/11 ]

I have made the coding changes in 3.1.2 (which should appear in promoted build 11) for 16302.

The doc or release notes should mention that glassfish-acc.xml becomes the default ACC config file (in the domain's config directory) and if the user does not specify "-xml path-to-acc-config-file" on the appclient command then the ACC will look for glassfish-acc.xml in the domain's config directory as the default. (Prior to these changes it would look for sun-acc.xml.)

If a user does an in-place update from 3.1 to 3.1.2, then the glassfish-acc.xml file will not appear in the domain's config directory. To support this use case the ACC will continue to use the sun-acc.xml file as the default ACC config file if it cannot find glassfish-acc.xml. Note that the user can always control what config file the ACC will read using the -xml option on the appclient command.

Comment by Tim Quinn [ 18/Nov/11 ]

Rebecca,

Upon further review, the small incompatibility that we'd introduce by making these changes in 3.1.2, given that this is a bug release, is one we should not create.

So I'm going to revert the changes for this in he 3.1.2 code base. We will not make the file name changes in 3.1.2.

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.





[GLASSFISH-15713] [UB]Non-sticky Load Balancer not supported in GlassFish HA Created: 27/Jan/11  Updated: 19/Dec/16

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1_dev
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Rajiv Mordani Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-approved, 3_1-need_more_info

 Description   

Need to document that when GlassFish is front ended with a non sticky load balancer HA is not supported. It may result in some data loss. Please see bug
http://java.net/jira/browse/GLASSFISH-15575



 Comments   
Comment by Paul Davies [ 27/Jan/11 ]

Reassigned to sfordin. Corrected typo in tag.

Comment by Scott Fordin [ 11/Feb/11 ]

With all the back-and-forth in the comments on this issue, it is unclear to me what actually needs to be said in the docs here, and even in which doc this issue would be most appropriately discussed. Can someone please advise me here?

Comment by Scott Fordin [ 17/Mar/11 ]

Second request: I still need more information to document this issue. It is not clear to me what needs to be said here and where it needs to be said. Can someone please advise?

Comment by Scott Fordin [ 31/May/11 ]

Reassigning to Paul Davies.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16166] [UB]GlassFish Admin Guide should document use of GenericJMSRA with Message Queue Created: 07/Mar/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Nigel Deakin Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The GlassFish 3.1 Administration Guide does not describe how to use the Generic Resource Adapter for JMS (GenericJMSRA) to connect to GlassFish Message Queue, even though this is supported.

The only documentation for GenericJMSRA is a section
"Using the Generic Resource Adapter for JMS to Integrate Supported External JMS Providers"
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gbtvg.html

This describes GenericJMSRA generically and then gives detailed configuration information for WebLogic JMS and IBM WebSphere MQ. However there is no equivalent section for GlassFish Message Queue.

Such a section should mention that when using GlassFish Message Queue, both jndi and javabean integration modes are supported, and what settings are needed in the two cases.



 Comments   
Comment by Mike Fitch [ 19/Jul/11 ]

Setting Fix Version to "future release", as the scope of 3.1.1 is limited to bug fixes, and this is issue requests additional content, not corrections to existing content.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





information from get-health is not displayed (GLASSFISH-17570)

[GLASSFISH-17811] get-health support Created: 23/Nov/11  Updated: 26/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: future release

Type: Sub-task Priority: Major
Reporter: Anissa Lam Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

refer to main task for UI changes



 Comments   
Comment by Rebecca Parks [ 07/Dec/11 ]

The engineering task of which this is a subtask has been deferred to a future release. I don't seem to have the permissions to defer this issue accordingly. Please defer this issue on my behalf or tell me how to do it. I want it out of my query for 3.1.2 please. Reassigning so you'll see my comment and act on it instead of ignoring it.

Comment by Anissa Lam [ 07/Dec/11 ]

set to future release to match main task.

Comment by Rebecca Parks [ 07/Dec/11 ]

Thanks, Anissa!





Provide UI to allow editing of web-context-param and env-entry (GLASSFISH-17622)

[GLASSFISH-17807] OLH: allow editing of web-context-param and env-entry Created: 23/Nov/11  Updated: 26/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: future release

Type: Sub-task Priority: Major
Reporter: Anissa Lam Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

refer to main task for any UI changes






[GLASSFISH-17806] [UB]Docs need to be corrected to reflect the supported OS and Webserver matrix for LB Created: 23/Nov/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: varunrupela Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-16490 [UB]Additional Instructions for setti... Open
is related to GLASSFISH-16491 [UB]Additional Instructions for setti... In Progress
Tags: 312_qa

 Description   

The "Supported Operating Systems and Webservers" for LB needs correction in the "Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide".

The supported matrix is available at:
http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/GlassFish+3.1.x+Loadbalancer+plugin

For example: The doc indicates support for 32 bit Webservers on Linux, while that is not the case for GF 3.1.1.



 Comments   
Comment by Mike Fitch [ 10/Jan/12 ]

Added [UB] to summary, as this issue applies to unbundled (i.e., not online or inline help) documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17287] [UB]General Vulnerability Assessment -> NonIntrusive -> Web Server Created: 12/Sep/11  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: v3.0.1
Fix Version/s: v3.0.1

Type: Bug Priority: Major
Reporter: fraggie Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris 10, SPARC and X86


Tags: Assessment, General, Glassfish, Security, Vulnerability

 Description   

The following security flaw has been identidfied:

http://www.mcafee.com/us/resources/release-notes/foundstone/fsl_05_11_2011.pdf11907 - Oracle Sun Products Suite Glassfish Denial Of Service

Category: General Vulnerability Assessment -> NonIntrusive -> Web Server

Risk Level: High

CVE: CVE-2011-0807

DISA IAVA: 2011-A-0054

Description

A denial of service vulnerability is present in some versions of Oracle Sun GlassFish Enterprise Server and Sun Java System

Application Server.

Observation

A denial of service vulnerability is present in some versions of Oracle Sun GlassFish Enterprise Server and Sun Java System

Application Server.

Oracle Sun GlassFish Enterprise Server 2.1, 2.1.1, and 3.0.1, and Sun Java System Application Server 9.1 are prone to a

unspecified vulnerability related to Administration. Successful exploitation could allow an attacker to cause a denial of service

This may be already fixed, but is not evident in the latest release notes:

Glassfish 3.1 release note: http://java.net/jira/secure/ReleaseNote.jspa?projectId=10231&version=10968

Glassfish 3.1.1 release note: http://glassfish.java.net/docs/3.1/release-notes.pdf



 Comments   
Comment by Shing Wai Chan [ 12/Sep/11 ]

From http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-0807 , we have

Unspecified vulnerability in Oracle Sun GlassFish Enterprise Server 2.1, 2.1.1, and 3.0.1, and Sun Java System Application Server 9.1, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Administration.

I have confirmed from admin team that this has been fixed in 3.1 and 3.1.1.

Comment by fraggie [ 13/Sep/11 ]

Hi Shing Wai Chan,

Thank you for that and the prompt reply, much appreciated.

One last thing, would it be possible for you to highlight where is states in the release notes that this has been fixed?

(Just for our records).

Regards,
Dónal

Comment by Bhakti Mehta [ 14/Oct/11 ]

Assigning to Shingwai for more input on the submitter's question

Comment by Anissa Lam [ 18/Oct/11 ]

As stated above, the bug exists in
Oracle Sun GlassFish Enterprise Server 2.1, 2.1.1, and 3.0.1, and Sun Java System Application Server 9.1
but not in v3.1 and 3.1.1.

3.1 and 3.1.1 ships before the bug was discovered/reported, thus the release notes of those release doesn't mention about that.

I am transferring this to doc. If they think this should be mentioned in the release note of next release, they can add that in.

Comment by Rebecca Parks [ 12/Dec/11 ]

It sounds to me like it's the Release Notes for 3.1/3.1.1 that need to be fixed. It's too bad I didn't look at this bug sooner, I just updated the 3.1/3.1.1 Release Notes. I think I can get this added for the next patch, scheduled for 1/13/12.

If it's added to the 3.1/3.1.1 Release Notes, it seems to me that it doesn't need to be in the 3.1.2 Release Notes as well, but I'd like to hear other opinions.

Comment by Rebecca Parks [ 04/Jan/12 ]

I checked with the doc team, and it is unfixed bugs that appear in the Release Notes, not fixed ones. So this would go in the SGES 2.1.1, SGCS 2.0, and OGS 3.0.1 Release Notes. I am currently updating the 2.1.1/2.0 Release Notes, so I will retarget this bug to 3.0.1.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Rebecca Parks [ 06/Mar/12 ]

Changed the fix version back to 3.0.1. This needs to be added to the 3.0.1 Release Notes at the next patch update.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.

Comment by Rebecca Parks [ 07/Mar/12 ]

Please don't make me do this AGAIN.

Comment by Mike Fitch [ 16/Feb/13 ]

As this applies to unbundled documentation, moving to 4.0.1

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 3.0.1 as per Rebecca's comment of 06/Mar/12 10:41 PM:

Changed the fix version back to 3.0.1. This needs to be added to the 3.0.1 Release Notes at the next patch update.





[GLASSFISH-17726] [UB]document IE security settings to load Admin Console remotely Created: 15/Nov/11  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_dev
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: lidiam Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows xp, IE 7


Attachments: JPEG File ie-cantload-security-tls.JPG    

 Description   

Admin Console cannot be loaded with IE 7 default settings. A generic page is displayed instead saying that "Internet Explorer cannot display the webpage". Steps to reproduce:

1. Install Glassfish b10 on some remote machine.
2. Start domain: asadmin start-domain.
3. Change admin password, if blank, by running asadmin change-admin-password command.
4. Enable secure administration: asadmin enable-secure-admin.
5. Restart the domain (asadmin stop-domain, asadmin start-domain).
6. On a windows machine bring up IE 7 and enter Admin Console url: http://<host>:4848
7. A page is displayed saying that "Internet Explorer cannot display the webpage" (screenshot attached).

The same page has more details and among them the following:

"If this is an secure (HTTPS) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section."

In my IE 7 TLS is not enabled by default. After enabling TLS Admin Console comes up. It is not intuitive to know that this is the issue for the user, cause the url that one is trying to access is http not https. The problem is because of the redirect, but the user may not know/realize that.

I'm not sure we can do anything about this. If not, we should at least document this issue.



 Comments   
Comment by Anissa Lam [ 15/Nov/11 ]

Thats a good point.
This may not be just for IE7, since IE8 (or other browser) will require the same settings. Regardless what is the default settings, we should document this.
With the security requirement changes in 3.1.2, maybe there is a section/chapter that dedicated for the changes. This should be added to such chapter, besides any other doc that the doc team believes this kind of info should go.

Comment by Paul Davies [ 15/Nov/11 ]

We should restrict the documentation for this issue to the behavior of GlassFish Server: namely explain when the url is re-directed from http://<host>:<port> to https://<host>:<port>.

We should avoid documenting in the GlassFish Server documentation standard browser behavior. Instead we should refer users to the browser help for that information.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17605] asadmin manual page is hardcoded for GlassFish Created: 03/Nov/11  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: Tom Mueller Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7ri_cleanup_deferred, nucleus-cleanup

 Description   

The administrative CLI for nucleus, known as asadmin, is actually a generic tool that is the interface for any nucleus-based product. Within nucleus, it is called "nadmin" for nucleus admin. However, it is intended to be "skinned" for each product based on nucleus, e.g., asadmin for the app server.

The output of nadmin -? is the manual page for the command. This manual page has "asadmin" embedded in it with references to Oracle GlassFish Server, i.e., it is branded for the GF product. This needs to either be made generic or the content of the manual page has to vary depending on the product that is using it.

This bug is for figuring out how to solve this problem.



 Comments   
Comment by Tom Mueller [ 14/Mar/12 ]

Other asadmin-related strings (besides command name and product name) in the manual page are:

  • Environment variable names such as AS_ADMIN_TERSE, AS_ADMIN_HOST
  • Prefixes for passwords, e.g., AS_ADMIN_PASSWORD. Note that this may effect the documentation for subcommands too, if they state the name of an environment variable that can be used to pass a value. For example, consider create-file-user and AS_ADMIN_USERPASSWORD.

Note: the documentation for the -W option in the asadmin manual page references configure-jms-cluster command which is not in nucleus. Also, the examples use create-jdbc-connection-pool.





Lack Of JNDI Browser In Admin UI (GLASSFISH-5842)

[GLASSFISH-17928] OLH for Jndi Browser Created: 08/Dec/11  Updated: 26/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: future release

Type: Sub-task Priority: Major
Reporter: Anissa Lam Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Please refer to the main task for UI changes.



 Comments   
Comment by Rebecca Parks [ 13/Dec/11 ]

Main issue deferred, deferring this issue as well.





[GLASSFISH-16699] (JDK) NLS: Crashed when tried to install the bundle in ko locale Created: 23/May/11  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.1_dev
Fix Version/s: None

Type: Bug Priority: Major
Reporter: sunny-gui Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Solaris 11 express x86
Bundle: java_ee_sdk-6u3-web-b05-jdk-solaris-x86-ml.sh
Locale: ko


Attachments: JPEG File crash_ko.jpg     Text File hs_err_pid1356.log    
Tags: 3_1-next_release-note-added, 3_1-next_release-notes, 3_1_1-scrubbed, 3_1_2-release-note-added, 3_1_2-release-notes, glassfish, installer

 Description   

Issue: The program crashed when tried to install the bundle "java_ee_sdk-6u3-web-b05-jdk-solaris-x86-ml.sh" in ko locale

To reproduce:
1. Run ./java_ee_sdk-6u3-web-b05-jdk-solaris-x86-ml.sh with unset JAVA_HOME
System says:
Could not locate a suitable jar utility.
Please ensure that you have Java 6 or newer installed on your system
and accessible in your PATH or by setting JAVA_HOME
2. Run export JAVA_HOME=Java_Install_Home
3. Run ./java_ee_sdk-6u3-web-b05-jdk-solaris-x86-ml.sh
System will pop ups install GUI, but it crashed when I click on Next button.
Please find attached screen shot for your reference.

I also tried in en and zh_CN locales, and this issue was not reproducible in those locales.



 Comments   
Comment by gmurr [ 23/May/11 ]

This seem to be x86/locale specific issue. I tried java_ee_sdk-6u3-web-b05-jdk-linux-x64-ml.sh in ko_KR.UTF8. I did not see any crash.
Sunny, could you please try the same installer in other locales, also in ko_KR.euc

Comment by sunny-gui [ 23/May/11 ]

I tried in another 7 locales, and this issue is reproducible in zh_TW.UTF-8.

Comment by scatari [ 24/May/11 ]

Assigning to Snjezana for further investigation.

Comment by sunny-gui [ 24/May/11 ]

I tried with the bundle "java_ee_sdk-6u3-b05-jdk7-solaris-x86-ml.sh" in zh_CN.UTF-8, zh_TW.UTF-8, ko_KR.UTF-8 and en_US.UTF-8 in the same environment, this issue is reproducible in ko and zh_TW locales.

Comment by Snjezana Sevo-Zenzerovic [ 01/Jun/11 ]

Given that this is actually JDK crash, could you try pointing JAVA_HOME to the latest JDK version (JDK 6u26) and see if the problem persists?

Comment by Snjezana Sevo-Zenzerovic [ 01/Jun/11 ]

And could you please attach JDK error report file?

Comment by sunny-gui [ 01/Jun/11 ]

I installed the jdk-6u26-fcs-bin-b03 bundle which downloaded from http://javaweb.us.oracle.com/java/re/jdk/1.6.0_26/latest/bundles/solaris-i586/.

This issue is still reproducible. Attached the JDK error report for your reference.

Comment by Snjezana Sevo-Zenzerovic [ 13/Jun/11 ]

I checked some similar JDK bug reports and it looks like this may be simply OS patch level issue. I'll try to find out what is the minimal patch/update level that is supposed to resolve this.

Comment by Snjezana Sevo-Zenzerovic [ 27/Jun/11 ]

This issue will have to be release noted in 3.1.1 release since it has to be addressed either in JDK or (more likely) in Solaris 11 patch.

Potential workarounds are:

  • Open Source Edition and Oracle GlassFish users could install in affected OS/locale combinations using zip distribution or temporarily switch to unaffected locale.
  • SDK users could temporarily switch to alternative locale or install SDK content using Update Center (SDK distribution exposure on this particular platform is not significant).
Comment by Rebecca Parks [ 07/Jul/11 ]

Added to the 3.1.1 Release Notes:

(JDK) NLS: Crashed when tried to install the bundle in ko locale (16699)

Description

Installation of the Solaris x86 SDK bundle fails in the ko and zh_TW locales.

Workaround

GlassFish Server users can install the ZIP distribution or temporarily switch to an unaffected locale. SDK users can install using the Update Center or temporarily switch to an unaffected locale.

Comment by scatari [ 08/Dec/11 ]

Please continue to document this in 3.1.2 release notes as the issue cannot be resolved in GlassFish code base.

Comment by Snjezana Sevo-Zenzerovic [ 14/Dec/11 ]

RN issue, reassigning to docs team.

Comment by Rebecca Parks [ 24/Jan/12 ]

All 3.1.1 Release Notes issues are automatically carried over to 3.1.2 unless they are fixed in 3.1.2. There was no need to flag this.

Comment by Rebecca Parks [ 31/Jan/12 ]

This seems to be related to issues 16304 and 16700.





[GLASSFISH-16491] [UB]Additional Instructions for setting up LB on OEL+ OHS 64-bit to be included Created: 27/Apr/11  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs, load_balancer
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Jothir Ganesan Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OEL + OHS 64-bit + Glassfish lb plugin


Issue Links:
Related
is related to GLASSFISH-17806 [UB]Docs need to be corrected to refl... Open
Tags: 3_1-next_need-more-info

 Description   

I configured lb plugin on 64-bit OHS according to the instructions given in
http://download.oracle.com/docs/cd/E18930_01/html/821-2426/gktke.html

When I start OHS, the https listeners of the instances are being detected as unhealthy.

Need to add the following to bin/apachectl script:
NSS_STRICT_NOFORK=DISABLED; export NSS_STRICT_NOFORK



 Comments   
Comment by Scott Fordin [ 18/May/11 ]

We clearly state at the beginning of "Configuring Web Servers for HTTP Load Balancing" chapter in the HA Admin Guide that, "The Loadbalancer Plug-In does not support web servers running in 64–bit mode, except for Microsoft IIS with 32–bit application support enabled." We also state in the "Configuring Oracle HTTP Server" instructions in that same chapter that, "These procedures apply to Oracle HTTP Server 11.1.1.4+ (32–bit) only. Other versions of Oracle HTTP Server are not supported." So I guess I'm confused. Do we now want to say that we support 64-bit? If so, this will require changes in several locations, not just this one bit in one particular step.

Comment by Scott Fordin [ 31/May/11 ]

Reassigning to Paul Davies.

Comment by kshitiz_saxena [ 14/Jul/11 ]

This issue is not specific to 64 bit OHS. This change is generic. Please capture is under point 3.

Comment by Mike Fitch [ 19/Jul/11 ]

Information added as per Description

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16490] [UB]Additional Instructions for setting up LB on Solaris 10 Sparc + apache 64-bit to be included Created: 27/Apr/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs, load_balancer
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Jothir Ganesan Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris 10 Sparc + Apache 64-bit with OpenSSl


Issue Links:
Related
is related to GLASSFISH-17806 [UB]Docs need to be corrected to refl... Open
Tags: 3_1-next_need-more-info

 Description   

Configure openssl as below :
1. ./Configure shared --openssldir=<openssl-install-dir> --prefix=<openssl-install-dir> solaris64-sparcv9-cc
2. make
3. make install

Configure Apache as below:
export CFLAGS="-m64"
export LDFLAGS="-m64"
export LD_LIBRARY_PATH=/usr/lib/64:/usr/sfw/lib/64
use sun studio compiler instead of gcc for 64-bit:
1../configure --with-mpm=worker --with-included-apr --with-ssl=/export/kshitiz/64bit/openssl/install --prefix=/export/kshitiz/64bit/apache2.2/install --enable-ssl --enable-so CC=/usr/dist/share/sunstudio_sparc/SUNWspro/bin/cc

2. make
3. make install



 Comments   
Comment by Scott Fordin [ 18/May/11 ]

Similar comment to http://java.net/jira/browse/GLASSFISH-16491, we clearly state at the beginning of "Configuring Web Servers for HTTP Load Balancing" chapter in the HA Admin Guide that, "The Loadbalancer Plug-In does not support web servers running in 64–bit mode, except for Microsoft IIS with 32–bit application support enabled." We also state in the "Configuring Apache HTTP Server" instructions in that same chapter that, "The Loadbalancer Plug-In supports Apache HTTP Server 2.2.x (32–bit)." So I guess I'm confused. Do we now want to say that we support 64-bit? If so, this will require changes in several locations, not just this one bit in one particular step.

Comment by Scott Fordin [ 31/May/11 ]

Reassigning to Paul Davies.

Comment by kshitiz_saxena [ 14/Jul/11 ]

In 3.1.1, we support 64 bit load-balancer plugin. Please refer to issue GLASSFISH-16905.

Comment by Mike Fitch [ 19/Jul/11 ]

Pushing this issue to "future release". For 3.1.1, description of 64-bit LBP support is limited to the Release Notes.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17178] [UB]Glassfish 3.1.1 with JK Listener enabled throws exception of NoSuchThreadPool when EJB is deployed Created: 10/Aug/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs, web_container
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: vin4bacchus Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS X Lion, Windows 7 32bit



 Description   

Glassfish 3.1.1 build12 with a JK Listener enabled and set to thread-pool-1 throws NoSuchThreadPool exception when EJB is deploy individually or as part of an EAR.

Tested on multiple environments standalone and via Eclipse plugin. Same results each time. Reproducible every time.
Deploying applications with no EJBs has no issue.
Removing JK Listener resolves the problem.

Steps to reproduce.
1) New Glassfish 3.1.1 (build 12) install from zip.
2) Configure JK Listener on port 8009 on address 0.0.0.0 with thread-pool-1 as thread pool on server "server".
3) Create test EJB Project in Eclipse with one Hello World type method with both local and remote interfaces.
4) Export test EJB Project to JAR.
5) Deploy from web interface Applications menu.

Exception details below:
WARNING: No default ThreadPool defined
com.sun.corba.ee.spi.orbutil.threadpool.NoSuchThreadPoolException
at org.glassfish.enterprise.iiop.util.S1ASThreadPoolManager.getThreadPool(S1ASThreadPoolManager.java:246)
at org.glassfish.enterprise.iiop.util.S1ASThreadPoolManager.getDefaultThreadPool(S1ASThreadPoolManager.java:276)
at org.glassfish.enterprise.iiop.impl.PEORBConfigurator.configure(PEORBConfigurator.java:138)
at com.sun.corba.ee.impl.orb.ORBConfiguratorImpl.runUserConfigurators(ORBConfiguratorImpl.java:185)
at com.sun.corba.ee.impl.orb.ORBConfiguratorImpl.configure(ORBConfiguratorImpl.java:170)
at com.sun.corba.ee.impl.orb.ORBImpl.postInit(ORBImpl.java:625)
at com.sun.corba.ee.impl.orb.ORBImpl.set_parameters(ORBImpl.java:704)
at com.sun.corba.ee.impl.orb.ORBImpl.setParameters(ORBImpl.java:691)
at com.sun.corba.ee.spi.osgi.ORBFactory.initialize(ORBFactory.java:107)
at org.glassfish.enterprise.iiop.impl.GlassFishORBManager.initORB(GlassFishORBManager.java:581)
at org.glassfish.enterprise.iiop.impl.GlassFishORBManager.getORB(GlassFishORBManager.java:263)
at org.glassfish.enterprise.iiop.impl.GlassFishORBFactoryImpl.createORB(GlassFishORBFactoryImpl.java:93)
at org.glassfish.enterprise.iiop.api.GlassFishORBHelper.getORB(GlassFishORBHelper.java:152)
at org.glassfish.enterprise.iiop.api.GlassFishORBHelper.getProtocolManager(GlassFishORBHelper.java:219)
at com.sun.ejb.containers.BaseContainer.initializeProtocolManager(BaseContainer.java:818)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:566)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:155)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:149)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:105)
at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:230)
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:290)
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:101)
at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:186)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:257)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:382)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1064)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1244)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1232)
at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:202)
at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:195)
at org.glassfish.admin.rest.resources.TemplateListOfResource.createResource(TemplateListOfResource.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer._service(GrizzlyContainer.java:182)
at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer.service(GrizzlyContainer.java:147)
at org.glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java:184)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:238)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:828)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:725)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:680)



 Comments   
Comment by Hong Zhang [ 10/Aug/11 ]

Not sure if it's an ejb issue or orb issue, assign to ejb team for initial evaluation.

Comment by Cheng Fang [ 10/Aug/11 ]

Can you try not specifying threadpool option when creating the listener? Or use "http-thread-pool".

thread-pool-1 is for servicing IIOP requests and for resource adapters to service work management requests.

Comment by vin4bacchus [ 10/Aug/11 ]

"thread-pool-1" was chosen because default "http-thread-pool" only has a max of 5 threads and choosing this pool threw a warning in the logs about not large enough max thread pool for AJP listener.

Upped "http-thread-pool" max threads to 50 and assigned the AJP JK Listener to it and tested on sample EJB project ok.
This appears to have solved the issue by using a different thread pool than "thread-pool-1".

Comment by Cheng Fang [ 10/Aug/11 ]

transfer to doc team to clarify. The following is what I observed. You may want to check with web container team:

do not use the build-in thread-pool-1 for any network-listener;

if users do not specify a threadpool for the jk listener, the default threadpool used is http-thread-pool. And users also need to up the max size for http-thread-pool from 5 to a bigger number.

users can also create a new thread pool with create-threadpool command with decent max size, for jk listener.

Comment by vin4bacchus [ 10/Aug/11 ]

Only one clarification. The default thread pool for a new JK Listener is actually the "admin" thread pool.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-21122] 4.0.1: Update default index.html and files in glassfish/docs Created: 09/Jul/14  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.1_dev
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Joe Di Pol Assignee: sbcaruso
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by GLASSFISH-21153 static copyright.html is missing from... Resolved
Tags: 4_0_1-mustfix

 Description   

We need to update the default index.html and files in glassfish/docs. Somethings to check/fix:

  • Copyright date (2013 to 2014)
  • GlassFish version (4.0 to 4.0.1)
  • Any other tweaks we think we should make

An FYI: these documents are not in the main GlassFish workspace. They are in a doc workspace:

https://svn.java.net/svn/glassfish~svn/trunk/main-docs

and are binary integrated (ugh) into the GlassFish build.



 Comments   
Comment by David Delabassee [ 09/Jul/14 ]

glassfish/docs/quickstart.html :

  • update the link to the 4.0.1 release notes
  • update the link "Starting and Stopping the Default Domain", it still points to 3.1.2 doc
  • 'Oracle GlassFish Server Application Deployment Guide' link is 404
  • remove the 'GlassFish Quality Community' section
Comment by David Delabassee [ 05/Aug/14 ]

The default "Your server is now running" page has

  • at the bottom right a dead "Legal Notices" link
  • 2010-2013 copyright
Comment by Romain Grécourt [ 05/Aug/14 ]

link related issue

Comment by Joe Di Pol [ 11/Aug/14 ]

I've made the following updates (some of these were done a few weeks ago):

  • change version to 4.1
  • changed the 3.1.2 doc links to point to the 4.0 pdfs
  • Removed the GlassFish Quality Community section
  • Updated copyright dates to 2014

Stephanie should still do a final review (and 21153 is still an issue, but likely existed in 4.0 as well).





[GLASSFISH-20940] create-file-user password option for --passwordfile isn't documented on Glassfish 4 Created: 23/Dec/13  Updated: 23/Dec/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: 3.1.1

Type: Bug Priority: Major
Reporter: atrajano Assignee: kevinmcd
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

To pass in the password for a user to the create-file-user command, the method is to use the --passwordfile option with the following variable:

AS_ADMIN_USERPASSWORD=mypassword

This isn't documented in the manual page for create-file-user, specifically, that the name of the variable in the password file is AS_ADMIN_USERPASSWORD.

This bug was prompted by issue GLASSFISH-16277 which is related to using create-file-user in embedded mode. However, this documentation fix is intended to deal with the CLI case. For the embedded case, once 16277 is resolved, then the embedded documentation needs to be updated with an explanation of how to pass a password to an embedded command.



 Comments   
Comment by atrajano [ 23/Dec/13 ]

help create-file-user on asadmin does not talk about the --passwordfile option

SYNOPSIS
create-file-user [--help] [--authrealmnameauth_realm_name]
[--target target
[--groups user_groups[:user_groups]*] user_name





[GLASSFISH-20719] Admin doc does not discuss effects of non-root account trying to administer DAS started from root Created: 22/Jul/13  Updated: 22/Jul/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Tim Quinn Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

(as Paul requested...)

The Admin Guide seems not to talk about the effects of trying to use a non-root account to administer a domain started with the root user.






[GLASSFISH-20475] [UB] Add release notes documentation concerning the state of the embedded features for 4.0 OSE Created: 06/May/13  Updated: 20/Dec/16

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Tom Mueller Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-release-notes, 4_0-release-notes-completed, 4_0-release-notes-drafted

 Description   

This issue is for making sure the release notes for the 4.0 OSE release describe the anticipated level of testing and quality for the embedded feature.



 Comments   
Comment by Mike Fitch [ 17/May/13 ]

Added the following to the release notes:

Note:
The main thrust of the GlassFish Server Open Source Edition 4.0 release is to provide an application server for developers to explore and begin exploiting the new and updated technologies in the Java EE 7 platform. Thus, the following features of GlassFish Server were not a focus of this release:

  • Clusters and standalone instances
  • High availability features
  • Upgrade
  • Embedded Server

These features are included in the release, but they may not function properly with some of the new features added in support of the Java EE 7 platform.





Support Implicit CDI enabled property during application deployment (GLASSFISH-20614)

[GLASSFISH-20615] OLH: add info for this newly added field Created: 06/Jun/13  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Sub-task Priority: Major
Reporter: Anissa Lam Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

refer to parent issue.






[GLASSFISH-20556] (Bundled docs) On localhost:8080 index page, Legal Notice link is broken Created: 17/May/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: Alex Pineda Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

See the problem using glassfish-4.0-b89-windows.exe & glassfish-4.0-b89-unix.sh builds, using Windows 7 and OEL6 systems, Firefox browser (latest), JDK 1.7.0_21



 Description   

After completing the Installation of Glassfish, go to the URL http://localhost:8080. Once the (GlassFish Server) page is displayed, go toward the bottom righ hand side of it and select "Legal Notices" link. It points to URL http://localhost:8080/copyright.html. After selecting it, the following error is displayed

"HTTP Status 404" further down it notes "The requested resource is not available"



 Comments   
Comment by Joe Di Pol [ 21/May/13 ]

At this point, probably not a stopper for 4.0, but worth evaluating to see if we can fix this if there is a respin for some other reason.

Comment by Snjezana Sevo-Zenzerovic [ 22/May/13 ]

So, this really looks like an issue with default index.html file which is delivered as part of bundled docs. Reassigning accordingly. Not sure how feasible it is to pick up fresh bundled docs drop, even if we do end up with another respin.

Comment by Paul Davies [ 22/May/13 ]

Any fix that involves adding a copyright.html page to the bundled docs relies on create-domain to copy the page to the appropriate place under docroot. Similarly, the page must also be included in any default domain that the installers create.

Comment by Mike Fitch [ 22/May/13 ]

This issue is not a regression: GlassFish 3.1.2 (and even earlier releases) exhibit this problem. Therefore, I am changing the fix version to 4.0.1.

As a workaround to this problem, an administrator can copy the file <as-install>/docs/copyright.html to <domain-dir>/docroot/.





[GLASSFISH-20081] [UB] javax.ejb.NoSuchEJBException in unsyncpcsfsb with ha Created: 27/Mar/13  Updated: 20/Dec/16

Status: Reopened
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: sherryshen Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHL6.2 and JDK1.7.0_10



 Description   

The problem was reported in
http://java.net/jira/browse/GLASSFISH-20020
which can't be accessed for a few days.
Hence, file this bug for failure analysis.
Will close the 20020 later.



 Comments   
Comment by sherryshen [ 27/Mar/13 ]

glassfish-4.0-b82-03_23_2013.zip
During the test dev and failure analysis for
http://java.net/jira/browse/GLASSFISH-20011
I observed javax.ejb.NoSuchEJBException in unsyncpcsfsb with ha.

To run tests, to see env in
http://java.net/jira/browse/GLASSFISH-20011

test2, persist, joinTx, no flush

test2 without ha, passed.
do "ant ee all-dbg"

test2 with ha, failed.
web.xml has <distributable/>
deploy war with --availabilityenabled=true
do "ant ee all-dbg-ha"

server.log from instance2

Error during checkpoint ([TestEJB]. Key:
[1f0090099dfa82de-ce0085b80d45218a-1])
[com.sun.ejb.containers.StatefulSessionContainer$EMNotSerializableException:
java.io.NotSerializableException:
org.eclipse.persistence.internal.jpa.EntityManagerImpl

.....
javax.ejb.NoSuchObjectLocalException: The EJB does not exist.
session-key: 1f0090099dfa82de-ce0085b80d45218a-1
at
com.sun.ejb.containers.StatefulSessionContainer._getContext(StatefulSessionContainer.java:1616)
at
com.sun.ejb.containers.BaseContainer.getContext(BaseContainer.java:2518)
at
com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1908)
.....
javax.ejb.NoSuchEJBException

Comment by sherryshen [ 27/Mar/13 ]

The JPA2.1 test info can be found at
http://aseng-wiki.us.oracle.com/asengwiki/display/ASQA/GF+4.0+Test+Development+Page
As a summary for the bugs on cluster.
1) SFSB tests passed on DAS.
Verified the fix for
http://java.net/jira/browse/GLASSFISH-19597
2) To wrap up my test dev, I ran SFSB tests on a cluster with using
different instances and reported
http://java.net/jira/browse/GLASSFISH-20011
3) Next, I enabled HA to see if it helps for 20011, but it failed with
http://java.net/jira/browse/GLASSFISH-20081
4) After, I tried a simple SFSB tests without JPA, it passed.

I have a hudson run to show to test env and problems.
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-lc-d/

#8 dbg failures
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-lc-d/8/artifact/appserver-sqe/reports/pe-ee/amd64_easqezorro5_Linux/html/test_results_ejb.html
The 3 tests are executed in the order below.
A) appserver-sqe/pe/ejb/ejb31/fo/sfsb, SFSB with HA, passed
B) appserver-sqe/pe/ejb/jpa20/war/unsyncpcsfsb, SFSB without HA, test2, passed.
C) appserver-sqe/pe/ejb/jpa20/war/unsyncpcsfsb, SFSB with HA, test2, failed. GLASSFISH-20081

#2, ejb-cluster with 1 failure, GLASSFISH-20011
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-lc-d/2/artifact/appserver-sqe/reports/pe-ee/amd64_easqezorro5_Linux/html/test_results_ejb.html

Comment by Mitesh Meswani [ 29/Mar/13 ]

As this is related to clustering, deferring this for 4.0.1. Ethan and Quiang will investigate further.

Comment by qiang.l.liu [ 17/Apr/13 ]

If the HA enabled, the SFSB container will try to store the ejb's session context for replication. When the container tries to serialize the context object, a NotSerializableException is thrown up:
com.sun.ejb.containers.StatefulSessionContainer$EMNotSerializableException: java.io.NotSerializableException: org.eclipse.persistence.internal.jpa.EntityManagerImpl, and the EJB is marked with destroyed. This is because the TestEJB has a reference of EntityManager. The EJB's context will be removed after it is marked destroyed. So, when a subsequence call to the EJB, the client will get NoSuchObjectLocalException.

Comment by qiang.l.liu [ 17/Apr/13 ]

After I putting "passivationCapable=false" on TestEJB, the test passed.

So, I'd like resolve the issue as work as designed.

Comment by sherryshen [ 18/Apr/13 ]

Thanks Qiang and Mitesh for the analysis for
http://java.net/jira/browse/GLASSFISH-20081

Here is what I understand the problem.

1) HA Limitation:
EntityManager can't be serialized as a context object in SFSB container for HA replication.
2) Workaround:
Update the @Stateful annotation on TestEJB
to @Stateful(passivationCapable=false), then
JPA will work in ha env without replication
or in non-ha env.

Where are these 2 points in the documents?

I verified the test passed on ha env without replication or non-ha env with b85 nightly.
http://javaweb.us.oracle.com/net/asqe-logs.us.oracle.com/export1/4.0/Results/build85/core/b20081/t1/html/test_results_ejb.html

Comment by sherryshen [ 18/Apr/13 ]

Copy the discussion about doc update.

On 4/17/2013 12:19 PM, Paul Davies wrote:
> Hi Mitesh,
>
> The corresponding section in the GlassFish 3.1.2 High Availability Administration guide is at:
>
> http://docs.oracle.com/cd/E26576_01/doc.312/e24934/session-persistence-and-failover.htm#abdlc .
>
> I have copied Mike Fitch on this response as he is leading the documentation effort for GF 4.0 and he should be able to advise how to proceed.
>
> Regards,
> -Paul
>
> On 4/17/2013 11:58 AM, Mitesh Meswani wrote:
>> Hi Paul,
>>
>> We would like to document the restriction that a SFSB injecting EntityManagers can not be passivated and failed over. Which document would it go to and who is the owner for that? We had a section on restrictions in GlassFish 2.1.1 High Availability Administration guide. I could not find a relevant section in GlassFish 3.1.2 High Availability Administration guide that documents such limitations.
>>
>> Thanks,
>> Mitesh

Comment by sherryshen [ 18/Apr/13 ]

Reopen for Mike Fitch to address the limitation in docs.

Comment by Mike Fitch [ 18/Apr/13 ]

Added [UB] to summary so this issue will appear in unbundled (ie, book-related) doc issues queries

Comment by Mike Fitch [ 18/Apr/13 ]

Also set Component to docs.

Comment by marina vatkina [ 18/Apr/13 ]

This behavior is per the EJB spec 3.2.





[GLASSFISH-20011] [UB] joinedTx missed data from another instance Created: 23/Mar/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: sherryshen Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHL6.2 and JDK1.7.0_10


Tags: 4_0-release-notes, 4_0-release-notes-completed, 4_0-release-notes-drafted

 Description   

joinedTx missed data from another instance

glassfish-4.0-b82-03_23_2013.zip

With the fix for
http://java.net/jira/browse/GLASSFISH-19597
appserver-sqe/pe/ejb/jpa20/war/unsyncpcsfsb
tests passed on das, or using one cluster instance,
but got 1 failure on using 2 cluster instances of cluster.
I will provide test details next.



 Comments   
Comment by sherryshen [ 23/Mar/13 ]

To use sqe-cluster env, please refer II B.
http://aseng-wiki.us.oracle.com/asengwiki/display/ASQA/4.0+Core+Test+Instructions

In sqe-cluster env, to reproduce the problem in test dir
appserver-sqe/pe/ejb/jpa20/war/unsyncpcsfsb
do "ant ee all_run2" and see failure with using 2 instances.
test1: passed
persist data1, not joinedTx, em.flush from instance1
verify db without data1

test2: passed
persist data2, joinedTx from instance2
verify db with data2

test3: failed.
persist data3, not joinedTx, from instance1
verify db without data3, passed.
verify db with data1, failed.

As a comparison,
do "all ee all_run1" and see tests all passed with using 1 instance.

Comment by Mitesh Meswani [ 26/Mar/13 ]

As this is related to clustering, deferring this for 4.0.1. Ethan and Quiang will investigate further.

Comment by sherryshen [ 27/Mar/13 ]

I enabled HA to see if it helps for 20011, but it failed
with a different error, see details in
http://java.net/jira/browse/GLASSFISH-20081

Comment by sherryshen [ 18/Apr/13 ]

Qiang has a very good description about tests. I am exploring how unsyncPC can
work in cluster env. Especially, how to make joinTx in test2 (instance2) to take care the data in test1 (instance1)?

On 4/17/2013 7:39 PM, Qiang Liu wrote:
> Hi Mitesh
> Ethan and I have discussed this test cases together before, and I can give a brief description for it:
>
> 1. The first request is sent to Instance 1, the EJB tries to persist Employee 1 and Employee 2 with not joining transaction, and then flush PC. An expected exception is caught.
>
> 2. The second request is sent to Instance 2, the EJB tries to persist Employee 3 and Emploee4 after join transaction. Even the flush is not invoked, the entities will be persisted to DB when the transaction is committed. But, since this is difference instance from Step 1, Employee 1 and Employee 2 will not be persisted to DB in this step.
>
> 3. The third request is sent to Instance 1, the EBJ tries to persist Employee 5 and Employee 6 without joining transaction, as it doesn't invoke the flush method, all the entities will not be persisted to DB. But, here the test case expects Employee 1 involved in PC in Step 1 will be persisted to DB in Step 2. Since the EM and PC will not be synced between instances in cluster env, so the test3 will not pass.
>
> Thanks
> -Qiang

Comment by sherryshen [ 01/May/13 ]

Mitesh, Ethan and I discussed this issue on April 29, 2013. We agreed
that the failure is due to the limitation of JPA2.1 feature,
unsynchronized persistence context.
It can be documented for 4.0 release, and addressed for later release.
Transfer the bug to docs.

Comment by ethan.wang [ 09/May/13 ]

After discussions with Mitesh and Sherry, we all agreed on following content to document:

Any updates to unsynchronized persistence context, while it's not joint to the current transaction is neither persisted to database nor replicated in cluster therefore subject to data loss. Developers should understand that before joining the PC with current transaction and the transaction being committed, all updates to the PC are only visible to the server instance which it resides and would not survive from server crash or fail over, so cautions should be exercised using unsynchronized PC in data critical application.

Comment by Mike Fitch [ 16/May/13 ]

Added 4_0-release-notes tag so this gets documented in the 4.0 release notes. Leaving the issue Open so the information can get integrated into the appropriate manual for the next release.

Comment by Gail Risdal [ 31/May/13 ]

Added the following to the release notes:

[UB] joinedTx missed data from another instance (20011)

Description
Updates made to an unsynchronized persistence context before it is joined to the current transaction and the transaction is committed are not persisted to a database or replicated in a cluster and data could be lost in the event of a server crash or failover.

Workaround
None. This is a limitation of the JPA 2.1 feature. Exercise caution when using an unsynchronized persistence context in a data-critical application.

Comment by Gail Risdal [ 05/Jun/13 ]

Revised release notes write-up slightly to now read:

Description
Updates made to an unsynchronized persistence context before it is joined to the current transaction and the transaction is committed are not persisted to a database or replicated in a cluster and data could be lost in the event of a server crash or failover.

Workaround
None. This is working as designed. The JPA 2.1 feature delays synchronization to a database until explicitly instructed to synchronize. Exercise caution when using an unsynchronized persistence context in a data-critical application.





[GLASSFISH-19831] Load Default button does not loads the default values Created: 12/Mar/13  Updated: 20/Dec/16

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: RameshT Assignee: Gail Risdal
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7/8 - IE 9 / 10


Tags: adminconsole, admingui, defaultbutton

 Description   

Load Defaults button does not make it default for "Format Exclude Fields"

Steps to reproduce :
1. Start Admin Console.
2. Navigate to Configurations -> server-config -> loggersettings
3. select some fields in "Format Exclude Fields"
4. Save the screen.
5. After saving the screen, now select Load Defaults.
6. Format Exclude Fields doesnot deselects the values selected.



 Comments   
Comment by Anissa Lam [ 12/Mar/13 ]

There is no default for "Format Exclude Fields". For any field that doesn't have default, the value will remain the same.
Works as designed.

Comment by RameshT [ 05/Apr/13 ]

The online help document is updated on build83. In this it is given as "The fields to exclude in log record. All fields are included by default". This is not working as it is expected. Hence reopening this issue.

I noticed something in the online document,this may helpful for improving the document.

It seems that , the default value details are given till Format Exclude Fields. After that for all other fields it is not given but works well for the defaults. ex. for the default fields are :

File Rotation Limit : 2000000 ( by default )
File Rotation Time Limit : 0 ( By default )
Flush Frequency : 1 ( By Default )
Maximum History Files : 0 ( By Default )
Log File : $

{com.sun.aas.InstanceRoot}

/logs/server.log ( By Default )
Log Handler : java.util.logging.ConsoleHandler ( By Default )

The above defaults can be included in the online document.

Comment by Anissa Lam [ 05/Apr/13 ]

We are talking about doc issues here.
Transferring to doc.

Comment by Gail Risdal [ 05/Apr/13 ]

Removed "All fields are included by default" for "Format Exclude Fields" in the OLH.

The change has been made in the documentation source but no further updates to the bundled documentation (man pages and OLH) are planned for the GlassFish 4.0 Open Source Edition release. Marking this 'In Progress' to record the fact that the work has already been done in the source and will be picked up when bundled docs are built/committed for a future release.





[GLASSFISH-19772] [UB] Add release notes documentation concerning the state of the clustering/HA features for 4.0 OSE Created: 05/Mar/13  Updated: 20/Dec/16

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Tom Mueller Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-release-notes, 4_0-release-notes-completed, 4_0-release-notes-drafted

 Description   

This issue is for making sure the release notes for the 4.0 OSE release describe the anticipated level of testing and quality for the clustering/HA feature.



 Comments   
Comment by Mike Fitch [ 14/Mar/13 ]

Added [UB] to summary so unbundled doc queries will pick up this issue.

Comment by Mike Fitch [ 17/May/13 ]

Added the following to the release notes:

Note:
The main thrust of the GlassFish Server Open Source Edition 4.0 release is to provide an application server for developers to explore and begin exploiting the new and updated technologies in the Java EE 7 platform. Thus, the following features of GlassFish Server were not a focus of this release:

  • Clusters and standalone instances
  • High availability features
  • Upgrade
  • Embedded Server

These features are included in the release, but they may not function properly with some of the new features added in support of the Java EE 7 platform.





[GLASSFISH-20260] ADMINGUI : view raw log information not described in online help document Created: 10/Apr/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: future release

Type: Bug Priority: Major
Reporter: RameshT Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WIN7 FF19 IE


Tags: admingui, docs, log, raw

 Description   

view raw log button information not described in the help document.

=========================
help document :
The General Information page contains the following information.

Stop Button

Click the Stop button to stop the GlassFish Server.
Restart Button

Click the Restart button to restart the GlassFish Server.
View Log Files Button

Click the View Log Files button to view log files for a GlassFish Server instance or cluster.
Rotate Log Button

Click the Rotate Log button to rotate the log file for the Admin Server (named server).
Recover Transaction Button

Click the Recover Transaction button to recover transactions for the Admin Server (named server) on the Recover Transactions page.
Secure Administration Button

Click the Secure Administration button to enable or disable secure administration on the Secure Administration page.
======================

In the above help document "View Raw Log" button not described.



 Comments   
Comment by Mike Fitch [ 10/Apr/13 ]

The problem mentioned in this issue predates GlassFish 4.0. According to Anissa, this button has been in the GUI since 3.1.2.

Moving this to "Future Release" because the final online help for GlassFish 4.0 has already been committed and is in translation.





[GLASSFISH-20259] AdminGUI : log viewer - search criteria - description Created: 10/Apr/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: future release

Type: Bug Priority: Major
Reporter: RameshT Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Win7 FF19 , IE


Tags: admingui, log, search, viewer

 Description   

server-> general -> view log files

In online help document.

Issue 1 :
Search criteria is given as :
The Search Criteria area contains the following options.

Advanced Search

Clicking this link opens an area that allows you to make additional refinements to the log viewer.

In the search criteria "Advanced Search" will not come. "Advanced Search" is an another topic. This has to be given in Advanced search section.

Issue 2 :
Here in search criteria the "text search" has not been explained.



 Comments   
Comment by Mike Fitch [ 10/Apr/13 ]

The two problems mentioned in this issue predate GlassFish 4.0. They were evident in GlassFish 3.x releases as well.

Moving this to "Future Release" because the final online help for GlassFish 4.0 has already been committed and is in translation.





[GLASSFISH-20376] Outdated link in Ch 11 Developing Connectors Created: 23/Apr/13  Updated: 23/Apr/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: marina vatkina Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

http://docs.oracle.com/cd/E26576_01/doc.312/e24930/connectors.htm#bealk

For connector examples, see http://developers.sun.com/appserver/reference/techart/as8_connectors.






[GLASSFISH-20365] Document guides are not available on the location specified Created: 22/Apr/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: RameshT Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Win 8 - IE 10 and OEL 6 - FF20 and WIN7-FF19 - all


Tags: 404, admingui, document, found, guide, not

 Description   

Administration Guide
Application Development Guide
Application deployment guide

The above Guides are not available on the appropriate locations.

Administration Guide - http://glassfish.java.net/docs/4.0/administration-guide.pdf
Application Development Guide - http://glassfish.java.net/docs/4.0/application-development-guide.pdf
Application deployment guide - http://glassfish.java.net/docs/4.0/application-deployment-guide.pdf

getting error as : HTTP 404 Not Found
=================================
The webpage cannot be found

HTTP 404

Most likely causes:
•There might be a typing error in the address.
•If you clicked on a link, it may be out of date.

What you can try:

Retype the address.

Go back to the previous page.

Go to and look for the information you want.

More information More information

====================================



 Comments   
Comment by Mike Fitch [ 23/Apr/13 ]

Set Fix Version to 4.0, as these links will not be live until GlassFish 4.0 is officially released.





[GLASSFISH-19077] [UB]Need to document how timeout is handled in XA transactions Created: 14/Sep/12  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: marina vatkina Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

If transaction timeout is set to a positive value, and it is an XA transaction a background thread is started that checks every 10 seconds (the value is currently not modifiable) if there are any timed-out transactions. The timed out transactions are marked as such, but the transaction is not marked for rollback. Because the transaction is not marked for rollback, the beforeCompletion callback is still being called, but then the transaction is rolled back. It is not an optimal behavior, but it doesn't break the spec.



 Comments   
Comment by Mike Fitch [ 16/Feb/13 ]

Added [UB] to summary and set fix version to 4.0.1 because this fix would be to unbundled documentation.

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.





[GLASSFISH-19163] [UB]Document -Dwriteout.xml=true option Created: 16/Oct/12  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: marina vatkina Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

From Hong's comments on GLASSFISH-17826:

Today you could use a system property to force the writing out of the generated descriptors for debug purpose (in the generated/xml directory like in v2), they are just no longer written out by default.
Add this jvm option to domain.xml and restart server before you deploy:
<jvm-options>-Dwriteout.xml=true</jvm-options>



 Comments   
Comment by Mike Fitch [ 16/Feb/13 ]

Added [UB] to summary and set fix version to 4.0.1 because this fix would be to unbundled documentation.

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.





[GLASSFISH-19134] Document that use of TimerWelcomeServlet will be depricated in the future Created: 09/Oct/12  Updated: 09/Oct/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: marina vatkina Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

See GLASSFISH-19059






[GLASSFISH-19297] [UB] Doc gives incorrect DTD prolog for GlassFish-specific app client deployment descriptor Created: 06/Nov/12  Updated: 14/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Tim Quinn Assignee: Mike Fitch
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

As mentioned in this stackoverflow post

http://stackoverflow.com/questions/13242300/what-is-the-correct-doctype-for-glassfish-application-client-xml

the doc here

http://docs.oracle.com/cd/E18930_01/html/821-2417/beaqo.html

gives the incorrect ID in the example for the GlassFish-specific app client DD.

Here is what the prolog should be using the most current DTD:

<!DOCTYPE glassfish-application-client PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Java EE Application Client 6.0//EN" "http://glassfish.org/dtds/glassfish-application-client_6_0-2.dtd">



 Comments   
Comment by Mike Fitch [ 14/Mar/13 ]

Added [UB] to summary, as this issue applies to unbundled documentation (as opposed to online help. Also, changed Fix Version to 4.0 so issue will show up on 4.0* queries. Actual commitment and build # TBD.





[GLASSFISH-19351] [UB]GlassFish Server 3.1 Administration Guide has incorrect steps for mod_jk Created: 15/Nov/12  Updated: 21/Sep/15

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2.2
Fix Version/s: 4.1.1

Type: Bug Priority: Major
Reporter: Ian Evans Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In To Enable mod_jk:
http://docs.oracle.com/cd/E18930_01/html/821-2416/gfaad.html
step 5 creates an http-listener on port 8009 with this asadmin command:

create-http-listener --listenerport 8009 --listeneraddress 0.0.0.0 --defaultvs server listener-name

Then in step 6, another network listener is created on port 8009:

create-network-listener --protocol http-listener-1 \
--listenerport 8009 --jkenabled true jk-connector

Step 5 is unnecessary if you're doing step 6, and results in an unstartable domain, as GlassFish attempts to create two listeners on port 8009.

The instructions should either be to create an http-listener as in step 5, then enable jk on that already-created listener like this:

set configs.config.server-config.network-config.network-listeners.network-listener.<listener name>.jk-enabled=true

or to use step 6, which does it all in one step.

It's also weird to not specify the listener name in step 5, but then to use an example listener name in step 6 ("jk-connector").



 Comments   
Comment by Ian Evans [ 15/Nov/12 ]

Also, step 6 assumes that the user is using a glassfish-jk.properties file in their domain, and not a workers.properties file with Apache httpd:

set server-config.network-config.network-listeners.network-listener.\
jk-connector.jk-configuration-file=domain-dir/config/glassfish-jk.properties

This command is unnecessary if you're configuring mod_jk on the Apache httpd side, and also uses an explicit listener name.

Comment by Paul Davies [ 16/Nov/12 ]

The target of the link in the description is the documentation for release 3.1. The corresponding section (To Enable mod_jk) in the documentation for release 3.1.2 has been updated and seems to address the duplication of the instruction to create a network listener in Step 5 and Step 6.

Comment by Ian Evans [ 16/Nov/12 ]

Paul, if you do a Google search for "glassfish mod_jk" you get the 3.1 doc as the very first link, with the title of "Administering mod_jk - Oracle GlassFish Server 3.1 Administration ...". I dug through the search results, and the 3.1.2 page (with the corrected info) is on page 4, with the far less useful title of "Administering Web Applications" (the chapter title, not the section). Links to older versions of the same section for GlassFish 3.0.1 and 2.1.1 appear on page 3 of the results. In between are a lot of blog entries, forum posts, and answer web site entries, all of them with more enticing titles than "Administering Web Applications".

In other words, the latest documentation is not only far down on the list, but maybe the least likely link to be clicked out of all of them. Perhaps this is something that should be addressed by the tools and web teams.





[GLASSFISH-18527] glassfish has a dependency on gsettings-desktop-schemas. Created: 18/Mar/12  Updated: 22/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: future release

Type: Bug Priority: Major
Reporter: crochery Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

slackware64 13.37
openjre 7 update 3
openjdk 7 update 3



 Description   

When I execute "asadmin start-domain --verbose", I see the following output.

asadmin> start-domain --verbose
Mar 18, 2012 8:49:54 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
-XX:+UnlockDiagnosticVMOptions
-XX:PermSize=64m
-XX:MaxPermSize=192m
-XX:NewRatio=2
-Xmx512m
-client
-javaagent:/misc/data/glassfish3/glassfish/lib/monitor/flashlight-agent.jar
-Dosgi.shell.telnet.maxconn=1
-Dfelix.fileinstall.disableConfigSave=false
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Dfelix.fileinstall.dir=/misc/data/glassfish3/glassfish/modules/autostart/
-Djavax.net.ssl.keyStore=/misc/data/glassfish3/glassfish/domains/domain1/config/keystore.jks
-Dosgi.shell.telnet.port=6666
-Djava.security.policy=/misc/data/glassfish3/glassfish/domains/domain1/config/server.policy
-Djava.awt.headless=true
-Dfelix.fileinstall.log.level=2
-Dfelix.fileinstall.poll=5000
-Dcom.sun.aas.instanceRoot=/misc/data/glassfish3/glassfish/domains/domain1
-Dosgi.shell.telnet.ip=127.0.0.1
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Djava.endorsed.dirs=/misc/data/glassfish3/glassfish/modules/endorsed:/misc/data/glassfish3/glassfish/lib/endorsed
-Dcom.sun.aas.installRoot=/misc/data/glassfish3/glassfish
-Dfelix.fileinstall.bundles.startTransient=true
-Djava.ext.dirs=/usr/lib64/java/lib/ext:/usr/lib64/java/jre/lib/ext:/misc/data/glassfish3/glassfish/domains/domain1/lib/ext
-Dfelix.fileinstall.bundles.new.start=true
-Djavax.net.ssl.trustStore=/misc/data/glassfish3/glassfish/domains/domain1/config/cacerts.jks
-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
-Djava.security.auth.login.config=/misc/data/glassfish3/glassfish/domains/domain1/config/login.conf
-DANTLR_USE_DIRECT_CLASS_LOADING=true
Dgosh.args=-nointeractive
Mar 18, 2012 8:49:54 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 11 msec.
Launching GlassFish on Felix platform
[#|2012-03-18T20:49:58.215+0900|INFO|glassfish3.1.2|com.sun.enterprise.server.logging.GFFileHandler|_ThreadID=1;_ThreadName=main;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2 (build 23)|#]

[#|2012-03-18T20:49:59.178+0900|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName=Grizzly-kernel-thread(1);|Grizzly Framework 1.9.46 started in: 107ms - bound to [0.0.0.0:8181]|#]

[#|2012-03-18T20:49:59.184+0900|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Grizzly-kernel-thread(1);|Grizzly Framework 1.9.46 started in: 34ms - bound to [0.0.0.0:4848]|#]

[#|2012-03-18T20:49:59.186+0900|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=22;_ThreadName=Grizzly-kernel-thread(1);|Grizzly Framework 1.9.46 started in: 215ms - bound to [0.0.0.0:8080]|#]

[#|2012-03-18T20:49:59.211+0900|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=29;_ThreadName=Grizzly-kernel-thread(1);|Grizzly Framework 1.9.46 started in: 39ms - bound to [0.0.0.0:3700]|#]

[#|2012-03-18T20:49:59.233+0900|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=32;_ThreadName=Grizzly-kernel-thread(1);|Grizzly Framework 1.9.46 started in: 22ms - bound to [0.0.0.0:7676]|#]

[#|2012-03-18T20:49:59.911+0900|INFO|glassfish3.1.2|org.glassfish.ha.store.spi.BackingStoreFactoryRegistry|_ThreadID=1;_ThreadName=main;|Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry|#]

[#|2012-03-18T20:50:00.104+0900|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=main;|GlassFish Server Open Source Edition 3.1.2 (23) startup time : Felix (3,227ms), startup services(2,352ms), total(5,579ms)|#]

GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy' is not installed

aborting...

A bit of googling indicates that org.gnome.system.proxy is installed by gsettings-desktop-schemas.

Because it is a bad design decision for glassfish to depend on a gnome lib, I want this dependency removed.



 Comments   
Comment by Tom Mueller [ 19/Mar/12 ]

GlassFish does not contain any direct references to any gnome library. However, depending on the update tool client configuration settings, it will set the java.net.useSystemProxies environment variable to true, which may cause Java SE to use a gnome library to read the system proxies. You can avoid this in any of the following ways:

  • set http_proxy or https_proxy environment variable
  • set the proxy values in the $HOME/.updatetool/init.cfg (or defaults.cfg) to something other than use system proxy.
Comment by crochery [ 20/Mar/12 ]

I disabled system proxy in $HOME/.updatetool/init.cfg, and glassfish started working.

Can you disable system proxy by default?

Or I think the fact that system proxy settings should be disabled on some environments by some means should be explained in glassfish doc.

Comment by Tom Mueller [ 21/Mar/12 ]

Changing this to be a docs bug so that the need to disable the use of the system properties for some systems can be explained.

I'm not sure what is meant by "by default" in the previous comment.

Changing the value in init.cfg (as you have done) will change the default behavior of GlassFish for all domains that are created by the user who owns the init.cfg.

If the .zip distribution of GlassFish is used, no init.cfg file is created by default, and the default behavior will be to use no proxy, not the system proxy. So for the zip distribution, not using the system proxy is already the default.

When installed using the installer, the installer prompts for the proxy to use with the update tool. It does not offer a "use system proxy" option at that point. So again, the default behavior is to not use the system proxy.

So I'm not sure how the use of system proxies was enabled on your system without actually selecting it via updatetool.

Comment by crochery [ 22/Mar/12 ]

Initially, I tried to install glassfish with an installer, but it only installed a small fraction of glassfish on slackware.
I think init.cfg was implanted when installing or executing the updatetool.

After removing init.cfg and extracting the zip distribution again, I found out that system proxy was off by default.

bin/updatetool sets [network] proxy.user.system to true in ~/.updatetool/init.cfg
What's your idea on this?





[GLASSFISH-18491] javadoc.glassfish.org not available Created: 09/Mar/12  Updated: 26/Jul/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: kovica Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I'm in a need to look at the Glassfish Javadocs. That is javadocs for the server, not javadocs for the JEE APIs.
When you click on the Javadoc link under "Using glassfish", the link points to http://javadoc.glassfish.org/v3/apidoc/index.html, but
everytime I click it, I get a timeout response.
Ist the link broken? Is the javadoc.glassfish.org server down?

PLEASE help.



 Comments   
Comment by Paul Davies [ 09/Mar/12 ]

As a workaround, use the API specification for GlassFish Server, including Java EE 6 platform packages and nonplatform packages that are specific to the GlassFish Server product at http://glassfish.java.net/nonav/docs/v3/api/. To see the GlassFish-specific, non-platform packages, scroll down the page.

Comment by kovica [ 10/Mar/12 ]

Thanks for the help.

This one works.

Comment by kovica [ 26/Jul/12 ]

This is still not fixed.
The javadocs at http://glassfish.java.net/nonav/docs/v3/api/ awere generated in 2009.
Are there any newer javadocs for Glassfish available?





[GLASSFISH-18750] [UB] enable-secure-admin doc incorrect regarding password requirement Created: 22/May/12  Updated: 14/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Chris Kasso Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The 3.1.2 docs says:

http://docs.oracle.com/cd/E26576_01/doc.312/e24940/administrative-security.htm#gkocv

By default, GlassFish Server includes a single account for user "admin" and an empty password. Therefore, if you make no other changes before you enable secure admin, "admin" is the initial default username and no password is required. You need to decide whether enabling secure admin without also requiring a password makes sense in your environment.

But I thought 3.1.2 does not allow secure admin to be enabled without an admin password.



 Comments   
Comment by Tim Quinn [ 22/May/12 ]

Hi, Mike.

Just to be clear...

The current (3.1.2) behavior is that the enable-secure-admin command checks to make sure that there is no administrator user with an empty password. The enable-secure-admin command fails if there is at least one such administrator user.

There is a brief note to this effect in this doc:

http://docs.oracle.com/cd/E26576_01/doc.312/e24940/administrative-security.htm#gknqh

just a few paragraphs above the passage Chris pointed to with the link in the initial problem description.

Comment by Mike Fitch [ 22/May/12 ]

Hi Tim,

I added the note you cite in 3.1.2 (as well as similar notes and statements elsewhere where enabling secure admin and admin passwords are mentioned).

The location Chris cites is an instance I missed, and is certainly incorrect.

Comment by Tim Quinn [ 23/May/12 ]

Hi, Mike.

Yeah, I should probably have caught that spot in my review of the changes.

Comment by Mike Fitch [ 14/Mar/13 ]

Added [UB] to summary as this issue applies to a book, "unbundled" documentation. Also, changed Fix Version to 4.0 so issue will show up on 4.0* queries. Actual commitment and build # TBD.





[GLASSFISH-18732] [UB]Incorrect jndi name of EJB for standalone java client Created: 16/May/12  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: v2.1, 3.1, 3.1.2, 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Cheng Fang Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Juan reported this in glassfish interest alias:

According to the documentation http://docs.oracle.com/cd/E26576_01/doc.312/e24930/jndi.htm#beany
The lookup for a standalone client should be done using the interoperable global name
"For a client that doesn't run within a Java EE container, the code just uses the interoperable global name instead of the simple global JNDI name. For example:
Context ic = new InitialContext(); Object o = ic.lookup("corbaname:iiop:host:port#a/b/Foo");
"

But I am trying with the corbaname and I unable to do it work...

If instead of the corbaname I use the portable global name java:global/HelloWorldEE-ejb/NewSessionBean then it works.
-----------

I checked GlassFish 2.1 doc, and it also contains the same instruction as 3.1.2
http://docs.oracle.com/cd/E19879-01/820-4336/beanv/index.html

I tend to think this is a oversight in docs and we should correct:

for 2.x and 3.0, use GlassFish-specific global jndi name for the remote ejb;

for 3.1 or later, one can use either the portable global jndi name (preferred), or GlassFish-specific global jndi name, for the remote ejb.



 Comments   
Comment by Mike Fitch [ 16/Feb/13 ]

Added [UB] to summary and set fix version to 4.0.1 because this fix would be to unbundled documentation.

Comment by Mike Fitch [ 15/Mar/13 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.





missing max save post size bytes under network-confg/protocols/http-listener-1/http. (GLASSFISH-20164)

[GLASSFISH-20166] OLH: need to add this attribute to the help page Created: 04/Apr/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: future release

Type: Sub-task Priority: Major
Reporter: Anissa Lam Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Refer to main task.



 Comments   
Comment by Mike Fitch [ 04/Apr/13 ]

Moving this to "Future Release". The final online help has already been committed and is in translation. If this issue is deemed a release blocker, please update its priority.





[GLASSFISH-19601] [UB] describe how MQ cluster name is generated for a given GlassFish cluster Created: 29/Jan/13  Updated: 14/Mar/13

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 9.1.1, v2.1, v2.1.1, V3, v3.0.1, 3.1, 3.1.1, 3.1.2, 3.1.2.2
Fix Version/s: 4.0

Type: Improvement Priority: Major
Reporter: amyk Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

see Summary. This issue is first filed to 'jms' to provide text for doc, then please transfer to 'docs'



 Comments   
Comment by David Zhao [ 30/Jan/13 ]

glassfish will pass <gfClusterName>_MQ to MQ for the property of "imq.cluster.clusterid". Please see MQ-275 for details of the doc issue.

Comment by amyk [ 30/Jan/13 ]

David,

According to the following GlassFish forum post, MQ broker sees MYCLSTRDEV_MQ for imq.cluster.clusterid without the '_'s in MY_CLSTR_DEV

http://www.java.net/forum/topic/glassfish/glassfish/glassfish-enhanced-jms-cluster-configuration

Re: Glassfish Enhanced JMS Cluster Configuration
January 29, 2013 - 04:54
#6
hopipouet
.....
To be perfect you can add that "_" are not used in the clusterId generated by glassfish, so you can add how many "_" you want in cluster name, it doesn't count in the length.

for example : MY_CLSTR_DEV
generate following index :
MQCONSTATE41CMYCLSTRDEV_MQIDX1
Comment by Mike Fitch [ 30/Jan/13 ]

Changed component to docs. Changed fix version to 4.0_b76_EE7MS5 for any changes that would go into the configure-jms-cluster man page or the JMS Availability or New Cluster console help pages.

Comment by Mike Fitch [ 14/Mar/13 ]

Added information about name length restrictions to the cluster-name operand in the create-cluster and configure-jms-cluster subcommand man pages. Fix available in main-docs build 4.0-b15, which was picked up by GlassFish as of revision 59613, 18-FEB-2013.

Added [UB] to the summary so remaining book-related changes will get tracked.

Changed Fix Version to 4.0 for remaining book-related changes.





[GLASSFISH-19762] [UB] Add release notes documentation concerning the state of the upgrade capability for 4.0 OSE Created: 01/Mar/13  Updated: 20/Dec/16

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Tom Mueller Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-release-notes, 4_0-release-notes-completed, 4_0-release-notes-drafted

 Description   

This issue is for making sure the release notes for the 4.0 OSE release describe the anticipated level of testing and quality for the upgrade feature, i.e., the --upgrade option of the start-domain command.



 Comments   
Comment by Mike Fitch [ 14/Mar/13 ]

Added [UB] to summary so unbundled doc queries will pick up this issue.

Comment by Mike Fitch [ 17/May/13 ]

Added the following to the release notes:

Note:
The main thrust of the GlassFish Server Open Source Edition 4.0 release is to provide an application server for developers to explore and begin exploiting the new and updated technologies in the Java EE 7 platform. Thus, the following features of GlassFish Server were not a focus of this release:

  • Clusters and standalone instances
  • High availability features
  • Upgrade
  • Embedded Server

These features are included in the release, but they may not function properly with some of the new features added in support of the Java EE 7 platform.





[GLASSFISH-17252] [UB]Improve GlassFish Administration Guide with mod_proxy_ajp info Created: 29/Aug/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Amy Roh Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

From user post http://forums.java.net/node/838467

"The GlassFish 3.1 Administration Guide provides information on fronting
GlassFish with Apache via mod_jk, but does not provide any information about
mod_proxy_ajp.

It appears that you can get Apache connected to GlassFish via mod_proxy_ajp
so it would be nice if the documentation at leasts mentions it (and discusses
any gotchas which I might be overlooking)."

We should improve GlassFish Administration Guide with mod_proxy_ajp info.



 Comments   
Comment by Mike Fitch [ 08/Nov/11 ]

Changing component to docs and assignee to myself.

Comment by Paul Davies [ 21/Jan/12 ]

[UB]: Affects unbundled documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16978] [UB]Change error message OR Improve documentation Created: 07/Jul/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: alessalessio Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day
Environment:

Windows 7, Eclipse Helios


Tags: documentation, error_handling, masterpassword

 Description   

Documentation about securing domain passwords in Glassfish should be improved, or error log changed.

Suppose to have a Connection Pool and a related resource. This connection pool contains:
<property name="password" value="$

{ALIAS=dbpass}

"/>.

As stated in Glassfish documentation, the encrypted value of the password linked by the alias is contained into a domain-passwords file. The key which encrypts and decrypts this password is contained into a masterpassword file (supposing that the domain is created with --savemasterpassword=true option).

Now, if i develop a we application running on a Glassfish server, and i want to protect it, leaving the DB access only to people that I want to. If i give a copy of those files (masterpassword and domain-passwords) to those people, they should be able to connect to the DB (since they have my masterpassword, and domain-passwords).

This actually does not happen, and Glassfish console states:
"The Master Password is required to start the domain. No console, no prompting possible. You should either create the domain with --savemasterpassword=true or provide a password file with the --passwordfile option."

Which is actually NOT true. The masterpassword is present and it was created with --savemasterpassword=true.

The problem seems to be that actually, i would need to send both masterpassword, domain-passwords, AND keystore.jks and cacerts.jks.

So please provide a better explanation how these two files are related to the masterpassword AND/OR change that error log.



 Comments   
Comment by Tom Mueller [ 22/Dec/11 ]

This is actually a documentation improvement suggestion.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17106] [UB]Add userdefined library information to load-balancer documentation Created: 26/Jul/11  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: kshitiz_saxena Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PDF File user-defined-load-balancing.pdf    
Issue Links:
Dependency
blocks GLASSFISH-16616 ReadMe.UserDefinedLB needs an update ... Reopened

 Description   

There is Readme for userdefined library bundled with load-balancer plugin. This information can be captured in load-balancer documentation itself.



 Comments   
Comment by kshitiz_saxena [ 26/Jul/11 ]

Content of user defined README
---------------------------------

With User Defined Loadbalancer the user can have a custom logic for loadbalancing. Examples would be user identity based redirect, mime based load balancing etc. The user of this feature has to develop a shared library which would be loaded by load balancer. The user has to implement the interface as defined in loadbalancer.h which be placed in <glassfish plugin install dir>/lib/install/templates. An example module which implements the basic roundrobin algorithm(roundrobin.c) is included. The following are the steps needed to compile and configure the User Defined module.
1. Copy the roundrobin.c to a work directory (for example: /home/user/workspacelb).
2. Compile roundrobin.c with either the ANSI C/C++ compiler(for eg. sunstudio compiler or gcc). Take care to build a dynamic shared library and not a static executable.

  • Using sun studio cc compiler:
    % cc -m64 -G -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
    Note: In case of relocations error, use option "-xcode=pic32" with cc. cc -m64 -G -xcode=pic32 -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
  • Using gcc
    % gcc -m64 -shared -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
    Note: In case of relocations error, use option "-fPIC" with gcc. The command will look like: gcc -m64 -shared -fPIC -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
  • On windows download MSVC++ 2008 Express Edition from http://www.microsoft.com/express/download/ . Ensure that system environment variables related to MSVC are set. These include INCLUDE=<msvc-install-dir/VC/include>, LIB=<msvc-install-dir>/VC/lib;<microsoft-sdk-lib-dir>. Also note to update the PATH to include <msvc-install-dir>/VC/bin;<msvc-install-dir>/Common7/IDE. The command to build the dll would be:
    % cl /D_WINDOWS /I<glassfish plugin install dir>/lib/install/templates /LD roundrobin.c

3. Change the loadbalancer.xml to point to the newly built module.
<cluster name="cluster1" policy="user-defined" policy-module="home/user/workspacelb/roundrobin.so">

4. Start the webserver if its not running or wait till LB re-configure.

Comment by Mike Fitch [ 01/Feb/12 ]

The attachment user-defined-load-balancing.pdf shows the content added to the HA Admin Guide to resolve this issue. Please review this content and update this issue with comments.

Comment by kshitiz_saxena [ 02/Feb/12 ]

Change
< To Build the Sample User-Defined Load Balancing Algorithm on Solaris
to
>To Build the Sample User-Defined Load Balancing Algorithm on Unix platform

Change
< The cc compiler, version 4.0.4 or later
to
> The sun studio cc compiler, version 4.0.4 or later

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-2431] [UB]Errors on generating identity primary key with Sybase data direct driver Created: 15/Feb/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: mzh777 Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive pkGenIdentity.zip    
Issuezilla Id: 2,431
Status Whiteboard:

as91ur1-na


 Description   

Build AS9.1 beta 33c.

The data direct driver packaged in the AS9.1 beta is version 3.60.7. When this
driver is used in generating identity primary key, exceptions were thrown:
[java] Exception Description: Cannot persist detached object
[ejb30.persistence.datatypes.ejb.DataTypes@738d08].
[java] Class> ejb30.persistence.datatypes.ejb.DataTypes Primary Key> [0]
[java] at
oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerImpl.persist
(EntityManagerImpl.java:193)
[java] at
ejb30.persistence.datatypes.client.TestOutsideContainer.createDataTypes(Unknown
Source)
...

When switched to use sybase j-connect driver (jconn2.jar), the same test passed.



 Comments   
Comment by mzh777 [ 15/Feb/07 ]

Created an attachment (id=740)
PK Identity generation test

Comment by mzh777 [ 15/Feb/07 ]

Added Mitesh and Marina to the cc list.

Comment by Mitesh Meswani [ 15/Feb/07 ]

The test uses following table
CREATE TABLE DATATYPES (ID INTEGER IDENTITY NOT NULL,......)

After inserting data into the table, Toplink is using SELECT @@IDENTITY to
retrieve the value of inserted ID column. I think datadirect is misbehaving here

Comment by lancea [ 21/Mar/07 ]

This issue is a bit ugly but turns out to be the result of the default behavior for
DataDirect drivers on Sybase where it creates a stored procedure for every
parameterized PreparedStatement.

To change the default driver behavior, set the following property:

PrepareMethod=direct

This disables the creation of the stored procedures.

Comment by sherryshen [ 24/Jul/07 ]

The problem still exists in 9.1pe_b55 promoted.
Can this solution or workaround be documented?
e.g.
With Sybase DD driver, set "PrepareMethod=direct" property in
domain.xml when ... ??? (generating identity primary key).
Thanks!

Comment by sherryshen [ 26/Jul/07 ]

Re-open it for docs after Ming and I discussed it with Lance.

Comment by basler [ 12/Nov/07 ]

Not a as91ur1 show stopper.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by Paul Davies [ 26/May/11 ]

Mike, please determine if this issue should be fixed in 3.1.1, resolved, or closed.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13200] [UB]certain number of join notifications are not seen after cluster startup. Created: 30/Aug/10  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: zorro Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Linux


Issuezilla Id: 13,200

 Description   

build: ogs-3.1-web-b18-08_30_2010

  • start DAS
  • wait for DAS to start
  • start cluster (9 CORE instances on 9 machines)
  • wait for all cluster instances to start
  • stop cluster
  • wait all cluster CORE nodes to stop
  • stop DAS
  • wait to DAS to stop
  • collect logs

bug:
nodes 5 and 10 do not have 9 join notification.

Expected:
Like other nodes at some point we should see 9 join notifications of the 9-node
clusters startup.

Results and logs:
http://aras2



 Comments   
Comment by Joe Fialli [ 31/Aug/10 ]

I am unable to resolve the link that is attached to this report to investigate
this issue. The link is a relative link to target machine(assumes auto
completion to a domain that I may not have configured to auto complete to.)

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

Additonal information required to evaluate this issue.
How is the cluster being started? With the "asadmin start-cluster" command or
are the instances being started up independently via "asadmin start-instance"
for each clustered instance (due to outstanding issue with "asadmin
start-cluster").

******

Note that only the DAS is required to see all JOIN notifications from all
instances during start-cluster sequence.

All GMS notifications are broadcasted to all active members of the cluster.
Since not all instances start in lock step at same moment of time, it is quite
possible that not every instance sees every other instance's JOIN notification.

When an instance registers for an JOIN notification, there are methods on the
notification that allow the instance to learn of all the other ALIVE and READY
members that are currently running.

After "start-cluster" completes and all instances are running, all future
individual GMS notifcations for clustered instances stopping, starting or
failing should be received by all active clustered members. Additionally, there
is a race condition at "asadmin stop-cluster" that not all instances will see
the PLANNED_SHUTDOWN of all other instances. This is basic attribute of GMS
notifications being a broadcast to all registered members. One can not guarantee
the reception of a broadcast during startup or shutdown of entire cluster.

Comment by zorro [ 31/Aug/10 ]
  • The reason this could be a bug is that in nodes 5, and 10 we see 10 join
    notification but no 9 join notification prior to that.
  • Instances were started using start-local-instance
Comment by Joe Fialli [ 15/Sep/10 ]

After applying the system configuration recommendations below,
this problem is no longer occurring on Oracle Enterprise Linux 5.

This system configuration issue must be documented for glassfish v3.1.
While we do not have final tuning values, I will keep this issue open as a
documentation issue for glassfish v3.1 so we remember to document this
important issue that requires OS level configuration.

The default Linux UDP buffer size is too small for a 10 instance cluster.

These values can be configured via sysctl -w (to configure in OS immediately)
and to fix across reboot of the OS, the values should be placed in /etc/sysctl.conf.

We are still working on final recommended UDP buffer size. But for now,
these values have test passsing.

net.core.rmem_max=524288
net.core.wmem_max=524288
net.core.rmem_default=524288
net.core.wmem_default=524288

We have determined that the default values are too small, but we have not come
up with a formula to compute what the values need to be based on the number of
instances in the cluster AND the number of instances per machine.

Comment by Joe Fialli [ 15/Sep/10 ]
      • Issue 13209 has been marked as a duplicate of this issue. ***
Comment by Joe Fialli [ 15/Sep/10 ]
      • Issue 13209 has been marked as a duplicate of this issue. ***
Comment by Paul Davies [ 04/Oct/10 ]

Added [UB] to Summary to denote unbundled documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





list-nodes: add target operand? (GLASSFISH-13967)

[GLASSFISH-14654] document list-nodes target operand Created: 12/Nov/10  Updated: 28/Nov/11

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: future release
Fix Version/s: future release

Type: Sub-task Priority: Minor
Reporter: Joe Di Pol Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-13967 list-nodes: add target operand? Open
Issuezilla Id: 14,654

 Description   

GLASSFISH-13967 adds a "target" operand to list-nodes. This may or may not make 3.1.
Need to make sure documentation accurately reflects what is implemented for the
release.






[GLASSFISH-15470] every subcommand manual page include "asadmin-options" in the synopsis Created: 06/Jan/11  Updated: 19/Dec/16

Status: Reopened
Project: glassfish
Component/s: docs
Affects Version/s: 3.1_dev
Fix Version/s: future release

Type: Improvement Priority: Minor
Reporter: jbenoit Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-exclude

 Description   

request that every subcommand manual page include "asadmin-options" in the synopsis with a note that information about the asadmin-options is on the asadmin manual page.

Here is the motivation/use case email thread from users@glassfish.java.net as to why this is requested:

http://java.net/projects/glassfish/lists/users/archive/2011-01/message/56



 Comments   
Comment by Paul Davies [ 24/Jan/11 ]

Defer to 3.2 for consideration. However, if the proposed fix is adopted, the synopsis would have to include asadmin <asadmin-options>, which reduces the prominence in the synopsis of the subcommand that is described in the man page.

Comment by Paul Davies [ 27/May/11 ]

After consideration, this RFE is declined. Adding this information would clutter the Synopsis and Options sections.

Comment by Paul Davies [ 05/Aug/11 ]

After further consideration and discussion, it seems that including all the related information is more important than not reducing the prominence in the synopsis of the subcommand that is described in the
man page.

The fix for this issue requires the following changes to the man page for each asadmin subcommand:

  • In Synopsis, prefix the subcommand with asadmin [asadmin-options] just like the usage statement.
  • In Options, add an explain for asadmin-options that cross-refers to asadmin(1M) and suggests running asadmin help as an alternative.
  • In See Also, move the cross-reference to asadmin(1M) to above the references to section 1 man pages.
Comment by Paul Davies [ 06/Mar/12 ]

Too ambitious for a minor release such as 3.1.2. Aim to fix in 4.0





[GLASSFISH-18139] [UB]Repository docs issue with upgrading from GlassFish Open Source Edition to Oracle GlassFish Server Created: 06/Jan/12  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_dev
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: jclingan Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Irrelevant.



 Description   

The default repositories are:
PUBLISHER TYPE STATUS URI
stable.glassfish.org (preferred) origin online http://pkg.glassfish.org/v3/stable/
contrib.glassfish.oracle.com origin online http://pkg.oracle.com/glassfish/v3/contrib/
contrib.glassfish.org origin online http://pkg.glassfish.org/v3/contrib/

Problem 1:
The documentation states to remove the following repositories:
dev.glassfish.org
stable.glassfish.org
release.javaeesdk.oracle.com

The only repository in common beteen the OSS and commercial versions is stable.glassfish.org. I think we want to state in the docs to remove stable.glassfish.org, and if the others exist [ the contrib and sdk repositories ], delete them as well.

Problem 2, the order of the documented steps is incorrect. You can't delete the preferred repository. First you must added the new repositories (including setting the new default repository as release.glassfish.oracle.com). After that is done, then you can remove the glassfish.org repositories.



 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





add support for commands related to Transaction service (GLASSFISH-17710)

[GLASSFISH-17818] OLH: commands related to transaction services Created: 23/Nov/11  Updated: 26/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: future release
Fix Version/s: future release

Type: Sub-task Priority: Minor
Reporter: Anissa Lam Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

refer to main task for UI changes. more info will be added when work started on it.






support list-containers (GLASSFISH-17631)

[GLASSFISH-17816] list-containers Created: 23/Nov/11  Updated: 26/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: future release
Fix Version/s: future release

Type: Sub-task Priority: Minor
Reporter: Anissa Lam Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Refer to main task for UI changes. Info will be added as work begins.






[GLASSFISH-16687] [UB]GFv3: add DB2 Type4 Driver to supported driver list Created: 19/May/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Task Priority: Minor
Reporter: Andreas Rieck Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux SLES 10 and SLES 11, GFv3.01 and GFv3.1, IBM DB2 JDBC Type-4 driver


Tags: DB2, JDBC, Type-4

 Description   

Seen within Oracle GlassFish Server 3.1 Administration Guide, Section Configuration Specifics for JDBC Drivers,
it is described that GlassFish Server is designed to support connectivity to any database management system
by using a corresponding JDBC driver.
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/beamw.html

However on the list for configuration information the "IBM DB2 Database Type 4 Driver" is not included.
The documentation looks like that DB2 type-4 driver is not supported, but we do provide
already within GFv2 and GFv3 installations coresponding configuration template as well.

see:

GFv2_INSTALL_DIR/lib/install/templates/resources/jdbc/db2_jcc_datasource.xml
GFv3_INSTALL_DIR/glassfish/lib/install/templates/resources/jdbc/db2_jcc_datasource.xml

Content of db2_jcc_datasource.xml, special the entry "driverType".

...
IBM DB2 JDBC type-4 driver for DB2 Databases
The JAR file for the DB2 driver db2jcc.jar
...
<jdbc-connection-pool
name="db2_jcc_pool"
datasource-classname="com.ibm.db2.jcc.DB2SimpleDataSource"
res-type="javax.sql.DataSource">
<property name="user" value="DB_USER"/>
<property name="password" value="DB_PASSWORD"/>
<property name="serverName" value="DB_HOSTNAME"/>
<property name="portNumber" value="50000"/>
<property name="databaseName" value="DATABASE_NAME"/>
<property name="driverType" value="4"/>
</jdbc-connection-pool>
...

Same IBM DB2 type 4 JDBC driver usage is described vor GFv1/v2 at Jagadish's Blog
http://blogs.oracle.com/JagadishPrasath/entry/jdbc_connection_pool_templates_glassfish

This is a Documentation RFE request, to please add "IBM DB2 Database Type 4 Driver" to this list as well.
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/beamw.html

IBM's article about DB2 JDBC can be found here:
http://www.ibm.com/developerworks/data/library/techarticle/0203zikopoulos/0203zikopoulos.html#type2
http://www.ibm.com/developerworks/data/library/techarticle/0203zikopoulos/0203zikopoulos.html#type4



 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-21304] Reference Correct Javadoc for Glassfish 4 Created: 12/Feb/15  Updated: 12/Feb/15

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: jskillin.idt Assignee: sbcaruso
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

(The docs@glassfish mailing list asked me to post my issue here instead.)

The Javadoc for Glassfish 4 is not linked in the main documentation page.

Also, the installation guide PDF, under "Related Documentation", claims the Javadoc is at http://glassfish.java.net/nonav/docs/v3/api/. When I opened that URL, I found it was the Javadoc for Glassfish 3. That document, and possibly others, will need to get updated to reference the 4 API.






[GLASSFISH-20765] asupgrade script included in documentation but missing in GF 4.0 distribution Created: 16/Aug/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: novaks Assignee: Mike Fitch
Resolution: Unresolved Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: asupgrade, upgrade_tool

 Description   

The asupgrade and asupgrade.bat scripts are missing in GlassFish 4.0 ZIP distribution (downloaded from http://download.java.net/glassfish/4.0/release/glassfish-4.0.zip, build 89). These scripts should be located under glassfish4/glassfish/bin and also the GF 4 Upgrade Guide PDF refers to them but they are missing in the downloaded ZIP archive.



 Comments   
Comment by juliohm [ 28/Aug/13 ]

This can be easily confirmed by looking at the contents of the official download package.

http://download.java.net/glassfish/4.0/release/glassfish-4.0.zip

Scritps asupgrade and asupgrade.bat are simply not there. Does any one know of a workaround? We need to start tesing upgrades from 3.1.2.2 to 4.0.

Comment by karinchen [ 25/Sep/13 ]

Upgrade tool also missing in self-extracting archive http://download.java.net/glassfish/4.0/release/glassfish-4.0-windows.exe

Please, can anyone provide a location from where we can download it?
We need to migrate a GF 2.1.1 server, so upgrade tool seems the only available option...

Comment by Joe Di Pol [ 17/Oct/13 ]

It looks like asupgrade was intentionally removed in GlassFish 4.0:

https://blogs.oracle.com/bobby/entry/the_glassfish_upgrade_tool

Based on this I'm lowering the priority and warning that this may be closed as not-a-bug.

The work around is to copy the source domain to the target and run "asadmin start-domain --upgrade"

It is my understanding that upgrade to 4.0 was not well (if at all) tested, so no promises as to how well this will work.

Comment by Joe Di Pol [ 18/Oct/13 ]

Assigning to documentation since the 4.0 upgrade guide (https://glassfish.java.net/docs/4.0/upgrade-guide.pdf) mentions using asupgrade.





[GLASSFISH-20877] admin-gui help has a mistake Created: 26/Oct/13  Updated: 28/Oct/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: HASUNUMA Kenji Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

N/A


Tags: admin-gui, docs, l10n

 Description   

ref-ldaprealmprop.html, one of help file in admin-gui, has an mistake.

The value of JAAS context is not "solarisRealm" but "ldapRealm".

First, I found this issue in the Japanese translation. But it is common issue other L10N or original (English) help.

For information, I show paches for it (English and Japanese) in follows:

Index: ref-ldaprealmprop.html
===================================================================
— ref-ldaprealmprop.html (revision 62871)
+++ ref-ldaprealmprop.html (working copy)
@@ -11,7 +11,7 @@
<dl>
<dt>JAAS Context</dt>
<dd>
-<p>The JAAS (Java Authentication and Authorization Service) context (the identifier for the login module to use for this realm). The only valid value is <code>solarisRealm</code>.</p>
+<p>The JAAS (Java Authentication and Authorization Service) context (the identifier for the login module to use for this realm). The only valid value is <code>ldapRealm</code>.</p>
</dd>
<dt>Directory</dt>
<dd>

Index: ref-ldaprealmprop.html
===================================================================
— ref-ldaprealmprop.html (revision 62871)
+++ ref-ldaprealmprop.html (working copy)
@@ -11,7 +11,7 @@
<dl>
<dt>JAASコンテキスト</dt>
<dd>
-<p>JAAS (Java Authentication and Authorization Service)コンテキスト(このレルムに使用するログイン・モジュールの識別子)。有効な値は<code>solarisRealm</code>のみです。</p>
+<p>JAAS (Java Authentication and Authorization Service)コンテキスト(このレルムに使用するログイン・モジュールの識別子)。有効な値は<code>ldapRealm</code>のみです。</p>
</dd>
<dt>ディレクトリ</dt>
<dd>



 Comments   
Comment by HASUNUMA Kenji [ 28/Oct/13 ]

I'm ready to provide the patch for the all languages as attachment file(s) if I permit it, because now I don't have the permission to attach file(s) on JIRA.
Or I'm also ready to commit the modified files to the repository if you could give me the Developer role.





[GLASSFISH-20644] clarify help for set-web-env-entry and set-web-context-param Created: 18/Jun/13  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0_dev
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: vince kraemer Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

glassfish 4, java 7 u21, mac os x 10.7.5



 Description   

The doc for these two asadmin subcommands could be improved in a couple different ways:

1. mention that a user needs to disable/enable an App to get the change to "take" in the app.

2. put the discussion of the effect of the commands in terms of the effect on an 'effective' deployment descriptor.
this is especially true around the description of --ignoredescriptoritem... It is pretty confusing on the first read.






[GLASSFISH-19278] [UB] GlassFish documentation about -Xrs JVM option is unclear Created: 02/Nov/12  Updated: 14/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2.2
Fix Version/s: 4.0

Type: Bug Priority: Minor
Reporter: ljnelson Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The GlassFish documentation set concerning the -Xrs JVM option does not really indicate if this is a requirement for setting up a service on Windows.

If it is a requirement, then shouldn't it be part of the configuration information produced by asadmin create-service?

Given that most of the time a Windows service runs as a different user from the one who is logging out, is this documentation intended to point out that any user's logout will cause the service to terminate?



 Comments   
Comment by ljnelson [ 03/Nov/12 ]

Looks like there's one related issue that claims to be a duplicate of another.

My intent is only to make sure that the documentation reflects whatever the consensus is, not to duplicate either bug.

Comment by Mike Fitch [ 14/Mar/13 ]

Added [UB] to summary as this issue relates to unbundled documentation (as opposed to online help). Also, changed Fix Version to 4.0 so issue will show up on 4.0* queries. Actual commitment and build # TBD.

Comment by Mike Fitch [ 14/Mar/13 ]

Whoops. Really changed fix version this time.





[GLASSFISH-18662] [UB] default index.html in upgraded domain shows wrong version number Created: 26/Apr/12  Updated: 20/Dec/16

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_dev, 3.1.2
Fix Version/s: 4.1.1

Type: Bug Priority: Minor
Reporter: lb54 Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Win 2008, Update from GF 3.1.1 to 3.1.2


Tags: index, update, updatecenter, upgrade

 Description   

It would be very nice, if the Update to a next Glassfish-Version overwrites the Version in the index.html of the DAS and instances.
Situation today: Updating a GF Server does not write the new Version of the Glassfish in the index.html which is shown on HTTP Port. It is very irritating, if you actually updated the GF and the http://localhost:38080/ Site says it is still the old version.

Thanks.



 Comments   
Comment by Bobby Bissett [ 26/Apr/12 ]

I know that this is surprising to the user (and, thus annoying), but there really isn't a workable fix from discussions we've had about this previously. I thought there was already a closed issue on this in Jira, but I can't find it now.

Everything under domainX/docroot belongs to the user, and in any production system where static content would end up being displayed, the index.html page should be replaced by a site's home page. If there's an app deployed to /, some "Application will be available shortly" kind of message should be there instead. So the contents of that index.html file could be anything. Replacing it would be trivial since the server could just copy the one from gf/lib/templates/docroot, but knowing when to copy it is impossible. The server would have to keep a copy of every version of index.html that had been the default in previous ones, and check them all against the current one. And if the user changed it in any way, there could still be old references to the version in there since it wouldn't be replaced. There's always the chance that the user didn't want it replaced anyway since this is static content.

Making this worse, it's a valid upgrade path to start a 3.X domain in a 3.X+1 server without ever running asupgrade or "asadmin start-domain --debug" – a 3.1 domain should not need to be upgraded to run with a 3.1.1 server. So the code that parses the index.html file would need to run on every startup, thus affecting startup time for something that may never need to actually happen.

So I hope you can see that it's not really a simple matter. Conceivably there could be some other startup option like --upgrade-docroot that overwrites the file, but if a user actually remembered such a detail then s/he could just do a 'cp' instead.

I'm not a member of the GF team anymore, so I can't change the resolution of this issue, but wanted to share my comments about it. Maybe you can think of a solution that's eluded me! Will be transferring to someone else to see how this issue should be handled.

Cheers,
Bobby

Comment by Bobby Bissett [ 26/Apr/12 ]

Hi Tom,

Sorry to bother you, but can you take a look at this and see if a decision needs to be made about closing it or trying some fix? I don't want to assign it to another category (eg admin) to change owners, because other people have thought of this and it'd be good to have the issue stay in the 'upgrade' category for future reference.

Thanks,
Bobby

Comment by Tom Mueller [ 26/Apr/12 ]

The default index.html is delivered as part of the documentation via the basedocs package. So I'm assigning this to Paul for further consideration.

Due to the problems that Bobby described with being able to actually update the file once it is in a domain, I would recommend that the fix for this should be to change the wording in the default index.html file so that:

  • the version is not in the file, or
  • the wording makes it clear that the version number that is there is the version of the software that was used to create the domain, thus not giving the impression that the version number would be updated when the software is updated.
Comment by Mike Fitch [ 24/Mar/13 ]

Removed version information from the default index.html page.

This change will become accessible in GlassFish when the next main-docs build is promoted and picked up by GlassFish builds.

Comment by Bobby Bissett [ 25/Mar/13 ]

Can we also have text in the upgrade documentation (if there still is such a doc – sorry, am out of the loop) that the contents of domainX/docroot are static and aren't changed when a domain is started up by a server other than the one that created the domain?

Comment by Mike Fitch [ 01/Apr/13 ]

Corrections to index.html included in main-docs 4.0_b26, which began getting picked up by GlassFish builds as of revision 61028.

Added [UB] to summary and set the fix version to 4.0.1 so this issue will get picked up by post-4.0 book-issue queries, as there is no Upgrade Guide for the 4.0 Open Source Edition release.





[GLASSFISH-21694] Update the bundled README.txt Created: 02/Mar/17  Updated: 02/Mar/17

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: David Delabassee Assignee: David Delabassee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

NA






[GLASSFISH-21126] Sync and cleanup GF download URL Created: 10/Jul/14  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0, 4.1
Fix Version/s: not determined

Type: Task Priority: Trivial
Reporter: David Delabassee Assignee: sbcaruso
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

NA



 Description   

The GF Install Guide mentions (#1) as the place to download GF but it is really (#2)

(#1) http://glassfish.java.net/public/downloadsindex.html
(#2) https://glassfish.java.net/download.html

I have put a redirect from (#1) to (#2) to temporally fix this. We should sync and agree on a single common URL for the next Doc rev.






[GLASSFISH-21116] update doc to remove GF commercial support Created: 08/Jul/14  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.1_dev
Fix Version/s: 4.1.1

Type: Task Priority: Trivial
Reporter: David Delabassee Assignee: jclingan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

NA



 Description   

remove from /glassfish/docs/features.html the mentions of commercial support.






[GLASSFISH-21096] wiki.sun.com is still mentioned in the doc Created: 24/Jun/14  Updated: 24/Jun/14

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: David Delabassee Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

NA



 Description   

wiki.sun.com is still mentioned in the doc.

Eg. http://wikis.sun.com/display/GlassFish/GlassFishFAQIndex is mentioned
in Annex 3 of the GF Troubleshooting guide (https://glassfish.java.net/docs/4.0/troubleshooting-guide.pdf).






Generated at Tue Apr 25 20:21:17 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.