Java.io.IOException: Bad record type(60) or version (63.120)

Hi all
I'm developing a java me xmpp client and when I try to create a secure socket connection I get the following error: java. io.IOException: Bad record type(60) or version (63.120). I have searched in many places but I don´t find any answer about that problem. Can anybody help me?
regards

Hi,
Thank you for the quick response.
I tried that, I can connect so wls:/offline> nmConnect('weblogic','password','10.110.90.156','5556','ClassicDomain','/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain');
Connecting to Node Manager ...
Successfully Connected to Node Manager.
wls:/nm/ClassicDomain>
but on
nmStart(serverName="AdminServer",domainDir="/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain")
Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer'
wls:/nm/ClassicDomain> nmStart(serverName="AdminServer",domainDir="/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain")
Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer'
wls:/nm/ClassicDomain>
And the AdminServer log shows security authentication error. Wondering why since I am not entering password when I do nmStart?
Do you have an idea?
Thank you
Anatoliy

Similar Messages

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
help me.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
HI Arivazhagan K,
Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SOAP: error occured: java.io.IOException: invalid content type for SOAP: TE

Hi,
We are implementing an XI scenario as follows: Mail Adapter->XI->SOAP Receiver.
Basically, we pass the XML File attachment from the Mail Adapter through XI to the SOAP Adapter. However, we keep getting the following error:
SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML
Any ideas on where we could look to fix this problem?
Thanks,
EC

People,
most of errors like that are 401 (unauthorized), 403 (forbidden), 404 (not found) and so on. To be sure, check the message content that comes back from the webservice, in the Message Monitoring.
Obs: To visualize sync messages payload in Message Monitoring, you'll have to set the Messaging.syncMessageRemover.removebody parameter to false (default is true) in SAP XI AF Messaging service, in the Visual Administrator.
Regards,
Henrique.

Java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

hi all,
please help me to resolve the error. i am working on a proxy to soap scenario and in SXMB_moni i am getting the following error.
i had check my url,its working fine.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>*
thanks
kasturika

Check this thread
Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML
might give you some directions to look at.
Sameer

Reason Of Error java.io.IOException: invalid content type for SOAP: TEXT/HT

Hi All,
I am getting an error, when I am sending message from few BPM's to a common Webservice Synchronously.
Delivery of the message to the application using connection AFW failed, due to: java.io.IOException: invalid content type for SOAP: TEXT/HTML. Setting message to status failed.
Previously, it was working fine. But today I am getting the errors. Could any one please explain, what exactly the reason is. I searched the Forum, but didnt find a proper resolution. We are sending the same set of data to the Webservice, which we were sending before. Please suggest.
Regards,
Subhendu

Hi Vijay,
I am wondering,Without this module, how it was working fine for so many days. Could you please throw light?
Regards,
Subhendu

EROR: java.io.IOException: invalid content type for SOAP: TEXT/HTML

hi group,
my problem is related to scenario HTML to WebService in which im trying to send a request to a free webservice on internet and retrieving the response back and showing it in my html page.
scenario in detail:
i have a html page deployed on my tomcat server at my local m/c. in which im taking a email string and sending it to webservice which checks whether the email string has a valid email format or not and in response, webservice returns a boolean true/false depending on the email string. i want to show this boolean result n my html page.i have configured HTTP adaptor and SOAP adaptor for this and interfaces are scynchronus.
im able to send my request to webservice and getting the response also...i checked in trace..it shows message request sent and response recieved...here is the trace..
http://hcl3sap:50000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = PIISUSER</Trace>
<Trace level="3" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
but i get an error java.io.IOException: invalid content type for SOAP: TEXT/HTML after that,
Does anyone know where im going wrong....
regrds

you are very correct..i used SOAP reciever as http://www.webservicex.net/ValidateEmail.asmx?wsdl and SOAP Action as http://www.webservicex.net/IsValidEmail but getting the same error.
and if you look in the trace above it says that my request actually went to webservice and got a response also (response code 200) but i think after recieving the message from webservice something is wrong. either mapping is not correct...(but i tested that ..it works fine) or could be my company firewall is prohibiting the message sent by webservice to XI server (i have given proxy settings with password also)...im NOT sure on this ....
second thing i noticed in moni while examining the trace was....message payload under "Message Branch According to Receiver List " shows this value
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:IsValidEmail xmlns:ns1="http://www.webservicex.net">
<ns1:Email>samWhgf.com</ns1:Email>
</ns1:IsValidEmail>
and then in just next step "Request Message Mapping" payload is
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:IsValidEmail xmlns:ns1="http://www.webservicex.net" />
i dont know really why payload is getting appended and if it is correct or not? but after this step further payload goes in this appended format only till call adaptor...if this is so i assume my message is going to webservice as
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:IsValidEmail xmlns:ns1="http://www.webservicex.net" />
which is not the proper format to be recieved by the webservice without any input value i.e "samWhgf.com"
im confused on this ..whether this is the route cause or any other...i have been trying to figure out the root cause from some days but still unsuccessful.
please provide ur valuable inputs.
regrds
Sameer

