[GLASSFISH-5693] No automatic post-install processing Created: 27/Aug/08  Updated: 06/Mar/12

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

Type: Improvement Priority: Critical
Reporter: driscoll Assignee: msreddy
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Linux


Issuezilla Id: 5,693

 Description   

Unlike the v2 version of the updatecenter, the v3 version does not support
post-install or pre-remove processing.

While many of the functions that would require this can now be handled with OSGi
(with proper versioning), some cannot - for instance, modification of domain.xml.

Without support for this feature, the updatetool is simply a file delivery
mechanism, not an update mechanism.

I've spoken to the updatecenter2 team, and they tell me that this is a product
specific feature, and they will not be providing this functionality.



 Comments   
Comment by rebeccas [ 27/Aug/08 ]

This is not a bug it is an enhancement request. The user is requesting
functionality never intended for the tool.

Comment by Snjezana Sevo-Zenzerovic [ 27/Aug/08 ]

Apologies for the confusion - this should actually be filed under "other" or
"admin" since it has to do with addon configuration functionality and not with
GF upgrade tool.

Moving to more appropriate subcategory and assigning to Sreeni.

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-5818] Existence of preconfigured, additional DataSource with JNDI: jdbc/sample Created: 02/Sep/08  Updated: 06/Mar/12

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

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

Operating System: other
Platform: All


Issuezilla Id: 5,818

 Description   

A preconfigured DataSource with the JNDI-Name: jdbc/sample, which points to
DerbyPool, would contribute to the "standardization" of demo apps. Netbeans
created the datasource for GF v2, so most of the demo applications already rely
on the existence of it.

We used the jdbc/sample datasource for prototyping as well. It is especially
convenient for novice GF users and saves few clicks...



 Comments   
Comment by msreddy [ 25/Jan/10 ]

We already have a default datasource called jdbc/__default which points to
sun-appserv-samples. Can this datasource be used instead of jdbc/sample ?

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-10508] mqfailover bundled sample, ant/asant create-jms-resources, delete-jms-resources - failed Created: 22/Oct/09  Updated: 06/Jan/11

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: v2.1.1
Fix Version/s: None

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

Operating System: All
Platform: Sun


Issuezilla Id: 10,508
Status Whiteboard:

v3_exclude


 Description   

GF 2.1.1 b31f, x86 machines, mqfailover bundled EE sample.

When I've executed:
1) ant or asant deploy;
2) ant or asant all;
3) ant or asant undeploy;
everything was fine, including jms recourses creation or removing.

But when I've tried to execute (from the same terminal window):
1) ant or asant create-jms-resources;
2) ant or asant delete-jms-resources;
3) ant or asant create-jms-queuecf1;

The execution failed with such messages:

create-jms-connectionfactory:
[echo] Creating JMS con. factory with name jms/durable/BeanQCF

BUILD FAILED
/opt/glassfish/samples/ee-samples/failover/apps/mqfailover/build.xml:76: The
following error occurred while executing this line:
/opt/glassfish/samples/ee-samples/failover/apps/mqfailover/build.xml:126:
Execute failed: java.io.IOException: Cannot run program "$

{exec.asadmin}

":
error=2, No such file or directory



 Comments   
Comment by msreddy [ 22/Oct/09 ]

v3_excluded

Comment by msreddy [ 26/Oct/09 ]

v3_exclude

Comment by Ed Bratt [ 26/Oct/09 ]

Evaluate for v2.1.2

Comment by msreddy [ 27/Oct/09 ]

made P4





[GLASSFISH-10489] ant deploy failed because of syntax error during jdbc resources creation Created: 21/Oct/09  Updated: 06/Jan/11

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: v2.1.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: easarina Assignee: msreddy
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: 10,489
Status Whiteboard:

v3_excluded


 Description   

GF 2.1.1 EE build 31f, x86 machines. For EE bundled samples that use JDBC
resources (dukesbookstore, product, roster) asant deploy failed because of a
syntax error during JDBC connection pool creation:

===================================================================
create-jdbc-connection-pool_common:
[exec] Usage: create-jdbc-connection-pool
--datasourceclassname classname [--terse=false] [--echo=false]
[--interactive=true] [--host localhost] [--port 4848|4849]
[--secure | -s] [--user admin_user] [--passwordfile file_name]
[--restype res_type] [--steadypoolsize 8] [--maxpoolsize 32]
[--maxwait 60000] [--poolresize 2] [--idletimeout 300]
[--isolationlevel isolation_level] [--isisolationguaranteed]
[--isconnectvalidatereq=false] [--validationmethod auto-commit]
[--validationtable tablename] [--failconnection=false]
[--allownoncomponentcallers=false]
[--nontransactionalconnections=false] [--description text]
[--property (name=value)[:name=value]*] jdbc_connection_pool_id
[exec] CLI131 Invalid property syntax.
[exec] Result: 1
...............................................................................

