[GLASSFISH-19479] JMS Resource -> Destination Resources shows ALL admin object resource, even when its not using jmsra resource adapter Created: 27/Dec/12  Updated: 02/Jan/13  Resolved: 27/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0_b68_EE7MS3
Fix Version/s: 4.0_b69

Type: Bug Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-19488 UI changes related to JMS resources Resolved

 Description   

Step to reproduce:

  • deploy the attached rar
  • create an admin object resource named 'ABC' using 'genericra' as the resource adapter
  • ABC will show up under JMS Resource tree node, this is a bug. This is not a JMS resource and list-jms-resources command doesn't show that either.


 Comments   
Comment by Anissa Lam [ 27/Dec/12 ]

Changed the code that populates the JMS resources tree node.

JMS Resources -> Connection Factories is generated by calling
list-jms-resources --restype javax.jms.ConnectionFactory
list-jms-resources --restype javax.jms.TopicConnectionFactory
list-jms-resources --restype javax.jms.QueueConnectionFactory
and combining the returned list.

JMS Resources -> Destination Resources is generated by calling
list-jms-resources --restype javax.jms.Queue
list-jms-resources --restype javax.jms.Topic
and combining the returned list.

However, due to GLASSFISH-19482, those tree nodes maybe wrong. Once GLASSFISH-19482 is fixed, the tree node will be correct.





[GLASSFISH-19264] Provide an option to list-domains to indicate what administrative port they are listening on Created: 30/Oct/12  Updated: 24/Dec/12  Resolved: 24/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin
Affects Version/s: 4.0_b60
Fix Version/s: 4.0_b69

Type: Improvement Priority: Minor
Reporter: ljnelson Assignee: Tom Mueller
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-19478 Document the --long and --header opti... Sub-task Resolved Gail Risdal  
Tags: asadmin, list-domains

 Description   

It would be nice if I could do something like:

asadmin list-domains --verbose
domain1 running (4848)
someotherdomain not running (5048)

...i.e. get administrative port information alongside the report of which domains are up and running.



 Comments   
Comment by Tom Mueller [ 24/Dec/12 ]

Committed revision 57816.

Revision: 57816
Author : tmueller
Date : Dec 24, 2012 1:20:12 PM
GLASSFISH-19264 - add --long and --header options to list-domains. With -l, the output looks like this:

DOMAIN ADMIN_HOST ADMIN_PORT RUNNING RESTART_REQUIRED
domain1 localhost 4848 false false
Command list-domains executed successfully.

The -h=false option can be used to suppress the header.





[GLASSFISH-19201] version command to be enhanced to return the parts of the version in extraproperties Created: 22/Oct/12  Updated: 19/Sep/14  Resolved: 24/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin
Affects Version/s: 9.0pe, 9.0peur1_dev, 9.0peur1, 9.1pe_dev, 9.1pe, 9.1peur1_dev, 9.1peur1, 9.1peur2_b03, 9.1peur2, 9.1.1_dev, 9.1.1, v2.1, v2.1.1_dev, v2.1.1, V3, v3.0.1, 3.1_b02, 3.1_ms01, 3.1_b03, 3.1_b05, 3.1_b06, 3.1_ms02, 3.1_b07, 3.1_b08, 3.1_b10, 3.1_ms03, 3.1_b12, 3.1_b13, 3.1_b14, 3.1_b15, 3.1_b16, 3.1_ms04, 3.1_b17, 3.1_b18, 3.1_b19, 3.1_b20, 3.1_ms05, 3.1_b21, 3.1_b22, 3.1_b23, 3.1_b24, 3.1_b25, 3.1_b26, 3.1_ms06, 3.1_b27, 3.1_b28, 3.1_b29, 3.1_b30, 3.1_b31, 3.1_b32, 3.1_ms07, 3.1_b33, 3.1_b34, 3.1_b35, 3.1_b36, 3.1_b37, 3.1_b38, 3.1_b39, 3.1_b40, 3.1_b41 , 3.1_b42, 3.1_b43, 3.1_ms08, 3.1, 3.1.1_b01, 3.1.1_b02, 3.1.1_b03 , 3.1.1_b04 , 3.1.1_b05, 3.1.1_b06 , 3.1.1_b07 , 3.1.1_b08, 3.1.1_b09, 3.1.1_b10, 3.1.1_b11, 3.1.1_b12, 3.1.1, 3.1.2_b01, 3.1.2_b02, 3.1.2_b03, 3.1.2_b04, 3.1.2_b05, 3.1.2_b06, 3.1.2_b07, 3.1.2_b09, 3.1.2_b10, 3.1.2_b11, 3.1.2_b12, 3.1.2_b13, 3.1.2_b14, 3.1.2_b15, 3.1.2_b16, 3.1.2_b17, 3.1.2_b18, 3.1.2_b19, 3.1.2_b20, 3.1.2_b21, 3.1.2_b22, 3.1.2_b23, 3.1.2, 3.1.2.2, 4.0_b01, 4.0_b02, 4.0_b03, 4.0_b04, 4.0_b05, 4.0_b06, 4.0_b08, 4.0_b09, 4.0_b10, 4.0_b11, 4.0_b12, 4.0_b13, 4.0_b14, 4.0_b15, 4.0_b16, 4.0_b17, 4.0_b18, 4.0_b19, 4.0_b20, 4.0_b21, 4.0_b22, 4.0_b23, 4.0_b24, 4.0_b25, 4.0_b26, 4.0_b27, 4.0_b28, 4.0_b29, 4.0_b30, 4.0_b31, 4.0_b32_ms1, 4.0_b33, 4.0_b34, 4.0_b35, 4.0_b36, 4.0_b37, 4.0_b38_ms2, 4.0_b39, 4.0_b40, 4.0_b41, 4.0_b42, 4.0_b43, 4.0_b44_ms3, 4.0_b45, 4.0_b46, 4.0_b47, 4.0_b48, 4.0_b49, 4.0_b50_ms4, 4.0_b51, 4.0_b52, 4.0_b53, 4.0_b54, 4.0_b55, 4.0_b56_ms5, 4.0_b57, 4.0_b58, 4.0_b59, 4.0_b60, 4.0_b61, 4.0_b62_ms6, 4.0_b63, 4.0_b64_EE7MS2, 4.0_b65, 4.0_b66, 4.0_b67_ms7, 4.0_b68_EE7MS3, 4.0_b69, 4.0_b70, 4.0_b71, 4.0_b72_EE7MS4, 4.0_b73, 4.0_b74, 4.0_b75, 4.0_b76_EE7MS5, 4.0_b77, 4.0_b78, 4.0_b79, 4.0_b80_EE7MS6, 4.0_b81, 4.0_b82_EE7MS7, 4.0_b83, 4.0_b84_RC1, 4.0_b85, 4.0_b86_RC2, 4.0_b87_RC3, 4.0, 4.1
Fix Version/s: 4.0_b69

