i have problem with websphere liberty app server.
i using intellij 12.1.4 and liberty 8.5.5.0
after creating my server in liberty and introducing liberty to intellij, in configuring at the bottom of form a warning with
"warning: Server jvm arguements must contain -Xshareclasses:none"
displayed.
1- what is this warn? is it a problem? if yes can i fix it and how?
however i can run and debug my app with no problem.
2- if debugging app break points not hit where it should? i dont no why? tomcat has not this problem???
3- if run app in debug mode and stopping it, after stop, a message with this message will be appeared:
Error running WebSphere 8.5.5.0:
Unable to open debugger port: java.net.SocketException "socket close"
Thanks for your response.
Related
I recently had to reinstall IntelliJ IDEA, and ever since then, I've been unable to run this one app that runs on Payara. I have Payara 5.2022.3 (full) installed and the project is using java 11.
This is the server log:
Artifact my_project-ear:ear exploded: Waiting for server connection to start artifact deployment…
Detected server admin port: 4848
Detected server http port: 8080
And then nothing happens.
And if I terminate the process I get a message:
Application Server was not connected before run configuration stop, reason: Unable to ping server at localhost:4848
Based on my observation it seems like a process starts running on port 4848 for a few seconds but then stops abruptly.
I checked the CrashDumps and here is the .dpm file in question.
https://drive.google.com/file/d/1AyLU2HOyXKxREjaDNyIU9eRYMnzaBspw/view?usp=sharing
I'd already tried:
Running it on a different port./ Checking if there was not a process blocking used ports.
"Renewing" the domain.xml in case it was corrupted somehow.
Using different JDK.
Reinstalling Windows
I'm positive there is no problem with the app's code (seen a friend run it on his computer today) and I also think no changes happened to the run/debug configuration or the payara and domain configuration ever since it was working before the IDEA reinstall.
(I'm also very new to payara, and software development in general, so I'm not quite as skilled in solving this kind of problem.)
Thank you for all your answers.
It looks like a bug in the Java version/vendor you are using which is causing the crash of the process. Updating to a more recent Java build or to a different JVM vendor should help.
We've recently moved from Eclipse to IntelliJ. When configuring remote debugging, it manage to connect to the process once (via host and port) and debugging works. However, after disconnecting, we cannot connect to the process again. IntelliJ shows:
Unable to open debugger port (itstl060:33411) java.net.ConnectException "Connection Refused"
This works in Eclipse and we can connect multiple times without any issues. Any idea if there is a solution for this?
Check your previous debugging service has stopped. Sometimes it may be still running. I have come across these kind of issues.
I have installed Worklight 6.2 on Linux, using Liberty 8.5.5 and DB2 10.5. Created the DB2 databases for WRKLGHT and WLREPORT. Have executed the Server Configuration Tool and successfully created a Worklight Server configuration (did not have any errors in the Console view when running the Ant tasks, tables were created successfully in the database, and configuration shows deployed status in the SCT). Created a runtime environment in the SCT, also seemed to succeed (no errors in Console view, tables created/updated, runtime environment shows deployed in the SCT). Stopped and restarted the Liberty server.
Can hit Worklight admin at (/worklightconsole) and log in successfully using my demo user, however it then indicates there are no runtime environments. When trying to access runtime environment at /worklight/console (which should be the correct URL given how I created the runtime config in SCT using my Worklight project WAR), I get various errors: first "Service unavailable since initialization is not yet complete." then after retrying for about a minute or two I get "javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up at com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForInitialization(AuthenticationFilter.java:561)".
Seems the management service is not starting up successfully. Upon reviewing the messages.log I see the following error precede it: "FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny serve. The most common reason is a failure in JMX communication with the ''worklightadmin'' service. You need to restart the web application after fixing the problem. [project worklight]" and this creates an FFDC log.
I know this is a lot of information but trying to be complete. Anything I should check to fix the JMX communication issue and get the management service starting?
Thank you for the replies back. Turns out there is an issue with Liberty (I was on 8.5.5.0) and the IBM JDK I was using (1.7_64). Swapped out to the Oracle JRE (1.7.0_60-b19), pointed Liberty to use it, and the problem was solved. I am pursuing a fix with the Liberty team through IBM Support for this issue.
I cannot give a unique solution, but I can explain the situation and this may lead to a solution.
The runtime servlet initialization tries to contact the Worklight Admin service. The Worklight Admin service is a web application that must be running when the runtime starts. The runtime was not able to find the Worklight Admin service. It waited a while, in case that the Worklight Admin service is just starting up, but then gave up due to a timeout because within a given time, it could not find the Worklight Admin service.
Possible reasons:
the web server is not at all configured to run the Worklight Admin service. In your case, this seems not the problem, since you can access the Worklight Console. You should also see in the log file whether the Worklight Admin service did start.
the worklightadmin service might never start up ... this could be a configuration problem, e.g. with the WLADMIN data base. This could also be detected from the server logs.
when the runtimes and the Worklight Admin service start up together, it might be that the Worklight Admin service simply takes too long to start. Let's say you have 100 webapps, and the runtime starts first and the Worklight Admin service starts last, it could be that the 98 other webapps take too much time to start. In that case, make your web server lighter ... run only Worklight on that webserver, nothing else.
the Worklight Admin service starts, but the runtime cannot communicate with it. This indicates that the JMX communication is misconfigured. Follow the documentation of the webserver how to configure JMX. For liberty, see http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_admin_restconnector.html?cp=SSD28V_8.5.5%2F1-5-2-10-1&lang=en
I'm using Eclipse Kepler WTP + the Glassfish Kepler plugins.
Problem is I'm not able to start my locally installed Glassfish any more with this configuration.
After run the launch configuration the progress bar is at 69% and does not continue. There is nothing in the logs etc. I also tried using a fresh workspace etc. but no success.
The Glassfish version I'm running is 3.1.2. With Eclipse Juno and the corresponding Glassfish plugins everything works just fine.
EDIT Seems to be an issue with the already existing domain inside GF. It is possible to use the plugin when creating a new domain.
Today I encountered the very same problem. For some reason, The Glassfish plugin couldn't start the domain - progess bar at 69%. A while after it stopped because of a time out. I don't know why it couldn't start.
Open the asadmin console : {GLASSFISH_DIRECTORY}/bin/asadmin
execute the start-domain command
Refresh the eclipse Glassfish plugin if needed. You can see that the server has been launched properly.
I know, it doesn't fix the problem. But do remember that the Glassfish plugin only provides a GUI. Command lines are still working if the plugin is not.
(Actually I don't want to create a domain again...)
The problem is eclipse cannot connect to your jmx glassfish port.
Look in your glassfish console por the jmx port where jmx admin service is listening, somethin like this:
2014-01-13T11:08:38.935+0100|Información: JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://mywks:8686/jndi/rmi://mywks:8686/jmxrmi
Check this port is running:
telnet mywks 8686
If the port is ok, the problem is eclipse can't connect to port using machine name , in my case the problem was due to proxy configuration.
Open eclipse proxy configuration (windows -> preferences -> network connection), try changing active provicer to "manual" and configure your proxy. If proxy is not the problem, you can try to configure your local machine name as local host loop in your etc/host file.
(Note changing your proxy settings can cause your eclipse stops accessing eclipse market place).
If this not resolves the problem, try to sniff eclipse to glassfish connection using wireshark.
Hope this help.
You probably have forgotten to fill in the root directory as Glassfish. Do that in the setting enviroment for the server in Eclipse.
I am attempting to deploy a simple exploded war application from idea 11.1.3 to a remote (same machine) JBoss 7.1.1. The War builds fine and starts to deploy, but I keep getting the following message on the attempted deploy:
Error running JBoss 7.1.1.Final: Unable to connect to the
localhost:8080
I am using Intellij's default JBoss 7 Remote configuration, which I've used successfully in the past. I can hit localhost:8080 directly with any browser so I know its responding. Ideas?
I've encountered with the same problem and found solution. May be this problem appeared because I've just switched from Eclipse. So I think someone it can be helpful.
For correct debugging JBoss remotely we need to specify 3 ports:
1) http port ('Port' field of the 'Remote Connection Settings' section) is used to ping JBoss server (periodical checking if the
server is alive) and to produce urls addressing resources on the server - FIRST TAB
2) native management port ('Management port' field of the 'JBoss Server Settings' section) is used to connect to the JBoss management
interface, to check for the server startup to be finished and to deploy artifacts - FIRST TAB
3) remote socket port - by default on JBoss it 8787 - LAST TAB
After this all will work fine.
I was little bit confusing because if I run JBoss under sudo – remote debug worked just fine.