[JBoss JIRA] (ISPN-8898) Indexing not working using REST with embedded cache manager
by Adam Melkus (JIRA)
Adam Melkus created ISPN-8898:
---------------------------------
Summary: Indexing not working using REST with embedded cache manager
Key: ISPN-8898
URL: https://issues.jboss.org/browse/ISPN-8898
Project: Infinispan
Issue Type: Bug
Components: Indexing, Remote Querying, REST
Affects Versions: 9.2.0.Final
Environment: sample application attached
Reporter: Adam Melkus
Priority: …
[View More]Critical
Attachments: ispn_broken.zip
JSON entities stored using REST with protobuf schema are not indexed and therefore querying using REST doesn't work.
Possible issue found is in class {{InternalCacheFactory}} on line 93 where {{DataConversion}} instance is created with {{ByteArrayWrapper}} wrapper. When the value type is {{application/x-protostream}} the wrapper should be {{ProtostreamWrapper}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8892) RestStore should only implement CacheLoader
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8892?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-8892:
--------------------------------
Summary: RestStore should only implement CacheLoader (was: RemoteStore should only implement CacheLoader)
> RestStore should only implement CacheLoader
> -------------------------------------------
>
> Key: ISPN-8892
> URL: https://issues.jboss.org/browse/ISPN-8892
> Project: …
[View More]Infinispan
> Issue Type: Task
> Components: Loaders and Stores
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.3.0.Final
>
>
> The RestStore is redundant since a user could just use the RemoteStore which performs better for pretty much every operation. The only real usage for RestStore is if you wanted to pull data from an existing server and wanted to cache that data. As such we should change RestStore to just implement the CacheLoader interface.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8896) HTTP/2 support is broken
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-8896?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec reassigned ISPN-8896:
-----------------------------------------
Assignee: Sebastian Łaskawiec
> HTTP/2 support is broken
> ------------------------
>
> Key: ISPN-8896
> URL: https://issues.jboss.org/browse/ISPN-8896
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.…
[View More]2.0.Final
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> CURL reports that HTTP Settings frame is broken:
> On Terminal 1:
> {code}
> docker run -e "APP_USER=test" -e "APP_PASS=test" jboss/infinispan-server:9.2.0.Final ../../docs/examples/configs/standalone-rest-ssl.xml
> {code}
> On Terminal 2:
> {code}
> curl "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
> * Illegal port number
> * Closing connection -1
> curl: (3) Illegal port number
> * Trying 172.17.0.2...
> * TCP_NODELAY set
> * Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * skipping SSL peer certificate verification
> * ALPN, server accepted to use h2
> * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate:
> * subject: CN=localhost
> * start date: Mar 01 12:02:32 2018 GMT
> * expire date: Feb 27 12:02:32 2028 GMT
> * common name: localhost
> * issuer: CN=localhost
> * Using HTTP2, server supports multi-use
> * Connection state changed (HTTP/2 confirmed)
> * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
> * Server auth using Basic with user 'test'
> * Using Stream ID: 1 (easy handle 0x55972b0700d0)
> > GET /rest/default/test HTTP/2
> > Host: 172.17.0.2:8443
> > Authorization: Basic dGVzdDp0ZXN0
> > User-Agent: curl/7.53.1
> > Accept: */*
> >
> * http2 error: Remote peer returned unexpected data while we expected SETTINGS frame. Perhaps, peer does not support HTTP/2 properly.
> * Closing connection 0
> curl: (16) Illegal port number
> {code}
> The same with 9.1.5.Final:
> {code}
> curl -d test -H "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
> * Trying 172.17.0.2...
> * TCP_NODELAY set
> * Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * skipping SSL peer certificate verification
> * ALPN, server accepted to use h2
> * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate:
> * subject: CN=localhost
> * start date: Mar 01 12:04:47 2018 GMT
> * expire date: Feb 27 12:04:47 2028 GMT
> * common name: localhost
> * issuer: CN=localhost
> * Using HTTP2, server supports multi-use
> * Connection state changed (HTTP/2 confirmed)
> * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
> * Server auth using Basic with user 'test'
> * Using Stream ID: 1 (easy handle 0x555cd62630d0)
> > POST /rest/default/test HTTP/2
> > Host: 172.17.0.2:8443
> > Authorization: Basic dGVzdDp0ZXN0
> > User-Agent: curl/7.53.1
> > Accept: text/plain
> > Content-Length: 4
> > Content-Type: application/x-www-form-urlencoded
> >
> * We are completely uploaded and fine
> * Connection state changed (MAX_CONCURRENT_STREAMS updated)!
> < HTTP/2 200
> < etag: application/x-www-form-urlencoded-235262424
> < content-type: text/plain
> < content-length: 0
> <
> * Connection #0 to host 172.17.0.2 left intact
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8896) HTTP/2 support is broken
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-8896?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-8896:
-------------------------------------------
It also seems that plain text upgrade is broken: {{curl -H "Accept: text/plain" -k -v --http2 -u test:test http://172.17.0.2:8080/rest/default/test}}
> HTTP/2 support is broken
> ------------------------
>
> Key: ISPN-8896
> URL: https://issues.jboss.org/browse/ISPN-8896
> …
[View More] Project: Infinispan
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.2.0.Final
> Reporter: Sebastian Łaskawiec
>
> CURL reports that HTTP Settings frame is broken:
> On Terminal 1:
> {code}
> docker run -e "APP_USER=test" -e "APP_PASS=test" jboss/infinispan-server:9.2.0.Final ../../docs/examples/configs/standalone-rest-ssl.xml
> {code}
> On Terminal 2:
> {code}
> curl "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
> * Illegal port number
> * Closing connection -1
> curl: (3) Illegal port number
> * Trying 172.17.0.2...
> * TCP_NODELAY set
> * Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * skipping SSL peer certificate verification
> * ALPN, server accepted to use h2
> * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate:
> * subject: CN=localhost
> * start date: Mar 01 12:02:32 2018 GMT
> * expire date: Feb 27 12:02:32 2028 GMT
> * common name: localhost
> * issuer: CN=localhost
> * Using HTTP2, server supports multi-use
> * Connection state changed (HTTP/2 confirmed)
> * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
> * Server auth using Basic with user 'test'
> * Using Stream ID: 1 (easy handle 0x55972b0700d0)
> > GET /rest/default/test HTTP/2
> > Host: 172.17.0.2:8443
> > Authorization: Basic dGVzdDp0ZXN0
> > User-Agent: curl/7.53.1
> > Accept: */*
> >
> * http2 error: Remote peer returned unexpected data while we expected SETTINGS frame. Perhaps, peer does not support HTTP/2 properly.
> * Closing connection 0
> curl: (16) Illegal port number
> {code}
> The same with 9.1.5.Final:
> {code}
> curl -d test -H "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
> * Trying 172.17.0.2...
> * TCP_NODELAY set
> * Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * skipping SSL peer certificate verification
> * ALPN, server accepted to use h2
> * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate:
> * subject: CN=localhost
> * start date: Mar 01 12:04:47 2018 GMT
> * expire date: Feb 27 12:04:47 2028 GMT
> * common name: localhost
> * issuer: CN=localhost
> * Using HTTP2, server supports multi-use
> * Connection state changed (HTTP/2 confirmed)
> * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
> * Server auth using Basic with user 'test'
> * Using Stream ID: 1 (easy handle 0x555cd62630d0)
> > POST /rest/default/test HTTP/2
> > Host: 172.17.0.2:8443
> > Authorization: Basic dGVzdDp0ZXN0
> > User-Agent: curl/7.53.1
> > Accept: text/plain
> > Content-Length: 4
> > Content-Type: application/x-www-form-urlencoded
> >
> * We are completely uploaded and fine
> * Connection state changed (MAX_CONCURRENT_STREAMS updated)!
> < HTTP/2 200
> < etag: application/x-www-form-urlencoded-235262424
> < content-type: text/plain
> < content-length: 0
> <
> * Connection #0 to host 172.17.0.2 left intact
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8896) HTTP/2 support is broken
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created ISPN-8896:
-----------------------------------------
Summary: HTTP/2 support is broken
Key: ISPN-8896
URL: https://issues.jboss.org/browse/ISPN-8896
Project: Infinispan
Issue Type: Bug
Components: REST
Affects Versions: 9.2.0.Final
Reporter: Sebastian Łaskawiec
CURL reports that HTTP Settings frame is broken:
On Terminal 1:
{code}
docker run -e "APP_USER=test" -e "…
[View More]APP_PASS=test" jboss/infinispan-server:9.2.0.Final ../../docs/examples/configs/standalone-rest-ssl.xml
{code}
On Terminal 2:
{code}
curl "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
* Illegal port number
* Closing connection -1
curl: (3) Illegal port number
* Trying 172.17.0.2...
* TCP_NODELAY set
* Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* ALPN, server accepted to use h2
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=localhost
* start date: Mar 01 12:02:32 2018 GMT
* expire date: Feb 27 12:02:32 2028 GMT
* common name: localhost
* issuer: CN=localhost
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user 'test'
* Using Stream ID: 1 (easy handle 0x55972b0700d0)
> GET /rest/default/test HTTP/2
> Host: 172.17.0.2:8443
> Authorization: Basic dGVzdDp0ZXN0
> User-Agent: curl/7.53.1
> Accept: */*
>
* http2 error: Remote peer returned unexpected data while we expected SETTINGS frame. Perhaps, peer does not support HTTP/2 properly.
* Closing connection 0
curl: (16) Illegal port number
{code}
The same with 9.1.5.Final:
{code}
curl -d test -H "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
* Trying 172.17.0.2...
* TCP_NODELAY set
* Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* ALPN, server accepted to use h2
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=localhost
* start date: Mar 01 12:04:47 2018 GMT
* expire date: Feb 27 12:04:47 2028 GMT
* common name: localhost
* issuer: CN=localhost
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user 'test'
* Using Stream ID: 1 (easy handle 0x555cd62630d0)
> POST /rest/default/test HTTP/2
> Host: 172.17.0.2:8443
> Authorization: Basic dGVzdDp0ZXN0
> User-Agent: curl/7.53.1
> Accept: text/plain
> Content-Length: 4
> Content-Type: application/x-www-form-urlencoded
>
* We are completely uploaded and fine
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200
< etag: application/x-www-form-urlencoded-235262424
< content-type: text/plain
< content-length: 0
<
* Connection #0 to host 172.17.0.2 left intact
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years
[JBoss JIRA] (ISPN-8853) Registering interposed synchronization fails in async operation with implicit transaction
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8853?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8853:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.2.1.Final
Resolution: Done
> Registering interposed synchronization fails in async operation with implicit transaction
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-8853
> …
[View More] URL: https://issues.jboss.org/browse/ISPN-8853
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Transactions
> Affects Versions: 9.2.0.CR2
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.2.1.Final
>
>
> {{TransactionTable.enlist}} calls {{transactionSynchronizationRegistry.registerInterposedSynchronization(sync);}} but when an async operation is invoked with implicit transaction, the thread-local transaction is suspended. That can result in
> {code}
> java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
> at org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.registerInterposedSynchronization(TransactionSynchronizationRegistryWrapper.java:69)
> {code}
> I guess that since {{TransactionSynchronizationRegistry}} does not offer a variant that would accept the transaction as parameter we need to wrap the call with resume & suspend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years