Socket Exception in Admin Server Logs

Hi All,
We are facing a socket exception in Admin Server log. PFB for the exception logs:
[2011-12-26T00:36:21.793-06:00] [AdminServer] [WARNING] [] [oracle.adfinternal.view.faces.renderkit.rich.TreeRendererUtils] [tid: [ACTIVE].ExecuteThread: '44' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000JHt5O2e6yGD_n95EiZ1Ev5590005ms,0] [APP: em] [dcid: 88568bb1654f17ca:22e22403:1344b1dc283:-7ffe-0000000000042162] Context menu child is not a RichMenu
[2011-12-26T00:39:05.574-06:00] [AdminServer] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '44' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000JHt60Xn6yGD_n95EiZ1Ev5590005nI,0] [APP: em] [dcid: 88568bb1654f17ca:22e22403:1344b1dc283:-7ffe-0000000000042182] Server Exception during PPR, #126[[
java.net.SocketException: Write failed: Broken pipe
     at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
     at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:46)
     at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java)
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:507)
     at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:486)
     at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:382)
     at weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:313)
     at weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:174)
     at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:111)
     at weblogic.servlet.internal.ServletResponseImpl.flushBuffer(ServletResponseImpl.java:185)
     at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:176)
     at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:176)
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:229)
     at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
     at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
     at oracle.sysman.emSDK.adfext.ctlr.EMViewHandlerImpl.renderView(EMViewHandlerImpl.java:149)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:710)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:273)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:205)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:164)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[2011-12-26T00:39:07.687-06:00] [AdminServer] [WARNING] [] [oracle.adfinternal.view.faces.renderkit.rich.TreeRendererUtils] [tid: [ACTIVE].ExecuteThread: '44' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000JHt60co6yGD_n95EiZ1Ev5590005nJ,0] [APP: em] [dcid: 88568bb1654f17ca:22e22403:1344b1dc283:-7ffe-0000000000042183] Context menu child is not a RichMenu
