[GLASSFISH-20826] NLS: Update Tool Bootstrap does not configured during install GF Created: 27/Sep/13  Updated: 27/Sep/13  Resolved: 27/Sep/13

Status: Closed
Project: glassfish
Component/s: configuration
Affects Version/s: 4.0_b89_RC5
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Major
Reporter: sunny-gui Assignee: Masoud Kalali
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: OEL6 x64 ko_KR.UTF-8
Bundle: java_ee_sdk-7-web-b89b-jdk7-linux-x64-ml.sh
JDK: jdk1.7.0_25 x64


Attachments: JPEG File updateTool_notConfigured_ko.jpg     JPEG File updateTool_zhCN.jpg    

 Description   

To Reproduce:
1. Set JAVA_HOME=JKD7_Install_DIR
2. run ./java_ee_sdk-7-web-b89b-jdk7-linux-x64-ml.sh
3. In the Update Tool page, fields of the Proxy Host and Proxy Port are truncated.
– It is a known issue, for more details please see https://java.net/jira/browse/GLASSFISH-20503
4. Click on Next to Summary page, it is end of GF installation page.

Results:
In the Summary page,
R1. The Status is 'incompletely' in Korean.
R2. For Update Tool Bootstrap,it is 'not configured' in Korean.

Attached screen shot for your reference.

I checked in the same env(with same bundle in the same host) with setting locale as zh_CN.UTF-8, this issue is not reproducible in the zh_CN.UTF-8.



 Comments   
Comment by sunny-gui [ 27/Sep/13 ]

I reinstalled GF in the same env(same bundle, same locale and same host), it is not reproducible, so close it.





[GLASSFISH-20675] password alias does not work for create-jmsdest Created: 02/Jul/13  Updated: 19/Dec/13  Resolved: 02/Jul/13

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 4.0
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Minor
Reporter: tak09 Assignee: David Zhao
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7



 Description   

Password alias does not work for create-jmsdest.

To reproduce the issue

1. Create password alias
asadmin create-password-alias jms-password

2. Set password alias
C:\>asadmin set server.jms-service.jms-host.default_JMS_host.admin-password=$

{ALIAS=jmspassword-alias}

3. Execute create-jmsdest

C:\>asadmin create-jmsdest --desttype queue JMSQueue2
remote failure: Unable to create JMS Destination.
Command create-jmsdest failed.

server.log shows the following error.

[2013-07-02T12:35:20.874+1000] [glassfish 4.0] [SEVERE] [] [] [tid: _ThreadID=35 _ThreadName=admin-listener(2)] [timeMillis: 1372732520874] [levelValue: 1000] [[
Error in dealiasing the password ${ALIAS=jmspassword-alias}

: Alias jmspassword-alias does not exist]]

[2013-07-02T12:35:20.887+1000] [glassfish 4.0] [SEVERE] [] [] [tid: _ThreadID=35 _ThreadName=Thread-4] [timeMillis: 1372732520887] [levelValue: 1000] [[
java.lang.SecurityException: JMX connector server jmxrmi: Failure detected during authentication com.sun.messaging.jmq.auth.api.FailedLoginException: [B4051]: Forbidden admin
at com.sun.messaging.jmq.jmsserver.management.agent.MQJMXAuthenticator.authenticate(MQJMXAuthenticator.java:135)
at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

4. Note that create-jms-resource works as expected.
C:\>asadmin create-jms-resource --restype javax.jms.ConnectionFactory jms/DurableConnectionFactory
Connector resource jms/DurableConnectionFactory created.
Command create-jms-resource executed successfully.



 Comments   
Comment by David Zhao [ 02/Jul/13 ]

The case is invalid that you are using different password alias. It is jms-password when creating, and jmspassword-alias when saving.

1. Create password alias
asadmin create-password-alias jms-password

2. Set password alias
C:\>asadmin set server.jms-service.jms-host.default_JMS_host.admin-password=${ALIAS=jmspassword-alias}

Comment by tak09 [ 02/Jul/13 ]

I still have the same problem with the same password alias.
Please see below.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\>asadmin start-domain
Waiting for domain1 to start ..........................
Successfully started the domain : domain1
domain Location: C:\glassfish\glassfish-4.0\glassfish4\glassfish\domains\domain1
Log File: C:\glassfish\glassfish-4.0\glassfish4\glassfish\domains\domain1\logs\server.log
Admin Port: 4848
Command start-domain executed successfully.

C:\>asadmin create-password-alias jms-password-alias
Enter the alias password>
Enter the alias password again>
Command create-password-alias executed successfully.

C:\>asadmin set server.jms-service.jms-host.default_JMS_host.admin-password=$

{ALIAS=jms-password-alias}
server.jms-service.jms-host.default_JMS_host.admin-password=${ALIAS=jms-password-alias}

Command set executed successfully.

C:\>asadmin create-jmsdest --desttype queue JMSQueue2
remote failure: Unable to create JMS Destination.
Command create-jmsdest failed.

C:\>

Comment by David Zhao [ 02/Jul/13 ]

What are the error messages in server.log?

Comment by tak09 [ 02/Jul/13 ]

[2013-07-02T16:02:02.925+1000] [glassfish 4.0] [SEVERE] [] [] [tid: _ThreadID=34 _ThreadName=Thread-4] [timeMillis: 1372744922925] [levelValue: 1000] [[
java.lang.SecurityException: JMX connector server jmxrmi: Failure detected during authentication com.sun.messaging.jmq.auth.api.FailedLoginException: [B4051]: Forbidden admin
at com.sun.messaging.jmq.jmsserver.management.agent.MQJMXAuthenticator.authenticate(MQJMXAuthenticator.java:135)
at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)

....... contiunes.

Comment by tak09 [ 02/Jul/13 ]

server.log and screenshot are available here.
https://www.dropbox.com/sh/ohsgcldetn89r2m/zecKTw3tWb

Comment by David Zhao [ 02/Jul/13 ]

The error message means wrong password - either alias is not found or the unaliased password is wrong.

1. Please make sure you can do create-jmsdest successfully without password alias, for example, asadmin set server.jms-service.jms-host.default_JMS_host.admin-password=admin

2. Make sure you created password alias with correct password: It is 'admin' by default.

I tried password alias by inputing password 'admin' at my environment, and create-jmsdest does work for me.

Comment by Kevin Dean [ 19/Dec/13 ]

This may be related to https://java.net/jira/browse/GLASSFISH-20938; see that issue for a description of the underlying problem.





[GLASSFISH-20510] URISyntaxException getting monitoring data Created: 11/May/13  Updated: 19/Sep/14  Resolved: 06/Jun/13

Status: Resolved
Project: glassfish
Component/s: monitoring
Affects Version/s: 4.0_b88_RC4
Fix Version/s: 4.0_b89_RC5, 4.1

Type: Bug Priority: Critical
Reporter: marina vatkina Assignee: Tim Quinn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-20613 Need to improve fix to URISyntaxExcep... Resolved
Tags: 4_0-approved

 Description   

1. start GF and derby
2. asadmin set configs.config.server-config.monitoring-service.module-monitoring-levels.ejb-container=HIGH
3. In devtests/ejb/timer/timertests do 'ant build deploy run'
4. asadmin get -m "*"
remote failure: Error during authorization
java.net.URISyntaxException: Illegal character in path at index 100: admin:/server/applications/ejb-timer-service-app/TimerBean/bean-methods/countTimersOwnedByServerIds-[Ljava%5C/lang%5C/String;/dotted-name
Command get failed.

Full stack trace:
java.net.URISyntaxException: Illegal character in path at index 100: admin:/server/applications/ejb-timer-service-app/TimerBean/bean-methods/countTimersOwnedByServerIds-[Ljava%5C/lang%5C/String;/dotted-name
at java.net.URI$Parser.fail(URI.java:2829)
at java.net.URI$Parser.checkChars(URI.java:3002)
at java.net.URI$Parser.parseHierarchical(URI.java:3086)
at java.net.URI$Parser.parse(URI.java:3034)
at java.net.URI.<init>(URI.java:824)
at com.sun.enterprise.admin.util.CommandSecurityChecker.resourceURIFromAccessCheck(CommandSecurityChecker.java:363)
at com.sun.enterprise.admin.util.CommandSecurityChecker.checkAccessRequired(CommandSecurityChecker.java:253)
at com.sun.enterprise.admin.util.CommandSecurityChecker.authorize(CommandSecurityChecker.java:193)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1203)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1500(CommandRunnerImpl.java:108)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1762)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1674)
at org.glassfish.admin.rest.resources.admin.CommandResource.executeCommand(CommandResource.java:396)
at org.glassfish.admin.rest.resources.admin.CommandResource.execCommandSimpInMultOut(CommandResource.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:125)
at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:91)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:346)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:341)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:101)
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:224)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:198)
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:946)
at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:331)
at org.glassfish.admin.rest.adapter.JerseyContainerCommandService$1.service(JerseyContainerCommandService.java:169)
at org.glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java:179)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:246)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544)
at java.lang.Thread.run(Thread.java:722)



 Comments   
