"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
Similar Messages
-
Write Channel Closed, possible SSL handshaking or trust failure
Hi,
I Have a problem while working with Two-way SSL. I get Write Channel Closed, possible
SSL handshaking or trust failure error while contacting the server for invoking
a webservice secured by SSL.
I could figure out that the error is happening on client side while validating
the server certificate.
One more observation that i was able to find is, it works fine if the Server certificate
and the client certificate are signed by the same (root) CA.
I tried various options but couldn't find my luck. The BEA documentation in this
regards is not at all sufficient.
If i give strict checking false on my client end, the application works fine.
But for my scenario i want strict checking to be happend (otherwise there is no
point in going for SSL itself).
I am using WLSSLAdapter on my client side. The client application is a standalone
java class running out of weblogic (ideally running on JRun).
The way i have coded in my java class is:
String certificatePath = "C:/Cerificates/cert.pem";
String caCertificatePath = "C:/Cerificates/clientca.pem";
String targetURL = "https://localhost:443/feedservice/FeedService";
//set weblogic ServiceFactory
System.setProperty( "javax.xml.rpc.ServiceFactory",
"weblogic.webservice.core.rpc.ServiceFactoryImpl" );
System.setProperty("java.protocol.handler.pkgs","com.certicom.net.ssl");
System.setProperty("https.cipherSuites","SHA1withRSA,MD5withRSA");
SSLAdapterFactory sslFactory = SSLAdapterFactory.getDefaultFactory();
WLSSLAdapter adapter = (WLSSLAdapter) sslFactory.getSSLAdapter();
adapter.setProtocolVersion("SSL3");
adapter.setStrictChecking(true);
adapter.setVerbose(true);
FileInputStream clientCredentialFile = new FileInputStream (certificatePath);
String pwd = "password";
System.out.println("Loding Certificate from ........"+certificatePath);
adapter.loadLocalIdentity(clientCredentialFile, pwd.toCharArray());
System.out.println("Loding CA Certificate from ........"+caCertificatePath);
adapter.setTrustedCertificatesFile(caCertificatePath);
// optionally set the Adapter factory to use this instance always.
sslFactory.setDefaultAdapter(adapter);
sslFactory.setUseDefaultAdapter(true);
// Webservice invocation code..
call.setTargetEndpointAddress(targetURL);
call.setProperty("weblogic.webservice.client.ssladapter",adapter);
Object result = call.invoke(new Object[]{"test.xml"});
The error that i get :
java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
Source)
at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:106)
at java.io.FilterOutputStream.write(FilterOutputStream.java:78)
at weblogic.webservice.binding.soap.HttpClientBinding.writeToStream(HttpClientBinding.java:359)
at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBinding.java:284)
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHandler.java:34)
at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java:131)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:421)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:363)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:423)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:292)
at com.chase.userspace.aceclient.Client.main(Client.java:253)
Exception in handler's handleRequest().
Exception in thread "main" javax.xml.rpc.soap.SOAPFaultException: Write Channel
Closed, possible SSL handshaking or trust fail
ure
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:479)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:363)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:423)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:292)
at com.chase.userspace.aceclient.Client.main(Client.java:253)
Can someone give the working phone number of ....BEA CUSTOMER SUPPORT...The signature validation failure means your trusted CA certificate is not the issuer
of the identity certificate. The identity certificate issuer name can match to
the trusted CA certificate name, but the signature check really determines whether
it is the issuer.
Pavel.
"Chandra Sekhar Rao" <[email protected]> wrote:
>
Hi payal,
I have the issuer of the server identity certificate in the trust file
on client
side. The problem is with signature validation
"Pavel" <[email protected]> wrote:
It looks like your client does not trust the server certificate. Make
sure the
certificate you pass in adapter.setTrustedCertificatesFile(caCertificatePath);
is the issuer of the server's identity certificate.
Pavel.
"Chandra Sekhar Rao" <[email protected]> wrote:
Hi,
I Have a problem while working with Two-way SSL. I get Write Channel
Closed, possible
SSL handshaking or trust failure error while contacting the server
for
invoking
a webservice secured by SSL.
I could figure out that the error is happening on client side whilevalidating
the server certificate.
One more observation that i was able to find is, it works fine if the
Server certificate
and the client certificate are signed by the same (root) CA.
I tried various options but couldn't find my luck. The BEA documentation
in this
regards is not at all sufficient.
If i give strict checking false on my client end, the application works
fine.
But for my scenario i want strict checking to be happend (otherwisethere
is no
point in going for SSL itself).
I am using WLSSLAdapter on my client side. The client application is
a standalone
java class running out of weblogic (ideally running on JRun).
The way i have coded in my java class is:
String certificatePath = "C:/Cerificates/cert.pem";
String caCertificatePath = "C:/Cerificates/clientca.pem";
String targetURL = "https://localhost:443/feedservice/FeedService";
//set weblogic ServiceFactory
System.setProperty( "javax.xml.rpc.ServiceFactory",
"weblogic.webservice.core.rpc.ServiceFactoryImpl" );
System.setProperty("java.protocol.handler.pkgs","com.certicom.net.ssl");
System.setProperty("https.cipherSuites","SHA1withRSA,MD5withRSA");
SSLAdapterFactory sslFactory = SSLAdapterFactory.getDefaultFactory();
WLSSLAdapter adapter = (WLSSLAdapter) sslFactory.getSSLAdapter();
adapter.setProtocolVersion("SSL3");
adapter.setStrictChecking(true);
adapter.setVerbose(true);
FileInputStream clientCredentialFile = new FileInputStream (certificatePath);
String pwd = "password";
System.out.println("Loding Certificate from ........"+certificatePath);
adapter.loadLocalIdentity(clientCredentialFile, pwd.toCharArray());
System.out.println("Loding CA Certificate from ........"+caCertificatePath);
adapter.setTrustedCertificatesFile(caCertificatePath);
// optionally set the Adapter factory to use this instance always.
sslFactory.setDefaultAdapter(adapter);
sslFactory.setUseDefaultAdapter(true);
// Webservice invocation code..
call.setTargetEndpointAddress(targetURL);
call.setProperty("weblogic.webservice.client.ssladapter",adapter);
Object result = call.invoke(new Object[]{"test.xml"});
The error that i get :
java.io.IOException: Write Channel Closed, possible SSL handshakingor
trust failure
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
Source)
at com.certicom.tls.record.ReadHandler.interpretContent(Unknown
Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:106)
at java.io.FilterOutputStream.write(FilterOutputStream.java:78)
at weblogic.webservice.binding.soap.HttpClientBinding.writeToStream(HttpClientBinding.java:359)
at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBinding.java:284)
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHandler.java:34)
at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java:131)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:421)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:363)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:423)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:292)
at com.chase.userspace.aceclient.Client.main(Client.java:253)
Exception in handler's handleRequest().
Exception in thread "main" javax.xml.rpc.soap.SOAPFaultException: Write
Channel
Closed, possible SSL handshaking or trust fail
ure
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:479)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:363)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:423)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:292)
at com.chase.userspace.aceclient.Client.main(Client.java:253)
Can someone give the working phone number of ....BEA CUSTOMER SUPPORT... -
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
-
Problem starting adminserver with WLST and Nodemanager
I have a domain with one cluster containing 4 managed servers. Now I want to start the adminserver with WLST using the Nodemanager. (I know there are other/beter ways but in this situation I need to do it with Nodemanager).
The problem is that the Nodemanager doesn't add the right memory arguments to the start command of the admin server.
This is what I do:
nmConnect(usernaam,password,host,port,domain)
nmstart(adminserver)
This does start the adminserver only without the proper memory arguments.
I tried:
using a startup.properties file in the directory <domain-dir> \servers\<server-name> \data\nodemanager with the following arguments: -Xms1024m -Xmx1024m
and
Puting the memory arguments in the "Server Start" properties in the config.xml (This works fine for the managedservers)
How can I solve this?The nmstart command has a properties argument. Have you tried that?
nmStart([serverName], [domainDir], [props], [writer])
<Richard Greeven> wrote in message news:[email protected]..
I have a domain with one cluster containing 4 managed servers. Now I want to
start the adminserver with WLST using the Nodemanager. (I know there are
other/beter ways but in this situation I need to do it with Nodemanager).
The problem is that the Nodemanager doesn't add the right memory arguments
to the start command of the admin server.
This is what I do:
nmConnect(usernaam,password,host,port,domain)
nmstart(adminserver)
This does start the adminserver only without the proper memory arguments.
I tried:
using a startup.properties file in the directory <domain-dir>
\servers\<server-name> \data\nodemanager with the following
arguments: -Xms1024m -Xmx1024m
and
Puting the memory arguments in the "Server Start" properties in the
config.xml (This works fine for the managedservers)
How can I solve this? -
Java.io.IOException: write error
Can any one tell me whats the problem .
Can any one Tips for handling this errorYou received and error writing a file. Either you have no permission if you are trying to write from an applet or there is something invalid in the way you set it up.
-
Java.util.logging: write to one log file from many application (classes)
I have a menuapp to launch many applications, all running in same JVM and i want to add logging information to them, using java.util.logging.
Intention is to redirect the logginginfo to a specific file within the menuapp. Then i want all logging from all applications written in same file. Finally, if needed (but i don't think it is), i will include code to write logging to specific file per app (class). The latter is probably not neccessary because there are tools to analyse the logging-files and allow to select filters on specific classes only.
The applications are in their own packages/jars and contain following logging-code:
// Redirect error output
try {
myHandler = new FileHandler("myLogging.xml",1000000,2);
} catch (IOException e) {
System.out.println("Could not create file. Using the console handler");
myLogger.addHandler(myHandler);
myLogger.info("Our first logging message");
myLogger.severe("Something terrible happened");
...When i launch the menuapplication, it writes info to "myLogging.xml.0"
but when i launch an application, the app writes info to "myLogging.xml.0.1"
I already tried to leave out the creation of a new Filehandler (try/catch block in code above) but it doesn't help.
Is it possible to write loginfo to same specific file?You should open/close it somehow at every write from different processes.
But I personally prefer different file names to your forced merging, though. -
Error JRF when start AdminServer with WLST
Hello,
I have a problem when I want to start the AdminServer with my WLST command :
startServer('AdminServer','mydomain','t3://localhost:7001','user','pwd', 'D:/Oracle/Middleware/user_projects/domains/mydomain',jvmArgs='-Ddomain.home=D:/Oracle/Middleware/user_projects/domains/mydomain -Doracle.security.jps.config=D:/Oracle/Middleware/user_projects/domains/mydomain/config/fmwconfig/jps-config.xml -Doracle.domain.config.dir=D:/Oracle/Middleware/user_projects/domains/mydomain/config')
Here is the error (sorry, it's in French) :
WLST-WLS-1336736583189: <11 mai 2012 13 h 43 CEST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", oracle.jrf.UnknownPlatformException: JRF ne peut pas déterminer la plate-forme de serveur d'applications en cours.
WLST-WLS-1336736583189: oracle.jrf.UnknownPlatformException: JRF ne peut pas déterminer la plate-forme de serveur d'applications en cours.
WLST-WLS-1336736583189: at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
WLST-WLS-1336736583189: at oracle.jrf.wls.JRFStartup.main(JRFStartup.java:42)
WLST-WLS-1336736583189: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
WLST-WLS-1336736583189: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
WLST-WLS-1336736583189: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Even with all these Warning/Error, I can use the Administration Console, but not the EM...
nodemanager.domains : The domain directory is good.
nodemanager.properties : StartScriptEnabled=true
I run setDomainEnv.cmd before each run of the command.
Do you have any idea/advice ?
Thanks !Hello,
I tried to start the AdminServer with the nodemanager and it works perfectly :
"nmConnect('NMUser','NMpwd','localhost','5556','DomaineName','Domainedirectory')"
I had to change the NM user and NM Password in "domain_name, Security, General, and then expand the Advanced options at the bottom.".
But because of this action, I can't manage my others WebApp on the second host :
Here is my error :
"<Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'DomaineName' for user 'NMUser' denied".> "
Here is my configuration :
Domain is setup on the HOST1
AdminServer : HOST1
WebApp1 : HOST1
WebApp2 : Host2
I can't manage WebApp2. I restarted the NodeManager on Host2. Same error...
Do you already have this error ? The nodemanager.properties and nodemanager.domains are ok the Host2.
Thanks for your help ! -
Weblogic 8.1 SP 6 throws Read channel closed when sending SOAP message
Hi,
I am using Weblogic8.1 SP6 & Axis1 to send SOAP message through RPC call using SSL. This is working intermittently.
I use WLSSLAdapter to set up the SSL, and some properties I set:
System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
System.setProperty("javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
In case of error, the server throws this:
java.io.IOException: Read channel closed
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Sourc
e)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown S
ource)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown S
ource)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Sourc
e)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown S
ource)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
AT java.io.FilterOutputStream.write(FilterOutputStream.java:80)
at weblogic.webservice.binding.soap.HttpClientBinding.writeToStream(HttpClientB
inding.java:430)
at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBinding.ja
va:219)
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHandler.j
ava:37)
at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.jav
a:143)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:471)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
Before sending message, application will first retrieve WSDL from the target. This is always success.
I need to know how to fix this problem.
Any help is appreciated. Thanks.
AlvinHi,
Even I am facing the same issue could any body help me out to solve this issue. -
Java.io.IOException: Data error (cyclic redundancy check)
Dear everyone,
I have a utility that copys a file, using streams.
It has always worked fine, but I ran into an
exception this morning:
java.io.IOException: Data error (cyclic redundancy check)
from the call:
int bytes = fileInputStream.read(byteBuffer);
Would you know what this exception is about? I
haven't seen that exception after that, though.
So it's a bit puzzling. Any help, or clue towards
solving this problem is appreciated.
Thanks a lot!
GeorgeIt's like the data stream is getting messed up...so I would think of a few things:
1) Bad memory?
2) Bad connections?
3) Bad disk?
4) Viruses
Anything that can screw up the data steam.
Other than that....maybe as simple as reinstall the JVM and put new compiled code out there and see if it behaves. -
Issue while starting AdminSerever using wlst commands
Hi, I am facing issue while trying to start the AdminServer and Managed Server via nodemanager using wlst commands. I have installelled WebLogic 11g on windows 2008 R2. Mentioned below are the steps that I followed:
1) In Nodemanager.properties files I set following parameters to true. I did this, so that nodemanager can start the server in case of crash.
CrashRecoveryEnabled=true
StartScriptEnabled=true
2) started nodemanager and then started AdminServer from the command prompt as follows:
nmConnect('weblogic','password','10.23.226.58','5556','IMDomain','E:\Oracle\Middleware\user_projects\domains\IMDomain','ssl')
nmStart('AdminServer')
I dont see any errors but it seems the AdminServer do Not start properly as in the cmd window I don't see any 'started successfully' message - the message remains as *"Starting AdminServer..."*
However in the adminServer logs I see that the status is Running (refer logs at the end) and I can also see it as Running in weblogic console.
I really didnt care if its not giving a success message in cmd window but the problem occurs when I start the managedServer. After starting the managed server in about 10 minutes, there is a stuck thread. (I guess it is 10 mins because Stuck Thread MaxTime value is 600).
If I set StartScriptEnabled=false, and start by directly running the startweblogic.cmd then it works fine.
I am struggling with this for last 1 week, appreciate any help.
LOGS.......
Starting WLS with line:
E:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -Dweblogic.security.SSL.nojce=true -Xverify:none -da -Dplatform.home=E:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dwli.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\integration -Dweblogic.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=E:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;E:\Oracle\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
<Mar 14, 2012 3:16:30 PM CDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Mar 14, 2012 3:16:30 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Mar 14, 2012 3:16:30 PM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.2-b06 from Sun Microsystems Inc.>
<Mar 14, 2012 3:16:31 PM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Mar 14, 2012 3:16:32 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 14, 2012 3:16:32 PM CDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 14, 2012 3:16:32 PM CDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\Oracle\Middleware\user_projects\domains\IMDomain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<Mar 14, 2012 3:16:36 PM CDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 14, 2012 3:16:37 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Mar 14, 2012 3:16:37 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Mar 14, 2012 3:16:39 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
Mar 14, 2012 3:16:39 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.227.211.13:8001 for protocols iiop, t3, ldap, snmp, http.>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "IMDomain" running in Production Mode>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\PROGRA~1\Java\JDK16~1.0_2\jre\lib\security\cacerts.>
<Mar 14, 2012 3:20:53 PM CDT> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 14:12:27 CST 2002,
To: Tue Mar 22 15:12:27 CDT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 15, 2012 11:41:41 AM CDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "650" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@68a3f7ed", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)
java.io.InputStream.read(InputStream.java:85)
com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)
com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
com.certicom.tls.record.ReadHandler.read(Unknown Source)
com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
java.io.InputStreamReader.read(InputStreamReader.java:167)
java.io.BufferedReader.fill(BufferedReader.java:136)
java.io.BufferedReader.readLine(BufferedReader.java:299)
java.io.BufferedReader.readLine(BufferedReader.java:362)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:289)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:102)
weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:47)
weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<Mar 15, 2012 11:42:41 AM CDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "710" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@68a3f7ed", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)
java.io.InputStream.read(InputStream.java:85)
com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)
com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
com.certicom.tls.record.ReadHandler.read(Unknown Source)
com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
java.io.InputStreamReader.read(InputStreamReader.java:167)
java.io.BufferedReader.fill(BufferedReader.java:136)
java.io.BufferedReader.readLine(BufferedReader.java:299)
java.io.BufferedReader.readLine(BufferedReader.java:362)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:289)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:102)
weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:47)
weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>Hi chamila,
I never tried the example. Exception is not clear. Could you please post more stack trace from log files.
Thanks,
Sham -
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> <WebLoHello 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 -
Java Web Start Error - java.io.IOException: EOF reading band
I am using Java Web Start to download an application and I am getting the following error. How do I resolve this? The jar that is being downloaded is present in the directory.
java.io.IOException: EOF reading band
at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method)
at com.sun.java.util.jar.pack.NativeUnpack.run(Unknown Source)
at com.sun.java.util.jar.pack.NativeUnpack.run(Unknown Source)
at com.sun.java.util.jar.pack.UnpackerImpl.unpack(Unknown Source)
at com.sun.deploy.net.HttpDownloadHelper.download(Unknown Source)
at com.sun.deploy.cache.Cache.downloadResourceToTempFile(Unknown Source)
at com.sun.deploy.cache.Cache.downloadResourceToCache(Unknown Source)
at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload.downloadJarFiles(Unknown Source)
at com.sun.javaws.LaunchDownload.downloadEagerorAll(Unknown Source)
at com.sun.javaws.Launcher.downloadResources(Unknown Source)
at com.sun.javaws.Launcher.prepareLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)jfdenise wrote:
Hi,
I am facing the exact same issue when getting a big jar of more than 7 megs. It seems to occur in some special network configuration that I am not yet able to figure out. It is obviously linked to the fact that the jar is unpacked on the client side.
Anybody ran into this one and understood the root cause?Please, don't resurrect old threads, and don't use signatures with addresses. I'm locking this thread.
Kaj -
Error in SOAP receiver channel: java.io.IOException: invalid http response:
Hi experts,
I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"Did you check this?
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Regards
Pothana -
Axis Client Web Service call problem: java.io.IOException: Stream closed
Hi, I tried to call a webservice from Axis Client, and I encounter the following error. Do you guys have any idea what actually happens?
Please help, I am newbie in web services.
==============Root Cause===============
AxisFault
faultCode: { h t t p : / / schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: Stream closed
faultActor:
faultNode:
faultDetail:
{h t t p : / / xml.apache.org/axis/}stackTrace:java.io.IOException: Stream closed
at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:170)
at java.io.FilterInputStream.read(FilterInputStream.java:111)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108)
at java.io.FilterInputStream.read(FilterInputStream.java:90)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127)
at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.java:688)
at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(HttpMethodBase.java:796)
at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:224)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
{h t t p : / / xml.apache.org/axis/}hostname:compname
java.io.IOException: Stream closed
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:301)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: java.io.IOException: Stream closed
at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:170)
at java.io.FilterInputStream.read(FilterInputStream.java:111)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108)
at java.io.FilterInputStream.read(FilterInputStream.java:90)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127)
at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.java:688)
at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(HttpMethodBase.java:796)
at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:224)
... 17 more I am calling through proxy, the setting is as follows:
System.setProperty("https.proxyHost", [proxyname here]);
System.setProperty("https.proxyPort", [proxyport here]);
System.setProperty("http.proxyHost", [proxyname here]);
System.setProperty("http.proxyPort", [proxyport here]);Are there any problems showing up in the server's log?
-
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
Maybe you are looking for
-
i connected the iphone to a new itunes it told me that its restoring and itwill take 5 more hours and i did as told although i have so many things on the iphone i dont wanna lose then for my luck it suddenly opened again and it asked for the passcode
-
Help getting a Photoshop CS4 script to work with PS CS5?
I don't know AppleScript, but have a script for Photoshop CS4 that saves to the currently open image as a .png file on the desktop try tell application "Adobe Photoshop CS4" activate --get the current document name set myDoc to the current document s
-
Unkown error (-50) ipod classic
i have recently been having a lot of issues with my ipod. ever since i updated my itunes to the most recent.songs not syncing onto it and when they do they are named wrong and have the wrong album artwork. or even better some of them just dont play.
-
Permissions from mulitple policies
I am pretty new to the whole world of OBIEE and am trying to find information on how permissions from application policies are granted. Assume a brand new install of 11.1.1.5 Out of the box the Authenticated User role is a member of BI Consumer. Clon
-
I'm using a number of Mac minis to run kiosks and would like to have just one monolithic disk image that I distribute to all of them, for ease of administration. But how do I manage the OS-X licensing in this situation? I shouldn't have to buy any ad