One of the issues that occur after WebSphere tuning

Source: Internet
Author: User
Tags session id xms

Linux under websphere7.0, tuning after restarting WebSphere error:

Admu0116i:tool information is being logged in file
/opt/ibm/websphere/appserver/profiles/appsrv01/logs/server1/startserver.log
Admu0128i:starting tool with the APPSRV01 profile
Admu3100i:reading Configuration for Server:server1
Admu3200i:server launched. Waiting for initialization status.
Admu3011e:server launched but failed initialization. StartServer.log,
SystemOut.log (or job log in ZOS) and other log files under
/opt/ibm/websphere/appserver/profiles/appsrv01/logs/server1 should
Contain failure information.

View SystemOut.log File:

[13-8-16 13:29:04:098 gmt+08:00] 0000001c webapp E com.ibm.ws.webcontainer.webapp.WebApp logservleterror srve0293e: [Servlet error]-[action]: Com.ibm.ws.sm.workspace.WorkSpaceException:WKSP0011E Unable to create existing session ID FILE/O PT/IBM/WEBSPHERE/APPSERVER/PROFILES/APPSRV01/WSTEMP/92668751/WORKSPACE/.WORKSPACE_D6ENAENTFVUYYQXSIU88ZYF-- Java.io.IOException:Too Many open files
At Com.ibm.ws.sm.workspace.impl.WorkSpaceLogger.createException (workspacelogger.java:114)
At Com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.createSessionIdFile ( workspacemasterrepositoryadapter.java:1078)
At Com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.setSessionId ( workspacemasterrepositoryadapter.java:994)
At Com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.setSessionId (workspaceimpl.java:537)
At Com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.createWorkSpace (workspacemanagerimpl.java:209)
At Com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getWorkSpace (workspacemanagerimpl.java:302)
At Com.ibm.isclite.runtime.action.LoginAction.createWorkSpace (loginaction.java:385)
At Com.ibm.isclite.runtime.action.LoginAction.createUser (loginaction.java:349)
At Com.ibm.isclite.runtime.action.LoginAction.execute (loginaction.java:278)
At Org.apache.struts.action.RequestProcessor.processActionPerform (Unknown Source)
At Org.apache.struts.action.RequestProcessor.process (Unknown Source)
At Org.apache.struts.action.ActionServlet.process (Unknown Source)
At Org.apache.struts.action.ActionServlet.doGet (Unknown Source)
At Javax.servlet.http.HttpServlet.service (httpservlet.java:718)
At Javax.servlet.http.HttpServlet.service (httpservlet.java:831)
At Com.ibm.ws.webcontainer.servlet.ServletWrapper.service (servletwrapper.java:1655)
At Com.ibm.ws.webcontainer.servlet.ServletWrapper.service (servletwrapper.java:1595)
At Com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter (webappfilterchain.java:131)
At Com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence (wscurlfilter.java:927)
At Com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState (wscurlfilter.java:494)
At Com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter (wscurlfilter.java:315)
At Com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter (filterinstancewrapper.java:188)
At Com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter (webappfilterchain.java:116)
At Com.ibm.ws.webcontainer.filter.webappfilterchain._dofilter (webappfilterchain.java:77)
At Com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter (webappfiltermanager.java:908)
At Com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest (servletwrapper.java:932)
At Com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest (servletwrapper.java:500)
At Com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest (servletwrapperimpl.java:178)
At Com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest (cacheservletwrapper.java:91)
At Com.ibm.ws.webcontainer.WebContainer.handleRequest (webcontainer.java:864)
At Com.ibm.ws.webcontainer.WSWebContainer.handleRequest (wswebcontainer.java:1583)
At Com.ibm.ws.webcontainer.channel.WCChannelLink.ready (wcchannellink.java:186)
At Com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination (httpinboundlink.java:455)
At Com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation (httpinboundlink.java:384)
At Com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete (httpiclreadcallback.java:83)
At Com.ibm.ws.ssl.channel.impl.sslreadservicecontext$sslreadcompletedcallback.complete ( sslreadservicecontext.java:1772)
At com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted (aioreadcompletionlistener.java:165)
At Com.ibm.io.async.AbstractAsyncFuture.invokeCallback (abstractasyncfuture.java:217)
At Com.ibm.io.async.AsyncChannelFuture.fireCompletionActions (asyncchannelfuture.java:161)
At com.ibm.io.async.AsyncFuture.completed (asyncfuture.java:138)
At Com.ibm.io.async.ResultHandler.complete (resulthandler.java:204)
At Com.ibm.io.async.ResultHandler.runEventProcessingLoop (resulthandler.java:775)
At Com.ibm.io.async.resulthandler$2.run (resulthandler.java:905)
At Com.ibm.ws.util.threadpool$worker.run (threadpool.java:1550)
caused by:java.io.IOException:Too many open files
At Java.io.File.createNewFile (file.java:883)
At Com.ibm.wsspi.configarchive.DefaultFileAccessor.createNewFile (defaultfileaccessor.java:246)
At Com.ibm.ws.sm.workspace.impl.FileAccessorUtil.createNewFile (fileaccessorutil.java:280)
At Com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.createSessionIdFile ( workspacemasterrepositoryadapter.java:1046)
... More

View Native_stderr.log File:

Jvmj9gc021e-xmo must be equal to-XMS
JVMJ9VM015W initialization error occurred in library J9GC24 (2) failed to initialize
Could not create the Java virtual machine.

Locate the configuration file:

/opt/ibm/websphere/appserver/profiles/appsrv01/config/cells/cmmi-contrbtnode01cell/nodes/cmmi-contrbtnode01/ Servers/server1 under Server.xml Modify the value of-xmo equals-xms, start WebSphere, issue resolution.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.