[sun-appserv-admin] ADMVAL1054: Attribute value (pool-name =
bookstorePool) is not found in list of jdbc connection pools.
[sun-appserv-admin] ADMVAL1070: Create of jdbc resource is
rejected.

BUILD FAILED
=====================================================================
If to create JDBC poool manually, for example:

asadmin create-jdbc-connection-pool --property
User=BOOKSTORE:Password=BOOKSTORE:dataBaseName=DerbyDB:serverName=localhost:port
Number=1527 --restype javax.sql.DataSource --datasourceclassname
org.apache.derby.jdbc.ClientDataSource bookstorePool

And then to execute again asant deploy, build will fail again because can not
run sql script:

[echo] Create the CMP tables if they will not be created by the appserver at
deploy time.

BUILD FAILED
/opt/sailfin/samples/ee-samples/failover/apps/dukesbookstore/build.xml:73: The
following error occurred while executing this line:
/opt/sailfin/samples/common-ant.xml:1145: Class Not Found: JDBC driver
$

{db.driver}

could not be loaded

I've executed the sql script manually.

If to use ant instead of asant, class error will happen.



 Comments   
Comment by msreddy [ 22/Oct/09 ]

specific to v2 ee-sample, v3_excluded

Comment by msreddy [ 22/Oct/09 ]

v3_excluded

Comment by Ed Bratt [ 22/Oct/09 ]

Updated the target version to 2.1.2. Priority adjusted to p4

Comment by easarina [ 22/Oct/09 ]

I've executed sql script manually, using for example such command:

$DERBY_HOME/bin/ij
$AS_HOME/samples/ee-samples/failover/apps/dukesbookstore/setup/sql/derby/derby.books.sql

But I've modified sql script and added a first line there:

connect
'jdbc:derby://localhost:1527/DerbyDB;create=true;user=BOOKSTORE;password=BOOKSTORE';





[GLASSFISH-10490] docs directory is absent under samples directory Created: 21/Oct/09  Updated: 06/Jan/11

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: v2.1.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: easarina Assignee: msreddy
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: 10,490

 Description   

GF 2.1.1 b31f, bundled ee samples, x86 machine. The documents in sam;ples docs
directories have such reference:
=============================================================
The general instructions for building, deploying, and running sample
applications are provided in
<a href="../../../../../docs/common-procedures.html">Building, Deploying, and
Running Sample Applications</a>.
In reading this document, use the following application-specific variables for
this application:
=========================================================

But this docs directory is absent under samples directory.



 Comments   
Comment by jagadesh [ 21/Oct/09 ]

Will not fix for v2.1.1 release (downgrading to P4).
Sreeni,
Please add the solution to the bug or update the online doc.

Thanks.

Comment by Ed Bratt [ 22/Oct/09 ]

Set Target to 2.1.2

Comment by easarina [ 22/Oct/09 ]

I want to add that an absent doc common-procedures.html has the instruction how
to build, deploy, run any sample using asant. All samples have correspondent
references to this doc. So without this doc users would not know how to build,
deploy, run samples using asant.

Also in the absent samples/docs directory would be list.html that comtains the
description of all samples.





[GLASSFISH-6759] In-memory replication not enabled for pure web-apps (clusterjsp) Created: 12/Nov/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: lwhite Assignee: msreddy
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: 6,759

 Description   

This issue was originally filed in SailFin issue
tracker as issue 1379 https://sailfin.dev.java.net/issues/show_bug.cgi?id=1379
It is being moved to GlassFish issue tracker because it is
really a GlassFish sample app issue



 Comments   
Comment by lwhite [ 12/Nov/08 ]

copying comments from SailFin issue 1379 for reference:

When deploying clusterjsp on a SailFin cluster with availabilityenabled=true ,
in memory replication is not enabled for the app. This seems to be an issue with
the persistence-type attribute. The value in the sample is "ha".

If I change the value to "replicated" things work fine. As per the sun-web.xml
DTD "ha" is the correct value for persistence-type.

