[GLASSFISH-19265] [Perf] Glassfish 4.0 uses Dynamic thread pool by default, while Glassfish 3.1.2 uses Fixed thread pool as default Created: 31/Oct/12  Updated: 16/Feb/13  Resolved: 16/Feb/13

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

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

Any platform/OS


Tags: Grizzly, PSRBUG, Threadpool

 Description   

We found that Glassfish 4.0 uses Dynamic thread pool as default, while Glassfish 3.1.2 uses Fixed thread pool as default. While there is anything wrong with choice of moving from Fixed to Dynamic thread pool (thats my own judgement), but it could lead to incomparable out-of-the-box peformance between these two releases. If this change has been evaluated earlier, then please mention that in this bug's comments.



 Comments   
Comment by oleksiys [ 31/Oct/12 ]

could be a bug in Glassfish 3.1.2, cause default domain.xml doesn't change max/min thread-pool-size explicitly so default min=2, max=5 should be used.
Can you pls. check Glassfish 3.1.2 domain.xml thread-pool settings?

Comment by deep_singh [ 31/Oct/12 ]

I am not setting thread pool min and max sizes explicitly. The domain.xml does not show any min/max entry for http-thread-pool. However when I look at thread dump, it shows me that its using Fixed thread pool.

Comment by oleksiys [ 16/Feb/13 ]

fixed





[GLASSFISH-19219] @WebServlet values are lost when the servlet is defined in deployment descriptor, under a different name Created: 23/Oct/12  Updated: 24/Oct/12  Resolved: 24/Oct/12

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

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


 Description   

When the same servlet class is declared in two places under @WebServlet and Deployment descriptor using different servlet name, they should be treated as different servlet. Right now, @WebServlet defined values are lost.



 Comments   
Comment by Shing Wai Chan [ 24/Oct/12 ]

Sending src/main/java/org/glassfish/web/deployment/annotation/handlers/WebServletHandler.java
Transmitting file data .
Committed revision 56712.





[GLASSFISH-19200] Performance Tuner page is broken, giving exception on screen Created: 19/Oct/12  Updated: 22/Oct/12  Resolved: 22/Oct/12

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0_b58
Fix Version/s: 4.0_b60

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


 Description   

Performance Tuner which is a value added feature in console, is broken.
Click on the Performance Tuner tree node, the page on the right says:

HTTP Status 500 - Internal Server Error

type Exception report

messageInternal Server Error

descriptionThe server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Handler 'tuner.runtimeInfo' in event 'beforeCreate' is not declared! Ensure the '@Handler' annotation has been defined on the handler Java method, that it has been compiled with the annotation processing tool, and that the resulting 'META-INF/jsftemplating/Handler.map' is located in your classpath (you may need to do a clean build).

root cause

com.sun.jsftemplating.layout.SyntaxException: Handler 'tuner.runtimeInfo' in event 'beforeCreate' is not declared! Ensure the '@Handler' annotation has been defined on the handler Java method, that it has been compiled with the annotation processing tool, and that the resulting 'META-INF/jsftemplating/Handler.map' is located in your classpath (you may need to do a clean build).

note The full stack traces of the exception and its root causes are available in the Oracle GlassFish Server 4.0 logs.
Oracle GlassFish Server 4.0



 Comments   
Comment by Anissa Lam [ 20/Oct/12 ]


The jar file is missing Handler.map. pom.xml changes is needed.

Comment by Anissa Lam [ 22/Oct/12 ]

Fixed.
Log Message:
------------
Use apt-maven-plugin to ensure jsftemplating handlers map is generated. This fixes GLASSFISH-19200

Modified Paths:
-----------
trunk/all/closed/appserver/performance-tuner/gui/pom.xml





[GLASSFISH-19130] Timer Creating "Active" Transactions in Transaction Service Monitor - Memory Leak Created: 05/Oct/12  Updated: 30/Oct/12  Resolved: 23/Oct/12

Status: Resolved
Project: glassfish
Component/s: jts
Affects Version/s: 3.1.2
Fix Version/s: 4.0_b60

Type: Bug Priority: Major
Reporter: hapi Assignee: marina vatkina
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Java Archive File jta.jar     Java Archive File jts.jar    
Tags: memory-leak, service, transaction

 Description   

After much isolation trying to pin down a memory leak I've gotten to what may be the root cause. We have the monitoring level set to HIGH for the Transaction Service and are using 3.1.2.2 build 5.

If I create a simple stateless bean that contains a method with a @Schedule annotation:

@Schedule(second = "", minute = "", hour = "", dayOfWeek = "", dayOfMonth = "", month = "", year = "*", info = "MasterScheduler")

This will cause the Transaction Service monitor to note an "active transaction" every time the timer is invoked.

Over the course of a day there's a noticeable memory leak and it will eventually run out of memory.

If we turn the monitoring level for the Transaction Service to OFF it goes away.



 Comments   
Comment by marina vatkina [ 09/Oct/12 ]

Timeout method (the one that is marked with @Schedule in your case) by default runs in a transaction. So the fact that transaction is active for each timeout, is a correct behavior. Do you see the monitoring table grow? Or do you see 1 transaction all the time?

Comment by hapi [ 09/Oct/12 ]

Yes with the Transaction Service monitoring turned on I see an active transaction added for each time the Timeout method is invoked and it never leaves the monitoring table. The table grows until it runs out of memory.

I would expect to see active transactions go to 1 and then go back to 0 after the method has completed. Am I looking at that the wrong way?

Comment by marina vatkina [ 09/Oct/12 ]

No, this shouldn't happen. I'll look into it.

Comment by hapi [ 11/Oct/12 ]

Curious - were you able to experience the same behavior? Should be quite simple to duplicate. Thanks.

Comment by marina vatkina [ 11/Oct/12 ]

Not yet - was busy with other stuff, but will check it as soon as I can

Comment by pdudits [ 22/Oct/12 ]

I am diagnosing similar situation right now, so I can put in some details from the heap dump. Our timer datasource is in a Oracle database, the pool is transactional (XATransaction), monitoring level for transaction service is set to LOW. The datasource is also used by the application itself.

We had the server die with OutOfMemoryError with J2EETransactionManagerSimplified.activeTransactions referring to 162319 transactions and allocating 1GB of heap. The com.sun.jts.CosTransactionTransactionState had following distribution by transaction state:

Transaction state Number of objects
7 STATE_COMMITED 135.327
11 STATE_COMMITTED_ONE_PHASE_OK 26.882
1 STATE_ACTIVE 76
9 STATE_ROLLED_BACK 18
10 STATE_COMMITTING_ONE_PHASE 2

One workaround was to annotate the timeout method with TransactionAttribute.NOT_SUPPORTED, but that resulted in last fire time of the timer not being updated in EJB_TIMER_TBL. This behaviour could not be reproduced with default datasource. The other is to disable monitoring of transaction service.

Another notable discovery from the heap dump is that all instances of com.sun.enterprise.transaction.JavaEETransactionImpl has value of isTimerTask == true.

Comment by marina vatkina [ 22/Oct/12 ]

yes, I do see it growing with some transaction removed and some not. Investigating...

Comment by marina vatkina [ 22/Oct/12 ]

Actually, concurrency might not be an issue, but the way transactions are committed - if they become XA transactions during commit, the monitoring table isn't updated, and the XA transaction can't be removed.

Comment by marina vatkina [ 23/Oct/12 ]

Can you try attached jars (you need both) with your 3.1.2 install? If you are using the trunk build, the fix will be available after the checkin.

Comment by marina vatkina [ 23/Oct/12 ]

Fixed with
Sending transaction/jta/src/main/java/com/sun/enterprise/transaction/JavaEETransactionImpl.java
Sending transaction/jta/src/main/java/com/sun/enterprise/transaction/JavaEETransactionManagerSimplified.java
Sending transaction/jts/src/main/java/com/sun/enterprise/transaction/jts/JavaEETransactionManagerJTSDelegate.java
Transmitting file data ...
Committed revision 56702.

Note that the changes include some cleanup in addition to the actual fix, which was to move monitoring table update to JavaEETransactionImpl (before it clears jtsTx ref)

Comment by hapi [ 30/Oct/12 ]

I can confirm (somewhat belatedly) that the attached jars did seem to solve the problem.

Will this be a part of some future sub-release? 3.1.2.3?

Comment by marina vatkina [ 30/Oct/12 ]

If there is a public release for 3.1.2.x, then yes. Otherwise you can get a patch from Oracle sustaining if you have a support contract.





[GLASSFISH-19103] [Perf] Glassfish 4.0 does not scale well compared to Glassfish 3.1.2 when adding more concurrent users while using Fixed HTTP thread pool Created: 24/Sep/12  Updated: 16/Feb/13  Resolved: 16/Feb/13

Status: Resolved
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0_b55
Fix Version/s: 4.0_b60

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

Linux x86 Suse Linux 2.6


Tags: PSRBUG

 Description   

This issue could be duplicate or subset of Glassfish issue GLASSFISH-19067, if not a new one. Will close the bug as appropriate.

When running a simple Session JSP test on a 4 CPU machine and using Fixed HTTP thread pool with same min/max pool values, found that when we add more users, Glassfish 3.1.2 is showing good scaling, but Glassfish 4.0 scales poorly.

Test 1: Thread pool size 15. Concurrent users 3
===================================
GF 3.1.2 TPS ==> 12061
GF 4.0 TPS ==> 14652
% diff ==> +21%

Test 2: Thread pool size 15. Concurrent users 5
====================================
GF 3.1.2 TPS ==> 19822
GF 4.0 TPS ==> 16318
% diff ==> -17%



 Comments   
Comment by oleksiys [ 25/Sep/12 ]

Deep, not sure about session.jsp, but when I tried embedded grizzly app and servlet (session.jsp like) on 256 concurrent users GF4 results were better than GF3.
Can you pls. explain why you think it's related to grizzly?

Comment by oleksiys [ 16/Feb/13 ]

fixed





[GLASSFISH-19080] Exception in JarURIPattern causes failures in webapp. Created: 16/Sep/12  Updated: 23/Oct/12  Resolved: 23/Oct/12

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

Type: Bug Priority: Major
Reporter: gfuser9999 Assignee: Shing Wai Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:
  • Any OS, any platform
  • GF3.1.x & GF 3.1.2

Tags: JarURIPattern, ZipException, getJarEntries

 Description   