Java.io.IOException: Bad file descriptor Jetty 9.2.10.v20150310

I started jetty in nonstop server on port 18095 and it was running fine, few days later suddenly noticed it consumes more CPU, when I check the log noticed the following log writing continiously
2015-07-08 13:25:48.606:WARN:oejs.ServerConnector:qtp26807578-18-acceptor-0@182e42f-ServerConnector@1f02fde {HTTP/1.1}{0.0.0.0:18095}:
java.io.IOException: Bad file descriptor (errno:4009)
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:241)
at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:377)
at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:500)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:724)
Can any one guess the root cause. Thanks.

I am using jdbc to connect the database. I want to update the blob fields that is picture into the database. Now i am using preparedstatement to update the fields. When it causes error, it will closed automatically. At that time, it causes bad file descriptor.

Exception clearing file manager: java.io.IOException: Bad file number

I see the following exception when closing the environment. Not reproducible easily, happens only with production user's data occasionally. Any ideas on what causes this and what can be done to resolve it?
com.sleepycat.je.RunRecoveryException: (JE 3.2.74)
Exception clearing file manager: java.io.IOException: Bad file number
at com.sleepycat.je.dbi.EnvironmentImpl.doClose(EnvironmentImpl.java:1123)
at com.sleepycat.je.dbi.EnvironmentImpl.close(EnvironmentImpl.java:995)
at com.sleepycat.je.Environment.close(Environment.java:322)

Thanks for the pointers.
We are running on Solaris.
I located a narrow window in our code where another thread from the same process was permitted to close the environment when a close is already in progress. Will plug that window.

Error occured: java.io.IOException: invalid content type for SOAP:TEXT/HTML

Hie experts, i got a very confusing error that i still unable to solve. I've tried to read some of the threads in here but i already try most of them but still does not work..
Anyone know how to explain actually what happen with this error and how i can handle this??

Hi Made,
XI expects a HTTP 200 response from the Web service with a empty SOAP Payload when it uses the SOAP adapter to call a webservice asynchronously . Also you would need to change its functionality to send this HTTP 200 response with an empty payload back to XI.
Refer the SOAP adapter FAQ on service market place for more info on this .
Also one thing, the Asynch message will hit the webservice and the SOAP adapter may error out with a timeout error. If that is not an issue, then the scenario will continue to work.
Please also refer the following blogs:
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Also check the proxy of your network.
find the details in IE -> tools -> internet options -> connections
regards,
Shibani
*Reward with points if helpful*

"java.io.IOException: Write Channel Closed" starting AdminServer from WLST