------- Additional comments from sonymanuel Mon Nov 10 00:25:20 +0000 2008 -------

Created an attachment (id=824)
clusterjsp app

------- Additional comments from shreedhar_ganapathy Mon Nov 10 03:18:50 +0000
2008 -------

This is a samples issue. There seems to be no samples subcomponent.
Also see the GlassFish issue :
https://glassfish.dev.java.net/issues/show_bug.cgi?id=5408

------- Additional comments from sonymanuel Mon Nov 10 04:40:51 +0000 2008 -------

The DTD sun-web-app_2_4-1.dtd does not document a value "replicated" for
persistence type. If replicated is the correct value then the DTD has to be
updated.

------- Additional comments from jluehe Mon Nov 10 17:28:21 +0000 2008 -------

In sun-web-app_2_5-0.dtd, we relaxed persistence-type to be of type CDATA, so it
can be set to anything (including "replicated"):

sun-web-app_2_4-1.dtd:

<!ENTITY % persistence-type "(memory | file | custom | ha | s1ws60 | mmap)">
<!ATTLIST session-manager persistence-type %persistence-type; "memory">

sun-web-app_2_5-0.dtd:

<!ATTLIST session-manager persistence-type CDATA "memory">

I recommend that the sun-web.xml in the clusterjsp sample be upgraded to
sun-web-app_2_5-0.dtd.

Where can I find the source code for this example so I can make the change?

------- Additional comments from jluehe Mon Nov 10 19:35:42 +0000 2008 -------

Reassigning, since I'm not authorized to make any changes to samples

------- Additional comments from shreedhar_ganapathy Mon Nov 10 19:44:34 +0000
2008 -------

Sony
Can you share where you get the clusterjsp app? Is this from Sailfin's samples
directory?

------- Additional comments from msreddy Mon Nov 10 20:03:56 +0000 2008 -------

Can we use the one which is a part of ee quickstart sample, it'll be easy to
update this sample.

------- Additional comments from lwhite Wed Nov 12 09:53:31 +0000 2008 -------

Closing this issue in SailFin issue tracker
because we are moving and re-filing it as
a GlassFish issue under sample-apps.
See: https://glassfish.dev.java.net/issues/show_bug.cgi?id=6759

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 kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

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-5408] ClusterJSP ear app hardcodes replication type to HA in sun-web.xml Created: 31/Jul/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: shreedhar_ganapathy Assignee: msreddy
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,408

 Description   

Given that we have both replication and ha type supported, the hard coding of
the replication type to ha in the clusterjsp.ear app overrides configuration
made through admin interfaces. The underlying cause is not then known to users
causing them to look at places like node agent synchronization.

We need to remove this hard coded value and let the admin interface
configuration take effect. This will allow people to use it for both in-memory
replication and HADB based state persistence.



 Comments   
Comment by shreedhar_ganapathy [ 31/Jul/08 ]

targetted for 9.1.1 or v2.1 release

Comment by shreedhar_ganapathy [ 31/Jul/08 ]

This is specifically for the sample included in ee-samples and not the one under
quickstart.

Comment by shreedhar_ganapathy [ 09/Nov/08 ]

Will this be fixed for v2.1?

Also see
https://sailfin.dev.java.net/issues/show_bug.cgi?id=1379
for a similar issue with the web app in samples.

Comment by msreddy [ 10/Nov/08 ]

This issue is about the same clusetr jsp sample for which the following sailfin
issue exists.
https://sailfin.dev.java.net/issues/show_bug.cgi?id=1379

Making the change as suggested by Jan in issue 1379 is easy but the complex part
is rebuilding, packaging and testing samples.

Since the sample bundled with the product works fine (accroding to Shreedhar), I
propose to release note it considering the resources/effort needed.

Comment by shreedhar_ganapathy [ 10/Nov/08 ]

The issue was opened based on feedback from field who expressed a pain point
when trying to use the Ent profile samples. So fixing this would be preferable.

As suggested by Jan in the Sailfin issue,
https://sailfin.dev.java.net/issues/show_bug.cgi?id=1379
could the following comment by Jan be followed?

"In sun-web-app_2_5-0.dtd, we relaxed persistence-type to be of type CDATA, so it
can be set to anything (including "replicated"):

sun-web-app_2_4-1.dtd:

<!ENTITY % persistence-type "(memory | file | custom | ha | s1ws60 | mmap)">
<!ATTLIST session-manager persistence-type %persistence-type; "memory">

sun-web-app_2_5-0.dtd:

