精华内容
下载资源
问答
  • WAS 启动失败

    2013-07-18 12:54:24
    ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in z/OS® ) and other log files under /home/dwhare/WebSphere61/profiles/Dmgr01/logs/d...
    今天服务器停止后,再也起不起来了

    ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in z/OS® ) and other log files under /home/dwhare/WebSphere61/profiles/Dmgr01/logs/dmgr should contain failure information.

    官方资料说是节点停止的时候启动应用服务器就会发生这个错误
    http://public.dhe.ibm.com/software/dw/jp/websphere/was/was7_adminguide/V7Guide_21_SysOpe_v2.pdf
    但,试了很多方法都没办法启动节点

    后来找到另一个官方资料才搞定的
    前后2个资料完全不相关。。。晕了
    http://www-01.ibm.com/support/docview.wss?uid=swg21244631

    Mark一记
    展开全文
  • Datastage 8.7安装后启动was失败

    千次阅读 2014-03-04 17:48:49
    按照安装教程安装虚拟机版的datastage 8.7后,使用命令启动was失败 infosrvr:~ # /opt/IBM/WebSphere/AppServer/bin/startServer.sh server1 ADMU0116I: Tool information is being logged in file /opt/IBM/...

    按照安装教程安装虚拟机版的datastage 8.7后,使用命令启动was失败

    infosrvr:~ # /opt/IBM/WebSphere/AppServer/bin/startServer.sh server1
    ADMU0116I: Tool information is being logged in file
               /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1/startServer.log
    ADMU0128I: Starting tool with the InfoSphere 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/InfoSphere/logs/server1 should
               contain failure information.

    按照提示查看报错日志:

    infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1 # tail -100 SystemErr.log 
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
            at java.lang.reflect.Method.invoke(Method.java:611)
            at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
            at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
            at org.eclipse.core.launcher.Main.run(Main.java:981)
            at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:340)
            at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:110)
    Caused by: 
    com.ascential.xmeta.repository.core.CoreRepositoryException: Error initializing persistence manager module
            at com.ascential.xmeta.repository.core.impl.DefaultSandbox.<init>(DefaultSandbox.java:70)
            at java.lang.J9VMInternals.newInstanceImpl(Native Method)
            at java.lang.Class.newInstance(Class.java:1345)
            at com.ascential.xmeta.repository.core.CoreRepositoryFactory.createSandbox(CoreRepositoryFactory.java:97)
            at com.ascential.xmeta.service.repository.core.SandboxPojoBusiness.<init>(SandboxPojoBusiness.java:61)
            ... 70 more
    Caused by: 
    com.ascential.xmeta.persistence.PersistenceManagerException: com.ascential.xmeta.persistence.PersistenceException: PersistentEObjectPersistenceException initializing persistence.
            at com.ascential.xmeta.persistence.impl.basic.BasicPersistenceManager.initialize(BasicPersistenceManager.java:78)
            at com.ascential.xmeta.repository.core.impl.DefaultSandbox.<init>(DefaultSandbox.java:68)
            ... 74 more
    Caused by: 
    com.ascential.xmeta.persistence.PersistenceException: PersistentEObjectPersistenceException initializing persistence.
            at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.initialize(BasicPersistence.java:462)
            at com.ascential.xmeta.persistence.impl.basic.BasicPersistenceManager.initialize(BasicPersistenceManager.java:74)
            ... 75 more
    Caused by: 
    com.ascential.xmeta.persistence.orm.PersistentEObjectPersistenceException: org.apache.ojb.broker.PersistenceBrokerException: Can't lookup a connection
            at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistenceRegistry.loadPackageCache(OjbPersistentEObjectPersistenceRegistry.java:446)
            at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistenceRegistry.initialize(OjbPersistentEObjectPersistenceRegistry.java:134)
            at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.initialize(OjbPersistentEObjectPersistence.java:372)
            at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.initialize(BasicPersistence.java:451)
            ... 76 more
    Caused by: 
    org.apache.ojb.broker.PersistenceBrokerException: Can't lookup a connection
            at org.apache.ojb.broker.accesslayer.ConnectionManagerImpl.localBegin(Unknown Source)
            at org.apache.ojb.broker.core.PersistenceBrokerImpl.beginTransaction(Unknown Source)
            at org.apache.ojb.broker.core.DelegatingPersistenceBroker.beginTransaction(Unknown Source)
            at org.apache.ojb.broker.core.DelegatingPersistenceBroker.beginTransaction(Unknown Source)
            at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistenceRegistry.loadPackageCache(OjbPersistentEObjectPersistenceRegistry.java:437)
            ... 79 more
    Caused by: 
    org.apache.ojb.broker.accesslayer.LookupException: Could not borrow connection from pool. Active/Idle instances in pool=0/0. org.apache.ojb.broker.metadata.JdbcConnectionDescriptor:  org.apache.ojb.broker.metadata.JdbcConnectionDescriptor@59a959a9[
      jcd-alias=pojo
      default-connection=false
      dbms=Db2
      jdbc-level=2.0
      driver=com.ibm.db2.jcc.DB2Driver
      protocol=jdbc
      sub-protocol=db2
      db-alias=//infosrvr.bootcamp.image.com:50000/xmeta
      user=xmeta
      password=*****
      eager-release=false
      ConnectionPoolDescriptor={whenExhaustedAction=0, maxIdle=-1, maxActive=21, maxWait=5000, removeAbandoned=false, numTestsPerEvictionRun=10, minEvictableIdleTimeMillis=600000, testWhileIdle=false, testOnReturn=false, logAbandoned=false, minIdle=0, fetchSize=0, removeAbandonedTimeout=300, timeBetweenEvictionRunsMillis=-1, testOnBorrow=true}
      batchMode=true
      useAutoCommit=AUTO_COMMIT_SET_FALSE
      ignoreAutoCommitExceptions=false
      sequenceDescriptor=<null>
    ]
            at org.apache.ojb.broker.accesslayer.ConnectionFactoryPooledImpl.checkOutJdbcConnection(Unknown Source)
            at org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl.lookupConnection(Unknown Source)
            at org.apache.ojb.broker.accesslayer.ConnectionManagerImpl.getConnection(Unknown Source)
            ... 84 more
    Caused by: 
    org.apache.ojb.broker.accesslayer.LookupException: Error getting Connection from DriverManager with url (jdbc:db2://infosrvr.bootcamp.image.com:50000/xmeta) and driver (com.ibm.db2.jcc.DB2Driver)
            at org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl.newConnectionFromDriverManager(Unknown Source)
            at org.apache.ojb.broker.accesslayer.ConnectionFactoryPooledImpl$ConPoolFactory.makeObject(Unknown Source)
            at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
            ... 87 more
    Caused by: 
    com.ibm.db2.jcc.am.oo: [jcc][t4][2043][11550][3.58.135] Exception java.net.ConnectException: Error opening socket to server infosrvr.bootcamp.image.com/127.0.0.2 on port 50,000 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001
            at com.ibm.db2.jcc.am.ed.a(ed.java:319)
            at com.ibm.db2.jcc.am.ed.a(ed.java:337)
            at com.ibm.db2.jcc.t4.zb.a(zb.java:400)
            at com.ibm.db2.jcc.t4.zb.<init>(zb.java:78)
            at com.ibm.db2.jcc.t4.a.y(a.java:309)
            at com.ibm.db2.jcc.t4.b.a(b.java:1806)
            at com.ibm.db2.jcc.am.jb.a(jb.java:578)
            at com.ibm.db2.jcc.am.jb.<init>(jb.java:529)
            at com.ibm.db2.jcc.t4.b.<init>(b.java:308)
            at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:214)
            at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:456)
            at java.sql.DriverManager.getConnection(DriverManager.java:322)
            at java.sql.DriverManager.getConnection(DriverManager.java:297)
            ... 90 more
    Caused by: 
    java.net.ConnectException: Connection refused
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:383)
            at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:245)
            at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:232)
            at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
            at java.net.Socket.connect(Socket.java:539)
            at com.ibm.db2.jcc.t4.ab.run(ab.java:34)
            at java.security.AccessController.doPrivileged(AccessController.java:251)
            at com.ibm.db2.jcc.t4.zb.a(zb.java:386)
            ... 100 more
    

    --

    --

    infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1 # tail -50 SystemOut.log 
            at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:109)
            at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:341)
            ... 33 more
    Caused by: com.ibm.websphere.security.WSSecurityException: Failed to get roles for user [server:infosrvrNode01Cell_infosrvrNode01_server1]: Unable to begin a transaction: [Error opening repository: []]
            at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjectInternal(ContextManagerImpl.java:2609)
            at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjectInternal(ContextManagerImpl.java:2254)
            at com.ibm.ws.security.auth.ContextManagerImpl.initialize(ContextManagerImpl.java:2891)
            ... 39 more
    Caused by: com.ibm.websphere.security.auth.WSLoginFailedException: Failed to get roles for user [server:infosrvrNode01Cell_infosrvrNode01_server1]: Unable to begin a transaction: [Error opening repository: []]
            at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:371)
            at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:395)
            at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3671)
            at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3541)
            at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjectInternal(ContextManagerImpl.java:2558)
            ... 41 more
    Caused by: javax.security.auth.login.FailedLoginException: Failed to get roles for user [server:infosrvrNode01Cell_infosrvrNode01_server1]: Unable to begin a transaction: [Error opening repository: []]
            at com.ascential.acs.security.auth.ISFAuthenticationProvider.commit(ISFAuthenticationProvider.java:318)
            at com.ibm.is.isf.j2ee.impl.was.security.WASCustomLoginModule.commit(WASCustomLoginModule.java:396)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
            at java.lang.reflect.Method.invoke(Method.java:611)
            at javax.security.auth.login.LoginContext.invoke(LoginContext.java:795)
            at javax.security.auth.login.LoginContext.access$000(LoginContext.java:209)
            at javax.security.auth.login.LoginContext$4.run(LoginContext.java:709)
            at java.security.AccessController.doPrivileged(AccessController.java:251)
            at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:706)
            at javax.security.auth.login.LoginContext.login(LoginContext.java:604)
            at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:354)
            ... 45 more
    Caused by: com.ascential.acs.security.repository.ASBRepositoryException: Unable to begin a transaction: [Error opening repository: []]
            at com.ascential.acs.security.repository.ASBRepositoryImpl.begin(ASBRepositoryImpl.java:158)
            at com.ascential.acs.security.directory.ASBDirectoryImpl.getRepository(ASBDirectoryImpl.java:88)
            at com.ascential.acs.security.directory.ASBDirectoryImpl.getUserRoles(ASBDirectoryImpl.java:315)
            at com.ascential.acs.security.directory.ASBDirectory.getUserRoles(ASBDirectory.java:146)
            at com.ascential.acs.security.auth.ISFAuthenticationProvider.commit(ISFAuthenticationProvider.java:309)
            ... 57 more
    Caused by: com.ascential.acs.security.repository.ASBRepositoryException: Error opening repository: []
            at com.ascential.acs.security.repository.ASBRepositoryImpl.getSandbox(ASBRepositoryImpl.java:701)
            at com.ascential.acs.security.repository.ASBRepositoryImpl.begin(ASBRepositoryImpl.java:156)
            ... 61 more
    
    [3/4/14 16:22:37:930 CST] 00000000 SchedulerServ I   SCHD0040I: The Scheduler Service is stopping.
    [3/4/14 16:22:38:005 CST] 00000000 SchedulerServ I   SCHD0002I: The Scheduler Service has stopped.
    [3/4/14 16:22:38:075 CST] 00000000 AppProfileCom I   ACIN0009I: The application profiling service is stopping.
    [3/4/14 16:22:38:147 CST] 00000000 ActivitySessi I   WACS0049I: The ActivitySession service is stopping.
    [3/4/14 16:22:38:213 CST] 00000000 ObjectPoolSer I   OBPL0011I: The Object Pool service is stopping.
    [3/4/14 16:22:38:331 CST] 00000000 distSecurityC I   securityServiceStarted is false
    [3/4/14 16:22:38:518 CST] 00000000 CGBridgeSubsc I   CWRCB0104I: The core group bridge service has stopped the subscription router.
    [3/4/14 16:22:38:591 CST] 00000000 CGBridgeServi I   CWRCB0103I: The core group bridge service has stopped.

    ---

    --

    infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1 # tail -100 startServer.log 
    [5/1/12 9:23:17:120 PDT] 00000000 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
    [5/1/12 9:23:17:718 PDT] 00000000 AdminTool     A   ADMU0128I: Starting tool with the InfoSphere profile
    [5/1/12 9:23:17:721 PDT] 00000000 AdminTool     A   ADMU3100I: Reading configuration for server: server1
    [5/1/12 9:23:18:449 PDT] 00000000 AdminTool     A   ADMU3200I: Server launched. Waiting for initialization status.
    [5/1/12 9:25:03:060 PDT] 00000000 AdminTool     A   ADMU3000I: Server server1 open for e-business; process id is 7673
    ************ Start Display Current Environment ************
    Host Operating System is Linux, version 2.6.32.12-0.7-pae
    Java version = JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
    J9VM - 20110216_075791
    JIT  - r9_20101028_17488ifx4
    GC   - 20101027_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = /opt/IBM/WebSphere/AppServer
    user.install.root = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere
    Java Home = /opt/IBM/WebSphere/AppServer/java/jre
    ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
    Classpath = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar
    Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/i386:/opt/IBM/WebSphere/AppServer/bin::/usr/lib
    Current trace specification = *=info
    ************* End Display Current Environment *************
    [3/3/14 11:38:55:871 CST] 00000000 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
    [3/3/14 11:38:56:380 CST] 00000000 AdminTool     A   ADMU0128I: Starting tool with the InfoSphere profile
    [3/3/14 11:38:56:393 CST] 00000000 AdminTool     A   ADMU3100I: Reading configuration for server: server1
    [3/3/14 11:38:57:579 CST] 00000000 AdminTool     A   ADMU3200I: Server launched. Waiting for initialization status.
    [3/3/14 11:41:30:374 CST] 00000000 AdminTool     A   ADMU3000I: Server server1 open for e-business; process id is 6575
    ************ Start Display Current Environment ************
    Host Operating System is Linux, version 2.6.32.12-0.7-pae
    Java version = JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
    J9VM - 20110216_075791
    JIT  - r9_20101028_17488ifx4
    GC   - 20101027_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = /opt/IBM/WebSphere/AppServer
    user.install.root = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere
    Java Home = /opt/IBM/WebSphere/AppServer/java/jre
    ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
    Classpath = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar
    Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/i386:/opt/IBM/WebSphere/AppServer/bin::/usr/lib
    Current trace specification = *=info
    ************* End Display Current Environment *************
    [3/3/14 15:32:11:681 CST] 00000000 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
    [3/3/14 15:32:12:120 CST] 00000000 AdminTool     A   ADMU0128I: Starting tool with the InfoSphere profile
    [3/3/14 15:32:12:127 CST] 00000000 AdminTool     A   ADMU3100I: Reading configuration for server: server1
    [3/3/14 15:32:13:601 CST] 00000000 AdminTool     A   ADMU3200I: Server launched. Waiting for initialization status.
    [3/3/14 15:34:18:689 CST] 00000000 AdminTool     A   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/InfoSphere/logs/server1 should contain failure information.
    ************ Start Display Current Environment ************
    Host Operating System is Linux, version 2.6.32.12-0.7-pae
    Java version = JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
    J9VM - 20110216_075791
    JIT  - r9_20101028_17488ifx4
    GC   - 20101027_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = /opt/IBM/WebSphere/AppServer
    user.install.root = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere
    Java Home = /opt/IBM/WebSphere/AppServer/java/jre
    ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
    Classpath = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar
    Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/i386:/opt/IBM/WebSphere/AppServer/bin::/usr/lib
    Current trace specification = *=info
    ************* End Display Current Environment *************
    [3/3/14 15:47:09:303 CST] 00000000 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
    [3/3/14 15:47:09:548 CST] 00000000 AdminTool     A   ADMU0128I: Starting tool with the InfoSphere profile
    [3/3/14 15:47:09:557 CST] 00000000 AdminTool     A   ADMU3100I: Reading configuration for server: server1
    [3/3/14 15:47:10:234 CST] 00000000 AdminTool     A   ADMU3200I: Server launched. Waiting for initialization status.
    [3/3/14 15:47:50:008 CST] 00000000 AdminTool     A   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/InfoSphere/logs/server1 should contain failure information.
    ************ Start Display Current Environment ************
    Host Operating System is Linux, version 2.6.32.12-0.7-pae
    Java version = JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
    J9VM - 20110216_075791
    JIT  - r9_20101028_17488ifx4
    GC   - 20101027_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = /opt/IBM/WebSphere/AppServer
    user.install.root = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere
    Java Home = /opt/IBM/WebSphere/AppServer/java/jre
    ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
    Classpath = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar
    Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/i386:/opt/IBM/WebSphere/AppServer/bin::/usr/lib
    Current trace specification = *=info
    ************* End Display Current Environment *************
    [3/4/14 16:14:38:413 CST] 00000000 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
    [3/4/14 16:14:38:771 CST] 00000000 AdminTool     A   ADMU0128I: Starting tool with the InfoSphere profile
    [3/4/14 16:14:38:782 CST] 00000000 AdminTool     A   ADMU3100I: Reading configuration for server: server1
    [3/4/14 16:14:39:593 CST] 00000000 AdminTool     A   ADMU3200I: Server launched. Waiting for initialization status.
    [3/4/14 16:15:43:331 CST] 00000000 AdminTool     A   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/InfoSphere/logs/server1 should contain failure information.
    ************ Start Display Current Environment ************
    Host Operating System is Linux, version 2.6.32.12-0.7-pae
    Java version = JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
    J9VM - 20110216_075791
    JIT  - r9_20101028_17488ifx4
    GC   - 20101027_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = /opt/IBM/WebSphere/AppServer
    user.install.root = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere
    Java Home = /opt/IBM/WebSphere/AppServer/java/jre
    ws.ext.dirs = /opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
    Classpath = /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar
    Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/i386:/opt/IBM/WebSphere/AppServer/bin::/usr/lib
    Current trace specification = *=info
    ************* End Display Current Environment *************
    [3/4/14 16:21:47:087 CST] 00000000 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
    [3/4/14 16:21:47:380 CST] 00000000 AdminTool     A   ADMU0128I: Starting tool with the InfoSphere profile
    [3/4/14 16:21:47:392 CST] 00000000 AdminTool     A   ADMU3100I: Reading configuration for server: server1
    [3/4/14 16:21:48:019 CST] 00000000 AdminTool     A   ADMU3200I: Server launched. Waiting for initialization status.
    [3/4/14 16:22:43:337 CST] 00000000 AdminTool     A   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/InfoSphere/logs/server1 should contain failure information.
    
    以上为三个日志文件的打印。以为是hosts文件错误,我在之前改过hostname,在最后一行刚增加一条语句,如下:
    Infosrvr:~ # more /etc/hosts
    #
    # hosts         This file describes a number of hostname-to-address
    #               mappings for the TCP/IP subsystem.  It is mostly
    #               used at boot time, when no name servers are running.
    #               On small systems, this file can be used instead of a
    #               "named" name server.
    # Syntax:
    #    
    # IP-Address  Full-Qualified-Hostname  Short-Hostname
    #
    
    127.0.0.1       localhost
    
    # special IPv6 addresses
    ::1             localhost ipv6-localhost ipv6-loopback
    
    fe00::0         ipv6-localnet
    
    ff00::0         ipv6-mcastprefix
    ff02::1         ipv6-allnodes
    ff02::2         ipv6-allrouters
    ff02::3         ipv6-allhosts
    127.0.0.2       infosrvr.bootcamp.image.com infosrvr
    192.168.26.10   infosrvr.bootcamp.image.com infosrvr
    10.13.2.223     infosrvr.wenchao.com infosrvr
    10.13.2.146     infosrvr.bootcamp.image.com infosrvr
    infosrvr:~ # 





    --
    重启还是报一样错。
    Google找到一篇文章:
    http://www-01.ibm.com/support/docview.wss?uid=swg21578246
    https://www-304.ibm.com/support/docview.wss?uid=swg21403644
    说是
    This technote specifically relates to the scenario where the cause is that the DB2 server is configured to not allow TCP/IP connections
    /
    A possible cause for this problem is that TCP/IP may not be properly enabled on your DB2 database server.
    解决步骤:
    db2set -all                 ---查看连接模式
    db2set DB2COMM=tcpip    --修改连接模式
    db2stop                 --重启代表db2   
    db2start


    老外给的步骤:
    On a badly configured DB2 server there will not be an entry "TCPIP" (next to "DB2COMM"). For example:
    DB2COMM=NETBIOS
    On a good DB2 server, there will be an entry similar to:
    DB2COMM=TCPIP
    Resolving the problem
    Reconfigure the DB2 server to allow TCP/IP connections.
    Steps:

    1. Logon to the DB2 server as an administrator
    2. Obtain a short period of downtime (no users using the DB2 database(s))
    3. Launch a command promopt, and run a command similar to the following (ask DB2 administrator if need more protocols than just TCPIP): db2set DB2COMM=TCPIP
    4. Restart DB2 server (for settings to take effect).




    步骤:
    infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1 # su db2inst1
    db2inst1@infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1> db2set DB2comm=tcpip
    db2inst1@infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1> db2stop
    SQL1064N  DB2STOP processing was successful.
    db2inst1@infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1> db2start
    SQL1063N  DB2START processing was successful.
    db2inst1@infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1> exit
    exit
    infosrvr:/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1 # /opt/IBM/WebSphere/AppServer/bin/startServer.sh server1
    ADMU0116I: Tool information is being logged in file
               /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1/startServer.log
    ADMU0128I: Starting tool with the InfoSphere profile
    ADMU3100I: Reading configuration for server: server1
    ADMU3200I: Server launched. Waiting for initialization status.
    ADMU3000I: Server server1 open for e-business; process id is 10262



    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    展开全文
  • 问题如下: 解决办法: 再次重启服务器就能解决这个问题。 转载于:https://www.cnblogs.com/TTTTT/p/6675452.html

    问题如下:

    解决办法:

    再次重启服务器就能解决这个问题。

     

    转载于:https://www.cnblogs.com/TTTTT/p/6675452.html

    展开全文
  • RedHat 6.4 安装 WAS 7.0,安装完成之后启动WAS失败,异常信息如下: [5/7/15 9:59:55:185 CST] 00000000 WsServerImpl E WSVR0100W: An error occurred initializing, server1 [class ...

    问题描述

    RedHat 6.4 安装 WAS 7.0,安装完成之后启动WAS失败,异常信息如下:

    [5/7/15 9:59:55:185 CST] 00000000 WsServerImpl  E   WSVR0100W: An error occurred initializing, server1 [class com.ibm.ws.runtime.component.ServerImpl]
    com.ibm.ws.exception.ConfigurationError: com.ibm.websphere.ssl.SSLException: com.ibm.websphere.ssl.SSLException: SPJYXZXKSDXT-APP-01: SPJYXZXKSDXT-APP-01
        at com.ibm.ws.ssl.core.SSLComponentImpl.initialize(SSLComponentImpl.java:208)
        at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1166)
        at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1073)
        at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:874)
        at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:780)
        at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:754)
        at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:350)
        at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:280)
        at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
        at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
        at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:599)
        at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
        at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
        at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:599)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
        at org.eclipse.core.launcher.Main.run(Main.java:981)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108)
    Caused by: com.ibm.websphere.ssl.SSLException: com.ibm.websphere.ssl.SSLException: SPJYXZXKSDXT-APP-01: SPJYXZXKSDXT-APP-01
        at com.ibm.ws.ssl.config.SSLConfigManager.initializeServerSSL(SSLConfigManager.java:322)
        at com.ibm.ws.ssl.core.SSLComponentImpl.initialize(SSLComponentImpl.java:145)
        ... 31 more
    Caused by: com.ibm.websphere.ssl.SSLException: SPJYXZXKSDXT-APP-01: SPJYXZXKSDXT-APP-01
        at com.ibm.ws.ssl.config.KeyStoreManager.checkIfKeyStoreExistsAndCreateIfNot(KeyStoreManager.java:1592)
        at com.ibm.ws.ssl.config.SSLConfigManager.parseSecureSocketLayer1(SSLConfigManager.java:1131)
        at com.ibm.ws.ssl.config.SSLConfigManager.parseSSLConfig(SSLConfigManager.java:667)
        at com.ibm.ws.ssl.config.SSLConfigManager.initializeServerSSL(SSLConfigManager.java:234)
        ... 32 more
    Caused by: java.net.UnknownHostException: SPJYXZXKSDXT-APP-01: SPJYXZXKSDXT-APP-01
        at java.net.InetAddress.getLocalHost(InetAddress.java:1380)
        at com.ibm.ws.ssl.config.CertificateManager.chainedCertificateCreate(CertificateManager.java:341)
        at com.ibm.ws.ssl.config.KeyStoreManager.checkIfKeyStoreExistsAndCreateIfNot(KeyStoreManager.java:1580)
        ... 35 more
    

    解决办法

    修改/ect/hosts文件,示例修改如下:

    127.0.0.1       localhost localhost.localdomain localhost4 localhost4.localdomain4 SPJYXZXKSDXT-APP-01.site SPJYXZXKSDXT-APP-01
    10.100.12.11    localhost localhost.localdomain localhost6 localhost6.localdomain6 SPJYXZXKSDXT-APP-01 SPJYXZXKSDXT-APP-01

    修改完之后,重新启动Linux再试就可以了

    参考资料

    http://m.blog.csdn.net/blog/yuyunliu/9380799

    http://www.cnblogs.com/hanxianlong/p/3379699.html

    展开全文
  • 项目采用一个文件夹的方式发布,内部结果和一个WAR包类似,操作系统为WIN2008 R2,weblogic版本为10.3.3,在AdminServer下部署成功,并启动成功,但部署在managerserver下,能部署但启动失败,提示如下weblogic....
  • 今天测试springMVC restful风格,我使用的是idea 一开始是java7+tomcat7正常启动...提示信息:Application Server was not connected before run configuration stop, reason: Unable to ping server at localhost:1099
  • Starting WebLogic Server with OpenJDK 64-Bit Server VM Version 25.222-b10 from >  <2021-1-18 下午03时56分24秒 CST> <Info> <Management> <BEA-141107> <Version: ...
  • 克隆或者安装好系统后,发现form打不开,报错截图:根据oracle 官方文档:R12: "FRM-92101:There was a failure in the Forms Server during startup" Error When Attempting to Launch Forms [ID 454427.1]Oracle ...
  • 2.打开Timeouts,设置启动时间为100,目的是让服务器有更多的时间去启动项目,因为服务器下,过多的项目很导致在短时间内无法读取项目的配置,所以项目部署失败 3.重启服务器,应该就可以了 转载于:...
  • 第一次配置成功,但是由于http server 控制服务密码输入错误,导致IBMHTTPAdministrationforWebSphereApplicationServerV8.5_50无法启动,于是删除插件配置重新配置,但是就出现配置失败的问题。 经反
  • 在CentOS7x64 7.3.1611上测试部署Zabbix3.0.9,到启动zabbix-server服务时报错:  [root@CentOS7x64 ~]# systemctl restart zabbix-server  Job for zabbix-server.service failed because a configured ...
  • Failed to retrieve JNDI naming context for container [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/hr01]] so no cleanup was performed for that container javax.naming.NamingExcepti...
  • 错误日志: ...2013-05-26 11:14:24.56 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. 求高手解惑!
  • 启动zabbix-server服务时报错: [root@CentOS7x64 ~]# systemctl restart zabbix-server Job for zabbix-server.service failed because a configured resource limit was exceede...
  • Tomcat 启动失败

    2019-09-29 19:23:32
    在web环境下,tomcat整合socket,使用 init()初始化socket服务。...Tomcat v9.0 Server at localhost was unable to start within 45 seconds. If the server requires more time, try increasing the timeout ...
  • 启动hbase时出现: Java HotSpot™ 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support ...
  • RocketMQ启动失败问题

    2020-11-22 22:54:45
    Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Unrecognized VM option 'UseCMSCompactAtFullCollection...
  • entos7.3配置mysql5.6无法启动和重启报错:Job for mysqld.service failed because a timeout was exceeded.尝试用root登录MySQL是报错ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ...
  • entos7.3配置mysql5.6无法启动和重启报错:Job for mysqld.service failed because a timeout was exceeded.尝试用root登录MySQL是报错ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ...
  • 1、使用root用户启动失败: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. [2019-12-11T15:45:07,664][WARN ][o...
  • @[TOC]记录webstorm启动失败的问题 ~ 在某个工作日,突然发现webstorm打不开了,怎么点都没有反应,鼠标也是快速...OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and w
  • Eclipse Photon启动Tomcat9失败

    千次阅读 2018-06-30 23:03:35
    Eclipse Oxygen升级到Photon启动Tomcat失败,提示Plug-in "org.eclipse.jst.server.tomcat.core" was unable to instantiate class。。。开始的时候,还以为是Tomcat版本过低,我之前用的是Tomcat9.0.1,...
  • Tomcat Server启动超时的解决

    千次阅读 2012-10-24 15:45:27
    Tomcat Server启动超过45S而导致失败的会提示如下错误。 Server Tomcat v5.5 Server at localhost was unable to start within 45 seconds. If the server requires more time, try increasing the timeout in ...
  • from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make ...
  • 列出启动失败的服务 [root@localhost ~]# systemctl list-units --state failed UNIT LOAD ACTIVE SUB DESCRIPTION ● httpd.service loaded failed failed The Apache HTTP Server LOAD = Reflects whether the ...
  • 错误:Server Tomcat vX.0 Server at localhost was unable to start within 45 seconds 表示:服务器启动时间不能超过45秒,否则视为启动失败。 在需要的情况下,服务器的启动时间超过45秒则需要通过修改配置来...

空空如也

空空如也

1 2 3 4 5 ... 7
收藏数 125
精华内容 50
关键字:

was启动server失败