Comment by Tim Quinn [ 13/May/13 ]

Because command authorization is involved here, I looked at this problem. With Marina's suggestion to add

asadmin set configs.config.server-config.monitoring-service.module-monitoring-levels.ejb-container=HIGH

before trying the "asadmin get" command, I was able to reproduce the problem.

This seems to be a new failure that does not seem to be related to a change in command authorization itself.

The "get" command creates AccessCheck objects dynamically based on what specific data is retrieved (rather than, for example, using the @AccessRequired annotation which would require knowing at build-time what resource name is being accessed). As part of creating the AccessCheck object, the resource name is converted into a URI which the authorization service can consume.

For the "get" command the resource name is derived from the dotted name of the data item being accessed. In this case, the dotted name is

"server.applications.ejb-timer-service-app.TimerBean.bean-methods.countTimersOwnedByServerIds-[Ljava\.lang\.String;.dotted-name"

It's the MonitoringReporter class which converts the dotted names into resource names. Up until now at least the dotted names processed during "get" have been valid Java identifiers, so that class's getAccessChecks method did not need to do any URI encoding to handle special characters.

Is this dotted name what's intended? If so, then the MonitoringReporter.getAccessChecks method can be revised to encode the URI.

If not then whatever is creating the dotted name should be changed to create a valid string.

Comment by marina vatkina [ 13/May/13 ]

Fixed the steps in the description.

Comment by Byron Nevins [ 13/May/13 ]

Following the instructions this looks fishy –

--libraries $

{libraries}

Is this right?


deploy-common-pe:
[exec] asadmin --host localhost --port 4848 --user admin --passwordfile /Users/wnevins/dev/v2/appserv-tests/config/adminpassword.txt --interactive=false --echo=true --terse=true deploy --libraries ${libraries}

--force=false --precompilejsp=false --verify=false --retrieve /Users/wnevins/dev/v2/appserv-tests/build/module/archive --generatermistubs=false --availabilityenabled=false --asyncreplication=true --target server --keepreposdir=false --keepfailedstubs=false --isredeploy=false --logreportederrors=true --_classicstyle=false /Users/wnevins/dev/v2/appserv-tests/build/module/archive/ejb-timer-timertestsApp.ear
[exec] Application deployed with name ejb-timer-timertestsApp.
[echo] Deployment on target server server successful

Comment by marina vatkina [ 13/May/13 ]

This doesn't affect monitoring

Comment by Byron Nevins [ 13/May/13 ]

This probably has nothing to do with Monitoring, and everything to do with the authorization code that was added to the get command.

Comment by Byron Nevins [ 13/May/13 ]

Analysis:

EjbMonitoringUtils.stringify() – it sets the name of the probe to be the method name with the args appended.

If the args happen to have an array then a "[" character will be in the name.
Which URI parsing code barfs on and throws an Exception.
The security code doesn't handle that exception – it just reports it and the command fails.

It is unusual to create a probe name in this fashion. It is only done by ejb-container.
Nevertheless I think that the security code ought to handle it in any case – even if the above method is changed to NOT put "[" into names.

– that's why I've assigned it to Tim.

Marina could provide a work-around by not allowing the "[" into names by,say, search & replace of that character with something else.

Note:
The probes of interest are in ejb container ->

