SPEC Community

Product Support => SPECvirt_sc2013 => Topic started by: Miles on May 31, 2017, 04:37:30 AM

Title: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on May 31, 2017, 04:37:30 AM
I have put postgresql-9.2-1004.jdbc4.jar in /opt and follow Example VM Setup Guide V1.03 and find some errors as below.

[root@dbserver other_scripts]# ./loaddb_postgres.sh
Script started Wed May 31 15:28:28 CST 2017
sleep 10
Starting Database Load
Loading database with orders_injection_rate = 500
Loading database with numThreads  = 4
Loading Databases ...
INFO : IR supplied : 500
INFO : stepped IR  : 500
java.lang.ClassNotFoundException: org.postgresql.Driver
   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:190)
   at org.spec.jappserver.load.DatabaseConnection.getConnection(DatabaseConnection.java:201)
   at org.spec.jappserver.load.LoadCorp.main(LoadCorp.java:114)
   at org.spec.jappserver.load.LoadAll.main(LoadAll.java:51)
Exception in thread "main" java.lang.RuntimeException: Failed to load Corp domain properlyorg.postgresql.Driver
   at org.spec.jappserver.load.LoadAll.main(LoadAll.java:55)
Ignoring read() errors...
Ignoring read() errors...
Ignoring read() errors...
Launcher: done waiting.
Finished Database Load
Script ended Wed May 31 15:28:38 CST 2017

Does it mean that I miss any package?
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: abond on May 31, 2017, 11:47:07 AM
Have you verified that the database is up and accessible?  You could try to connect to it via a standalone client utility like psql. 
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: AnoopGupta on June 06, 2017, 06:50:35 PM
Hello Miles,

ClassNotFound exception suggests that the loader is unable to locate the jdbc jar file you have under /opt.

Please check your jdbc jar name and location specified in /opt/SPECjAppServer2004/config/glassfish.env and update it to point to your /opt/postgresql-9.2-1004.jdbc4.jar

If you continue to see this issue, please attach your glassfish.env file, as well as output of the following command:
jar -tvf /opt/postgresql-9.2-1004.jdbc4.jar | grep postgresql | grep Driver

Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on June 13, 2017, 01:58:27 AM
Hi abond
I connect to specdb on the DBServer from the AppServer using psql -h specdb -U spec -d specdb:

[root@appserver bin]# psql -h specdb -U spec -d specdb
psql: could not connect to server: Connection refused
   Is the server running on host "specdb" (10.10.1.5) and accepting
   TCP/IP connections on port 5432?

Hi AnoopGupta
I have attached my glassfish.env file.
The result returned by typing the command is as below: 

[root@dbserver Desktop]# jar -tvf /opt/postgresql-9.2-1004-jdbc4.jar | grep postgresql | grep Driver
   769 Fri Nov 01 13:40:46 CST 2013 org/postgresql/Driver$1.class
  2790 Fri Nov 01 13:40:46 CST 2013 org/postgresql/Driver$ConnectThread.class
 15877 Fri Nov 01 13:40:46 CST 2013 org/postgresql/Driver.class
  1093 Fri Nov 01 13:40:52 CST 2013 org/postgresql/util/PSQLDriverVersion.class
[root@dbserver Desktop]#

Thanks for both of your help!
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: abond on June 20, 2017, 10:33:35 AM
Hey Miles,

Is this issue still a problem for you? 

If so, can you log into the postgresql database using psql on the dbserver itself?  If so, have you tried disabling the firewall on the dbserver and retrying your psql database connection from the appserver?

Thanks,
Andy
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: AnoopGupta on June 20, 2017, 12:40:56 PM
Hi Miles,

As I said in my previous post, please set JDBC_CLASSPATH=/opt/postgresql-9.2-1004.jdbc4.jar in your glassfish.env to fix ClassNotFoundException.

You will still need to look into whether postgresql is up and running and that you can connect to it using psql from DBServer and AppServer. Please follow Andy's suggestion.

Thanks,
Anoop
 
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on June 29, 2017, 01:14:06 AM
Hi
I have set JDBC_CLASSPATH=/opt/postgresql-9.2-1004.jdbc4.jar in my glassfish.env
and use command "service postgresql status" to check "postmaster (pid 2287) is running...".
The issue still happens.

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: abond on June 29, 2017, 02:44:20 PM
Hey Miles,

I am sorry to hear you are still having trouble getting the database connections to work. 

Do you still get an error when you try to execute the "psql -h specdb -U spec -d specdb" command from the appserver?  Have you had a chance to try the command "psql -Uspec -d specdb" from the dbserver itself?  The goal here is to verify whether the database is accessible locally and just the remote connections to the database are failing. 

Thanks,
Andy
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: AnoopGupta on July 06, 2017, 12:56:23 PM
Please respond to what Andy has asked. In addition, I noticed a typo:

You have set JDBC_CLASSPATH=/opt/postgresql-9.2-1004.jdbc4.jar, however when you ran the jar tvf command, your jar file was /opt/postgresql-9.2-1004-jdbc4.jar

There is a difference of . vs - between 1004 and jdbc4
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on July 06, 2017, 10:44:10 PM
Hi
I have replaced "postgresql-9.2.1004.jdbc4.jar" with "postgresql-9.2-1004.jdbc4.jar".
I am so careless.
Thank you so much!

from appserver:
[root@appserver bin]# psql -h specdb -U spec -d specdb
psql: could not connect to server: Connection refused
   Is the server running on host "specdb" (10.10.1.5) and accepting
   TCP/IP connections on port 5432?

