Closed glassfishrobot closed 15 years ago
glassfishrobot
commented
6 years ago glassfishrobot
commented
15 years ago @glassfishrobot Commented mm110999 said: Ming,
[echo] org.glassfish.appclient.client.acc.UserError: ACC003: No app client in the app client group jar:/C:/v3/appserver-sqe/build/pe/x86_ENGSVC3_Windows_NT /ejb-cmp/archive/ejb-cmp-datatypesAppClient.jar matches the main class name "null" or the app client name "ejb-cmp-datatypesClient";
Above looks like to be the root cause to me. Can you please check everything was ok at build stage of the test.
Tim, Assigning it to you as Ming reported a success on Unix for the same test.
glassfishrobot
commented
15 years ago @glassfishrobot Commented sherryshen said: cc
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: This is strange. The error message which the ACC displayed should result only if the application contains at least two app clients and the appclient command did not choose one. Further, the choices the ACC displays in the error message are weird. One looks like a legitimate client, but the other one is based on one of the client-related JARs generated during deployment.
Similar confusion seems to be occurring on the server side, because there are log messages about stopping Java Web Start services for two clients. The second one looks like it is from a generated JAR file.
Have you seen this error more than once? It almost looks as if the test was restarted partway through, as if the downloaded JAR from one run was included in the EAR that was built for the next run.
Can you retry the test and see if something like this might be going on?
glassfishrobot
commented
15 years ago @glassfishrobot Commented mzh777 said: Thread dump from appclient: C:\v3\appserver-sqe\pe\ejb\ejb30\persistence\pkgClientJar>appclient -client C:\v 3\appserver-sqe/build/pe/x86_ENGSVC3_Windows_NT/ejb-cmp/archive/ejb-cmp-datatype sAppClient.jar -name ejb-cmp-datatypesClient -textauth -user j2ee -password j2ee EJB3-EAR-pkgClientJar Oct 30, 2009 3:54:32 PM org.glassfish.appclient.client.acc.FacadeLaunchable sele ctFacadeFromGroup WARNING: appclient.singleNestedClientNoMatch WS HOME appserver-sqe Oct 30, 2009 3:54:39 PM com.sun.enterprise.transaction.JavaEETransactionManagerS implified initDelegates INFO: Using com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelega te as the delegate 2009-10-30 15:55:35 Full thread dump Java HotSpot(TM) Client VM (14.2-b01 mixed mode):
"SelectorThread" daemon prio=6 tid=0x0bcff800 nid=0xe8 runnable [0x0ce4f000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method) at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.j ava:274) at sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelector Impl.java:256) at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:137)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
"transaction-manager" daemon prio=6 tid=0x0bc6a800 nid=0xe24 in Object.wait() [0 x0bdff000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method)
"Attach Listener" daemon prio=10 tid=0x0b101000 nid=0x1250 runnable [0x00000000]
java.lang.Thread.State: RUNNABLE
"Signal Dispatcher" daemon prio=10 tid=0x0b10b800 nid=0x1a04 waiting on conditio n [0x00000000] java.lang.Thread.State: RUNNABLE
"Finalizer" daemon prio=8 tid=0x0acec800 nid=0x1bf4 in Object.wait() [0x0ae5f000 ] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method)
"Reference Handler" daemon prio=10 tid=0x0ace8000 nid=0x12d8 in Object.wait() [0 x0ae0f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method)
"main" prio=6 tid=0x003b8c00 nid=0x1e6c waiting on condition [0x00a0e000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method)
"VM Thread" prio=10 tid=0x0ace4000 nid=0x1ef8 runnable
JNI global references: 50
Heap def new generation total 2048K, used 653K [0x02bd0000, 0x02e00000, 0x030b0000 ) eden space 1856K, 35% used [0x02bd0000, 0x02c73508, 0x02da0000) from space 192K, 0% used [0x02da0000, 0x02da0000, 0x02dd0000) to space 192K, 0% used [0x02dd0000, 0x02dd0000, 0x02e00000) tenured generation total 26412K, used 15846K [0x030b0000, 0x04a7b000, 0x06bd0 000) the space 26412K, 59% used [0x030b0000, 0x04029878, 0x04029a00, 0x04a7b000) compacting perm gen total 21760K, used 21674K [0x06bd0000, 0x08110000, 0x0abd0 000) the space 21760K, 99% used [0x06bd0000, 0x080fabd8, 0x080fac00, 0x08110000) No shared spaces configured.
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: Some further updates...
I tried this test on a Windows system using b71. To see what happens more closely I used ant to run the clean, build, setup, deploy, and run steps separately. That way the client was able to launch correctly but it stalled. I connected into Ming's system and we tried the same thing and saw the same results...with the thread dump that Ming posted recently.
The last test Ming and I did on his system was to use "ant all" and THEN we could see the original problem. I am going to try that on my system to see if I can recreate that behavior. But separate from that we seem to have another problem once the client starts. It looks like an ORB issue but it's not clear yet.
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: OK, I see what's happening with the original problem Ming reported.
In the test, the 'clean' step is done at the end of 'ant all.' If by some chance you stop the test in the middle, or run the individual steps without running clean, then if you build the app again the build.xml packages the generated app client JAR file in with the real JAR. This leads to the problem Ming originally reported, in which the ACC complains because there are two clients in the EAR now and the information on the appclient command does not select one of them.
I'd suggest moving the clean to the beginning of the "ant all" sequence, or perhaps even as a prerequisite to the "build" step to avoid this.
Now with that out of the way it looks as if we're facing an ORB problem, because the client hangs (with the thread dump Ming provided). I'll attach a jstack dump from the server in a moment. I'm also transferring this to the ORB folks and adding to the summary to reflect the apparent ORB hang.
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: Created an attachment (id=3703) jstack output from the server during the hang
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: reassigning
glassfishrobot
commented
15 years ago @glassfishrobot Commented kcavanaugh said: This should be fixed with the latest ORB integration (b032, integrated around 14:40 PST 10/30/09). The stack trace is the same as in issue 10581.
glassfishrobot
commented
15 years ago @glassfishrobot Commented sherryshen said: glassfish-v3-b71-11_01_2009.zip Tests failed with similar error, runMyClient-common: [echo] Executing appclient at C:\hudson\workspace\ming-ejb-win-dbg\label\asqe-xeon-4.sfbay.sun.com\appserver-sqe\pe\ejb\ejb30\persistence\pkgClientJar [exec] Result: 1 [echo] Nov 1, 2009 8:09:03 AM org.glassfish.appclient.client.acc.FacadeLaunchable selectFacadeFromGroup [echo] WARNING: appclient.singleNestedClientNoMatch [echo] WS HOME appserver-sqe [echo] java.lang.RuntimeException: Could not resolve a persistence unit corresponding to the persistence-unit-ref-name [ejb30.persistence.datatypes.client.Client/emf] in scope of the module called []. Please verify your application. [echo] at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUsViaPURefs(BundleDescriptor.java:653) [echo] at com.sun.enterprise.deployment.ApplicationClientDescriptor.findReferencedPUs(ApplicationClientDescriptor.java:728) [echo] at org.glassfish.appclient.client.acc.AppClientContainer.completePreparation(AppClientContainer.java:365) [echo] at org.glassfish.appclient.client.acc.AppClientContainer.prepare(AppClientContainer.java:311) [echo] at org.glassfish.appclient.client.AppClientFacade.prepareACC(AppClientFacade.java:261) [echo] at org.glassfish.appclient.client.acc.agent.AppClientContainerAgent.premain(AppClientContainerAgent.java:75) [echo] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [echo] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [echo] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [echo] at java.lang.reflect.Method.invoke(Method.java:597) [echo] at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323) [echo] at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
Please see client output and server.log in http://sqe-hudson.sfbay.sun.com:8080/hudson/job/ming-ejb-win-dbg/label=asqe-xeon-4.sfbay.sun.com/1/ Reopen the bug.
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: The error you saw seems not to be an ORB issue so I'm reassigning this as an app client issue, but ...
I just downloaded the Nov. 1 build 71 and this test ran fine on Windows for me.
Can you please retry, making sure to run clean before build? (Ming ran into some problems last week when the EAR was created incorrectly because some left-over files in the build directory were added to the EAR.)
runMyClient-common:
[echo] Executing appclient at
C:\tim\asgroup\sqe\appserver-sqe\pe\ejb\ejb30\persistence\pkgClientJar
[echo] Nov 1, 2009 11:27:10 AM
org.glassfish.appclient.client.acc.FacadeLaunchable selectFacadeFromGroup
[echo] WARNING: appclient.singleNestedClientNoMatch
[echo] WS HOME appserver-sqe
[echo] Nov 1, 2009 11:27:18 AM
com.sun.enterprise.transaction.JavaEETransactionManagerSimplified initDelegates
[echo] INFO: Using
com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the
delegate
[echo] Nov 1, 2009 11:27:27 AM org.hibernate.validator.util.Version
glassfishrobot
commented
15 years ago @glassfishrobot Commented @tjquinno said: Ming has also confirmed that b71 from Nov. 1 works for him on the failing test (as it passed for me also).
So I'm closing this. Sherry, please let's reopen it if you discover further failures.
glassfishrobot
commented
15 years ago @glassfishrobot Commented File: server.txt Attached By: @tjquinno
glassfishrobot
commented
7 years ago @glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-10707
glassfishrobot
commented
15 years ago @glassfishrobot Commented Reported by mzh777
glassfishrobot
commented
15 years ago @glassfishrobot Commented Marked as fixed on Monday, November 2nd 2009, 5:08:53 am
B70 promoted build.
The pkaClientJar test passed on Unix but failed on windows. On client side: runMyClient-common: [echo] Executing appclient at C:\v3\appserver-sqe\pe\ejb\ejb30\persistence\pkgClientJar [exec] Result: 1 [echo] org.glassfish.appclient.client.acc.UserError: ACC003: No app client in the app client group jar:/C:/v3/appserver-sqe/build/pe/x86_ENGSVC3_Windows_NT /ejb-cmp/archive/ejb-cmp-datatypesAppClient.jar matches the main class name "null" or the app client name "ejb-cmp-datatypesClient"; [echo] Please choose one using -mainclass [ejb30.persistence.datatypes.client.Client, org.glassfish.appclient.client.AppClientGroupFacade] or -name [ejb-cmp-datatypes-client, ejb-cmp-datatypesAppClient]
On server side: [#|2009-10-30T11:49:27.546-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=24;_ThreadName=Thread-1;|ejb-cmp-datatypesApp was successfully deployed in 2,140 milliseconds.|#]
[#|2009-10-30T11:49:32.437-0700|INFO|glassfish|javax.enterprise.system.container.appclient.org.glassfish.appclient.server.core|_ThreadID=25;_ThreadName=Thread-1;|ACDEPL104: Java Web Start services stopped for the app client ejb-cmp-datatypesApp/ejb-cmp-datatypes-client.jar|#]
[#|2009-10-30T11:49:32.437-0700|FINEST|glassfish|org.eclipse.persistence.session.file:/C:/v3/glassfishv3/glassfish/domains/domain1/applications/ejb-cmp-datatypesApp/ejb-cmp-datatypes-client_jar/-em.properties|_ThreadID=25;_ThreadName=Thread-1;ClassName=null;MethodName=null;|Begin undeploying Persistence Unit em; state Predeployed; factoryCount 1|#]
[#|2009-10-30T11:49:32.437-0700|FINEST|glassfish|org.eclipse.persistence.session.file:/C:/v3/glassfishv3/glassfish/domains/domain1/applications/ejb-cmp-datatypesApp/ejb-cmp-datatypes-client_jar/-em.properties|_ThreadID=25;_ThreadName=Thread-1;ClassName=null;MethodName=null;|End undeploying Persistence Unit em; state Undeployed; factoryCount 0|#]
[#|2009-10-30T11:49:32.437-0700|INFO|glassfish|javax.enterprise.system.container.appclient.org.glassfish.appclient.server.core|_ThreadID=25;_ThreadName=Thread-1;|ACDEPL104: Java Web Start services stopped for the app client ejb-cmp-datatypesApp/ejb-cmp-datatypesAppClient.jar|#]
[#|2009-10-30T12:03:25.671-0700|INFO|glassfish|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin|_ThreadID=26;_ThreadName=Thread-1;|Server shutdown initiated|#]
[#|2009-10-30T12:03:25.671-0700|INFO|glassfish|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service|_ThreadID=26;_ThreadName=Thread-1;|RAR7094: __ds_jdbc_ra shutdown successful.|#]
[#|2009-10-30T12:03:28.765-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=26;_ThreadName=Thread-1;|JMXStartupService: shutting down AMX and JMX|#]
[#|2009-10-30T12:03:28.765-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=26;_ThreadName=Thread-1;|JMXStartupService: Stopped JMXConnectorServer: service:jmx:rmi://engsvc3.SFBay.Sun.COM:8686/jndi/rmi://engsvc3.SFBay.Sun.COM:8686/jmxrmi|#]
[#|2009-10-30T12:03:28.765-0700|INFO|glassfish|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=26;_ThreadName=Thread-1;|Shutdown procedure finished|#]
Environment
Operating System: Windows XP Platform: All
Affected Versions
[V3]