Author Topic: What is the reason of the error reading file "Atomicity.html"  (Read 6752 times)

lintao

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Why we try the test, we found the error in result file:
    Application Server Errors:
        Error reading file '/opt/SPECjAppServer2004/output/690/Atomicity.html'


Than we found this error in "primectrl.out" file in client machine:
2015-05-29 18:59:37:595 Workload validation errors reported!:
0-0-0 = Error reading file '/opt/SPECjAppServer2004/output/690/Atomicity.html'
0-0-1 = Dealer Avg. Response Time FAILED
0-0-2 = Purchase Cycle Time Avg. FAILED
0-0-3 = Manage Cycle Time Avg. FAILED
0-0-4 = Browse Cycle Time Avg. FAILED
0-0-5 = Average vehicles per order FAILED
0-0-6 = Vehicle Purchasing Rate FAILED
0-0-7 = Percent Purchases that are Large Orders FAILED
0-0-8 = Largeorder Vehicle Purchase Rate FAILED
0-0-9 = Regular Vehicle Purchase Rate FAILED
0-0-10 = LargeOrderLine Vehicle Rate FAILED
0-0-11 = PlannedLines Vehicle Rate FAILED
2015-05-29 18:59:37:598 PrimeControl: aggregate audit...
2015-05-29 18:59:37:598 PrimeControl: aggregate audit...
2015-05-29 18:59:37:603 PrimeControl: aggregate audit...
2015-05-29 18:59:37:624 PrimeControl: aggregate audit...
2015-05-29 18:59:37:624 PrimeControl: validating aggregate audit...
2015-05-29 18:59:39:710 PrimeControl: stopping clients.
2015-05-29 18:59:39:710 PrimeControl: stopping remote client processes
2015-05-29 18:59:41:716 PrimeControl: stopping local client threads
  > Loading Raw Result File..

2015-05-29 18:59:41:810 PrimeControl: terminating run. Please wait...
2015-05-29 18:59:42:814 specvirt: Done!


At last, we found these messages in "/opt/SPECvirt/logs/20150529-164529/ client-100.0.54.8_1091.log" in client machine, 100.0.54.8 is our APP server's IP:
Messages from: 100.0.54.8:1091
-> May 23, 2015 12:11:40 PM com.sun.corba.ee.impl.encoding.CDRInputStream_1_0 readRMIIIOPValueType
-> WARNING: "IOP00810211: (MARSHAL) Exception from readValue on ValueHandler in CDRInputStream"
-> org.omg.CORBA.MARSHAL:   vmcid: SUN  minor code: 211 completed: Maybe
->    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.valuehandlerReadException(ORBUtilSystemException.java:8888)
->    at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.readRMIIIOPValueType(CDRInputStream_1_0.java:1076)
->    at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.read_value(CDRInputStream_1_0.java:1175)
->    at com.sun.corba.ee.impl.encoding.CDRInputObject.read_value(CDRInputObject.java:655)
->    at com.sun.corba.ee.impl.io.IIOPInputStream.inputObjectField(IIOPInputStream.java:2298)
->    at com.sun.corba.ee.impl.io.IIOPInputStream.inputClassFields(IIOPInputStream.java:2552)
->    at com.sun.corba.ee.impl.io.IIOPInputStream.inputObject(IIOPInputStream.java:1310)
->    at com.sun.corba.ee.impl.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:449)
->    at com.sun.corba.ee.impl.io.ValueHandlerImpl.readValueInternal(ValueHandlerImpl.java:364)
->    at com.sun.corba.ee.impl.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:320)
->    at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.readRMIIIOPValueType(CDRInputStream_1_0.java:1066)
->    at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.read_value(CDRInputStream_1_0.java:1175)
->    at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.read_value(CDRInputStream_1_0.java:986)
->    at com.sun.corba.ee.impl.encoding.CDRInputObject.read_value(CDRInputObject.java:646)
->    at com.sun.corba.ee.impl.servicecontext.UEInfoServiceContextImpl.<init>(UEInfoServiceContextImpl.java:65)
->    at com.sun.corba.ee.spi.servicecontext.ServiceContextDefaults$5.create(ServiceContextDefaults.java:200)
->    at com.sun.corba.ee.impl.servicecontext.ServiceContextsImpl.unmarshal(ServiceContextsImpl.java:265)
->    at com.sun.corba.ee.impl.servicecontext.ServiceContextsImpl.get(ServiceContextsImpl.java:448)
->    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:559)
->    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:369)
->    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:235)
->    at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:187)
->    at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:147)
->    at com.sun.corba.ee.impl.presentation.rmi.codegen.CodegenStubBase.invoke(CodegenStubBase.java:225)
->    at org.spec.jappserver.mfg.workorderses.ejb._WorkOrderSes_DynamicStub.scheduleWorkOrder(org/spec/jappserver/mfg/workorderses/ejb/_WorkOrderSes_DynamicStub.java)
->    at org.spec.jappserver.driver.PlannedLine.createVehicle(PlannedLine.java:416)
->    at org.spec.jappserver.driver.PlannedLine.createVehicle(PlannedLine.java:375)
->    at org.spec.jappserver.driver.PlannedLine.run(PlannedLine.java:193)
-> Caused by: java.io.IOException: Mismatched serialization UIDs : Source (Rep. IDRMI:javax.ejb.EJBException:958C33FAE8798D83:E573C8C3FC5EB5E2) = E573C8C3FC5EB5E2 whereas Target (Rep. ID RMI:javax.ejb.EJBException:958C33FAE8798D83:0B0EB2FF36CB22F6) = 0B0EB2FF36CB22F6
->    at com.sun.corba.ee.impl.util.RepositoryId.useFullValueDescription(RepositoryId.java:675)
->    at com.sun.corba.ee.impl.util.RepositoryId.useFullValueDescription(RepositoryId.java:635)
->    at com.sun.corba.ee.impl.io.ValueHandlerImpl.useFullValueDescription(ValueHandlerImpl.java:420)
->    at com.sun.corba.ee.impl.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:446)
->    at com.sun.corba.ee.impl.io.ValueHandlerImpl.readValueInternal(ValueHandlerImpl.java:364)
->    at com.sun.corba.ee.impl.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:320)
->    at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.readRMIIIOPValueType(CDRInputStream_1_0.java:1066)
->    ... 26 more

