Websphere Liberty profile AdminCenter page not loading - solaris
I have downloaded the latest stable WLP runtime with JAVA EE7 for solaris environment.
Version : 16.0.0.3
The zip file is extracted and profile is created. AdminCenter installed by using below command:
.\installUtility install adminCenter-1.0
Server.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<server description="server1">
<!-- Enable features -->
<quickStartSecurity userName="admin" userPassword="adminpwd" />
<featureManager>
<feature>jsp-2.3</feature>
<feature>servlet-3.1</feature>
<feature>ssl-1.0</feature>
<feature>jndi-1.0</feature>
<feature>json-1.0</feature>
<feature>adminCenter-1.0</feature>
<feature>distributedMap-1.0</feature>
<feature>appSecurity-2.0</feature>
<feature>jaxrs-2.0</feature>
<feature>restConnector-1.0</feature>
<feature>jaxrsClient-2.0</feature>
</featureManager>
<keyStore id="defaultKeyStore" password="{xor}PjsyNjEfbm1s" />
<httpEndpoint id="defaultHttpEndpoint"
host="*"
httpPort="9060"
httpsPort="9443" />
<!-- Automatically expand WAR files and EAR files -->
<applicationManager autoExpand="true"/>
</server>
The WAS service also started. In Browser, after providing the credentials, it shows blank page. I'm unable to view any errors in the log.The log message is given below:
********************************************************************************
product = WebSphere Application Server 16.0.0.3 (wlp-1.0.14.cl160320160831-1555)
wlp.install.dir = /home/wlp/wlp/
java.home = /usr/jdk/instances/jdk1.8.0/jre
java.version = 1.8.0_05
java.runtime = Java(TM) SE Runtime Environment (1.8.0_05-b13)
os = SunOS (5.11; amd64) (en_US)
process = 1894#solaris
********************************************************************************
[1/3/17 7:02:31:377 UTC] 00000001 com.ibm.ws.kernel.launch.internal.FrameworkManager A CWWKE0001I: The server server1 has been launched.
[1/3/17 7:02:31:407 UTC] 00000001 com.ibm.ws.kernel.launch.internal.FrameworkManager A CWWKE0100I: This product is licensed for development, and limited production use. The full license terms can be viewed here: https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/license/base_ilan/ilan/16.0.0.3/lafiles/en.html
[1/3/17 7:02:33:346 UTC] 00000017 com.ibm.ws.kernel.feature.internal.FeatureManager I CWWKF0007I: Feature update started.
[1/3/17 7:02:33:468 UTC] 00000001 com.ibm.ws.kernel.launch.internal.FrameworkManager I CWWKE0002I: The kernel started after 2.347 seconds
[1/3/17 7:02:34:007 UTC] 0000000f com.ibm.ws.security.ready.internal.SecurityReadyServiceImpl I CWWKS0007I: The security service is starting...
[1/3/17 7:02:34:570 UTC] 00000018 com.ibm.ws.security.token.ltpa.internal.LTPAKeyCreateTask I CWWKS4105I: LTPA configuration is ready after 0.043 seconds.
[1/3/17 7:02:34:771 UTC] 0000000f com.ibm.ws.security.ready.internal.SecurityReadyServiceImpl I CWWKS0008I: The security service is ready.
[1/3/17 7:02:34:973 UTC] 00000018 com.ibm.ws.tcpchannel.internal.TCPChannel I CWWKO0219I: TCP Channel defaultHttpEndpoint has been started and is now listening for requests on host * (IPv6) port 9060.
[1/3/17 7:02:34:977 UTC] 00000018 com.ibm.ws.tcpchannel.internal.TCPChannel I CWWKO0219I: TCP Channel defaultHttpEndpoint-ssl has been started and is now listening for requests on host * (IPv6) port 9443.
[1/3/17 7:02:35:026 UTC] 0000000f com.ibm.ws.app.manager.internal.monitor.DropinMonitor A CWWKZ0058I: Monitoring dropins for applications.
[1/3/17 7:02:35:360 UTC] 0000000f com.ibm.ws.cache.ServerCache I DYNA1001I: WebSphere Dynamic Cache instance named baseCache initialized successfully.
[1/3/17 7:02:35:361 UTC] 0000000f com.ibm.ws.cache.ServerCache I DYNA1071I: The cache provider default is being used.
[1/3/17 7:02:35:362 UTC] 0000000f com.ibm.ws.cache.CacheServiceImpl I DYNA1056I: Dynamic Cache (object cache) initialized successfully.
[1/3/17 7:02:35:817 UTC] 0000000f com.ibm.ws.ui.internal.v1.pojo.POJOLoaderService I CWWKX1015I: FILE persistence layer initialized for the Admin Center.
[1/3/17 7:02:35:821 UTC] 0000000f com.ibm.ws.ui.internal.v1.pojo.PlainTextLoaderService I CWWKX1063I: FILE persistence layer initialized for the Admin Center tool data loader.
[1/3/17 7:02:36:088 UTC] 00000017 com.ibm.ws.kernel.feature.internal.FeatureManager A CWWKF0012I: The server installed the following features: [jsp-2.3, servlet-3.1, ssl-1.0, jndi-1.0, json-1.0, adminCenter-1.0, distributedMap-1.0, appSecurity-2.0, jaxrs-2.0, restConnector-1.0, jaxrsClient-2.0, el-3.0].
[1/3/17 7:02:36:088 UTC] 00000017 com.ibm.ws.kernel.feature.internal.FeatureManager I CWWKF0008I: Feature update completed in 2.848 seconds.
[1/3/17 7:02:36:088 UTC] 00000017 com.ibm.ws.kernel.feature.internal.FeatureManager A CWWKF0011I: The server server1 is ready to run a smarter planet.
[1/3/17 7:02:36:454 UTC] 00000017 com.ibm.ws.webcontainer.osgi.webapp.WebGroup I SRVE0169I: Loading Web Module: IBMJMXConnectorREST.
[1/3/17 7:02:36:456 UTC] 00000017 com.ibm.ws.webcontainer I SRVE0250I: Web Module IBMJMXConnectorREST has been bound to default_host.
[1/3/17 7:02:36:456 UTC] 00000017 com.ibm.ws.http.internal.VirtualHostImpl A CWWKT0016I: Web application available (default_host): http://10.95.238.96:9060/IBMJMXConnectorREST/
[1/3/17 7:02:36:458 UTC] 00000017 com.ibm.ws.jmx.connector.server.rest.RESTAppListener I CWWKX0103I: The JMX REST connector is running and is available at the following service URL: service:jmx:rest://10.95.238.96:9443/IBMJMXConnectorREST
[1/3/17 7:02:36:459 UTC] 00000017 com.ibm.ws.jmx.connector.server.rest.RESTAppListener I CWWKX0103I: The JMX REST connector is running and is available at the following service URL: service:jmx:rest://10.95.238.96:9443/IBMJMXConnectorREST
[1/3/17 7:02:36:599 UTC] 00000018 com.ibm.ws.webcontainer.osgi.webapp.WebGroup I SRVE0169I: Loading Web Module: ibm/api.
[1/3/17 7:02:36:599 UTC] 00000018 com.ibm.ws.webcontainer I SRVE0250I: Web Module ibm/api has been bound to default_host.
[1/3/17 7:02:36:600 UTC] 00000018 com.ibm.ws.http.internal.VirtualHostImpl A CWWKT0016I: Web application available (default_host): http://10.95.238.96:9060/ibm/api/
[1/3/17 7:02:36:637 UTC] 00000018 com.ibm.ws.webcontainer.osgi.webapp.WebGroup I SRVE0169I: Loading Web Module: The Liberty Server Config Tool.
[1/3/17 7:02:36:637 UTC] 00000018 com.ibm.ws.webcontainer I SRVE0250I: Web Module The Liberty Server Config Tool has been bound to default_host.
[1/3/17 7:02:36:637 UTC] 00000018 com.ibm.ws.http.internal.VirtualHostImpl A CWWKT0016I: Web application available (default_host): http://10.95.238.96:9060/ibm/adminCenter/serverConfig-1.0/
[1/3/17 7:02:37:049 UTC] 00000018 com.ibm.ws.webcontainer.osgi.webapp.WebGroup I SRVE0169I: Loading Web Module: The Liberty Explore Tool.
[1/3/17 7:02:37:050 UTC] 00000018 com.ibm.ws.webcontainer I SRVE0250I: Web Module The Liberty Explore Tool has been bound to default_host.
[1/3/17 7:02:37:050 UTC] 00000018 com.ibm.ws.http.internal.VirtualHostImpl A CWWKT0016I: Web application available (default_host): http://10.95.238.96:9060/ibm/adminCenter/explore-1.0/
[1/3/17 7:02:37:183 UTC] 00000017 com.ibm.ws.webcontainer.osgi.webapp.WebGroup I SRVE0169I: Loading Web Module: The Liberty Admin Center.
[1/3/17 7:02:37:184 UTC] 00000017 com.ibm.ws.webcontainer I SRVE0250I: Web Module The Liberty Admin Center has been bound to default_host.
[1/3/17 7:02:37:184 UTC] 00000017 com.ibm.ws.http.internal.VirtualHostImpl A CWWKT0016I: Web application available (default_host): http://10.95.238.96:9060/adminCenter/
[1/3/17 7:04:00:203 UTC] 00000023 com.ibm.ws.session.WASSessionCore I SESN8501I: The session manager did not find a persistent storage location; HttpSession objects will be stored in the local application server's memory.
[1/3/17 7:04:00:205 UTC] 00000023 com.ibm.ws.session.WASSessionCore I SESN0176I: A new session context will be created for application key default_host/adminCenter
[1/3/17 7:04:00:212 UTC] 00000023 com.ibm.ws.util I SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation.
[1/3/17 7:04:00:222 UTC] 00000023 com.ibm.ws.jsp I JSPG8502I: The value of the JSP attribute jdkSourceLevel is "15".
[1/3/17 7:04:00:241 UTC] 00000023 com.ibm.ws.cache.CacheServiceImpl I DYNA1056I: Dynamic Cache (object cache) initialized successfully.
[1/3/17 7:04:00:281 UTC] 00000023 com.ibm.ws.webcontainer.security.ServletStartedListener I CWWKS9122I: For URL /* in application com.ibm.ws.ui, the following HTTP methods are uncovered, and accessible: HEAD OPTIONS TRACE
[1/3/17 7:04:00:282 UTC] 00000023 com.ibm.ws.webcontainer.security.ServletStartedListener I CWWKS9122I: For URL /dojo/* in application com.ibm.ws.ui, the following HTTP methods are uncovered, and accessible: HEAD OPTIONS TRACE
[1/3/17 7:04:00:282 UTC] 00000023 com.ibm.ws.webcontainer.security.ServletStartedListener I CWWKS9122I: For URL /login/* in application com.ibm.ws.ui, the following HTTP methods are uncovered, and accessible: HEAD OPTIONS TRACE
[1/3/17 7:04:00:282 UTC] 00000023 com.ibm.ws.webcontainer.security.ServletStartedListener I CWWKS9122I: For URL /login.jsp in application com.ibm.ws.ui, the following HTTP methods are uncovered, and accessible: HEAD OPTIONS TRACE
[1/3/17 7:04:00:283 UTC] 00000023 com.ibm.ws.webcontainer.security.ServletStartedListener I CWWKS9122I: For URL /fonts/HelvNeueRomanforIBM.otf in application com.ibm.ws.ui, the following HTTP methods are uncovered, and accessible: HEAD OPTIONS TRACE
[1/3/17 7:04:00:283 UTC] 00000023 com.ibm.ws.webcontainer.security.ServletStartedListener I CWWKS9122I: For URL /ibm_security_logout in application com.ibm.ws.ui, the following HTTP methods are uncovered, and accessible: HEAD OPTIONS TRACE
[1/3/17 7:04:04:191 UTC] 00000023 com.ibm.ws.webcontainer.servlet I SRVE0242I: [com.ibm.ws.ui] [/adminCenter] [/login.jsp]: Initialization successful.
[1/3/17 7:04:04:400 UTC] 00000023 com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "java.lang.IllegalStateException: Must use either different key or iv for GCM encryption com.ibm.ws.webcontainer.servlet.FileServletWrapper.writeResponseToClient 689" at ffdc_17.01.03_07.04.04.0.log
[1/3/17 7:04:09:486 UTC] 00000023 com.ibm.ws.webcontainer.servlet I SRVE0242I: [com.ibm.ws.ui] [/adminCenter] [/toolbox.jsp]: Initialization successful.
[1/3/17 7:04:09:535 UTC] 00000021 com.ibm.ws.session.WASSessionCore I SESN0176I: A new session context will be created for application key default_host/ibm/api
[1/3/17 7:04:09:536 UTC] 00000021 com.ibm.ws.util I SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation.
[1/3/17 7:04:09:553 UTC] 00000021 com.ibm.ws.webcontainer.servlet I SRVE0242I: [com.ibm.ws.rest.handler] [/ibm/api] [RESTProxyServlet]: Initialization successful.
[1/3/17 7:04:09:612 UTC] 00000021 com.ibm.ws.ui.internal.v1.pojo.POJOLoaderService I CWWKX1029I: The Admin Center default toolbox for user admin loaded.
[1/3/17 7:04:09:613 UTC] 00000021 com.ibm.ws.ui.internal.v1.pojo.POJOLoaderService I CWWKX1000I: The Admin Center default catalog loaded.
Kindly guide me how to fix this issue.
Looks like issue in Solaris JVM , try to:
Disable the GCM implementation from the OracleUcrypto provider by
adding the "Cipher.AES/GCM/NoPadding" string to the disabledServices
section in its provider configuration file, for example,
/lib/security/ucrypto-solaris.cfg.
Or install JVM that is available in WebSphere Application Server product installation files (downloadable separately from Passport Advantage).
Related
ERROR [org.keycloak.services] : Failed to send email: javax.mail.AuthenticationFailedException: 421 4.7.66 TLS 1.0 and 1.1 are not supported
I am having keycloak running on docker container version 15.0.2 , Java version 1.8.0_181 OS - Windows server 2016 10.0 ERROR [org.keycloak.services] (default task-2) KC-SERVICES0029: Failed to send email: javax.mail.AuthenticationFailedException: 421 4.7.66 TLS 1.0 and 1.1 are not supported. Please upgrade/update your client to support TLS 1.2 Click here to see details of Keycloak server info
Getting 500 Internal server error from application deployed on IHS and WAS server
Web based application intermittently throwing '500 Internal Server Error'. This application is deployed on WAS 8.0 server with IHS and WAS servers hosted on different machines. Please find below the TRACE level plugin logs at IHS end. DEBUG: ws_common: websphereExecute: Wrote the request; reading the response (timeout 900) DETAIL: lib_htresponse: htresponseRead: Reading the response: 64040a70 TRACE: lib_rio: Blocking for read, waiting 900 DEBUG: lib_rio.c line 896 : Read failed, rc=104 DEBUG: lib_htresponse: htresponseSetError: Setting the error to: |READ_FAILED|(1, Line: 713) DEBUG: ws_common: websphereExecute: Failed to read from an old stream; probably Keep-Alive timeout fired DEBUG: ws_transport: transportStreamDequeue: Checking for existing stream from the queue DEBUG: lib_stream: destroyStream: Destroying the stream DEBUG: lib_rio: rclose: socket 13 closed STATS: ws_server: serverSetFailoverStatus: Server xxxxx : pendingRequests 0 failedRequests 7 affinityRequests 57 totalRequests 51. ERROR: ws_common: websphereHandleRequest: Failed to execute the transaction to 'xxxxx' on host 'yyyyy'; will try another one ERROR: ws_common: websphereWriteRequestReadResponse: Failed to find an app server to handle this request ERROR: ESI: getResponse: failed to get response: rc = 10 DEBUG: ESI: esiHandleRequest: failed to get response DEBUG: ESI: esiRequestUrlStackDestroy DEBUG: ESI: cacheURL: '/site/index' DETAIL: ESI: esiRequestPopUrl: '/site/index' DEBUG: ESI: esiUrlDestroy: '/site/index' ERROR: [://site/index] ws_common: websphereHandleRequest: Failed to handle request rc=10 DEBUG: ws_common: websphereCloseConnection DETAIL: ws_common: websphereEndRequest: Ending the request Please help me to get the issue resolved. Thanks in advance
rc=104 is the linux return code indicating that the socket was reset by the partner address so you need to look at the application server for errors.
OrientDB & .Net driver: Unable to read data from the transport connection
Getting error while reading network stream from a successful socket connection. PL see the debug log from orient DB:
2016-04-08 18:08:51:590 WARNI Not enough physical memory available for DISKCACHE: 1,977MB (heap=494MB). Set lower Maximum Heap (-Xmx setting on JVM) and restart OrientDB. Now
running with DISKCACHE=256MB [orientechnologies]
2016-04-08 18:08:51:606 INFO OrientDB config DISKCACHE=-566MB (heap=494MB os=1,977MB disk=16,656MB) [orientechnologies]
2016-04-08 18:08:51:809 INFO Loading configuration from: C:/inetpub/wwwroot/orientdb-2.1.5/config/orientdb-server-config.xml... [OServerConfigurationLoaderXml]
2016-04-08 18:08:52:292 INFO OrientDB Server v2.1.5 (build 2.1.x#r${buildNumber}; 2015-10-29 16:54:25+0000) is starting up... [OServer]
2016-04-08 18:08:52:370 INFO Databases directory: C:\inetpub\wwwroot\orientdb-2.1.5\databases [OServer]
2016-04-08 18:08:52:495 INFO Listening binary connections on 127.0.0.1:2424 (protocol v.32, socket=default) [OServerNetworkListener]
2016-04-08 18:08:52:511 INFO Listening http connections on 127.0.0.1:2480 (protocol v.10, socket=default) [OServerNetworkListener]
2016-04-08 18:08:52:573 INFO Installing dynamic plugin 'studio-2.1.zip'... [OServerPluginManager]
2016-04-08 18:08:52:838 INFO Installing GREMLIN language v.2.6.0 - graph.pool.max=50 [OGraphServerHandler]
2016-04-08 18:08:52:838 INFO [OVariableParser.resolveVariables] Error on resolving property: distributed [orientechnologies]
2016-04-08 18:08:52:854 INFO Installing Script interpreter. WARN: authenticated clients can execute any kind of code into the server by using the following allowed languages:
[sql] [OServerSideScriptInterpreter]
2016-04-08 18:08:52:854 INFO OrientDB Server v2.1.5 (build 2.1.x#r${buildNumber}; 2015-10-29 16:54:25+0000) is active. [OServer]
2016-04-08 18:08:57:986 INFO /127.0.0.1:49243 - Connected [OChannelBinaryServer]
2016-04-08 18:08:58:002 INFO /127.0.0.1:49243 - Writing short (2 bytes): 32 [OChannelBinaryServer]
2016-04-08 18:08:58:002 INFO /127.0.0.1:49243 - Flush [OChannelBinaryServer]
2016-04-08 18:08:58:002 INFO /127.0.0.1:49243 - Reading byte (1 byte)... [OChannelBinaryServer]
Using OrientDB .Net binary (C# driver) in Windows Vista. This was working fine until recently. Not sure what broke it...
Resetting TCP/IP using NetShell utility did not help.
Any help is highly appreciated.
The problem was with the AVG anti-virus program that is blocking the socket. Added an exception in the program for localhost to fix the problem.
Connect to embedded orientdb server
I have a embedded server with this default config: orientdb-server-config.xml I use version 1.0 from maven. I'm having trouble connecting to it from the console. Here is the command I tried: connect remote:localhost/temp admin admin Disconnecting from the database [null]...OK Connecting to database [remote:localhost/temp] with user 'admin'... Error: com.orientechnologies.orient.enterprise.channel.binary.ONetworkProtocolException: Binary protocol is incompatible with the Server connected: client=9, server=12 But I have these listeners: <listener protocol="binary" port-range="2424-2430" ip-address="0.0.0.0"/> <listener protocol="cluster" port-range="2434-2440" ip-address="0.0.0.0"/> <listener protocol="http" port-range="2480-2490" ip-address="0.0.0.0"> And this storage: <storage loaded-at-startup="true" userPassword="admin" userName="admin" path="memory:temp" name="temp"/> Everything is like the default orientdb-server-config.xml How do I connect to this embedded database from the console? Startup output: 2012-05-21 06:57:37:496 INFO OrientDB Server v1.0 is starting up... [OServer] 2012-05-21 06:57:38:003 INFO -> Loaded memory database 'temp' [OServer] 2012-05-21 06:57:38:038 INFO Listening binary connections on 0.0.0.0:2424 [OServerNetworkListener] 2012-05-21 06:57:38:039 INFO Listening cluster connections on 0.0.0.0:2434 [OServerNetworkListener] 2012-05-21 06:57:38:040 INFO Listening http connections on 0.0.0.0:2480 [OServerNetworkListener] 2012-05-21 06:57:38:062 INFO OrientDB Server v1.0 is active. [OServer] UPDATE: it's working with [OServer] OrientDB Server v1.0rc9 UPDATE2: the issue was that I had version 1.0 in the server and used the console client from 1.0rc9. But now everything seems ok when server is running 1.0 and i try with client console 1.0. Thanks!
Unable to start JBoss from within Eclipse
I am unable to start JBoss server 5.1.0.GA version from eclipse Indigo. Eclipse shows me message box saying 'Server JBoss v5.0 at localhost was unable to start within 500 seconds. If the server requires more time, try increasing the timeout in the server editor.' but in the console window I can see that JBoss has been actually started. here is some part of log which I can see in console window of eclipse : SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface 15:14:20,212 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3 15:14:20,212 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView 15:14:20,222 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: SecureManagementView/remote - EJB3.x Default Remote Business Interface SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface 15:14:20,252 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3 15:14:20,262 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService 15:14:20,272 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: SecureProfileService/remote - EJB3.x Default Remote Business Interface SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface 15:14:20,362 INFO [TomcatDeployment] deploy, ctxPath=/admin-console 15:14:20,412 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console' 15:14:23,486 INFO [TomcatDeployment] deploy, ctxPath=/BannedListSearch 15:14:27,532 INFO [TomcatDeployment] deploy, ctxPath=/IWorkWebApp 15:14:27,813 INFO [TomcatDeployment] deploy, ctxPath=/ 15:14:29,155 INFO [TomcatDeployment] deploy, ctxPath=/TestWebProject 15:14:30,036 INFO [TomcatDeployment] deploy, ctxPath=/displaytag-examples-1.2 15:14:30,136 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console 15:14:30,276 INFO [TomcatDeployment] deploy, ctxPath=/HelloWebService 15:14:30,407 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 15:14:30,687 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8081 15:14:30,707 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 15:14:30,707 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 48s:110ms I have increased start Timeout of server to 500 seconds then also I am getting same error. I have not changed anything else. I am able to start JBoss from command prompt successfully but same server is not getting started from eclipse. Please help me to start the JBoss server.
Sound to me like the http port you are configured in JBoss is different to the port you have in the Eclipse configuration for JBoss. Eclipse uses the port configuration to listen to JBoss' port so that it can determine that JBoss has actually started. If they differ, Eclipse thinks JBoss has never started although it actually has according to the log console. Make the ports match and it will probably work. Updated: According to your log, JBoss is using port 8081 for HTTP: Starting Coyote HTTP/1.1 on http-127.0.0.1-8081 Now you have to tell Eclipse to listen to that port so that it can figure out whether JBoss has started (default is 8080 and therefore Eclipse will never be aware of it!). Go to your servers view, double click on your JBoss server, and the configuration screen will come up: You have to edit the HTTP port (in the 'Port' box) and set it to 8081 so that it matches your server's.