from dbserver:
[root@dbserver Desktop]# psql -U spec -d specdb
psql: FATAL:  Ident authentication failed for user "spec"

./loaddb_postgres.sh
[root@dbserver other_scripts]# ./loaddb_postgres.sh
Script started Fri Jul 7 10:36:25 CST 2017
sleep 10
Starting Database Load
Loading database with orders_injection_rate = 500
Loading database with numThreads  = 4
Loading Databases ...
INFO : IR supplied : 500
INFO : stepped IR  : 500
org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
   at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:207)
   at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64)
   at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:136)
   at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:29)
   at org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:21)
   at org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:31)
   at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
   at org.postgresql.Driver.makeConnection(Driver.java:397)
   at org.postgresql.Driver.connect(Driver.java:267)
   at java.sql.DriverManager.getConnection(DriverManager.java:571)
   at java.sql.DriverManager.getConnection(DriverManager.java:215)
   at org.spec.jappserver.load.DatabaseConnection.getConnection(DatabaseConnection.java:212)
   at org.spec.jappserver.load.LoadCorp.main(LoadCorp.java:114)
   at org.spec.jappserver.load.LoadAll.main(LoadAll.java:51)
Caused by: java.net.ConnectException: Connection refused
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
   at java.net.Socket.connect(Socket.java:579)
   at java.net.Socket.connect(Socket.java:528)
   at org.postgresql.core.PGStream.<init>(PGStream.java:60)
   at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:101)
   ... 13 more
Exception in thread "main" java.lang.RuntimeException: Failed to load Corp domain properlyConnection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
   at org.spec.jappserver.load.LoadAll.main(LoadAll.java:55)
Ignoring read() errors...
Ignoring read() errors...
Ignoring read() errors...
Launcher: done waiting.
Finished Database Load
Script ended Fri Jul 7 10:36:36 CST 2017



Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 10, 2017, 05:05:19 PM
Hi Miles.

Going through the checklist here....

Is the firewall turned off? Andy asked but I don't think you confirmed. Is SELINUX off?

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on July 10, 2017, 11:15:54 PM
Hi Andy
Sorry, I didn't reply your question.
Both firewall and SELINUX are turned off.

Another problem is
"http://specdelivery:8000/Supplier/DeliveryServlet?cmd=switchlog"
 returned "HTTP Status 404" from my appserver, but it was successful to
 execute "ant -f build_glassfish.xml".

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 11, 2017, 01:53:34 PM
Hey Miles,

I'm reproducing the example VM environment for db/appserver, and I've found mistakes in the documentation (that I helped write and recently updated thinking it was finished for good).  :-[ I'm sorry to hear this is still a problem, and I'm working on it.

Thanks for your patience.

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 11, 2017, 05:29:09 PM
Please make sure you have the link for the JDBC driver. Issue this command:

# ls -l /opt/SPECjAppServer2004/jdbc/postgresql.jar

You should see this:

lrwxrwxrwx 1 root root 34 Jul 11 18:39 /opt/SPECjAppServer2004/jdbc/postgresql.jar -> /opt/postgresql-9.2-1004.jdbc4.jar


Lastly, make sure there's only one instance of the following parameters in /etc/sysctl.conf:

kernel.sem = 500 64000 400 512
kernel.shmmax = 137438953472
kernel.shmmni = 11118096
kernel.shmall = 8294967296

I found that running the makeme_dbserver.sh script more than once messes these up. Do you see any PostgreSQL errors at the end of /var/log/messages?

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 11, 2017, 05:48:11 PM
I think I found it - make sure specdb is set correctly in /etc/hosts. The makeme_exampleVM.sh script adds example VM names and addresses, and for dbserver it adds:

10.10.1.5       dbserver1-int specdb

You can use either the internal or external address for dbserver, but just make sure it's in there. Give that a try and let us know.

Lisa

Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on July 11, 2017, 10:16:09 PM
Hi
[1]
The link for the JDBC driver in my dbserver :
  [root@dbserver Desktop]# ls -l /opt/SPECjAppServer2004/jdbc/postgresql.jar
  lrwxrwxrwx. 1 root root 34 Jul  7 10:36 /opt/SPECjAppServer2004 
  /jdbc/postgresql.jar -> /opt/postgresql-9.2-1004-jdbc4.jar

[2]
There's only one instance of the following parameters in /etc/sysctl.conf:
        kernel.sem = 500 64000 400 512
        kernel.shmmax = 137438953472 
        kernel.shmmni = 11118096
        kernel.shmall = 8294967296

[3]
I don't see any PostgreSQL errors at the end of /var/log/messages.
[4]
I have executed makeme_exampleVM.sh at the first and     
      10.10.1.5       dbserver1-int specdb
  is added.
[5]
Now the result returned is :
[root@dbserver other_scripts]# ./loaddb_postgres.sh 500
Script started Wed Jul 12 10:08:10 CST 2017
sleep 10
Starting Database Load
Loading database with orders_injection_rate = 500
Loading database with numThreads  = 4
Loading Databases ...
INFO : IR supplied : 500
INFO : stepped IR  : 500
org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
   at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
   at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
   at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
   at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
   at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
   at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:363)
   at org.spec.jappserver.load.LoadCorp.cleanAll(LoadCorp.java:171)
   at org.spec.jappserver.load.LoadCorp.main(LoadCorp.java:152)
   at org.spec.jappserver.load.LoadAll.main(LoadAll.java:51)
