Hi Michael,

We looked at the logs and saw that the client side cookie handling has a
problem.

There is already an issue: https://www.canoo.com/jira/browse/UBA-7034 .

The work around is that when you use Java 5 use the Java's cookie management
instead of ULC's cookie management in DefaultJNLPLauncher.

So you need to adapt the DefaultJNLPLauncher to use the
AppletRequestPropertyStore(instead of the CookieRequestPropertyStore). The
AppletRequestPropertyStore does not send along the cookie but relies on the
browser to do this. This is exactly what we want because Java WebStart also
manages cookies as of Java 5.

See if the above change works for you with Java 5 on the client side.
However, this change will not allow your client ot run with Java 1.4.

If it works with Java 5, then change the change the DefaultJNLPLauncher to
create the
AppletRequestPropertyStore if running under Java 5 and the
CookieRequestPropertyStore under Java 1.4.

I hope this helps.

Thanks and regards,

Janak

>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of
>[EMAIL PROTECTED]
>Sent: Monday, October 30, 2006 11:01 PM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED] Com; [EMAIL PROTECTED]
>Subject: RE: [ULC-developer] ULC Servlet Error in Oracle App Server
>
>
>Janak,
>
>I found out some more information on the problem we are seeing.  One thing
>I have noted is that if I set my client side web start properties to point
>to a 1.4.2 JRE then the application runs fine.  If I set the web start
>system to point to a 1.5 JRE then  I get the error I was seeing.  So
>basically this error only appears when I use a 1.5 JRE on the client side.
> It should be noted that the server side app server is running in a 1.4.2
>JDK.  I would expect that I could run 1.4.2 on the server side and 1.5 on
>the client side with out an issue.
>
>Here are the two log files:
>
>
>
>
>Michael MacFadden
>Tomax Corp - http://www.tomax.com
>[EMAIL PROTECTED]
>
>[EMAIL PROTECTED] wrote on 10/30/2006 09:48:55 AM:
>
>> Janak,
>>
>> This is how I have the properties set up in the server and client files.
>I
>> think the issue is with the java logging framework for web start.  It
>> seems to be defaulting the logging format to XML instead of plain text.
>> When I set the java console to display when the webstart launches, the
>> output there is plain text, however the webstart log file that is
>created
>> on disk is in xml format.  The is probably a configuration some where I
>> can set to make that plain text as well.  I would just copy from the
>java
>> console itself, but the ulc error dialogs are modal over the top of it
>so
>> I cannot interact with the java console directly.  As soon as I clear
>the
>> ulc error dialog the application quits and the java console disappears.
>>
>> I will get the files to you ASAP thanks.
>>
>>
>> Michael MacFadden
>> Tomax Corp - http://www.tomax.com
>> [EMAIL PROTECTED]
>>
>>
>> "Janak Mulani" <[EMAIL PROTECTED]> wrote on 10/30/2006 09:24:34 AM:
>>
>> > Hi Michael,
>> >
>> > The client-side log should be text and should look like the
>server-side
>> log
>> > that you sent.
>> >
>> > In your jnlp file:
>> >
>> >  <application-desc
>> > main-class="com.ulcjava.environment.jnlp.client.DefaultJnlpLauncher">
>> >         <argument>url-string=$$context/yourapp.ulc</argument>
>> >         <argument>keep-alive-interval=900</argument>
>> > >>>>>   <argument>log-level=ALL</argument>
>> >   </application-desc>
>> >
>> >
>> > In your web.xml:
>> >
>> >  <servlet>
>> >         <servlet-name>Application</servlet-name>
>> > <servlet-class>com.ulcjava.container.servlet.server.ServletContainer
>> > Adapter</servlet-class>
>> >         <init-param>
>> >             <param-name>application-class</param-name>
>> >             <param-value>com.yourapp.App</param-value>
>> >         </init-param>
>> >         <init-param>
>> >             <param-name>log-level</param-name>
>> > >>>>        <param-value>ALL</param-value>
>> >         </init-param>
>> >     </servlet>
>> >
>> > Thanks and regards,
>> >
>> > Janak
>> >
>> > >-----Original Message-----
>> > >From: [EMAIL PROTECTED]
>> > >[mailto:[EMAIL PROTECTED] Behalf Of
>> > >[EMAIL PROTECTED]
>> > >Sent: Monday, October 30, 2006 9:23 PM
>> > >To: Janak Mulani
>> > >Cc: [email protected]
>> > >Subject: RE: [ULC-developer] ULC Servlet Error in Oracle App Server
>> > >
>> > >
>> > >Hi,
>> > >
>> > >I have still been working on this issue.  I will send you the log
>files
>> > >today.  The only thing I wanted to ask is that the log file on the
>> client
>> > >side seem to come out in an XML format and not a plain text format.
>Is
>> > >this acceptable or do I need to do something different.  I checked on
>
>> our
>> > >deployment config and there is no clustering or load balancing.  I
>also
>> > >believe that the server side http session is set to 1200 seconds and
>> the
>> > >ulc keep alive interval is at 900 seconds.  In either case the error
>I
>> am
>> > >getting happens as soon as the application launches (before any UI
>> shows
>> > >up/within maybe 10 seconds of the web start launching) so I doubt it
>is
>> a
>> > >time out issue.
>> > >
>> > >Let me know if the xml log file is ok.  Thanks.
>> > >
>> > >
>> > >Michael MacFadden
>> > >Tomax Corp - http://www.tomax.com
>> > >[EMAIL PROTECTED]
>> > >
>> > >"Janak Mulani" <[EMAIL PROTECTED]> wrote on 10/26/2006 11:41:41
>> AM:
>> > >
>> > >> Hi Michael,
>> > >>
>> > >> Could you please also send the corresponding client side log too
>(set
>> in
>> > >the
>> > >> JNLP file for the ULC client)? Please send the server and client
>side
>> > >logs
>> > >> from the same run.
>> > >>
>> > >> Are you using clustering for load-balancing in your Oracle App
>> Server?
>> > >Does
>> > >> your configuration  specify the sessions to be sticky, i.e., that
>> > >requests
>> > >> of the same session should always be forwarded to the same
>instance?
>> > >>
>> > >> There is another possibility that your ULC session really
>timed-out.
>> > >(You
>> > >> must make sure that the polling-interval in the deployment
>descriptor
>> > >for
>> > >> the ULC application is shorter than the session timeout in your app
>> > >server
>> > >> instances.)
>> > >>
>> > >> Thanks and regards,
>> > >>
>> > >> Janak
>> > >>
>> > >> >-----Original Message-----
>> > >> >From: [EMAIL PROTECTED]
>> > >> >[mailto:[EMAIL PROTECTED] Behalf Of
>> > >> >[EMAIL PROTECTED]
>> > >> >Sent: Thursday, October 26, 2006 8:32 PM
>> > >> >To: [email protected]
>> > >> >Subject: RE: [ULC-developer] ULC Servlet Error in Oracle App
>Server
>> > >> >
>> > >> >
>> > >> >Rolf,
>> > >> >
>> > >> >I have attached the server side log with the log level set to
>FINEST
>> as
>> > >> >you requested.  There is a lot more information now.  I still
>don't
>> see
>> > >a
>> > >> >glaring error anywhere, however I am not an expert at reading the
>> debug
>> > >> >output from ULC.  It looks like everything is working fine and
>then
>> it
>> > >> >just dies.  I hope the log file helps.  I have been double
>checking
>> the
>> > >> >config and deployment.  As I mentioned in another part of this
>> thread,
>> > >the
>> > >> >ear file worked just fine in JBoss and also in the stand alone
>> version
>> > >of
>> > >> >OC4J.  Just when I deploy in the full blown oracle app server does
>
>> it
>> > >die.
>> > >> >
>> > >> >Hopefully the log file will help figure out what the issue is.
>> Thanks.
>> > >> >
>> > >> >
>> > >> >Michael MacFadden
>> > >> >Tomax Corp - http://www.tomax.com
>> > >> >[EMAIL PROTECTED]
>> > >> >
>> > >> >
>> > >> >
>> > >> >[EMAIL PROTECTED] wrote on 10/25/2006 03:47:54
>AM:
>> > >> >
>> > >> >> Hi Michael
>> > >> >>
>> > >> >> This error occurs if the ULC framework cannot find an already
>> running
>> > >> >ULC
>> > >> >> session.
>> > >> >>
>> > >> >> On the initial HTTP request, a new ULC session is created,
>stored
>> > >inside
>> > >> >the
>> > >> >> HttpSession, and a ULC session id is assigned (there might be
>more
>> > >> >> than one ULC
>> > >> >> session in one HTTP session). With every following HTTP request
>> this
>> > >> >> ULC session
>> > >> >> id is sent along. The application server now first looks up the
>> > >correct
>> > >> >HTTP
>> > >> >> session, and then the ULC framework looks up the ULC session
>> inside
>> > >this
>> > >> >HTTP
>> > >> >> session.
>> > >> >>
>> > >> >> So, either you do not get back the correct HTTP session (e.g.,
>the
>> > >old
>> > >> >one has
>> > >> >> been invalidated), or the ULC session has been cleared away.
>> > >> >>
>> > >> >> If you need more help on this, please set the log level to
>FINEST
>> for
>> > >> >the
>> > >> >> server-side log (in the web.xml file) and send us the log file.
>> > >> >>
>> > >> >> Cheers
>> > >> >> Rolf
>> > >> >>
>> > >> >> **************************************
>> > >> >> Rolf Pfenninger
>> > >> >> Canoo Engineering AG
>> > >> >> Kirschgartenstrasse 7
>> > >> >> CH-4051 Basel
>> > >> >> Tel +41 61 228 9444
>> > >> >> Fax +41 61 228 9449
>> > >> >> mailto:[EMAIL PROTECTED]
>> > >> >> http://www.canoo.com
>> > >> >>
>> > >> >> ULC - Rich Clients for J2EE
>> > >> >> http://www.canoo.com/ulc
>> > >> >> **************************************
>> > >> >>
>> > >> >>
>> > >> >> -----Original Message-----
>> > >> >> From: [EMAIL PROTECTED]
>> > >> >> [mailto:[EMAIL PROTECTED] Behalf Of
>> > >> >> [EMAIL PROTECTED]
>> > >> >> Sent: Dienstag, 24. Oktober 2006 19:07
>> > >> >> To: [email protected]
>> > >> >> Subject: [ULC-developer] ULC Servlet Error in Oracle App Server
>> > >> >>
>> > >> >>
>> > >> >> Hello,
>> > >> >>
>> > >> >> I am trying to run a ULC application in Oracle App Server 10gR2.
>I
>> > >have
>> > >> >> the application working via a web start in OC4J on my desktop.
>> > >However
>> > >> >> when I deploy the same ear file to the App Server I get the
>> following
>> > >> >two
>> > >> >> exceptions when I try to launch my app:
>> > >> >>
>> > >> >> "OC4J~ism_ulc~default_island~1" 186 lines, 14743 characters
>> > >> >>         at
>> > >> >>
>> > >>
>> >
>>
>>>com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.
>java:224)
>> > >> >>         at
>> > >> >>
>> > >>
>> >
>>
>>>com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.
>java:133)
>> > >> >>         at
>> > >> >> com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.
>> > >> >> run(ReleasableResour
>> > >> >> cePooledExecutor.java:186)
>> > >> >>         at java.lang.Thread.run(Thread.java:534)
>> > >> >> ]
>> > >> >> 06/10/19 12:38:09 2      19.10.2006 12:38:09.394        1,000
>> SEVERE
>> > >> >> Thread[AJPRequestHandler-ApplicationServerThread-7,5,Applica
>> > >> >> tionServerThreadGroup]
>> > >> >>
>com.ulcjava.container.servlet.server.ServletContainerAdapterHelper
>> b
>> > >> >>     got servlet exception while
>> > >> >> processing      [javax.servlet.ServletException: unable to get
>ulc
>> > >> >session
>> > >> >> (session already terminated)
>> > >> >>         at
>> > >> >> com.ulcjava.container.servlet.server.ContainerCommand.
>> > >> >> getUlcSession(ContainerCom
>> > >> >> mand.java:27)
>> > >> >>         at
>> > >> >> com.ulcjava.container.servlet.server.RemoveSessionCommand.
>> > >> >> handleRequestContent(R
>> > >> >> emoveSessionCommand.java:10)
>> > >> >>         at
>> > >> >> com.ulcjava.container.servlet.server.ContainerCommand.
>> > >> >> execute(ContainerCommand.j
>> > >> >> ava:43)
>> > >> >>         at
>> > >> >>
>> com.ulcjava.container.servlet.server.ServletContainerAdapterHelper.
>> > >> >> b(ServletCont
>> > >> >> ainerAdapterHelper.java:175)
>> > >> >>         at
>> > >> >>
>> com.ulcjava.container.servlet.server.ServletContainerAdapterHelper.
>> > >> >> service(Servl
>> > >> >> etContainerAdapterHelper.java:86)
>> > >> >>         at
>> > >> >> com.ulcjava.container.servlet.server.ServletContainerAdapter.
>> > >> >> service(ServletCont
>> > >> >> ainerAdapter.java:1)
>> > >> >>         at
>> > >javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>> > >> >>         at
>> > >> >> com.evermind.server.http.ServletRequestDispatcher.
>> > >> >> invoke(ServletRequestDispatche
>> > >> >> r.java:824)
>> > >> >>         at
>> > >> >> com.evermind.server.http.ServletRequestDispatcher.
>> > >> >> forwardInternal(ServletRequest
>> > >> >> Dispatcher.java:330)
>> > >> >>         at
>> > >> >> com.evermind.server.http.HttpRequestHandler.
>> > >> >> processRequest(HttpRequestHandler.ja
>> > >> >> va:830)
>> > >> >>         at
>> > >> >>
>> > >>
>> >
>>
>>>com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.
>java:224)
>> > >> >>         at
>> > >> >>
>> > >>
>> >
>>
>>>com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.
>java:133)
>> > >> >>         at
>> > >> >> com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.
>> > >> >> run(ReleasableResour
>> > >> >> cePooledExecutor.java:186)
>> > >> >>         at java.lang.Thread.run(Thread.java:534)
>> > >> >>
>> > >> >> It should be noted that the web start downloads sucessfully
>along
>> > >with
>> > >> >all
>> > >> >> the client jars.  This error looks like the ulc servlet is
>having
>> a
>> > >> >> problem when the jnlp lunacher is trying to compunicate back to
>> the
>> > >> >server
>> > >> >> side to bootstrap the application.  This happens the first time
>> the
>> > >> >> application is run after restarting the app server as well as on
>> > >> >> subsequent attempts.  I realize this might be a configuration
>> issue
>> > >with
>> > >> >> my app server, however I am looking for suggestions on what
>kinds
>> of
>> > >> >> things can cause this error.. or at least what this error means.
>> > >Thanks.
>> > >> >>
>> > >> >>
>> > >> >> Michael MacFadden
>> > >> >> Tomax Corp - http://www.tomax.com
>> > >> >> [EMAIL PROTECTED]
>> > >> >> _______________________________________________
>> > >> >> ULC-developer mailing list
>> > >> >> [email protected]
>> > >> >> http://lists.canoo.com/mailman/listinfo/ulc-developer
>> > >> >>
>> > >> >> _______________________________________________
>> > >> >> ULC-developer mailing list
>> > >> >> [email protected]
>> > >> >> http://lists.canoo.com/mailman/listinfo/ulc-developer
>> > >> >>
>> > >> >
>> > >>
>> > >>
>> > >
>> > >_______________________________________________
>> > >ULC-developer mailing list
>> > >[email protected]
>> > >http://lists.canoo.com/mailman/listinfo/ulc-developer
>> >
>> >
>>
>> _______________________________________________
>> ULC-developer mailing list
>> [email protected]
>> http://lists.canoo.com/mailman/listinfo/ulc-developer
>>
>

_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer

Reply via email to