~/dev/bg/main/appserver/ejb> tg countTimersOwnedByServerIds
/Users/wnevins/dev/bg/main/appserver/ejb/ejb-full-container/src/main/java/org/glassfish/ejb/persistent/timer/PersistentEJBTimerService.java[189]:
totalTimers = timerLocal_.countTimersOwnedByServerIds(serverIds);
/Users/wnevins/dev/bg/main/appserver/ejb/ejb-full-container/src/main/java/org/glassfish/ejb/persistent/timer/TimerBean.java[588]:
public String[] countTimersOwnedByServerIds(String[] serverIds) {
/Users/wnevins/dev/bg/main/appserver/ejb/ejb-full-container/src/main/java/org/glassfish/ejb/persistent/timer/TimerLocal.java[148]:
String[] countTimersOwnedByServerIds(String[] serverIds);

Comment by Byron Nevins [ 13/May/13 ]

Note that this issue is a great candidate for adding a permanent regression Dev Test...

Comment by Byron Nevins [ 13/May/13 ]

I made a simple change/built/tested. It fixes the problem just fine:

I did NOT check it in though...

~/dev/v2/appserv-tests/devtests/ejb/timer/timertests> getm "*" | wc -l
8525

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

Index: src/main/java/com/sun/ejb/monitoring/stats/EjbMonitoringUtils.java
===================================================================
— src/main/java/com/sun/ejb/monitoring/stats/EjbMonitoringUtils.java (revision 61944)
+++ src/main/java/com/sun/ejb/monitoring/stats/EjbMonitoringUtils.java (working copy)
@@ -133,6 +133,7 @@
sb.append(SEP).append(c.getName().replaceAll("_", "
."));
}
String result = sb.toString().replaceAll("
.", "\\\\.");
+ result = StringUtils.replace(result, "[", "_ARRAY_");
if (_logger.isLoggable(Level.FINE))

{ _logger.fine("==> Converted method String: " + result); }
Comment by Byron Nevins [ 13/May/13 ]

In case you use my work-around code change in the previous comment, you'd also need this import:

import com.sun.enterprise.util.StringUtils;

Comment by Tim Quinn [ 14/May/13 ]

I expect we will use standard URI encoding to deal with this.

Comment by Tim Quinn [ 14/May/13 ]

What is the impact on the customer of the bug?
The 'asadmin get -m ' command can incorrectly report an authorization failure, depending on what monitored properties are being accessed.

How likely is it that a customer will see the bug and how serious is the bug?
This is a regression which causes at least one EJB devtest to fail.

What is the cost/risk of fixing the bug?
low

How risky is the fix? How much work is the fix? Is the fix complicated?
low - We will use the standard Java SE URLEncoding class to encode the URI that is based on the property.

Is there an impact on documentation or message strings?
No

Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
Any tests which use asadmin commands. (The EJB devtest which Marina described earlier will show whether the bug has been fixed or not.)

Which is the targeted build of 4.0 for this fix?
4.0_b89

If this an integration of a new version of a component from another project,
what are the changes that are being brought in? This might be list of
Jira issues from that project or a list of revision messages.
N/A

Comment by Tom Mueller [ 14/May/13 ]

Approved for 4.0.

Comment by Tim Quinn [ 14/May/13 ]

Fixes checked into the branch and the trunk.

Project: glassfish
Repository: svn
Revision: 61977
Author: tjquinn
Date: 2013-05-14 14:55:27 UTC
Link:

Log Message:
------------
Fix for GLASSFISH-20510 URISyntaxException getting monitoring data

The "get" command, as some other asadmin commands, must compute the admin security access checks dynamically based on exactly which resources that invocation of the command accesses. The CommandSecurityChecker class then submits each individual resource separately to the authorization service, passing each resource as a URI. In the case of "get" the resource names come from the dotted names for the items reported.

Some EJB monitoring probes (reported using 'get -m "*"' for example) contain characters that are not legal in a URI, but CommandSecurityChecker did not encode such names.

With this fix, such encoding takes place using the standard SE URLEncoding class. The effect is a no-op if the resource name already conforms to URI/URL rules and encodes the resource name otherwise.

Approved for 4.0: Tom
Reviewed: Tom
Test: Passed QL tests, the sequence of commands identified by Marina in the issue

Revisions:
----------
61977

Modified Paths:
---------------
branches/4.0/nucleus/admin/util/src/main/java/com/sun/enterprise/admin/util/CommandSecurityChecker.java

======
Revisions:
----------
61976

Modified Paths:
---------------
trunk/main/nucleus/admin/util/src/main/java/com/sun/enterprise/admin/util/CommandSecurityChecker.java

Comment by Tim Quinn [ 06/Jun/13 ]

The change I made earlier side-stepped the problem but in a way that causes problems in the resource names that are constructed for admin access control. The problem does NOT affect 4.0 but should be fixed.

Comment by Tim Quinn [ 06/Jun/13 ]

I decided to open a new issue, targeting a release after 4.0, rather than confusing the sequence of events on the old issue.





[GLASSFISH-20499] Potential IllegalStateException in form based login Created: 10/May/13  Updated: 10/May/13  Resolved: 10/May/13

Status: Resolved
Project: glassfish
Component/s: web_container
Affects Version/s: None
Fix Version/s: 4.0_b89_RC5

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

Tags: 4_0-approved

 Description   

In FormAuthenticator#forwardToLoginPage, it has the following:

        if (isChangeSessionIdOnAuthentication()) {
            request.changeSessionId();
        }

This is a potential IllegalStateException here as session may be null.



 Comments   
Comment by Shing Wai Chan [ 10/May/13 ]

fix in trunk
Sending web-core/src/main/java/org/apache/catalina/authenticator/FormAuthenticator.java
Transmitting file data .
Committed revision 61945.

Comment by Shing Wai Chan [ 10/May/13 ]
  • What is the impact on the customer of the bug?
    a possible IllegalStateException when there is no session created for a form based login application
  • What is the cost/risk of fixing the bug?
    low. One line fix
  • Is there an impact on documentation or message strings?
    No.
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
    SQE web tests
  • Which is the targeted build of 4.0 for this fix?
    4.0_b89
  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.
    N/A
Comment by Shing Wai Chan [ 10/May/13 ]

port fix to 4.0 branch
Sending src/main/java/org/apache/catalina/authenticator/FormAuthenticator.java
Transmitting file data .
Committed revision 61946.





[GLASSFISH-20455] Updated 3RD-PARTY-LICENSE.txt and 3RD-PARTY-LICENSE-WEB-PROFILE.txt Created: 02/May/13  Updated: 15/May/13  Resolved: 15/May/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b87_RC3
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Blocker
Reporter: Joe Di Pol Assignee: michael.y.chen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved

 Description   

We need updated content for 3RD-PARTY-LICENSE.txt and 3RD-PARTY-LICENSE-WEB-PROFILE.txt.



 Comments   
Comment by michael.y.chen [ 07/May/13 ]

3rd party license file update. This is a must have. txt file update with no risk.

Comment by michael.y.chen [ 09/May/13 ]

Nancy and I are working on this. We should have this done by 5/13.

Comment by michael.y.chen [ 14/May/13 ]

The 3rd party license files are delivered to RE. They will include it in the build.

Comment by Romain Grécourt [ 14/May/13 ]

3 party files are actually part of the source tree, see https://svn.java.net/svn/glassfish~svn/branches/4.0/appserver/packager/legal/src/main/resources/glassfish/legal/

Re-opening, the right way is to update those license files properly.

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

Licenses checked into GlassFish trunk and branch workspaces (which is prerequisite for GF b89). Keeping the issue open until RI workspace checkin is complete.

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

Updated 3rd party licenses checked into RI branch and trunk workspaces.





[GLASSFISH-20282]  javax--javaee-api--7.0-b84 pom doesn't specify a license Created: 11/Apr/13  Updated: 14/May/13  Resolved: 14/May/13

Status: Resolved
Project: glassfish
Component/s: packaging
Affects Version/s: 4.0_b85
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Major
Reporter: myfear Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: fishcat

 Description   

Running the http://mojo.codehaus.org/license-maven-plugin/examples/example-add-license.html plugin with

mvn license:add-third-party

on a project with the ee 7 api as a dependency I noticed, that the api doesn't specify a license. That should be the case.
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>7.0-b84</version>
<scope>provided</scope>
</dependency>



 Comments   
Comment by myfear [ 11/Apr/13 ]

Here is a simple sample project to test it ..
https://github.com/myfear/two-factor-sam

  • M
Comment by shreedhar_ganapathy [ 16/Apr/13 ]

Romain, could you look into this asap?

Comment by Romain Grécourt [ 16/Apr/13 ]

I have other on going tasks. This will have to wait till b86 I think.

Comment by Romain Grécourt [ 14/May/13 ]
Index: nucleus/pom.xml
===================================================================
--- nucleus/pom.xml	(revision 61971)
+++ nucleus/pom.xml	(working copy)
@@ -61,10 +61,20 @@
         <developerConnection>scm:svn:https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus</developerConnection>
         <url>https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus</url>
     </scm>
+    
     <issueManagement>
         <system>IssueTracker</system>
         <url>http://java.net/jira/browse/GLASSFISH</url>
     </issueManagement>
+    
+    <licenses>
+      <license>
+        <name>CDDL + GPLv2 with classpath exception</name>
+        <url>http://glassfish.java.net/nonav/public/CDDL+GPL.html</url>
+        <distribution>repo</distribution>
+        <comments>A business-friendly OSS license</comments>
+      </license>
+    </licenses>    
 
     <mailingLists>
         <mailingList>
Sending        nucleus/pom.xml
Transmitting file data .
Committed revision 61972.




[GLASSFISH-20281] SDK 4.0 - Connector samples (mailconnector) fails to deploy Created: 11/Apr/13  Updated: 14/May/13  Resolved: 14/May/13

Status: Resolved
Project: glassfish
Component/s: sample_apps
Affects Version/s: 4.0_b83
Fix Version/s: 4.0_b89_RC5

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

Installed java_ee_sdk-7-b83-unix.sh*, on OEL6 machine, using Maven version 3.0.5. Configured Maven environment as noted in http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/BG+Development+Environment+Guide


Tags: 4_0-approved

 Description   

Following the "Building, Deploying, Running the Application" instructions that came with the Connector sample, one is not able to deploy the sample. The exact commands executed were:

1. [test@wolfrun] $ cd $WORKSPACE/glassfish4/samples/connectors
2. [test@wolfrun] $ mvn clean install
3. [test@wolfrun] $ mvn cargo:start -Dglassfish.home=$WORKSPACE/glassfish4

Step 1 and 2 work without problem. Please note that when executing "mvn install", the sample is built as follows
[INFO] ------------------------------------------------------------------------
[INFO] Building Mail Enterprise Application 4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — maven-enforcer-plugin:1.2:enforce (enforce-maven) @ mailconnector-ear —
[INFO]
[INFO] — maven-enforcer-plugin:1.2:enforce (enforce-versions) @ mailconnector-ear —
[INFO]
[INFO] — maven-ear-plugin:2.8:generate-application-xml (default-generate-application-xml) @ mailconnector-ear —
[INFO] Generating application.xml
[INFO]
[INFO] — maven-resources-plugin:2.4.3:resources (default-resources) @ mailconnector-ear —
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/agpineda/workspace/glassfish4/samples/connectors/mailconnector/mailconnector-ear/src/main/resources
[INFO]
[INFO] — maven-ear-plugin:2.8:ear (default-ear) @ mailconnector-ear —
[INFO] Copying artifact [ejb:org.glassfish-samples:mailconnector-mdb:4.0-SNAPSHOT] to [mailconnector-mdb.jar]
[INFO] Copying artifact [war:org.glassfish-samples:mailconnector-web:4.0-SNAPSHOT] to [mailconnector-web.war]
[INFO] Copying artifact [rar:org.glassfish-samples:mailconnector-ra:4.0-SNAPSHOT] to [mailconnector.rar]
[INFO] Copy ear sources to /home/agpineda/workspace/glassfish4/samples/connectors/mailconnector/mailconnector-ear/target/mailconnector-ear-4.0-SNAPSHOT
[INFO] Including custom manifest file [/home/agpineda/workspace/glassfish4/samples/connectors/mailconnector/mailconnector-ear/target/mailconnector-ear-4.0-SNAPSHOT/META-INF/MANIFEST.MF]
[INFO] Building jar: /home/agpineda/workspace/glassfish4/samples/connectors/mailconnector/mailconnector-ear/target/mailconnector-ear.ear
[INFO]
[INFO] — maven-install-plugin:2.3.1:install (default-install) @ mailconnector-ear —
[INFO] Installing /home/agpineda/workspace/glassfish4/samples/connectors/mailconnector/mailconnector-ear/target/mailconnector-ear.ear to /home/agpineda/.m2/repository/org/glassfish-samples/mailconnector-ear/4.0-SNAPSHOT/mailconnector-ear-4.0-SNAPSHOT.ear
[INFO] Installing /home/agpineda/workspace/glassfish4/samples/connectors/mailconnector/mailconnector-ear/pom.xml to /home/agpineda/.m2/repository/org/glassfish-samples/mailconnector-ear/4.0-SNAPSHOT/mailconnector-ear-4.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] mailconnector application ......................... SUCCESS [0.975s]
[INFO] MailConnector Resource Adapter .................... SUCCESS [2.695s]
[INFO] Mail MDB Reciever ................................. SUCCESS [1.261s]
[INFO] Mail Web Application .............................. SUCCESS [0.784s]
[INFO] Mail Enterprise Application ....................... SUCCESS [0.336s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.378s
[INFO] Finished at: Wed Apr 10 20:46:54 PDT 2013
[INFO] Final Memory: 28M/346M
[INFO] ------------------------------------------------------------------------

To deploy the sample, "mvn cargo:start -Dglassfish.home=$WORKSPACE/glassfish4" is executed and the following errors are seen
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.glassfish-samples:mailconnector-ra:rar:4.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-rar-plugin is missing. @ line 86, column 17
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 71, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] mailconnector application
[INFO] MailConnector Resource Adapter
[INFO] Mail MDB Reciever
[INFO] Mail Web Application
[INFO] Mail Enterprise Application
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building mailconnector application 4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — cargo-maven2-plugin:1.3.2:start (default-cli) @ mailconnector-app —
[INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-glassfish:jar:1.3.2 for container glassfish3x
[INFO] [talledLocalContainer] Using port 4848 for Admin.
[INFO] [talledLocalContainer] Using port 8080 for HTTP Instance.
[INFO] [talledLocalContainer] Using port 7676 for JMS.
[INFO] [talledLocalContainer] Using port 3700 for IIOP.
[INFO] [talledLocalContainer] Using port 8181 for HTTP_SSL.
[INFO] [talledLocalContainer] Using port 3820 for IIOP_SSL.
[INFO] [talledLocalContainer] Using port 3920 for IIOP_MUTUALAUTH.
[INFO] [talledLocalContainer] Using port 8686 for JMX_ADMIN.
[INFO] [talledLocalContainer] Using port 6666 for OSGI_SHELL.
[INFO] [talledLocalContainer] Using port 9009 for JAVA_DEBUGGER.
[INFO] [talledLocalContainer] Distinguished Name of the self-signed X.509 Server Certificate is:
[INFO] [talledLocalContainer] [CN=wolfrun.us.oracle.com,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
[INFO] [talledLocalContainer] Distinguished Name of the self-signed X.509 Server Certificate is:
[INFO] [talledLocalContainer] [CN=wolfrun.us.oracle.com-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
[INFO] [talledLocalContainer] Domain cargo-domain created.
[INFO] [talledLocalContainer] Domain cargo-domain admin port is 4848.
[INFO] [talledLocalContainer] Domain cargo-domain admin user is "admin".
[INFO] [talledLocalContainer] Command create-domain executed successfully.
[INFO] [talledLocalContainer] GlassFish 3.x starting...
[INFO] [talledLocalContainer] Waiting for cargo-domain to start .......
[INFO] [talledLocalContainer] Successfully started the domain : cargo-domain
[INFO] [talledLocalContainer] domain Location: /home/agpineda/workspace/glassfish4/glassfish/domains/cargo-domain
[INFO] [talledLocalContainer] Log File: /home/agpineda/workspace/glassfish4/glassfish/domains/cargo-domain/logs/server.log
[INFO] [talledLocalContainer] Admin Port: 4848
[INFO] [talledLocalContainer] Command start-domain executed successfully.
[INFO] [talledLocalContainer] Application deployed with name cargocpc.
[INFO] [talledLocalContainer] Command deploy executed successfully.
[INFO] [talledLocalContainer] GlassFish 3.x started on port [8080]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building MailConnector Resource Adapter 4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — cargo-maven2-plugin:1.3.2:start (default-cli) @ mailconnector-ra —
[INFO] [talledLocalContainer] Port for cargo-domain (4848) is in use. Try a different port number.
[INFO] [talledLocalContainer] CLI130: Could not create domain, cargo-domain
[INFO] [talledLocalContainer] Command create-domain failed.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] mailconnector application ......................... SUCCESS [32.192s]
[INFO] MailConnector Resource Adapter .................... FAILURE [1.596s]
[INFO] Mail MDB Reciever ................................. SKIPPED
[INFO] Mail Web Application .............................. SKIPPED
[INFO] Mail Enterprise Application ....................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 34.321s
[INFO] Finished at: Wed Apr 10 20:50:33 PDT 2013
[INFO] Final Memory: 8M/212M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.3.2:start (default-cli) on project mailconnector-ra: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.3.2:start failed: Failed to create a GlassFish 3.x standalone configuration: GlassFish admin command failed: asadmin exited 1 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :mailconnector-ra



 Comments   
Comment by shreedhar_ganapathy [ 19/Apr/13 ]

Hi Siva
Can you please take a look at this connector sample issue?
We need to resolve soon.

Comment by Sivakumar Thyagarajan [ 19/Apr/13 ]

I don't know why cargo tries to create the cargo-domain again during the deployment of the RAR. This appears to be the reason the maven invocation has failed. Requesting Dapeng to investigate.

Comment by dapeng_hu [ 24/Apr/13 ]

The mail connector project is an ear application which contains multiple sub modules: MDB, web and rar. In this case, the cargo goals should be executed in the mailconnector-ear module, instead of the parent module "mailconnector". This is a limitation of the cargo plugin.

As mentioned in the document of mailconnector "connectors/mailconnector/docs/index.html", this sample project should be built, deployed, undeployed in these steps:
1. $ cd $WORKSPACE/glassfish4/samples/connectors
2. $ mvn clean install
3. $ cd mailconnector/mailconnector-ear
4. $ mvn cargo:install
5. Add 3rd party library mock-javamail.jar in GlassFish. which is a dummy mail server. Without this library, the sample can be deployed, but do not work.
6. $ mvn cargo:start -Dglassfish.home=$WORKSPACE/glassfish4
7. $ mvn antrun:run # this goal will add some user accounts in GlassFish File realm.
8. $ mvn cargo:deployer-undeploy
9. $ mvn cargo:stop clean

Comment by Alex Pineda [ 24/Apr/13 ]

Thanks for the information on how to run the sample. Request that you transfer the information to the sample documentation (index.html file) and provide the details on the 3rd party library mock-javamail.jar and how to use it for running the sample.

However, I wonder why you want to call cargo:install. My understanding is this command will install a container distribution. I normally use "cargo: start" with "-Dglassfish.home=<GF Install Directory>" as to use the container (or server) that I install from the SDK distribution.

Comment by dapeng_hu [ 24/Apr/13 ]

[1] In the sample document, there is sections which introduce the mock javamail library, along with how to use it.

[2] Yes, the cargo:install only download the GF distribution to local host. But this sample project depends on 3rd library mock-javamail. This library should be added manually to the directory glassfish4/glassfish/lib/ before GlassFish is starting up. That is why we inset the step 5 above between cargo:install and cargo:start. Other sample projects do not have this kind of runtime dependency. So they can directly run the goal cargo:start.

Comment by dapeng_hu [ 24/Apr/13 ]

The assumption behind the my instruction is that: you use the cargo plugin to download and manage GlassFish distribution.

If you download and manage GlassFish by yourself, of cause you can skip the step 4 cargo:install and go the step 5.

Comment by Alex Pineda [ 24/Apr/13 ]

Not sure I made my point clear, but I think we're saying the same thing. As part of testing the sample, I plan to copy the mock library to the GlassFish lib directory, then invoke cargo:start. This command starts the server, creates a cargo-domain and deploys the sample. By using the -Dglassfish.home option, it will use my local GF installation. Afterwards run cargo: undeploy stop clean.

I'm assuming you have already added the instructions to the sample documentation. Just got the official (for QA) build 85 SDK builds. I will give look for the update in the index.html file.

Comment by Alex Pineda [ 24/Apr/13 ]

Which Glassfish distribution to use is a point of debate. As a QA person, I believe we should have the use use what they get through the SDK distribution. This is the reason why we're testing the product sa to make sure the SDK contents are useable and working. Some like you, want the user to get the latest from our open source repository. I understand why, but this is an option that is not tested daily or continuously. Again, we have a difference in opinion. Our PM has the final word on this option.

Comment by dapeng_hu [ 24/Apr/13 ]

In the pom.xml of top-most parent project, there is property as follows:
<cargo.maven.containerUrl>http://javaweb.us.oracle.com/java/re/glassfish/4.0/promoted/b85/archive/bundles/latest-glassfish.zip</cargo.maven.containerUrl>

This is where cargo plugin will download the GF distribution. So far, this URL address point to the latest GF available. And the value of this property is updated for each new build. But I guess it finally will be a stable version after GF4.0 is officially published.

Moreover, this property is shared by all sample projects, other sample project also use cargo to download and manage GF by default (not only me _). I guess this is because the sample projects can be shipped standalone (perhaps will be here: https://java.net/projects/glassfish-samples/downloads). If users only download the samples without GlassFish, this will save their time to install GlassFish and quickly start to play with the samples.

By the way, to suppress the warning message as you mentioned, I will add version for maven-rar-plugin and maven-jar-plugin in the pom.xml of mailconnector-rar module.

Comment by dapeng_hu [ 24/Apr/13 ]
  • What is the impact on the customer of the bug?
    In the pom.xml of sample project mailconnector-rar, the version number of plugin maven-rar-plugin and maven-jar-plugin are not specified.
    Maven will print out warning messages as follows when it loads the pom.xml.

[WARNING] Some problems were encountered while building the effective model for org.glassfish-samples:mailconnector-ra:rar:4.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-rar-plugin is missing. @ line 86, column 17
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 71, column 17

This problem has no impact on CTS, security, performance, etc.

  • What CTS failures are caused by this bug?
    None
  • What is the cost/risk of fixing the bug?
    None
  • How risky is the fix? How much work is the fix? Is the fix complicated?
    The fix is quite straightforward: add version number for plugin maven-rar-plugin and maven-jar-plugin in pom.xml.
  • Is there an impact on documentation or message strings?
    None
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
    None
  • Which is the targeted build of 4.0 for this fix?
    b86
  • If this an integration of a new version of a component from another project, what are the changes that are being brought in?
    None
Comment by dapeng_hu [ 28/Apr/13 ]

Move plugin version definition to top level pom.xml

Comment by Alex Pineda [ 01/May/13 ]

I went the instructions as noted in this report and what came with sample. The steps worked as mentioned and documented, however, when I tried to build the javamail mock library, I got a build error. The exact steps that I followed are:

o [test@wolfrun] $ cd $TEST/glassfish4/samples/connectors
o [test@wolfrun] $ svn checkout https://svn.java.net/svn/mock-javamail~svn/trunk/mock-javamail
Checked out revision 92.

o [test@wolfrun] cd mock-javamail
o [test@wolfrun] mvn clean
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

o [test@wolfrun] $ mvn install
[WARNING] Some problems were encountered while building the effective model for org.jvnet.mock-javamail:mock-javamail:jar:1.12-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-idea-plugin is missing. @ line 71, column 15
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 64, column 15
[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 114, column 15
[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-jxr-plugin is missing. @ line 117, column 15
[WARNING] 'repositories.repository.layout' for java.net uses the unsupported value 'legacy', artifact resolution might fail. @ line 35, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JavaMail mock objects 1.12-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.716s
[INFO] Finished at: Tue Apr 30 17:07:38 PDT 2013
[INFO] Final Memory: 5M/149M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project mock-javamail: Could not resolve dependencies for project org.jvnet.mock-javamail:mock-javamail:jar:1.12-SNAPSHOT: Failed to collect dependencies for [javax.mail:mail:jar:1.4 (compile), junit:junit:jar:3.8 (compile)]: Failed to read artifact descriptor for javax.mail:mail:jar:1.4: Could not transfer artifact javax.mail:mail:pom:1.4 from/to internal-glassfish-nexus (http://gf-maven.us.oracle.com/nexus/content/groups/internal-gf-nexus/): No connector available to access repository internal-glassfish-nexus (http://gf-maven.us.oracle.com/nexus/content/groups/internal-gf-nexus/) of type legacy using the available factories WagonRepositoryConnectorFactory -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Comment by Alex Pineda [ 01/May/13 ]

Re-opening bug, although, I'm aware that this issue is not a product issue. Is more of missing instructions or configuration that is probably missing in the sample documentation.

Comment by dapeng_hu [ 01/May/13 ]

This is an issue of pom.xml of the project mock-javamail. The fix is as follows:

Index: pom.xml
===================================================================
— pom.xml (revision 92)
+++ pom.xml (working copy)
@@ -27,7 +27,7 @@
<archive>http://java.net/projects/mock-javamail/lists/users/archive</archive>
</mailingList>
</mailingLists>
-
+ <!--
<repositories>
<repository>
<id>java.net</id>
@@ -41,7 +41,7 @@
<layout>default</layout>
</repository>
</repositories>
-
+ -->
<distributionManagement>
<snapshotRepository>
<id>jvnet-nexus-snapshots</id>
@@ -86,7 +86,7 @@
</configuration>
</plugin>
</plugins>
-
+ <!--
<extensions>
<extension>
<groupId>org.jvnet.wagon-svn</groupId>
@@ -94,6 +94,7 @@
<version>1.6</version>
</extension>
</extensions>
+ -->
</build>

<dependencies>

I have created a new issue on JIRA to keep track of the issue: https://java.net/jira/browse/MOCK_JAVAMAIL-12

Comment by dapeng_hu [ 01/May/13 ]

The mock-javamial's issue will be tracked by another issue: https://java.net/jira/browse/MOCK_JAVAMAIL-12

Comment by michael.y.chen [ 01/May/13 ]

Does this mean the connector sample still fail to deploy / build?

The mock_javamail is a project no one is actively working on, I am pretty sure we won't get a fix for it in next week. We are 1 week from our last build, we either need to find another solution to work around the mock_javamail problem, remove usage of mock_javamail, or remove this connector sample. We can't ship the broken sample.

Comment by dapeng_hu [ 02/May/13 ]

That is an easy issue. I have found the fix for it. Please give me a chance to solve it.

Comment by dapeng_hu [ 03/May/13 ]

Because it involves a few tricks to build the mock-javamail project. The mock-javamail library is added in the connector sample project. So user and tester can directly deploy the library and do not have to download/build the mock-javamail project. The deployment instruction in the sample document has been updated too.

Comment by dapeng_hu [ 03/May/13 ]

Code change has been submitted.

Comment by Alex Pineda [ 14/May/13 ]

I was able to run the sample using the mock_javamail jar file that is now included in the SDK samples distribution. All the instructions work as documented, however, there's one small minor issue. The instructions says go to "samples_install_dir/javaee7/connectors", however, the correct directory is just "samples_install_dir/connectors". Would it possible to update the document in the next build. If it's too risky, then not a problem. I'm sure any intermediate or advance user will figure this out.

Re-opening the issue to see what can be done if anything.

Comment by Alex Pineda [ 14/May/13 ]

Request to see if the sample instructions can be updated to resolve an issue on the location of the sample. Not a major issue if the fix is too risky.

Comment by dapeng_hu [ 14/May/13 ]

Good catch, I am fixing it.

Comment by dapeng_hu [ 14/May/13 ]

The directory error in the sample document has been fixed.





[GLASSFISH-19747] Duplication of weld classes causes increase of distribution size by 3.5MB Created: 28/Feb/13  Updated: 12/Aug/13  Resolved: 09/May/13

Status: Closed
Project: glassfish
Component/s: cdi
Affects Version/s: 4.0_b78
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Major
Reporter: Sanjeeb Sahoo Assignee: phil.zampino
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved

 Description   

To support CDI in ACC, we are including weld-se.jar in distribution. Its size is 3.5MB - same as weld-osgi-bundle.jar. A quick analysis shows that the two jars mostly overlapping. See the attached files which list the jar contents as resource names. In fact, the se jar even repackages javax.annotation, javax.el, javax.interceptor inside it. I see no reason for them to be included like that in our product when we already have them in file system in separate places. The only extra set of classes are actually org.jboss.weld.environment.se and crucial META-INF/services files. Here is what we should strive for:
a) Just have all weld related classes in weld-osgi-bundle.jar and make it useable from ACC.
b) If this is not possible, then see the SE specific artifacts can be packaged in to a separate jar and used in conjunction with above jar.



 Comments   
Comment by phil.zampino [ 29/Apr/13 ]

Determining if weld-se-core.jar can be the resolution to this issue.

Comment by phil.zampino [ 09/May/13 ]

Committed revision 61908. Replaced weld-se.jar with weld-se-core.jar

Comment by Sanjeeb Sahoo [ 09/May/13 ]

If this fix was so simple, I am wondering why we didn't do it in 4.0 which is going to be downloaded by a lot of folks. It reduces the benefit of the fix.

Comment by phil.zampino [ 09/May/13 ]
  • What is the impact on the customer of the bug?
    Improved download experience; Reduces the distribution size by almost 3.5M
  • How likely is it that a customer will see the bug and how serious is the bug?
    Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
    What CTS failures are caused by this bug?

Every customer who downloads the distribution will "feel" the additional 3.5M, but there is no associated functional issue.

  • What is the cost/risk of fixing the bug?
    There is little to no risk associated with this change. The functionality is new for 4.0, and has already been in place for some time. This change merely modifies the dependencies to re-use existing copies in the distribution, rather than adding duplicates.

How risky is the fix? How much work is the fix? Is the fix complicated?

  • Is there an impact on documentation or message strings?

There is no doc or message impact.

  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

Quicklook, EJB devtests (these leverage the ACC, so they could be affected)

  • Which is the targeted build of 4.0 for this fix?

B89

  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.

This is not a new revision of the Weld dependencies, just a different packaging thereof.

Comment by michael.y.chen [ 09/May/13 ]

approved for B89.

Comment by phil.zampino [ 10/May/13 ]

Committed revision 61948 to 4.0 branch





[GLASSFISH-19456] The JMS RI throws XAException for one of the CDI bean use case test (beanUseCaseK) Created: 17/Dec/12  Updated: 02/Jul/13  Resolved: 02/Jul/13

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 4.0_b67_ms7
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Minor
Reporter: adf59 Assignee: David Zhao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The following tests fail in CTS JMS.

FAILED........com/sun/ts/tests/jms/ee20/cditests/usecases/Client.java#beanUseCaseK

Get the following exception.

[#|2012-12-16T22:17:13.153+0000|SEVERE|44.0|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233153;_LevelValue=1000;|startTransaction (XA) on JMSService:jmsdirect failed for connectionId:7157974240937103104 due to Unknown JMSService server error NOT_FOUND: com.sun.messaging.jmq.jmsserver.util.BrokerException: Unknown XID 616463363134303338302C7365727665722C50333639392C00F603000083E6A9A5616463363134303338302C7365727665722C5033363939|#]

[#|2012-12-16T22:17:13.153+0000|WARNING|44.0|javax.enterprise.system.core.transaction.com.sun.jts.jta|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233153;_LevelValue=900;_MessageID=jts.resource_outside_transaction;|JTS5041: The resource manager is doing work outside a global transaction
javax.transaction.xa.XAException
at com.sun.messaging.jms.ra.DirectXAResource.sendStartToBroker(DirectXAResource.java:853)
at com.sun.messaging.jms.ra.DirectXAResource.start(DirectXAResource.java:804)
at com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:320)
at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:212)
at com.sun.enterprise.transaction.JavaEETransactionImpl.enlistResource(JavaEETransactionImpl.java:660)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistXAResource(JavaEETransactionManagerSimplified.java:1277)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistResource(JavaEETransactionManagerSimplified.java:368)
at com.sun.enterprise.resource.rm.ResourceManagerImpl.registerResource(ResourceManagerImpl.java:152)
at com.sun.enterprise.resource.rm.ResourceManagerImpl.enlistResource(ResourceManagerImpl.java:112)
at com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:211)
at com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:337)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:306)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:207)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:170)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
at com.sun.messaging.jms.ra.DirectConnectionFactory._allocateConnection(DirectConnectionFactory.java:567)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createConnection(DirectConnectionFactory.java:260)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createConnection(DirectConnectionFactory.java:239)
at com.sun.messaging.jmq.jmsclient.JMSContextImpl.<init>(JMSContextImpl.java:204)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createContext(DirectConnectionFactory.java:285)
at org.glassfish.jms.injection.AbstractJMSContextManager.createContext(AbstractJMSContextManager.java:78)
at org.glassfish.jms.injection.AbstractJMSContextManager.getContext(AbstractJMSContextManager.java:93)
at org.glassfish.jms.injection.TransactedJMSContextManager$Proxy$$$_WeldClientProxy.getContext(TransactedJMSContextManager$Proxy$$$_WeldClientProxy.java)
at org.glassfish.jms.injection.InjectableJMSContext.toString(InjectableJMSContext.java:133)
at java.lang.String.valueOf(String.java:2902)
at java.lang.StringBuilder.append(StringBuilder.java:128)
at com.sun.ts.tests.jms.ee20.cditests.usecases.CMBean1.method6(CMBean1.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1035)
at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1107)
at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:4676)
at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:625)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:577)
at org.jboss.weld.ejb.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:49)
at sun.reflect.GeneratedMethodAccessor504.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:857)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:577)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doAround(SystemInterceptorProxy.java:162)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.aroundInvoke(SystemInterceptorProxy.java:144)
at sun.reflect.GeneratedMethodAccessor512.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:857)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:369)
at com.sun.ejb.containers.BaseContainer.__intercept(BaseContainer.java:4648)
at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4636)
at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:205)
at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:79)
at $Proxy393.method6(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:143)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:173)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatchToServant(ServerRequestDispatcherImpl.java:528)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatch(ServerRequestDispatcherImpl.java:199)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequestRequest(MessageMediatorImpl.java:1596)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:1458)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleInput(MessageMediatorImpl.java:966)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:718)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.dispatch(MessageMediatorImpl.java:515)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.doWork(MessageMediatorImpl.java:2291)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)
Caused by: com.sun.messaging.jmq.jmsservice.JMSServiceException: startTransaction: start transaction failed. Connection ID: 7157974240937103104, session ID: 0, XID: (Available at FINE log level)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQDirectService.startTransaction(IMQDirectService.java:1558)
at com.sun.messaging.jms.ra.DirectXAResource.sendStartToBroker(DirectXAResource.java:823)
... 73 more
Caused by: com.sun.messaging.jmq.jmsserver.util.BrokerException: Unknown XID 616463363134303338302C7365727665722C50333639392C00F603000083E6A9A5616463363134303338302C7365727665722C5033363939
at com.sun.messaging.jmq.jmsserver.data.protocol.ProtocolImpl.startTransaction(ProtocolImpl.java:686)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQDirectService.startTransaction(IMQDirectService.java:1547)
... 74 more

