wcst_import concurrent will have error in petascope

[Bang Pham Huu]

@Alex: I don't know about this behavior (e.g allow to many users run wcst_import to server at same time). However, it will have error (in rasnet) from both terminals which run wcst_import simultaneously.

   <ows:ExceptionText>java.lang.RuntimeException : The client with client ID b58d51f0-c56e-4abb-bdbd-7d8041e71859 does not exist.</ows:ExceptionText>
    </ows:Exception>

or

  <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>java.util.NoSuchElementException : null</ows:ExceptionText>

you can close if it is invalid.

See log file below. Thanks.

[Alex Dumitru]

There was a patch which fixed the NoSuchElementException today. Maybe try updating first and report back. We should determine what causes the client id error.

[Bang Pham Huu]

@Alex: btw, I could not find error in petascope.log as now it is full with log like this. Do you think should remove and put to other file (e.g gprc.log) ?

[18:18:50] DEBUG NettyClientTransport@71: 
----------------INBOUND--------------------
DATA: streamId=15, padding=0, endStream=false, length=5, bytes=0000000000
------------------------------------
[18:18:50] DEBUG NettyClientTransport@71: 
----------------INBOUND--------------------
HEADERS: streamId=15, headers=DefaultHttp2Headers[grpc-status: 0], padding=0, endStream=true
------------------------------------

[Alex Dumitru]

Yes, please open a ticket on this.

[Bang Pham Huu]

log error

[Bang Pham Huu]

@Alex: I've pulled and reinstall Rasdaman again, the error still appears when use wcst_import.sh to import coverage

here is the log ​http://rasdaman.org/attachment/ticket/1152/log_1.tar.gz, thanks.

    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>java.util.NoSuchElementException : null</ows:ExceptionText>
    </ows:Exception>

[Bang Pham Huu]

I can see one case that can make this error is when coverage_id starts with number like this "coverage_id": "1_xxxx", but in the logs above it is normal name like cov_number_*.

Do you think wcst_import.sh should check coverage_id is valid also?

[Alex Toader]

I've also come across the error this morning. We are investigating.

[Bang Pham Huu]

To reproduce this problem, run 3 scripts in ​http://rasdaman.org/attachment/ticket/1152/test_wcst_concurent.tar.gz on 3 terminal at the same time. It will show that, the progress will fail soon after few imported coverage, error from wcst_import can be see here ​http://pastebin.com/SA9xru5R

This functionality is useful if user wants to import multiple different coverages to Petascope in batch mode (instead of 1 sequence), but it depend on what Petascope can handle and it is not urgent.

[Bang Pham Huu]

I will test this ticket tomorrow with new Petascope, and then, if it is safe enough then can close it.

[Bang Pham Huu]

The script can run to the end of the loop without problems, so close ticket.

[Dimitar Misev]

can you attach the script?

[Dimitar Misev]

a ok, I guess it's this one: attachment:test_wcst_concurent.tar.gz​