aspose file tools*
The moose likes Websphere and the fly likes IBM WAS8.5 - ClassNotFoundException error occurs Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "IBM WAS8.5 - ClassNotFoundException error occurs" Watch "IBM WAS8.5 - ClassNotFoundException error occurs" New topic
Author

IBM WAS8.5 - ClassNotFoundException error occurs

Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 14
Hi,

I have an EAR which runs fine on WAS7. I have upgraded my WAS to 8.5 and during server start-up I am getting the below logs. These are classNotFound for the apache logger class. As per the IBM post
("http://www-01.ibm.com/support/docview.wss?uid=swg1PM21839") this issue was in WAS7 and they added the fix in the fix pack. So, I assume that this should be included in the latest WAS version. But unfortunately this is occuring during server start-up.

Per them, this is due to "When a JAX-WS Web service application includes the Jakarta Commons Logging classes within their application or classpath, a ClassNotFoundException may occur."
I tried removing my commons-logging.jar from a runtime folder in my application but still getting errors and moreover my WAS Admin console does not open because of this.

The client has reported this issue and we need to get rid of it. So, seeking for help..!!

[6/5/14 14:07:11:298 IST] 00000001 ModelMgr I WSVR0800I: Initializing core configuration models
[6/5/14 14:07:12:539 IST] 00000001 ComponentMeta I WSVR0179I: The runtime provisioning feature is disabled. All components will be started.
[6/5/14 14:07:12:838 IST] 00000001 ProviderTrack I com.ibm.ffdc.osgi.ProviderTracker AddingService FFDC1007I: FFDC Provider Installed: com.ibm.ws.ffdc.impl.FfdcProvider@c7c0d838
[6/5/14 14:07:13:196 IST] 00000001 AdminInitiali A ADMN0015I: The administration service is initialized.
[6/5/14 14:07:14:578 IST] 00000001 PluginConfigS I PLGC0057I: The plug-in configuration service started successfully.
[6/5/14 14:07:14:778 IST] 00000001 SSLComponentI I CWPKI0001I: SSL service is initializing the configuration
[6/5/14 14:07:14:793 IST] 00000001 FIPSManager I CWPKI0044I: FIPS security mode is : No FIPS property found.
[6/5/14 14:07:14:796 IST] 00000001 WSKeyStore W CWPKI0041W: One or more key stores are using the default password.
[6/5/14 14:07:14:818 IST] 00000001 SSLConfigMana I CWPKI0027I: Disabling default hostname verification for HTTPS URL connections.
[6/5/14 14:07:14:833 IST] 00000001 SSLDiagnostic I CWPKI0014I: The SSL component's FFDC Diagnostic Module com.ibm.ws.ssl.core.SSLDiagnosticModule registered successfully: true.
[6/5/14 14:07:14:837 IST] 00000001 SSLComponentI I CWPKI0002I: SSL service initialization completed successfully
[6/5/14 14:07:14:846 IST] 00000001 DiagnosticCon I com.ibm.wsspi.rasdiag.DiagnosticConfigHome setStateCollectionSpec RASD0012I: Updating State Collection Spec from Uninitialized Value to .*:.*=0
[6/5/14 14:07:14:851 IST] 00000001 PMIImpl A CWPMI1001I: PMI is enabled
[6/5/14 14:07:15:683 IST] 00000001 GAPAgentCompo I CWLRS6000I: GAP (Grid Application Placement) Component has initialized successfully on process UnManagedProcess.
[6/5/14 14:07:15:780 IST] 00000001 SibMessage I [:] CWSIU0000I: Release: WAS85.SIB Level: cf011240.02
[6/5/14 14:07:15:923 IST] 00000001 SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[6/5/14 14:07:16:048 IST] 00000001 distSecurityC I SECJ6004I: Security Auditing is disabled.
[6/5/14 14:07:16:053 IST] 00000001 distSecurityC I SECJ0309I: Java 2 Security is disabled.
[6/5/14 14:07:16:059 IST] 00000001 Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[6/5/14 14:07:16:087 IST] 00000001 distSecurityC I SECJ0240I: Security service initialization completed successfully
[6/5/14 14:07:16:864 IST] 00000001 JAASLoginConf I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[6/5/14 14:07:16:893 IST] 00000001 J2EEServiceMa I ASYN0059I: Work Manager service initialized successfully.
[6/5/14 14:07:17:049 IST] 00000001 CScopeCompone I CSCP0002I: Compensation service is disabled.
[6/5/14 14:07:17:158 IST] 00000001 SibMessage I [:] CWSID0006I: The SIB service was not enabled and will not be started.
[6/5/14 14:07:17:166 IST] 00000001 ActivitySessi I WACS0045I: ActivitySession service is disabled.
[6/5/14 14:07:17:175 IST] 00000001 AppProfileCom I ACIN0030I: Application Profiling service is disabled.
[6/5/14 14:07:17:202 IST] 00000001 SOAPContainer I WSWS1062I: The SOAP Container service has been initialized.
[6/5/14 14:07:17:424 IST] 00000001 FFDCJanitor I com.ibm.ws.ffdc.impl.FFDCJanitor doCleanupIfNeeded FFDCJANITOR_DELETED_FILES
[6/5/14 14:07:17:436 IST] 00000001 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv03\logs\ffdc\server1_5ec7328e_14.06.05_14.07.17.4271822329839264253804.txt null 1011
[6/5/14 14:07:17:437 IST] 00000001 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.websvcs.component.WASAxis2ComponentImpl
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:250)
at com.ibm.ws.websvcs.component.WASAxis2ComponentImpl.initialize(WASAxis2ComponentImpl.java:390)
at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1192)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1099)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:901)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750)
at com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(ApplicationServerImpl.java:192)
at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1192)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1099)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:928)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:333)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:336)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:267)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:730)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
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 com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
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.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:379)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:150)
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4JLogger
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:429)
at java.security.AccessController.doPrivileged(AccessController.java:280)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:420)
at org.apache.axis2.jaxws.registry.FactoryRegistry.<clinit>(FactoryRegistry.java:93)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:228)
... 43 more
Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4JLogger
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
... 51 more
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4JLogger
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:136)
at org.apache.commons.logging.impl.LogFactoryImpl$1.run(LogFactoryImpl.java:466)
at java.security.AccessController.doPrivileged(AccessController.java:229)
at org.apache.commons.logging.impl.LogFactoryImpl.loadClass(LogFactoryImpl.java:454)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:406)
... 52 more

