Author Topic: Run the benchmark failed  (Read 19708 times)

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #30 on: November 04, 2015, 03:25:37 PM »
last test debug info...

lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: Run the benchmark failed
« Reply #31 on: November 04, 2015, 03:30:03 PM »
Congratulations, your short test ran. Ignore the findDerbyClient errors.

Is your appserver still set to 32 GB or memory? If so, set appserver to have 2 VCPUs and 8 GB memory, set NUM_WORKOADS=1, and rerun to make sure appserver is still good. If that's good, then set NUM_WORKLOADS=4 and run a short test.

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #32 on: November 04, 2015, 04:16:38 PM »
appserver is 2 VCPUs and 8G memory now.

[root@appserver bin]# cat /proc/cpuinfo |grep ^processor
processor       : 0
processor       : 1
[root@appserver bin]# free -m
             total       used       free     shared    buffers     cached
Mem:          7873       7137        736          0         29        262
-/+ buffers/cache:       6845       1028
Swap:         4999          0       4999
[root@appserver bin]#

last test result

lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: Run the benchmark failed
« Reply #33 on: November 04, 2015, 04:18:28 PM »
Go ahead and set NUM_WORKLOADS=4 and run a short test. If that looks good, run a long one.

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #34 on: November 04, 2015, 05:09:03 PM »
fail NUM_WORKLOAD=4 short test

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #35 on: November 04, 2015, 05:48:37 PM »
Find out a problem? Could you solve?

lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: Run the benchmark failed
« Reply #36 on: November 04, 2015, 05:52:07 PM »
I think it's a tuning problem. I'm asking the experts - hold please.

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #37 on: November 04, 2015, 06:36:48 PM »
appserver set 4cpu 16G memory , run NUM_WORKLOADS=4 done.
why can not set appserver 4cpu 16G ?


lroderic

  • Moderator
  • Full Member
  • *****
  • Posts: 167
  • Karma: +6/-0
Re: Run the benchmark failed
« Reply #38 on: November 05, 2015, 12:45:35 PM »
Please post the GlassFish server.log file.

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #39 on: November 05, 2015, 05:46:32 PM »
glassfish log

AnoopGupta

  • Jr. Member
  • **
  • Posts: 60
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #40 on: November 05, 2015, 05:49:31 PM »
We need to see the server.log after you see any Null Pointer exceptions or your run fails.
The server.log you attached is right after restarting GlassFish, so I don't see any errors.

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #41 on: November 05, 2015, 05:58:03 PM »
ok, I run test again.

AnoopGupta

  • Jr. Member
  • **
  • Posts: 60
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #42 on: November 05, 2015, 06:24:57 PM »
When you run, please check for your max network usage during the run, especially when you get errors in the client logs.
If there is network tuning or bandwidth issue, the 1098 client may show Null pointer exceptions.

Also, try after reload / restore your database.

onlyloveu2

  • Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #43 on: November 06, 2015, 10:23:17 AM »
After reload dbserver database, run test result.

AnoopGupta

  • Jr. Member
  • **
  • Posts: 60
  • Karma: +0/-0
Re: Run the benchmark failed
« Reply #44 on: November 06, 2015, 11:35:27 AM »
Glassfish server.log shows:

java.sql.SQLException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.


Check the max-pool-size and max-wait-time tunings in GlassFish domain.xml. You may have to increase and try. Please compare with domain.xml from a recent SPECvirt_sc2013 result that used GlassFish to determine which tunings you may need.