Starting Websphere from Eclipse hangs when security is enabled

I have WebSphere Application Server 8.0.0.6 installed as part of RAD.

I need to start the server from Eclipse Java EE Kepler or Luna. This is not a problem when administrative security is disabled. However, once protection is enabled, the server either does not start completely or Ecplise cannot detect it.

The progress bar stops at 23%. Last logged message: "Server1 is open for e-business." However, the status is still "starting". After a while, I get a message that the server did not start after 300 seconds. It then tries to stop the server and remains "stopping" indefinitely.

The server is running, Eclipse just doesn't see it. I cannot access the admin console from Eclipse (although I can using a browser), I cannot publish or debug applications, and I cannot stop the server from Eclipse.

This happens with both Kepler and the Moon.

The server starts working fine in RAD or when started with a script run.

I tested starting websphere server from RAD hanging on Server1 open for e-business . There is a similat issue: Websphere in RAD hangs on startup but there was no solution.

Update: The problem is the communication between Ecipse and Websphere, after Websphere started (as wFateem pointed out).

Eclipse makes SOAP calls to Websphere to check the state. If administrative security is disabled in WAS, it accepts SOAP calls in plain HTTP. When security is enabled, only HTTPS is allowed.

I have checked the communication between Eclipse and WAS using TCP-Monitor built into Eclipse. With security disabled, I see successful SOAP calls. After enabling security, I expected to see only SSL binary data. However, Eclipse was still trying to use HTTP with no success.

Eclipse has an option for the WAS server that specifies that the server is secure and what user and password to use for calls. It even has a flag related to SSL communication ("automatically trust the server certificate during SSL handshaking"). But for some reason it doesn't use SSL.

I had no problem with this scenario on my old development machine, which was replaced by my current machine a few days ago.

So the current status is: Eclipse is not using SSL when talking to WAS even though it knows the server is secure.

Now the question is, what did I do wrong that Eclipse doesn't use SSL to communicate with the secure server?

+3


source to share


7 replies


If you suspect SSL issues, you can try the following workaround.
After starting the server (for example, via the command line), go to the web administrator console, and then: Global security > CSIv2 inbound communications

and in the transport section, set the transport to TCP-IP

. Save and restart the server. This will disable SSL for RMI / IIOP connections.

Then in RAD in the server settings change Server connection types...

to Manually provide connection settings

and select only RMI

.



Check if it works better.

As a last resort, you can also try to start the server, then exit RAD and start RAD again, it should detect the server as already running. But this is not very useful ...

+4


source


I have solved the same problems for WebSphere 7 and Eclipse Neon. Just start eclipse with ibm jdk 8 (google "ibm jdk 8 download").

My eclipse ini



-vm 
..\ibm_sdk80\jre\bin\javaw.exe 
-vmargs
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Xms256m
-Xmx1024m
-XX:MaxPermSize=320m   
-Dcom.ibm.ws.management.event.max_polling_interval=1000
-Dcom.ibm.websphere.thinclient=true

      

Best wishes, Sergei Batsura

+3


source


I'm not too familiar with running WAS from Eclipse. However, because of this sound, it looks like a communication problem between your IDE and the WAS server. If you can start the server and you get an "open for e-business" message, but Eclipse cannot see the corresponding status, and this only happens when security is enabled, then you need to learn how Eclipse authenticates and makes an SSL connection to the server WAS.

You can start the server without any problem, but other tasks will require authentication (stopping the server, getting status, etc.).

You may need to obtain a personal WAS server certificate from the local Eclipse trust store, for example.

+1


source


I got the same issue when trying to start WebSphere from Eclipse Luna. Finally, I was able to run it according to the guidelines posted by Alexander Kovacs in response to the developer forum: Failed to initialize SSL connection (WASCE7)

Hope this helps!

+1


source


it is important to change eclipse.ini. First of all by specifying WebSphere -vm BEFORE -vmargs Here are my options:

--launcher.XXMaxPermSize 
512M
-vm
C:\IBM\WebSphere\AppServer\java\jre\bin\javaw.exe
-vmargs
-Xms256m
-Xmx1024m
-XX:MaxPermSize=512m
-Xmx1024m
-Xshareclasses:name=IBMSDP_%u
-Xcompressedrefs
-Xquickstart
-Xgcpolicy:gencon
-Xmnx64m
-XX:+UseCompressedOops 
-Dcom.ibm.ws.management.event.max_polling_interval=1000
-Dcom.ibm.websphere.thinclient=true

      

After the above changes, communication with eclipse in WebSphere with security enabled works without issue

+1


source


It might be a silly piece of advice, but have you tried using the WebSphere Developer Tools? They are installed on top of Eclipse, either Luna or Kepler using P2

https://developer.ibm.com/wasdev/

Take a look at this web page to learn how to install the tools.

http://www-01.ibm.com/support/knowledgecenter/was_beta_devtools/com.ibm.websphere.wdt.doc/topics/t_install_wdt.htm

0


source


Update the JDK in the eclipse.ini file to IBM JDB 1.8 64Bit. I am using WAS 8.5.0 with Eclipse MARS. -vm : /IBM/WebSphere8.5/AppServer/java_1.8_64/bin/javaw

If eclipse won't start and return code = 13 then eclipse.ini version check is 1.7 -vmargs -Dosgi.requiredJavaVersion = 1.7 -Xms256m -Xmx1024m

Note. I've already commented on Sergey's answer, but you need to update some information.

0


source







All Articles