[GLASSFISH-15349] references to sun glassfish in documentation Created: 26/Dec/10  Updated: 27/Dec/10

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

Type: Task Priority: Major
Reporter: Justin Lee Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-review

 Description   

After running "asadmin generate-domain-schema" i see several references to Sun or "Sun GlassFish" in the generated docs. This text comes from the hk2 dom interfaces classes and so will affect, in all likelihood, several different modules.



 Comments   
Comment by Justin Lee [ 26/Dec/10 ]

Looks like the JMS code is the biggest offender, but there's also a reference to sun-web.xml which has been renamed to glassfish-web.xml if I recall correctly.





[GLASSFISH-4283] asadmin commands: Runtime Management: Web Services Managment Created: 27/Feb/08  Updated: 06/Mar/12

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

Type: New Feature Priority: Major
Reporter: Jennifer Chou Assignee: Nazrul
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: 4,283

 Description   

Add the following asadmin commands for web services management:

configure-webservice-management
create-transformation-rule
delete-transformation-rule
list-registry-locations
list-transformation-rules
publish-to-registry



 Comments   
Comment by km [ 07/Jan/10 ]

routing ...

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-15948] [RFE] More configuration options for GlassFish when started using glassfish.jar Created: 10/Feb/11  Updated: 10/Feb/11

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

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

Existing OSGi environment



 Description   

When we start GlassFish inside an existing OSGi environment using the glassfish.jar we would like to specify at least the following:

  • custom domain.xml
  • custom logging.properties





[GLASSFISH-16850] One process per webapp Created: 13/Jun/11  Updated: 15/Jun/11

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

Type: New Feature Priority: Major
Reporter: cowwoc Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I don't know whether this proposal has been made before so I apologize in advance if I'm rehashing an old idea. I'd like to propose a simple but powerful architectural change: each webapp should run in its own JVM.

