I have a micro service written using Java EE + Openliberty. I have deployed this into kubernetes in my Docker-Desktop. I want to know, is there any way to debug this deployed service? I am using Eclipse. Please let me know how can I debug deployed service. Thank you!
I heartily endorse looking at telepresence. I don't use it for real yet, but I've verified it will be very useful in our enterprise once we get some pieces in place.
However, I don't believe you need that complication for your simpler situation. Telepresence will be very nice for injecting NEW code into a cluster without actually deploying it. In your case, you just want to debug the existing code. This allows for a simpler mechanism.
To remotely debug in Eclipse, you need to connect to a debugger port. To do this with code running in a k8s cluster, you have to expose the port to connect to, and make it available on your desktop.
In your image, you have to ensure that your Java command line has the "-Xdebug" parameters, which specifies the debugger port (5005 by convention). You also have to ensure that your Dockerfile specifies that port to be exposed. When that is running in your cluster, you have to use "kubectl port-forward" on your desktop (with appropriate parameters). This will proxy the debugger port in the cluster to a corresponding port on your desktop. You then connect to that port from Eclipse.
If you want to debug your application, you can do it using either squash or telepresence. Here is great article comparing these two solutions
Article also mentions that squash doesn't support eclipse, but notice that is was written in 2018 and since then squash added support for eclipse IDE.
I'm trying to migrate a web app from Websphere to JBoss.
I believe the first step is to port the configurations of the server. The main configuration file in Jboss is standalone.xml (or domain.xml for running multiple instances of a server).
Could you tell me what the equivalent of standalone.xml is in websphere ?
Thank you for your time.
There is no direct equivalent. WebSphere is administered via the administration console. If you run WebSphere Express you can connect directly to the app. server's administration port. If you run Network Deployment, you connect to the deployment manager console (DMGR).
The console has all the configuration. They are stored in many XML files, that can be a pain to use directly. Much easier with the console.
The default console port is 9060 (http) or 9043 (https).
URL:
http://yourserver:9060/ibm/console
https://yourserver:9043/ibm/console
See this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21155098
for a bit more information.
You can look at this migration guide for JBoss AS 7.
https://docs.jboss.org/author/display/AS72/How+do+I+migrate+my+application+from+WebSphere+to+AS+7?_sscc=t
I am very new to jboss app server and using jboss app server 4.1.4 and want to upgrade to any latest version like 6 or 7. What’s the best process to perform i.e. I have seen that “copy the .rar and .war files” and these can’t make right scene to work. What's the best process?
The best way to start is to get an overview over your existing application. In particular:
Which non-standard JBoss features do you use (JBoss Cache, JCA Work Manager, …)?
What "managed resources" (data sources, connection factories, …) do you use?
Which configuration changes did you make (connection pool, transaction timeout, …)?
Which classloading assumptions does your packaging make?
and then individually check how these are handled in the JBoss version you want to migrate to.
there is no one to answer this question..looks shame about it.
While starting JBoss, it stops at Binding TransactionManager JNDI.
This is a clean install of JBoss on my machine and before installing it I had installed Oracle.
I thought there might be a port conflict so I changed the ports used by oracle to 9090.
Also I tried restarting my machine and running it again but it still didn't work.
Any idea what I might be doing wrong ?
Use a port monitoring application such as CurrPorts and try to identify if there are any ports which are used for JNDI is bound to any other application. If found, terminate the application and probably your JBoss will start up without any issue.
If the problem persists, try to see and correct if there is any entities in your application which are wrongly mapped.
I had something like this once, and it turned out that my AV software (Avast) was using a port that JBoss wanted. Once I sorted out the conflict, all was well.
Staring JBoss server from within Eclipse Ganymede gives me the following problem:
"Server JBoss v4.0 at localhost was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor."
The console shows JBoss has started in so and so minutes but soon after, there is a pop up if the above message.
I can also start the JBoss externally.
I had a similar problem, but it was with a Tomcat 5.5 server.
The startup time was quite important, so I got this error.
To solve this problem, I did that steps:
In Preferences, Server, I changed the property "Server timeout delay" to "Unlimited".
Edit:
For Eclipse Ganymede, you must do that:
In the server view, double-click on your server JBoss.
In the overview, you have a "Timeouts" panel (by default, it is collapsed).
You can define the timeouts for server start and stop operations.
I had a similar problem. It turned out that Eclipse’s server default port was set to 8080 while my JBoss was working from 8180.
By changing the server’s configuration in Eclipse (double-click on the server and edit server property), it worked.
Increasing the timeout doesn't solve the problem. Eclipse never recognizes that the server has started (not sure if that's a big deal), just irritated me. I had this problem for weeks and finally figured out that (at least for me) the host name and address had to be identical. I had hostname:localhost; address"127.0.0.1" and it would not work. I changed both to 127.0.0.1 and voila!
Like this:
In my Eclipse with Jboss Tools, that ocurred too, I change the "Host name", on General information of JbossServer, from my machine name to 127.0.0.1.
Thanks, this works fine!
I've seen this behavior when I've changed JBoss to run via SSL on port 8443 instead of unencrypted on port 8080. It is my theory that the Eclipse plugin is checking on port 8080 to confirm that JBoss has started, and that this check is hardcoded and does not respect changes you make to the configuration to specify that the server runs on a different port.
Our workaround is to start JBoss from the debug pulldown menu, which apparently disables the timeout.
Try the following:-
Check if the port jboss configured correctly in the general information. It is usually 8080 unless you've changed it.
I use the hostname as 0.0.0.0 so that it can be accessed from other computers on the network.
I had a problem where I was connected to a vpn and it was causing this issue. Shut off any vpn connections.
You have to change ports defined in JBoss configuration panel. I have used -Djboss.service.binding.set=ports-01 to upgrade port numbers - and forgot to change Eclipse/JBoss configuration - and Eclipse failed to notice JBoss is already running.
Yes I had similar problem Jboss could not start from Eclipse Galileo within default 50 secs
so just changed server startup time by double clicking Jboss server icon in Server window near console & error log (NOT at windows->preferences->server). It opens server editor and then increased the start up time to 300
It worked then. !!!
I had the same issue and corrected it by modifying a "server.xml" file in the jboss folders.
I modified '<Connector port="8080"' by '<Connector port="server port defined in Eclipse"'
You may check whether you are running Jboss version 4.0.4 or version 4.2.2. You might get this error when you have installed Jboss 4.2.2 but configured Jboss 4.0.4 in Eclipse.
Are yoy runing on Linux?
If so, check if jBoss has write privileges over /tmp ...
I had the same problem, and I fixed creating a temp directory with RW privileges to User, Group and others, and adding this line to eclipse.ini
-Djava.io.tmpdir=yourTempDirectory
where your temp directory is the absolute addres of the Temp directory that you created.
I've come upon the same problem and found the explanation. For Eclipse, JBoss is expected to support the jboss-web service (tomcat.sar) which implies an HTTP port to be opened at the end of the process. In my case, as this service is disabled, no HTTP port is opened when the server is running...
Solution: simply double click on the jboss server in the Servers panel and copy the JNDI port to the Port field, in Server Properties section. This makes it.
This way, it is no more necessary to change host name to 127.0.0.1, you may let it be what you want (e.g. localhost is the default).
Double click on the jBoss server icon in the server view. A window pops up with “Timeout” collapsed. Click on the arrow and increase the start time.
I am new to EJB - Jboss. I too was getting the same problem
Jboss Is not started in given time, increase Start-up time out]]
It is not solved by your given valuable suggestions.
According to console: My Jboss-5.1.0.GA Server started in 50:21, 49:91 ...so on.
But not responded well with given host name: 10.168.2.11
Server Configuration Server: 10.168.2.11 which I like to execute when using ant.
Solution: All though It is worked well with
host Name: localhost
Server Name:localhost
Even increased port i.e. ports-02: result in http: port 8280
Attempted every practice given here. This is mine. Hope that eclipse community with jboss collaboration give right solution.
I don't know but bit Ground point in this Suggestion: https://stackoverflow.com/a/945444/1164686
Right click on "JBoss 4.2 at localhost" at "servers" window and select open, after that,
just change the port number from 8080 to 8081 and you are good to go.
I could fix it by using Aboucabar Toure's advice: under Eclipse Indigo, I opened JBoss server properties and edited the Server Ports group to match my JBoss ports configuration (unchecking Detect from Local Runtime boxes).
Then everything worked just fine!
If you are using a non default port for, instance 8180. You should configure eclipse to poll server at desired port number. See this picture:
This also happened when you create the jboss with different server version. I was using JBoss AS 7.2.0 final but had no idea to use which server version in eclipse. I tried with WildFly but that leads to this error. With all the good tips in here didn't solve my problem. Thanks to this post i corrected that with correct version. I should have used Jboss Enterprise Application platform 6.1.
Remove all eclipse breakpoint in the debug view, and the jboss will quickly start.
I am also facing same issue, after change the port number it has worked for me.
Port number in server.xml and jboss port number should be same.
goto -> jboss-4.0.3\server\default\deploy\jbossweb-tomcat55.sar\server.xml
Connector port="9090"
goto -> Double click on server and change your port number as what you gave in server.xml