#623 Niagara 4.6

Keith Bishoρ Wed 1 Aug 2018

Has anyone gotten nHaystack 2.1.0 to work with Niagara 4.6?

We're getting "Invalid HTTP response" on the client side.

Authentication seems to be working, but when we try to ping the Jace, we see 4 pairs of what I think looks like normal traffic and then on the fifth transaction, we don't get a response from the Jace.

No errors show up in the application director. It seems like it's just lost, but the error says invalid response.

Any ideas?

Richard McElhinney Thu 2 Aug 2018

Hi Keith,

I haven't done a build of nhaystack against Niagara 4.6 yet.

Having said that, I would have thought it should just work anyway. Can you provide more details on the error?

Is the an error in the Niagara Application Director?

Cheers....

Keith Bishoρ Thu 2 Aug 2018

Richard,

There are no errors in the application director.

I'm remote to our installation for this testing. I'll email you the http message traffic (from both ends) early next week.

Nagesh Narvekar Tue 7 May

Hi Richard,

when will the nhaystack version will be released which is compatible to Niagara 4.6.

Nagesh Narvekar Tue 7 May

Hi Richard, I am also getting the same error as keith. The full details of error is as follow :

sys::IOErr: Invalid HTTP response:

web::WebClient.readRes (WebClient.fan:484)
haystack::ClientAuth.send (ClientAuth.fan:160)
haystack::ClientAuth.get (ClientAuth.fan:133)
haystack::ClientAuthAlgorithm.get (ClientAuth.fan:239)
haystack::NiagaraScramAuthAlgorithm.upgradeInsecureReqs (ClientAuth.fan:537)
haystack::NiagaraScramAuthAlgorithm.auth (ClientAuth.fan:478)
haystack::ClientAuth.authHaystack (ClientAuth.fan:79)
haystack::Client.openx (Client.fan:39)
haystackExt::HaystackConn.onOpen (HaystackConn.fan:60)
connExt::Conn.open (Conn.fan:150)
connExt::Conn.openLinger (Conn.fan:116)
connExt::Conn.openLinger (Conn.fan)
connExt::Conn.ping (Conn.fan:204)
connExt::Conn.receive (Conn.fan:318)
haystackExt::HaystackConn.receive (HaystackConn.fan:44)
connExt::ConnActor.receive (ConnActor.fan:131)
concurrent::Actor._dispatch (Actor.java:230)
concurrent::Actor._work (Actor.java:201)
concurrent::ThreadPool$Worker.run (ThreadPool.java:262)

Cause:

sys::IOErr: java.net.SocketTimeoutException: Read timed out
  java.net.SocketInputStream.socketRead0 (Unknown)
  java.net.SocketInputStream.socketRead (Unknown)
  java.net.SocketInputStream.read (Unknown)
  java.net.SocketInputStream.read (Unknown)
  java.io.BufferedInputStream.fill (Unknown)
  java.io.BufferedInputStream.read (Unknown)
  fan.sys.SysInStream.r (SysInStream.java:63)
  fan.sys.Charset$Utf8Decoder.decode (Charset.java:120)
  fan.sys.InStream.rChar (InStream.java:78)
  fan.sys.InStream.readLine (InStream.java:466)
  fan.sys.InStream.readLine (InStream.java:451)
  web::WebClient.readRes (WebClient.fan:472)
  haystack::ClientAuth.send (ClientAuth.fan:160)
  haystack::ClientAuth.get (ClientAuth.fan:133)
  haystack::ClientAuthAlgorithm.get (ClientAuth.fan:239)
  haystack::NiagaraScramAuthAlgorithm.upgradeInsecureReqs (ClientAuth.fan:537)
  haystack::NiagaraScramAuthAlgorithm.auth (ClientAuth.fan:478)
  haystack::ClientAuth.authHaystack (ClientAuth.fan:79)
  haystack::Client.openx (Client.fan:39)
  haystackExt::HaystackConn.onOpen (HaystackConn.fan:60)
  connExt::Conn.open (Conn.fan:150)
  connExt::Conn.openLinger (Conn.fan:116)
  connExt::Conn.openLinger (Conn.fan)
  connExt::Conn.ping (Conn.fan:204)
  connExt::Conn.receive (Conn.fan:318)
  6 More...

pollBuckets:

uri: http://localhost/haystack/ product: null null module: null null watchId: null watchLeaseReq: null watchLeaseRes: null

currentMessage: none

Actor

pool: demo-Haystack submitted: false queue: 0 ActorPool

name: demo-Haystack maxThreads: 100 pending: 0 idle: 2 workers: 3 demo-Haystack-Worker-30: fan.connExt.ConnPoller@19cc606 [queue: 1] demo-Haystack-Worker-27: idle demo-Haystack-Worker-26: idle

Nagesh Narvekar Tue 14 May

Please suggest how to resolve this ASAP. Thanks.

Richard McElhinney Tue 28 May

Hi Nagesh,

The information you have posted looks like it comes from SkySpark. This doesn't provide me with any information on what the issue could be on the Niagara side.

Can you please provide the output of the Application Director from the Niagara instance you are connecting to?

Login or Signup to reply.