[KULRICE-4656] Maintenance/Transactional screen's images are being served from standalone rice server Created: 06/Oct/10  Updated: 10/Jul/12  Resolved: 10/Jul/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: KC Release 3.0, 1.0.3
Fix Version/s: KC Release 3.0, 1.0.3

Type: Improvement Priority: Major
Reporter: Travis Schneeberger Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Similar issues:
KULRICE-7354Standalone server is attempting to load remotable attributes locally
KULRICE-6993KNS Infrastructure not supporting quickfinder lookups against standalone Rice server
KULRICE-3815Expanding pages when using standalone Rice
KULRICE-2855Document Kuali Rice Standalone Server installation and configuration
KULRICE-2932rice-config.xml for deployment of standalone server
KULRICE-2764Deploy Rice standalone server to our test environments
KULRICE-6329Remove KRAD tab from standalone
KULRICE-9899Add documentation to IG on how to configure an application to work with Rice standalone server
KULRICE-6749Configure rice sample app as a client app running against a standalone server
KULRICE-2864Set up clustering for the Rice standalone servers
Rice Module:
Application Requirement:
KAI Review Status: Not Required
KTI Review Status: Not Required


We noticed today we our standalone rice server went down in one of our testing environments all the standard images on a maintenance & trans doc screen were broken. This is because the images were being served from the standalone rice server rather than the client application. This really should not be this way because
1) the client apps have all the images so these client screens should use them
2) the rice server doesn't need to be put under the additional load of serving up static content for all client applications
3) there are probably other reasons why this is a bad idea that I'm not thinking of

See linked issue for more details.

Comment by Travis Schneeberger [ 06/Oct/10 ]

it appears that this is a problem with our configuration....

Comment by Jessica Coltrin (Inactive) [ 03/Jul/12 ]

reopening to set fix version to something other than 1.x-backlog.

Comment by Jessica Coltrin (Inactive) [ 10/Jul/12 ]


Generated at Fri May 29 19:05:00 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.