Have you viewed the source to your blank page? Do you see the MyFaces
tags? I am having this problem on the Oracle OC4J external server that
comes with JDeveloper. The application starts up fine w/o any error
messages and the requests are getting processed but the tags are not
getting processed so they appear in the source view of the page.
-Richard
mchandir wrote:
I just thought i would update regarding this issue. Damon thanks for taking
time to giving me some suggestions. What i found in all this painful
experiment is i had no luck running the application with Application
Classloader as PARENT_LAST, WAR Classloader policy as MODULE & Web Module
Classloader as PARENT_LAST. I even tried running a simple welcome page
application same behaviour that i was getting blank page. In the trace i can
see the request was getting processed by WAS and getiing dispatched but when
the response is sent i get a blank page (dunno why still remains as a
mystery)
Then i tried setting Application Classloader as PARENT_FIRST and WAR
Classloader policy as APPLICATION and WAR Classloader as PARENT_LAST but ran
into some jdom.jar conflict where i found WAS 5.1.x was loading jdom.jar
(version 0.7 beta) wherea our applicaion needs jdom-1.0.jar. As a workaround
i copied the jdom.jar to application lib folder and was able to successfully
run my application.
This classloading combination is the only combination where i can get the
application up and running successfully.
thought this might help someone who run into the situation.
thanks,
mchandir wrote:
yes i tried including the jar you mentioned no luck :-( would you be able
to confirm that when u deployed in WAS 5.1.x what version of WAS you were
using? What was the enterprise application classloader mode? what was the
WAR classloader policy? and what was the webmodule's Classloader mode?
Becoz if i set the Webmodule's classloader mode to PARENT_FIRST, i was
succesfully able to log in to my application and navigate but having some
java.lang.verifyError errors here and there and i think it is becoz of the
JDOM version conflict as we are bundling our own version. So i would want
to set the classloader mode to PARENT_LAST.
Damon Weyant wrote:
Another quick suggestion:
I was comparing the list of JAR files you have in your application
compared to the applications we have up and running in WebSphere...we
have the commons-el-1.0.jar file in our WEB-INF/lib folder, but that Jar
file was not included in your list of JARs in your application. It's a
shot in the dark, but who knows ;-)
- Damon
-----Original Message-----
From: mchandir [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 31, 2008 2:33 PM
To: [email protected]
Subject: RE: MyFaces 1.1 not working on Websphere 5.1.1.15 with
Classloader set to PARENT_LAST
Thanks for your suggestion. I tried it but still not working. Whatz
annoying is when i hit the url i get a blank page and there is no error
in the log files. while i turned on the trace i see that the request is
getting processed and i also see the response is dispatched properly to
HttpConnection.readAndHandleRequest(): completed dispatch to uri:
/JSF/index.faces but after that i see something strange like this towards
the end of the trace file:
[1/31/08 14:25:08:078 EST] 45410934 HttpRequest < finish
[1/31/08 14:25:08:078 EST] 45410934 HttpConnectio < readAndHandleRequest
[1/31/08 14:25:13:078 EST] 45410934 HttpConnectio d Read timed out
java.net.SocketTimeoutException: Read
timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at
java.net.SocketInputStream.read(SocketInputStream.java(Compiled Code))
at com.ibm.ws.io.Stream.read(Stream.java(Compiled Code))
at com.ibm.ws.io.ReadStream.readBuffer(ReadStream.java(Inlined
Compiled
Code))
at com.ibm.ws.io.ReadStream.read(ReadStream.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:454)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:937)
[1/31/08 14:25:13:078 EST] 45410934 TransportLogg d HttpConnection.run():
socket closed: remotePort=[9837] remoteAddress=[127.0.0.1]
[1/31/08 14:25:13:078 EST] 45410934 HttpServer <
connectionKeepAliveCnt:
count=0
[1/31/08 14:25:13:078 EST] 45410934 HttpConnectio < run
[1/31/08 14:25:13:078 EST] 45410934 InvocationCac >
threadReturned([EMAIL PROTECTED], 1, 50)
[1/31/08 14:25:13:078 EST] 45410934 InvocationCac < threadReturned
I am not sure what this is or is this causing the application not to
function properly. Atleast if i have a error message i will have
something to start looking into but this is really vague and don't know
if the Httpconnection is timing out...
any thoughts?
thanks again
Damon Weyant wrote:
I've had MyFaces application running on WAS v5.1.x before (we're
currently running them in WAS v6.1.x), I know one thing we did was set
the WAR classloader policy from "Module" to "Application" so maybe
that might do the trick for you as well. Hope this helps...
- Damon
-----Original Message-----
From: mchandir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 30, 2008 4:20 PM
To: [email protected]
Subject: MyFaces 1.1 not working on Websphere 5.1.1.15 with
Classloader set to PARENT_LAST
I am trying to deploy a simple MyFaces application on Websphere App
Server
5.1.1.15 and having trouble invoking the index page. I am using
MyFaces
1.1.5 and tomahawk 1.1.6. I also went through this link
http://wiki.apache.org/myfaces/Websphere_Installation and still not
working.
I want my Classloader mode to be PARENT_LAST for both application and
Web Module as my application needs it. This works fine on Websphere
6.0.2. I was able to successfully deploy the application to WAS
5.1.1.15 with one additional jar file (jsp-api.jar) which is not part
of WAS 6.0.2 deployment.
Has anyone successfully deployed MyFaces 1.1 on Websphere 5.1.x? if so
do i need any additonal jar file. Right now i have
commons-beanutils-1.7.0.jar
commons-codec-1.3.jar
commons-collections-3.1.jar
commons-digester-1.6.jar
commons-lang-2.1.jar
commons-fileupload-1.0.jar
commons-validator.jar
jsp-api.jar
jstl-1.0.jar
myfaces-api-1.1.5.jar
myfaces-impl-1.1.5.jar
standard-1.0.jar
tomahawk-1.1.3.jar
The problem i have is when i hit my index page url:
http://localhost:9080/myproj/index.faces i get a blank page and there
is no error message in the logs :-( I have no clue what is happening.
But if i change the Web Module class loader to PARENT_FIRST it is
working fine, but i don't need that.
Any help will be useful as im stuck at this point. thanks in advance
--
View this message in context:
http://www.nabble.com/MyFaces-1.1-not-working-on-Websphere-5.1.1.15-wi
th-Classloader-set-to-PARENT_LAST-tp15192182p15192182.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/MyFaces-1.1-not-working-on-Websphere-5.1.1.15-with-Classloader-set-to-PARENT_LAST-tp15192182p15212943.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
