tcpproxy 'failed to connect' errors

View: New views
7 Messages — Rating Filter:   Alert me  

tcpproxy 'failed to connect' errors

by Lisa Davis-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa

 

 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Re: tcpproxy 'failed to connect' errors

by Anirvan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

When you mention “I’ve reset my proxy to localhost:8001”, you mean the proxy settings in your browser right?

 

As far as I remember, I overrode the proxy settings of my browser to use HTTP Proxy: localhost, using port: 8001. Thereafter, I launched the TCPProxy application and then accessed any website for which I needed to record a browsing session.

 

Are you doing all these things as well?

 

From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: 11 September 2009 02:11
To: grinder-use@...
Subject: [Grinder-use] tcpproxy 'failed to connect' errors

 

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa

 

 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Re: tcpproxy 'failed to connect' errors

by Lisa Davis-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Yes, I meant resetting the proxy settings in my browser.  Sorry about that, I should have been more clear.  It seems like it should be relatively straight forward but I’m not able to access those third-party libs once the TCPProxy app is launched.  Just curious but when you say that you “…then accessed any website for which I needed to record a browsing session…”, were you referring to Intranet or Internet sites?

 


From: Anirvan Majumdar [mailto:anirvan.majumdar@...]
Sent: Thursday, September 10, 2009 2:58 PM
To: 'grinder-use'
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

When you mention “I’ve reset my proxy to localhost:8001”, you mean the proxy settings in your browser right?

 

As far as I remember, I overrode the proxy settings of my browser to use HTTP Proxy: localhost, using port: 8001. Thereafter, I launched the TCPProxy application and then accessed any website for which I needed to record a browsing session.

 

Are you doing all these things as well?

 

From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: 11 September 2009 02:11
To: grinder-use@...
Subject: [Grinder-use] tcpproxy 'failed to connect' errors

 

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa

 

 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Re: tcpproxy 'failed to connect' errors

by Lisa Davis-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

I think I know what’s wrong but I will likely need to add network authentication information to get this to work.  What file(s) would I put that info in?

 


From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: Thursday, September 10, 2009 3:06 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

Yes, I meant resetting the proxy settings in my browser.  Sorry about that, I should have been more clear.  It seems like it should be relatively straight forward but I’m not able to access those third-party libs once the TCPProxy app is launched.  Just curious but when you say that you “…then accessed any website for which I needed to record a browsing session…”, were you referring to Intranet or Internet sites?

 


From: Anirvan Majumdar [mailto:anirvan.majumdar@...]
Sent: Thursday, September 10, 2009 2:58 PM
To: 'grinder-use'
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

When you mention “I’ve reset my proxy to localhost:8001”, you mean the proxy settings in your browser right?

 

As far as I remember, I overrode the proxy settings of my browser to use HTTP Proxy: localhost, using port: 8001. Thereafter, I launched the TCPProxy application and then accessed any website for which I needed to record a browsing session.

 

Are you doing all these things as well?

 

From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: 11 September 2009 02:11
To: grinder-use@...
Subject: [Grinder-use] tcpproxy 'failed to connect' errors

 

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa

 

 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Re: tcpproxy 'failed to connect' errors

by Lisa Davis-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

I have it working now and I can get to the Internet and roam around, but when I try to hit our customer-facing web site from the Internet, this error shows up in the stacktrace.  I’m not even sure it’s negatively impacting anything but I can’t say that I really know what I’m doing yet either.  Has anyone ever seen this and what is the cause, impact, and resolution?

 

Thanks,

Lisa

 

 

Exception in thread "HTTPProxyStreamDemultiplexer for Socket[addr=localhost/127.

0.0.1,port=3136,localport=8001]" java.lang.IllegalStateException: No match found

 

        at java.util.regex.Matcher.group(Unknown Source)

        at net.grinder.util.URIParserImplementation.parse(URIParserImplementatio

n.java:76)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Response$ResponseBody.end(ConnectionHandlerImplementation.java:660)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Response.end(ConnectionHandlerImplementation.java:601)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Request.end(ConnectionHandlerImplementation.java:427)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n.requestFinished(ConnectionHandlerImplementation.java:330)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionCache.close(Connecti

onCache.java:129)

        at net.grinder.plugin.http.tcpproxyfilter.HTTPRequestFilter.connectionCl

