• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Getting jrpp Errors after installing hf900-00002.jar Patch

New Here ,
Feb 09, 2011 Feb 09, 2011

Copy link to clipboard

Copied

I am running the developer edition of Coldfusion 9.0 as a standalone install (Applications/ColdFusion/webroot) on a Macbook Pro running Mac OSX 10.6.6

Per this Article: http://kb2.adobe.com/cps/890/cpsid_89094.html  I installed the security patch.

After restarting, anytime I load pages from a local CF site I am seeing errors like these written over and over in the log:

[localhost]:02/09 12:00:19 Error [jrpp-47] -

[localhost]:02/09 12:00:19 Error [jrpp-47] -

[localhost]:02/09 12:00:19 Error [jrpp-47] -

[localhost]:02/09 12:00:19 Error [jrpp-47] -

[localhost]:02/09 12:00:19 Error [jrpp-47] -

[localhost]:02/09 12:00:19 Error [jrpp-47] -
[localhost]:02/09 12:00:19 Error [jrpp-47] -
[localhost]:02/09 12:00:19 Information [jrpp-47] - onSiteRequest: 502
[localhost]:02/09 12:00:19 Error [jrpp-47] -

AND

[localhost]:02/09 12:01:31 Error [jrpp-49] -
[localhost]:02/09 12:01:31 Error [jrpp-49] -
[localhost]:02/09 12:01:31 Error [jrpp-49] -
[localhost]:02/09 12:01:31 Error [jrpp-49] -
[localhost]:02/09 12:01:31 Error [jrpp-49] -
[localhost]:02/09 12:01:32 Information [jrpp-49] - onSiteRequest: 493

For the Record I have also seen error codes: 41, 37, 21, 33, 23, 35, 46, 50 and so on.

What does these mean and should I be concerned?  Is there anything I can do to prevent these?

Views

1.2K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 10, 2011 Feb 10, 2011

Copy link to clipboard

Copied

I'd recommend that you upgrade to 9.0.1. It may or may not fix this problem, but you should do it anyway.

Dave Watts, CTO, Fig Leaf Software

http://www.figleaf.com/

http://training.figleaf.com/

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 02, 2011 Jun 02, 2011

Copy link to clipboard

Copied

LATEST

For what it's worth, I've seen issues like this with empty try/catch blocks.  IE:

try{

... stuff to try...

} catch(any e){}

Notice that the catch is empty. I've seen cases where that adds these log records.  Adding something like x=1 into the catch has resolved that issue for me. 

That said, I'm working on a project now where I'm seeing a ton of these, but have been unable to find a specific try/catch that is causing this issue. In other words, that might not be the only situation that triggers these.  For the most part they seem harmless, but it would be nice to know what's causing them.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation