Skip to main content

Hi

Fresh installation from buildHome on win2016, UPD17, db Oracle 19c

I have many errors NullPointerException sometimes without details sometimes with details in AdminServer\PROD.log as below. Does anyone had similar problem? What should I check more?

###<2023-01-29 21:36:33,371 CET> <Error> <Kernel> <APP> <ManagedServer1> <[active] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cf2a4b4e-ae12-4d64-afbb-2fa096f1f199-00001b31> <1675024593371> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000802> <ExecuteRequest failed
 java.lang.NullPointerException.
java.lang.NullPointerException
    at weblogic.socket.NIOOutputStream.getByteBuffer(NIOOutputStream.java:210)
    at weblogic.socket.NIOOutputStream.write(NIOOutputStream.java:218)
    at weblogic.websocket.internal.WSChunkOutput.writeToSocket(WSChunkOutput.java:228)
    at weblogic.websocket.internal.WSChunkOutput.flush(WSChunkOutput.java:208)
    at weblogic.websocket.internal.WSChunkOutput.sendRawData(WSChunkOutput.java:127)
    at weblogic.websocket.tyrus.TyrusMuxableWebSocket.sendRawData(TyrusMuxableWebSocket.java:167)
    at weblogic.websocket.tyrus.TyrusServletWriter.write(TyrusServletWriter.java:75)
    at org.glassfish.tyrus.core.ProtocolHandler.write(ProtocolHandler.java:484)
    at org.glassfish.tyrus.core.ProtocolHandler.send(ProtocolHandler.java:270)
    at org.glassfish.tyrus.core.ProtocolHandler.close(ProtocolHandler.java:467)
    at org.glassfish.tyrus.core.TyrusWebSocket.close(TyrusWebSocket.java:260)
    at org.glassfish.tyrus.core.TyrusWebSocketEngine$TyrusConnection.close(TyrusWebSocketEngine.java:853)
    at weblogic.websocket.tyrus.TyrusMuxableWebSocket$2.run(TyrusMuxableWebSocket.java:103)
    at weblogic.websocket.tyrus.TyrusMuxableWebSocket$4$1.run(TyrusMuxableWebSocket.java:252)
    at weblogic.websocket.tyrus.TyrusMuxableWebSocket$4$1.run(TyrusMuxableWebSocket.java:249)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:328)
    at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
    at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
    at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
    at weblogic.websocket.tyrus.TyrusMuxableWebSocket$4.run(TyrusMuxableWebSocket.java:249)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:678)
    at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
    at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
    at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
    at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:652)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)

Hi @knepiosko,

This appears to be caused by the default Socker Muxer in Weblogic, which needs to be changed based on the OS version. The error is referring to the NIOSocketMuxer, which is the default setting in Weblogic. If your Application Server is installed on Windows, it needs to be changed to NTSocketMuxer. You can specify the Muxer class in startup parameters of the relevant server. 

Please refer to below KBA regarding how to set this startup parameter. The error mentioned in the KBA is a different one, but the solution should be applicable for this one as well.

Since the error occurs for ManagedServer1, you need to do the above setting for that.

Hope this helps!

Hi @Charith Epitawatta

 

I have reconfigured application using Your hint. Custom java parameter is only available for ManagedServer1 so I set only this.

I have to monitor AS and MS1 logs to check result.

Thank You very much.

Reply


Terms & ConditionsCookie settings