Problem about "Expect: 100-continue"

Hi,
I recently konw that Sun Java System Webserver doesn't respond "Expect: 100-continue" of request header.
I tried something like below.
================ [Web Logic Plug-in] ================
----- [Web Server 6.0 sp8] -----
telnet localhost 92
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
POST /HelloJSP/HelloJSP.jsp?numtimes=3 HTTP/1.1
Expect: 100-Continue
Content-Length: 280
Host: EAI:92
HTTP/1.1 100 Continue <----------------------------- 100 continue
Connection closed by foreign host.
----- [Web Server 6.1 sp4] -----
telnet localhost 83
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
POST /HelloJSP/HelloJSP.jsp?numtimes=3 HTTP/1.1
Expect: 100-Continue
Content-Length: 280
Host: EAI:83
HTTP/1.1 500 Server Error <-------------------------- 500 Server Error
Server: Sun-ONE-Web-Server/6.1
Date: Sun, 31 Oct 2004 01:50:41 GMT
Content-type: text/jsp
Transfer-encoding: chunked
19
HTTP/1.1 100 Continue
================ [Web Logic Not Plug-in] ================
----- [Web Server 6.0 sp8] -----
telnet localhost 7890
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
POST /choi/HelloJSP.jsp?numtimes=3 HTTP/1.1
Expect: 100-Continue
Content-Length: 280
Host: EAI:7890
HTTP/1.1 200 OK <------------------------------------ 200 OK
Server: Netscape-Enterprise/6.0
Date: Sun, 31 Oct 2004 02:13:11 GMT
Content-length: 141
Content-type: text/html;charset=ISO-8859-1
Set-cookie: JSESSIONID=sjs60-0%253A41844a19%253A4b78ebbde37542e;path=/
<html>
<head>
<title>Hello JSP</title>
</head>
<body>
Hello, World! 
Hello, World! 
Hello, World! 
</body>
</html>
Connection closed by foreign host.
----- [Web Server 6.1 sp4] -----
telnet localhost 84
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
POST /HelloJSP/HelloJSP.jsp?numtimes=3 HTTP/1.1
Expect: 100-Continue
Content-Length: 280
Host: EAI:84
HTTP/1.1 200 OK <------------------------------------ 200 OK
Server: Sun-ONE-Web-Server/6.1
Date: Sun, 31 Oct 2004 02:07:55 GMT
Content-type: text/html;charset=ISO-8859-1
Set-cookie: JSESSIONID=E3ACEFCBB553E20E567D65A697D4F057;Path=/
Transfer-encoding: chunked
008e
<html>
<head>
<title>Hello JSP</title>
</head>
<body>
Hello, World! 
Hello, World! 
Hello, World! 
</body>
</html>
0
I think that Sun Java System Web Server 6.0 and 6.1 don't respond "HTTP/1.1 100 Continue" but just pass it from WebLogic.
And I found 500 Error is responsed on Sun Java System Webserver6.1 .
Is there anybody knows about this problem?
How can I set the Web Server to response "HTTP/1.1 100 Continue" message and to solve 500 Error?

See the poster's revised post:
http://swforum.sun.com/jive/thread.jspa?threadID=58470

Similar Messages

XSQLPages does not handle 'Expect: 100-continue'

I am running Jigsaw2.0.5 (from W3C) and XSQLPages1.0.2. When posting messages using libWWW (from W3C), an 'Expect: 100-continue' is included in the HTTP/1.1 header allowing the server to respond with a '100-continue' before the body of the message is sent.
However, it looks like XSQLPages is ignoring the 'Expect: 100-continue' request and tries to complete the 'xsql:insert-request' without the posted XML document.

Yes, I am referring to section 8.2.3 of rfc2616.
As I understand it, the reason for sending 'Expect: 100-continue', is to allow the server (i.e. XSQLPages) to reject the body of the message based on information in the header (Content-Type, Content-Length, etc.) BEFORE the body is sent/received. This will speed up the response time in case of a reject.
Our application (server) does not really care about this. We have written test code that passes the header and the body in one go and that works OK. However, a customer interfacing to our server is experiencing problems, because they use libWWW to post on our server. Since libWWW breaks up the body and the header, their client does not work against our server.
BTW: The server mentioned above is part of a IP Telephony solution (not wireless clients).

