Java.io.IOException: SysCall : bind() failed

Hello -
I am the support engineer for an OEM Itronix of a rugged handheld device with PXA25x (ARM4VI) processor that is running WM 5.0. Potential customer in Ireland has sent me the following log reporting that the main problem is probably the java.io.IOException: Syscall : bind() failed. I have attached the actual log file below.
My question is: 1. how can I best debug this issue? I doubt that anything is using port 45000? Unless customer unknowing is loading something before hand that would be using this port? I ran a netstat program on the ports of my device and by default there is nothing in our handheld that uses anything remotely close to port 45000.
2. I'm not certain as to what version of Creme they are using - I suspect it must be Creme 2.7a as they claim they have run this on another WM 5.0 device and sent me logs showing that it did not have a java.io.IOException: Syscall : bind() failed exception - only our handheld failed with this exception evidently?
Note that I don't have the MI System to attempt to recreate this, nor do I have any prior experience with SAP MI (although that may change real fast). I do have DB2e and Creme and have used both in the past.
Can anyone give me some suggestions and help on how to help debug this on our device?
Thanks Neal Davis
Sorry about the long log - but maybe it will help show big picture:
[20060101 14:49:24:000] I [MI/API/Logging           ] ***** LOG / TRACE SWITCHED ON
[20060101 14:49:24:000] I [MI/API/Logging           ] ***** Mobile Engine version: MI 25 SP 18 Patch 00 Build 200607272043
[20060101 14:49:24:000] I [MI/API/Logging           ] ***** Current timezone: PST
[20060101 14:49:37:121] E [MI/API/Services          ] MultiObjectFileStorage: Error in data read access to mapping file /MI/data/LastSuccessfulSync/datreg.obj - Generating initial mapping (root cause: /MI/data/LastSuccessfulSync/datreg.obj [java.io.FileNotFoundException])
[20060101 14:49:49:050] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/0.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()
[20060101 14:49:51:039] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/0.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()
[20060101 14:49:53:824] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/0.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()
[20060101 14:51:53:152] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/0.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.mi.systemnews.NewsImpl.create()
     at com.sap.ip.mi.systemnews.StartListener.userLoggedOn()
     at com.sap.ip.me.core.UserManagerImpl.fireLogon()
     at com.sap.ip.me.core.UserManagerImpl.logOnUser()
     at com.sap.ip.me.core.UserManagerImpl.logOnUser()
     at com.sap.ip.me.apps.jsp.LoginServlet.doHandleEvent()
     at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe()
     at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet()
     at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost()
     at javax.servlet.http.HttpServlet.service()
     at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service()
     at javax.servlet.http.HttpServlet.service()
     at org.apache.tomcat.core.ServletWrapper.doService()
     at org.apache.tomcat.core.Handler.service()
     at org.apache.tomcat.core.ServletWrapper.service()
     at org.apache.tomcat.core.ContextManager.internalService()
     at org.apache.tomcat.core.ContextManager.service()
     at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection()
     at org.apache.tomcat.service.TcpWorkerThread.runIt()
     at org.apache.tomcat.util.ThreadPool$ControlRunnable.run()
     at java.lang.Thread.run()
[20060101 15:00:39:734] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/0.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.ccms.remotetracing.RemoteTracingInboundProcessor.registerItself()
     at com.sap.ip.me.ccms.remotetracing.RemoteTracingListener.actionPerformed()
     at com.sap.ip.me.sync.SyncEventRegistryImpl.fireSyncEventNotifierMethod()
     at com.sap.ip.me.sync.SyncManagerImpl.raiseSyncEvent()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()
     at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()
     at java.lang.Thread.run()
[20060101 15:00:47:332] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/0.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.sync.LogSenderInboundProcessor.registerItself()
     at com.sap.ip.me.sync.LogSender.sendLogToBackend()
     at com.sap.ip.me.sync.LogSender.actionPerformed()
     at com.sap.ip.me.sync.SyncEventRegistryImpl.fireSyncEventNotifierMethod()
     at com.sap.ip.me.sync.SyncManagerImpl.raiseSyncEvent()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()
     at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()
     at java.lang.Thread.run()