<!ATTLIST session-manager persistence-type CDATA "memory">

I recommend that the sun-web.xml in the clusterjsp sample be upgraded to
sun-web-app_2_5-0.dtd."

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 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-9001] Blueprints instruction has to be updated. Created: 03/Aug/09  Updated: 06/Mar/12

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

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

Operating System: All
Platform: Sun


Issuezilla Id: 9,001

 Description   

V3 build 57, Solaris 10 Sparc and petstore sample from:
http://java.sun.com/javaee/downloads, scroll to the bottom of the page and look
for Java Blueprints Update 6.

I've tried to setup this petstore with V3. I've noticed several issue with a
blueprints instruction: blueprints/install.html

1) An instruction has to say clearly that blueprints along with javaee5 samples
have to be placed under <AS_HOME>/samples directory.
2) An instruction has a reference to
javaee5/docs/UserREADME.html, which says: "Add <javaee.home>/lib/ant/bin
directory to your PATH environment variable." But V3 doesn't include ant. So
in the PATH has to be included ant bin directory, that can have any location.
And because now ant is not bundled with V3, has to be mentioned the required
ant version.
3) None of the instructions mention that in
samples/bp-project/app-server.properties has to be configured a correct
javaee.home.



 Comments   
Comment by msreddy [ 24/Sep/09 ]

Based on Carla, blueprints are not bundled in Java EE SDK 6 so lowering the
priority to P4.

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-2276] <BT6518990>Need a better directory tree structure to arrange different component samples Created: 31/Jan/07  Updated: 06/Mar/12

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

Type: Bug Priority: Minor
Reporter: gfbugbridge Assignee: msreddy
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: 2,276

 Description   

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6518990
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6518990
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am testing SDK b05 (app platforms).
When I installed the SDK build, I see many samples are put directly under samples
directory, it makes the tree structure not so clean.

Could we add a subcomponent name as a subdirectory under samples directory, just
like the way we arranged the javaee5 samples.

Suggested directory tree:
.../samples/subcomname/differentsamples

I mark this issue as P2 since I feel if we decide to fix then it is better to fix in
Beta.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description Hi Sreeni:
Here are the info requested:

  • sdk build which is used: It is SDK b05
  • what components were selected: This bug is regarding to all the components. We
    should have a sub directory under samples directory.
  • list of samples: Here are the samples we have under samples directory, as you
    can see there is no component sub directory, I like the way you arranged javaee5,
    so I suggest other component sample should also follow this way.

d:\AppServer Install\sdkup3pv\samples>ls
atomserver common.properties jsf-extensions wadl
blogapps index.html phobos
bp-project javaee5 quickstart
common-ant.xml jmaki rest-impl

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [2-High]a better tree structure to arrange the sample XXXXXX 2007-01-30 02:40:26 GMT

**********READ-ONLY Data from Bugtraq Ends********



 Comments   
Comment by gfbugbridge [ 08/Mar/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6518990
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6518990
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am testing SDK b05 (app platforms).
When I installed the SDK build, I see many samples are put directly under samples
directory, it makes the tree structure not so clean.

Could we add a subcomponent name as a subdirectory under samples directory, just
like the way we arranged the javaee5 samples.

Suggested directory tree:
.../samples/subcomname/differentsamples

I mark this issue as P2 since I feel if we decide to fix then it is better to fix in
Beta.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description Hi Sreeni:
Here are the info requested:

  • sdk build which is used: It is SDK b05
  • what components were selected: This bug is regarding to all the components. We
    should have a sub directory under samples directory.
  • list of samples: Here are the samples we have under samples directory, as you
    can see there is no component sub directory, I like the way you arranged javaee5,
    so I suggest other component sample should also follow this way.

d:\AppServer Install\sdkup3pv\samples>ls
atomserver common.properties jsf-extensions wadl
blogapps index.html phobos
bp-project javaee5 quickstart
common-ant.xml jmaki rest-impl

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Evaluation I am
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [2-High]a better tree structure to arrange the sample XXXXXX 2007-01-30 02:40:26 GMT

Priority changed from [2-High] to [3-Medium]
it is ok to fix this in XXXXXX 2007-03-07 23:41:55 GMT

**********READ-ONLY Data from Bugtraq Ends********

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 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-4688] execption when running a lottery-annotation-ear's appclient Created: 08/Apr/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: vince kraemer Assignee: msreddy
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,688

 Description   

installed java_ee_sdk-5_05-solaris-i586.bin
built NB 6.1 rc1 from sources