osed(HTTPRequestFilter.java:99)

        at net.grinder.tools.tcpproxy.CompositeFilter.connectionClosed(Composite

Filter.java:104)

        at net.grinder.tools.tcpproxy.AbstractFilterDecorator.connectionClosed(A

bstractFilterDecorator.java:75)

        at net.grinder.tools.tcpproxy.AbstractFilterDecorator.connectionClosed(A

bstractFilterDecorator.java:75)

        at net.grinder.tools.tcpproxy.AbstractTCPProxyEngine$OutputStreamFilterT

ee.connectionClosed(AbstractTCPProxyEngine.java:572)

        at net.grinder.tools.tcpproxy.HTTPProxyTCPProxyEngine$HTTPProxyStreamDem

ultiplexer.interruptibleRun(HTTPProxyTCPProxyEngine.java:568)

        at net.grinder.util.thread.InterruptibleRunnableAdapter.run(Interruptibl

eRunnableAdapter.java:59)

        at java.lang.Thread.run(Unknown Source)

 

 

 


From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: Thursday, September 10, 2009 4:17 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

I think I know what’s wrong but I will likely need to add network authentication information to get this to work.  What file(s) would I put that info in?

 


From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: Thursday, September 10, 2009 3:06 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

Yes, I meant resetting the proxy settings in my browser.  Sorry about that, I should have been more clear.  It seems like it should be relatively straight forward but I’m not able to access those third-party libs once the TCPProxy app is launched.  Just curious but when you say that you “…then accessed any website for which I needed to record a browsing session…”, were you referring to Intranet or Internet sites?

 


From: Anirvan Majumdar [mailto:anirvan.majumdar@...]
Sent: Thursday, September 10, 2009 2:58 PM
To: 'grinder-use'
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

When you mention “I’ve reset my proxy to localhost:8001”, you mean the proxy settings in your browser right?

 

As far as I remember, I overrode the proxy settings of my browser to use HTTP Proxy: localhost, using port: 8001. Thereafter, I launched the TCPProxy application and then accessed any website for which I needed to record a browsing session.

 

Are you doing all these things as well?

 

From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: 11 September 2009 02:11
To: grinder-use@...
Subject: [Grinder-use] tcpproxy 'failed to connect' errors

 

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa

 

 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Re: tcpproxy 'failed to connect' errors

by Anirban Majumdar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

This error means that a Java regular expression did not match the input text.

A call to Matcher.group() was made although a previous .find() or .match() didn't find anything. But then, considering it occurred within the Grinder API @ URIParserImplementation – it might be that there is something about your client’s web-application’s URI which leads to this problem.

 

I fear I’m not in a position to accurately discuss about the impact and resolution of this problem. Probably someone from Grinder’s core dev team will be able to help you better.

 

---------

anirvan

 


From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: Friday, September 11, 2009 6:00 AM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

I have it working now and I can get to the Internet and roam around, but when I try to hit our customer-facing web site from the Internet, this error shows up in the stacktrace.  I’m not even sure it’s negatively impacting anything but I can’t say that I really know what I’m doing yet either.  Has anyone ever seen this and what is the cause, impact, and resolution?

 

Thanks,

Lisa

 

 

Exception in thread "HTTPProxyStreamDemultiplexer for Socket[addr=localhost/127.

0.0.1,port=3136,localport=8001]" java.lang.IllegalStateException: No match found

 

        at java.util.regex.Matcher.group(Unknown Source)

        at net.grinder.util.URIParserImplementation.parse(URIParserImplementatio

n.java:76)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Response$ResponseBody.end(ConnectionHandlerImplementation.java:660)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Response.end(ConnectionHandlerImplementation.java:601)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Request.end(ConnectionHandlerImplementation.java:427)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n.requestFinished(ConnectionHandlerImplementation.java:330)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionCache.close(Connecti

onCache.java:129)

        at net.grinder.plugin.http.tcpproxyfilter.HTTPRequestFilter.connectionCl

