[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp-interop] Verify interoperability with Oracle Portal
NetCache appliance (NetApp/5.3.1R3)After closer examination, this was indeed our proxy server - the request was never reaching the IBM producer.
RE: [wsrp-interop] Verify interoperability with Oracle Portal .NET also sends the keep-alive on (and only on) the first 1.1 request
(it also sends an Expect: 100-continue on every request).I've been trying to provoke wsrp.dyndns.org into dropping a connection
(with or without sending a close) but to avail so far.David, I see that you are going via a proxy/cache from your trace
which may be worth eliminating (as well as testing against wsrp.dyndns.org:8083).regards,
Andre-----Original Message-----
From: David Ward [mailto:david.ward@oracle.com]
Sent: 16 June 2003 21:13
To: richard.jacob@de.ibm.com
Cc: wsrp-interop@lists.oasis-open.org
Subject: Re: [wsrp-interop] Verify interoperability with Oracle Portal
Richard
I am attaching the trace I got from a TCP tunnel when our Portal tries to make consecutive initCookie and getMarkup requests through the same pooled TCP connection. After further investigation, I found that the "Keep-Alive" value we send in the Connection header of the first request is actually HTTP 1.0 semantics that can be ignored by an HTTP 1.1 server. That's why it doesn't appear in the second request. An HTTP 1.1 server would return Connection: close if it doesn't want the connection to be kept open, since the default is that the connection is kept alive. An HTTP 1.0 server would set the Keep-Alive header on the response if it wanted the connection to be kept open. Because we get an HTTP 1.1 response with no Connection close header, our client assumes it can keep the connection open and send another request on it, but this doesn't seem to be working.
We are using the same HTTPClient library we have relied on for years (not that that means it might not have bugs!). You can force your JVM to use it instead of the regular JDK HttpURLConnection by setting the java.protocol.handler.pkgs system property to HTTPClient.
Thanks
Dave
David Ward wrote:
Hi David, thanks.
1. yes we have this namespacing issue still open due to the JSR168
container reference implementation.
Once this is changed on the container side we can skip the namespacing
here.
2. strange, we tested with both AXIS HTTP1.0 -> no keep alive and with
.NETs HTTP1.1 and keep alive set.
Citrix's consumer also sets the keep-alive flag.
Andre, can you confirm please, and rerun your consumer against our producer
over the monitoring port (8082).
David could you also try to connect via the monitoring port 8083, please.
Maybe we discover something.I'll attach one WSI-monitor file showing a conversation between Citrix and
IBM, here the keep alive seem to work. You should have the xsl files (from
the WS-I monitor) placed in the directory "../xsl" relative to your log
file directory to generate a user-friedly output.(See attached file: log8082.xml.030606150200.xml)(See attached file:
assertions.xsl)(See attached file: common.xsl)(See attached file: log.xsl)
(See attached file: report.xsl)Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com
|---------+---------------------------->
| | David Ward |
| | <david.ward@oracl|
| | e.com> |
| | |
| | 06/16/2003 11:37 |
| | AM |
|---------+---------------------------->>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: Richard Jacob/Germany/IBM@IBMDE
|
| cc: wsrp-interop@lists.oasis-open.org
|
| Subject: Re: [wsrp-interop] Verify interoperability with Oracle Portal |>--------------------------------------------------------------------------------------------------------------------------------------------------|
Thanks
I have altered our WSDL to reference
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
in the import, and will make this fix available when we next patch our
site!We got the IBM portlet displaying, but there's a few glitches I want to
talk about. I'll investigate further as soon as I get the chance, but:
The portlet seems to be namespacing the input fields in its form. Is
this required?
The producer can't seem to cope with HTTP 1.1 keep alive behaviour -
we can only register the producer when we turn off connection pooling
RegardsDavid
Richard Jacob wrote:
Hi David,there is an absolut location for the wsdl.
You can find them here:
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_types.xsd
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
See chapter 14 of the spec or the wsrp group's home page.
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com
|---------+---------------------------->
| | David Ward |
| | <david.ward@oracl|
| | e.com> |
| | |
| | 06/12/2003 02:21 |
| | PM |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: Peter Fischer3/Germany/IBM@IBMDE
|
| cc: Michael Freedman <Michael.Freedman@oracle.com>,
wsrp-interop <wsrp-interop@lists.oasis-open.org>
|
| Subject: Re: [wsrp-interop] Verify interoperability with
Oracle Portal
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
This is indeed a bug. We will need to fix the WSDL we return so that
the
imports actually resolve to a location on our webserver.It would be useful if there was an absolute location on OASIS that
everyone
could use in their imports.Regards
David
Peter Fischer3 wrote:
Hi Mike,our consumer is having problems reading the wsdl you provided.
It imports the binding wsdl like this:<import namespace="urn:oasis:names:tc:wsrp:v1:bind" location="
wsrp_v1_bindings.wsdl" />but at this location (realtive to
http://portalstandards.oracle.com/wsrp/jaxrpc?WSDL)no such
document
can be
found.Should a WSRP consumer be able to handle that by using a local
version of
the wsdl or must the producer provide a correct / complete
wsdl?Mit freundlichen Grüßen / Best Regards
Peter
"Don't think of the problem - think of the solution!" ;-)
___________________________________________________________________
IBM WebSphere Portal Development Boeblingen, Germany
Phone: ++49-7031-16-4497
eMail: peter.fischer@de.ibm.com
|---------+----------------------------->
| | Michael Freedman |
| | <Michael.Freedman@|
| | oracle.com> |
| | |
| | 06/10/2003 07:45 |
| | PM |
| | |
|---------+----------------------------->
>
-----------------------------------------------------------------------------------------------------------------------------|
|
|
| To: WSRP <wsrp@lists.oasis-open.org>,
wsrp-interop
<wsrp-interop@lists.oasis-open.org> |
| cc:
|
| Subject: [wsrp-interop] Verify interoperability with
Oracle Portal
|
|
|
|
|
>
-----------------------------------------------------------------------------------------------------------------------------|
As of yesterday, Monday June9th, Oracle is publically hosting a
pre-release version of its portal implementing the TC 1.0 WSRP
specification so other vendors/customers can verify their
implementations interoperate with Oracle. By making this
publically
available we hope to accelerate the use and implementation of
interoperable WSRP producers. The site is available at:
http://portalstandards.oracle.com. Additonal supporting
information
is
available if you click on the "Go back to Oracle9iAS Portal
Center"
link
on this sites welcome page. To use the site [to test your
producer]
you
must be a logged in "Oracle Technology Network" user. Login
accounts
are free and available to all. Merely click on the "login"
link in
the
upper right corner and either login to an existing account or
sign up
for a new one. Once logged in you will be able to register
your
producer(s) with the Oracle Portal and add portlets from this
producer
to your own sandboxed portal page. The site contains
instructions on
how to do this as well as an existing sample page containing
portlets
from the Oracle WSRP Sample Producer. This later is also
hosted
publically so other WSRP consumers can test if they
work/interoperate
with Oracle's WSRP/JSR 168 container. The WSDL for this
producer is
available at http://portalstandards.oracle.com/wsrp/jaxrpc?WSDL
.
Though the site requests problems/support issues be directed
to
discussion lists/support, we prefer you use the
wsrp-interop@lists.oasis-open.org mailing list to communicate
questions/issues/problems. Dave and I track this list more
closely
ensuring faster turn around on reported issues.-Mike-
You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php
You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php
--
|--------------------+---------------------------+-----------------------|
| | |
|
| David Ward | Oracle European |
|
| Principal | Development Centre |
|
| Software Engineer | 520 Oracle Parkway |
Email: |
| Oracle Portal | Thames Valley Park |
david |
| | Reading |
.ward |
| | Berkshire RG6 1RA |
@orac |
| | UK |
le.co |
| | | m
|
| | |
Tel: |
| | |
+44 |
| | |
118 |
| | |
924 |
| | |
5079 |
| | |
Fax: |
| | |
+44 |
| | |
118 |
| | |
924 |
| | |
5005 |
| | |
|
| | |
||--------------------+---------------------------+-----------------------|
You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php
--
|--------------------+---------------------------+-----------------------|
| | | |
| David Ward | Oracle European | |
| Principal | Development Centre | |
| Software Engineer | 520 Oracle Parkway | Email: |
| Oracle Portal | Thames Valley Park | david |
| | Reading | .ward |
| | Berkshire RG6 1RA | @orac |
| | UK | le.co |
| | | m |
| | | Tel: |
| | | +44 |
| | | 118 |
| | | 924 |
| | | 5079 |
| | | Fax: |
| | | +44 |
| | | 118 |
| | | 924 |
| | | 5005 |
| | | |
| | | |
|--------------------+---------------------------+-----------------------|
--
David Ward
Principal Software Engineer
Oracle Portal
Oracle European Development Centre
520 Oracle Parkway
Thames Valley Park
Reading
Berkshire RG6 1RA
UK Email:david.ward@oracle.com
Tel:+44 118 924 5079
Fax:+44 118 924 5005
| David Ward Principal Software Engineer Oracle Portal |
Oracle European Development Centre 520 Oracle Parkway Thames Valley Park Reading Berkshire RG6 1RA UK |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]