started built IDE

registered the installed SDK's domain1 with the IDE
opened the project <SDK-INSTALL>/samples/javaee5/enterprise/lottery-annotation-ear

select the project node labeled lottery-annotation-ear.

right-click on the selected node and select the Run item from the menu

This is the message you see in the output window:
...
post-init:
init-check:
init:
run-ac:
/export/home/vkraemer/SDK2/samples/javaee5/enterprise/lottery-annotation-ear/build.xml:47:
The following error occurred while executing this line:
/export/home/vkraemer/SDK2/samples/javaee5/enterprise/lottery-annotation-ear/build.xml:64:
The following error occurred while executing this line:
/export/home/vkraemer/SDK2/samples/javaee5/enterprise/lottery-annotation-ear/nbproject/build-impl.xml:266:
The following error occurred while executing this line:
/export/home/vkraemer/SDK2/samples/javaee5/enterprise/lottery-annotation-ear/nbproject/build-impl.xml:304:
Warning: Could not find file
/export/home/vkraemer/SDK2/domains/domain1/generated/xml/j2ee-apps/lottery-annotation-ear/lottery-annotation-earClient.jar
to copy.
BUILD FAILED (total time: 6 seconds)



 Comments   
Comment by vince kraemer [ 08/Apr/08 ]

changing the display name of the project resolves this issue...

replace

<display-name>annotation-simple</display-name>

with

<display-name>lottery-annotation-ear</display-name>

in lottery-annotation-ear/src/conf/application.xml seems to resolve the issue.

If the application.xml file is removed the appclient executes correctly. So
does the web app...

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 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-4681] need better error message Created: 08/Apr/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: 9.1peur2
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: vince kraemer Assignee: msreddy
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: XML File build.xml    
Issuezilla Id: 4,681

 Description   

installed java_ee_sdk-5_05-solaris-i586.bin
built NB 6.1 rc1 from sources

started built IDE

registered the installed SDK's domain1 with the IDE
opened the project <SDK-INSTALL>/samples/javaee5/enterprise/security-stateless-ear

switch to the files view

expanded the security-stateless-ear node.
expanded the build.xml node.
select the create-file-user node
right-click on the selected node and select the Run Target item from the menu

The following message appear in the output window.
create-file-user:
/export/home/vkraemer/SDK2/samples/javaee5/enterprise/security-stateless-ear/build.xml:47:
The following error occurred while executing this line:
Target "keygen-common" does not exist in the project "security-stateless-ear".
BUILD FAILED (total time: 0 seconds)

This is pretty useless for a user.



 Comments   
Comment by vince kraemer [ 08/Apr/08 ]

I added <import file="../../../bp-project/app-server-ant.xml"/>

right below the other import in the .../security-stateless-ear/build.xml

This got me a slightly better error message...

create-file-user:
check:
/export/home/vkraemer/SDK2/samples/javaee5/enterprise/security-stateless-ear/build.xml:48:
The following error occurred while executing this line:
/export/home/vkraemer/SDK2/samples/bp-project/app-server-ant.xml:447: Property
javaee.server.passwordfile not specified. Please
specify the javaee.server.passwordfile property in
'bp-project/build.properties'.
You will also need to ensure that the passwordfile is present and contains
AS_ADMIN_PASSWORD.
BUILD FAILED (total time: 0 seconds)

This gave me something to work against which is better.

Comment by vince kraemer [ 08/Apr/08 ]

modified build.xml attached.

I think it handles the "create-file-user" as part of the Run item on the project
node's right click menu.

It may be worth incorporating into the sample...

Comment by vince kraemer [ 08/Apr/08 ]

Created an attachment (id=1426)
modified build.xml

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 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-4551] ManagementFactory.getPlatformMBeanServer causes ClassNotFoundException Created: 31/Mar/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: other
Affects Version/s: 9.1peur1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: yardus Assignee: msreddy
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux
URL: https://glassfish.dev.java.net/issues/show_bug.cgi?id=1409


Attachments: XML File domain.xml     Text File server.log    
Issuezilla Id: 4,551
Status Whiteboard:

as911-na


 Description   

We at the NetBeans Profiler team are still experiencing problems as described in
the issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=1409.
The only difference is that the problems manifests itself only if using
clustered environment. For single instance setup it works correctly.
Also, there is a P2 issue filed for Profiler which is a direct result of the
aforementioned problem.
Will attach domain.xml and log file.



 Comments   