Hi,
I am trying to start the admin server through WLST.
Per "Oracle® Fusion Middleware WebLogic Scripting Tool Command Reference 11g Release 1 (10.3.2)" I tried it both ways - online and offline.
When online
wls:/nm/ClassicDomain> startServer('AdminServer','ClassicDomain','t3://10.110.90.156:7002','weblogic','<password>','/u0/app/oracle/product/middleware/user_projects/domains')
I am getting
Starting server AdminServer ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 412, in startServer
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEStarting server AdminServer ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 412, in startServer
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
at java.io.BufferedWriter.flush(BufferedWriter.java:236)
at weblogic.nodemanager.common.DataFormat.writeCommand(DataFormat.java:243)
at weblogic.nodemanager.client.NMServerClient.sendCmd(NMServerClient.java:320)
at weblogic.nodemanager.client.NMServerClient.sendServer(NMServerClient.java:265)
at weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:94)
at weblogic.management.scripting.NodeManagerService.nmStart(NodeManagerService.java:368)
at weblogic.management.scripting.LifeCycleHandler.startSvr(LifeCycleHandler.java:887)
at weblogic.management.scripting.WLScriptContext.startSvr(WLScriptContext.java:384)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
java.io.IOException: java.io.IOException: Write Channel Closed
and the node manager log shows:
WARNING: Uncaught exception in server handlerjava.io.IOException: Bad properties data format
java.io.IOException: Bad properties data format
at weblogic.nodemanager.common.DataFormat.readProperties(DataFormat.java:44)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:537)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
And if I try it offline
wls:/offline> startServer('AdminServer','ClassicDomain','t3://10.110.90.156:7002','weblogic','<passwd>','/u0/app/oracle/product/middleware/user_projects/domains');
I am getting a big stack below. Can anybody through an idea?
Thank you
Anatoliy
Offline stack:
Starting weblogic server ...
WLST-WLS-1273604718586: <May 11, 2010 3:05:19 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
WLST-WLS-1273604718586: <May 11, 2010 3:05:20 PM EDT> <Info> <Management> <BEA-140013> </u0/app/oracle/product/middleware/user_projects/domains/config/config.xml not found>
WLST-WLS-1273604718586: <May 11, 2010 3:05:20 PM EDT> <Info> <Management> <BEA-141254> <Generating new domain directory in /u0/app/oracle/product/middleware/user_projects/domains>
...WLST-WLS-1273604718586: <May 11, 2010 3:05:27 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
WLST-WLS-1273604718586:
WLST-WLS-1273604718586: There are 1 nested errors:
WLST-WLS-1273604718586:
WLST-WLS-1273604718586: weblogic.management.ManagementException: Failure during domain creation
WLST-WLS-1273604718586: at weblogic.management.internal.DomainDirectoryService.generateDomain(DomainDirectoryService.java:229)
WLST-WLS-1273604718586: at weblogic.management.internal.DomainDirectoryService.ensureDomainExists(DomainDirectoryService.java:152)
WLST-WLS-1273604718586: at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:72)
WLST-WLS-1273604718586: at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
WLST-WLS-1273604718586: at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
WLST-WLS-1273604718586: at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
WLST-WLS-1273604718586: at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
WLST-WLS-1273604718586: at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
WLST-WLS-1273604718586: at weblogic.Server.main(Server.java:67)
WLST-WLS-1273604718586: Caused by: com.bea.plateng.domain.script.ScriptException: The domain location must have write permission.
WLST-WLS-1273604718586: at com.bea.plateng.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:723)
WLST-WLS-1273604718586: at com.bea.plateng.domain.script.ScriptParserClassic$StateMachine.processWrite(ScriptParserClassic.java:575)
WLST-WLS-1273604718586: at com.bea.plateng.domain.script.ScriptParserClassic$StateMachine.execute(ScriptParserClassic.java:431)
WLST-WLS-1273604718586: at com.bea.plateng.domain.script.ScriptParserClassic.parseAndRun(ScriptParserClassic.java:150)
WLST-WLS-1273604718586: at com.bea.plateng.domain.script.ScriptParserClassic.doExecute(ScriptParserClassic.java:112)
WLST-WLS-1273604718586: at com.bea.plateng.domain.script.ScriptParser.execute(ScriptParser.java:73)
WLST-WLS-1273604718586: at com.bea.plateng.domain.DomainInfoHelper.executeSilentScript(DomainInfoHelper.java:858)
WLST-WLS-1273604718586: at com.bea.plateng.domain.DomainInfoHelper.createDefaultDomain(DomainInfoHelper.java:1762)
WLST-WLS-1273604718586: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
WLST-WLS-1273604718586: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
WLST-WLS-1273604718586: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
WLST-WLS-1273604718586: at java.lang.reflect.Method.invoke(Method.java:597)
WLST-WLS-1273604718586: at weblogic.management.internal.DomainDirectoryService.generateDomain(DomainDirectoryService.java:224)
WLST-WLS-1273604718586: ... 8 more
WLST-WLS-1273604718586:
WLST-WLS-1273604718586: >
WLST-WLS-1273604718586: <May 11, 2010 3:05:27 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
WLST-WLS-1273604718586: <May 11, 2010 3:05:27 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
WLST-WLS-1273604718586: <May 11, 2010 3:05:27 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
WLST-WLS-1273604718586: Stopped draining WLST-WLS-1273604718586
WLST-WLS-1273604718586: Stopped draining WLST-WLS-1273604718586 .............................................Could not connect to the server to verify that it has started. The error returned is: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.110.90.156:7002: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination] Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 432, in startServer
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing startServer : Could not start the server, the process might have timed out or there is an Error starting the server. Please refer to the log files for more details.

Hi,
Thank you for the quick response.
I tried that, I can connect so wls:/offline> nmConnect('weblogic','password','10.110.90.156','5556','ClassicDomain','/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain');
Connecting to Node Manager ...
Successfully Connected to Node Manager.
wls:/nm/ClassicDomain>
but on
nmStart(serverName="AdminServer",domainDir="/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain")
Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer'
wls:/nm/ClassicDomain> nmStart(serverName="AdminServer",domainDir="/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain")
Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer'
wls:/nm/ClassicDomain>
And the AdminServer log shows security authentication error. Wondering why since I am not entering password when I do nmStart?
Do you have an idea?
Thank you
Anatoliy