[6/5/14 14:07:17:616 IST] 00000001 SchedulerServ I SCHD0036I: The Scheduler Service is initializing.

[6/5/14 14:07:17:629 IST] 00000001 SchedulerServ I SCHD0037I: The Scheduler Service has been initialized.
[6/5/14 14:07:17:638 IST] 00000001 JPAComponentI I CWWJP0026I: The Java Persistence API (JPA) component is initializing.
[6/5/14 14:07:17:673 IST] 00000001 AbstractJPACo I CWWJP0006I: The com.ibm.websphere.persistence.PersistenceProviderImpl class is loaded as the default Java Persistence API (JPA) provider.
[6/5/14 14:07:17:674 IST] 00000001 JPAComponentI I CWWJP0027I: The Java Persistence API (JPA) component has initialized.
[6/5/14 14:07:18:332 IST] 00000001 ApplicationRe I ApplicationRepositoryFactory CWSCT0405I: The application router is configured to select applications by the weight.
[6/5/14 14:07:18:339 IST] 00000001 ApplicationRe I ApplicationRepositoryFactory CWSCT0415I: Loading default application router, weight strategy.
[6/5/14 14:07:18:339 IST] 00000001 DefaultApplic I DefaultApplicationRouter CWSCT0401I: Default application router has been initialized.
[6/5/14 14:07:18:357 IST] 00000001 WebsphereComm I WebsphereCommonLauncher CWSCT0332I: SIP Container was launched successfully but will only be initialized when first SIP application is loaded.
[6/5/14 14:07:18:982 IST] 00000001 StartUpServic I STUP0008I: The Startup Beans service is disabled.
[6/5/14 14:07:18:996 IST] 00000001 I18nService I I18N0010I: The Internationalization service is created on server1.
[6/5/14 14:07:18:999 IST] 00000001 I18nServiceSe I I18N0010I: The Internationalization service is disabled on server1.
[6/5/14 14:07:19:310 IST] 00000001 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv03\logs\ffdc\server1_5ec7328e_14.06.05_14.07.19.3069049515367707445261.txt null 789
[6/5/14 14:07:19:378 IST] 00000001 GridConfigura I GridConfigurator initialized successfully
[6/5/14 14:07:19:383 IST] 00000001 GridDBConfigu I GridDBConfigurator initialized successfully.
[6/5/14 14:07:19:386 IST] 00000001 BatchSensorCo I BatchSensorComponent initializing.
[6/5/14 14:07:19:392 IST] 00000001 BatchSensorCo I BatchSensorComponent initialized successfully.
[6/5/14 14:07:19:475 IST] 00000001 WsServerImpl W WSVR0100W: An error occurred initializing, server1 [class com.ibm.ws.runtime.component.ServerImpl]
com.ibm.ws.exception.ConfigurationWarning: Exception caught when initializing component
at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1237)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1099)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:901)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750)
at com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(ApplicationServerImpl.java:192)
at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1192)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1099)
at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:928)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:333)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:336)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:267)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:730)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
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 com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
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.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:379)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:150)
Caused by: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:250)
at com.ibm.ws.websvcs.component.WASAxis2ComponentImpl.initialize(WASAxis2ComponentImpl.java:390)
at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1192)
... 41 more
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4JLogger
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:429)
at java.security.AccessController.doPrivileged(AccessController.java:280)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:420)
at org.apache.axis2.jaxws.registry.FactoryRegistry.<clinit>(FactoryRegistry.java:93)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:228)
... 43 more
Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4JLogger
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
... 51 more
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4JLogger
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:136)
at org.apache.commons.logging.impl.LogFactoryImpl$1.run(LogFactoryImpl.java:466)
at java.security.AccessController.doPrivileged(AccessController.java:229)
at org.apache.commons.logging.impl.LogFactoryImpl.loadClass(LogFactoryImpl.java:454)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:406)
... 52 more