Comment by yardus [ 31/Mar/08 ]

Created an attachment (id=1416)
domain.xml

Comment by yardus [ 31/Mar/08 ]

Created an attachment (id=1417)
server.log

Comment by yardus [ 31/Mar/08 ]

The dependent profiler issue: http://www.netbeans.org/issues/show_bug.cgi?id=117464

Comment by dochez [ 18/Jul/08 ]

9.1 mbeanserver issue

Comment by harpreet [ 04/Sep/08 ]

Marking target milestone as 9.1.1

Comment by km [ 14/Oct/08 ]

yardus, can you tell us the severity of this problem? I think the problem is in
setting up the correct classpath in EE case, so that the server finds the
necessary classes.

harpreet – depending upon submitter's response, we may want to fix it. But
since this is rather old, I am not sure if enough people will run into it.

Byron – please take a look.

Comment by yardus [ 15/Oct/08 ]

As for severity - it practically prevents profiling of glassfish instances
participating in a cluster. Failing to resolve this issue will make the bad
impression of not being able to use Sun tools to profile Sun application server

Comment by harpreet [ 20/Oct/08 ]

Please scrub issue and see if it is critical to v2.1.

Comment by Nazrul [ 25/Oct/08 ]

Requesting Sreeni to evaluate this issue.

Comment by msreddy [ 28/Oct/08 ]

I am able to reproduce the reported issue on windows as given below.

01 Built AS 9.1.1 on windows.
02 Installed Netbeans IDE 6.1 with web distribution.
03 Started netbeans, added server on Services tab
04 Started server in profile mode and attached the profiler, it worked fine only
for the first time.
05 Created a second domain, started in profile mode, attached profiler. Ran for
10 seconds and hung with the excption given below.
Because of freeze, I had to restart the machine.
After restarting, when I start either domain (default or newly created) it is
not able to start in profiler mode and similar log message is displayed.

At this time, I think it is caused during the launch process (it may not have
gotten to the log manager yet) and I don't see any additional info to debug this
further.

Since submitter feels that it is critical, suggest that some one faimilar with
launcher looks at this.

Could not load Logmanager "com.sun.enterprise.server.logging.ServerLogManager"
java.lang.ClassNotFoundException: com.sun.enterprise.server.logging.ServerLogManager
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.util.logging.LogManager$1.run(LogManager.java:166)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:156)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at com.sun.jmx.trace.Trace.initDestination(Trace.java:46)
at com.sun.jmx.trace.Trace.<clinit>(Trace.java:25)
at javax.management.MBeanServerFactory.debug(MBeanServerFactory.java:524)
at
javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:483)
at
javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511)
at
javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213)
at
javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174)
at
sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
at
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
at
org.netbeans.lib.profiler.server.system.HeapDump.initialize16(HeapDump.java:102)
at
org.netbeans.lib.profiler.server.system.HeapDump.initialize(HeapDump.java:78)
at
org.netbeans.lib.profiler.server.ProfilerInterface.initProfilerInterface(ProfilerInterface.java:464)
at
org.netbeans.lib.profiler.server.ProfilerServer.initSupportingFunctionality(ProfilerServer.java:973)
at
org.netbeans.lib.profiler.server.ProfilerServer.doActivate(ProfilerServer.java:904)
at
org.netbeans.lib.profiler.server.ProfilerServer.activate(ProfilerServer.java:512)
Failed to load MBeanServerBuilder class
com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder:
java.lang.ClassNotFoundException:
com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder
Profiler Agent: Initializing...
Profiler Agent: Options: >"C:\Program Files\NetBeans 6.1\profiler3\lib",5140<

Comment by msreddy [ 30/Oct/08 ]

Reassiging to Byron for his help with the launcher code.

Comment by msreddy [ 03/Nov/08 ]

Based on discussion with Yardus (the submitter) it is important that we get this
fixed for latest v3 version. Once we make sure that it works for v3, and since
it works with domain, the priority may be reduced for v2.

We need to work closely with Yardus to understand the profiler interaction with
launcher to fix this issue.

Comment by Nazrul [ 03/Nov/08 ]

...

Comment by harpreet [ 04/Nov/08 ]

Based on Sreeni's comments it looks like the issue is not critical to v2.1. Removing it from the approved
list. Sreeni can you comment on the underlying cause.

Comment by msreddy [ 04/Nov/08 ]

pl. see my comment on 03nov08

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 jchristi [ 12/Feb/10 ]