[20060101 15:00:58:958] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/1.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.ccms.configinfo.ConfigInfoCheckerInboundProcessor.registerItself()
     at com.sap.ip.me.ccms.configinfo.ConfigInfoListener.actionPerformed()
     at com.sap.ip.me.sync.SyncEventRegistryImpl.fireSyncEventNotifierMethod()
     at com.sap.ip.me.sync.SyncManagerImpl.raiseSyncEvent()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()
     at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()
     at java.lang.Thread.run()
[20060101 15:01:11:889] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/1.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.ccms.configinfo.ConfigInfoCollectorInboundProcessor.registerItself()
     at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.createConfigInfoContainer()
     at com.sap.ip.me.ccms.configinfo.ConfigInfoCheckerInboundProcessor.process()
     at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()
     at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()
     at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()
     at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()
     at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
     at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()
     at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()
     at java.lang.Thread.run()
[20060101 15:07:01:133] I [MI/API/Logging           ] ***** LOG / TRACE SWITCHED ON
[20060101 15:07:01:133] I [MI/API/Logging           ] ***** Mobile Engine version: MI 25 SP 18 Patch 00 Build 200607272043
[20060101 15:07:01:133] I [MI/API/Logging           ] ***** Current timezone: GMT
[20060101 15:07:12:071] E [AppLog/MI/API/Services   ] java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectInputStream.readObject()
     at java.io.ObjectInputStream.defaultReadObject()
     at java.io.ObjectInputStream.inputObject()
     at java.io.ObjectInputStream.readObject()
     at java.io.ObjectInputStream.readObject()
     at com.sap.ip.me.api.services.IOUtils.readSerializedObjectFromFile()
     at com.sap.ip.me.api.services.IOUtils.readHashtableFromDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.<init>()
     at java.lang.Class.newInstance()
     at com.sap.ip.me.api.conf.Configuration.createInstanceForType()
     at com.sap.ip.me.api.conf.Configuration.getSingletonInstanceForType()
     at com.sap.ip.me.api.sync.InboundProcessorRegistry.<clinit>()
     at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.initializeSmartSyncFramework()
     at com.sap.ip.me.core.FrameworkInitializer.initSmartSync()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()
Martyn Lewis (This is different) ??????????????????????????????
[20060101 15:07:59:692] E [MI/ComServer             ] Exception while running communication server:
java.io.IOException: SysCall : bind() failed
     at java.net.PlainSocketImpl.bind()
     at java.net.ServerSocket.<init>()
     at java.net.ServerSocket.<init>()
     at com.sap.ip.me.core.CommunicationServer.run()
     at java.lang.Thread.run()
[20060101 15:08:04:639] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/1.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()
[20060101 15:08:07:836] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/1.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()
[20060101 15:08:10:780] E [AppLog/MI/API/Services   ] Problems while saving /MI/sync/inboundProcessors/1.value
java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at java.io.ObjectOutputStream.defaultWriteObject()
     at java.io.ObjectOutputStream.outputObject()
     at java.io.ObjectOutputStream.writeObject()
     at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()
     at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()
     at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()
     at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()
     at com.sap.ip.me.core.FrameworkInitializer.main()
     at com.sap.ip.me.core.Startup.main()