IOException: invalid content type for SOAP: TEXT/ using Sender SOAP adapter

Hi all,
When I am using Sender SOAP adapter, i am getting (MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System) exception.
From my RWB I can see:
2009-05-25 16:18:39 Information The message was successfully retrieved from the call queue.
2009-05-25 16:18:39 Information The message status was set to DLNG.
2009-05-25 16:18:39 Error Failed to parse the XI system response.
2009-05-25 16:18:39 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System.
2009-05-25 16:18:39 Error The message status was set to FAIL.
2009-05-25 16:18:39 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML
Please help if possible! Thanks!
Mayank

Hi,
Check in SLD your integration engine business system have the following
pipeline url : http://server:httpport/sap/xi/engine?type=entry
check Http port also
After that go to TCODE - SXMB_ADM - integrationn engine configuration and check if your server is configured as HUB with the same url or not.
Thanks
Kasturika Phukan

SOAP: call failed: java.io.IOException

Hi gurus,
I was executing several stress-tests for an interface between to non-SAP systems over PI, that both use async SOAP adapter communication.
The requirement is to transfer up to 70mb files with single files. I executed the tests successfully with a 50MB message size and lower, and then I tried with a 70MB message, but the message failed and got this error in the adapter log:
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
I believe this is coming from the adapter itself and not from the receiving system. I have checked the binary message data from the messaging system and it looks perfectly fine.
Any ideas why this is happening? Is there a limitation for message sizes with the SOAP adapter?
I also checked the messaging system configuration settings in the AS Java but could not find anythig related to the SOAP adapter.
Thanks in advance.
Regards,
S. Gökhan TOPÇ

Hi Gokhan,
I believe this is coming from the adapter itself and not from the receiving system. I have checked the binary message data from the messaging system and it looks perfectly fine.
I believe this is a client-side error, as your request was not properly addressed and the SOAP service was not reached.
Any ideas why this is happening? Is there a limitation for message sizes with the SOAP adapter?
Well, SAP's message size limit is huge but a lot depends on your receiving server's capabilities and network connections. So, you might not be able to reach the SAP's tested message size. In my project, I am able to do a max of 55 megs through SOAP.
Hope this helps.
regards,
Neetesh

IOException: invalid content type for SOAP: TEXT/HTML

Hi all,
After the IS received a SOAP request successfully and sent it to the Adapter Engine I get an IOException in my SOAP Adapter (I configured a SOAP communication channel). From my RWB I can see:
2005-08-12 10:53:17 Success SOAP: request message entering the adapter
2005-08-12 10:53:17 Success SOAP: completed the processing
2005-08-12 10:53:18 Success The message was successfully received by the messaging system. Profile: XI URL: http://ecsap:50000/MessagingSystem/receive/AFW/XI
2005-08-12 10:53:18 Success Using connection AFW. Trying to put the message into the receive queue.
2005-08-12 10:53:18 Success Message successfully put into the queue.
2005-08-12 10:53:18 Success The message was successfully retrieved from the receive queue.
2005-08-12 10:53:18 Success The message status set to DLNG.
2005-08-12 10:53:18 Success Delivering to channel: J2E_ReceiverChannel_SOAP
2005-08-12 10:53:18 Success SOAP: request message entering the adapter
2005-08-12 10:53:18 Error SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML
2005-08-12 10:53:18 Error Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML
2005-08-12 10:53:18 Error Delivery of the message to the application using connection AFW failed, due to: invalid content type for SOAP: TEXT/HTML.
2005-08-12 10:53:18 Success The asynchronous message was successfully scheduled to be delivered at Fri Aug 12 10:58:18 CEST 2005.
2005-08-12 10:53:18 Success The message status set to WAIT.
Please help if possible! Thanks!
Denis

hi guys
this is my soap Reciever CC is showing the Error .
please suggest me the solution.
2007-12-21 10:09:27 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML
2007-12-21 10:09:27 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML: java.io.IOException: invalid content type for SOAP: TEXT/HTML
2007-12-21 10:09:27 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML: java.io.IOException: invalid content type for SOAP: TEXT/HTML
2007-12-21 10:09:27 Error Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML
2007-12-21 10:09:27 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML: java.io.IOException: invalid content type for SOAP: TEXT/HTML. Setting message to status failed.
2007-12-21 10:09:27 Error The message status set to FAIL.
2007-12-21 10:09:27 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML: java.io.IOException: invalid content type for SOAP: TEXT/HTML.
thanks & Regards
Ravi