adding me to cc

Comment by hegalor [ 16/Jun/10 ]

Would be nice, if that issue could be fixed.

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-2161] <BT2141385>JES5 b09,8/4. Derby 10.1.3 was restarted, but AS was not, then problems happened Created: 20/Jan/07  Updated: 06/Mar/12

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

Type: Bug Priority: Minor
Reporter: gfbugbridge Assignee: msreddy
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: 2,161

 Description   

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=2141385
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2141385
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification forward port the fix from XXXXXX 2006-08-28 19:22:43 GMT

**********READ-ONLY Data from Bugtraq Ends********



 Comments   
Comment by gfbugbridge [ 21/Jan/07 ]
      • Issue 2156 has been marked as a duplicate of this issue. ***
Comment by gfbugbridge [ 16/Feb/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=2141385
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2141385
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification forward port the fix from XXXXXX 2006-08-28 19:22:43 GMT

**********READ-ONLY Data from Bugtraq Ends********

Comment by gfbugbridge [ 17/Feb/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=2141385
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2141385
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification forward port the fix from XXXXXX 2006-08-28 19:22:43 GMT

**********READ-ONLY Data from Bugtraq Ends********

Comment by gfbugbridge [ 31/Mar/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=2141385
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2141385
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification forward port the fix from XXXXXX 2006-08-28 19:22:43 GMT

Priority changed from [3-Medium] to [4-Low]
the j2ee 1.4 samples are in maintenance XXXXXX 2007-03-30 23:19:24 GMT

**********READ-ONLY Data from Bugtraq Ends********

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-2162] <BT6485231>Got confusing message when using NB to run java5ee sample annotation-override-interceptor-ear Created: 20/Jan/07  Updated: 06/Mar/12

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

Type: Bug Priority: Minor
Reporter: gfbugbridge Assignee: msreddy
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: 2,162

 Description   

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6485231
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6485231
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am using 9.1 build 22 with the NB 5.5 RC2 build on window XP
When using NB to run java5ee sample annotation-override-interceptor-ear, I am seeing the
following message in red in the output "Duplicated project name in import", however
the sample runs fine. I feel this can cause user confusion and don't know what and
where is a problem or not. We should remove this kind message

----- job output ----
run:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
run-ant:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
run-nb:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
pre-init:

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am seeing the same kind confusing message when running other sampels, please look into them and fix the same.

For example, when I ran interceptor-stateless-ear, I saw this issue.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [3-Medium]improve sample XXXXXX 2006-10-23 23:20:20 GMT

**********READ-ONLY Data from Bugtraq Ends********



 Comments   
Comment by gfbugbridge [ 21/Jan/07 ]
      • Issue 2157 has been marked as a duplicate of this issue. ***
Comment by gfbugbridge [ 16/Feb/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6485231
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6485231
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am using 9.1 build 22 with the NB 5.5 RC2 build on window XP
When using NB to run java5ee sample annotation-override-interceptor-ear, I am seeing the
following message in red in the output "Duplicated project name in import", however
the sample runs fine. I feel this can cause user confusion and don't know what and
where is a problem or not. We should remove this kind message

----- job output ----
run:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
run-ant:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
run-nb:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
pre-init:

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am seeing the same kind confusing message when running other sampels, please look into them and fix the same.

For example, when I ran interceptor-stateless-ear, I saw this issue.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [3-Medium]improve sample XXXXXX 2006-10-23 23:20:20 GMT

**********READ-ONLY Data from Bugtraq Ends********

Comment by gfbugbridge [ 17/Feb/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6485231
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6485231
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am using 9.1 build 22 with the NB 5.5 RC2 build on window XP
When using NB to run java5ee sample annotation-override-interceptor-ear, I am seeing the
following message in red in the output "Duplicated project name in import", however
the sample runs fine. I feel this can cause user confusion and don't know what and
where is a problem or not. We should remove this kind message

----- job output ----
run:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
run-ant:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
run-nb:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init:
Duplicated project name in import. Project annotation-override-interceptor-ear-impl defined first in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\ant-deploy.xml and again in D:\AppServer Install\9.0UR1sdk\samples\javaee5\enterprise\annotation-override-interceptor-ear\nbproject\build-impl.xml
pre-init:

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description I am seeing the same kind confusing message when running other sampels, please look into them and fix the same.

For example, when I ran interceptor-stateless-ear, I saw this issue.

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to [3-Medium]improve sample XXXXXX 2006-10-23 23:20:20 GMT

**********READ-ONLY Data from Bugtraq Ends********

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 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-2159] <BT6451263>javaee5:SDK:start-domain and start-db targets should be executed in background Created: 20/Jan/07  Updated: 06/Mar/12

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

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

Operating System: Solaris
Platform: All


Issuezilla Id: 2,159

 Description   

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6451263
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6451263
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description The 2 target command above (start-domain and start-db) when execute does not termimate at the console terminal.
STEPS TO REPRODUCE:
1. Install AppServer 9PE SDK version
2. Follow the common build instuction to setup build enviroment
3. From (eg, app_dir: install_dir/samples/ws/javaee5/enterprise/customer-cmp-ear) execute
ant start-domain or start-db
BUG:
domain1 was started; howerver, the command was not return to the prompt for next ant target
It's shown as message below:
----------------------------------------------------------------------------------------
start-domain:
[echo] Starting default domain for C:/Sun/AppServer9
[exec] Starting Domain domain1, please wait.
[exec] Log redirected to C:\Sun\AppServer9\domains\domain1\logs\server.log.
[exec] Domain domain1 is ready to receive client requests. Additional services are being started in background.
[exec] Domain [domain1] is running [Sun Java System Application Server Platform Edition 9.0 (build b03)] with its configuration and logs at: [C:\Sun\AppServer9\domains].
[exec] Admin Console is available at http://localhost:4848.
[exec] Use the same port [4848] for "asadmin" commands.
[exec] User web applications are available at these URLs:
[exec] http://localhost:8080 https://localhost:8181.
[exec] Following web-contexts are available:
[exec] [/web1 /asadmin ].
[exec] Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[exec] [service:jmx:rmi:///jndi/rmi://swoon:8686/jmxrmi] for domain management purposes.
[exec] Domain listens on at least following ports for connections:
[exec] [8080 8181 4848 3700 3820 3920 8686 ].

Terminate batch job (Y/N)? y

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to XXXXXX 2006-07-21 01:26:12 GMT

**********READ-ONLY Data from Bugtraq Ends********



 Comments   
Comment by gfbugbridge [ 21/Jan/07 ]
      • Issue 2155 has been marked as a duplicate of this issue. ***
Comment by gfbugbridge [ 15/Feb/07 ]

*********READ-ONLY Data from Bugtraq*********************
Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6451263
Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6451263
**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Description The 2 target command above (start-domain and start-db) when execute does not termimate at the console terminal.
STEPS TO REPRODUCE:
1. Install AppServer 9PE SDK version
2. Follow the common build instuction to setup build enviroment
3. From (eg, app_dir: install_dir/samples/ws/javaee5/enterprise/customer-cmp-ear) execute
ant start-domain or start-db
BUG:
domain1 was started; howerver, the command was not return to the prompt for next ant target
It's shown as message below:
----------------------------------------------------------------------------------------
start-domain:
[echo] Starting default domain for C:/Sun/AppServer9
[exec] Starting Domain domain1, please wait.
[exec] Log redirected to C:\Sun\AppServer9\domains\domain1\logs\server.log.
[exec] Domain domain1 is ready to receive client requests. Additional services are being started in background.
[exec] Domain [domain1] is running [Sun Java System Application Server Platform Edition 9.0 (build b03)] with its configuration and logs at: [C:\Sun\AppServer9\domains].
[exec] Admin Console is available at http://localhost:4848.
[exec] Use the same port [4848] for "asadmin" commands.
[exec] User web applications are available at these URLs:
[exec] http://localhost:8080 https://localhost:8181.
[exec] Following web-contexts are available:
[exec] [/web1 /asadmin ].
[exec] Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[exec] [service:jmx:rmi:///jndi/rmi://swoon:8686/jmxrmi] for domain management purposes.
[exec] Domain listens on at least following ports for connections:
[exec] [8080 8181 4848 3700 3820 3920 8686 ].

Terminate batch job (Y/N)? y

**********READ-ONLY Data from Bugtraq Ends********
*********READ-ONLY Data from Bugtraq*********************
Justification Priority changed from [] to XXXXXX 2006-07-21 01:26:12 GMT

Priority changed from [3-Medium] to [4-Low]
The issue is specific to windows and the targets start-domain or start-datbase are usually meant for build XXXXXX 2007-02-14 19:54:12 GMT

**********READ-ONLY Data from Bugtraq Ends********

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.





Generated at Mon Aug 31 23:08:51 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.