Http header expect:100-continue

I am trying to make a HTTP PUT request to a webservice, which I can't get to work because it keeps returning the following error in its header: HTTP/1.1 417 Expectation Failed
In the body it explains that I have a header "expect:100-continue" in my PUT request header (see image).
I have tried everything to remove that particular header from my request (using LabviewHTTPclient.lvlib:removeheader.vi), but Labview still sends it.
2 questions:
- Is there a tool that lets me see what header/request labview actually sends to the webservice?
- how come I can't remove that header?
Thanks for your input!
BTW. I got it working in Curl, which I believe is used by Labview itself as well
Attachments:
Error 417 Expectation Failed.png ‏8 KB

Hello Aartjan,
About the tool:
You could use wireshark (just an example).
About the header part:
Can you share your code or a simplification of it (Project and files [vi's..]) that allows me to test/reproduce/see what's going on?
To know what causes the issue we need to see your code.
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

OSB HTTP Header "Expect: 100-Continue"

Hello!
Client (.Net) call web-service on osb (ProxyService).
Http request have header "Expect: 100-Continue".
This request "freeze" the server and bus don't send response.
How it fix?
OSB 11g, WebLogic 10.3.3
Thanks

I can't change client side.
Server log:
<Notice> <Diagnostics> <LAM-ESB> <AdminServer> <[STANDBY] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <f3cc0ecdd0498662:-6b8c6571:12b81234e70:-7ff1-0000000000000260> <1286367032826> <BEA-320068> <Watch 'StuckThread' with severity 'Notice' on server 'AdminServer' has triggered at 06.10.2010 16:10:32 MSD. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND (MSGID = 'BEA-000337')
WatchData: DATE = окт 6, 2010 4:10:31 PM MSD SERVER = AdminServer MESSAGE = [STUCK] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "645" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@5e3e203[
POST /LAM_ESB/ProxyServices_v1/ReportServiceWS HTTP/1.1
SOAPAction: http://lam.org/esb/report/v1/SaveReportParameters
Content-Type: text/xml
Content-Length: 595
Expect: 100-continue
Connection: Keep-Alive
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-141 "[STUCK] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, priority=1, DAEMON> {
 weblogic.xml.query.tokens.common.BEA_PIToken.create(BEA_PIToken.java:32)
 weblogic.xml.query.tokens.BasicTokenFactory.createPI(BasicTokenFactory.java:769)
 weblogic.xml.query.tokens.BasicTokenFactory.createPI(BasicTokenFactory.java:730)
 weblogic.xml.query.parsers.StAXCursorAdaptor$LiteToken.next(StAXCursorAdaptor.java:257)
 weblogic.xml.query.parsers.StAXCursorAdaptor.fetchNext(StAXCursorAdaptor.java:103)
 weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:102)
 com.bea.wli.common.xquery.iterators.DocumentFilterIterator.fetchNext(DocumentFilterIterator.java:57)
 weblogic.xml.query.xdbc.iterators.DefaultTokenIterator.next(DefaultTokenIterator.java:112)
 com.bea.wli.common.xquery.iterators.ExpandTopLevelFullNodes.fetchNext(ExpandTopLevelFullNodes.java:36)
 weblogic.xml.query.xdbc.iterators.DefaultTokenIterator.next(DefaultTokenIterator.java:112)
 com.bea.wli.sb.context.SoapEnvelopeBodySource.skipToBodyAndValidate(LargeSOAPMessageImpl.java:827)
 com.bea.wli.sb.context.SoapEnvelopeBodySource.<init>(LargeSOAPMessageImpl.java:777)
 com.bea.wli.sb.context.BindingOperationMapper$OptimizedQNameMapper.computeOperationName(BindingOperationMapper.java:524)
 com.bea.wli.sb.context.OperationVariable.getTypedValue(OperationVariable.java:40)
 com.bea.wli.sb.context.MessageContextImpl.getOperation(MessageContextImpl.java:165)
 com.bea.wli.sb.context.BindingLayerImpl.addRequest(BindingLayerImpl.java:221)
 com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:39)
 com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
 com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:350)
 weblogic.security.service.SecurityManager.runAs(SecurityManager.java:143)
 com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
 com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:572)
 com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:252)
 com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:154)
 com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:350)
 weblogic.security.service.SecurityManager.runAs(SecurityManager.java:143)
 com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:146)
 com.bea.wli.sb.transports.http.generic.RequestHelperBase.service(RequestHelperBase.java:72)
 com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:106)
 weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:24)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
 weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)
 weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:206)
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3656)
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
 weblogic.security.service.SecurityManager.runAs(SecurityManager.java:117)
 weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2204)
 weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2126)
 weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1412)
 weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
 weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