Benefits:

  • Ability to manage resources (memory, cpu, etc) on a per-webapp level
  • Improved fault-tolerance (a failing webapp won't take others down with it)
  • Ability to load JNI libraries from webapps without having to jump through any hoops or running into "java.lang.UnsatisfiedLinkError: Native Library x already loaded in another classloader."

Please let me know what you think.



 Comments   
Comment by vince kraemer [ 15/Jun/11 ]

a bit more background on this is here: http://stackoverflow.com/questions/6333056/running-webapps-in-separate-processes





[GLASSFISH-15256] Add a column on the admin console to display web app date and version Created: 17/Dec/10  Updated: 17/Dec/10

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

Type: New Feature Priority: Minor
Reporter: sroughto Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

glassfish admin


Tags: administration, console, source_control

 Description   

A question that frequently arises in the software lifecycle is, is the production server running the same code as the int/test/qa/dev server? This should be solved by a solid software release management scheme, of course, but it would be very helpful if the Glassfish admin console displayed a version string (e.g. $Id$) and deployment date for each app in the Web Applications table.

Currently a workaround is to include $Id$ (or equivalent) in the web.xml description field, and drill down in the admin console to view this file.






[GLASSFISH-15401] Print full cause when creation of external resource fails Created: 31/Dec/10  Updated: 31/Dec/10

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

Type: Improvement Priority: Minor
Reporter: rsmogura Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Glassfish v3.1 b35 / connector module



 Description   

When I create external resource I got only
SEVERE: RAR5011:Exception thrown creating initial context for external JNDI factory '[com.sun.jndi.ldap.LdapCtxFactory]'
SEVERE: RAR5047:Exception thrown creating initial context for external JNDI factory [localhost:389]
Looking at line 247 of ExternalJndiResourceDeployer it is visible exception is skipped and only message is logged. This can cause problem to determine why connection fails (PKIX certification path, invalid credentials, etc...).






[GLASSFISH-15907] configuring datasource/pool has "URL" and "Url" which is confusing Created: 09/Feb/11  Updated: 09/Feb/11

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

Type: Bug Priority: Minor
Reporter: mwessendorf Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File NewDS_Issue.png    

 Description   

configuring datasource/pool has "URL" and "Url" which is confusing

see screenshot






[GLASSFISH-15859] Undeploy issues with an app deployed to a stopped instance with missing resources Created: 04/Feb/11  Updated: 04/Feb/11

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

Type: Bug Priority: Minor
Reporter: lidiam Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File das.server.log     Text File in1.server.log     Text File in2.server.log    
Tags: 3_1-exclude

 Description   

This is a negative test case; tried it twice to verify issues. Steps to reproduce:

1. Start database
2. Create two standalone instances on localhost and start them.
3. Stop both instances.
4. Deploy scrumtoys application to one of the instances (it requires jdbc resources that are missing at this point).
5. Start both instances.
6. Add second instance as a target for this application, so the application will be deployed on two instances only.
7. Try to launch the application on both instances using the Launch link - 404 error is displayed for both, since necessary resources were not created for the application before deployment.
8. Try to undeploy the application - Issue 1: the following error is displayed:

An error has occurred
An error occurred during replication FAILURE: Command delete-application-ref failed on server instance in1: remote failure: Application scrumtoys not registered

In the least, the above should be a warning, not an error. However, I'm not sure this is correct, after all, the application is not properly deployed anywhere...

9. Click on application name - now it says it is enabled on 1 target (is this expected?). From the targets tab it looks like the application is enabled on the second instance.

10. Go to first instance page - Issue 2: it is indicated as restart required (why?). Click on restart button. The instance now shows as running.

11. Go back to Applications page and click Undeploy for scrumtoys again. This time application is undeployed without any errors in GUI.






[GLASSFISH-16107] java.rmi.NotBoundException on shutdown when Created: 28/Feb/11  Updated: 28/Feb/11

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

Type: Bug Priority: Minor
Reporter: chaoslayer Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I just tried to bind the JMX-connector to the IPv6 localhost address ([::1]).

It seems to work fine although I didn't verify specifically.

However, during shutdown I noticed this one:

java.rmi.NotBoundException: [::1]
at sun.rmi.registry.RegistryImpl.unbind(RegistryImpl.java:140)
Completed shutdown of Log manager service
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.stopAndUnexport(RMIConnectorStarter.java:314)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.shutdown(JMXStartupService.java:191)
at org.glassfish.admin.mbeanserver.JMXStartupService.shutdown(JMXStartupService.java:146)
at org.glassfish.admin.mbeanserver.JMXStartupService.access$000(JMXStartupService.java:87)
at org.glassfish.admin.mbeanserver.JMXStartupService$ShutdownListener.event(JMXStartupService.java:115)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
at com.sun.enterprise.v3.server.AppServerStartup.stop(AppServerStartup.java:425)
at com.sun.enterprise.glassfish.bootstrap.GlassFishImpl.stop(GlassFishImpl.java:88)

...the same appears to be the case with any other specific interface value.






[GLASSFISH-16063] Can't find resource for bundle java.util.PropertyResourceBundle, key xfmgr.errTransTags Created: 21/Feb/11  Updated: 06/Mar/12

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

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


 Description   

Seeing SEVERE message in server.log, can't find resource for bundle when looking for key xfmgr.errTransTags:

Feb 21, 2011 2:15:51 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 16 msec.
[#|2011-02-21T02:16:01.710+0000|INFO|glassfish3.1|null|_ThreadID=1;_ThreadName=Thread-1;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1-SNAPSHOT (build 42)|#]
[snip]
[#|2011-02-21T02:19:44.473+0000|SEVERE|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=76;_ThreadName=Thread-1;|Exception in thread "registration" |#]

[#|2011-02-21T02:19:44.476+0000|SEVERE|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=76;_ThreadName=Thread-1;|java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key xfmgr.errTransTags
at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
at java.util.ResourceBundle.getString(ResourceBundle.java:334)
at com.sun.enterprise.registration.impl.StringManager.getString(StringManager.java:64)
at com.sun.enterprise.registration.impl.SysnetTransferManager.transferServiceTags(SysnetTransferManager.java:118)
at com.sun.enterprise.registration.impl.SysnetRegistrationService.transferEligibleServiceTagsToSysNet(SysnetRegistrationService.java:153)
at com.sun.enterprise.registration.glassfish.TransferService$1.run(TransferService.java:85)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

#]


 Comments   
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-17187] Stateful Security Context for secured EJB remote method calls Created: 11/Aug/11  Updated: 11/Aug/11

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

Type: New Feature Priority: Minor
Reporter: snelders Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Kind request to implement stateful security context for secured EJB remote method calls.

Reason:
Currently AppservPasswordLoginModule.authenticateUser() of a login module securing an EJB is called for every remote call to a method of this EJB.
It would be better (in terms of performance) if after the first succesful authentication a 'session' is generated and used for any following EJB call to make the security context stateful instead of stateless as described by the CORBA Common Secure Interoperability (CSIv2).






[GLASSFISH-17203] Instances keep logging No route to host Created: 18/Aug/11  Updated: 27/Mar/14

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

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

CentOS 5.6 x64
java version "1.6.0_26"
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)



 Description   

I have a GlassFish 3.1.1 cluster setup and all of the instances keep filling up the logs with:

[#|2011-08-18T12:30:27.604-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=29;_ThreadName=Thread-2;|No route to host|#]

[#|2011-08-18T12:30:29.605-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=31;_ThreadName=Thread-2;|No route to host|#]

[#|2011-08-18T12:30:31.609-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=32;_ThreadName=Thread-2;|No route to host|#]

[#|2011-08-18T12:30:33.613-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=33;_ThreadName=Thread-2;|No route to host|#]

[#|2011-08-18T12:30:35.617-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=37;_ThreadName=Thread-2;|No route to host|#]

[#|2011-08-18T12:30:37.622-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=38;_ThreadName=Thread-2;|No route to host|#]

[#|2011-08-18T12:30:39.626-0500|SEVERE|glassfish3.1.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=39;_ThreadName=Thread-2;|No route to host|#]

I don't know what host they are trying to connect to, but everything seems to be working. Any idea what is cuasing this? As work around I've turned off logging for the com.sun.grizzly.config.GrizzlyServiceListener class, but I still want to know the cause.



 Comments   
Comment by julesbowden [ 27/Mar/14 ]

Experiencing the same thing:

Centos 6.5
java version "1.7.0_51"
OpenJDK Runtime Environment (rhel-2.4.4.1.el6_5-x86_64 u51-b02)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)





[GLASSFISH-16862] Domains Created with --portbase Listen on Unexpected Ports Created: 14/Jun/11  Updated: 04/Apr/12

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

Type: Bug Priority: Minor
Reporter: James Saffery Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

glassfish@aumbankslogg1:~> uname -a
Linux aumbankslogg1 2.6.32.29-0.3-default #1 SMP 2011-02-25 13:36:59 +0100 x86_64 x86_64 x86_64 GNU/Linux
glassfish@aumbankslogg1:~> java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
glassfish@aumbankslogg1:~> asadmin version
Version = GlassFish Server Open Source Edition 3.1 (build 43)
Command version executed successfully.



 Description   

I have created five domains to support multiple developers and testing as follows:

asadmin create-domain --portbase 9000 domain90
asadmin create-domain --portbase 9100 domain91
asadmin create-domain --portbase 9200 domain92
asadmin create-domain --portbase 9300 domain93
asadmin create-domain --portbase 9400 domain94

My expectation was that the each domain would only listen on the port numbers in the output of asadmin and also documented under portbase (in "asadmin help create-domain"), ie:

o Administration port: portbase + 48
o HTTP listener port: portbase + 80
o HTTPS listener port: portbase + 81
o JMS port: portbase + 76
o IIOP listener port: portbase + 37
o Secure IIOP listener port: portbase + 38
o Secure IIOP with mutual authentication port: portbase + 39
o JMX port: portbase + 86
o JPA debugger port: portbase + 9
o Felix shell service port for OSGi module management: portbase + 66

In reality, a domain sometimes but not always also listens on portbase + 176.

I have found that to reliably successfully start my domains, I need to do it in reverse order, ie domain94, domain93, domain92, domain91, domain90.

Otherwise, I can see the following type of error, for example

[#|2011-06-15T11:38:09.488+1000|SEVERE|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=main;|Shutting down v3 due
to startup exception : No free port within range: 9176=com.sun.enterprise.v3.services.impl.ServiceInitializerHandler@4ae7b77|#]

when domain90 is listening on 9176 (confirmed by "lsof -i -P") and domain91 therefore cannot start.



 Comments   
Comment by James Saffery [ 04/Apr/12 ]

After some research, I believe that the port at portbase + 176 is being used by Message Queue for an RMI Registry.

The output of asadmin and the documentation should specify this.

Also, it would be really preferable if the offset was a number less than 100 rather than the current 176. This would facilitate creating and using multiple domains as above





Generated at Mon Aug 03 09:14:45 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.