"Packet length determination problem" error

[Pritesh Patel]

Hi,

We are facing issue with one of our production site where it just keep loading but never response and seems work fine when you run directly by port at the same time. So guessing there is some issue with connecting IIS and Tomcat. I have gone through documentation of Boncode where it mention max connections should be same for boncode and server.xml. I have tried to setup both at 500 couple of days ago but seems again we face similar issue. There was another mention for same issue that compression should be disabled, as far as I have check by default compression is disabled and I haven't add any compression for tomcat manually. 

Apart from this I am noticing following errors in boncode. Is this related to it and how can I sort it out? 

2016-04-25 00:00:00 BonCode AJP Connenctor version 1.0.25

2016-04-25 00:00:00 BonCode AJP Connenctor version 1.0.25

2016-04-25 03:37:07 1.0.25 ERROR 

TCP Client level -- Server/Port:localhost/8009

Thread was being aborted.

2016-04-25 03:37:07 One Connection raised an error

2016-04-25 06:25:30 1.0.25 ERROR 

TCP Client level -- Server/Port:localhost/8009

Thread was being aborted.

2016-04-25 06:25:30 One Connection raised an error

2016-04-25 06:32:46 1.0.25 ERROR 

TCP Client level -- Server/Port:localhost/8009

Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index

2016-04-25 06:32:46 One Connection raised an error

2016-04-25 08:49:17 1.0.25 ERROR 

packet length determination problem

Source array was not long enough. Check srcIndex and length, and the array's lower bounds.

 

Thanks,

Pritesh

[Bilal]

Pritesh:
Can you please post your configurations:
Server.xml
Boncodeajp13.settings (from c:\windows)

[Pritesh Patel]

Hi Bilal,

Sorry for delay in response, somehow didn't receive email for it

Here is Boncodeapj13.settings (from c:\windows) (masked modcfmlsecret key)

<Settings>

<Server>localhost</Server>

<Port>8009</Port>

<EnableRemoteAdmin>True</EnableRemoteAdmin>

<EnableHeaderDataSupport>True</EnableHeaderDataSupport>

<ForceSecureSession>False</ForceSecureSession>

<AllowEmptyHeaders>False</AllowEmptyHeaders>

<ModCFMLSecret>f0633610d962f8******247564c7b789ce38f573f99e2d7e5514959ef******</ModCFMLSecret>

<MaxConnections>500</MaxConnections>

<LogLevel>1</LogLevel>

<LogDir>D:\_logs\boncode</LogDir>

</Settings>

Attached "server.xml" file. 

PS: earlier I do not have maxconnection setup in boncode or server.xml but I was still facing issue. 

[Bilal]

Thanks Pritesh:

Is there a consistent way you can replicate this, e.g. calling a piece of code after a certain time?

Would I be able to setup your environment?

Best,

Bilal

[Pritesh Patel]

Hi Bilal,

No there isn't specific type of code to replicate but the project I use having moderate traffic but there are some pages which taking around 2 mins of time and back end is SQL Server.

For couple of instance it was goes down during that script run but later this wasn't case.

Regards,
Pritesh
Sent from Outlook Mobile

--
You received this message because you are subscribed to a topic in the Google Groups "mod_cfml" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mod_cfml/cE08btyl-_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mod_cfml+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bilal]

Pritesh:

Thanks for the info.

The only way I can replicate this is to turn off Tomcat (shutdown) while it is processing and has active connections to IIS.

Do you or have you ever just restarted tomcat by itself or first? If so you could see messages like this for threads that were forcefully and/or unexpectedly closed. The shutdown sequence should be IIS first, then Tomcat. This will shutdown threads gracefully.

As far as the two minutes is concerned I would ensure that all of your service timeouts are in sync, IIS, Tomcat, Connector, and Lucee. See manual on how to change connector timeout if you are not certain.

I also have a beta available for 1.0.27 if you want to give that a try. It suppresses a lot of the messages that are shutdown related:

http://boncode.net/connector/archive/AJP13_v1027B5.zip

Let me know how it goes.

Best,

Bilal

[Pritesh Patel]

Hi Bilal,

Yes, I had restarted whole server since many time restarting lucee doesn't resolve issue. Yes that can be possible that Tomcat restarted first and then IIS make this happen. I will follow restart sequence now onward and check out if that happen again. Also, check out connector timeout and will implement.

As of now I am not able to implement beta version on production but will check on development server.

Thanks for your help.

Pritesh

[Pritesh Patel]

Hello Bilal,

I am back again but seems different problem though cant' find solution of first one as well. While testing with your beta version (also tested with previous two version as well) I found that I can only send maximum  10 requests at a time. 

Here is what I have done to test.

File used in testing available in below gist.

https://gist.github.com/thecfguy/32a0eb1111cdca9ec2ae51d7bffbc114 

Files:

test.cfm : File which sleep for 10 seconds and complete.

boncode.settings: Having 500 maxconnection

server.xml : have setting maxThread = "500"

Here what I did...

use jMeter to run 500 concurrent requests. 

Case #1 : Use direct request to tomcat with URL http://alpha.test.local:8888/test.cfm. So assuming all requests going to take 10 seconds of time to execute and since I have allowed 500 threads in http connector and all requests completed with in 15 seconds of timespan.

Case#2 : Use request through IIS with URL http://alpha.test.local/test.cfm with maxconnection 500. Not sure 500 connections means 500 thread in Tomcat. When run load test with same amount of requests it running just 10 requests at a time and other 490 maintained in Q. Then next 10 and son on. It almost take around 500 seconds to complete requests.

I have checked in IIS but can't find anykind of restrictions related to 10 threads only. Wondering what is blocking to 10 concurrent connections only.

I think that is what restricting for my project since we have some schedule file running in background which taking around 20 seconds to complete.

Thanks,

Pritesh

[Bilal]

What Windows OS did you use. As far as I understand all workstation editions are restricted in the number of connections. That includes Windows 7, 8, 10.

[Pritesh Patel]

I use window 10. So probably that is reason, I will try to same with development server which use window server 2012 r2.

Regards,
Pritesh
Sent from Outlook Mobile

On Fri, May 13, 2016 at 6:36 AM -0700, "Bilal" <bilal...@gmail.com> wrote:

What Windows OS did you use. As far as I understand all workstation editions are restricted in the number of connections. That includes Windows 7, 8, 10.

-- 
You received this message because you are subscribed to a topic in the Google Groups "mod_cfml" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mod_cfml/cE08btyl-_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mod_cfml+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.