Thanks Jo for your input - I have investedigated and still not certain of what is really going on and if this applies or not.
I did get a screen shot back from the customer and here is what it looks like (had to type out as I don't see a way to post and image to this forum):
Internet Explorer
Screen Shot
SAP
Synchronization Log
-Synchroniztion started
-Connection set up (without proxy) to: http://
headsap001s:50000/meSync/servlet/meSync?
~sysid=mob&
-Successfully connected with server.
-Processing of inbound data began.
-Synchronisation problems: Transport-layer (http) sync
exception raised (root cause: Exception while
synchronizing (java.net.SocketException: Remote
Connection Closed: Remote connection closed))
One suspicious thing I noticed about the screen shot above is Syncronization or Syncronizing is always spelled with a "z" except in one case above is spelled with an "s" - the UK spelling method? I check the screen shot several times and this is not a typo on my part it is how it is in the actual screen shot - almost if someone changed the log file being reported to the screen?
Can someone comment on the error, has this been seen by anyone else and was there a solution?
Also how difficult is it to hook up the entire solution so that I can recreate at my desk? I have DB2e and Java Creme (3.28). I need SAP MI I guess and probably need to set up sometime of server so I can replicate the whole process of installation and synchronization. What is the minimum I can do to replicate this and can I get a SAP MI system as a demo to put this whole puzzle together?
Thanks so much for any input anyone can provide on above.
Neal Davis

Similar Messages

Java.io.IOException: WEB8001: Write failed

I have written a servlet to download a tar file.
The Servlet takes the parameters and create a tar file based on the parameters and then opens the file for download for the user. I am able to download the tar file and the contents of the tar file is ok. But when I write the content to the OutputStream I getting an IOException
(1) Refer to the code snippt below. Here I am getting the following IOException: Cannot read and write data java.io.IOException: WEB8001: Write failed
private void sendDownloadFile(File downloadFile, HttpServletResponse response) {
try {
response.setContentType(contentType + "; name=\""
+ downloadFile.getName() + "\"");
Long length = new Long(downloadFile.length());
response.setContentLength(length.intValue());
response.setHeader("Content-Disposition", "attachment; filename=\""
+ downloadFile.getName() + "\"");
OutputStream outStream =
new BufferedOutputStream(response.getOutputStream());
InputStream streamIn = new BufferedInputStream(
new FileInputStream(downloadFile));
byte[] tarBytes = new byte[1024];
while (streamIn.read(tarBytes) != -1) {
outStream.write(tarBytes);
outStream.flush();
streamIn.close();
}catch (FileNotFoundException fnfex) {
logger.fatal("File is MISSING!!");
}catch (IOException ioex) {
logger.fatal("IOException: Cannot read and write data " + ioex);
catch (Exception e) {
logger.fatal("Download Exception: " + e);
}Any help would be appreciated.

What are you using as your test client?The test client is WebStone 1.0. WebStone always downloads the whole response, and reports the size of the response in bytes. From this I can see that when the IO exception occurs, webstone is unable to read the whole response, as it reports a smaller size.
So, I do not think the problem is that the client has prematurely aborted its download. WebStone doesn't work that way. I think something has gone awry on the server side, and this worries me.

SOAP: call failed: java.io.IOException: unable to create a socket ??

Hi
I am getting the following error in PI for one of my sync interfaces.
SOAP: call failed: java.io.IOException: unable to create a socket
The interface works most of the time, but i get this error couple of times a day.
Regards,
XIer

Hav you able to resolve this issue? Please let me know what was cause of this "unable to create a socket"
Thanks,
Sagar

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.

Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK

Hi PI gurus,
Need some suggestions on one issue below -
Scenario - proxy (SAP) to SOAP (Web based system)
In the RWB Communication Channel Monitirong we are receiving the below error
" Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK"
the request from XI system is going to target system and printing the lables (as per the functionality) with no issues but the comminication channel is giving the above error and this is causing the repeated sending the same request to target sytem and the data is printing repeateadly. This issues is occuring in Quality environment.
Strangley the same Interface with the same connectivity details is working fine in Development environment. But not working in Quality environment. Checked the firewalls settings on both in XI and Target system side and confirmed that everything is fine.
Below are the Logs both from Quality and developement are as follows
Quality ( Failure Case)
17.03.2011 07:19:59 Success SOAP: request message entering the adapter with user J2EE_GUEST
17.03.2011 07:25:03 Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK
Development (Success ful)
17.03.2011 07:27:55 Success SOAP: request message entering the adapter with user J2EE_GUEST
17.03.2011 07:27:58 Success SOAP: completed the processing
When we checked with basis team on user id J2EE_GUEST, they confirmed that they are same in Development and Quality.
I repeat,, that the same target url and everthing is same in XI Configuration
Thanks in Advance. Points would be rewared for the best solution.
Thanks,
Jitender

HI Jitender,
If your scenariois working in DEV and if it is not working in QAS.Could you please check if both the systems are at same patch levels..
Please refer below notes :1551161,817894,952402.
Cheers!!!
Naveen.

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

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?

Attempt to process file failed with java.io.IOException

Hi,
The scenario is from Idoc to flat file and messages are getting processed successfully in XI. but in receiver communication channel error is coming:
Attempt to process file failed with java.io.IOException: Error during STOR/APPE epilogue: com.sap.aii.adapter.file.ftp.FTPEx: 426 Connection closed; transfer aborted.
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error during STOR/APPE epilogue: com.sap.aii.adapter.file.ftp.FTPEx: 426 Connection closed; transfer aborted.: java.io.IOException: Error during STOR/APPE epilogue: com.sap.aii.adapter.file.ftp.FTPEx: 426 Connection closed; transfer aborted.

Hi,
If you are using FTP then,
1. Make sure that the FTP sever does not have issues with Firewall or a Proxy server access.
2. Also verify that the specified FTP user ID has the necessary WRITE or overwrite authorization?
Regards,
Sarvesh
***Reward points, if it helped you.

SOAP Sender Channel Failed to render XIMessage. Reason: java.io.IOException

I am attemping to set up a sender channel using the SOAP adatper to process HTTP(S) posts containg a file that is being uploaded.
The Sender channel is set up to use HTTPS With Client Authentication, and selected "Do Not Use SOAP Envelope" -- since the payload will not be SOAP. I am simply trying to generate a message in PI from the HTTP post.
I have posted the data but am getting the following error in the channel:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Failed to render XIMessage. Reason: java.io.IOException: Missing mandatory element <sap:Main>sap:Receiver/sap:Service
The trading partner I am workgin with only has the ability to use a generic POST (I believe he is usnig CURL or some some other tool the 'post' the data.

Thank you for your reply.
The solution I am seeking is not for XML payload. Its a flat-file that one of our trading partners is sending to us, both for flat files as well as EDI/X12 data. I have the checkbox selected to not use the SOAP Envelope and am using the "nosoap=true" in the URL.
This should be simple, as all we need to do is to pass the data as posted by the trading partner to a SFTP or FILE adapter on the receiver side. Nothing more than we've already done using an AS2 Sender channel for, the trouble with in case case our trading partner does not support any encrypted transports except for HTTPS.
-Gerry

Java.io.IOException: open HTTP connection failed

I got this error message when trying to load applets in a web page, with J2SDK_Forte:
==================================
load: class myClass.class not found.
java.lang.ClassNotFoundException: myClass.class
     at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:151)
     at sun.plugin.security.PluginClassLoader.findClass(PluginClassLoader.java:189)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:112)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:262)
     at sun.applet.AppletClassLoader.loadCode(AppletClassLoader.java:478)
     at sun.applet.AppletPanel.createApplet(AppletPanel.java:548)
     at sun.plugin.AppletViewer.createApplet(AppletViewer.java:1621)
     at sun.applet.AppletPanel.runLoader(AppletPanel.java:477)
     at sun.applet.AppletPanel.run(AppletPanel.java:290)
     at java.lang.Thread.run(Thread.java:536)
Caused by: java.io.IOException: open HTTP connection failed.
     at sun.applet.AppletClassLoader.getBytes(AppletClassLoader.java:224)
     at sun.applet.AppletClassLoader.access$100(AppletClassLoader.java:40)
     at sun.applet.AppletClassLoader$1.run(AppletClassLoader.java:141)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:138)
     ... 10 more
==================================
The applet is in the same directory as the ASP. It is a NT 4 (SP6) server. The applets loaded and ran fine with jdk1.3. Do I need to do something different in my ASP, or IIS setup to allow java applet HTTP connection in JDK1.4?
Thanks!

I have the exact same problem but have yet to find a solution.
It works fine in 1.3 but fails occasionally in 1.4. If I refresh the browser several times it eventually
loads.
Scott

Java.io.IOException: Compiler failed executable.exec

I m trying to deploy a EAR file which has a single EJB.
It deploys fine but when i try to start it it throws the exception trac
ebelow.
Any ideas on how to solve ? I ve put Jrockit javac in path, set BEA_HOME
and tried a few other things with no luck.
Any ideas ?
/s
Unable to deploy EJB: hello_ejb_wls9.jar from hello_ejb_wls9.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvo
ker.java:435)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:
295)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:
303)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:284)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:470)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:439)
at
weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:436)
The server compiler and ejb compiler are set as javac in the options.