When there is some invalid jar files in the filesystem,
the GlassFish cannot load web application. For example
the Admin console will fail to work. Even though
an invalid jar is added, the GF server should not
fail to start. THE WORST thing about this is there
is TOTALLY no indication of what/where this file is.

[#|2012-09-16T12:22:55.459+0000|SEVERE|oracle-glassfish3.1.2|org.apache.catalina.core.ContainerBase|_ThreadID=21;_ThreadName=Thread-2;|ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5332)
at com.sun.enterprise.web.WebModule.start(WebModule.java:498)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:733)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2019)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1669)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThread.java:210)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThread.java:108)
Caused by: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:88)
at org.glassfish.web.LibrariesTldProvider.postConstruct(LibrariesTldProvider.java:119)
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(EventPublishingIn at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationL
ifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplicat
ion(ApplicationLoaderService.java:375)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThr
ead.java:210)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThre
ad.java:108)
Caused by: java.lang.RuntimeException: java.util.zip.ZipException: error in open
ing zip file
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern
.java:88)
at org.glassfish.web.LibrariesTldProvider.postConstruct(LibrariesTldProv
ider.java:119)
at com.sun.hk2.component.AbstractCreatorImpl.inject(AbstractCreatorImpl.
java:131)
at com.sun.hk2.component.ConstructorCreator.initialize(ConstructorCreato
r.java:91)
at com.sun.hk2.component.AbstractCreatorImpl.get(AbstractCreatorImpl.jav
a:82)
at com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.jav
a:67)
at com.sun.hk2.component.EventPublishingInhabitant.get(EventPublishingIn
habitant.java:139)
at com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:78)
at org.jvnet.hk2.component.Habitat$5.get(Habitat.java:703)
at java.util.AbstractList$Itr.next(AbstractList.java:345)
at com.sun.enterprise.web.WebModuleListener.configureJsp(WebModuleListener.java:187)
at com.sun.enterprise.web.WebModuleListener.lifecycleEvent(WebModuleListener.java:148)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5329)
... 14 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at java.util.jar.JarFile.<init>(JarFile.java:135)
at java.util.jar.JarFile.<init>(JarFile.java:99)
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:78)
at com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:78)
at org.jvnet.hk2.component.Habitat$5.get(Habitat.java:703)
at java.util.AbstractList$Itr.next(AbstractList.java:345)
at com.sun.enterprise.web.WebModuleListener.configureJsp(WebModuleListener.java:187)
at com.sun.enterprise.web.WebModuleListener.lifecycleEvent(WebModuleListener.java:148)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5329)
... 14 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at java.util.jar.JarFile.<init>(JarFile.java:135)
at java.util.jar.JarFile.<init>(JarFile.java:99)
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:78)
.java:78)
... 27 more

#]