[6/5/14 14:07:19:516 IST] 00000001 ThreadPoolMgr W WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.
[6/5/14 14:07:19:540 IST] 00000001 SSLComponentI I CWPKI0003I: SSL service is starting
[6/5/14 14:07:19:560 IST] 00000001 SSLComponentI I CWPKI0004I: SSL service started successfully
[6/5/14 14:07:21:037 IST] 00000001 CoordinatorIm I HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup. The active coordinator set is [CSCINDAE744036Node01Cell\CSCINDAE744036Node01\server1].
[6/5/14 14:07:21:106 IST] 00000001 DCSPluginSing I HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup.
[6/5/14 14:07:21:166 IST] 00000001 DragDropDeplo I CWLDD0103I: Monitored directory application deployment service has been configured to be off.
[6/5/14 14:07:21:301 IST] 00000001 NameServerImp A NMSV0018I: Name server available on bootstrap port 2809.
[6/5/14 14:07:21:324 IST] 00000001 CGBridgeSubsc I CWRCB0102I: The core group bridge service has started the subscription router.
[6/5/14 14:07:21:594 IST] 00000001 JMSRegistrati A WMSG1611I: The installed level of the WebSphere MQ messaging provider is 7.1.0.1.
[6/5/14 14:07:21:599 IST] 00000001 JMSRegistrati I WMSG1703I: RAR implementation version 7.1.0.1-k710-001-120424
[6/5/14 14:07:21:658 IST] 00000001 ObjectPoolSer I OBPL0010I: The Object Pool service started successfully.
[6/5/14 14:07:22:382 IST] 00000001 JMXSoapAdapte A ADMC0013I: The SOAP connector is available at port 8880
[6/5/14 14:07:22:598 IST] 00000001 TCPChannel I TCPC0001I: TCP Channel TCPInboundChannel_ipcc.Default_IPC_Connector_Name is listening on host 127.0.0.1 (IPv4: 127.0.0.1) port 9633.
[6/5/14 14:07:22:601 IST] 00000001 WSChannelFram A CHFW0019I: The Transport Channel Service has started chain IPCCInboundChain.Default_IPC_Connector_Name.
[6/5/14 14:07:22:602 IST] 00000001 IPCConnectorS I ADMC0070I: The IPC connector is available at port 9633
[6/5/14 14:07:22:612 IST] 00000001 distSecurityC I securityServiceStarted is true
[6/5/14 14:07:22:613 IST] 00000001 distSecurityC I SECJ0243I: Security service started successfully
[6/5/14 14:07:22:614 IST] 00000001 distSecurityC I SECJ0210I: Security enabled false
[6/5/14 14:07:22:646 IST] 00000001 J2EEServiceMa I ASYN0055I: The Work Manager service started successfully.
[6/5/14 14:07:22:828 IST] 00000001 RecoveryDirec I CWRLS0010I: Performing recovery processing for local WebSphere server (CSCINDAE744036Node01Cell\CSCINDAE744036Node01\server1).
[6/5/14 14:07:22:847 IST] 00000001 RecoveryDirec I CWRLS0012I: All persistent services have been directed to perform recovery processing for this WebSphere server (CSCINDAE744036Node01Cell\CSCINDAE744036Node01\server1).
[6/5/14 14:07:22:940 IST] 00000038 RecoveryManag A WTRN0132I: Transaction recovery for CSCINDAE744036Node01Cell\CSCINDAE744036Node01\server1 initiated with server uuid 7a32306d095fb4f0c028e25cc6a4cea401913042 and restart epoch 0
[6/5/14 14:07:22:945 IST] 00000038 RecoveryManag I WTRN0135I: Transaction service recovering no transactions.
[6/5/14 14:07:22:948 IST] 00000038 RecoveryManag A WTRN0134I: Recovering 0 XA resource manager(s) from the transaction partner logs
[6/5/14 14:07:22:983 IST] 00000038 RecoveryManag A WTRN0133I: Transaction recovery processing for this server is complete
[6/5/14 14:07:23:332 IST] 00000001 ResourceMgrIm I WSVR0049I: Binding AsyncRequestDispatcherWorkManager as wm/ard
[6/5/14 14:07:23:411 IST] 00000001 ResourceMgrIm I WSVR0049I: Binding DefaultEJBTimerDataSource as jdbc/DefaultEJBTimerDataSource
[6/5/14 14:07:23:433 IST] 00000001 ResourceMgrIm I WSVR0049I: Binding Default_CF as eis/DefaultDatasource_CMP
[6/5/14 14:07:23:449 IST] 00000001 ResourceMgrIm I WSVR0049I: Binding Default Datasource as DefaultDatasource
[6/5/14 14:07:23:464 IST] 00000001 ResourceMgrIm I WSVR0049I: Binding DefaultWorkManager as wm/default
[6/5/14 14:07:23:469 IST] 00000001 ResourceMgrIm I WSVR0049I: Binding DefaultTimerManager as tm/default
[6/5/14 14:07:23:525 IST] 00000001 WorkAreaServi A ACWA0002I: WorkArea service not enabled on server1.
[6/5/14 14:07:23:553 IST] 00000001 SOAPAcceptorC I WSSC1019I: The SOAP Acceptor Channel has been configured.
[6/5/14 14:07:23:615 IST] 00000001 CacheServiceI I DYNA1054I: Dynamic Cache (core cache) initialized successfully.
[6/5/14 14:07:23:628 IST] 00000001 ObjectCacheSe I DYNA1056I: Dynamic Cache (object cache) initialized successfully.
[6/5/14 14:07:24:405 IST] 00000001 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv03\logs\ffdc\server1_5ec7328e_14.06.05_14.07.24.4034978276067867068181.txt null 484
[6/5/14 14:07:24:406 IST] 00000001 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.wsaddressing.jaxws.component.WSAddressingComponentImpl@ec8ef009
java.lang.NoClassDefFoundError: org.apache.axis2.jaxws.registry.FactoryRegistry (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:168)
at com.ibm.ws.wsaddressing.jaxws.urimap.EndpointMappingListener.initialize(EndpointMappingListener.java:191)
at com.ibm.ws.wsaddressing.jaxws.urimap.EndpointMappingListener.<init>(EndpointMappingListener.java:118)
at com.ibm.ws.wsaddressing.jaxws.component.WSAddressingComponentImpl.start(WSAddressingComponentImpl.java:140)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:539)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:252)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:539)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:503)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:354)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:267)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:730)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
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 com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
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.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:379)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:150)