#]

[#|2012-12-16T22:17:13.162+0000|SEVERE|44.0|javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.rm|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233162;_LevelValue=1000;_MessageID=poolmgr.component_register_exception;|RAR5029:Unexpected exception while registering component
javax.transaction.SystemException
at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:224)
at com.sun.enterprise.transaction.JavaEETransactionImpl.enlistResource(JavaEETransactionImpl.java:660)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistXAResource(JavaEETransactionManagerSimplified.java:1277)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistResource(JavaEETransactionManagerSimplified.java:368)
at com.sun.enterprise.resource.rm.ResourceManagerImpl.registerResource(ResourceManagerImpl.java:152)
at com.sun.enterprise.resource.rm.ResourceManagerImpl.enlistResource(ResourceManagerImpl.java:112)
at com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:211)
at com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:337)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:306)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:207)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:170)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
at com.sun.messaging.jms.ra.DirectConnectionFactory._allocateConnection(DirectConnectionFactory.java:567)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createConnection(DirectConnectionFactory.java:260)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createConnection(DirectConnectionFactory.java:239)
at com.sun.messaging.jmq.jmsclient.JMSContextImpl.<init>(JMSContextImpl.java:204)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createContext(DirectConnectionFactory.java:285)
at org.glassfish.jms.injection.AbstractJMSContextManager.createContext(AbstractJMSContextManager.java:78)
at org.glassfish.jms.injection.AbstractJMSContextManager.getContext(AbstractJMSContextManager.java:93)
at org.glassfish.jms.injection.TransactedJMSContextManager$Proxy$$$_WeldClientProxy.getContext(TransactedJMSContextManager$Proxy$$$_WeldClientProxy.java)
at org.glassfish.jms.injection.InjectableJMSContext.toString(InjectableJMSContext.java:133)
at java.lang.String.valueOf(String.java:2902)
at java.lang.StringBuilder.append(StringBuilder.java:128)
at com.sun.ts.tests.jms.ee20.cditests.usecases.CMBean1.method6(CMBean1.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1035)
at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1107)
at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:4676)
at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:625)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:577)
at org.jboss.weld.ejb.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:49)
at sun.reflect.GeneratedMethodAccessor504.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:857)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:577)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doAround(SystemInterceptorProxy.java:162)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.aroundInvoke(SystemInterceptorProxy.java:144)
at sun.reflect.GeneratedMethodAccessor512.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:857)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:369)
at com.sun.ejb.containers.BaseContainer.__intercept(BaseContainer.java:4648)
at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4636)
at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:205)
at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:79)
at $Proxy393.method6(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:143)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:173)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatchToServant(ServerRequestDispatcherImpl.java:528)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatch(ServerRequestDispatcherImpl.java:199)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequestRequest(MessageMediatorImpl.java:1596)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:1458)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleInput(MessageMediatorImpl.java:966)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:718)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.dispatch(MessageMediatorImpl.java:515)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.doWork(MessageMediatorImpl.java:2291)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)