[#|2012-09-16T12:22:55.466+0000|WARNING|oracle-glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=21;_ThreadName=Thread-2;|java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
[#|2012-09-16T12:22:55.497+0800|SEVERE|oracle-glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=21;_ThreadName=Thread-2;|Exception while loading the app|#]

[#|2012-09-16T12:22:55.550+0000|SEVERE|oracle-glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=21;_ThreadName=Thread-2;|Exception while loading the app|#]

Cause:
------
1) The com.sun.enterprise.util.net.JarURIPattern.getJarEntries should
should be robust to ZipException.
I believe it should continue instead of bailing out entirely if it sees
a bad JAR. Imagine for example, we have a corrupt JAR or a JAR that
have permission denied.

2) Even if fail-fast, AT LEAST the default SHOULD have it LOG in WARNING
what this FILE is to have use do CORRECTIVE action.
As it is now, there just no easy way to know what file this is....



 Comments   
Comment by Tom Mueller [ 17/Sep/12 ]

Shing Wai, can you please take a look at this?

Comment by bernaps [ 25/Sep/12 ]

Please note that our production system did exactly the same thing after rebooting our DAS server with around 8 clusters defined in it. This server did not reboot for a few month.

Error is the same as above. Here is more info. We are not able to load the DAS at all. in this directory there is only one zip file which is the configuration

Here is startup log

[#|2012-09-25T10:30:44.322+0800|WARNING|glassfish3.1.2|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin|_ThreadID=37;_ThreadName=Thread-2;|There should be only 1 primordial module but 0 primordial modules were found.|#]

Sep 25, 2012 10:30:45 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=1024m
-XX:PermSize=768m
-XX:NewRatio=2
-XX:+UseLinuxPosixThreadCPUClocks
-Xms2048m
-Xmx2048m
-javaagent:/home/gfuser/glassfish312/glassfish/lib/monitor/flashlight-agent.jar
-server
-Dfelix.fileinstall.disableConfigSave=false
-Djavax.net.ssl.keyStore=/home/gfuser/glassfish312/glassfish/domains/domain1/config/keystore.jks
-Djava.awt.headless=true
-Dfelix.fileinstall.poll=5000
-Djava.endorsed.dirs=/home/gfuser/glassfish312/glassfish/modules/endorsed:/home/gfuser/glassfish312/glassfish/lib/endorsed
-Djava.net.preferIPv4Stack=true
-Dfelix.fileinstall.bundles.startTransient=true
-Djavax.net.ssl.trustStore=/home/gfuser/glassfish312/glassfish/domains/domain1/config/cacerts.jks
-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
-Djava.security.auth.login.config=/home/gfuser/glassfish312/glassfish/domains/domain1/config/login.conf
-DANTLR_USE_DIRECT_CLASS_LOADING=true
Dgosh.args=-nointeractive
-Dosgi.shell.telnet.maxconn=1
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Dfelix.fileinstall.dir=/home/gfuser/glassfish312/glassfish/modules/autostart/
-Dosgi.shell.telnet.port=7777
-Djava.security.policy=/home/gfuser/glassfish312/glassfish/domains/domain1/config/server.policy
-Dfelix.fileinstall.log.level=3
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dosgi.shell.telnet.ip=127.0.0.1
-Dcom.sun.aas.instanceRoot=/home/gfuser/glassfish312/glassfish/domains/domain1
-Dcom.sun.aas.installRoot=/home/gfuser/glassfish312/glassfish
-Djava.ext.dirs=/home/gfuser/jdk1.6.0_31/lib/ext:/home/gfuser/jdk1.6.0_31/jre/lib/ext:/home/gfuser/glassfish312/glassfish/domains/domain1/lib/ext
-Dfelix.fileinstall.bundles.new.start=true
Sep 25, 2012 10:30:47 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 41 msec.
[#|2012-09-25T10:30:54.445+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 (build 23)|#]

[#|2012-09-25T10:30:54.804+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1095: member: server is joining group: cluster-dcs-stress ...|#]

[#|2012-09-25T10:30:54.887+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|instantiated following NetworkManager implementation:com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyNetworkManager1_9|#]

[#|2012-09-25T10:30:54.890+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS MAX_MESSAGE_LENGTH=4,196,352|#]

[#|2012-09-25T10:30:54.896+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|
GrizzlyNetworkManager1_9 Configuration
BIND_INTERFACE_ADDRESS:null NetworkInterfaceName:null
TCPSTARTPORT..TCPENDPORT:9090..9200
MULTICAST_ADDRESS:MULTICAST_PORT:228.9.171.155:18290 MULTICAST_PACKET_SIZE:65536 MULTICAST_TIME_TO_LIVE: default
FAILURE_DETECT_TCP_RETRANSMIT_TIMEOUT(ms):10000
MAX_PARALLEL:15
START_TIMEOUT(ms):15000 WRITE_TIMEOUT(ms):10000
MAX_WRITE_SELECTOR_POOL_SIZE:30

#]

[#|2012-09-25T10:30:54.902+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=10;_ThreadName=Thread-2;|Grizzly 1.9 NetworkManager|#]

[#|2012-09-25T10:30:54.961+0800|INFO|glassfish3.1.2|grizzly|_ThreadID=11;_ThreadName=Thread-2;|GRIZZLY0001: Starting Grizzly Framework 1.9.46 - 9/25/12 10:30 AM|#]

[#|2012-09-25T10:30:55.001+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Grizzly controller listening on /0.0.0.0:9118. Controller started in 48 ms|#]

[#|2012-09-25T10:30:55.008+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Set via default minimum: MulticastSocket.getTimeToLive()=4|#]

[#|2012-09-25T10:30:55.014+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|MulticastSocket configuration: local socket address: 0.0.0.0/0.0.0.0:18290 network interface: name:null multicast address:/228.9.171.155 timeToLive=4|#]

[#|2012-09-25T10:30:55.041+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|HealthMonitor: heartBeatTimeout(ms)=2000 maxMissedBeats=3 failureDetectionTCPTimeout(ms)=10000 failureDetectionTCPPort=9000|#]

[#|2012-09-25T10:30:55.043+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|starting cluster cluster-dcs-stress for member:server|#]

[#|2012-09-25T10:30:55.050+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1061: MasterNode message listener is registered for member: server group: cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.068+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1005: Member server joined group cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.068+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1004: Started GMS for instance server in group cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.082+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-stress : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9118:228.9.171.155:18290:cluster-dcs-stress:server

#]

[#|2012-09-25T10:30:55.082+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.091+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.097+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=13;_ThreadName=Thread-2;|MySystemAdvertisement(summary): GMSMember name: server group: cluster-dcs-stress memberType: SPECTATOR startTime: Sep 25, 2012 10:30:54 AM HKT ID:10.11.1.207:9118:228.9.171.155:18290:cluster-dcs-stress:server TCP uri(s):[tcp://10.11.1.207:4000]|#]

[#|2012-09-25T10:30:55.102+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=13;_ThreadName=Thread-2;|MySystemAdvertisement(dump)=PEERID[10.11.1.207:9118:228.9.171.155:18290:cluster-dcs-stress:server]
CUSTOMTAGS[GROUP_NAME:cluster-dcs-stress, MEMBER_TYPE:SPECTATOR, START_TIME[10:30:54 AM HKT on Sep 25, 2012]], ENDPONTADDRESSES[[tcp://10.11.1.207:4000]], NAME:server, OSNAME:Linux, OSVERSION:3.0.0-15-server, OSARCH:amd64, HWARCH:amd64, HWVENDOR:Sun Microsystems Inc.|#]

[#|2012-09-25T10:30:55.122+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1095: member: server is joining group: cluster-dcs-prod ...|#]

[#|2012-09-25T10:30:55.129+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|instantiated following NetworkManager implementation:com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyNetworkManager1_9|#]

[#|2012-09-25T10:30:55.130+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS MAX_MESSAGE_LENGTH=4,196,352|#]

[#|2012-09-25T10:30:55.130+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|
GrizzlyNetworkManager1_9 Configuration
BIND_INTERFACE_ADDRESS:null NetworkInterfaceName:null
TCPSTARTPORT..TCPENDPORT:9090..9200
MULTICAST_ADDRESS:MULTICAST_PORT:228.9.224.35:10733 MULTICAST_PACKET_SIZE:65536 MULTICAST_TIME_TO_LIVE: default
FAILURE_DETECT_TCP_RETRANSMIT_TIMEOUT(ms):10000
MAX_PARALLEL:15
START_TIMEOUT(ms):15000 WRITE_TIMEOUT(ms):10000
MAX_WRITE_SELECTOR_POOL_SIZE:30

#]

[#|2012-09-25T10:30:55.131+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-stress : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: dcs-gf05-stress, MemberType: CORE, Address: 10.11.1.237:9177:228.9.171.155:18290:cluster-dcs-stress:dcs-gf05-stress
2: MemberId: dcs-gf06-stress, MemberType: CORE, Address: 10.11.1.238:9126:228.9.171.155:18290:cluster-dcs-stress:dcs-gf06-stress
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9118:228.9.171.155:18290:cluster-dcs-stress:server

#]

[#|2012-09-25T10:30:55.131+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: dcs-gf06-stress of group: cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.131+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: dcs-gf06-stress of group: cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.132+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1024: Adding Join member: dcs-gf05-stress group: cluster-dcs-stress StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.133+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1024: Adding Join member: dcs-gf06-stress group: cluster-dcs-stress StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.136+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-stress : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: dcs-gf05-stress, MemberType: CORE, Address: 10.11.1.237:9177:228.9.171.155:18290:cluster-dcs-stress:dcs-gf05-stress
2: MemberId: dcs-gf06-stress, MemberType: CORE, Address: 10.11.1.238:9126:228.9.171.155:18290:cluster-dcs-stress:dcs-gf06-stress
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9118:228.9.171.155:18290:cluster-dcs-stress:server

#]

[#|2012-09-25T10:30:55.137+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: server of group: cluster-dcs-stress|#]

[#|2012-09-25T10:30:55.145+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=10;_ThreadName=Thread-2;|Grizzly 1.9 NetworkManager|#]

[#|2012-09-25T10:30:55.146+0800|INFO|glassfish3.1.2|grizzly|_ThreadID=14;_ThreadName=Thread-2;|GRIZZLY0001: Starting Grizzly Framework 1.9.46 - 9/25/12 10:30 AM|#]

[#|2012-09-25T10:30:55.157+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Grizzly controller listening on /0.0.0.0:9196. Controller started in 11 ms|#]

[#|2012-09-25T10:30:55.158+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Set via default minimum: MulticastSocket.getTimeToLive()=4|#]

[#|2012-09-25T10:30:55.159+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|MulticastSocket configuration: local socket address: 0.0.0.0/0.0.0.0:10733 network interface: name:null multicast address:/228.9.224.35 timeToLive=4|#]

[#|2012-09-25T10:30:55.166+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|HealthMonitor: heartBeatTimeout(ms)=2000 maxMissedBeats=3 failureDetectionTCPTimeout(ms)=10000 failureDetectionTCPPort=9000|#]

[#|2012-09-25T10:30:55.166+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|starting cluster cluster-dcs-prod for member:server|#]

[#|2012-09-25T10:30:55.167+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1061: MasterNode message listener is registered for member: server group: cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.178+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1005: Member server joined group cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.179+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1004: Started GMS for instance server in group cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.185+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-prod : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9196:228.9.224.35:10733:cluster-dcs-prod:server

#]

[#|2012-09-25T10:30:55.185+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.185+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.186+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=16;_ThreadName=Thread-2;|MySystemAdvertisement(summary): GMSMember name: server group: cluster-dcs-prod memberType: SPECTATOR startTime: Sep 25, 2012 10:30:55 AM HKT ID:10.11.1.207:9196:228.9.224.35:10733:cluster-dcs-prod:server TCP uri(s):[tcp://10.11.1.207:4000]|#]

[#|2012-09-25T10:30:55.187+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=16;_ThreadName=Thread-2;|MySystemAdvertisement(dump)=PEERID[10.11.1.207:9196:228.9.224.35:10733:cluster-dcs-prod:server]
CUSTOMTAGS[GROUP_NAME:cluster-dcs-prod, MEMBER_TYPE:SPECTATOR, START_TIME[10:30:55 AM HKT on Sep 25, 2012]], ENDPONTADDRESSES[[tcp://10.11.1.207:4000]], NAME:server, OSNAME:Linux, OSVERSION:3.0.0-15-server, OSARCH:amd64, HWARCH:amd64, HWVENDOR:Sun Microsystems Inc.|#]

[#|2012-09-25T10:30:55.208+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-prod : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: dcs-gf07-prod, MemberType: CORE, Address: 10.11.1.211:9195:228.9.224.35:10733:cluster-dcs-prod:dcs-gf07-prod
2: MemberId: dcs-gf08-prod, MemberType: CORE, Address: 10.11.1.212:9182:228.9.224.35:10733:cluster-dcs-prod:dcs-gf08-prod
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9196:228.9.224.35:10733:cluster-dcs-prod:server

#]

[#|2012-09-25T10:30:55.208+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: dcs-gf07-prod of group: cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.208+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: dcs-gf07-prod of group: cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.208+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1024: Adding Join member: dcs-gf07-prod group: cluster-dcs-prod StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.209+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1024: Adding Join member: dcs-gf08-prod group: cluster-dcs-prod StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.210+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-prod : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: dcs-gf07-prod, MemberType: CORE, Address: 10.11.1.211:9195:228.9.224.35:10733:cluster-dcs-prod:dcs-gf07-prod
2: MemberId: dcs-gf08-prod, MemberType: CORE, Address: 10.11.1.212:9182:228.9.224.35:10733:cluster-dcs-prod:dcs-gf08-prod
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9196:228.9.224.35:10733:cluster-dcs-prod:server

#]

[#|2012-09-25T10:30:55.211+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: server of group: cluster-dcs-prod|#]

[#|2012-09-25T10:30:55.230+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1095: member: server is joining group: cluster-ccws-prod ...|#]

[#|2012-09-25T10:30:55.235+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|instantiated following NetworkManager implementation:com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyNetworkManager1_9|#]

[#|2012-09-25T10:30:55.235+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS MAX_MESSAGE_LENGTH=4,196,352|#]

[#|2012-09-25T10:30:55.236+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|
GrizzlyNetworkManager1_9 Configuration
BIND_INTERFACE_ADDRESS:null NetworkInterfaceName:null
TCPSTARTPORT..TCPENDPORT:9090..9200
MULTICAST_ADDRESS:MULTICAST_PORT:228.9.75.35:22027 MULTICAST_PACKET_SIZE:65536 MULTICAST_TIME_TO_LIVE: default
FAILURE_DETECT_TCP_RETRANSMIT_TIMEOUT(ms):10000
MAX_PARALLEL:15
START_TIMEOUT(ms):15000 WRITE_TIMEOUT(ms):10000
MAX_WRITE_SELECTOR_POOL_SIZE:30

#]

[#|2012-09-25T10:30:55.236+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=10;_ThreadName=Thread-2;|Grizzly 1.9 NetworkManager|#]

[#|2012-09-25T10:30:55.237+0800|INFO|glassfish3.1.2|grizzly|_ThreadID=17;_ThreadName=Thread-2;|GRIZZLY0001: Starting Grizzly Framework 1.9.46 - 9/25/12 10:30 AM|#]

[#|2012-09-25T10:30:55.253+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Grizzly controller listening on /0.0.0.0:9094. Controller started in 16 ms|#]

[#|2012-09-25T10:30:55.254+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Set via default minimum: MulticastSocket.getTimeToLive()=4|#]

[#|2012-09-25T10:30:55.255+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|MulticastSocket configuration: local socket address: 0.0.0.0/0.0.0.0:22027 network interface: name:null multicast address:/228.9.75.35 timeToLive=4|#]

[#|2012-09-25T10:30:55.257+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|HealthMonitor: heartBeatTimeout(ms)=2000 maxMissedBeats=3 failureDetectionTCPTimeout(ms)=10000 failureDetectionTCPPort=9000|#]

[#|2012-09-25T10:30:55.260+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|starting cluster cluster-ccws-prod for member:server|#]

[#|2012-09-25T10:30:55.260+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1061: MasterNode message listener is registered for member: server group: cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.273+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1005: Member server joined group cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.274+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1004: Started GMS for instance server in group cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.282+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|MySystemAdvertisement(summary): GMSMember name: server group: cluster-ccws-prod memberType: SPECTATOR startTime: Sep 25, 2012 10:30:55 AM HKT ID:10.11.1.207:9094:228.9.75.35:22027:cluster-ccws-prod:server TCP uri(s):[tcp://10.11.1.207:4000]|#]

[#|2012-09-25T10:30:55.282+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|MySystemAdvertisement(dump)=PEERID[10.11.1.207:9094:228.9.75.35:22027:cluster-ccws-prod:server]
CUSTOMTAGS[GROUP_NAME:cluster-ccws-prod, MEMBER_TYPE:SPECTATOR, START_TIME[10:30:55 AM HKT on Sep 25, 2012]], ENDPONTADDRESSES[[tcp://10.11.1.207:4000]], NAME:server, OSNAME:Linux, OSVERSION:3.0.0-15-server, OSARCH:amd64, HWARCH:amd64, HWVENDOR:Sun Microsystems Inc.|#]

[#|2012-09-25T10:30:55.389+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-prod : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9094:228.9.75.35:22027:cluster-ccws-prod:server

#]

[#|2012-09-25T10:30:55.390+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.390+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.401+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-prod : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: ccws-gf01-prod, MemberType: CORE, Address: 10.11.1.208:9128:228.9.75.35:22027:cluster-ccws-prod:ccws-gf01-prod
2: MemberId: ccws-gf02-prod, MemberType: CORE, Address: 10.11.1.210:9145:228.9.75.35:22027:cluster-ccws-prod:ccws-gf02-prod
3: MemberId: ccws-gf03-prod, MemberType: CORE, Address: 10.11.1.213:9118:228.9.75.35:22027:cluster-ccws-prod:ccws-gf03-prod
4: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9094:228.9.75.35:22027:cluster-ccws-prod:server

#]

[#|2012-09-25T10:30:55.401+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: ccws-gf01-prod of group: cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.402+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: ccws-gf01-prod of group: cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.402+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1024: Adding Join member: ccws-gf01-prod group: cluster-ccws-prod StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.402+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1024: Adding Join member: ccws-gf02-prod group: cluster-ccws-prod StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.402+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1024: Adding Join member: ccws-gf03-prod group: cluster-ccws-prod StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.404+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-prod : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: ccws-gf01-prod, MemberType: CORE, Address: 10.11.1.208:9128:228.9.75.35:22027:cluster-ccws-prod:ccws-gf01-prod
2: MemberId: ccws-gf02-prod, MemberType: CORE, Address: 10.11.1.210:9145:228.9.75.35:22027:cluster-ccws-prod:ccws-gf02-prod
3: MemberId: ccws-gf03-prod, MemberType: CORE, Address: 10.11.1.213:9118:228.9.75.35:22027:cluster-ccws-prod:ccws-gf03-prod
4: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9094:228.9.75.35:22027:cluster-ccws-prod:server

#]

[#|2012-09-25T10:30:55.404+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: server of group: cluster-ccws-prod|#]

[#|2012-09-25T10:30:55.407+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1095: member: server is joining group: cluster-ccws-stress ...|#]

[#|2012-09-25T10:30:55.417+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|instantiated following NetworkManager implementation:com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyNetworkManager1_9|#]

[#|2012-09-25T10:30:55.421+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS MAX_MESSAGE_LENGTH=4,196,352|#]

[#|2012-09-25T10:30:55.422+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|
GrizzlyNetworkManager1_9 Configuration
BIND_INTERFACE_ADDRESS:null NetworkInterfaceName:null
TCPSTARTPORT..TCPENDPORT:9090..9200
MULTICAST_ADDRESS:MULTICAST_PORT:228.9.54.166:6369 MULTICAST_PACKET_SIZE:65536 MULTICAST_TIME_TO_LIVE: default
FAILURE_DETECT_TCP_RETRANSMIT_TIMEOUT(ms):10000
MAX_PARALLEL:15
START_TIMEOUT(ms):15000 WRITE_TIMEOUT(ms):10000
MAX_WRITE_SELECTOR_POOL_SIZE:30

#]

[#|2012-09-25T10:30:55.422+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=10;_ThreadName=Thread-2;|Grizzly 1.9 NetworkManager|#]

[#|2012-09-25T10:30:55.426+0800|INFO|glassfish3.1.2|grizzly|_ThreadID=20;_ThreadName=Thread-2;|GRIZZLY0001: Starting Grizzly Framework 1.9.46 - 9/25/12 10:30 AM|#]

[#|2012-09-25T10:30:55.433+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Grizzly controller listening on /0.0.0.0:9153. Controller started in 10 ms|#]

[#|2012-09-25T10:30:55.434+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Set via default minimum: MulticastSocket.getTimeToLive()=4|#]

[#|2012-09-25T10:30:55.435+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|MulticastSocket configuration: local socket address: 0.0.0.0/0.0.0.0:6369 network interface: name:null multicast address:/228.9.54.166 timeToLive=4|#]

[#|2012-09-25T10:30:55.437+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|HealthMonitor: heartBeatTimeout(ms)=2000 maxMissedBeats=3 failureDetectionTCPTimeout(ms)=10000 failureDetectionTCPPort=9000|#]

[#|2012-09-25T10:30:55.439+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|starting cluster cluster-ccws-stress for member:server|#]

[#|2012-09-25T10:30:55.439+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1061: MasterNode message listener is registered for member: server group: cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.442+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1005: Member server joined group cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.442+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1004: Started GMS for instance server in group cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.456+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=21;_ThreadName=Thread-2;|MySystemAdvertisement(summary): GMSMember name: server group: cluster-ccws-stress memberType: SPECTATOR startTime: Sep 25, 2012 10:30:55 AM HKT ID:10.11.1.207:9153:228.9.54.166:6369:cluster-ccws-stress:server TCP uri(s):[tcp://10.11.1.207:4000]|#]

[#|2012-09-25T10:30:55.456+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=21;_ThreadName=Thread-2;|MySystemAdvertisement(dump)=PEERID[10.11.1.207:9153:228.9.54.166:6369:cluster-ccws-stress:server]
CUSTOMTAGS[GROUP_NAME:cluster-ccws-stress, MEMBER_TYPE:SPECTATOR, START_TIME[10:30:55 AM HKT on Sep 25, 2012]], ENDPONTADDRESSES[[tcp://10.11.1.207:4000]], NAME:server, OSNAME:Linux, OSVERSION:3.0.0-15-server, OSARCH:amd64, HWARCH:amd64, HWVENDOR:Sun Microsystems Inc.|#]

[#|2012-09-25T10:30:55.457+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-stress : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9153:228.9.54.166:6369:cluster-ccws-stress:server

#]

[#|2012-09-25T10:30:55.457+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.457+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.468+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1095: member: server is joining group: cluster-cci-prod ...|#]

[#|2012-09-25T10:30:55.484+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-stress : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: ccws-gf02-stress, MemberType: CORE, Address: 10.11.1.210:9164:228.9.54.166:6369:cluster-ccws-stress:ccws-gf02-stress
2: MemberId: ccws-gf03-stress, MemberType: CORE, Address: 10.11.1.213:9160:228.9.54.166:6369:cluster-ccws-stress:ccws-gf03-stress
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9153:228.9.54.166:6369:cluster-ccws-stress:server

#]

[#|2012-09-25T10:30:55.487+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: ccws-gf02-stress of group: cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.487+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: ccws-gf02-stress of group: cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.487+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1024: Adding Join member: ccws-gf02-stress group: cluster-ccws-stress StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.488+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1024: Adding Join member: ccws-gf03-stress group: cluster-ccws-stress StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.489+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-stress : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: ccws-gf02-stress, MemberType: CORE, Address: 10.11.1.210:9164:228.9.54.166:6369:cluster-ccws-stress:ccws-gf02-stress
2: MemberId: ccws-gf03-stress, MemberType: CORE, Address: 10.11.1.213:9160:228.9.54.166:6369:cluster-ccws-stress:ccws-gf03-stress
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9153:228.9.54.166:6369:cluster-ccws-stress:server

#]

[#|2012-09-25T10:30:55.484+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|instantiated following NetworkManager implementation:com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyNetworkManager1_9|#]

[#|2012-09-25T10:30:55.489+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: server of group: cluster-ccws-stress|#]

[#|2012-09-25T10:30:55.490+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS MAX_MESSAGE_LENGTH=4,196,352|#]

[#|2012-09-25T10:30:55.491+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|
GrizzlyNetworkManager1_9 Configuration
BIND_INTERFACE_ADDRESS:null NetworkInterfaceName:null
TCPSTARTPORT..TCPENDPORT:9090..9200
MULTICAST_ADDRESS:MULTICAST_PORT:228.9.47.209:5433 MULTICAST_PACKET_SIZE:65536 MULTICAST_TIME_TO_LIVE: default
FAILURE_DETECT_TCP_RETRANSMIT_TIMEOUT(ms):10000
MAX_PARALLEL:15
START_TIMEOUT(ms):15000 WRITE_TIMEOUT(ms):10000
MAX_WRITE_SELECTOR_POOL_SIZE:30

#]

[#|2012-09-25T10:30:55.491+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=10;_ThreadName=Thread-2;|Grizzly 1.9 NetworkManager|#]

[#|2012-09-25T10:30:55.498+0800|INFO|glassfish3.1.2|grizzly|_ThreadID=23;_ThreadName=Thread-2;|GRIZZLY0001: Starting Grizzly Framework 1.9.46 - 9/25/12 10:30 AM|#]

[#|2012-09-25T10:30:55.506+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Grizzly controller listening on /0.0.0.0:9192. Controller started in 9 ms|#]

[#|2012-09-25T10:30:55.506+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Set via default minimum: MulticastSocket.getTimeToLive()=4|#]

[#|2012-09-25T10:30:55.507+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|MulticastSocket configuration: local socket address: 0.0.0.0/0.0.0.0:5433 network interface: name:null multicast address:/228.9.47.209 timeToLive=4|#]

[#|2012-09-25T10:30:55.509+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|HealthMonitor: heartBeatTimeout(ms)=2000 maxMissedBeats=3 failureDetectionTCPTimeout(ms)=10000 failureDetectionTCPPort=9000|#]

[#|2012-09-25T10:30:55.509+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|starting cluster cluster-cci-prod for member:server|#]

[#|2012-09-25T10:30:55.509+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1061: MasterNode message listener is registered for member: server group: cluster-cci-prod|#]

[#|2012-09-25T10:30:55.515+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1005: Member server joined group cluster-cci-prod|#]

[#|2012-09-25T10:30:55.515+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1004: Started GMS for instance server in group cluster-cci-prod|#]

[#|2012-09-25T10:30:55.520+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-cci-prod : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9192:228.9.47.209:5433:cluster-cci-prod:server

#]

[#|2012-09-25T10:30:55.521+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-cci-prod|#]

[#|2012-09-25T10:30:55.521+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-cci-prod|#]

[#|2012-09-25T10:30:55.526+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=25;_ThreadName=Thread-2;|MySystemAdvertisement(summary): GMSMember name: server group: cluster-cci-prod memberType: SPECTATOR startTime: Sep 25, 2012 10:30:55 AM HKT ID:10.11.1.207:9192:228.9.47.209:5433:cluster-cci-prod:server TCP uri(s):[tcp://10.11.1.207:4000]|#]

[#|2012-09-25T10:30:55.526+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=25;_ThreadName=Thread-2;|MySystemAdvertisement(dump)=PEERID[10.11.1.207:9192:228.9.47.209:5433:cluster-cci-prod:server]
CUSTOMTAGS[GROUP_NAME:cluster-cci-prod, MEMBER_TYPE:SPECTATOR, START_TIME[10:30:55 AM HKT on Sep 25, 2012]], ENDPONTADDRESSES[[tcp://10.11.1.207:4000]], NAME:server, OSNAME:Linux, OSVERSION:3.0.0-15-server, OSARCH:amd64, HWARCH:amd64, HWVENDOR:Sun Microsystems Inc.|#]

[#|2012-09-25T10:30:55.550+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1095: member: server is joining group: cluster-dcs-test ...|#]

[#|2012-09-25T10:30:55.552+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|instantiated following NetworkManager implementation:com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyNetworkManager1_9|#]

[#|2012-09-25T10:30:55.552+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS MAX_MESSAGE_LENGTH=4,196,352|#]

[#|2012-09-25T10:30:55.553+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|
GrizzlyNetworkManager1_9 Configuration
BIND_INTERFACE_ADDRESS:null NetworkInterfaceName:null
TCPSTARTPORT..TCPENDPORT:9090..9200
MULTICAST_ADDRESS:MULTICAST_PORT:228.9.134.222:14372 MULTICAST_PACKET_SIZE:65536 MULTICAST_TIME_TO_LIVE: default
FAILURE_DETECT_TCP_RETRANSMIT_TIMEOUT(ms):10000
MAX_PARALLEL:15
START_TIMEOUT(ms):15000 WRITE_TIMEOUT(ms):10000
MAX_WRITE_SELECTOR_POOL_SIZE:30

#]

[#|2012-09-25T10:30:55.553+0800|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=10;_ThreadName=Thread-2;|Grizzly 1.9 NetworkManager|#]

[#|2012-09-25T10:30:55.554+0800|INFO|glassfish3.1.2|grizzly|_ThreadID=26;_ThreadName=Thread-2;|GRIZZLY0001: Starting Grizzly Framework 1.9.46 - 9/25/12 10:30 AM|#]

[#|2012-09-25T10:30:55.555+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Grizzly controller listening on /0.0.0.0:9198. Controller started in 1 ms|#]

[#|2012-09-25T10:30:55.555+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|Set via default minimum: MulticastSocket.getTimeToLive()=4|#]

[#|2012-09-25T10:30:55.556+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|MulticastSocket configuration: local socket address: 0.0.0.0/0.0.0.0:14372 network interface: name:null multicast address:/228.9.134.222 timeToLive=4|#]

[#|2012-09-25T10:30:55.558+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|HealthMonitor: heartBeatTimeout(ms)=2000 maxMissedBeats=3 failureDetectionTCPTimeout(ms)=10000 failureDetectionTCPPort=9000|#]

[#|2012-09-25T10:30:55.558+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|starting cluster cluster-dcs-test for member:server|#]

[#|2012-09-25T10:30:55.561+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1061: MasterNode message listener is registered for member: server group: cluster-dcs-test|#]

[#|2012-09-25T10:30:55.563+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1005: Member server joined group cluster-dcs-test|#]

[#|2012-09-25T10:30:55.563+0800|INFO|glassfish3.1.2|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=10;_ThreadName=Thread-2;|GMSAD1004: Started GMS for instance server in group cluster-dcs-test|#]

[#|2012-09-25T10:30:55.574+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-test : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9198:228.9.134.222:14372:cluster-dcs-test:server

#]

[#|2012-09-25T10:30:55.574+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-dcs-test|#]

[#|2012-09-25T10:30:55.574+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-dcs-test|#]

[#|2012-09-25T10:30:55.576+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=28;_ThreadName=Thread-2;|MySystemAdvertisement(summary): GMSMember name: server group: cluster-dcs-test memberType: SPECTATOR startTime: Sep 25, 2012 10:30:55 AM HKT ID:10.11.1.207:9198:228.9.134.222:14372:cluster-dcs-test:server TCP uri(s):[tcp://10.11.1.207:4000]|#]

[#|2012-09-25T10:30:55.576+0800|CONFIG|glassfish3.1.2|ShoalLogger|_ThreadID=28;_ThreadName=Thread-2;|MySystemAdvertisement(dump)=PEERID[10.11.1.207:9198:228.9.134.222:14372:cluster-dcs-test:server]
CUSTOMTAGS[GROUP_NAME:cluster-dcs-test, MEMBER_TYPE:SPECTATOR, START_TIME[10:30:55 AM HKT on Sep 25, 2012]], ENDPONTADDRESSES[[tcp://10.11.1.207:4000]], NAME:server, OSNAME:Linux, OSVERSION:3.0.0-15-server, OSARCH:amd64, HWARCH:amd64, HWVENDOR:Sun Microsystems Inc.|#]

[#|2012-09-25T10:30:55.616+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-test : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: dcs-gf01-test, MemberType: CORE, Address: 10.11.1.208:9183:228.9.134.222:14372:cluster-dcs-test:dcs-gf01-test
2: MemberId: dcs-gf02-test, MemberType: CORE, Address: 10.11.1.210:9128:228.9.134.222:14372:cluster-dcs-test:dcs-gf02-test
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9198:228.9.134.222:14372:cluster-dcs-test:server

#]

[#|2012-09-25T10:30:55.616+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: dcs-gf02-test of group: cluster-dcs-test|#]

[#|2012-09-25T10:30:55.616+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: dcs-gf02-test of group: cluster-dcs-test|#]

[#|2012-09-25T10:30:55.617+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1024: Adding Join member: dcs-gf01-test group: cluster-dcs-test StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.617+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1024: Adding Join member: dcs-gf02-test group: cluster-dcs-test StartupState: INSTANCE_STARTUP |#]

[#|2012-09-25T10:30:55.618+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-test : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: dcs-gf01-test, MemberType: CORE, Address: 10.11.1.208:9183:228.9.134.222:14372:cluster-dcs-test:dcs-gf01-test
2: MemberId: dcs-gf02-test, MemberType: CORE, Address: 10.11.1.210:9128:228.9.134.222:14372:cluster-dcs-test:dcs-gf02-test
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9198:228.9.134.222:14372:cluster-dcs-test:server

#]

[#|2012-09-25T10:30:55.618+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: server of group: cluster-dcs-test|#]

[#|2012-09-25T10:30:55.892+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=29;_ThreadName=Thread-2;|Grizzly Framework 1.9.46 started in: 55ms - bound to [0.0.0.0:9090]|#]

[#|2012-09-25T10:30:55.910+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=30;_ThreadName=Thread-2;|Grizzly Framework 1.9.46 started in: 26ms - bound to [0.0.0.0:9191]|#]

[#|2012-09-25T10:30:55.970+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=31;_ThreadName=Thread-2;|Grizzly Framework 1.9.46 started in: 9ms - bound to [0.0.0.0:4949]|#]

[#|2012-09-25T10:30:55.998+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=32;_ThreadName=Thread-2;|Grizzly Framework 1.9.46 started in: 21ms - bound to [0.0.0.0:4700]|#]

[#|2012-09-25T10:30:56.002+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=33;_ThreadName=Thread-2;|Grizzly Framework 1.9.46 started in: 5ms - bound to [0.0.0.0:9696]|#]

[#|2012-09-25T10:30:56.376+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=10;_ThreadName=Thread-2;|The Admin Console is already installed, but not yet loaded.|#]

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

[#|2012-09-25T10:31:00.375+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.ejb.com.sun.ejb.containers|_ThreadID=10;_ThreadName=Thread-2;|Created EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool-size 32 thread-keep-alive-seconds 60 thread-queue-capacity 2147483647 allow-core-thread-timeout false |#]

[#|2012-09-25T10:31:00.449+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=10;_ThreadName=Thread-2;|SEC1002: Security Manager is OFF.|#]

[#|2012-09-25T10:31:00.501+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=10;_ThreadName=Thread-2;|SEC1010: Entering Security Startup Service|#]

[#|2012-09-25T10:31:00.521+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=34;_ThreadName=Thread-2;|GMS1058: Assuming Master Node designation member: server for group: cluster-cci-prod|#]

[#|2012-09-25T10:31:00.521+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-cci-prod : Members in view for MASTER_CHANGE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9192:228.9.47.209:5433:cluster-cci-prod:server

#]

[#|2012-09-25T10:31:00.522+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: MASTER_CHANGE_EVENT for member: server of group: cluster-cci-prod|#]

[#|2012-09-25T10:31:00.522+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1093: adding GroupLeadershipNotification signal leadermember: server of group: cluster-cci-prod|#]

[#|2012-09-25T10:31:00.533+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=34;_ThreadName=Thread-2;|GMS1057: Announcing Master Node designation for member: server of group: cluster-cci-prod. Local view contains 1 entries|#]

[#|2012-09-25T10:31:00.551+0800|INFO|glassfish3.1.2|org.glassfish.flashlight.transformer.ProbeProviderClassFileTransformer|_ThreadID=10;_ThreadName=Thread-2;|Successfully got INSTRUMENTATION: sun.instrument.InstrumentationImpl@4873e835|#]

[#|2012-09-25T10:31:00.598+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=10;_ThreadName=Thread-2;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2012-09-25T10:31:00.727+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=10;_ThreadName=Thread-2;|SEC1115: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2012-09-25T10:31:00.735+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=10;_ThreadName=Thread-2;|SEC1115: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2012-09-25T10:31:00.751+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=10;_ThreadName=Thread-2;|SEC1115: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.|#]

[#|2012-09-25T10:31:00.827+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=10;_ThreadName=Thread-2;|LARAJDBCRealm Version 2012/05/02 19:09|#]

[#|2012-09-25T10:31:00.981+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm|_ThreadID=10;_ThreadName=Thread-2;|SEC1115: Realm [LARADCS] of classtype [com.cmacgm.LaraJdbcRealm] successfully created.|#]

[#|2012-09-25T10:31:01.015+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=10;_ThreadName=Thread-2;|SEC1011: Security Service(s) Started Successfully|#]

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

[#|2012-09-25T10:31:01.688+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=10;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [http-listener-2] on host/port [0.0.0.0:9191]|#]

[#|2012-09-25T10:31:01.711+0800|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=10;_ThreadName=Thread-2;|WEB0169: Created HTTP listener [admin-listener] on host/port [0.0.0.0:4949]|#]

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

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

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

[#|2012-09-25T10:31:04.211+0800|SEVERE|glassfish3.1.2|org.apache.catalina.core.ContainerBase|_ThreadID=10;_ThreadName=Thread-2;|PWC1240: Container StandardEngine[glassfish-web].StandardHost[server].StandardContext[] has not been started
org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5332)
at com.sun.enterprise.web.WebModule.start(WebModule.java:498)
at org.apache.catalina.core.ContainerBase.startChildren(ContainerBase.java:1518)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1184)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:995)
at org.apache.catalina.core.ContainerBase.startChildren(ContainerBase.java:1518)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1184)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:529)
at org.apache.catalina.startup.Embedded.start(Embedded.java:942)
at com.sun.enterprise.web.WebContainer.postConstruct(WebContainer.java:604)
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 org.glassfish.internal.data.EngineInfo.getContainer(EngineInfo.java:93)
at com.sun.enterprise.v3.server.ApplicationLifecycle.startContainers(ApplicationLifecycle.java:956)
at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:666)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)
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:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:97)
at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55)
Caused by: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:88)
at org.glassfish.web.LibrariesTldProvider.postConstruct(LibrariesTldProvider.java:119)
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 org.jvnet.hk2.component.Habitat$5.get(Habitat.java:703)
at java.util.AbstractList$Itr.next(AbstractList.java:345)
at com.sun.enterprise.web.WebModuleListener.configureJsp(WebModuleListener.java:187)
at com.sun.enterprise.web.WebModuleListener.lifecycleEvent(WebModuleListener.java:148)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5329)
... 40 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at java.util.jar.JarFile.<init>(JarFile.java:135)
at java.util.jar.JarFile.<init>(JarFile.java:99)
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:78)
... 53 more

#]

[#|2012-09-25T10:31:06.421+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|CORE10010: Loading application CCWS done in 9,640 ms|#]

[#|2012-09-25T10:31:07.802+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|CORE10010: Loading application CCInvoice_1_0_5 done in 1,377 ms|#]

[#|2012-09-25T10:31:15.894+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|CORE10010: Loading application dcsTest1_0_55_02_JAAS done in 8,090 ms|#]

[#|2012-09-25T10:31:18.114+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|CORE10010: Loading application dcsProd_1_0_60_04_base64_ha_JAAS done in 2,217 ms|#]

[#|2012-09-25T10:31:18.718+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|CORE10010: Loading application arolstreet_cluster-ccws-stress done in 602 ms|#]

[#|2012-09-25T10:31:22.460+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|CORE10010: Loading application dcsStress_1_1_1_641_01_ha_NOJAAS done in 3,740 ms|#]

[#|2012-09-25T10:31:22.468+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=Thread-2;|GlassFish Server Open Source Edition 3.1.2 (23) startup time : Felix (5,673ms), startup services(29,216ms), total(34,889ms)|#]

[#|2012-09-25T10:31:22.469+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1099: GMS:Reporting Joined and Ready state to group: cluster-dcs-stress|#]

[#|2012-09-25T10:31:22.471+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1099: GMS:Reporting Joined and Ready state to group: cluster-dcs-prod|#]

[#|2012-09-25T10:31:22.472+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1099: GMS:Reporting Joined and Ready state to group: cluster-ccws-prod|#]

[#|2012-09-25T10:31:22.474+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-stress : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: dcs-gf05-stress, MemberType: CORE, Address: 10.11.1.237:9177:228.9.171.155:18290:cluster-dcs-stress:dcs-gf05-stress
2: MemberId: dcs-gf06-stress, MemberType: CORE, Address: 10.11.1.238:9126:228.9.171.155:18290:cluster-dcs-stress:dcs-gf06-stress
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9118:228.9.171.155:18290:cluster-dcs-stress:server

#]

[#|2012-09-25T10:31:22.474+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=12;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: JOINED_AND_READY_EVENT for member: server of group: cluster-dcs-stress|#]

[#|2012-09-25T10:31:22.476+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1099: GMS:Reporting Joined and Ready state to group: cluster-ccws-stress|#]

[#|2012-09-25T10:31:22.477+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1099: GMS:Reporting Joined and Ready state to group: cluster-cci-prod|#]

[#|2012-09-25T10:31:22.481+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-prod : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: ccws-gf01-prod, MemberType: CORE, Address: 10.11.1.208:9128:228.9.75.35:22027:cluster-ccws-prod:ccws-gf01-prod
2: MemberId: ccws-gf02-prod, MemberType: CORE, Address: 10.11.1.210:9145:228.9.75.35:22027:cluster-ccws-prod:ccws-gf02-prod
3: MemberId: ccws-gf03-prod, MemberType: CORE, Address: 10.11.1.213:9118:228.9.75.35:22027:cluster-ccws-prod:ccws-gf03-prod
4: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9094:228.9.75.35:22027:cluster-ccws-prod:server

#]

[#|2012-09-25T10:31:22.481+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=19;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: JOINED_AND_READY_EVENT for member: server of group: cluster-ccws-prod|#]

[#|2012-09-25T10:31:22.481+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-ccws-stress : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: ccws-gf02-stress, MemberType: CORE, Address: 10.11.1.210:9164:228.9.54.166:6369:cluster-ccws-stress:ccws-gf02-stress
2: MemberId: ccws-gf03-stress, MemberType: CORE, Address: 10.11.1.213:9160:228.9.54.166:6369:cluster-ccws-stress:ccws-gf03-stress
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9153:228.9.54.166:6369:cluster-ccws-stress:server

#]

[#|2012-09-25T10:31:22.481+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=22;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: JOINED_AND_READY_EVENT for member: server of group: cluster-ccws-stress|#]

[#|2012-09-25T10:31:22.482+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-cci-prod : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9192:228.9.47.209:5433:cluster-cci-prod:server

#]

[#|2012-09-25T10:31:22.482+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=24;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: JOINED_AND_READY_EVENT for member: server of group: cluster-cci-prod|#]

[#|2012-09-25T10:31:22.490+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-prod : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: dcs-gf07-prod, MemberType: CORE, Address: 10.11.1.211:9195:228.9.224.35:10733:cluster-dcs-prod:dcs-gf07-prod
2: MemberId: dcs-gf08-prod, MemberType: CORE, Address: 10.11.1.212:9182:228.9.224.35:10733:cluster-dcs-prod:dcs-gf08-prod
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9196:228.9.224.35:10733:cluster-dcs-prod:server

#]

[#|2012-09-25T10:31:22.490+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=15;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: JOINED_AND_READY_EVENT for member: server of group: cluster-dcs-prod|#]

[#|2012-09-25T10:31:22.484+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=10;_ThreadName=Thread-2;|GMS1099: GMS:Reporting Joined and Ready state to group: cluster-dcs-test|#]

[#|2012-09-25T10:31:22.497+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1092: GMS View Change Received for group: cluster-dcs-test : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: dcs-gf01-test, MemberType: CORE, Address: 10.11.1.208:9183:228.9.134.222:14372:cluster-dcs-test:dcs-gf01-test
2: MemberId: dcs-gf02-test, MemberType: CORE, Address: 10.11.1.210:9128:228.9.134.222:14372:cluster-dcs-test:dcs-gf02-test
3: MemberId: server, MemberType: SPECTATOR, Address: 10.11.1.207:9198:228.9.134.222:14372:cluster-dcs-test:server

#]

[#|2012-09-25T10:31:22.498+0800|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=27;_ThreadName=Thread-2;|GMS1016: Analyzing new membership snapshot received as part of event: JOINED_AND_READY_EVENT for member: server of group: cluster-dcs-test|#]

[#|2012-09-25T10:31:24.009+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=35;_ThreadName=Thread-2;|java.rmi.server.ExportException: Port already in use: 9696; nested exception is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:188)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:100)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:76)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter._startRegistry(RMIConnectorStarter.java:236)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.startRegistry(RMIConnectorStarter.java:217)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.<init>(RMIConnectorStarter.java:152)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.startConnector(JMXStartupService.java:278)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.run(JMXStartupService.java:322)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
at java.net.ServerSocket.bind(ServerSocket.java:328)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at java.net.ServerSocket.<init>(ServerSocket.java:106)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
... 12 more

#]

[#|2012-09-25T10:31:24.032+0800|WARNING|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=35;_ThreadName=Thread-2;|JMX007: Cannot start JMX connector JmxConnector config:

{ name = system, Protocol = rmi_jrmp, Address = 0.0.0.0, Port = 9696, AcceptAll = false, AuthRealmName = admin-realm, SecurityEnabled = false}

having exception java.lang.RuntimeException: Port 9696 is not available for the internal rmi registry. This means that a call was made with the same port, without closing earlier registry instance. This has to do with the system jmx connector configuration in admin-service element of the configuration associated with this instance|#]

[#|2012-09-25T10:31:24.032+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=35;_ThreadName=Thread-2;|java.lang.RuntimeException: Port 9696 is not available for the internal rmi registry. This means that a call was made with the same port, without closing earlier registry instance. This has to do with the system jmx connector configuration in admin-service element of the configuration associated with this instance
at org.glassfish.admin.mbeanserver.RMIConnectorStarter._startRegistry(RMIConnectorStarter.java:240)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.startRegistry(RMIConnectorStarter.java:217)
at org.glassfish.admin.mbeanserver.RMIConnectorStarter.<init>(RMIConnectorStarter.java:152)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.startConnector(JMXStartupService.java:278)
at org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread.run(JMXStartupService.java:322)

#]

[#|2012-09-25T10:31:24.153+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=36;_ThreadName=Thread-2;|The Admin Console is already installed, but not yet loaded.|#]

[#|2012-09-25T10:31:24.158+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=36;_ThreadName=Thread-2;|The Admin Console is starting. Please wait.|#]

[#|2012-09-25T10:31:26.921+0800|SEVERE|glassfish3.1.2|org.apache.catalina.core.ContainerBase|_ThreadID=36;_ThreadName=Thread-2;|ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5332)
at com.sun.enterprise.web.WebModule.start(WebModule.java:498)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:733)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2018)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1669)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThread.java:210)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThread.java:108)
Caused by: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:88)
at org.glassfish.web.LibrariesTldProvider.postConstruct(LibrariesTldProvider.java:119)
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 org.jvnet.hk2.component.Habitat$5.get(Habitat.java:703)
at java.util.AbstractList$Itr.next(AbstractList.java:345)
at com.sun.enterprise.web.WebModuleListener.configureJsp(WebModuleListener.java:187)
at com.sun.enterprise.web.WebModuleListener.lifecycleEvent(WebModuleListener.java:148)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5329)
... 14 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at java.util.jar.JarFile.<init>(JarFile.java:135)
at java.util.jar.JarFile.<init>(JarFile.java:99)
at com.sun.enterprise.util.net.JarURIPattern.getJarEntries(JarURIPattern.java:78)
... 27 more

#]

[#|2012-09-25T10:31:26.931+0800|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=36;_ThreadName=Thread-2;|java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:921)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:733)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2018)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1669)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThread.java:210)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThread.java:108)

#]

[#|2012-09-25T10:31:26.943+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-2;|Exception while invoking class com.sun.enterprise.web.WebApplication start method
java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:138)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThread.java:210)
at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThread.java:108)

#]

[#|2012-09-25T10:31:26.943+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-2;|Exception while loading the app|#]

[#|2012-09-25T10:31:26.960+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=36;_ThreadName=Thread-2;|Exception while loading the app|#]

[#|2012-09-25T10:31:26.966+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=36;_ThreadName=Thread-2;|The Admin Console application is loaded.|#]

[#|2012-09-25T10:32:29.399+0800|INFO|glassfish3.1.2|org.hibernate.validator.util.Version|_ThreadID=37;_ThreadName=Thread-2;|Hibernate Validator 4.2.0.Final|#]

Comment by bernaps [ 25/Sep/12 ]

Since I found only one zip file for the config under glassfish312/glassfish/domains/domain1/config/glassfish1205579867436504600.zip

After testing the zip file to see if it was valid. It was not

unzip -t config/glassfish1205579867436504600.zip

Archive: config/glassfish1205579867436504600.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of config/glassfish1205579867436504600.zip or
config/glassfish1205579867436504600.zip.zip, and cannot find config/glassfish1205579867436504600.zip.ZIP, period.

Somehow this file was created with errors.

Could it be due to out of memory for being started for many months ? Why is this file created ? when we have domain/config/domain.xml ?

Comment by Shing Wai Chan [ 25/Sep/12 ]

Hi bemaps,
The original issue is about having a message to indicate which jar is corrupted.
Your issue is about an unknown zip file.
You may like to file a different issue to track the problem.

Comment by Shing Wai Chan [ 23/Oct/12 ]

add a WARNING message on which jar file has issue
Sending common-util/src/main/java/com/sun/enterprise/util/net/JarURIPattern.java
Adding common-util/src/main/java/com/sun/enterprise/util/net/LocalStrings.properties
Transmitting file data ..
Committed revision 56711.





[GLASSFISH-19067] [Perf] Glassfish performance drops when Fixed HTTP thread pool has much more threads in pool than number of clients Created: 10/Sep/12  Updated: 16/Feb/13  Resolved: 16/Feb/13

Status: Resolved
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0_b49
Fix Version/s: 4.0_b60

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

Linux 2.6.16.46 x86_64


Tags: PSRBUG, grizzly, http-thread-pool, pool, pooling, thread

 Description   

When running a JSP atomic benchmark accessing a simple JSP which creates and maintains a session with hit counter, we found that when http thread pool is configured much larger than number of users accessing it, Glassfish performance drops. The atomic test is run with 5 concurrent users without any think time. Keeping the concurrent users same, as size of thread pool is increased (i.e thread pool min & max values are changed), the performance metric transactions/sec (TPS) obtained from a test is less than that obtained earlier.

Thread pool size TPS
Min Max
50 50 17368 (10x more threads)
25 25 17799 (5x more threads)
15 15 19669 (3x more threads)
10 10 22527 (2x more threads)
5 5 23384 (1x threads)



 Comments   
Comment by deep_singh [ 10/Sep/12 ]

Alexey has asked to try out latest Grizzly 2.3-SNAPSHOT since he has made some changes in Fixed Thread Pool. Following is a snippet from Alexey's email:

"2.3-SNAPSHOT has all the perf. optimizations we applied recently. IMO the most important was to change BlockingQueue implementation in the FixedThreadPool: LinkedTransferQueue -> LinkedBlockingQueue. IMO it was the main source of the scalability problem. W/ LinkedTransferQueue in place Selector threads were spinning too much and consumed much more CPU than needed."

Comment by oleksiys [ 16/Feb/13 ]

fixed





[GLASSFISH-19035] [Perf] Performance degradation when using dynamic http thread pool Created: 23/Aug/12  Updated: 16/Feb/13  Resolved: 16/Feb/13

Status: Resolved
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0_b40
Fix Version/s: 4.0_b60

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

Linux 2.2.16 OEL x64


Tags: HTTP, JSP, PSRBUG, ThreadPool, glassfish

 Description   

Seeing significant performance degradation when using dynamic http thread pool when running a JSP HTTP micro benchmark. The degradation has been traced to a hot ReentrantLock in SyncThreadPool implementation of thread pool. When FixedThreadPool is used, there is significant improvement in performance results compared to dynamic thread pool.

Have tried a patch from Alexey replacing ReentrantLock with a Synchronized block, but that is not yielding much improvement.

The benchmark is a simple war file with 3 JSPs doing HelloWorld, showing current date and maintaining a simple user session with hit count.



 Comments   
Comment by deep_singh [ 16/Nov/12 ]

Re-tried the Synchronized block change in dynamic thread pool on b62 with patch built with latest Grizzly 2.3-beta8 binaries. Found 17% improvement when compared to Reentrant lock and 7% improvement when compared to Glassfish 3.1.2 . This test was done with thread pool size min=1 max=8 on a 4 CPU machine and used JSP POST Reader test with 50 concurrent users.

Comment by oleksiys [ 16/Feb/13 ]

fixed





[GLASSFISH-18982] Seeing SAAJ regressions in GFV4.0 Build 49 dated 08/03/2012 Created: 07/Aug/12  Updated: 31/Oct/12  Resolved: 31/Oct/12

Status: Resolved
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0_b39
Fix Version/s: 4.0_b60

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

ALL Platforms


Attachments: Text File full_runclient_unix.log     Text File full_server.log     Text File runclient_unix.log     Text File server.log    

 Description   

I am getting 8 saaj regressions in latest CTS run with GFV4.0 Build 49 dated 08/03/2012. I will attach the run log and server log.

The regressions are:

[javatest.batch] FAILED........com/sun/ts/tests/saaj/api/javax_xml_soap/SOAPMessage/URLClient.java#setConte
ntDescriptionTest
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/SendVariousMimeAttachments/URLClient.java#SendVario
usMimeAttachmentsSOAP11Te
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/SendVariousMimeAttachments/URLClient.java#SendVario
usMimeAttachmentsSOAP12Te
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/Standalone/Client.java#SASendVariousMimeAttachments
SOAP11Test_from_appclient
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/Standalone/Client.java#SASendVariousMimeAttachments
SOAP11Test_from_jsp
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/Standalone/Client.java#SASendVariousMimeAttachments
SOAP12Test_from_appclient
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/Standalone/Client.java#SASendVariousMimeAttachments
SOAP12Test_from_jsp
[javatest.batch] FAILED........com/sun/ts/tests/saaj/ee/Standalone/Client.java#SASendVariousMimeAttachments
SOAP12Test_from_servlet



 Comments   
Comment by Ryan Lubke [ 29/Oct/12 ]

To save time:

Caused by: org.glassfish.grizzly.PendingWriteQueueLimitExceededException: Max queued data limit exceeded: 114760>100872
at org.glassfish.grizzly.nio.AbstractNIOAsyncQueueWriter.checkQueueSize(AbstractNIOAsyncQueueWriter.java:620)
at org.glassfish.grizzly.nio.AbstractNIOAsyncQueueWriter.writeQueueRecord(AbstractNIOAsyncQueueWriter.java:280)
at org.glassfish.grizzly.nio.AbstractNIOAsyncQueueWriter.write(AbstractNIOAsyncQueueWriter.java:219)
at org.glassfish.grizzly.nio.transport.TCPNIOTransportFilter.handleWrite(TCPNIOTransportFilter.java:127)
at org.glassfish.grizzly.filterchain.TransportFilter.handleWrite(TransportFilter.java:191)
at org.glassfish.grizzly.filterchain.ExecutorResolver$8.execute(ExecutorResolver.java:111)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:265)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:200)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:134)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:112)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:78)
at org.glassfish.grizzly.filterchain.FilterChainContext.write(FilterChainContext.java:652)
at org.glassfish.grizzly.http.server.io.OutputBuffer.writeContentBuffer0(OutputBuffer.java:867)
at org.glassfish.grizzly.http.server.io.OutputBuffer.write(OutputBuffer.java:602)
at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:351)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:338)
at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:161)
at javax.activation.DataHandler.writeTo(DataHandler.java:309)
at com.sun.xml.messaging.saaj.packaging.mime.internet.MimeBodyPart.writeTo(MimeBodyPart.java:976)
at com.sun.xml.messaging.saaj.packaging.mime.internet.MimeMultipart.writeTo(MimeMultipart.java:292)
at com.sun.xml.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1337)

Comment by Ryan Lubke [ 29/Oct/12 ]

Is this still an issue with the current weekly promoted builds?

Comment by Lukas Jungmann [ 31/Oct/12 ]

no, I believe this is fixed, I'm not seeing any failures (related to this issue) in test job

Comment by oleksiys [ 31/Oct/12 ]

fixed





[GLASSFISH-12033] DYREC-007: progress status implementation Created: 25/May/10  Updated: 13/Dec/12  Due: 15/Aug/11  Resolved: 13/Dec/12

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

Type: New Feature Priority: Blocker
Reporter: Tom Mueller Assignee: martin.mares
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-12032 DYREC-007: progress status design Resolved
blocks GLASSFISH-16536 provide infrastructure to display pro... Open
Duplicate
is duplicated by GLASSFISH-16940 all output buffered until commond com... Resolved
is duplicated by GLASSFISH-16941 poor feedback for start-cluster command Resolved
Issuezilla Id: 12,033

 Description   

See: http://wiki.glassfish.java.net/Wiki.jsp?page=ClusterDynamicReconfig

This feature is to provide a mechanism to get progress status for long running
operations (ex. deploy). This issue is for the implementation of the feature.



 Comments   
Comment by vijaysr [ 08/Jun/10 ]

Since some resources were moved out, this feature has been given a lower priority. This may be dropped
from 3.1 itself - not decided as yet.

Comment by Alexis MP [ 29/Jun/10 ]

cc

Comment by vijaysr [ 03/Aug/10 ]

Dropped for 3.1

Comment by vijaysr [ 28/Oct/10 ]

Transferring requested / planned enhancements for 3.2 to Tom to be reassigned to appropriate engineers
later

Comment by Tom Mueller [ 06/Apr/11 ]

Must have for 3.2.

Comment by Tom Mueller [ 05/Jul/11 ]

The implementation of this progress framework should also include changes to the start-instance and start-cluster commands to use it.





[GLASSFISH-7948] deploy command should fail when retrieve option is given for webmodule deployment Created: 21/Apr/09  Updated: 26/Oct/12  Resolved: 26/Oct/12

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

Type: Improvement Priority: Major
Reporter: sankarpn Assignee: Jeremy_Lv
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Related
is related to GLASSFISH-18929 Executing "get-client-stubs" commands... Resolved
Issuezilla Id: 7,948

 Description   

asadmin deploy --virtualservers server --contextroot test --force=true
--precompilejsp=true --verify=true --upload=true --retrieve
/usr/sankar/ws/v3/appserver-sqe/pe/admincli/tonga/results.pe.developer/root.SunOS.sparc/deploy_undeploy_01
--enabled=true
/usr/sankar/ws/v3/appserver-sqe/common/admincli/apps/helloworld/assemble/helloworld-web.war
File download results

Command deploy executed successfully.



 Comments   
Comment by Hong Zhang [ 22/Apr/09 ]

I don't think we should fail deployment in this case. We can probably print out
a warning to tell user this option is not applicable though.

Comment by Hong Zhang [ 21/Jan/11 ]

assign to Tim to further evaluate this RFE

Comment by Tim Quinn [ 21/Jan/11 ]

The handling of downloadable artifacts - which are delivered to the client during --retrieve - is quite generic currently and does not at all depend on the type of module being deployed. This is intentional so new module types can come along in the future and be supported without requiring changes to the general framework. This applies both to the server code and to the code in asadmin which must handle any downloaded artifacts and deposit them on the client system.

Currently, if none of the modules that make up the deployed app register any downloadable artifacts then none are actually delivered. And GlassFish 3.1 currently does not display the "File download results" message. So specifying

asadmin deploy --retrieve localdir /Users/Tim/asgroup/v3/v2/appserv-tests/devtests/deployment/build/servletonly.war

produces

Application deployed with name servletonly.
Command deploy executed successfully.

I suppose we could enhance the deployment (and the related get-client-stubs) logic to add a warning to the action report if the user requested --retrieve but the app has no downloadable artifacts. I am not sure how much value this would be; even without such a warning the user would be able to see directly that the specified directory does not contain any new files after the "deploy --retrieve" or "get-client-stubs" had finished if the app did not have any downloadable artifacts to begin with.

Comment by Hong Zhang [ 26/Oct/12 ]

This is now resolved as part of the fix to issue 18929.





[GLASSFISH-597] JoinColumns is mandatory for using composite FK Created: 24/Apr/06  Updated: 01/Nov/12  Resolved: 01/Nov/12

Status: Closed
Project: glassfish
Component/s: entity-persistence
Affects Version/s: 9.0pe
Fix Version/s: 4.0_b60

Type: Improvement Priority: Major
Reporter: Sanjeeb Sahoo Assignee: tware
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive issue_597.zip    
Issuezilla Id: 597

 Description   

It appears to me that TopLink Essential requires JoinColumns to be set when
there is a composite FK. I don't see this being mentioned in the spec. Can the
default join column names not be calculated for such a case? In the attached
test case, the entities are defined like this:

@Entity
@IdClass(EventPK.class)
public class Event implements java.io.Serializable {

@Id String notificationId;

@Id String discriminatorValue = this.getClass().getSimpleName();
}

@Entity
@IdClass(EventPK.class)
public class Alarm implements java.io.Serializable {

@Id String notificationId;

@Id String discriminatorValue = this.getClass().getSimpleName();

@OneToOne Event event;

}

When I run this, I get the exception:
Exception Description: The @JoinColumns on the annotated element [Event
Alarm.event] from the entity class [class Alarm] is incomplete. When the source
entity class uses a composite primary key, a @JoinColumn must be specified for
each join column using the @JoinColumns. Both the name and the
referenceColumnName elements must be specified in each such @JoinColumn.

The same exception appears even when I run verifier.



 Comments   
Comment by Sanjeeb Sahoo [ 24/Apr/06 ]

Created an attachment (id=232)
test case along with README

Comment by gyorke [ 24/Apr/06 ]

In the case of a Class using a Composite PK any references to that class would
default to referencing that PK making any reference a composite FK having
multiple join columns. The specification states, “If there is more than one
join column, a JoinColumn annotation must be specified for each join column
using the JoinColumns annotation. Both the name and the referencedColumnName
elements must be specified in each such JoinColumn annotation.� (Section 9.1.6)

As such, users are required to specify the @JoinColumns annotation or similar XML.

Comment by Sanjeeb Sahoo [ 24/Apr/06 ]

Gordon,

Yes, I have read that section. The spec is not clear, because I don't see such
text in section #2.1.8. Raise it to EG if you think that is more appropriate. If
the spec says the same thing in more than one place, then it needs to
consistent. More over, can you kindly justify why the default JoinColumn names
can not be computed by a provider? For your kind information, Hibernate defaults
the right column names for me. I would like to know the rational for asking user
to supply some value which can be calculated. In one hand, TopLink Essential
automatically adds missing relationship annotations (e.g.) @OneToOne etc (see
GLASSFISH-555), on the other hand it requires user to supply default join column
names! Why?

Thanks,
Sahoo

Comment by marina vatkina [ 24/Apr/06 ]

It really seems an oversight of the spec, because in @JoinTable (9.1.25) both,
joinColumns and inverseJoinColumns are optional, i.e. expect the provider to
figure this out for more than 1 column.

-marina

Comment by gyorke [ 25/Apr/06 ]

Marina,
@JoinColumns is optional in @JoinTable otherwise every usage of @JoinTable
would require @JoinColumns even for a single, defaultable, join column. The
default, in the case of no JoinColumns, clearly states that the default for
@JoinColumn should be used. “The same defaults as for JoinColumn.� (section
9.1.25) which would result in a single JoinColumn being defined. “If no
JoinColumn annotation is specified, a single join column is assumed and the
default values described below apply.� (Section 9.1.6) . As such, the provided
would not be allowed to default to @JoinColumns in this case.

--Gordon

Comment by gyorke [ 25/Apr/06 ]

Sahoo,
You were quite adamant that we not calculate values beyond what is required
by the specification in GLASSFISH-555. Why the change of opinion? The specification
talks about a single join column in section 2.1.8 not a Composite FK. The
specification wording is quite clear in section 9.1.6 with respect to the
requirement of a @JoinColumns annotation. If you are now of the opinion that
TopLink should go beyond the specification and provide extended functionality
then let us mark this bug as an enhancement request.

--Gordon

Comment by Sanjeeb Sahoo [ 25/Apr/06 ]

Gordon,

Can you explain the rational behind mandating use of @JoinColumns? I firmly
believe, it can be computed by a provider and hence should not be mandated. More
over, the two sections in the spec contradict. Issue #555 is different in the
sense that a provider can not always determine the right value. So the spec
requires it to be explicitly specified. Is this the case for @JoinColumns?

Sahoo

Comment by gyorke [ 25/Apr/06 ]

Sahoo,
The reason you considered GLASSFISH-555 a bug is the same reason this issue is
not a bug. TopLink can always default a OneToOne relationship. TopLink can
always default a ToMany relationship where generic collections are used and
GLASSFISH-555 was filed because we chose to do that defaulting. In the case of
@JoinColumns (composite FKs) the provider can only default the @JoinColumn
annotation in its entirety. If a user specifies a partial @JoinColumn, no
referencedColumnName, then the provider can not determine which target column
the custom FK name should reference and what other FK names should be defaulted
and mapped to. The provider can not always calculate defaults for composite FKs.
However, whether the provider can calculate the @JoinColumns or not is a
non-issue. Sections 2.1.8 and 9.1.6 do not contradict each other they
compliment each other. 2.1.8 talks about defaulting a non-composite FK and 9.1.6
talks about how to specify a composite FK making this issue “not a bug�.
TopLink has always highly valued the user experience and I believe that in
the cases where we can calculate @JoinColumns we should. So this issue should
be an enhancement request and GLASSFISH-555 should be marked "invalid"
--Gordon

Comment by Sanjeeb Sahoo [ 25/Apr/06 ]

Gordon,

How can TopLink safely decide whether a relationship is bidirectional? How can
TopLink decide whether a relationship is ManyToMany?

I understand the need to disallow a partial JoinColumns. But when user has not
placed JoinColumns at all, why can't provider calculate the default value? I
like to read the spec in black and white. Where does the spec says that 2.1.8 is
only applicable for non-composite FK.

Sahoo

Comment by gyorke [ 25/Apr/06 ]

Sahoo,
For GLASSFISH-555 TopLink does not need to 'decide' on the nature of a
relationship. TopLink simply defaults undefined relationships as
uni-directional mappings either OneToMany or OneToOne.
As for this bug I do not believe we are in disagreement on if TopLink can
calculate @JoinColumns in certain circumstances only on the nature of this bug
report.
If you are reading the spec in "black and white" where does it mention
composite FKs or multiple join columns(other than the JoinTable reference) in
section 2.1.8?
--Gordon

Comment by Sanjeeb Sahoo [ 25/Apr/06 ]

Section #2.1.8 says the following:
"This section defines the mapping defaults that apply to the use of the
OneToOne, OneToMany,ManyToOne, and ManyToMany relationship modeling annotations."

Where does it say that it is only applicable for entities with simple PK?

Sahoo

Comment by Mitesh Meswani [ 01/Nov/12 ]

Marking as fixed. As per Peter, in EclipseLink, the following example will now work without specifying a JoinColumn:


@Entity

@IdClass(EmpPK.class)
public class Employee implements java.io.Serializable {

@Id String Id1;

@Id String id2;
}

@Entity
public class Address implements java.io.Serializable {
...
...
@OneToOne Employee employee;

}





Generated at Mon May 25 07:49:36 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.