Exception in thread "main" java.lang.RuntimeException: Failed to load Corp domain properlyERROR: current transaction is aborted, commands ignored until end of transaction block
   at org.spec.jappserver.load.LoadAll.main(LoadAll.java:55)
Ignoring read() errors...
Ignoring read() errors...
Ignoring read() errors...
Launcher: done waiting.
Finished Database Load
Script ended Wed Jul 12 10:08:20 CST 2017


Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 11, 2017, 10:42:05 PM
What do you see when you issue ifconfig on the dbserver?

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on July 11, 2017, 11:13:11 PM
Hi Lisa
I just followed emampleVM_scripts to build my testbed.

[root@dbserver Desktop]# ifconfig
eth0      Link encap:Ethernet  HWaddr 52:54:00:1D:1A:75 
          inet addr:10.10.1.5  Bcast:10.10.255.255  Mask:255.255.0.0
          inet6 addr: fe80::5054:ff:fe1d:1a75/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:36681 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1912932 (1.8 MiB)  TX bytes:2133 (2.0 KiB)

eth1      Link encap:Ethernet  HWaddr 52:54:00:11:C3:73 
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2000:2:3:4:5054:ff:fe11:c373/64 Scope:Global
          inet6 addr: 2001:db8:0:1:5054:ff:fe11:c373/64 Scope:Global
          inet6 addr: fe80::5054:ff:fe11:c373/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1080563 errors:0 dropped:0 overruns:0 frame:0
          TX packets:209 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:102138149 (97.4 MiB)  TX bytes:41318 (40.3 KiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:19368 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19368 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2620964 (2.4 MiB)  TX bytes:2620964 (2.4 MiB)

virbr0    Link encap:Ethernet  HWaddr 52:54:00:83:F7:89 
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 13, 2017, 02:25:34 PM
Hi Miles. I made corrections to the scripts and would like for you to retry creating dbserver. Please clone your VM to create a clean dbserver, reinstall SPECvirt (if needed), and download then unpack the attached in /opt. Again, I apologize for the inconvenience.

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on July 13, 2017, 11:41:22 PM
Hi Lisa
I have reinstalled and use optdirs-sc2013-v1.04 to setup my dbserver,
   but I got below error message when executing loaddb.sh
org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
   I will try to find out which steps not included in scripts I missed or made mistakes.

Thanks for your help.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 14, 2017, 09:20:58 AM
When you cloned the create a fresh dbserver, did you use a CentOS 6 or 7 VM? The scripts work for me on CentOS 6.x.

Please reboot the VM. That's not in the instructions, but I found I had to do it manually after makeme_dbserver.sh applies the /etc/sysctl.conf shared memory settings.

After the reboot, can you do:

psql -U spec -d specdb

And see:

psql -U spec -d specdb
psql (8.4.20, server 9.2.21)
WARNING: psql version 8.4, server version 9.2.
         Some psql features might not work.
Type "help" for help.

specdb=#

If that works, Ctrl+D to exit. Let's turn off IPV6:

sysctl -w net.ipv6.conf.default.disable_ipv6=1
sysctl -w net.ipv6.conf.all.disable_ipv6=1


Then retry /opt/other_scripts/loaddb_postgres.sh.

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on July 17, 2017, 09:10:42 PM
Hi Lisa
It works in my CentOS6.5 now!
I think two different versions of postgresql resulted in my problem.
After I uninstalled postgresql_8.4  contained in CentOS6.5, the errors disappeared.

Thanks for your help.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on July 18, 2017, 09:22:26 AM
Glad to hear it! I'll add an instruction to remove PostgreSQL 8 before proceeding.

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on August 29, 2017, 02:50:08 PM
Hi
Now I am trying to run with 6T3W(app, batch and mail workloads), but always see below message in clientmgr1_1088.out:
-> For txRate(100), loadFactor(5), and load_scale_factor(1.0), your DBIR must be built for 500IR

Even if I re-run loaddb_postgres.sh in both dbservers, the message still happen and the run is aborted.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on August 29, 2017, 02:52:20 PM
This is an informational message, not an error message. You're always going to see it. What do the Client logs report?

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on August 30, 2017, 03:23:46 AM
Hi
Now I understand the message is not a error. Thanks.
The error I should try to fix  is below:
"O1:2041: error adding cars to cart for customer 2590686 - Part 2 java.lang.NullPointerException"
"O1:1697: error adding cars to cart for customer 1105229 - Part 2 java.lang.NullPointerException"
"O1:956: error adding cars to cart for customer 1440489 - Part 2 java.lang.NullPointerException"


And I have a question:
The Use% of "/" directory in appserver will increase while running.
How and what should I release after each run?

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on August 30, 2017, 11:14:56 AM
On occasion you'll get these "error adding cars to cart" messages. If you have a few, they're fine and you can ignore them. I'll update the Technical Support FAQ at https://www.spec.org/virt_sc2013/docs/SPECvirt_TechnicalSupport.html (https://www.spec.org/virt_sc2013/docs/SPECvirt_TechnicalSupport.html) with this info.

The root directory on appserver will fill up over time. jAppInit.sh and jAppInitRstr.sh will issue commands to remove:

Code: [Select]
/opt/glassfish3/glassfish/domains/spec2004-1/imq/instances/imqbroker/log/*"
/opt/glassfish3/glassfish/domains/spec2004-1/imq/instances/imqbroker/fs370/*"
/opt/glassfish3/glassfish/domains/spec2004-1/logs/server.log*

The full results of the appserver run are kept in /opt/SPECjAppServer2004/output/# where # is the sequence number of the run. You could remove the directories for the older test runs. Or you could add a disk to appserver and soft link it to /opt/SPECjAppServer2004.

You're making progress!  :)

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on August 31, 2017, 02:30:02 PM
Hi
jAppInit.sh and jAppInitRstr.sh work, thanks.

There are many Validation Errors in my report and the application score is almost "0".
According to SPECvirt_sc2013 Technical Support, it said
"To find a sample domain.xml file, extract the archive and look under the Virtualization folder (VIRT) and select any tile. Then navigate through the appserver folder to software (SOFTW) then spec2004-01 then config where domain.xml resides. "
I just download a domain.xml to and copy to my appservers, but SPECvirt cannot start to run.
So, what values and how do I modify them to meet my 6T3W run? increase or decrease?

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on August 31, 2017, 04:11:58 PM
Go back to the original domain.xml you had before. Please post the output of the errors in the Clientmgr out files.

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on August 31, 2017, 10:49:10 PM
Hi
Sorry, I don't know why I cannot attach my logs.
There are so many errors such as :

-> O1:492: error adding cars to cart for customer 10155 - Part 2 java.lang.NullPointerException
-> O1:779: error adding cars to cart for customer 3045993 - Part 2 java.lang.NullPointerException
-> O1:273: error adding cars to cart for customer 131422 - Part 2 java.lang.NullPointerException
-> O1:71: error adding cars to cart for customer 1424268 - Part 2 java.lang.NullPointerException
-> O1:73: error adding cars to cart for customer 2392633 - Part 2 java.lang.NullPointerException
-> O1:149: error adding cars to cart for customer 1611828 - Part 2 java.lang.NullPointerException
-> O1:64: error adding cars to cart for customer 2635826 - Part 2 java.lang.NullPointerException
-> O1:352: error adding cars to cart for customer 993335 - Part 2 java.lang.NullPointerException
-> O1:957: error adding cars to cart for customer 1941322 - Part 2 java.lang.NullPointerExcepti

    ...

java version "1.7.0_45"


Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on September 01, 2017, 11:07:40 AM
You're having problems with both appserver and webserver (https://www.spec.org/forums/index.php?topic=89.msg557#msg557 (https://www.spec.org/forums/index.php?topic=89.msg557#msg557)), so let's get one workload working before adding more. I'm not clear if you can even run one tile at this point.

Set NUM_WORKLOADS=1 for now to run only appserver. Can you run successfully two tiles (two appservers against one dbserver)? Are you restoring the dbserver database between runs? After you restore the database, what do you see when you log into appserver and run jApp-testappserver.sh in the helper directory:

Code: [Select]
echo "Stopping Appserver (will fail if already stopped)"
ssh specdelivery -n 'cd /opt/SPECjAppServer2004/bin;./appsrv-ctrl.sh stop'
echo
echo "Stopping Emulator (will fail if already stopped)"
ssh specemulator -n 'cd /opt/SPECjAppServer2004/bin;./tomcat-ctrl.sh stop'

sleep 5

echo "Starting Appserver"
ssh specdelivery -n 'cd /opt/SPECjAppServer2004/bin;./appsrv-ctrl.sh start'

echo "Starting Emulator"
ssh specemulator -n 'cd /opt/SPECjAppServer2004/bin;./tomcat-ctrl.sh start'

echo; echo "Test Emulator - should show 200 OK"
curl http://specemulator:8080/Emulator/EmulatorServlet?cmd=switchlog

echo; echo "Test Delivery - should show 200 OK"
curl http://specdelivery:8000/Supplier/DeliveryServlet?cmd=switchlog

echo; echo "Test Appserver - should show three tests PASSED if"
echo; echo "database is up. Rerun this script after dbserver is set up."
read -p "Press Enter to continue..."
curl http://specdelivery:8000/SPECjAppServer/app?action=atomicityTests

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on September 27, 2017, 09:50:56 PM
Hi
I set the value of LOAD_SCALE_FACTORS="0.1"  to run with 5-Tile_4-workload, but errors appeared.
Before executing, I have run jAppInitRstr.sh on client1 and client5; jAppInit.sh on client2~client4.

primectrl.out
...
-09-28 02:47:06:955 PrimeControl: waiting for 1 masters to finish
2017-09-28 02:47:21:955 PrimeControl: waiting for 1 masters to finish
2017-09-28 02:47:36:956 PrimeControl: [ERROR] Maximum prime client wait time exceeded!
2017-09-28 02:55:04:590 PrimeControl: client1:1098 (PRIME_HOST[0][0]) run complete; numStarted = 0
2017-09-28 02:55:04:594 Workload validation errors reported!:
2-1-0 = Weighted percentage difference (2.60%) for home in Iteration 1 is too high. Expected: 15657 requests, Actual: 10642

2-1-1 = Weighted percentage difference (4.13%) for search in Iteration 1 is too high. Expected: 24358 requests, Actual: 16389

2-1-2 = Weighted percentage difference (3.85%) for catalog in Iteration 1 is too high. Expected: 22613 requests, Actual: 15187

2-1-3 = Weighted percentage difference (8.21%) for product in Iteration 1 is too high. Expected: 47847 requests, Actual: 32000

2-1-4 = Weighted percentage difference (7.36%) for fileCatalog in Iteration 1 is too high. Expected: 43500 requests, Actual: 29295

2-1-5 = Weighted percentage difference (4.33%) for file in Iteration 1 is too high. Expected: 26099 requests, Actual: 17739

2-1-6 = Weighted percentage difference (2.16%) for download in Iteration 1 is too high. Expected: 13055 requests, Actual: 8879

2-1-7 = Sum of weighted percentage difference (32.62%) exceeds 1.5% for Iteration 1
2-1-8 = Page home errors (10642) >= 0.01 * Requests ( 10642) = 106.42
2-1-9 = Page search errors (16389) >= 0.01 * Requests ( 16389) = 163.89000000000001
2-1-10 = Page catalog errors (15187) >= 0.01 * Requests ( 15187) = 151.87
2-1-11 = Page product errors (32000) >= 0.01 * Requests ( 32000) = 320.0
2-1-12 = Page fileCatalog errors (29295) >= 0.01 * Requests ( 29295) = 292.95
2-1-13 = Page file errors (17739) >= 0.01 * Requests ( 17739) = 177.39000000000001
2-1-14 = Page download errors (8879) >= 0.01 * Requests ( 8879) = 88.79
2-1-15 = Total validation errors (130131) >= 0.005 * TotalRequests ( 130131) =650.655
1-1-0 = Weighted percentage difference (2.59%) for home in Iteration 1 is too high. Expected: 15657 requests, Actual: 10647

1-1-1 = Weighted percentage difference (4.14%) for search in Iteration 1 is too high. Expected: 24358 requests, Actual: 16371

1-1-2 = Weighted percentage difference (3.84%) for catalog in Iteration 1 is too high. Expected: 22613 requests, Actual: 15201

1-1-3 = Weighted percentage difference (8.22%) for product in Iteration 1 is too high. Expected: 47847 requests, Actual: 31976

1-1-4 = Weighted percentage difference (7.39%) for fileCatalog in Iteration 1 is too high. Expected: 43500 requests, Actual: 29228

1-1-5 = Weighted percentage difference (4.35%) for file in Iteration 1 is too high. Expected: 26099 requests, Actual: 17699

1-1-6 = Weighted percentage difference (2.16%) for download in Iteration 1 is too high. Expected: 13055 requests, Actual: 8889

1-1-7 = Sum of weighted percentage difference (32.68%) exceeds 1.5% for Iteration 1
1-1-8 = Page home errors (10647) >= 0.01 * Requests ( 10647) = 106.47
1-1-9 = Page search errors (16371) >= 0.01 * Requests ( 16371) = 163.71
1-1-10 = Page catalog errors (15201) >= 0.01 * Requests ( 15201) = 152.01
1-1-11 = Page product errors (31976) >= 0.01 * Requests ( 31976) = 319.76
1-1-12 = Page fileCatalog errors (29228) >= 0.01 * Requests ( 29228) = 292.28000000000003
1-1-13 = Page file errors (17699) >= 0.01 * Requests ( 17699) = 176.99
1-1-14 = Page download errors (8889) >= 0.01 * Requests ( 8889) = 88.89
1-1-15 = Total validation errors (130011) >= 0.005 * TotalRequests ( 130011) =650.0550000000001
3-1-0 = Weighted percentage difference (2.60%) for home in Iteration 1 is too high. Expected: 15657 requests, Actual: 10641

3-1-1 = Weighted percentage difference (4.19%) for search in Iteration 1 is too high. Expected: 24358 requests, Actual: 16260

3-1-2 = Weighted percentage difference (3.86%) for catalog in Iteration 1 is too high. Expected: 22613 requests, Actual: 15166

3-1-3 = Weighted percentage difference (8.28%) for product in Iteration 1 is too high. Expected: 47847 requests, Actual: 31849

3-1-4 = Weighted percentage difference (7.43%) for fileCatalog in Iteration 1 is too high. Expected: 43500 requests, Actual: 29144

3-1-5 = Weighted percentage difference (4.38%) for file in Iteration 1 is too high. Expected: 26099 requests, Actual: 17649

3-1-6 = Weighted percentage difference (2.16%) for download in Iteration 1 is too high. Expected: 13055 requests, Actual: 8878

3-1-7 = Sum of weighted percentage difference (32.90%) exceeds 1.5% for Iteration 1
3-1-8 = Page home errors (10641) >= 0.01 * Requests ( 10641) = 106.41
3-1-9 = Page search errors (16260) >= 0.01 * Requests ( 16260) = 162.6
3-1-10 = Page catalog errors (15166) >= 0.01 * Requests ( 15166) = 151.66
3-1-11 = Page product errors (31849) >= 0.01 * Requests ( 31849) = 318.49
3-1-12 = Page fileCatalog errors (29144) >= 0.01 * Requests ( 29144) = 291.44
3-1-13 = Page file errors (17649) >= 0.01 * Requests ( 17649) = 176.49
3-1-14 = Page download errors (8878) >= 0.01 * Requests ( 8878) = 88.78
3-1-15 = Total validation errors (129587) >= 0.005 * TotalRequests ( 129587) =647.9350000000001
3-0-0 = Error reading file '/opt/SPECjAppServer2004/output/11/Atomicity.html'
3-0-1 = Error reading file '/opt/SPECjAppServer2004/output/11/ValidationErr.txt'
0-1-0 = Weighted percentage difference (2.60%) for home in Iteration 1 is too high. Expected: 15657 requests, Actual: 10633

0-1-1 = Weighted percentage difference (4.13%) for search in Iteration 1 is too high. Expected: 24358 requests, Actual: 16377

0-1-2 = Weighted percentage difference (3.83%) for catalog in Iteration 1 is too high. Expected: 22613 requests, Actual: 15211

0-1-3 = Weighted percentage difference (8.21%) for product in Iteration 1 is too high. Expected: 47847 requests, Actual: 31985

0-1-4 = Weighted percentage difference (7.38%) for fileCatalog in Iteration 1 is too high. Expected: 43500 requests, Actual: 29252

0-1-5 = Weighted percentage difference (4.34%) for file in Iteration 1 is too high. Expected: 26099 requests, Actual: 17711

0-1-6 = Weighted percentage difference (2.17%) for download in Iteration 1 is too high. Expected: 13055 requests, Actual: 8872

0-1-7 = Sum of weighted percentage difference (32.67%) exceeds 1.5% for Iteration 1
0-1-8 = Page home errors (10633) >= 0.01 * Requests ( 10633) = 106.33
0-1-9 = Page search errors (16377) >= 0.01 * Requests ( 16377) = 163.77
0-1-10 = Page catalog errors (15211) >= 0.01 * Requests ( 15211) = 152.11
0-1-11 = Page product errors (31985) >= 0.01 * Requests ( 31985) = 319.85
0-1-12 = Page fileCatalog errors (29252) >= 0.01 * Requests ( 29252) = 292.52
0-1-13 = Page file errors (17711) >= 0.01 * Requests ( 17711) = 177.11
0-1-14 = Page download errors (8872) >= 0.01 * Requests ( 8872) = 88.72
0-1-15 = Total validation errors (130041) >= 0.005 * TotalRequests ( 130041) =650.205
1-0-0 = Error reading file '/opt/SPECjAppServer2004/output/25/Atomicity.html'
1-0-1 = Error reading file '/opt/SPECjAppServer2004/output/25/ValidationErr.txt'
4-0-0 = Error reading file '/opt/SPECjAppServer2004/output/15/Atomicity.html'
4-0-1 = Dealer Purchase Transaction Mix: FAILED
4-0-2 = Dealer Manage Transaction Mix: FAILED
4-0-3 = Dealer Browse Transaction Mix: FAILED
4-0-4 = Dealer 90% Response Time FAILED
4-0-5 = Dealer Avg. Response Time FAILED
4-0-6 = Purchase Cycle Time Avg. FAILED
4-0-7 = Manage Cycle Time Avg. FAILED
4-0-8 = Browse Cycle Time Avg. FAILED
4-0-9 = Vehicle Purchasing Rate FAILED
4-0-10 = Largeorder Vehicle Purchase Rate FAILED
4-0-11 = Regular Vehicle Purchase Rate FAILED
4-0-12 = LargeOrderLine Vehicle Rate FAILED
4-0-13 = PlannedLines Vehicle Rate FAILED
4-0-14 = Manufacturing 90% Response Time FAILED
2-0-0 = Error reading file '/opt/SPECjAppServer2004/output/18/Atomicity.html'
2-0-1 = Error reading file '/opt/SPECjAppServer2004/output/18/ValidationErr.txt'
4-2-0 = UID_STORE_NUM_UNSET_FLAGS_SEEN Mix Pct Failed. Expected: 30.000, Achieved: 31.288
0-0-0 = Dealer Purchase Transaction Mix: FAILED
0-0-1 = Dealer Manage Transaction Mix: FAILED
0-0-2 = Dealer Browse Transaction Mix: FAILED
0-0-3 = Dealer 90% Response Time FAILED
0-0-4 = Dealer Avg. Response Time FAILED
0-0-5 = Purchase Cycle Time Avg. FAILED
0-0-6 = Manage Cycle Time Avg. FAILED
0-0-7 = Average vehicles per order FAILED
0-0-8 = Vehicle Purchasing Rate FAILED
0-0-9 = Percent Purchases that are Large Orders FAILED
0-0-10 = Average # of vehicles per regular order FAILED
0-0-11 = Regular Vehicle Purchase Rate FAILED
0-0-12 = LargeOrderLine Vehicle Rate FAILED
0-0-13 = Manufacturing 90% Response Time FAILED
2017-09-28 02:55:04:647 PrimeControl: aggregate audit...
2017-09-28 02:55:04:648 PrimeControl: aggregate audit...
2017-09-28 02:55:04:648 PrimeControl: aggregate audit...
2017-09-28 02:55:04:649 PrimeControl: aggregate audit...
2017-09-28 02:55:04:649 PrimeControl: aggregate audit...
2017-09-28 02:55:04:650 PrimeControl: aggregate audit...
2017-09-28 02:55:04:651 PrimeControl: aggregate audit...
2017-09-28 02:55:04:651 PrimeControl: aggregate audit...
2017-09-28 02:55:04:652 PrimeControl: aggregate audit...
2017-09-28 02:55:04:655 PrimeControl: aggregate audit...
2017-09-28 02:55:04:655 PrimeControl: aggregate audit...
2017-09-28 02:55:04:656 PrimeControl: aggregate audit...
2017-09-28 02:55:04:656 PrimeControl: aggregate audit...
2017-09-28 02:55:04:657 PrimeControl: aggregate audit...
2017-09-28 02:55:04:657 PrimeControl: aggregate audit...
2017-09-28 02:55:04:664 PrimeControl: aggregate audit...
2017-09-28 02:55:04:670 PrimeControl: aggregate audit...
2017-09-28 02:55:04:672 PrimeControl: aggregate audit...
2017-09-28 02:55:04:675 PrimeControl: aggregate audit...
2017-09-28 02:55:04:675 PrimeControl: aggregate audit...
2017-09-28 02:55:04:675 PrimeControl: validating aggregate audit...
Exception in thread "Thread-18" java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:514)
   at org.spec.virt.Configuration.setValue(Configuration.java:201)
   at org.spec.virt.Configuration.setValue(Configuration.java:192)
   at org.spec.virt.PrimeControl.printPrimeMetrics(PrimeControl.java:1154)
   at org.spec.virt.PrimeControl.access$2200(PrimeControl.java:32)
   at org.spec.virt.PrimeControl$PrimeClientThread.run(PrimeControl.java:1904)
Exception in thread "Thread-26" java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:514)
   at org.spec.virt.Configuration.setValue(Configuration.java:201)
   at org.spec.virt.Configuration.setValue(Configuration.java:192)
   at org.spec.virt.PrimeControl.printPrimeMetrics(PrimeControl.java:1154)
   at org.spec.virt.PrimeControl.access$2200(PrimeControl.java:32)
   at org.spec.virt.PrimeControl$PrimeClientThread.run(PrimeControl.java:1904)
Exception in thread "Thread-22" java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:514)
   at org.spec.virt.Configuration.setValue(Configuration.java:201)
   at org.spec.virt.Configuration.setValue(Configuration.java:192)
   at org.spec.virt.PrimeControl.printPrimeMetrics(PrimeControl.java:1154)
   at org.spec.virt.PrimeControl.access$2200(PrimeControl.java:32)
   at org.spec.virt.PrimeControl$PrimeClientThread.run(PrimeControl.java:1904)
        ....

This symptom did not occur in tile1 and tile2, but existed in tile3~tile5.
(I found the disk usage of both tile1 and tile2 didn't decrease after a run.)
The usage of storage in tile3 tile4 and tile5 is as follows:
before executing runspecvirt.sh
[root@appserver Desktop]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda3        33G  7.6G   24G  25% /
tmpfs           4.0G  224K  4.0G   1% /dev/shm
/dev/vda1      1008M   62M  896M   7% /boot

after executing runspecvirt.sh
[root@appserver Desktop]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda3        33G   33G     0 100% /
tmpfs           4.0G  224K  4.0G   1% /dev/shm
/dev/vda1      1008M   62M  896M   7% /boot

Should I re-install appservers with larger volume?
How do I determine how much it needs to run 5 or more tiles?

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: lroderic on September 28, 2017, 11:21:09 AM
Hi. One of the subcommittee members uses the following to clean up appserver between test runs:

Code: [Select]
$sjasprimedir = /opt/SPECjAppServer2004/
echo "0" >~/specjappserver.seq
rm -rf $sjasprimedir/classes/*.txt
rm -rf $sjasprimedir/output/*
echo -n "0" >$sjasprimedir/output/specjappserver.seq
mkdir -p $sjasprimedir/output/0
touch $sjasprimedir/output/0/Atomicity.html

That you're running out of disk space means you're filling log files with errors.

Lisa
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on October 19, 2017, 11:34:48 PM
Hi
I have completed a 3T4W run but validation errors in Application Server and Web Server are as follows:

Code: [Select]
Application Server Errors:
◾Dealer Purchase Transaction Mix: FAILED
◾Dealer Manage Transaction Mix: FAILED
◾Dealer Browse Transaction Mix: FAILED
◾Dealer 90% Response Time FAILED
◾Dealer Avg. Response Time FAILED
◾Purchase Cycle Time Avg. FAILED
◾Manage Cycle Time Avg. FAILED
◾Average vehicles per order FAILED
◾Vehicle Purchasing Rate FAILED
◾Percent Purchases that are Large Orders FAILED
◾Average # of vehicles per regular order FAILED
◾Regular Vehicle Purchase Rate FAILED
◾LargeOrderLine Vehicle Rate FAILED
◾PlannedLines Vehicle Rate FAILED
◾Manufacturing 90% Response Time FAILED

Web Server Errors:
◾Page file errors (171421) >= 0.01 * Requests ( 175025) = 1750.25
◾Total validation errors (171421) >= 0.005 * TotalRequests ( 1290937) =6454.685

◦ Aggregate Audit for Shared Database
◾Database 1 Errors: ◾Work Order Transaction validation FAILED
◾PO Transaction validation FAILED
◾POLine Transaction validation: WARNING: New POLine DB Count ~ Delivery Servlet Tx Count > 10%
◾Manufacturing Delivery Statistics: WARNING: Number of depleted components higher than expected!

Code: [Select]
[1] The following working means the Glassfish server is running:
http://specdelivery:8000/
"Your server is now running' was returned.
Code: [Select]
[2] The following returning 200 OK means the SPECjAppServer.ear deployed on the GlassFish:
curl http://specdelivery:8000/Supplier/DeliveryServlet?cmd=switchlog
"200 OK" was returned.
Code: [Select]
[3] Once deployment works, then verify DB connectivity:
curl http://specdelivery:8000/SPECjAppServer/app?action=atomicityTests
"PASSED" was returned.

I followed ExampleVM script to setup the VMs and executed jAppInit.sh/jAppInitRstr.sh before a new run.

Which steps did I miss or correct?

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: DavidSchmidt on October 23, 2017, 04:49:07 PM
Hi Miles. Would you please attach the primectrl.out file and the results/[run-dir]/1-1.0/*_Audit.report files for this run? These will help to determine how the runs are failing QoS. Thanks,
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on October 23, 2017, 09:08:14 PM
Hi
The logs are attached.

I found "Conflict invalid XML format" error appeared in the server.log on appservers as ollows:

[#|2017-10-24T16:02:26.703+0800|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=319;_ThreadName=Thread-2;|org.spec.jappserver.common.SPECjAppServerException: Remote side error: 409 Conflict invalid XML format

0-0_Dealer.summary
Code: [Select]
Dealer Summary Report
Version : SPECjAppServer2004 v1.08


Dealer Transaction Rate : 0.00 Transactions/sec

TRANSACTION MIX

Total number of transactions = 5
TYPE TX. COUNT MIX REQD. MIX.(5% Deviation Allowed)
---- --------- --- ----------
Purchase: 00001 20.00% 25% FAILED
Manage     : 00004 80.00% 25% FAILED
Browse Autos: 00000 0.00% 50% FAILED

RESPONSE TIMES AVG. MAX. 90TH% REQD. 90TH%

Purchase 246.146 246.146 0.100 2
Manage        551.489 732.166 10.000 2
Browse    0.000 0.000 0.000

Requirement for 90% Response Time FAILED
Requirement for Avg. Response Time FAILED


CYCLE TIMES TARGETED AVG. ACTUAL AVG. MIN. MAX.

Purchase 23.753 552.320 0.000 552.320 FAILED
Manage    7.165 1190.950 0.000 1525.712 FAILED
Browse    0.000 0.000

MISC. STATISTICS

Average vehicles per order 17.000 FAILED
Vehicle Purchasing Rate 0.002/sec FAILED
Percent Purchases that are Large Orders 0.00 FAILED
Average # of vehicles per Large Order 0.000 PASSED
Largeorder Vehicle Purchase Rate 0.000/sec PASSED
Average # of vehicles per regular order 17.000 FAILED
Regular Vehicle Purchase Rate 0.002/sec FAILED


 -- SUNDRY COUNTS (no pass/fail) --

Purchase: denied due to bad credit 00000
Purchase: vehicles immediate txns 00000
Purchase: vehicles deferred txns 00001
Purchase: cart clears 00000
Purchase: vehicles removed from cart 00000
Manage: open orders cancelled 00000
Manage: vehicles sold from lot 00041
Manage: average vehicles sold per txn 00010
Manage: application level errors 00000
Browse: forwards 00000
Browse: backwards 00000
Logins:                1
Trans/sec(txPerSec): 0.001
purcPer:        20.000
percentLrgDealer: 0.000
sumPurcOlCnt:       17
sumPurcLrgOlCnt:     0
sumPurcCount:        1
sumPurcLrgCnt:        0


LITTLE'S LAW VERIFICATION


Number of users = 2250
Sum of Avg. RT * TPS for all Tx. Types = 0.738350



Thanks for your help.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on October 26, 2017, 10:41:47 PM
Hi
Should I provide other log or messages to debug?

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: DavidSchmidt on October 30, 2017, 02:28:47 PM
Hi Miles.

It looks like you are not really getting any appserver workload traffic. For a 2-hour run, your TX counts should be closer to 180K for purchase and Manage and 360K for Browse Autos. The error you see regarding and invalid XML format is probably the issue. Can you post your server.xml file from the appserver?

Thanks,
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on November 01, 2017, 01:52:30 AM
Hi
I download Apache Tomcat 7.0.54 from the URL describled in "SPECvirt_sc2013 Example VM Setup Guide".

I am not sure which one is so I attach 3 files as follows:
"server-1.xml" is copied from /etc/tomcat6/
"server-2.xml" is copied from /opt/apache-tomcat_7.0.54/conf/
"server-3.xml" is copied for /opt/tomcat/conf

Thanks.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: DavidSchmidt on November 03, 2017, 10:44:49 AM
Hi Miles. The errors you are seeing were seen during our development when the appserver workload (SPECjAppServer.ear) and emulator (emulator.ear/war) are not in sync on the SUT VMs. Please check your appserver (Glassfish) server.log file and emulator (Tomcat) log for conflict errors on all of your tiles.

Also, please verify that the SPECjAppserver.ear file and emulator.war file on your SUT VMs in your Glassfish environment match the original versions provided in the SPECvirt_sc2013 kit in the /opt/SPECjAppServer2004/jars directory. There should be no need to rebuild either file for your environment.
Title: Re: Errors in dbsrver VM when loaddb_postgres.sh is executed
Post by: Miles on November 06, 2017, 01:32:05 AM
Hi
I added IP of appserver VMs to pg_hba.conf then used command
 "service postgresql-9.4 restart" ,but the symptom still exist.

I have checked the appserver (Glassfish) server.log file and emulator (Tomcat) log and found the following message:
Code: [Select]
[#|2017-11-06T18:50:47.381+0800|INFO|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=86;_ThreadName=Thread-2;|JTS5078: Table for transaction logging was not added.|#]
Then I copied SPECvirt_sc2013 kit to overwrite my SPECjApp folder on dbserver and re-run, but got the same validation errors.

I think I didn't realize what you mean.

Thanks.