SUBSYSTEM = WebLogicServer USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-000337 MACHINE = LAM-ESB TXID = CONTEXTID = f3cc0ecdd0498662:-6b8c6571:12b81234e70:-7ff1-000000000000025e TIMESTAMP = 1286367031998
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 600000
>Thanks

HTTP/1.1 100 Continue from PTWC 3.0

Hi all
We are getting the string "HTTP/1.1 100 Continue" appearing every so often after a PTWC 3.0 postback .. it doesn't seem to have any detrimental affect on the app but it's a little confusing to end users.
Has anyone else experienced this? We'd like to know why it's occuring and what we can do about it
thanks in Advance
Simon

Here's the bug info and resolution stuff via patch.
Microsoft bug, makes all our lives that much harder.
http://support.microsoft.com/default.aspx?scid=kb;en-us;898708&sd=rss&spid=2097
(Article ID: 898708):
SYMPTOMS
When you send a POST request to a server that is running Microsoft Internet Information Services (IIS) 6.0, IIS may send an "HTTP 100 Continue" response in the middle of the response stream. IIS sends the "HTTP 100 Continue" response after IIS has sent the “HTTP 200 OK” response."
Here is a link to another interesting article:
http://haacked.com/archive/2004/05/15/http-web-request-expect-100-continue.aspx

WSRP Consumer - producer registration error : (100)continue return code