Hi,
I think you are not creating that ear correctly.
Could you check the following points ?
1. make sure all the files you need are there
2. make sure folder hierararchy is ok
If that's cool: And its still doesnt work:
Export your example ear from weblogic and use that one
Regards
Anilkumar kari

Failed to start "admin server" and "BI publisher" : Reason java.io.IOException openWallet

Hello,
I need your help to fix a critical problem to start Admin server and BI server :
# ...domains/bifoundation_domain/bin/startWebLogic.sh ....
Failed with
17-Mar-2015 17:17:33 oracle.security.jps.internal.credstore.ssp.CsfWalletManager openWallet
WARNING: Opening of wallet based credential store failed. Reason java.io.IOException
Best Regards
Djams
More détails in ... /logs/AdminServer.log :
####<17-Mar-2015 17:14:16 o'clock CET> <Notice> <Log Management> <srver3.domaine.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (sel
f-tuning)'> <> <> <> <1426608856985> <BEA-170019> <The server log file /servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminSe
rver.log is opened. All server side log events will be written to this file.>
####<17-Mar-2015 17:14:16 o'clock CET> <Info> <Log Management> <srver3.domaine.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-
tuning)'> <> <> <> <1426608856998> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Diagnostics> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
t (self-tuning)'> <<WLS Kernel>> <> <> <1426608857142> <BEA-320001> <The ServerDebug service initialized successfully.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857307> <BEA-002622> <The protocol "t3" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857308> <BEA-002622> <The protocol "t3s" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857309> <BEA-002622> <The protocol "http" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857309> <BEA-002622> <The protocol "https" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857311> <BEA-002622> <The protocol "iiop" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857313> <BEA-002622> <The protocol "iiops" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857314> <BEA-002622> <The protocol "ldap" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857316> <BEA-002622> <The protocol "ldaps" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857323> <BEA-002622> <The protocol "cluster" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857324> <BEA-002622> <The protocol "clusters" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857333> <BEA-002622> <The protocol "snmp" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857333> <BEA-002622> <The protocol "admin" is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
lf-tuning)'> <<WLS Kernel>> <> <> <1426608857334> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <RJVM> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self
-tuning)'> <<WLS Kernel>> <> <> <1426608857380> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address          :7001
Public Address          N/A
Http Enabled            true
Tunneling Enabled       false
Outbound Enabled        false
Admin Traffic Enabled   true>
#####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Server> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857449> <BEA-002609> <Channel Service initialized.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857487> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857488> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857489> <BEA-000406> <PosixSocketMuxer was built on Apr 24 2007 16:05:00>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857518> <BEA-000436> <Allocating 4 reader threads.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <Socket> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857521> <BEA-000446> <Native IO Enabled.>
####<17-Mar-2015 17:14:17 o'clock CET> <Info> <IIOP> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608857866> <BEA-002014> <IIOP subsystem enabled.>
####<17-Mar-2015 17:14:22 o'clock CET> <Error> <Security> <srver3.domaine.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1426608862432> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException>
####<17-Mar-2015 17:14:22 o'clock CET> <Critical> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862434> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.jps.JpsRuntimeException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:170)
        at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.jps.JpsException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
