Bug 158241 - Stop sending newset in request
Stop sending newset in request
Status: CLOSED CURRENTRELEASE
Product: Red Hat Network
Classification: Red Hat
Component: RHN/R&D (Show other bugs)
RHN Devel
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ken Ganong
Vlady Zlatkin
:
Depends On:
Blocks: 151514
  Show dependency treegraph
 
Reported: 2005-05-19 15:57 EDT by Ken Ganong
Modified: 2007-04-18 13:26 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHN 4.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-31 17:08:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Here is the log, note the newset value (252.62 KB, text/plain)
2005-05-19 15:57 EDT, Ken Ganong
no flags Details

  None (edit)
Description Ken Ganong 2005-05-19 15:57:28 EDT
in Java:
We are sending newset in the request which keeps track of the RhnSet.  We should
use the database to take care of newset.

When are sets are too large for a request, here's what we get:
May 19, 2005 3:51:38 PM org.apache.jk.common.MsgAjp cpBytes
SEVERE: Overflow
java.lang.Throwable
    at org.apache.jk.common.MsgAjp.cpBytes(MsgAjp.java:172)
    at org.apache.jk.common.MsgAjp.appendByteChunk(MsgAjp.java:146)
    at org.apache.jk.common.MsgAjp.appendBytes(MsgAjp.java:132)
    at org.apache.jk.server.JkCoyoteHandler.appendHead(JkCoyoteHandler.java:398)
    at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:416)
    at org.apache.coyote.Response.action(Response.java:182)
    at org.apache.coyote.Response.sendHeaders(Response.java:374)
    at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:321)
    at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:282)
    at
org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:476)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:163)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
    at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
Comment 1 Ken Ganong 2005-05-19 15:57:31 EDT
Created attachment 114586 [details]
Here is the log, note the newset value
Comment 2 Ken Ganong 2005-05-24 08:29:48 EDT
Now instead of chaining newset continuously through the request, we simply
commit to the database.
Comment 3 Jesus M. Rodriguez 2005-06-10 14:34:04 EDT
Mass moving ON_DEV to ON_QA
Comment 4 Vlady Zlatkin 2005-07-03 17:53:31 EDT
fails qa b/c there is no testplan, please add
Comment 5 Ken Ganong 2005-07-05 09:48:26 EDT
TEST PLAN:
Go to a list display page with a set and checkboxes, example:
/rhn/systems/details/packages/PackageList.do?sid=XXX.
Select some items in the set.
Paginate.
Select some more items.
Paginate.

During the above process, there should be no request content named newset
because newset has the potential to get very large.  items_on_page is the
acceptable similar content (in case you need a reference).
Comment 6 Vlady Zlatkin 2005-07-06 17:01:17 EDT
prod ready

Note You need to log in before you can comment on or make changes to this bug.