<< Back to previous view

[GLASSFISH-19271] Timer <method-intf> support is not implemented Created: 01/Nov/12  Updated: 01/Nov/12  Resolved: 01/Nov/12

Status: Resolved
Project: glassfish
Component/s: None
Affects Version/s: 4.0_b60
Fix Version/s: 4.0_b61

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

Tags:
Participants: marina vatkina

 Description   

Tested by replacing in DD ejb31/timer31/nonpersistenttimer

<container-transaction>
<method>
<ejb-name>FooEJB_CMT</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>

with

<container-transaction>
<method>
<ejb-name>FooEJB_CMT</ejb-name>
<method-intf>Timer</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>

And checking transaction status in the ejbTimeout method - it's active



 Comments   
Comment by marina vatkina [ 01/Nov/12 05:59 PM ]

Fixed with rev 56835. This is just the basic support.





[GLASSFISH-19255]  Error in formatting Logrecord in jpa tests Created: 29/Oct/12  Updated: 02/Nov/12  Resolved: 31/Oct/12

Status: Resolved
Project: glassfish
Component/s: entity-persistence
Affects Version/s: 4.0_b60
Fix Version/s: 4.0_b61

Type: Bug Priority: Critical
Reporter: sherryshen Assignee: sandeep.shrivastava
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHL 5.0 and JDK1.7.0_03


Tags: 40-regression
Participants: sandeep.shrivastava and sherryshen

 Description   

glassfish-4.0-b61-10_28_2012.zip

During the failure analysis of other jpa issue, I
noticed that some jpa tests passed with log exception on das so
that some part of FINE log is not shown, e.g.

appserver-sqe/pe/ejb/jpa20/ear/bvauto
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-das-dbg/134/console
[echo] - JPA2-BVAuto-EAR-J2DB:persistWithLongName: PASS -
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-das-dbg/134/artifact/server.log
EclipseLink, version: Eclipse Persistence Services - 2.5.0.v20121016-ab08992
....
[#|2012-10-29T11:09:53.293-0700|SEVERE|44.0|javax.enterprise.logging.stderr|
_ThreadID=93;_ThreadName=p: thread-pool-1; w: 5;_TimeMillis=1351534193293;
_LevelValue=1000;|java.util.logging.ErrorManager:
5: Error in formatting Logrecord|#]

[#|2012-10-29T11:09:53.295-0700|SEVERE|44.0|javax.enterprise.logging.stderr|
_ThreadID=93;_ThreadName=p: thread-pool-1; w: 5;
_TimeMillis=1351534193295;_LevelValue=1000;|
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:432)
at
com.sun.enterprise.server.logging.UniformLogFormatter.uniformLogFormat(UniformLogFormatter.java:311)
at
com.sun.enterprise.server.logging.UniformLogFormatter.format(UniformLogFormatter.java:160)
at java.util.logging.StreamHandler.publish(StreamHandler.java:196)
at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:105)
at java.util.logging.Logger.log(Logger.java:522)
at
org.eclipse.persistence.logging.JavaLog.internalLog(JavaLog.java:290)

This error is not shown on glassfish-4.0-b60.zip, while FINE log is shown
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-das-dbg/135/artifact/server.log
EclipseLink, version: Eclipse Persistence Services - 2.5.0.v20121016-ab08992
.....
[#|2012-10-29T12:10:47.843-0700|FINE|44.0|org.eclipse.persistence.session.file:
/export/hudson/workspace/sherry-das-dbg/glassfish3/glassfish/domains/domain1/
applications/jpa20-bvautoApp/lib/entity.jar_pu1.sql|
ThreadID=88;_ThreadName=p: thread-pool-1; w: 5;
TimeMillis=1351537847843;_LevelValue=500;ClassName=null;MethodName=null;|
INSERT INTO BV_EMPL (ID, NAME, SALARY) VALUES (?, ?, ?)
bind => [3 parameters bound]|#]



 Comments   
Comment by sherryshen [ 29/Oct/12 08:35 PM ]

Raised to P2 since bvauto suite is hanging during cluster run.

The deploy went through, but it failed to insert entity
http://sqe-hudson.us.oracle.com:8080/hudson/job/sherry-lc-np/89/
[exec] asadmin --host localhost --port 4848 --user admin --passwordfile /export/hudson/workspace/sherry-lc-np/appserver-sqe/build-config/adminpassword.txt
--interactive=false --echo=true --terse=false deploy --force=false --precompilejsp=false --verify=false
--retrieve /export/hudson/workspace/sherry-lc-np/appserver-sqe/build/ee/amd64_apg-sqe1_Linux/jpa20-bvauto/archive
--generatermistubs=false --availabilityenabled=false --asyncreplication=true --target sqe-cluster --keepreposdir=false --keepfailedstubs=false
--isredeploy=false --logreportederrors=true --_classicstyle=false
/export/hudson/workspace/sherry-lc-np/appserver-sqe/build/ee/amd64_apg-sqe1_Linux/jpa20-bvauto/archive/jpa20-bvautoApp.ear
[exec] Application deployed with name jpa20-bvautoApp.
[exec] Command deploy executed successfully.

[echo] Executing appclient at /export/hudson/workspace/sherry-lc-np/appserver-sqe/pe/ejb/jpa20/ear/bvauto
..... hanging

The similar log error is shown in server.log.
http://javaweb.us.oracle.com/net/asqe-logs/export1/4.0/Results/build60/core/b19225/lc/server_in2.log

Comment by sherryshen [ 29/Oct/12 09:09 PM ]

To run jpa tests, please see instruction section 5.
http://aseng-wiki.us.oracle.com/asengwiki/display/ASQA/4.0+Core+Test+Instructions

To run bvauto suite only, do "ant all" for das or
"ant ee all" for cluster in test dir.
Please see my hudson configure as example.
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-das-dbg/
http://sqe-hudson.us.oracle.com:8080/hudson/view/Sherry_core/job/sherry-lc-np/

Comment by sandeep.shrivastava [ 31/Oct/12 02:21 PM ]

This should be fixed with revision 56805.

Comment by sherryshen [ 02/Nov/12 10:59 PM ]

Verified the fix on glassfish-4.0-b61.zip.
EclipsLink FINE log is shown in das run.
Test is not hanging on cluster run.
Thanks Sandeep for the prompt fix and support.





[GLASSFISH-19253] Suppport --runtimealtdd for glassfish-web.xml Created: 26/Oct/12  Updated: 29/Oct/12  Resolved: 29/Oct/12

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

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

Tags:
Participants: Shing Wai Chan

 Description   

Need to enhance pre-parsing logic of glassfish-web.xml for --runtimealtdd.



 Comments   
Comment by Shing Wai Chan [ 29/Oct/12 10:43 PM ]

Sending src/main/java/com/sun/enterprise/glassfish/web/WarHandler.java
Transmitting file data .
Committed revision 56786.





[GLASSFISH-19233] Failure while deploying webservices on embedded glassfish Created: 25/Oct/12  Updated: 26/Oct/12  Resolved: 26/Oct/12

Status: Resolved
Project: glassfish
Component/s: embedded
Affects Version/s: None
Fix Version/s: 4.0_b61

Type: Bug Priority: Critical
Reporter: sakshi.jain Assignee: Bhavanishankar
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

File Attachments: Java Source File egf.java     File webservice.war    
Tags:
Participants: Bhavanishankar and sakshi.jain

 Description   

When a war of a webservices application is deployed using embedded glassfish it fails with the following error:
Running org.glassfish.tests.ejbwar.WebTest
java.io.FileNotFoundException: http://localhost:8080/webservice/SimpleWebServiceService?wsdl
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)
at org.glassfish.tests.ejbwar.WebTest.goGet(WebTest.java:80)
at org.glassfish.tests.ejbwar.WebTest.testWeb(WebTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)



 Comments   
Comment by Bhavanishankar [ 26/Oct/12 09:53 AM ]

Change details :

http://java.net/projects/glassfish/lists/commits/archive/2012-10/message/457

Comment by Bhavanishankar [ 26/Oct/12 09:59 AM ]

This is the check-in (by mtuabe@java.net) that has caused this issue:

http://java.net/projects/glassfish/lists/commits/archive/2012-06/message/10

(keeping this comment for future reference)





[GLASSFISH-19195] [PERF] Improve handling of header encoding (tracking bug) Created: 19/Oct/12  Updated: 21/Dec/12  Resolved: 21/Dec/12

Status: Resolved
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0_b57
Fix Version/s: 4.0_b61

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

Tags: PSRBUG
Participants: Ryan Lubke and Scott Oaks

 Description   

Tracking bug for GRIZZLY-1354.



 Comments   
Comment by Ryan Lubke [ 29/Oct/12 10:44 PM ]

Issue resolved on Grizzly side. Waiting for confirmation on an additional fix upon which we'll release and integrate.

Comment by Ryan Lubke [ 21/Dec/12 11:30 PM ]

Grizzly 2.3-beta 8 was released on Oct 31 which contains the fix.





[GLASSFISH-19161] Webapp with application scoped resources fails to startup when node is restarted Created: 16/Oct/12  Updated: 26/Oct/12  Resolved: 26/Oct/12

Status: Closed
Project: glassfish
Component/s: deployment
Affects Version/s: 3.1.2
Fix Version/s: 4.0_b61

Type: Bug Priority: Critical
Reporter: craigday Assignee: naman_mehta
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux lwlserver 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux, GlassFish Server Open Source Edition 3.1.2.2 (build 5), JRE version 1.7.0_04


File Attachments: File testcase.tar     File testcase.tar    
Tags:
Participants: craigday, Hong Zhang, Jagadish and naman_mehta

 Description   

Steps to reproduce:

----------------------------------------
STEP 1: Create and start a new local instance:
----------------------------------------

apps@lwlserver:~$ asadmin create-local-instance testcase
Rendezvoused with DAS on localhost:4848.
Using DAS host localhost and port 4848 from existing das.properties for node
localhost-domain1. To use a different DAS, create a new node using create-node-ssh or
create-node-config. Create the instance with the new node and correct
host and port:
asadmin --host das_host --port das_port create-local-instance --node node_name instance_name.
Port Assignments for server instance testcase:
JMX_SYSTEM_CONNECTOR_PORT=28692
JMS_PROVIDER_PORT=27682
HTTP_LISTENER_PORT=28086
ASADMIN_LISTENER_PORT=24854
JAVA_DEBUGGER_PORT=29015
IIOP_SSL_LISTENER_PORT=23826
IIOP_LISTENER_PORT=23706
OSGI_SHELL_TELNET_PORT=26672
HTTP_SSL_LISTENER_PORT=28187
IIOP_SSL_MUTUALAUTH_PORT=23926
Command create-local-instance executed successfully.

apps@lwlserver:~$ asadmin start-instance testcase
Waiting for testcase to start ......
Successfully started the instance: testcase
instance Location: /home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase
Log File: /home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/logs/server.log
Admin Port: 24854
Command start-local-instance executed successfully.
The instance, testcase, was started on host localhost
Command start-instance executed successfully.

----------------------------------------
STEP 2: Deploy the attached testcase:
----------------------------------------

apps@lwlserver:~$ asadmin deploy --target testcase testcase.war
Application deployed with name testcase.
Command deploy executed successfully.

----------------------------------------
STEP 3: Observe server.log for successful deploy:
----------------------------------------