I am trying to get an ALI WSRP Consumer working with the ALI WSRP Producer. Whenever I try to register the producer wsdl, the consumer fails with the error :
Failed to get a service description from WSRP provider!
Error message from WSRP provider: (100)Continue
Any clues? I can successfully register this producer with a different portal's consumer. Is there a configuration property that needs to be set to allow the (100) response code? Or perhaps my Producer should avoid that response code in the first place? Has anybody run into this?
Below is the stack trace generated by my consumer on the back-end (from ALI Logging Spy) :
Failed to get service description from WSRP provider: http://scollins.sd.defenseweb.net:80/wsrpproducer1.1/1.0/WSRPBaseService.asmx
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (100)Continue
faultActor:
faultNode:
faultDetail:
 {}string: return code: 100
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.1
Date: Wed, 22 Apr 2009 23:31:53 GMT
X-Powered-By: ASP.NET
Connection: close
X-AspNet-Version: 2.0.50727
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Content-Length: 3084
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><soap:Header><wsa:Action>urn:oasis:names:tc:wsrp:v1:getServiceDescriptionResponse</wsa:Action><wsa:MessageID>uuid:dc3a3069-320a-4a6d-a997-45313098bc00</wsa:MessageID><wsa:RelatesTo>uuid:c827c145-c82d-4958-a201-30e7a86c053b</wsa:RelatesTo><wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To><wsse:Security><wsu:Timestamp wsu:Id="Timestamp-18d05f2a-c5dd-4519-8d1d-24b68f27b9e5"><wsu:Created>2009-04-22T23:31:54Z</wsu:Created><wsu:Expires>2009-04-22T23:36:54Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><getServiceDescriptionResponse xmlns="urn:oasis:names:tc:wsrp:v1:types"><requiresRegistration>false</requiresRegistration><offeredPortlets><portletHandle>simple</portletHandle><markupTypes><mimeType>text/html</mimeType><modes>wsrp:edit</modes><modes>wsrp:help</modes><modes>wsrp:view</modes><windowStates>wsrp:maximized</windowStates><windowStates>wsrp:minimized</windowStates><windowStates>wsrp:normal</windowStates><windowStates>wsrp:solo</windowStates><locales>en</locales></markupTypes><description xml:lang="en"><value>Simple view portlet to test WSRP viewing</value></description><shortTitle xml:lang="en"><value>View</value></shortTitle><title xml:lang="en"><value>View Portlet</value></title><displayName xml:lang="en"><value>SimpleView</value></displayName><userProfileItems>UserProfileName/PropertyName</userProfileItems><templatesStoredInSession>true</templatesStoredInSession><doesUrlTemplateProcessing>true</doesUrlTemplateProcessing></offeredPortlets><offeredPortlets><portletHandle>helloworld</portletHandle><markupTypes><mimeType>text/html</mimeType><modes>wsrp:edit</modes><modes>wsrp:help</modes><modes>wsrp:view</modes><windowStates>wsrp:maximized</windowStates><windowStates>wsrp:minimized</windowStates><windowStates>wsrp:normal</windowStates><windowStates>wsrp:solo</windowStates><locales>en</locales></markupTypes><description xml:lang="en"><value>Hello world portlet to test WSRP viewing</value></description><shortTitle xml:lang="en"><value>View</value></shortTitle><title xml:lang="en"><value>Hello World Portlet</value></title><displayName xml:lang="en"><value>HelloWorld99</value></displayName><userProfileItems>UserProfileName/PropertyName</userProfileItems><templatesStoredInSession>true</templatesStoredInSession><doesUrlTemplateProcessing>true</doesUrlTemplateProcessing></offeredPortlets><registrationPropertyDescription><propertyDescriptions name="ConsumerName" type="xsd:string" /><propertyDescriptions name="BuildDate" type="xsd:dateTime" /></registrationPropertyDescription></getServiceDescriptionResponse></soap:Body></soap:Envelope>
(100)Continue
 at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:695)
 at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:129)
 at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
 at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
 at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
 at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
 at org.apache.axis.client.Call.invokeEngine(Call.java:2575)
 at org.apache.axis.client.Call.invoke(Call.java:2564)
 at org.apache.axis.client.Call.invoke(Call.java:2259)
 at org.apache.axis.client.Call.invoke(Call.java:2182)
 at org.apache.axis.client.Call.invoke(Call.java:1702)
 at com.plumtree.wsrp.base.WSRP_v1_ServiceDescription_Binding_SOAPStub.getServiceDescription(WSRP_v1_ServiceDescription_Binding_SOAPStub.java:857)
 at com.plumtree.wsrp.consumer.impl.ServiceDescriptionManager.getServiceDescription(ServiceDescriptionManager.java:118)
 at com.plumtree.wsrp.consumer.servlet.AdminPreference.renderSetRegistrationPage(AdminPreference.java:992)
 at com.plumtree.wsrp.consumer.servlet.AdminPreference.service(AdminPreference.java:117)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 at java.lang.Thread.run(Unknown Source)