osed(HTTPRequestFilter.java:99)

        at net.grinder.tools.tcpproxy.CompositeFilter.connectionClosed(Composite

Filter.java:104)

        at net.grinder.tools.tcpproxy.AbstractFilterDecorator.connectionClosed(A

bstractFilterDecorator.java:75)

        at net.grinder.tools.tcpproxy.AbstractFilterDecorator.connectionClosed(A

bstractFilterDecorator.java:75)

        at net.grinder.tools.tcpproxy.AbstractTCPProxyEngine$OutputStreamFilterT

ee.connectionClosed(AbstractTCPProxyEngine.java:572)

        at net.grinder.tools.tcpproxy.HTTPProxyTCPProxyEngine$HTTPProxyStreamDem

ultiplexer.interruptibleRun(HTTPProxyTCPProxyEngine.java:568)

        at net.grinder.util.thread.InterruptibleRunnableAdapter.run(Interruptibl

eRunnableAdapter.java:59)

        at java.lang.Thread.run(Unknown Source)

 

 

 


From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: Thursday, September 10, 2009 4:17 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

I think I know what’s wrong but I will likely need to add network authentication information to get this to work.  What file(s) would I put that info in?

 


From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: Thursday, September 10, 2009 3:06 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

Yes, I meant resetting the proxy settings in my browser.  Sorry about that, I should have been more clear.  It seems like it should be relatively straight forward but I’m not able to access those third-party libs once the TCPProxy app is launched.  Just curious but when you say that you “…then accessed any website for which I needed to record a browsing session…”, were you referring to Intranet or Internet sites?

 


From: Anirvan Majumdar [mailto:anirvan.majumdar@...]
Sent: Thursday, September 10, 2009 2:58 PM
To: 'grinder-use'
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

When you mention “I’ve reset my proxy to localhost:8001”, you mean the proxy settings in your browser right?

 

As far as I remember, I overrode the proxy settings of my browser to use HTTP Proxy: localhost, using port: 8001. Thereafter, I launched the TCPProxy application and then accessed any website for which I needed to record a browsing session.

 

Are you doing all these things as well?

 

From: Lisa Davis [mailto:Lisa.Davis@...]
Sent: 11 September 2009 02:11
To: grinder-use@...
Subject: [Grinder-use] tcpproxy 'failed to connect' errors

 

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa

 

 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Re: tcpproxy 'failed to connect' errors

by Philip Aston-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
I'm interested in the URI that failed to parse.

Please add the attached patch to the beginning of your CLASSPATH and re-run your test. This will include the URI in the exception.

Thanks,

- Phil

Anirban Majumdar wrote:

This error means that a Java regular expression did not match the input text.

A call to Matcher.group() was made although a previous .find() or .match() didn't find anything. But then, considering it occurred within the Grinder API @ URIParserImplementation – it might be that there is something about your client’s web-application’s URI which leads to this problem.

 

I fear I’m not in a position to accurately discuss about the impact and resolution of this problem. Probably someone from Grinder’s core dev team will be able to help you better.

 

---------

anirvan

 


From: Lisa Davis [Lisa.Davis@...]
Sent: Friday, September 11, 2009 6:00 AM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

I have it working now and I can get to the Internet and roam around, but when I try to hit our customer-facing web site from the Internet, this error shows up in the stacktrace.  I’m not even sure it’s negatively impacting anything but I can’t say that I really know what I’m doing yet either.  Has anyone ever seen this and what is the cause, impact, and resolution?

 

Thanks,

Lisa

 

 

Exception in thread "HTTPProxyStreamDemultiplexer for Socket[addr=localhost/127.

0.0.1,port=3136,localport=8001]" java.lang.IllegalStateException: No match found

 

        at java.util.regex.Matcher.group(Unknown Source)

        at net.grinder.util.URIParserImplementation.parse(URIParserImplementatio

n.java:76)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Response$ResponseBody.end(ConnectionHandlerImplementation.java:660)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Response.end(ConnectionHandlerImplementation.java:601)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n$Request.end(ConnectionHandlerImplementation.java:427)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionHandlerImplementatio

