I have problem while starting my WebSphere Application Server 7.0 in debug mode.I keep getting a window prompting for "Edit source Lookup Path".I have cleared wstemp,temp and after that the server got started in debug mode but the breakpoints are getting skipped.I couldn't find any difference whether the server runs in normal / debug mode.
IDE Used : Rational Application Developer 7.5.3
Please suggest a solution to run my WAS in debug mode and check with breakpoints.
You could try updating your version of RAD to 7.5.5.5 (there might even be a newer version), and update your version of WAS to the latest patch as well. We had a lot of issues with earlier versions of RAD
Related
I am trying to run Weblogic server on IntelliJ in debug mode. But I get the following exception
Method threw 'java.lang.NullPointerException' exception. Cannot evaluate weblogic.management.configuration.DomainMBeanImpl.toString()
I tried deleting all the deployments through IntelliJ and config.xml file, still I get this issue.
However Weblogic is able to run fine when not in Debug mode.
Please feel free to reach out for any further clarifications.
I'm running a small java application on TomCat 9.0.56 for class that has to connect to a database. I'm using jdbc (ojdbc8 - 19.3.0.0). It was working fine untill it started displaying the following error:
16-Jan-2022 21:03:42.631 SEVERE [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener [oracle.ucp.jdbc.UCPServletContextListener] java.lang.NoSuchMethodException: oracle.ucp.jdbc.UCPServletContextListener.<init>()
I'm new to tomcat and I'm not sure how to fix this. I have re-installed everything but it hasn't worked again. Any idea?
IDE - IntelliJ 2021.2.3
JDK - 17.0.1
I am sure you must be using Oracle JDBC and UCP binaries from 21.1 release instead of 19.3 release. You can check and validate the ojdbc and ucp jar version using below command:
java -jar ucp.jar
java -jar ojdbc8.jar
The issue you have described above is a known issue with ucp 21.1 release jars. In order to fix the issue, you can simply switch to ucp/jdbc 21.3 release. Please make sure to upgrade both ucp.jar and ojdbc8.jar to 21.3, not just one. Also, make sure to remove all duplicate jars(if any) from the class-path.
Here is a related thread for the same issue:
Ojdbc8 jars upgrade to 21.1.0.0 throws Nosuchmethod exception UCPservletContextListener init
Weirdly, uninstalling and deleting all tomcat versions previously used and installing a new one and setting up a new configuration made the error stop happening and the app is running nicely again.
I had done this before with no results, but this time it did work.
Since updating my iPad to iOS 15, I can no longer run the debug version of my app on it (the prod version works fine). It gives me an error saying "The developer of this app needs to update it to work with this version of iPadOS."
Googling this error, I found a post about going to 64 bit by default to resolve this, back from 2017 (https://www.codenameone.com/blog/moving-to-64bit-by-default.html)
I checked my app settings and I don't have the hint that would force a 32bit build (ios.debug.archs=armv7). Is there anything else I can check to see why this is happening?
This is probably related to this: https://www.reddit.com/r/cn1/comments/ori4ve/ios_14_support/
Try the ios.zsign=true build hint.
I am attempting to create/deploy an application onto the Redhat OpenShift Express platform, and am attempting to do this via eclipse using the JBoss OpenShift plugins.
I am following the instructions here: https://www.redhat.com/openshift/community/blogs/getting-started-with-the-openshift-eclipse-plug-in-for-java-applications-on-the-cloud
But when entering my user credentials I get an error preventing me getting any further:
Could not check user credentials: Could not unmarshall response "
{"data":
{"user_info":
{"env_vars":null,
"max_gears":5,
"system_ssh_keys":null,
"uuid":"5a81de3405fe4ac6b5718dbb8540736f",
"rhc_domain":"rhcloud.com",
"rhlogin":"robert.hinds#accenture.com",
"ssh_keys":
{"laptop":{"type":"ssh-rsa","key":"AAAAB3NzaC1yc2EAAAABIwAAAQEAw5GIjtI+B42SBv2kmV32OHI5tCBO7JWmlhF7w9dNy2Tp7MNtK8nE7nLUKYyXSZRzK0i4azPuMDDmmJ4jFpcyAwRdzBM43xZLo/6MlMFneT3t66ukNMNOgYptiRH7Zy8Tmjquwu2dXpui77tRQaEpq4Ms/JxHvanD+YMDNTXlrv8gIDwOjhtetuyeKbf/sr+UK1Bit8eDTgai01UmjXm+u/0Hi1tD6oG/GwNviQKb/2gmrmEs0uPhcJ9Olzrn67Gyu7c2PFOjTEvOXMQHjSUrVp905t8SzffiJ7uWzVnvufrweC5gXlR/v1tp3FrFgRcZVmZX6QlhyOiy5Tr1cLD8pw=="}},
"consumed_gears":0,
"vip":false,
"namespace":"star",
"ssh_key":null,
"ssh_type":null
},
"app_info":{}
},
"api_c":["placeholder"],
"messages":"",
"broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],
"exit_code":0,
"debug":"",
"api":"1.1.3",
"result":""
}
has anyone come across this previously? I am on Win7 Eclipse Indigo on JDK7
Update:
I get this problem using the following versions/steps
Using Eclipse: Eclipse Java EE IDE for Web Developers. Version: Indigo Service Release 2 Build id: 20120216-1857
Installed the OpenShift express tools from the JBoss software update site here: http://download.jboss.org/jbosstools/updates/development/indigo/ today (the current version that is downloaded today!)
Then simply file > new > openshift aplication, then enter my username and password (created today with OpenShift Express) and I get the error.
hope thats helpful - will wait for the update to the software.
this is a "known" issue in the sense that you're not the first that reported this:
https://issues.jboss.org/browse/JBIDE-11431
The "interesting" part is that unmarshalling the response fails because of the following 2 properties with null values:
"ssh_key":null,
"ssh_type":null
This error occurrs since OpenShift added support for several keys. We fixed the unmarhslling issue but still dont know how to reproduce it. If you can we'd be very happy to get your instructions.
The fixed version of our client plugin will make it to our nightly update site in a few days. Stay tuned!
When I try to debug any project in Java EE INDIGO (64 bit) in win 7 and place a breakpoint somewhere the program acts as expected but when I hit f6 or f5 to go further eclipse throws an error which reads (I have Spring installed):
An internal error occurred during: "JDI Event Dispatch".
com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
(No typo, "Z" does appear)
Now I can't debug any program because it always gives this error. Can anyone help?
From the eclipse error log:
!MESSAGE com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
!STACK 0
java.lang.AbstractMethodError: com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
at org.eclipse.contribution.jdt.debug.DebugHooksAspect.isInterestingLaunch(DebugHooksAspect.aj:253)
at org.eclipse.contribution.jdt.debug.DebugHooksAspect.ajc$inlineAccessMethod$org_eclipse_contribution_jdt_debug_DebugHooksAspect$org_eclipse_contribution_jdt_debug_DebugHooksAspect$isInterestingLaunch(DebugHooksAspect.aj:1)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.getStepFilters_aroundBody1$advice(JDIDebugTarget.java:195)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.getStepFilters(JDIDebugTarget.java:1)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.attachFiltersToStepRequest(JDIThread.java:2154)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.createStepRequest(JDIThread.java:2065)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.createStepRequest(JDIThread.java:2040)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.step(JDIThread.java:1989)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.stepOver(JDIThread.java:1412)
at org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.stepOver(JDIStackFrame.java:418)
at org.eclipse.debug.internal.core.commands.StepOverCommand.step(StepOverCommand.java:27)
at org.eclipse.debug.internal.core.commands.StepCommand.doExecute(StepCommand.java:34)
at org.eclipse.debug.core.commands.AbstractDebugCommand$1.run(AbstractDebugCommand.java:213)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
This seems to be a similar bug to this bug in codehaus jira (see comments section). I was able to switch back to an older eclipse installation (from two weeks ago) to get rid of the current problem and will upgrade to Eclipse 3.7 as soon as time permits.
As crazy as this sounds, I too was getting this error when debugging an Android App and trying to step into a specific method, and resolved it by renaming the method I was trying to step into.
I had tried:
completely reinstalling the app
cleaning in Eclipse
reboot of device (phone), OS, and restart of Eclipse
increasing debug timeouts in Preferences | Java | Debug
My method was called "getMessageInfoFromDb"... and was in a class that didn't extend anything, but implemented Serializable ;-)
Try disabling simple step filtering, especially filtering of simple getters.
delete the Temp folder from yourlocalpath\domainfolder\server\AdminServer
domains\base_domain\servers\AdminServer
Have you done any DB import twice or more time on the same DB that you use for the application in which you are running in debug mode. Because I am also getting similar error with the caption JDI while starting Application Server with deployed .ear in Eclipse based IDE as a popup.
When db is imported twice user created tables gets imported if it's been tried in the same kind of databases. But Oracle App & System Specific tables throws error in process of importing. And some crash in that....
I hope this is what scenario yours as well....
In my scenario I had imported Oracle db from UNIX environment to Oracle XE in Windows environment.