#]

[#|2012-12-16T22:17:13.162+0000|WARNING|44.0|javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.pool|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233162;_LevelValue=900;_MessageID=poolmgr.err_enlisting_res_in_getconn;|RAR7132: Unable to enlist the resource in transaction. Returned resource to pool. Pool name: [ jms/ConnectionFactory-Connection-Pool ]|#]

[#|2012-12-16T22:17:13.162+0000|WARNING|44.0|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233162;_LevelValue=900;_MessageID=poolmgr.get_connection_failure;|RAR5117 : Failed to obtain/create connection from connection pool [ jms/ConnectionFactory-Connection-Pool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: javax.transaction.SystemException
com.sun.appserv.connectors.internal.api.PoolingException: javax.transaction.SystemException
at com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:221)
at com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:337)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:306)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:207)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:170)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
at com.sun.messaging.jms.ra.DirectConnectionFactory._allocateConnection(DirectConnectionFactory.java:567)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createConnection(DirectConnectionFactory.java:260)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createConnection(DirectConnectionFactory.java:239)
at com.sun.messaging.jmq.jmsclient.JMSContextImpl.<init>(JMSContextImpl.java:204)
at com.sun.messaging.jms.ra.DirectConnectionFactory.createContext(DirectConnectionFactory.java:285)
at org.glassfish.jms.injection.AbstractJMSContextManager.createContext(AbstractJMSContextManager.java:78)
at org.glassfish.jms.injection.AbstractJMSContextManager.getContext(AbstractJMSContextManager.java:93)
at org.glassfish.jms.injection.TransactedJMSContextManager$Proxy$$$_WeldClientProxy.getContext(TransactedJMSContextManager$Proxy$$$_WeldClientProxy.java)
at org.glassfish.jms.injection.InjectableJMSContext.toString(InjectableJMSContext.java:133)
at java.lang.String.valueOf(String.java:2902)
at java.lang.StringBuilder.append(StringBuilder.java:128)
at com.sun.ts.tests.jms.ee20.cditests.usecases.CMBean1.method6(CMBean1.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1035)
at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1107)
at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:4676)
at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:625)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:577)
at org.jboss.weld.ejb.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:49)
at sun.reflect.GeneratedMethodAccessor504.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:857)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:577)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doAround(SystemInterceptorProxy.java:162)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.aroundInvoke(SystemInterceptorProxy.java:144)
at sun.reflect.GeneratedMethodAccessor512.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:857)
at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:796)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:369)
at com.sun.ejb.containers.BaseContainer.__intercept(BaseContainer.java:4648)
at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4636)
at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:205)
at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:79)
at $Proxy393.method6(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:143)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:173)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatchToServant(ServerRequestDispatcherImpl.java:528)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatch(ServerRequestDispatcherImpl.java:199)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequestRequest(MessageMediatorImpl.java:1596)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:1458)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleInput(MessageMediatorImpl.java:966)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:718)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.dispatch(MessageMediatorImpl.java:515)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.doWork(MessageMediatorImpl.java:2291)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)
Caused by: com.sun.appserv.connectors.internal.api.PoolingException: javax.transaction.SystemException
at com.sun.enterprise.resource.rm.ResourceManagerImpl.registerResource(ResourceManagerImpl.java:173)
at com.sun.enterprise.resource.rm.ResourceManagerImpl.enlistResource(ResourceManagerImpl.java:112)
at com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:211)
... 64 more
Caused by: javax.transaction.SystemException
at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:224)
at com.sun.enterprise.transaction.JavaEETransactionImpl.enlistResource(JavaEETransactionImpl.java:660)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistXAResource(JavaEETransactionManagerSimplified.java:1277)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistResource(JavaEETransactionManagerSimplified.java:368)
at com.sun.enterprise.resource.rm.ResourceManagerImpl.registerResource(ResourceManagerImpl.java:152)
... 66 more