[6/5/14 14:07:24:485 IST] 00000001 SchedulerServ I SCHD0031I: The Scheduler Service is starting.
[6/5/14 14:07:24:504 IST] 00000001 SchedulerServ I SCHD0001I: The Scheduler Service has started.
[6/5/14 14:07:24:506 IST] 00000001 JPAComponentI I CWWJP0028I: The Java Persistence API (JPA) component is starting.
[6/5/14 14:07:24:542 IST] 00000001 JPAComponentI I CWWJP0017I: The Java Persistence API (JPA) component has started.
[6/5/14 14:07:24:678 IST] 00000001 ServerCache I DYNA1001I: WebSphere Dynamic Cache instance named ws/com.ibm.ws.wssecurity.sctClientCacheMap initialized successfully.
[6/5/14 14:07:24:679 IST] 00000001 ServerCache I DYNA1071I: The cache provider "default" is being used.
[6/5/14 14:07:24:690 IST] 00000001 ServerCache I DYNA1001I: WebSphere Dynamic Cache instance named ws/com.ibm.ws.wssecurity.sctServiceCacheMap initialized successfully.
[6/5/14 14:07:24:691 IST] 00000001 ServerCache I DYNA1071I: The cache provider "default" is being used.
[6/5/14 14:07:24:834 IST] 00000001 RegistryConfi I CWXRS0017I: Extension Registry objects storage: C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv03\temp\CSCINDAE744036Node01\server1\_extensionregistry
[6/5/14 14:07:24:944 IST] 00000001 ServerCache I DYNA1001I: WebSphere Dynamic Cache instance named ws/com.ibm.workplace/ExtensionRegistryCache initialized successfully.
[6/5/14 14:07:24:945 IST] 00000001 ServerCache I DYNA1071I: The cache provider "default" is being used.
Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 493
    
    1