Caused By: oracle.security.jps.JpsException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
        at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2984)
        at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
        at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException
        at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:184)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:358)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:176)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:160)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:118)
        at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:56)
        at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
        at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
        at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
        at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
        at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
        at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2956)
        at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2950)
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2950)
        at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
        at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<17-Mar-2015 17:14:22 o'clock CET> <Notice> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862461> <BEA-000365> <Server state changed to FAILED>
####<17-Mar-2015 17:14:22 o'clock CET> <Error> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862461> <BEA-000383> <A critical service failed. The server will shut itself down>
####<17-Mar-2015 17:14:22 o'clock CET> <Notice> <WebLogicServer> <srver3.domaine.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1426608862462> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<17-Mar-2015 17:14:22 o'clock CET> <Info> <WebLo

Hello Djam,
Please review the following:
The FMW WebLogic Server (WLS) installation has been configured to use a non-default Java temporary files directory,
i.e. the following has been set in the WebLogic startup or setDomainEnv.sh script:
EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/appl/oracle/temp_java_files ${EXTRA_JAVA_PROPERTIES}"
Reference: How to Change the WebLogic Server Location for Temporary Files (Doc ID 1336002.1)
When the Middleware home was restored the directory specified by java.io.tmpdir parameter was missing,
Therefore an IOException occurred when opening the wallet and WLS was unable to initialize the OPSS successfully.
To resolve the issue re-create the directory specified by the java.io.tmp dir parameter, and make sure the owner and group access are the same as for the FMW installation.
Unable Start AdminServer: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException (Doc ID 1923395.1)
Bogdan

Opening of wallet based credential store failed. Reason java.io.IOException