Type: Improvement Priority: Major
Reporter: vishnudwaram Assignee: Tom Mueller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Currently to find out the version of the GlassFish the only way we can get from REST is by:

https://locahost:4848/management/domain/version

But unfortunately this will return the value as "GlassFish Server Open Source Edition 3.1.2.2 (build 5)"

Need a way to find the version. Ex: in this case version of glass fish is "3.1.2.2"

This rest version command endpoint has to be enhanced to return the parts of the version in extraProperties.

Without this enhancement, to get the version users will endup parsing the string which can be error prone if any changes are made to the string format in future



 Comments   
Comment by Tom Mueller [ 24/Dec/12 ]

Fixed in revision 57815. The extra properties are:

  • version (the product name and version)
  • full-version (this is the message that is currently printed)
  • version-number (just the number part of the version, e.g., 4.0)




[GLASSFISH-19139] Unable to build kernel using relative path Created: 09/Oct/12  Updated: 24/Dec/12  Resolved: 24/Dec/12

Status: Resolved
Project: glassfish
Component/s: test
Affects Version/s: 4.0_b56_ms5
Fix Version/s: 4.0_b69

Type: Bug Priority: Minor
Reporter: Sanjeeb Sahoo Assignee: Tom Mueller
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I tried to build kernel module using relative path to pom.xml as the command below shows:

mvn -f nucleus/core/kernel/pom.xml clean install

Results :

Tests in error:
privacyTests(com.sun.enterprise.v3.admin.PrivacyTest)
deployUndeployTest(org.glassfish.tests.kernel.deployment.EventsTest)
badUndeployTest(org.glassfish.tests.kernel.deployment.EventsTest)

Tests run: 23, Failures: 0, Errors: 3, Skipped: 5

Given below stacktrace of one of the tests:

ss141213@Sahoo:/space/ss141213/WS/gf$ more /space/ss141213/WS/gf/./trunk/nucleus/core/kernel/target/surefire-reports/com.sun.enterprise.v3.admin.PrivacyTest.txt
-------------------------------------------------------------------------------
Test set: com.sun.enterprise.v3.admin.PrivacyTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.011 sec <<< FAILURE!
privacyTests(com.sun.enterprise.v3.admin.PrivacyTest) Time elapsed: 0.009 sec <<< ERROR!
java.lang.NullPointerException
at org.glassfish.tests.utils.Utils.getNewHabitat(Utils.java:131)
at com.sun.enterprise.v3.admin.PrivacyTest.privacyTests(PrivacyTest.java:58)
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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
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 org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:241)
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:537)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

What is surprising is if I cd to core/kernel and run mvn clean install, the tests pass!



 Comments   
Comment by Tom Mueller [ 24/Dec/12 ]

Just tried this and am not seeing the failure on the current trunk.
There are 5 skipped tests, but this is either when in that directory or not.





Generated at Thu Sep 03 18:56:57 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.