This seemed promising, but the proposed solution (adding 'servicePointManager expect100Continue="false"' to Web.config) had no effect.
My consumer request actually does not include the "Expect: 100-continue" header and receives the 100 response anyways. My understanding now is that this is okay (thought I'm not sure why) and that the client should be expected to handle that response code in any case.
I am wondering if there is an issue with the combination of products in my environment that is not supported by this product?? I am using
IIS 5.1,
.Net 2.0
AquaLogic WSRP Producer 1.1/WebCenter WSRP Producer 10.3.0 (tried both)
I am testing this producer in two environments -
- AquaLogic Consumer running on AL Portal 6.5. When the WSRPConsumer is configured with the producer wsdl, it fails with message "Failed to get service description from WSRP Provider: .... faultString: (100) Continue".
- Liferay - AFTER successful registration, attempts to deploy my registered .Net portlet (simple hello-world) result in an internal exception thrown in the Producer [Bea.Portlet.Management.PortletManager.LoadPortlet(PortletManager.cs:line 114)] Error loading PortletContainer: Bad PortletState. No request is made to my .Net application.
It appears from both of these tests that both my producer and consumer are having fundamental problems that do not seem overly exotic (although I have successfully registered other WSRP portlets with the AL Consumer). However, I have not come across much information on these sorts of problems.

A problem about calling Labview vi in VB

Hi all:
I meeting a problem about data transfer and parallel operation between VB and Labview.
Actually, I want develop a VB program, in which, the Labview VI can be called and corresponding parameters can be transferred to Labview. and then, I also can operate my system by VB program at same time. something like parallel operation (VB and Labview program).
But the question is :
1. If I use "Call" method of ActiveX in VB, and the LabVIEW subvi is not stopped (for example, a loop structure), I can not do parallel operation on VB program. The error message is "other application is busy" which is attached below. The sample codes is also attached.
2. I tried to use other methods like "OpenFrontPanel" and "Run", but I am not sure how to transfer the parameter??
3. Then I tried to use "SetControlValue" to set the parameters, but there is a error " := expected", which is very strange, because the statement I wrote is followed with the help documents [ eg: VI.SetControlValue ("string", value)], why it is still need a "=" ??
Does anybody know something about it? Thanks a lot
Message Edited by hanwei on 11-07-2008 03:18 PM
Attachments:
vb_labview_error_message_1.JPG ‏14 KB
VB_to_LV.zip ‏10 KB

I sure hope OP has solved it by now.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

A switch on/off problem about the relay in a loop

hi group:
I am developing a project based the Ni-sci-1160. Now I meet a problem about switch on/off in a loop.
for example: I creat a loop, and continually check a boolean. if the boolean is true, then the realy is closed, otherwise the relay is open. The problem is when I make the boolean is true, the corresponding relay is not always on, but just on-off, on-off,on-off. I don't know why? Is there any good idea to fix it?
the easy example codes is attached here , thanks for you help.
Attachments:
relay_problem.vi ‏19 KB

Try moving that first DAQmx function out of the while loop. Since it is called switch set and Reset, I'm guessing it is resetting the status of the switch every iteration of the while loop which probably means setting it back to false. It looks like an initialization type of function which means it should only be run once.

Problem about using Oracle Form 6i to connect Oracle Database 10g express.

Sorry to interrupt all of you.
I have encountered a problem about using Oracle Form 6i to connect Oracle Database 10g express.
As I would like to
I use Oracle Net8 Easy Config to create a connection.
According to "tnsnames.ora", the paramater of connection is as follows;
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 127.0.0.1)(PORT = 1521))
(CONNECT_DATA = (SID = XE))
Unfortunately, when I use Oracle Net8 Easy Config to test the connection, an error message is prompted as follows:
Connecting....
The test did not succeed.
ORA-03106: fatal two-task communication protocol error
There may be an error in the fields entered
or the server may not be ready for a connection.
You can check the server and retry, or continue.
After I google it, I still have no idea how to solve the problem. I would like to ask, could anyone mind providing some hints or solution to address the issues.
Thanks for your assistance in advance.