n.requestFinished(ConnectionHandlerImplementation.java:330)

        at net.grinder.plugin.http.tcpproxyfilter.ConnectionCache.close(Connecti

onCache.java:129)

        at net.grinder.plugin.http.tcpproxyfilter.HTTPRequestFilter.connectionCl

osed(HTTPRequestFilter.java:99)

        at net.grinder.tools.tcpproxy.CompositeFilter.connectionClosed(Composite

Filter.java:104)

        at net.grinder.tools.tcpproxy.AbstractFilterDecorator.connectionClosed(A

bstractFilterDecorator.java:75)

        at net.grinder.tools.tcpproxy.AbstractFilterDecorator.connectionClosed(A

bstractFilterDecorator.java:75)

        at net.grinder.tools.tcpproxy.AbstractTCPProxyEngine$OutputStreamFilterT

ee.connectionClosed(AbstractTCPProxyEngine.java:572)

        at net.grinder.tools.tcpproxy.HTTPProxyTCPProxyEngine$HTTPProxyStreamDem

ultiplexer.interruptibleRun(HTTPProxyTCPProxyEngine.java:568)

        at net.grinder.util.thread.InterruptibleRunnableAdapter.run(Interruptibl

eRunnableAdapter.java:59)

        at java.lang.Thread.run(Unknown Source)

 

 

 


From: Lisa Davis [Lisa.Davis@...]
Sent: Thursday, September 10, 2009 4:17 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

I think I know what’s wrong but I will likely need to add network authentication information to get this to work.  What file(s) would I put that info in?

 


From: Lisa Davis [Lisa.Davis@...]
Sent: Thursday, September 10, 2009 3:06 PM
To: grinder-use
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

Yes, I meant resetting the proxy settings in my browser.  Sorry about that, I should have been more clear.  It seems like it should be relatively straight forward but I’m not able to access those third-party libs once the TCPProxy app is launched.  Just curious but when you say that you “…then accessed any website for which I needed to record a browsing session…”, were you referring to Intranet or Internet sites?

 


From: Anirvan Majumdar [anirvan.majumdar@...]
Sent: Thursday, September 10, 2009 2:58 PM
To: 'grinder-use'
Subject: Re: [Grinder-use] tcpproxy 'failed to connect' errors

 

When you mention “I’ve reset my proxy to localhost:8001”, you mean the proxy settings in your browser right?

 

As far as I remember, I overrode the proxy settings of my browser to use HTTP Proxy: localhost, using port: 8001. Thereafter, I launched the TCPProxy application and then accessed any website for which I needed to record a browsing session.

 

Are you doing all these things as well?

 

From: Lisa Davis [Lisa.Davis@...]
Sent: 11 September 2009 02:11
To: grinder-use@...
Subject: [Grinder-use] tcpproxy 'failed to connect' errors

 

Hello,

 

I’m very new to Grinder and am in need of some guidance, and I apologize upfront if this seems elementary.  I’m trying to use the TCPProxy tool to record some user interactions with my company’s web site, so I can conduct some load, capacity, and stress testing.  I’ve reset my proxy to localhost:8001 as the directions instructed.  When I initialize the TCPProxy to record the session though (yes I have set my classpath), I immediately get a 502 connection refused – failed to connect error. 

 

I should explain that we use third-party JS and CSS libraries from google and yahoo.  Upon setting my proxy to localhost:8001, with NO TCPProxy initialized, I get this: I can go through the basics of a login and navigation of the site and it works just fine—no errors.  But, with the TCPProxy initialized I get this:  I immediately get a 502 error telling me failed to connect to… and connection refused. 

 

This is the exact error message (with multiple iterations): Failed to connect to www.google-analytics.com:80, and (Connection refused: connect).

 

I’m obviously at a loss and am under a very aggressive timeline.  If I can provide any more info or anyone has any questions, please let me know.  Any assistance anyone can provide would be very much appreciated. 

 

Best,

 

Lisa




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

debug-uri-parse.jar (5K) Download Attachment