Anand Bansal wrote:
I tried removing my commons-logging.jar from a runtime folder in my application but still getting errors and moreover my WAS Admin console does not open because of this.


They seems to be two unrelated problems. Which is the runtime folder from which you deleted jars ? Hopefully it would be something in your application, not at WebSphere runtime level...
Can't you avoid to use Apache Logger class, by editing your code ? Use instead some Logger provided by websphere....

Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 14
Thanks for your reply.

The runtime folder is one of my project folder. It has a commons-logging.jar. Let me clarify one thing... There is just one issue.
Issue 1) Logging issue coming while starting was 8.5 with my EAR, which runs fine on WAS 6.5. Even if do no add my EAR, the server start-up shows the same log. I read in the IBM post that if I am using a external logging class, othen than the JAX-WS, it may give me a class not found exception - and this is what I am getting.

The issue related to the admin console is just a side effect of removing this apache commons logging from my project runtime folder. We need to look into the original issue (above).
Please let me know if you need any other information.
Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 493
    
    1

Mmm, honestly that's sound strange. First, admin console is a separated ear (or war, don't remember), so why would it be affected from classes put in your ear? Anyway, let's go on. When you say that you deleted commons logging jar from your application, I would assume that you manually deleted jars from somewhere in profile/installed apps etc. Ok, that may not be enough, try and delete your application via wsadmin (it's far less usable than console, at least for my taste,but web console isn't accessible). This said, i think you have two paths to follow : open a PMR, or try to solve your issue refactoring the code without include commons logging.
But, first, remove your app and restart your server.
Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 14
Thanks Claude.

I restarted my server after removing the application but it is still giving me the same issue.

Lets forget the admin-console-not-opening issue for the moment. I was also surprised why it got affected.

The main issue is logging issue in JAX-WS logger issue. I had removed the external loggings jat from a project folder and it is being referred in some other projects.

This runtime project is included in the IBM Websphere - Process Definition -> JVM Custom properties.
Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 493
    
    1

Anand Bansal wrote:

The main issue is logging issue in JAX-WS logger issue. I had removed the external loggings jat from a project folder and it is being referred in some other projects.

This runtime project is included in the IBM Websphere - Process Definition -> JVM Custom properties.


This way, your jars are loaded at root level, so that they may affect all Java EE.. admin console included.
Edit:just realized i told you a nonsense, by jvm custom properties you cannot deploy nothing so: what exactly is that "runtime project"?
How do you deploy it?
Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 14
Runtime is just another project which has the jars of various projects in it. The path of this project is included in the Custom properties (ws.ext.dirs).

We need to somehow let the websphere know that you need to pick the internal JAX-WS internal logging and not the external jar specified in the runtime project.

The issue is that the JAX-WS internal logging jars (package) is not picked and hence it gives class not found exception for the logging purpose.

I may need -
a) either the solution to the root cause - some way of loading JAX-WS logging before loading external logging (GOOD)

b) suppress this logging error by lowering the verbosity of the class giving the error in console (BAD)
Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 493
    
    1

Anand Bansal wrote:
We need to somehow let the websphere know that you need to pick the internal JAX-WS internal logging and not the external jar specified in the runtime project.


I don't remember exactly but if you put a jar in ws.ext.dirs, those jars are loaded by WebSphere runtime so I don't think you'll be able to prevent WebSphere to load them. If you have source control over this runtime project, you
may try to remove problematic logging jars and substitute them with standard logging utilities provided by WAS runtime. Otherwise, no matter when this project is loaded, I'm afraid you'll always get the ClassLoader problem you
described above.
Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 14
I agree, these are JVM generated logs and would not be resolved as easily. I found a way to suppress the apache logger logs in the console. I guess that would do the work for me.

Thanks Claude for the much help.
Anand Bansal
Greenhorn

Joined: Oct 15, 2012
Posts: 14
I agree, these are JVM generated logs and would not be resolved as easily. I found a way to suppress the apache logger logs in the console. I guess that would do the work for me.

Thanks Claude for the much help.
Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 493
    
    1

Glad i helped you, even if i think you found the solution by your own efforts. In theory, i think that when there's a classloader issue it should manifest as soon as classes are loaded,so i would not bet suppressing logging may be enough.. but practice is often another story so i 'll keep my fingers crossed for you.
Regards,
Claude
 
Consider Paul's rocket mass heater.
 
subject: IBM WAS8.5 - ClassNotFoundException error occurs