[
https://issues.apache.org/jira/browse/TRINIDAD-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758466#action_12758466
]
Don Kleppinger edited comment on TRINIDAD-1540 at 9/22/09 3:50 PM:
-------------------------------------------------------------------
We are seeing a similar issue on Oracle 11g where when we start-up our weblogic
managed servers (we have 12), one of the JVMs gets this error and any attempt
to load pages from that JVM get this error in the response http header
<!--ERROR: could not create stylesheet for skins/CustomSkin/SkinBasic.css-->.
When we go to a good jvm and retrieve the page it works fine and we can see the
url of the actual css it is loading. When we use that url on the bad jvm we
can retrieve it fine, but somehow the jvm has cached state and thinks the css
is not available so returns that error in the header. The problem goes away
when we restart the particular weblogic server having the problem.
was (Author: c094728):
We are seeing a similar issue on 11g where when we start-up our weblogic
managed servers (we have 12), one of the JVMs gets this error and any attempt
to load pages from that JVM get this error in the response http header
<!--ERROR: could not create stylesheet for skins/CustomSkin/SkinBasic.css-->.
When we go to a good jvm and retrieve the page it works fine and we can see the
url of the actual css it is loading. When we use that url on the bad jvm we
can retrieve it fine, but somehow the jvm has cached state and thinks the css
is not available so returns that error in the header. The problem goes away
when we restart the particular weblogic server having the problem.
> Unable to generate the style sheet test-desktop-q1tmkf-en-ie-6-cmp.css in
> cache directory
> -----------------------------------------------------------------------------------------
>
> Key: TRINIDAD-1540
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1540
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Skinning
> Affects Versions: 1.0.4-core
> Environment: WebSphere 6.1 application server
> Reporter: Sanjay Kammili
>
> When we are trying to access the jspx pages after deploying the application
> getting the below error.
> [7/26/09 4:17:30:217 CDT] 0000007a FileSystemSty W
> org.apache.myfaces.trinidadinternal.style.cache.FileSystemStyleCache
> _createStyleSheetFile
> Unable to generate the style sheet test-desktop-q1tmkf-en-ie-6-cmp.css in
> cache directory
> /apps/WebSphere/AppServer61/profiles/sawprdfdn/temp/ncdww-prd1941sawprdfdnnode/sawprd_swfdn1941_server01/chordiant/Advisor.war/adf/styles/cache.
> Please make sure that the cache directory exists and is writable.
> Due to this we are not able to load the styles to the application.The
> trinidad components are coming in different sytles than correct ones.
> We are using the follwing jars.
> myfaces-api-1.1.5.jar
> myfaces-impl-1.1.5.jar
> trinidad-api-1.0.4-SNAPSHOT.jar
> trinidad-impl-1.0.4-SNAPSHOT.jar
> jsf-facelets-1.1.11.jar
> Normal fonts are coming in BOLD and BOLD are coming in normal.Tr:table
> horizontal lines are disappearing.
> Could you help me to resolve the issue.
> Thanks,
> Sanjay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