I don't believe the Net8 Easy Config (NEC) will create a compatible entry in the tnsnames.ora. I have Forms 6i running successfully against a 10g Express database, but I did not use the NEC - I created the entry myself. Here is the entry I use:
XE=
(DESCRIPTION=
 (ADDRESS=
 (PROTOCOL=TCP)
 (HOST=<<servername or IP address>>)
 (PORT=1521)
 (CONNECT_DATA=
 (SERVER=dedicated)
 (SERVICE_NAME=XE)
)Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Fault handler triggered for "100 Continue" messages from web service

I'm using the Flex/Flash "WebService" class to connect to a .NET4 web service.
Things always work fine unless the service sends a "100 Continue" message,
(which it does seemingly at random, which is allowed by HTTP1.1).
The problem is that Flex/Flash does not appear to handle this message.
It triggers the fault handler with the following message:
"SOAP Response cannot be decoded".
The message body pulled from the Flash Builder's "Network Monitor" window (raw view) is:
HTTP/1.1 100 Continue
Server: ASP.NET Development Server/10.0.0.0
Date: Tue, 21 Aug 2012 14:42:25 GMT
Content-Length: 0
If I understand correctly, any client using HTTP 1.1 should be able to handle "100 Continue" messages even if they didn't ask for them.
Does anyone know what's going on here?
Here are the software versions of everything involved:
Flash plugin: 11.3.300.257 (ActiveX)
Flash Builder: 4.6
Flex Compiler SDK: 4.6.0
OS: WinXP Pro, 32-bit, SP3
Browser: IE 8.0.6001
Web Service: .NET framework 4
Any help/advice is greatly appreciated!!

Update: The problem also occurs with Firefox 12 using the debug version of FlashPlayer 11.3.300.257, so I don't think it's a browser issue... Looks like Flash itself.

URLConnection and 100 Continue

I'm having trouble using the URLConnection. I'm posting form data in an attempt to read cookie headers in the response. Before opening the connection, I set headers to mimic a user agent, and then post the data.
The server sends a 100 continue, which the URLConnection follows, and then a 302 ObjectMoved which sends the cookie data. In this communication the URLConnection is dropping the pre-set headers (set and used in the initial transfer), and not creating the cookies. When it follows the 302, then, it is being redirected again as having not successfully supplied the form data posted.
Do I have finer control than Harold points out in his book, or do I have to build a socket from scratch?

Yes, setFollowRedirects() does prevent the follow. That solved a problem, thank you. Now the difficulty is in capturing the Set-Cookie header values passed with the 302 Object Moved. I have been capturing them with a packet spy, entering them (creating a cookie response) manually, and then proceeding with the communication, which works as it should. I'm using the following code to post data:
     public InputStream post() throws IOException {
          //open the connection and prepare it to post
          uc = (HttpURLConnection)url.openConnection();
          HttpURLConnection.setFollowRedirects(false);
          uc.setRequestProperty("User-Agent", " Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)");
          uc.setRequestProperty("Accept", " text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5");
          uc.setRequestProperty("Accept-Language", " en-us,en;q=0.5");
          uc.setRequestProperty("Accept-Encoding", " gzip,deflate");
          uc.setRequestProperty("Accept-Charset", " ISO-8859-1,utf-8;q=0.7,*;q=0.7");
          uc.setRequestProperty("Keep-Alive", " 300");
          uc.setRequestProperty("Connection", " keep-alive");
          uc.setRequestProperty("Referer", con.referer_string); //Scripted Referer
          uc.setRequestProperty("Cookie", con.cookie_string); //My cookie data; captured and entered manually
          uc.setDoOutput(true);
          OutputStreamWriter out = new OutputStreamWriter(uc.getOutputStream(), "ASCII");
          out.write(query.toString());
          out.write("\r\n");
          out.flush();
          out.close();
          return uc.getInputStream();
     }Now, as I mentioned previously, the method encounters a 100 Continue, posts the data, receives a 302 Object Moved (which passes a Set-Cookie header), and then the connection is terminated (by me). When using an HttpURLConnection without setDoOutput , I can capture the header data like this:
     for (int j = 1; ; j++) {
          String header = uc.getHeaderField(j);
          String key = uc.getHeaderFieldKey(j);
          if (header == null || key == null) break;
          System.out.println(uc.getHeaderFieldKey(j)+": "+header);
     }However, the uc connection used in the post() method above does not return the data needed from the 302. How do I get to it?
Message was edited by:
phossal

My iphone 3gs has a vibrating problem where the phone continuously vibrates

my iphone 3gs has a vibrating problem where the phone continuously vibrates

Did you already try to reset the phone by holding the sleep and home button for about 10sec, until the Apple logo comes back again? You will not lose data by resetting.
If this does not work, set it up as new device: Use iTunes to restore your iOS device to factory settings - Apple Support
If still no luck, get it checked by an Authorized Apple Service Provider or Apple:
iPhone - Contact Support - Apple Support
Has the software on your phone been modified at some point in the past?

An old and difficult problem about "UnsatisfiedLinkError"

Hi dear all,
I have been struck with the problem about "UnsatisfiedLinkError". I have a c++ class HelloWorld with a method hello(), and I want to call it from within a java class. In fact, I have succeeded in calling it on the windows platform. But when I transfer it to linux, the error "UnsatisfiedLinkError" comes out. I have tried to take the measures as Forum has suggested, but it failed.
The source code is very simple to demonstrate JNI.
"HelloWorld.h"
#ifndef INCLUDEDHELLOWORLD_H
#define INCLUDEDHELLOWORLD_H
class HelloWorld
public:
void hello();
#endif
"HelloWorld.cpp"
#include <iostream>
#include "HelloWorld.h"
using namespace std;
void HelloWorld::hello()
cout << "Hello, World!" << endl;
"JHelloWorld.java"
public class JHelloWorld
public native void hello();
static
System.loadLibrary("hellolib");
public static void main(String[] argv)
JHelloWorld hw = new JHelloWorld();
hw.hello();
"JHelloWorld.cpp"
#include <iostream>
#include <jni.h>
#include "HelloWorld.h"
#include "JHelloWorld.h"
JNIEXPORT void JNICALL Java_JHelloWorld_hello (JNIEnv * env, jobject obj)
HelloWorld hw;
hw.hello();
All the files are in the same directory and all the processes are under the dirctory:
1. javac JHelloWorld.java
2. javah -classpath . JHelloWorld
3. g++ -c -I/usr/java/jdk1.3/include -I/usr/java/jdk1.3/include/linux JHelloWorld.cpp HelloWorld.cpp
4. ld -shared -o hellolib.so *.o
5. java -cp . -Djava.library.path=. JHelloWorld
Exception in thread "main" java.lang.UnsatisfiedLinkError: no hellolib in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1349)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at JHelloWorld.<clinit>(JHelloWorld.java:7)
Tried another measure:
i) export LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH
ii)java -cp . JHelloWorld
The same error came out as above.
I really don't know what is wrong with it.
Would you like to help me as soon as possible?
Thanks.
Regards,
Johnson