Oct 16, 2012 2:25:02 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
-XX:+UnlockDiagnosticVMOptions
-XX:PermSize=64m
-XX:MaxPermSize=192m
-XX:NewRatio=2
-Xmx512m
-javaagent:/home/apps/glassfish3122/glassfish/lib/monitor/flashlight-agent.jar
-server
-Dosgi.shell.telnet.maxconn=1
-Dfelix.fileinstall.disableConfigSave=false
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Dfelix.fileinstall.dir=/home/apps/glassfish3122/glassfish/modules/autostart/
-Djavax.net.ssl.keyStore=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/keystore.jks
-Dosgi.shell.telnet.port=26672
-Djava.security.policy=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/server.policy
-Djava.awt.headless=true
-Dfelix.fileinstall.log.level=3
-Dfelix.fileinstall.poll=5000
-Dcom.sun.aas.instanceRoot=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase
-Dosgi.shell.telnet.ip=127.0.0.1
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Djava.endorsed.dirs=/home/apps/glassfish3122/glassfish/modules/endorsed:/home/apps/glassfish3122/glassfish/lib/endorsed
-Dcom.sun.aas.installRoot=/home/apps/glassfish3122/glassfish
-Dfelix.fileinstall.bundles.startTransient=true
-Djava.ext.dirs=/home/apps/jdk1.7.0_04/lib/ext:/home/apps/jdk1.7.0_04/jre/lib/ext:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/lib/ext
-Dfelix.fileinstall.bundles.new.start=true
-Djavax.net.ssl.trustStore=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/cacerts.jks
-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
-Djava.security.auth.login.config=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/login.conf
-DANTLR_USE_DIRECT_CLASS_LOADING=true
Dgosh.args=-noshutdown -c noop=true
Oct 16, 2012 2:25:02 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 3 msec.
[#|2012-10-16T14:25:05.002+0800|INFO|glassfish3.1.2|com.sun.enterprise.server.logging.GFFileHandler|_ThreadID=1;_ThreadName=Thread-2;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2.2 (build 5)|#]

[#|2012-10-16T14:25:05.172+0800|INFO|glassfish3.1.2|org.glassfish.ha.store.spi.BackingStoreFactoryRegistry|_ThreadID=1;_ThreadName=Thread-2;|Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry|#]

[#|2012-10-16T14:25:05.560+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=1;_ThreadName=Thread-2;|JTS5014: Recoverable JTS instance, serverId = [100]|#]

[#|2012-10-16T14:25:05.853+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=23;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 18ms - bound to [0.0.0.0:28187]|#]

[#|2012-10-16T14:25:05.853+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=20;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 45ms - bound to [0.0.0.0:28086]|#]

[#|2012-10-16T14:25:05.890+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=27;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 4ms - bound to [0.0.0.0:24854]|#]

[#|2012-10-16T14:25:05.915+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=35;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 10ms - bound to [0.0.0.0:27682]|#]

[#|2012-10-16T14:25:06.299+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [http-listener-1] on host/port [0.0.0.0:28086]|#]

[#|2012-10-16T14:25:06.313+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [http-listener-2] on host/port [0.0.0.0:28187]|#]

[#|2012-10-16T14:25:06.324+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [admin-listener] on host/port [0.0.0.0:24854]|#]

[#|2012-10-16T14:25:06.390+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0171: Created virtual server [server]|#]

[#|2012-10-16T14:25:06.396+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0171: Created virtual server [__asadmin]|#]

[#|2012-10-16T14:25:06.836+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0172: Virtual server [server] loaded default web module []|#]

[#|2012-10-16T14:25:07.844+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=1;_ThreadName=Thread-2;|core.start_container_done|#]

[#|2012-10-16T14:25:07.928+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-2;|GlassFish Server Open Source Edition 3.1.2.2 (5) startup time : Felix (2,434ms), startup services(3,246ms), total(5,680ms)|#]

[#|2012-10-16T14:25:08.167+0800|INFO|glassfish3.1.2|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.inbound|_ThreadID=44;_ThreadName=Thread-2;|Recovery of Inbound Transactions started.|#]

[#|2012-10-16T14:25:08.177+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=44;_ThreadName=Thread-2;|JTS5014: Recoverable JTS instance, serverId = [100]|#]

[#|2012-10-16T14:25:08.936+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=12;_ThreadName=Thread-2;|/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/autodeploy/bundles does not exist, please create it.|#]

[#|2012-10-16T14:25:09.077+0800|INFO|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=48;_ThreadName=Thread-2;|JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://lwlserver:28692/jndi/rmi://lwlserver:28692/jmxrmi|#]

[#|2012-10-16T14:27:14.283+0800|INFO|glassfish3.1.2|org.hibernate.validator.internal.util.Version|_ThreadID=28;_ThreadName=Thread-2;|HV000001: Hibernate Validator 4.3.0.Final|#]

[#|2012-10-16T14:27:14.454+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=28;_ThreadName=Thread-2;|SEC1002: Security Manager is OFF.|#]

[#|2012-10-16T14:27:14.477+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=28;_ThreadName=Thread-2;|SEC1010: Entering Security Startup Service|#]

[#|2012-10-16T14:27:14.481+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=28;_ThreadName=Thread-2;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2012-10-16T14:27:14.523+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=28;_ThreadName=Thread-2;|SEC1115: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2012-10-16T14:27:14.524+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=28;_ThreadName=Thread-2;|SEC1115: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2012-10-16T14:27:14.533+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=28;_ThreadName=Thread-2;|SEC1115: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.|#]

[#|2012-10-16T14:27:14.545+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=28;_ThreadName=Thread-2;|SEC1011: Security Service(s) Started Successfully|#]

[#|2012-10-16T14:27:16.091+0800|INFO|glassfish3.1.2|org.eclipse.persistence.session.file:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/applications/testcase/WEB-INF/classes/_testcase|_ThreadID=28;_ThreadName=Thread-2;|EclipseLink, version: Eclipse Persistence Services - 2.3.2.v20111125-r10461|#]

[#|2012-10-16T14:27:24.273+0800|INFO|glassfish3.1.2|org.eclipse.persistence.session.file:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/applications/testcase/WEB-INF/classes/_testcase|_ThreadID=28;_ThreadName=Thread-2;|file:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/applications/testcase/WEB-INF/classes/_testcase login successful|#]

[#|2012-10-16T14:27:24.274+0800|WARNING|glassfish3.1.2|org.eclipse.persistence.session.file:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/applications/testcase/WEB-INF/classes/_testcase.server|_ThreadID=28;_ThreadName=Thread-2;|Multiple [2] JMX MBeanServer instances exist, we will use the server at index [0] : [com.sun.jmx.mbeanserver.JmxMBeanServer@43a6a5f9].|#]

[#|2012-10-16T14:27:24.274+0800|WARNING|glassfish3.1.2|org.eclipse.persistence.session.file:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/applications/testcase/WEB-INF/classes/_testcase.server|_ThreadID=28;_ThreadName=Thread-2;|JMX MBeanServer in use: [com.sun.jmx.mbeanserver.JmxMBeanServer@43a6a5f9] from index [0] |#]

[#|2012-10-16T14:27:24.275+0800|WARNING|glassfish3.1.2|org.eclipse.persistence.session.file:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/applications/testcase/WEB-INF/classes/_testcase.server|_ThreadID=28;_ThreadName=Thread-2;|JMX MBeanServer in use: [com.sun.jmx.mbeanserver.JmxMBeanServer@50d2ffa8] from index [1] |#]

[#|2012-10-16T14:27:24.295+0800|WARNING|glassfish3.1.2|org.eclipse.persistence.default|_ThreadID=28;_ThreadName=Thread-2;|The collection of metamodel types is empty. Model classes may not have been found during entity search for Java SE and some Java EE container managed persistence units. Please verify that your entity classes are referenced in persistence.xml using either <class> elements or a global <exclude-unlisted-classes>false</exclude-unlisted-classes> element|#]

[#|2012-10-16T14:27:24.393+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=28;_ThreadName=Thread-2;|WEB0671: Loading application [testcase] at [/testcase]|#]

[#|2012-10-16T14:27:24.520+0800|INFO|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=28;_ThreadName=Thread-2;|testcase was successfully deployed in 10,310 milliseconds.|#]

----------------------------------------
STEP 4: Restart instance:
----------------------------------------

apps@lwlserver:~$ asadmin restart-instance testcase
testcase was restarted.
Command restart-instance executed successfully.
apps@lwlserver:~$

----------------------------------------
STEP 5: Observe server.log for failed startup:
----------------------------------------

[#|2012-10-16T14:27:49.989+0800|INFO|glassfish3.1.2|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=96;_ThreadName=Thread-2;|Server restart initiated|#]

[#|2012-10-16T14:27:49.997+0800|WARNING|glassfish3.1.2|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=96;_ThreadName=Thread-2;|There should be only 1 primordial module but 0 primordial modules were found.|#]

Oct 16, 2012 2:27:51 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
-XX:+UnlockDiagnosticVMOptions
-XX:PermSize=64m
-XX:MaxPermSize=192m
-XX:NewRatio=2
-Xmx512m
-javaagent:/home/apps/glassfish3122/glassfish/lib/monitor/flashlight-agent.jar
-server
-Dosgi.shell.telnet.maxconn=1
-Dfelix.fileinstall.disableConfigSave=false
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Dfelix.fileinstall.dir=/home/apps/glassfish3122/glassfish/modules/autostart/
-Djavax.net.ssl.keyStore=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/keystore.jks
-Dosgi.shell.telnet.port=26672
-Djava.security.policy=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/server.policy
-Djava.awt.headless=true
-Dfelix.fileinstall.log.level=3
-Dfelix.fileinstall.poll=5000
-Dcom.sun.aas.instanceRoot=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase
-Dosgi.shell.telnet.ip=127.0.0.1
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Djava.endorsed.dirs=/home/apps/glassfish3122/glassfish/modules/endorsed:/home/apps/glassfish3122/glassfish/lib/endorsed
-Dcom.sun.aas.installRoot=/home/apps/glassfish3122/glassfish
-Dfelix.fileinstall.bundles.startTransient=true
-Djava.ext.dirs=/home/apps/jdk1.7.0_04/lib/ext:/home/apps/jdk1.7.0_04/jre/lib/ext:/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/lib/ext
-Dfelix.fileinstall.bundles.new.start=true
-Djavax.net.ssl.trustStore=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/cacerts.jks
-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
-Djava.security.auth.login.config=/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/config/login.conf
-DANTLR_USE_DIRECT_CLASS_LOADING=true
Dgosh.args=-noshutdown -c noop=true
Oct 16, 2012 2:27:51 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 3 msec.
[#|2012-10-16T14:27:54.391+0800|INFO|glassfish3.1.2|com.sun.enterprise.server.logging.GFFileHandler|_ThreadID=1;_ThreadName=Thread-2;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2.2 (build 5)|#]

[#|2012-10-16T14:27:54.543+0800|INFO|glassfish3.1.2|org.glassfish.ha.store.spi.BackingStoreFactoryRegistry|_ThreadID=1;_ThreadName=Thread-2;|Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry|#]

[#|2012-10-16T14:27:54.919+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=1;_ThreadName=Thread-2;|JTS5014: Recoverable JTS instance, serverId = [100]|#]

[#|2012-10-16T14:27:55.229+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=23;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 56ms - bound to [0.0.0.0:28086]|#]

[#|2012-10-16T14:27:55.229+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=22;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 31ms - bound to [0.0.0.0:28187]|#]

[#|2012-10-16T14:27:55.247+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=27;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 5ms - bound to [0.0.0.0:24854]|#]

[#|2012-10-16T14:27:55.273+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=35;_ThreadName=Thread-2;|Grizzly Framework 1.9.50 started in: 11ms - bound to [0.0.0.0:27682]|#]

[#|2012-10-16T14:27:55.662+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [http-listener-1] on host/port [0.0.0.0:28086]|#]

[#|2012-10-16T14:27:55.675+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [http-listener-2] on host/port [0.0.0.0:28187]|#]

[#|2012-10-16T14:27:55.686+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [admin-listener] on host/port [0.0.0.0:24854]|#]

[#|2012-10-16T14:27:55.751+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0171: Created virtual server [server]|#]

[#|2012-10-16T14:27:55.757+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0171: Created virtual server [__asadmin]|#]

[#|2012-10-16T14:27:56.237+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=1;_ThreadName=Thread-2;|WEB0172: Virtual server [server] loaded default web module []|#]

[#|2012-10-16T14:27:57.663+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=1;_ThreadName=Thread-2;|core.start_container_done|#]

[#|2012-10-16T14:27:57.976+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=1;_ThreadName=Thread-2;|SEC1002: Security Manager is OFF.|#]

[#|2012-10-16T14:27:58.000+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=1;_ThreadName=Thread-2;|SEC1010: Entering Security Startup Service|#]

[#|2012-10-16T14:27:58.004+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=1;_ThreadName=Thread-2;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2012-10-16T14:27:58.135+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=1;_ThreadName=Thread-2;|SEC1115: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2012-10-16T14:27:58.136+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=1;_ThreadName=Thread-2;|SEC1115: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2012-10-16T14:27:58.186+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=1;_ThreadName=Thread-2;|SEC1115: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.|#]

[#|2012-10-16T14:27:58.238+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=1;_ThreadName=Thread-2;|SEC1011: Security Service(s) Started Successfully|#]

[#|2012-10-16T14:27:58.764+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-2;|Exception while invoking class org.glassfish.persistence.jpa.JPADeployer prepare method|#]

[#|2012-10-16T14:27:58.765+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-2;|Exception while preparing the app|#]

[#|2012-10-16T14:27:58.765+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-2;|javax.naming.NameNotFoundException: No object bound to name java:app/jdbc/TestDB
java.lang.RuntimeException: javax.naming.NameNotFoundException: No object bound to name java:app/jdbc/TestDB
at org.glassfish.persistence.jpa.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:111)
at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:155)
at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
at com.sun.enterprise.v3.server.ApplicationLoaderService.postConstruct(ApplicationLoaderService.java:219)
at com.sun.hk2.component.AbstractCreatorImpl.inject(AbstractCreatorImpl.java:131)
at com.sun.hk2.component.ConstructorCreator.initialize(ConstructorCreator.java:91)
at com.sun.hk2.component.AbstractCreatorImpl.get(AbstractCreatorImpl.java:82)
at com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:67)
at com.sun.hk2.component.EventPublishingInhabitant.get(EventPublishingInhabitant.java:139)
at com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:78)
at com.sun.enterprise.v3.server.AppServerStartup.run(AppServerStartup.java:253)
at com.sun.enterprise.v3.server.AppServerStartup.doStart(AppServerStartup.java:145)
at com.sun.enterprise.v3.server.AppServerStartup.start(AppServerStartup.java:136)
at com.sun.enterprise.glassfish.bootstrap.GlassFishImpl.start(GlassFishImpl.java:79)
at com.sun.enterprise.glassfish.bootstrap.GlassFishDecorator.start(GlassFishDecorator.java:63)
at com.sun.enterprise.glassfish.bootstrap.osgi.OSGiGlassFishImpl.start(OSGiGlassFishImpl.java:69)
at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.launch(GlassFishMain.java:117)
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.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:97)
at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55)
Caused by: javax.naming.NameNotFoundException: No object bound to name java:app/jdbc/TestDB
at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookupFromNamespace(GlassfishNamingManagerImpl.java:394)
at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookupFromAppNamespace(GlassfishNamingManagerImpl.java:420)
at com.sun.appserv.connectors.internal.api.ResourceNamingService.lookup(ResourceNamingService.java:209)
at com.sun.enterprise.connectors.service.ConnectorResourceAdminServiceImpl.lookup(ConnectorResourceAdminServiceImpl.java:227)
at com.sun.enterprise.connectors.ConnectorRuntime.lookupPMResource(ConnectorRuntime.java:463)
at org.glassfish.persistence.common.PersistenceHelper.lookupPMResource(PersistenceHelper.java:63)
at org.glassfish.persistence.jpa.ProviderContainerContractInfoBase.lookupDataSource(ProviderContainerContractInfoBase.java:71)
at org.glassfish.persistence.jpa.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:108)
... 29 more

#]

[#|2012-10-16T14:27:58.975+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-2;|Exception while preparing the app|#]

[#|2012-10-16T14:27:58.980+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-2;|GlassFish Server Open Source Edition 3.1.2.2 (5) startup time : Felix (2,432ms), startup services(4,926ms), total(7,358ms)|#]

[#|2012-10-16T14:27:59.290+0800|SEVERE|glassfish3.1.2|javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.recovery|_ThreadID=44;_ThreadName=Thread-2;|RAR7109: Error while loading jdbc resources during recovery : java:app/jdbc/TestDB|#]

[#|2012-10-16T14:27:59.291+0800|INFO|glassfish3.1.2|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.inbound|_ThreadID=44;_ThreadName=Thread-2;|Recovery of Inbound Transactions started.|#]

[#|2012-10-16T14:27:59.293+0800|WARNING|glassfish3.1.2|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.inbound|_ThreadID=44;_ThreadName=Thread-2;|RAR8505: Application [ testcase ] does not seem to have started. Skipping Inbound Recovery for the application.|#]

[#|2012-10-16T14:27:59.299+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=44;_ThreadName=Thread-2;|JTS5014: Recoverable JTS instance, serverId = [100]|#]

[#|2012-10-16T14:27:59.780+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=12;_ThreadName=Thread-2;|/home/apps/glassfish3122/glassfish/nodes/localhost-domain1/testcase/autodeploy/bundles does not exist, please create it.|#]

[#|2012-10-16T14:27:59.863+0800|INFO|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=49;_ThreadName=Thread-2;|JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://lwlserver:28692/jndi/rmi://lwlserver:28692/jmxrmi|#]



 Comments   
Comment by craigday [ 16/Oct/12 07:36 AM ]

Also, issue briefly discussed (with another report of the issue) at http://www.java.net/forum/topic/glassfish/glassfish/application-scoped-resources-and-persistencexml-do-not-work-together-what-i-did-wrong

Comment by Hong Zhang [ 16/Oct/12 01:08 PM ]

Assign to Jagadish for initial evaluation.

(BTW: I feel we should have a resource category or something similar in the JIRA..)

Comment by Jagadish [ 18/Oct/12 11:17 AM ]

Transferring to Naman for investigation.

Comment by craigday [ 18/Oct/12 02:26 PM ]

Any update/progress on this issue?

Comment by craigday [ 23/Oct/12 12:32 AM ]

Any update/progress on this issue?

Comment by naman_mehta [ 23/Oct/12 03:19 AM ]

I will look into this and update you on the same.

Comment by naman_mehta [ 26/Oct/12 09:59 AM ]

To fix the same we are calling 'ApplicationScopedResourcesManager' service to run during start up to load all application scoped resources. Attaching new testcase to verify the same.

Current attached testcase is not working as it's throwing derby error 'https://issues.apache.org/jira/browse/DERBY-5526' on restart.

Comment by naman_mehta [ 26/Oct/12 09:59 AM ]

Attached new testcase to verify this bug.

Comment by naman_mehta [ 26/Oct/12 10:00 AM ]

Made required changes and run all required tests.

Sending kernel/src/main/java/com/sun/enterprise/v3/server/ApplicationLoaderService.java
Transmitting file data .
Committed revision 56746.





[GLASSFISH-19154] EJB Schedule triggered every second Created: 14/Oct/12  Updated: 26/Oct/12  Resolved: 26/Oct/12

Status: Resolved
Project: glassfish
Component/s: ejb_container
Affects Version/s: 3.1.2
Fix Version/s: 4.0_b61

Type: Bug Priority: Major
Reporter: perissf Assignee: marina vatkina
Resolution: Duplicate Votes: 0
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day
Environment:

Windows Vista


File Attachments: Java Archive File ejb-container.jar     Java Source File NewSessionBean.java    
Tags: ejb schedule
Participants: marina vatkina and perissf

 Description   

GlassFish ver: 3.1.2.2 build 5.
I can reproduce the issue on my Vista PC but non on server Windows Server 2008.

Create with NetBeans a new EJB Module. Create a Stateless EJB with a persistent timer annotated like this:

@Schedule(dayOfWeek="Mon-Fri", hour="7", minute="0", second="0")

Run it on Sunday.
During deployment, GlassFish will give the following output:
Informazioni: keepstate is true and will not create new auto timers during deployment.
Informazioni: Rescheduling missed expiration for periodic timer '17@@1350199439622@@server@@domain1' 'TimedObject = NewSessionBean' 'Application = EJBModule5' 'CREATED' 'PERIODIC' 'Container ID = 88486669793296384' 'Mon Oct 08 07:00:00 CEST 2012' '0' '0 # 0 # 7 # * # * # Mon-Fri # * # null # null # null # true # dailyTask # 0' . Last timer expiration occurred at Sun Oct 14 10:35:31 CEST 2012

After deployment, the timer is triggered every second.
The same module, when deployed on the Server, doesn't give those information messages and the timer is not triggered every second, and this is the correct behaviour.



 Comments   
Comment by perissf [ 14/Oct/12 09:17 AM ]

Note that the deployment has been done on Sun Oct 14. The missed expiration (Mon Oct 08 07:00:00) is on last Monday prior to the deployment date.

Comment by marina vatkina [ 15/Oct/12 04:58 PM ]

Can you check the locales of your setups? If the locales are different, you might be seeing this bug: http://java.net/jira/browse/GLASSFISH-18804

Comment by perissf [ 15/Oct/12 08:52 PM ]

My default locale is it-IT. I agree that might be the cause, together with keepstate option and a missed expiration. Unfortunately I am not able to reproduce the issue anymore (perhaps because it's Monday).

Comment by marina vatkina [ 15/Oct/12 10:19 PM ]

That other bug says it's Sunday specific.

Comment by marina vatkina [ 16/Oct/12 12:09 AM ]

See my note to that other bug: http://java.net/jira/browse/GLASSFISH-18804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347968#action_347968

I can't reproduce the error on it_IT locale

Comment by marina vatkina [ 16/Oct/12 08:07 PM ]

patched version for using EN locale for all calendars and string conversions

Comment by marina vatkina [ 16/Oct/12 08:09 PM ]

Can you try the attached jar (replace the same jar in the modules dir, preserving the original somewhere)? It has the fix for GLASSFISH-18804.

Comment by marina vatkina [ 26/Oct/12 02:11 AM ]

Let's close it as a duplicate of GLASSFISH-18804. Please reopen if the fix for GLASSFISH-18804 doesn't solve it.





[GLASSFISH-19125] GFFileHandler blocks on log calls when consumer thread catches RuntimeException Created: 05/Oct/12  Updated: 30/Oct/12  Resolved: 30/Oct/12

Status: Resolved
Project: glassfish
Component/s: logging
Affects Version/s: 3.1.2_b23
Fix Version/s: 4.0_b61

Type: Bug Priority: Major
Reporter: Oresztesz Margaritisz Assignee: sandeep.shrivastava
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags:
Participants: Oresztesz Margaritisz and sandeep.shrivastava

 Description   

Inside the GFFileHandler class all log requests arrive in an ArrayBlockingQueue. There is a dedicated consumer thread started inside postConstruct() which removes entries from the queue and pushes them to the filesystem. However if any push eds up by throwing RuntimeException, the thread swallows the exception and quits. After a while the ArrayBlockingQueue fills up and all log calls are turning to blocking calls. The server hangs up without any response, the ADB fails to start, and any loaded application may hang at any point (where log is called).

I post the code block inside the postConstruct() call which starts the consumer thread:
...

// start the Queue consummer thread.

pump = new Thread() {

public void run() {
try {
while (!done.isSignalled()) { log(); }
} catch (RuntimeException e) {

}
}

};
pump.start();
...



 Comments   
Comment by sandeep.shrivastava [ 30/Oct/12 09:36 PM ]

This should be fixed with revision # 56802.





[GLASSFISH-18418] Deployment: Inspect JDK 7 getMethods()/getDeclaredMethods() usage Created: 28/Feb/12  Updated: 07/Nov/12  Resolved: 07/Nov/12

Status: Resolved
Project: glassfish
Component/s: deployment
Affects Version/s: 4.0_b25
Fix Version/s: 4.0_b61

Type: Task Priority: Major
Reporter: Joe Di Pol Assignee: Hong Zhang
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags:
Participants: Hong Zhang and Joe Di Pol

 Description   

Recent JDK 7 releases have altered the order of methods returned by the
Class.getMethods() and Class.getDeclaredMethods() calls. The order is
no longer stable and can change from one JVM run to the next.

This caused a number of sporadic bugs to appear during 3.1.2 development
when running with JDK 7. Those have been fixed, but further inspection
of the source has found a number of cases where we use getMethods() and
getDeclaredMethods().

Each of these cases should be visually inspected to see if the code is
making any assumptions on the order of methods returned by get*Methods().
In particular it should handle the case of multiple methods having the
same name.

For more details on what to look for and how to fix it see this document:

https://wikis.oracle.com/display/GlassFish/Method+Ordering+from+Class.getMethods

Please inspect the following files for their use of getMethods() /
getDeclaredMethods() to ensure the code is not making any assumptions
with respect to the order of methods returned. Create bugs for
any issues that need to be fixed and link them to this task. Once you
have completed inspection update this task with status and close it.

Deployment Object Library
    EjbCMPEntityDescriptor.java
    EjbDescriptor.java
    IASEjbCMPEntityDescriptor.java
    ManagedBeanHandler.java
    MessageDescriptor.java
    PersistenceDescriptor.java
    TypeUtil.java
    ComponentValidator.java
    EjbBundleValidator.java
    EjbMessageBeanDescriptor.java
    LifecycleCallbackDescriptor.java
    WebComponentDescriptor.java
GlassFish Java EE Annotation Framework
    ComponentDefinition.java


 Comments   
Comment by Hong Zhang [ 07/Nov/12 02:38 PM ]

Closed the issue after checking with the relevant container teams.





[GLASSFISH-16516] Jersey: Review and improve JSR-330 (Java Dependency Injection) integration Created: 02/May/11  Updated: 04/Dec/12  Resolved: 04/Dec/12

Status: Resolved
Project: glassfish
Component/s: web_services
Affects Version/s: None
Fix Version/s: 4.0_b61

Type: Improvement Priority: Major
Reporter: Jakub Podlesak Assignee: Marek Potociar
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_2prd
Participants: Jakub Podlesak and Marek Potociar

 Comments   
Comment by Marek Potociar [ 04/Dec/12 06:43 PM ]

The JSR330 support provided by HK2 is being leveraged by Jersey RI. As for JAX-RS 2.0, this support has been dropped.





[GLASSFISH-16487] Enhance logging related commands to support GlassFish use as a PaaS environment Created: 27/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: logging
Affects Version/s: None
Fix Version/s: 4.0_b61

Type: New Feature Priority: Major
Reporter: naman_mehta Assignee: naman_mehta
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16494 Enhancement for logging in a PaaS env... Closed
Tags: ee7_cleanup_closed
Participants: naman_mehta and Tom Mueller

 Description   

Creating this RFE based on my investigation on logging side to support GlassFish use as a PaaS environment.

So plan to update more details after one pager review comment:
http://wikis.sun.com/display/GlassFish/v32LoggingOnePager#v32LoggingOnePager-4.1.1EnhancementforlogginginaPaaSenvironment



 Comments   
Comment by Tom Mueller [ 01/Oct/12 10:27 PM ]

Since cloud support has been deferred for the Java EE 7 release, this issue is being closed. If it is useful for future Java EE work, it can be reopened.





[GLASSFISH-16483] Multiple application deployment to user-managed cluster Created: 27/Apr/11  Updated: 14/Mar/12  Resolved: 18/Jan/12

Status: Resolved
Project: glassfish
Component/s: deployment
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Critical
Reporter: Hong Zhang Assignee: Hong Zhang
Resolution: Won't Fix Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16431 CLUST-2 User-Managed Clusters Resolved
Tags: 3_2prd
Participants: Hong Zhang and Tom Mueller

 Description   

Allow multiple applications to be deployed to an user-managed cluster



 Comments   
Comment by Tom Mueller [ 18/Jan/12 08:58 PM ]

The 3.2 release has been cancelled - moving on to 4.0.
Marking this as "won't fix" because it isn't a part of the 4.0 plan.





[GLASSFISH-16454] Metro 2.2 for GlassFish 3.2 Created: 26/Apr/11  Updated: 26/Oct/12  Resolved: 26/Oct/12

Status: Closed
Project: glassfish
Component/s: web_services
Affects Version/s: None
Fix Version/s: 4.0_b61

Type: New Feature Priority: Major
Reporter: ritzmann Assignee: ritzmann
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_2prd
Participants: michael.y.chen and ritzmann

 Description   

http://wikis.sun.com/display/GlassFish/GF3.2MetroOnePager



 Comments   
Comment by michael.y.chen [ 26/Oct/12 05:48 AM ]

There is no 3.2. New issue for 4.0 is here. http://java.net/jira/browse/GLASSFISH-19230





[GLASSFISH-16428] Support application versioning for Paas deployment Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: deployment
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Major
Reporter: Hong Zhang Assignee: Hong Zhang
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed
Participants: Hong Zhang and Tom Mueller

 Description   

Support application versioning for Paas deployment.

Necessary changes will be made on the deployment framework to allow orchestrator to plug in its work to do service provisioning for versioned applications.

This is a sub issue to address requirements on deployment for the high level service provisioning feature. End-to-end feature delivery will depend on service orchestration.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 10:27 PM ]

Since cloud support has been deferred for the Java EE 7 release, this issue is being closed. If it is useful for future Java EE work, it can be reopened.





[GLASSFISH-16427] Support the asynch mode for Paas deployment Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: deployment
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Major
Reporter: Hong Zhang Assignee: Hong Zhang
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16409 Support various PaaS deployment scena... Closed
Tags: ee7_cleanup_closed
Participants: Hong Zhang and Tom Mueller

 Description   

Support the asynch mode for Paas deployment. Paas deployment could be a long running process and we want to provide an option for user to run the deploy command in asynch mode.

This depends on the command framework to provide the basic implementation for progress reporting during long-running commands.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 10:27 PM ]

Since cloud support has been deferred for the Java EE 7 release, this issue is being closed. If it is useful for future Java EE work, it can be reopened.





[GLASSFISH-16409] Support various PaaS deployment scenarios Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: None
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Major
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16423 Support the basic Paas deploy and und... Closed
depends on GLASSFISH-16425 Support the Paas enable and disable s... Closed
depends on GLASSFISH-16426 Support the Paas redeploy scenario. Closed
depends on GLASSFISH-16424 Additional support for Paas deploy an... Closed
depends on GLASSFISH-16427 Support the asynch mode for Paas depl... Closed
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed
Participants: Sivakumar Thyagarajan and Tom Mueller

 Description   

Support various scenarios around single-click application provisioning and deployment(PaaS deployment). Support could include:

  • P2: Deployment plan: Allow a user to specify the cloud meta-data external to the application, via deployment plan Deployment module must not ignore the cloud meta-data specified via deployment plan
  • P1: Automatic Service Decommissioning: Automatically decommission all the application-scoped provisioned services of an application during application undeployment.
  • P1: Pause/Stop Provisioned Services: Pause/Stop all the application-scoped provisioned services when an application is disabled. Similarly, start all the provisioned services when the application is enabled. The Orchestrator will invoke the Plugin to pause/stop the service. So it is the Plugin's responsibility to stop the service.
  • P1: Provisioning during redeployment: Support redeployment of the application. Possibly with a "--retain" redeployment option to re-use the previously provisioned services instead of re-provisioning again.
  • P3: Support application versioning: Only one version of the application will be active at a time. Each version of the application will have its own provisioned service(s) scoped to that particular version of the application. When a particular version of the application is disabled, all its associated application-scoped services are stopped.
  • P1: Service decommissioning during domain deletion: Decommission all the provisioned services (application scoped and global/shared) during domain deletion.
    We should decommission shared services as they are used only within the domain. The Orchestrator will invoke all the related plugins to decommission the services.
    Admin infrastructure would need to send a delete-domain callback to the Orchestrator.
  • P1: Track provisioned services: Orchestrator must keep track of all the services provisioned via the Orchestrator.


 Comments   
Comment by Tom Mueller [ 01/Oct/12 10:27 PM ]

Since cloud support has been deferred for the Java EE 7 release, this issue is being closed. If it is useful for future Java EE work, it can be reopened.





[GLASSFISH-16405] Automatically provision services during application deployment Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16423 Support the basic Paas deploy and und... Closed
depends on GLASSFISH-16424 Additional support for Paas deploy an... Closed
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed
Participants: shreedhar_ganapathy, Sivakumar Thyagarajan and Tom Mueller

 Description   

Automatically provision services during application deployment:

Provision all the required dependent services during deployment of a Java EE application. The application could come up with full/partial/no cloud meta-data.

The Orchestrator would use the IaaS APIs to provision and manage the lifecycle of a Provisioned Service. The Orchestrator must be Service VM Host/Guest OS agnostic. In other words, the Orchestrator must not have any additional dependencies/restrictions on Host/Guest OS of a Service VM Image as we expect the IaaS API and implementation to handle these.

The following must be considered as part of Service Provisioning

  • Service Provider Matching (Template matching rules): Using the service meta-data bundled with or discovered from the application, the Orchestrator must match the service requirements of the application to a Service Template. This template would then be used to provision and realize the Service. These matching rules are still a work in progress. One simple rule that has been identified is: If the application requires a RDBMS service and the service definition is not specified in the cloud meta-data or the service definition does not explicit point to a particular Service Provider(say MySQL), then by default the Orchestrator will select a "default" template (e.g: Derby service template).
  • Atomic provisioning: Provisioning of the dependent services of an application must be atomic (ALL or NONE).
  • Failure handling: If a subset of dependent services cannot be provisioned, the deployment must fail and the state of the system must roll-back to the state prior to the current deployment. [Atomic deployment]
  • Ambiguity during provider matching When multiple plugins can handle particular service requirement and a particular service provider can not be matched then deployment must fail.
  • Automatically provisioning services for vanilla Java EE archives


 Comments   
Comment by Sivakumar Thyagarajan [ 21/Apr/11 08:56 AM ]

Updated the feature description to add additional service provisioning requirements

Comment by shreedhar_ganapathy [ 27/Oct/11 07:33 PM ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 09:57 PM ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16402] Single-click application provisioning and deployment of a PaaS application Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16403 Support External, Shared Provisioned ... Closed
depends on GLASSFISH-16411 Add administration and management cap... Closed
depends on GLASSFISH-16410 Provide a set of standard pre-built S... Closed
depends on GLASSFISH-16407 Automatic Service association for a P... Closed
depends on GLASSFISH-16405 Automatically provision services duri... Closed
depends on GLASSFISH-16404 Define deployment-time service metada... Closed
depends on GLASSFISH-16409 Support various PaaS deployment scena... Closed
depends on GLASSFISH-16408 Service provisioning to support a sta... Closed
Tags: ee7_cleanup_closed
Participants: shreedhar_ganapathy, Sivakumar Thyagarajan and Tom Mueller

 Description   

This is the umbrella RFE for the Service Orchestration feature in GlassFish 3.2.

Single-click application provisioning and deployment of a PaaS application through service dependency discovery, service provisioning and service association.



 Comments   
Comment by Sivakumar Thyagarajan [ 21/Apr/11 10:37 AM ]

Adding sub-RFEs for this umbrella RFE.

Comment by shreedhar_ganapathy [ 27/Oct/11 07:33 PM ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 09:57 PM ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-13996] [PERF] Copyobject fails on long linked structures Created: 14/Oct/10  Updated: 18/Oct/12  Resolved: 18/Oct/12

Status: Resolved
Project: glassfish
Component/s: orb
Affects Version/s: 3.1
Fix Version/s: 4.0_b61

Type: Improvement Priority: Blocker
Reporter: Ken Cavanaugh Assignee: Harshad Vilekar
Resolution: Works as designed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issue Links:
Dependency
blocks GLASSFISH-13573 [PERF] Huge regression with trade2 be... Closed
Issuezilla Id: 13,996
Tags: 3_1-exclude
Participants: Harshad Vilekar, Ken Cavanaugh, Nazrul and Scott Oaks

 Description   

The copyobject implementation currently has problems with LinkedLists and
similar data structures. The recursive traversal of such objects can cause
stack overflows if the linked lists are long enough (generally a few thousand
elements will cause this problem).

This issue proposes an enhancement to fix this behavior by moving to a
non-recursive worklist algorithm for traversing all object graphs.



 Comments   
Comment by Scott Oaks [ 20/Oct/10 08:18 AM ]

The current handling of linked lists is also quite a performance penalty.

Comment by Scott Oaks [ 22/Oct/10 09:17 AM ]

...

Comment by Nazrul [ 22/Oct/10 01:09 PM ]

This is an important performance fix needed for this release. Refer to 13573.

Comment by Ken Cavanaugh [ 02/Nov/10 10:44 AM ]

Assuming that this issue is fixed in the current build (which I believe it is)
by using the Map copier on LinkedHashMap, I am changing this to an
enhancement and moving it to the next release. There is not enough time
remaining to do this for 3.1.

Comment by Harshad Vilekar [ 18/Oct/12 07:39 PM ]

I believe this issue is already resolved, since the dependent issue 13573 is closed. No further action is planned on this issue.





[GLASSFISH-1429] JMS standalone client hangs on exit Created: 06/Nov/06  Updated: 24/Oct/12  Resolved: 24/Oct/12

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 9.1pe
Fix Version/s: 4.0_b61

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

Operating System: All
Platform: All


Issuezilla Id: 1,429
Status Whiteboard:

v2.1.1_exclude

Tags:
Participants: claus_list, David Zhao, Ed Bratt, gfbugbridge, jicai.liu, jthoennes, Kim Haase, oleksiys, rampsarathy, Satish Kumar, Sivakumar Thyagarajan and Tom Mueller

 Description   

This appears to be a bug. Even when the connection is closed, there appears to
be an active MQ client daemon thread which prevents the VM from exiting. Could
you file a GlassFish issue? We shall investigate this further.

> "Timer-0" daemon prio=1 tid=0x09b4b328 nid=0x622f in Object.wait()
[0xa72f8000..0xa72f8f30]
> at java.lang.Object.wait(Native Method)
> - waiting on <0xaa780068> (a java.util.TaskQueue)
> at java.util.TimerThread.mainLoop(Timer.java:509)
> - locked <0xaa780068> (a java.util.TaskQueue)
> at java.util.TimerThread.run(Timer.java:462)
>
> "iMQReadChannel-1" prio=1 tid=0x09b450d0 nid=0x622e runnable
[0xa7379000..0xa7379eb0]
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
> - locked <0xaae3dfe8> (a java.io.BufferedInputStream)
> at
com.sun.messaging.jmq.io.ReadOnlyPacket.readFully(ReadOnlyPacket.java:263)
> at
com.sun.messaging.jmq.io.ReadOnlyPacket.readFixedHeader(ReadOnlyPacket.java:183)
> at
com.sun.messaging.jmq.io.ReadOnlyPacket.readPacket(ReadOnlyPacket.java:143)
> at
com.sun.messaging.jmq.io.ReadWritePacket.readPacket(ReadWritePacket.java:73)
> - locked <0xaa73e1f8> (a com.sun.messaging.jmq.io.ReadWritePacket)
> at
com.sun.messaging.jmq.jmsclient.ProtocolHandler.readPacket(ProtocolHandler.java:1719)
> at com.sun.messaging.jmq.jmsclient.ReadChannel.run(ReadChannel.java:1139)
> at java.lang.Thread.run(Thread.java:595)
>
> "imqConnectionFlowControl-1" prio=1 tid=0x09b44c40 nid=0x622d in Object.wait()
[0xa73fa000..0xa73fae30]
> at java.lang.Object.wait(Native Method)
> - waiting on <0xaae3e110> (a com.sun.messaging.jmq.jmsclient.FlowControl)
> at com.sun.messaging.jmq.jmsclient.FlowControl.run(FlowControl.java:290)
> - locked <0xaae3e110> (a com.sun.messaging.jmq.jmsclient.FlowControl)
> at java.lang.Thread.run(Thread.java:595)

Thanks
--Siva.



 Comments   
Comment by gfbugbridge [ 17/Jan/07 06:29 PM ]

<BT6514413>

Comment by Sivakumar Thyagarajan [ 16/Apr/07 02:44 AM ]

Requesting Ramesh to look at this.

Comment by rampsarathy [ 17/Apr/07 11:44 PM ]

There are certain daemon threads associated with a jms connection, since the
connection factory that is looked up is a managed connection factory (belongs to
jms resource adaptor), and the connections are obtained and returned from/to a
connection pool, a connection.close will not actually close the underlying
ohysical connection but only return it to the pool. So the threads that were
created for this connections are also alive as long as the connecion is kept
alive in the pool. And there are specific reasons why these threads have to be
daemon threads and not user threads.
Because of the above reasons the client program hangs, waiting indefinitely (or
until the idle time out in the pool is exhausted) for the threads to exit.

As a workaround we need to configure the connection pool (used by the connector
resource) in such a way that it does not pool connections (closes them
immediately instead of pooling it).
This can be achieved by setting the following pool properties in GlassFish V2

steady-pool-size=0
max-connection-usage-count=1
pool-resize-quantity=1
idle-timeout-in-seconds=5 ( the lesser the better because the connnections will
be closed after this time)

Please use asadmin set --user <user> --passwordfile <file>
domain.resources.connector-connection-pool.<poolname>.<property>=<value>

Using the above values (in b42) the client program exits immediately,

Comment by jthoennes [ 20/Aug/09 05:01 AM ]

See discussion in forums thread:
http://forums.java.net/jive/thread.jspa?threadID=37143

I also remember a related issue with regard to the ACC container.
There was a specific mechanism used to tear down the OpenMQ runtime.

This workaround suggested by rampsarathy is not a solution to this issue.

Comment by rampsarathy [ 20/Aug/09 05:15 AM ]

Assigning to Satish

Comment by Satish Kumar [ 13/Oct/09 11:38 PM ]

This is a GF V2.1 issue. Marking this as v3_exlude

Comment by Satish Kumar [ 13/Oct/09 11:41 PM ]

Adding status white board v3_exclude

Comment by Kim Haase [ 14/Oct/09 08:05 AM ]

This is also an issue at v3 (I'm using glassfish-v3-b68-10_13_2009.zip).

A standalone client jar hangs on exit (with a plain vanilla connection factory).
The only way to prevent the hang is to deploy the jar with the --retrieve option
or to deploy it and then use the get-client-stubs command. The client jar that
is returned contains a Facade class that enables the client to exit.

The standalone client jar that hangs consists of a simple Java class:

jdench 183 =>jar tvf dist/producer.jar
0 Wed Oct 14 10:06:14 EDT 2009 META-INF/
124 Wed Oct 14 10:06:12 EDT 2009 META-INF/MANIFEST.MF
3413 Wed Oct 14 10:06:12 EDT 2009 Producer.class

When I run the jar, the output looks like this. I have to Control-C to exit the app.

jdench 193 =>appclient -client dist/producer.jar queue 3
Oct 14, 2009 10:21:58 AM
com.sun.enterprise.transaction.JavaEETransactionManagerSimplified initDelegates
INFO: Using
com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the
delegate
Oct 14, 2009 10:22:14 AM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting: REMOTE
Oct 14, 2009 10:22:14 AM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started:REMOTE
Oct 14, 2009 10:22:15 AM com.sun.messaging.jms.ra.ManagedConnectionFactory
setAddressList
INFO: MQJMSRA_MF1101: setAddressList:NOT setting default value=localhost
Oct 14, 2009 10:22:15 AM com.sun.messaging.jms.ra.ManagedConnectionFactory
setPassword
INFO: MQJMSRA_MF1101: setPassword:NOT setting default value
Oct 14, 2009 10:22:15 AM com.sun.messaging.jms.ra.ManagedConnectionFactory
setUserName
INFO: MQJMSRA_MF1101: setUserName:NOT setting default value=guest
Destination type is queue
Sending message: This is message 1
Sending message: This is message 2
Sending message: This is message 3
^C jdench 194 =>

The jar returned after deployment looks like this:

jdench 188 =>jar tvf client-jar/appClient.jar
248 Wed Oct 14 10:13:40 EDT 2009 META-INF/MANIFEST.MF
1696 Wed Oct 14 10:13:40 EDT 2009 META-INF/application-client.xml
893 Wed Oct 14 10:13:40 EDT 2009 META-INF/sun-application-client.xml
18414 Wed Oct 14 10:13:40 EDT 2009
org/glassfish/appclient/client/AppClientFacade.class

When it runs, the output looks like this:

jdench 191 =>appclient -client client-jar/appClient.jar queue 3
Oct 14, 2009 10:18:52 AM
com.sun.enterprise.transaction.JavaEETransactionManagerSimplified initDelegates
INFO: Using
com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the
delegate
Oct 14, 2009 10:19:20 AM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting: REMOTE
Oct 14, 2009 10:19:21 AM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started:REMOTE
Oct 14, 2009 10:19:23 AM com.sun.messaging.jms.ra.ManagedConnectionFactory
setAddressList
INFO: MQJMSRA_MF1101: setAddressList:NOT setting default value=localhost
Oct 14, 2009 10:19:23 AM com.sun.messaging.jms.ra.ManagedConnectionFactory
setPassword
INFO: MQJMSRA_MF1101: setPassword:NOT setting default value
Oct 14, 2009 10:19:23 AM com.sun.messaging.jms.ra.ManagedConnectionFactory
setUserName
INFO: MQJMSRA_MF1101: setUserName:NOT setting default value=guest
Destination type is queue
Sending message: This is message 1
Sending message: This is message 2
Sending message: This is message 3
Oct 14, 2009 10:19:24 AM com.sun.messaging.jms.ra.ResourceAdapter stop
INFO: MQJMSRA_RA1101: SJSMQ JMSRA stopping...
Oct 14, 2009 10:19:24 AM com.sun.messaging.jms.ra.ResourceAdapter stop
INFO: MQJMSRA_RA1101: SJSMQ JMSRA stopped.
Oct 14, 2009 10:19:24 AM
com.sun.enterprise.connectors.service.ResourceAdapterAdminServiceImpl
sendStopToResourceAdapter
INFO: ra.stop-successful

Comment by Ed Bratt [ 15/Oct/09 04:26 PM ]

Will not fix in v2.1.1

Comment by Satish Kumar [ 26/Oct/09 04:29 AM ]

Removing v3_exclude from the status whiteboard since this appears to be a
problem in V3 as well.

Comment by jicai.liu [ 05/May/11 03:19 AM ]

When i set the property "jms.jmsra.inAcc" with the value "false",it works well~
note: in version 2

Comment by jthoennes [ 12/May/11 04:07 AM ]

In reply to comment #11:
> When i set the property "jms.jmsra.inAcc" with the value "false",it works well~

I guess you mean "imq.jmsra.inAcc"? Shall I set this as a system property as in:

java -Dimq.jmsra.inAcc=false

Were are these system properties documented?

Comment by claus_list [ 12/Jun/11 09:16 AM ]

java -Dimq.jmsra.inAcc=false

Works on my consumer but not on the producer. (same setup standalone clients according to the tutorial)

Does not work for me. Is there another system property ?

Comment by Tom Mueller [ 06/Mar/12 10:00 PM ]

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

Comment by David Zhao [ 24/Oct/12 02:54 AM ]

Fixed.





Generated at Mon Apr 21 05:47:02 UTC 2014 using JIRA 4.0.2#472.