We guess our APP server may have some error, but we can't find it. Does anyone meet it? If you can give us some hint, we will always appreciate you^_^

Best regards.

AnoopGupta

  • Jr. Member
  • **
  • Posts: 60
  • Karma: +0/-0
Re: What is the reason of the error reading file "Atomicity.html"
« Reply #1 on: June 02, 2015, 12:49:05 PM »
We would need more information to determine the cause of this issue.
- Was this setup working before? Could you please share a html report confirming this, to give us an idea of the QoS?
- If you repeat the run, do you run into the same issue every time?
- Was GlassFish or Java version recently updated in the App Server VM, or on the client?

Please check the disk usage on the App Server VM, DB Server VM, and the clients. It is possible that Atomicity.html was not written as client disk was full.

Thanks,
Anoop

azure

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: What is the reason of the error reading file "Atomicity.html"
« Reply #2 on: June 06, 2023, 04:08:07 AM »
I have the same issue,  found  glassfish3.log “specdb:5432 refused”,and modify the /etc/hosts:192.168.1.5  dbserver dbserver1 specdb
run test again and be ok

Dorothy

  • Guest
Re: What is the reason of the error reading file "Atomicity.html"
« Reply #3 on: June 22, 2023, 08:22:12 AM »
Verify the file path, double-check that the file '/opt/SPECjAppServer2004/output/690/Atomicity.html' exists in the specified location. Ensure that the path is accurate and matches the actual location of the file. Check file permissions, make sure that the application server has the necessary permissions to read the file. The user or process running the application server should have read access to the file and its parent directories. You can use the 'ls' command (e.g., 'ls -l /opt/SPECjAppServer2004/output/690/Atomicity.html') to view and modify the file permissions if needed. Validate file integrity, if the file exists but the error persists, it's possible that the file is corrupted. Try accessing the file from another location or check if you have a backup copy. If available, replace the file with a known working version. Restart the application server, in some cases, restarting the application server can resolve temporary file access issues. Restart the application server and see if the error still occurs. Review application server logs, check the logs of the application server for any additional error messages or clues related to the file reading issue. The logs may provide more specific information about the root cause of the problem.
« Last Edit: June 26, 2023, 10:32:28 AM by lroderic »