#]

[#|2012-12-16T22:17:13.163+0000|WARNING|44.0|javax.enterprise.system.core.transaction.com.sun.jts.jtsxa|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233163;_LevelValue=900;_MessageID=jts.unexpected_error_occurred_twopc_rollback;|JTS5068: Unexpected error occurred in rollback
java.lang.IllegalStateException: Wrong XAState: -1
at com.sun.jts.jta.TransactionState._rollback(TransactionState.java:222)
at com.sun.jts.jta.TransactionState.rollback(TransactionState.java:180)
at com.sun.jts.jtsxa.OTSResourceImpl.rollback(OTSResourceImpl.java:333)
at com.sun.jts.CosTransactions.RegisteredResources.distributeRollback(RegisteredResources.java:1040)
at com.sun.jts.CosTransactions.TopCoordinator.rollback(TopCoordinator.java:2291)
at com.sun.jts.CosTransactions.CoordinatorTerm.rollback(CoordinatorTerm.java:530)
at com.sun.jts.CosTransactions.TerminatorImpl.rollback(TerminatorImpl.java:286)
at com.sun.jts.CosTransactions.CurrentImpl.rollback(CurrentImpl.java:767)
at com.sun.jts.jta.TransactionManagerImpl.rollback(TransactionManagerImpl.java:372)
at com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate.rollbackDistributedTransaction(JavaEETransactionManagerJTSDelegate.java:218)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.rollback(JavaEETransactionManagerSimplified.java:862)
at com.sun.ejb.containers.EJBContainerTransactionManager.destroyBeanAndRollback(EJBContainerTransactionManager.java:574)
at com.sun.ejb.containers.EJBContainerTransactionManager.completeNewTx(EJBContainerTransactionManager.java:697)
at com.sun.ejb.containers.EJBContainerTransactionManager.postInvokeTx(EJBContainerTransactionManager.java:503)
at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4456)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1991)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1961)
at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:212)
at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:79)
at $Proxy393.method6(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:143)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:173)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatchToServant(ServerRequestDispatcherImpl.java:528)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatch(ServerRequestDispatcherImpl.java:199)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequestRequest(MessageMediatorImpl.java:1596)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:1458)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleInput(MessageMediatorImpl.java:966)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:718)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.dispatch(MessageMediatorImpl.java:515)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.doWork(MessageMediatorImpl.java:2291)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)