[2011-12-26T00:41:42.485-06:00] [AdminServer] [WARNING] [] [oracle.adfinternal.view.faces.renderkit.rich.TreeRendererUtils] [tid: [ACTIVE].ExecuteThread: '65' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000JHt6aR46yGD_n95EiZ1Ev5590005na,0] [APP: em] [dcid: 88568bb1654f17ca:22e22403:1344b1dc283:-7ffe-0000000000042198] Context menu child is not a RichMenu
[2011-12-26T10:30:56.963-06:00] [AdminServer] [WARNING] [] [org.apache.myfaces.trinidad.webapp.ResourceServlet] [tid: [ACTIVE].ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000JHvDUMs6yGD_n95EiZ1Ev5590005q5,0] [APP: em] [dcid: 88568bb1654f17ca:22e22403:1344b1dc283:-7ffe-0000000000046718] ResourceServlet._setHeaders(): Content type for /bi/jsLibs/engine_20100410.swf is NULL![[
Cause: Unknown file extension
Kindly provide us a solution to avoid this issue.
Thanks & Regards,
Prabhu

It seems that chunking is causing the issue. In the HTTP Transport Configuration Options of your business service, disable the setting "Use Chunked Streaming Mode"
Regards,
Anuj

Similar Messages

  • BPEL Admin:   Server / Log tab: Where this log is generated?

    Hi All
    There is a log configuration tab on BPEL Admin (where you can configure log for apache axis for instance), but I can´t locate where this log is beeing generated, can you help me please?
    I have already checked log files on:
    {OracleHome}/bpel/domains/xxx/log
    {OracleHome}/j2ee/bpel/log
    {OracleHome}/opmn/logs
    Thanks

    Hi Afonso
    I´m trying to catch some log for Apache Axis or something related to SOAP messages, WSIF or WebServices call.
    I have two BPEL process (lets say A and B).
    Process A call process B using dynamic partner links (setting the EndpointReference at runtime).
    I have also two BPEL servers installations: let´s say 1 and 2.
    If I deploy these two process on the server 1, everything works fine.
    If I deploy the process on the server 2, I get this error:
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message transmission failure, response code: 500
    We are trying to find out what is the diference between server 1 and server 2, as we believe they should be igual (both are 10.1.3.3.0).
    And now I believe I have just found another BPEL Bug, because the log configuration on BPEL Admin seen to not work!
    []´s

  • Socket Exception when closing Server Socket Streams if Client closes first

    Hi
    I have 2 processes - a Server socket and a client socket. If I close the Client process first, and then try closing down the Streams on the Server process, I get a SocketException with message "Socket is closed" when I try and close the 2nd Stream. It does not matter on the order of the Stream being closed down, the exception is always thrown when I try and close the second stream. The code snippets are below:
    SERVER =======
    import java.io.InputStream;
    import java.io.OutputStream;
    import java.net.ServerSocket;
    import java.net.Socket;
    public class ServerSocketTest {
    public static void main(String args[]) {
    try {
    ServerSocket ss = new ServerSocket(9999);
    Socket s = ss.accept();
    // Get refs to streams...
    InputStream is = s.getInputStream();
    OutputStream os = s.getOutputStream();
    // sleep to let client shutdown first...
    try {
    Thread.sleep(10000);
    } catch (InterruptedException e) {
    System.err.println(e);
    System.err.println("B4 inClose: isBound=" + s.isBound());
    System.err.println("B4 inClose: isClosed=" + s.isClosed());
    System.err.println("B4 inClose: isConnected=" + s.isConnected());
    System.err.println("B4 inClose: isInputShutdown=" + s.isInputShutdown());
    System.err.println("B4 inClose: isOutputShutdown=" + s.isOutputShutdown());
    s.getInputStream().close();
    System.err.println("After inClose: isBound=" + s.isBound());
    System.err.println("After inClose: isClosed=" + s.isClosed());
    System.err.println("After inClose: isConnected=" + s.isConnected());
    System.err.println("After inClose: isInputShutdown=" + s.isInputShutdown());
    System.err.println("After inClose: isOutputShutdown=" + s.isOutputShutdown());
    s.getOutputStream().close(); // will break here with SocketException!
    System.err.println("After outClose: isBound=" + s.isBound());
    System.err.println("After outClose: isClosed=" + s.isClosed());
    System.err.println("After outClose: isConnected=" + s.isConnected());
    System.err.println("After outClose: isInputShutdown=" + s.isInputShutdown());
    System.err.println("After outClose: isOutputShutdown=" + s.isOutputShutdown());
    s.close();
    } catch (Exception e) {
    System.err.println(e);
    CLIENT ======
    import java.net.Socket;
    public class ClientSocket {
    public static void main(String args[]) {
    try {
    Socket s = new Socket("localhost", 9999);
    try {
    // sleep to leave connection up for a while...
    Thread.sleep(2000);
    } catch (InterruptedException e) {
    System.err.println(e);
    s.close();
    } catch (Exception e) {
    System.err.println(e);
    The debug shows that isClosed() is set to 'true' after the first call to s.getInputStream().close(). The Sun API Socket class getOutputStream() has a call to isClosed() at the start of the method - it then throws the SocketException that I get. Why does the SocketImpl do this before I get a chance to call a.getOutputStream().close()?
    One final thing, the calls to s.isInputShutdown() and s.isOuputShutdown always seem to return false even if the Streams have had their .close() method called.
    Any ideas/help here greatly appreciated.
    Thanks
    Gaz

    Ok, I know what's going on now - I needed something to do on Friday afternoon anyhow!
    Basically if you call either getOutputStream.close() or getInputStream().close(), the underlying Sun implementation will close the Socket.
    Here's what's happening under the covers in the Sun code:
    s.getInputStream() is called on the Socket class.
    The Socket class holds a reference to the SocketImpl class.
    The SocketImpl class is abstract and forces sublclasses to extend it' s getInputStream() method.
    The PlainSocketImpl extends SocketImpl.
    PlainSocketImpl has a getInputStream() method that returns a SocketInputStream. When the stream is created for the first time, the PlainSocketImpl object is passed into the Constructor.
    The SocketInputStream class has a close() method on it. The snippet of code below shows how the socket is closed:
    <pre>
    * Closes the stream.
    private boolean closing = false;
    public void close() throws IOException {
         // Prevent recursion. See BugId 4484411
         if (closing)
         return;
         closing = true;
         if (socket != null) {
         if (!socket.isClosed())
              socket.close();
         } else
         impl.close();
         closing = false;
    </pre>
    So, it seems that out PlainSocketImpl is getting closed for us, hence the SocketException being thrown in Socket.getOutputStream() when I call it after Socket.getInputStream()/
    I've not had a look at the reason why the calls to s.isInputShutdown() and s.isOuputShutdown always seem to return false even if the Streams have had their .close() method called though - any thoughts appreciated.
    Thanks
    G

  • Assertion Exception in Cache Server log

    Can someone let me know in what circumstances do we see the below exception
    2011-06-17 02:30:06,811 ERROR [Logger@9236976 3.6.0.1] Coherence 2011-06-17 02:30:06.809/199.394 Oracle Coherence GE 3.6.0.1 <Error> (thread=DistributedCache, member=1): Assertion failed:
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.registerPoll(Grid.CDB:36)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.post(Grid.CDB:31)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.checkDistribution(PartitionedService.CDB:80)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:15)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    at java.lang.Thread.run(Thread.java:662)
    2011-06-17 02:30:06,812 ERROR [Logger@9236976 3.6.0.1] Coherence 2011-06-17 02:30:06.809/199.394 Oracle Coherence GE 3.6.0.1 <Error> (thread=DistributedCache, member=1): Terminating PartitionedCache due to unhandled exception: com.tangosol.util.AssertionException
    2011-06-17 02:30:06,874 ERROR [Logger@9236976 3.6.0.1] Coherence 2011-06-17 02:30:06.809/199.394 Oracle Coherence GE 3.6.0.1 <Error> (thread=DistributedCache, member=1):
    com.tangosol.util.AssertionException:
    at com.tangosol.coherence.Component._assertFailed(Component.CDB:12) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.Component._assert(Component.CDB:3) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.registerPoll(Grid.CDB:36) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.post(Grid.CDB:31) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.checkDistribution(PartitionedService.CDB:80) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:15) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3) [coherence-3.6.0.1.jar:3.6.0.1]
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42) [coherence-3.6.0.1.jar:3.6.0.1]
    at java.lang.Thread.run(Thread.java:662) [na:1.6.0_24]
    2011-06-17 02:30:08,479 INFO [Logger@9236976 3.6.0.1] Coherence 2011-06-17 02:30:08.478/201.063 Oracle Coherence GE 3.6.0.1 <Info> (thread=Thread-0, member=1): Restarting Service: DistributedCache
    Thanks,
    Yashas

    Jonathan.Knight wrote:
    Hi,
    Yes, with two nodes you should be able to put more data into your Coherence cluster - the capacity scales with the number of storage nodes in the cluster.
    Actually, this is not true. :-)
    By default configuration, and not using indexes, you are able to store the same amount of data in one node as in two nodes in case of a distributed cache.
    This is because if you have one node, Coherence does not create backups. If you have two nodes, it creates one backup (if you configured a backup, which default configuration did).
    It starts to increase total capacity only with the third node (assuming backup count is 1).
    All of this assuming that all nodes are storage-enabled and are running the service.
    Best regards,
    Robert

  • Socket Exception in Weblogic Server when invoking webservice via JPD

     

    We faced with the similar issue in WLS 7.X after below Assertion error after restoring services we were able to resolve this issue for time being as per the weblogic there is a patch provided by BEA and this sort of issue is resolved.
    This issue has been identified and updated under cars CR103525
    Regards,
    CSR
    BEA Analyst

  • Weblogic admin server error.

    Hi Team,
    I am trying to started weblogic admin server from windows i am getting below error from admin server logs.
    but I am able to start weblogic from the command prompt.
    I verified classpath are same in command prompt and windows services and Node Manager also working fine from windows services.
    Please help me on this.it is urgent for me .
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000436> <Allocating 2 reader threads.>
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000446> <Native IO Enabled.>
    ####<Nov 14, 2012 8:31:27 PM GMT+05:30> <Info> <IIOP> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905287039> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288695> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288898> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090511> <The following exception has occurred:
    com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Error> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Notice> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Critical> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289023> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FAILED>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Error> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Info> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000236> <Stopping execute threads.>
    Thanks in advance.
    Regards,
    Ravi.

    Hi,
    Check this link :
    Re: myrealm error when start through node manager

  • Weblogic 8.1 managed server unable to contact Admin server

    I have a strange issue here.
    I have admin server on Linux Machine A
    Managed server on Linux Machine B.
    When i try to start managed server on Machine B, i get the following error.
    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://MachineA:7100/wl_management_internal2/Bootstrap, user: system
    java.io.EOFException
    at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputStream.java:2571)
    at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:1990)
    The error suggests that managed server on machine B, is unable to contact Admin server on Machine A.
    But i know for sure that Admin server is running on that port 7100 for sure.
    It has been for the last 3 years.
    To see if Machine B and Machine A have network issues, i did telnet.
    From Machine B: i typed the following
    telnet MachineA 7100
    Connected to MachineA.
    Escape character is '^]'
    The above telnet command tells us that no network issues exist.
    After a few tries, the managed server contacts to admin server and comes up.
    This is not a one time thing.
    I saw this behavior many times.
    How should i resolve this?
    Edited by: gvamsius on Feb 12, 2009 1:23 PM

    Every thing is configured fine.
    Nothing wrong with Configuration.
    This domain has been running for the past 3 years.
    Recently, i found something interesting in admin server logs, when i try to start the managed servers.
    I realized there will be some amount of hand shake that happens during managed server startup, when it tries to communicate with admin server.
    Here is the log snippet when managed server A contacts Admin server and starts up successfully.
    ####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server A.>
    ####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server A.>
    ####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server A.>
    ####<Mar 10, 2009 12:11:46 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
    Here is the log snippet when managed server B contacts Admin server and does not start.
    ####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server B.>
    ####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server B.>
    ####<Mar 10, 2009 12:07:08 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server B.>
    The difference as you can see here is that managed server starts up only when Admin Server does the following
    <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
    Does any one knows why Admin server would not send the above bootstrap configuation all the times for the managed servers?

  • Admin Server and Managed server startup problem

    Hi,
    My weblogic server version is 11g and OS is Linux.
    When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
    FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
    FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
    FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
    FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
    FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
    FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
    FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
    FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
    Module_base_address=0800000000003000
    Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
    CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
    - Stack Backtrace -
    /usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
    /usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
    /usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
    /usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
    0x00000000
    JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
    JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
    JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
    JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
    UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
    JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
    JVMDUMP013I Processed dump event "gpf", detail "".
    After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
    <server>
    <name>AdminServer</name>
    <native-io-enabled>false</native-io-enabled>     
    <listen-port>9595</listen-port>
    <listen-address>10.10.15.16</listen-address>
    </server>
    i did the same thing for managed servers to start the server.
    My Question is:
    Are we missing any configurations/settings while creating domain?
    Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
    Regards,
    Naga

    Hi,
    my managed server heap size properties are
    -XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
    But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
    option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
    Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server?

  • Admin Server cannot start

    I installed the patch 117665-03 for Directory Server but i had the following error:
    Starting the admin server...
    Change dir to /var/opt/mps/serverroot/
    ./start-admin
    SunONE-WebServer-Enterprise/6.0SP3 B05/19/2004 02:48
    warning: daemon is running as super-user
    [LS ls1] http://localhost.mydomain.com, port 390 ready to accept requests
    failure: server initialization failed (Interrupted system call)
    Any solution for this error?
    What's happening?
    I tried to see the log but dont exist log on /var/opt/mps/admin-serv/logs.
    Please, i need a help.
    Thanks.
    Everton

    I had this problem and the pkgchk mentioned above helped to get the admin server going (thanks!) but I could not run the admin console. I saw:
    Exception in thread "main" java.lang.UnsupportedClassVersionError: org/GNOME/Accessibility/JavaBridge (Unsupported major.minor version 49.0)
    It turned out that something (I suspect the patch) had replaced my java1.5.0_06 binary with a java1.4.2_03 binary - but left the java1.5 directory structure alone! i.e. looking in /usr/jdk would have indicated that java1.5 was installed, but when I ran jdk1.5.0_06/bin/java -version , it reported java version "1.4.2_03". I was unimpressed.
    I ended up removing all the SUNWj5* packages and reinstalling them and then I could start the admin console.
    Now to find out what other damage this patch might have caused.....

  • V5.2 Admin-Server fails to start HP-UX 11i

    Hi,
    I'am installing on HP-UX 11i and everything works fine except of the Admin server.
    Executing the "start-admin" results in:
    $ ./start-admin
    SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 18:28
    failure: server terminated (signal 10) (Interrupted system call)
    failure: server initialization failed (Interrupted system call)
    $
    When i go to admin-serv/logs and have a look at the file "errors" all i see is:
    [07/Apr/2004:16:55:32] info ( 9038): SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 18:28
    [07/Apr/2004:16:55:32] catastrophe ( 9038): Server crash detected (signal SIGBUS)
    [07/Apr/2004:16:55:32] info ( 9038): Crash occurred in NSAPI SAF admin40_check_ds_availability_init
    Any help is very apprieciated.
    Many thanks in advance.
    Carsten

    5.1SP3 works great on HP-UX.
    5.2 will probably run well on HP-UX when 5.2SP3 is released (but first we need SP1 and SP2...)

  • WebLogic Admin Server (9.1)is not running.

    When I was trying to start Admin, it gives "There are nested errors" error message.

    Please share the admin server log snippet from the last start-up attempt to understand the cause of the failure which are located at domain_home/servers/adminserver/logs. The file named would be adminserver.log.
    Without this information, we would not be able to understand the cause of the failure.

  • Problems in starting Admin server for soa suite in windows 7 homebasic

    Hi All,
    I installed SOA Suite R1 in my laptop running windows 7 home basic version.
    Its 64 bit OS but I installed the files in win32 folder as it didn't allow me to install the generic file and even win64 file.
    installation was successful but after installation once I try to start the weblogic admin server using
    startAdminServer.cmd through my command prompt. It is running for few seconds and command prompt is getting closed abruptly and nothing comes up.
    It's very strange and I am not able to find out... Please help me.
    Thanks In Advance.

    Ideally you should be able to set up the 64-bit generic installer not sure of the reason...
    Please use the correct version of 64 bit jdk and check the logs
    You can check out the weblogic admin server logs
    BEA_HOME\user_projects\domains\your_domain\servers\AdminServer\logs

  • Admin server not sending bootstrap servlet configuration to managed servers

    I am having a bit of strange issue.
    I have weblogic 8.1 SP5 domain in PROD.
    14 managed servers in the domain
    When i start the managed serverA, sometimes it starts, sometimes it doesnt.
    By looking at admin server logs, i found the following.
    When the managed ServerA doesnt start, the admin server has the following log snippet
    <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server ServerA.>
    ####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA>
    ####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
    When the managed ServerA starts, the admin server has the following log snippet
    Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server serverA.>
    ####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA.>
    ####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
    ####<Apr 14, 2009 2:38:21 AM EDT> <Info> <Configuration Management> <catlmsxp166.corp.cox.com> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> *<The bootstrap servlet has finished sending the configuration to serverA.>*
    The difference is that admin server unable to send the bootstrap servlet configuration to managed servers, as highlighted above
    Has anyone encountered this issue?
    If so, is there is solution to this?
    Right now i am doing the work around (Which is restart admin server and then start managed server, for every managed server that does not start)
    But i cant do this all the time.
    MY domain has 14 managed servers. All of them exhibit similar behaviour.
    Some times they start, some times they dont.
    Edited by: gvamsius on Apr 14, 2009 1:22 PM
    Edited by: gvamsius on Apr 14, 2009 1:23 PM

    Honestly I've never seen a similar problem.
    Could you show us the "standard out" when you start the servers?
    Could you to show us the standard out when you start the servers?

  • Weblogic 11g Admin console - Admin Server Health shows "Warning"

    Hi,
    My env details : db 11.1.0.7, wls1033, RCU 11.1.1.3, soa 11.1.1.3, AIA11gR1 PS2
    When I start only Admin server, Health shows "Ok" but when I start soa_server1, Admin Server Health becomes "Warning".
    When I checked "Health information details" for Admin server, threadpool subsystem is showing "Warning".
    Steps I tried to resolve this issue : increased "Stuck Thread Max Time" to "1200" and "Stuck Thread Timer Interval" to "120" and restarted server, but still it shows "Warning" for Admin server Health
    Once I start soa_server1, Admin Server log shows below trace
    <Sep 30, 2010 3:39:38 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 30, 2010 5:17:34 PM IST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
    <Sep 30, 2010 5:21:34 PM IST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WLSServerControlTablePage.>
    <Sep 30, 2010 5:41:37 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,203" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@dbf6176", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace:
    Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
    sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:250)
    sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:289)
    sun.nio.cs.StreamDecoder.read(StreamDecoder.java:125)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.InputStreamReader.read(InputStreamReader.java:167)
    java.io.BufferedReader.fill(BufferedReader.java:105)
    java.io.BufferedReader.readLine(BufferedReader.java:288)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.BufferedReader.readLine(BufferedReader.java:362)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
    weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:93)
    ^-- Holding lock: weblogic.nodemanager.client.PlainClient@dbf5115[thin lock]
    weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
    weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:45)
    weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    >
    <Sep 30, 2010 5:41:37 PM IST> <Notice> <Diagnostics> <BEA-320068> <Watch 'StuckThread' with severity 'Notice' on server 'AdminServer' has triggered at Sep 30, 2010 5:41:37 PM IST. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND (MSGID = 'BEA-000337')
    WatchData: DATE = Sep 30, 2010 5:41:37 PM IST SERVER = AdminServer MESSAGE = [STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,203" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@dbf6176", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace:
    Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
    sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:250)
    sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:289)
    sun.nio.cs.StreamDecoder.read(StreamDecoder.java:125)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.InputStreamReader.read(InputStreamReader.java:167)
    java.io.BufferedReader.fill(BufferedReader.java:105)
    java.io.BufferedReader.readLine(BufferedReader.java:288)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.BufferedReader.readLine(BufferedReader.java:362)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
    weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:93)
    ^-- Holding lock: weblogic.nodemanager.client.PlainClient@dbf5115[thin lock]
    weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
    weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:45)
    weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    SUBSYSTEM = WebLogicServer USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-000337 MACHINE = navistarlnx01.in.corp.sa TXID = CONTEXTID = a29dda85e23940b7:-4a5394b7:12b621e55e6:-8000-000000000000005d TIMESTAMP = 1285848697597
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 600000
    >
    <Sep 30, 2010 5:41:55 PM IST> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in /u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/adr/diag/ofm/base_domain/AdminServer/incident/incdir_10 with a lockout minute period of 1.>
    <Sep 30, 2010 5:43:37 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,323" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@dbf6176", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace:
    Thread-21 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
    jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
    java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
    java.net.SocketInputStream.read(SocketInputStream.java:107)
    sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:250)
    sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:289)
    sun.nio.cs.StreamDecoder.read(StreamDecoder.java:125)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.InputStreamReader.read(InputStreamReader.java:167)
    java.io.BufferedReader.fill(BufferedReader.java:105)
    java.io.BufferedReader.readLine(BufferedReader.java:288)
    ^-- Holding lock: java.io.InputStreamReader@dbf1cdd[thin lock]
    java.io.BufferedReader.readLine(BufferedReader.java:362)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
    weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
    weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:93)
    ^-- Holding lock: weblogic.nodemanager.client.PlainClient@dbf5115[thin lock]
    weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
    weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:45)
    weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    Thx for your help.

    Is there any information on this StuckThread Issue ?
    It happens in every restart of the SOA Managed server.

  • The admin server could not be reached

    Dear All,
    I have oracle weblogic server running on red hat enterprise Linux, with one managed server. I created a self-signed certificate to access the admin server using SSL connection, after creating the certificate and start running the domain, The admin server run fine, but when i start running the managed server using
    $ ./startManagedWebLogic.sh osb_server1 https://server_ip:7006 i got that error, " The admin server could not be reached on https://server_ip:7006
    and the managed server running independence of admin server, as well as admin server can not establish jmx:t3 connection with the managed server on its SSL port
    also in admin server log i got this error
    <Sep 30, 2013 6:51:00 PM EET> <Warning> <JMX> <BEA-149504> <The adminstration server was unable to establish JMX Connectivity with the osb_server1 at the JMX Service URL of service:jmx:t3://172.17.11.13:8011/jndi/weblogic.management.mbeanservers.runtime.>
    how can i resolve this error?
    thanks in advanced 

    Hi John,
    Thanks. Notable errors in this log are:
    Failed to connect.[Root Cause: Connection refused ] com.hyperion.css.spi.util.jndi.pool.JNDIConnectionPool.validateSocketConnection(Unknown Source)
    Native Directory is not reachable. Will try to re-connect after 3 seconds... com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
    Attempting to connect to Native Directory: Retry Count: 10 com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
    Failed to connect to native directory. com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
    Any ideas?
    Thanks.
    Edited by: 960369 on 21-Sep-2012 02:56
    Edited by: 960369 on 21-Sep-2012 03:33

Maybe you are looking for