Hi all,
I installed soa 11.1.1.3 when i am trying to run admin server i am getting the below exception plz help me if you have any idea .
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1394)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.JpsRuntimeException: JPS-01538: The default policy provider was not found.
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:273)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.JpsException: JPS-01538: The default policy provider was not found.
     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:705)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.JpsException: JPS-01514: The default context is missing in jps-config.xml.
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:665)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
     at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:177)
     at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:218)
     at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:140)
     at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:127)
     at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:115)
     at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:53)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:133)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:128)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:656)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>

Credit goes to http://brajeshwar.com/2005/file-access-denied-on-windows-xp-and-how-to-take-ownership/
For my windows XP solution. Basically the cwallet.sso file was not controllable via the XP user I was logged in as. Added the XP user to have full access to the file
Here are the steps in quickie mode
1.Log on to the computer with an account that has administrative credentials. If you are running Microsoft Windows XP Home Edition, you must start the computer in safe mode, and then log on with an account that has Administrative rights to have access to the Security tab.
2.If you are using Windows XP Professional, you must disable Simple File Sharing.
3.Right-click the folder/file that you want to take ownership of, and then click Properties.
4.Click the Security tab, and then click OK on the Security message (if one appears).
5.Click Advanced, and then click the Owner tab.
6.In the Name list, click your user name, or click Administrator if you are logged in as Administrator, or click the Administrators group. If you want to take ownership of the contents of that folder, select the Replace owner on subcontainers and objects check box.
7.Click OK, and then click Yes when you receive the following message:
You do not have permission to read the contents of directory folderName. Do you want to replace the directory permissions with permissions granting you Full Control?
All permissions will be replaced if you press Yes.
8.Click OK, and then reapply the permissions and security settings that you want for the folder and its contents.

Java.io.IOException: Write failed

Hi, I posted this question a while back in the JDBC forum because the exception occurs when I call DriverManager.getConnection(), but got no bites because my stack trace doesn't reflect any JDBC errors. This is such a strange problem. It occurs internal to the getConnection method. The connection object is still returned and my web-app works fine other than our log file being filled with the same exception. This problem only occurs on our SunONE server and not on Tomcat, which I test on. Any clues as to what it means and why it occurs. Thanks
java.io.IOException: Write failed
     at com.iplanet.ias.web.connector.nsapi.NSAPIConnector.write(NSAPIConnector.java:507)
     at com.iplanet.ias.web.connector.nsapi.NSAPIResponseStream.write(NSAPIResponseStream.java:74)
     at org.apache.catalina.connector.ResponseBase.flushBuffer(ResponseBase.java:760)
     at org.apache.catalina.connector.HttpResponseBase.flushBuffer(HttpResponseBase.java:774)
     at com.iplanet.ias.web.connector.nsapi.NSAPIResponse.flushBuffer(NSAPIResponse.java:55)
     at org.apache.catalina.connector.ResponseBase.write(ResponseBase.java:733)
     at org.apache.catalina.connector.ResponseStream.write(ResponseStream.java:325)
     at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1919)
     at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1668)
     at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1213)
     at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:520)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
     at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
     at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
     at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)

Wow, just found out what it means. I have a javascript window.close() called after clicking the link to my app. This exception occurs when the response is not completed its write. Sorry to waste your time. ahaha

Java.io.IOException: failed to connectTCP open

Hello all,
I am newcomer to J2ME. I am facing following problem.
I am using mmapi. While calling method Manager.createPlayer(String url)
following exception occurs:
java.io.IOException: failed to connectTCP open
at com.sun.mmedia.protocol.CommonDS.getConnection(+385)
at com.sun.mmedia.protocol.BasicDS.connect(+12)
at javax.microedition.media.Manager.createDataSource(+71)
at javax.microedition.media.Manager.createPlayer(+196)
at example.audiodemo.PlayerCanvas.createPlayer(+86)
at example.audiodemo.PlayerCanvas.run(+4)
I have specified url as http://localhost:7001/startup.wav
This link executes fine in browser.
Please help.
Thanks and Regards,
Pramod

uddinr0121 wrote:
thanks for the great advice... this is a bug in java
[http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6780505|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6780505]
The bug you linked to says it has to do with a shared directory that has spaces in its path. The code you posted has no spaces in the path. That does not sound like the same problem to me.

Java.io.IOException: SysCall : bind() failed

Similar Messages

Maybe you are looking for