#]

[#|2012-12-16T22:17:13.164+0000|SEVERE|44.0|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233164;_LevelValue=1000;|JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed: Maybe] on Resource [rollback] operation.|#]

[#|2012-12-16T22:17:13.165+0000|WARNING|44.0|javax.enterprise.system.container.ejb.com.sun.ejb.containers|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233165;_LevelValue=900;_MessageID=ejb.system_exception;|EJB5184:A system exception occurred during an invocation on EJB CDIUseCasesCMBEAN1, method: public void com.sun.ts.tests.jms.ee20.cditests.usecases.CMBean1.method6()|#]

[#|2012-12-16T22:17:13.165+0000|WARNING|44.0|javax.enterprise.system.container.ejb.com.sun.ejb.containers|_ThreadID=443;_ThreadName=p: thread-pool-1; w: 8;_TimeMillis=1355696233165;_LevelValue=900;|javax.ejb.EJBException: javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed: Maybe] on Resource [rollback] operation. vmcid: 0x0 minor code: 0 completed: No
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1998)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1961)
at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:212)
at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:79)
at $Proxy393.method6(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:143)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:173)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatchToServant(ServerRequestDispatcherImpl.java:528)
at com.sun.corba.ee.impl.protocol.ServerRequestDispatcherImpl.dispatch(ServerRequestDispatcherImpl.java:199)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequestRequest(MessageMediatorImpl.java:1596)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:1458)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleInput(MessageMediatorImpl.java:966)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.handleRequest(MessageMediatorImpl.java:718)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.dispatch(MessageMediatorImpl.java:515)
at com.sun.corba.ee.impl.protocol.MessageMediatorImpl.doWork(MessageMediatorImpl.java:2291)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)
Caused by: javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed: Maybe] on Resource [rollback] operation. vmcid: 0x0 minor code: 0 completed: No
at com.sun.jts.jta.TransactionManagerImpl.rollback(TransactionManagerImpl.java:378)
at com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate.rollbackDistributedTransaction(JavaEETransactionManagerJTSDelegate.java:218)
at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.rollback(JavaEETransactionManagerSimplified.java:862)
at com.sun.ejb.containers.EJBContainerTransactionManager.destroyBeanAndRollback(EJBContainerTransactionManager.java:574)
at com.sun.ejb.containers.EJBContainerTransactionManager.completeNewTx(EJBContainerTransactionManager.java:697)
at com.sun.ejb.containers.EJBContainerTransactionManager.postInvokeTx(EJBContainerTransactionManager.java:503)
at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4456)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1991)
... 21 more



 Comments   