Java.io.IOException: Failed to rename log file on attempt to rotate logs

Hello.
I'm currently using Weblogic 5.1 SP6 on WinNT Server 4.0 SP6.
I set the weblogic.properties file like this so that the "access.log" will
be rotated every day at midnight.
-- weblogic.properties --
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=D:/WLSlog/access.log
weblogic.httpd.logFileFlushSecs=60
weblogic.httpd.logRotationType=date
weblogic.httpd.logRotationPeriodMins=1440
weblogic.httpd.logRotationBeginTime=11-01-2000-00:00:00
-- weblogic.properties <end>--
The rotation has been working well, but one day when I checked my
weblogic.log, I was getting some errors.
I found out that my "access.log" wasn't being rotated (nor being written,
flushed) after this error came out.
After rebooting WebLogic, this problem went away.
Has anyone clues about why WebLogic failed to "rename log file?"
-- weblogic.log --
? 2 04 00:00:00 JST 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Failed to rename log file on attempt to rotate logs
at weblogic.t3.srvr.httplog.LogManagerHttp.rotateLog(LogManagerHttp.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.io.IOException.<init>(IOException.java, Compiled Code)
at weblogic.t3.srvr.httplog.LogManagerHttp.rotateLog(LogManagerHttp.java,
Compiled Code)
at
weblogic.t3.srvr.httplog.LogManagerHttp.access$2(LogManagerHttp.java:271)
at
weblogic.t3.srvr.httplog.LogManagerHttp$RotateLogTrigger.trigger(LogManagerH
ttp.java:539)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java, Compiled Code)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
, Compiled Code)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
? 2 04 00:00:25 JST 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Bad file descriptor
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java, Compiled Code)
at
weblogic.utils.io.DoubleBufferedOutputStream.flushBuffer(DoubleBufferedOutpu
tStream.java, Compiled Code)
at
weblogic.utils.io.DoubleBufferedOutputStream.flush(DoubleBufferedOutputStrea
m.java, Compiled Code)
at
weblogic.t3.srvr.httplog.LogManagerHttp$FlushLogStreamTrigger.trigger(LogMan
agerHttp.java, Compiled Code)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java, Compiled Code)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
, Compiled Code)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
-- weblogic.log <end> --
note:
? 2 04 00:00:25 JST 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Bad file descriptor
keeps coming out every minute after on.
I suppose this is because I have set the HTTP log to be flushed every one
minute.
Thanks in advance.
Ryotaro

I'm also getting this error on Weblogic 6.1.1.
It only occurs if you set the format to "extended".
Is there any fix or workaround for this?

IOException: Incorrect stream type, doesn't allow push back of bytes

Hi,
We are trying to develop a java program that is supposed to open an SSL connection to an external trading partner and send some xml data. We are using the http_client.jar (HTTPClient) library to do that. We have already managed to write a program to do SSL requests but we also need to pass these requests through a proxy server. When we use this proxy server we get the following exception from HTTPClient:
Exception in thread "main" java.io.IOException: Incorrect stream type, doesn't allow push back of bytes
at HTTPClient.Response.readLines(Response.java(Compiled Code))
at HTTPClient.Response.readResponseHeaders(Response.java:1030)
at HTTPClient.Response.getHeaders(Response.java:713)
at HTTPClient.Response.getStatusCode(Response.java:262)
at HTTPClient.HTTPConnection.enableSSLTunneling(HTTPConnection.java:3335)
at HTTPClient.HTTPConnection.doConnect(HTTPConnection.java:4027)
at HTTPClient.HTTPConnection.connect(HTTPConnection.java:4004)
at SSLRequest.main(SSLRequest.java:22)
Out program source code is:
public class SSLRequest
     public static void main(String[] args) throws Exception
          HTTPConnection httpsConnection = new HTTPConnection("https", "www.verisign.com", 443);
          httpsConnection.setCurrentProxy("myproxy.mydomain.gr", 8080);
          httpsConnection.setAllowUserInteraction(false);
          httpsConnection.connect();
          HTTPResponse rsp = httpsConnection.Get("/");
          System.out.println(rsp);
We would really appreciate any help on this
Thanks.

Hi,
I found out that this is a reported bug (bug no. 3748882) that applies with App Server version 9.0.4 which is using SSL via a proxy server. The solution is to upgrade to app server version 10.1.2
Patrick.

Java.io.IOException: Bad record type(60) or version (63.120)

Similar Messages

Maybe you are looking for