Hi Fabio,
Thanks a lot for your help.
It is very kind of you.
Regards,
Johnson

HT201210 hi everyone, i have a problem about my iphone 4S, doesn't work with wifi connection and bluetooth since upgrade to the IOS 7.0.3. Can anyone can help me tosolve this problem?????Thank's regards paulus

hi everyone, i have a problem about my iphone 4S, doesn't work with wifi connection and bluetooth since upgrade to the IOS 7.0.3. Can anyone can help me tosolve this problem?????Thank's regards paulus

Try the suggestions here to see if they resolve your problem:
http://support.apple.com/kb/ts1559
If these don't work you may have a hardware problem. Visit an Apple store for an evaluation or contact Apple Support.

Problem about Handling of Empty Files in File Adapter

Hello everyone,
NetWeaver 2004s --- XI
In Sender i have a File Adapter.
Now i meet a problem about Handling of Empty Files. When i send empty file, but don't cerate a leer message.
I have seen following text in help document. But in adapter configuration i can not find the correspond parameter.
can you give me some tips?
Thx in advance
best regards
Yaning
SAP Help Document über File Adapter
+Handling of Empty Files
Specify how empty files (length 0 bytes) are to be handled.
○ Do Not Create Message
No XI messages are created from empty files.
The files are processed according to the selected Processing Mode.
For example, if the processing mode is Delete, empty files are deleted in the source directory.
○ Process Empty Files
XI messages are created with an empty main payload.
The files are processed according to the selected Processing Mode.
○ Skip Empty Files
No XI messages are created from empty files.
Empty files are skipped and remain in the source directory.+
Help Docu

hi,
it's available since Sp19 for XI 3.0
and the corresponding SPS fpr XI 7.0
http://help.sap.com/saphelp_nw04/helpdata/en/44/f565854b7341e6e10000000a1553f6/frameset.htm
so probably you need to install the new SP
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Problem about "Expect: 100-continue"

Similar Messages

Maybe you are looking for