Comment by David Zhao [ 02/Jul/13 ]

I cannot reproduce it at my local environment.

This transaction related issue might be fixed too by GLASSFISH-19872 and GLASSFISH-19769.

Please feel free to reopen it if you can still reproduce it with latest glassfish release.





[GLASSFISH-19352] An empty string ("") can be set for clientID Created: 16/Nov/12  Updated: 01/Jul/13  Resolved: 01/Jul/13

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 4.0_b45
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Trivial
Reporter: tak09 Assignee: David Zhao
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Glassfish v4.0 b45
Windows 7


Attachments: PNG File clientid.png     Zip Archive setClientID.zip    

 Description   

An empty string ("") can be used when setting a clientID using GUI or setClientID() method.

1. Set ("") in the Resources > JMS Resources > Connection Factories > Connection Factory Name Additional Properties. If you click Save, it is saved successfully. (Bug) Please see the attachment file.

2. When "" is used for setting clientID, it is compiled and executed without an error. (Bug) See the attachment file for the use of setClientID("\"\"").

3. When asadmin is used for setting an empty string ("") in clientID, this operation fails. (Working as expected. Not a bug)

C:\GFFeedback\3043ClientID\TP\setClientID\run>C:\glassfish\glassfish-4.0-b45\glassfish3\glassfish\bi
n\asadmin create-jms-resource --restype javax.jms.ConnectionFactory --property ClientID=^"^\^"^\^"^"
 jms/ConnectionFactory001
remote failure: Unable to create connection pool.
Invalid property syntax, missing property value: ClientID=
Command create-jms-resource failed.

^ is an escape sequence character in MS-DOS.



 Comments   
Comment by David Zhao [ 01/Jul/13 ]

In the admin gui, the value is escaped by default. So if you input "" for ClientID property, then the value stored in domain.xml will be "" with no change. If you want to test empty string for the property, you should leave the value field blank and then click Save button, thus the property will not be saved, which is expected.





[GLASSFISH-19340] [PERF] NullPointerException in StatefulSessionContainer.forceDestroyBean Created: 13/Nov/12  Updated: 16/May/13  Resolved: 16/May/13

Status: Closed
Project: glassfish
Component/s: ejb_container
Affects Version/s: 4.0_b62_ms6
Fix Version/s: 4.0_b89_RC5

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

Tags: PSRBUG

 Description   

Under load tests, calls to remove a stateful session bean sometimes throw this exception:

java.lang.NullPointerException
	at com.sun.ejb.containers.StatefulSessionContainer.forceDestroyBean(StatefulSessionContainer.java:1215)
	at com.sun.ejb.containers.StatefulSessionContainer.releaseContext(StatefulSessionContainer.java:1779)
	at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:2004)
	at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1964)
	at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:220)
	at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:88)
	at $Proxy151.remove(Unknown Source)
	at com.oracle.psr.PingServlet.doLocalSFSB(PingServlet.java:195)
	at com.oracle.psr.PingServlet.processRequest(PingServlet.java:93)
	at com.oracle.psr.PingServlet.doGet(PingServlet.java:151)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)

I suspect this means that the app may be using the same stateful session bean in two threads at the same time, which means that the lookup of the bean returned the same bean to two different sessions. The basic servlet code is essentially this:

public void doGet(...) {
    InitialContext ic = new InitialContext();
    MyBean sfsb = ic.lookup(...);
    sfsb.cancel();   // cancel is annotated with @Remove
}

[Yes, we're not storing the sfsb for the session; it's a load test to look at the performance of the lookup and remove.]



 Comments   
Comment by marina vatkina [ 27/Mar/13 ]

Scott, can you rerun the test on the latest GF build? There had been a lot of changes and the line numbers don't match now.

Comment by marina vatkina [ 15/May/13 ]

Assigning back to Scott to verify on the latest build

Comment by Scott Oaks [ 16/May/13 ]

Fixed in latest builds.





[GLASSFISH-19260] Java EE 7 RI Source Bundle Created: 30/Oct/12  Updated: 08/Aug/13  Resolved: 08/Aug/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b60
Fix Version/s: 4.0_b89_RC5

Type: New Feature Priority: Major
Reporter: Joe Di Pol Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-19589 Java EE 7 RI Build binary Resolved

 Description   

The RI binaries delivered to licensees must be built from source to ensure consistency between the binaries and source, and as a result the source should be easily buildable by licensees so they can build the binaries themselves.

Detailed requirements for this are still being worked out and will be specified in the internal wiki page:

http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Java+EE+7+RI+Source+Build



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 01/Nov/12 ]

Setting targeted fix to MS7 (hard code freeze) but initial RI build implementation will be made available by MS4 (b72).





[GLASSFISH-16608] com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/myQueue@java Created: 11/May/11  Updated: 03/Jul/13  Resolved: 03/Jul/13

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 3.1_b43
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Minor
Reporter: crytal123 Assignee: David Zhao
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

JDK1.6.0_25, GF3.1 (build 43), Netbeans 7.0 on Windows XP & 7 (Intel platform)


Attachments: Text File JMSEnterpriseProject AC Error.log     Microsoft Word JMSEnterpriseProject Server log Error.doc     File JMSEnterpriseProject.rar     Text File server.log    

 Description   

java.lang.NullPointerException resulted when declaring JMS resource name by looking up logical name (@Resource(name = "jms/myQueue" and @Resource(name = "jms/myQueueConnectionFactory") instead of directly referencing its Physical JNDI name (@Resource(mappedName = "jms/myQueue" and @Resource(mappedName = "jms/myQueueConnectionFactory")



 Comments   
Comment by David Zhao [ 03/Jul/13 ]

The logical name should in java:comp, java:module, java:app, java:global namespaces. Please don't use vendor specific physical jndi name here.

The name of the resource, which is defined by the name element or defaulted, is a name that is local to the application component using the resource. (By default the name will be in the JNDI java:comp/env namespace).

For example, if name doesn't have namespace,

@Resource(name="jms/myQueue")

then it equals to:

@Resource(name="java:comp/env/jms/myQueue")





Generated at Fri Mar 06 20:58:44 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.