Kony Service call opstatus 1000 debug - temenos-quantum

I am making a simple service call in my Kony application and i can see that opstatus is returning back value as 1000, i have looked into the kony docs about this, Can anyone please help how to debug and make this working ?

Check your platform settings .
1000- Unknown Error while connecting (If the platform cannot differentiate between the various kinds of network errors, the platform reports this error code by default).

If you are using Java SE version 1.6, try again with Java SE version 1.7.

Related

JMeter, MSSQL, JDBC, and Integrated Security with sqljdbc_auth.dll

Notwithstanding this question, I still have not determined the error in my configuration causing the JMeter JDBC sampler to reject integrated security.
Downloaded the SQL Server JDBC package for x64 and installed mssql-jdbc-9.4.1.jre8.jar in JMETER_PATH\lib.
Installed mssql-jdbc_auth-9.4.1.x86.dll in JMETER_PATH\lib, too, but, as advised on the Blazemeter comments, I also installed it in C:\windows\system32, since it is on my java.library.path.
Restarted JMeter.
Still getting the error in the Response:
Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication. ClientConnectionId:9c225a40-362d-4aba-8339-cfab9270048f)
JMeter version is 5.4.1.
Updating with screenshot showing os.arch, java.library.path, and placement of the DLL.
Database URL: jdbc:sqlserver://myservername:1433;integratedSecurity=true
Add a Debug Sampler to your Test Plan and configure it like:
Look for os.arch property, it should be amd64 or x86_64, if it isn't - geta 64-bit Java SDK
Look for java.library.path property, copy the mssql-jdbc_auth-9.4.1.x64.dll library to one of the folders which are in the java.library.path
Restart JMeter to pick up the .dll
Make sure that integratedSecurity=true stanza is in your JDBC URL like
jdbc:sqlserver://somehost:1433;integratedSecurity=true

Connecting to Db2 on z/OS via JDBC using IBM JDK vs OpenJDK

I am able to connect to Db2 on z/OS with the IBM universal JDBC driver file db2jcc4.jar using IBM JDK 1.8 that is bundled with WebSphere 9. Every thing works fine and I can browse the catalog and execute queries. I used Squirrel SQL version 4.0.0.
But when I switch my JDK to the Open JDK 8 or 12 while keeping everything else the same, I get the following error. What should be done to fix this error? What is the difference between IBM JDK and Open JDK, which causes the DB2 connection to work with one JDK and fail with the other?
Here is one of matching articles of your case:
JDBC application may receive error "Security mechanism not supported"
https://www.ibm.com/support/pages/jdbc-application-may-receive-error-security-mechanism-not-supported
Resolving The Problem
Set the following property :
securityMechanism = ENCRYPTED_USER_PASSWORD_AND_DATA_SECURITY (13)
Alternatively you can set property retryWithAlternativeSecurityMechanism to YES(1).
Hope this helps.
According to IBM's documentation for their IBM Data Server Driver for JDBC and SQLJ, error code -4214 is an "Authorization failed" error -- and you know that much. But you can get more specific information about the problem if you call SQLException.getMessage. I think you may have done that already, but it's not entirely clear.
My semi-educated guess is that you haven't yet followed the configuration steps in IBM's driver documentation in the section "Configuring the Java Runtime Environment to Use SSL":
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_t0054066.html
You'll have to apply some common sense knowledge to those instructions to adapt them for the OpenJDK, and this might not be an IBM supported combination depending on what/how you do it. If you can somehow use the IBMJSSE2 Provider, that'd be nice.
I think Mao and Mustaccio probably have the right ideas, and probably you're just missing the server certificate in your truststore. The instructions linked above walk you through how to configure that.

MQ - 2142 error

I am new to Java-MQ programming. I am facing a strange issue.
I am trying to send a text message to WMQ V7 using java.
In my code I have a property called identifier which I am setting to the message by using the method msg.setStringProperty("IDENTIFIER", "XXXXX");
I deployed the code in Unix system and while testing I am getting MQ-2142 error MQRC_HEADER_ERROR.
The strange thing is when I am running the same code from my local desktop using netbeans-6.9 (like a standalone application) it is executing successfully.
Please help me out with this issue?

WebSphere 7 - class loader trace

I have just upgraded to WebSphere 7 (from 6.1), and I am having new class loading conflicts which I didn't have before.
I have looked a lot over the internet but couldn't find directions on how:
1. How to enable class loading trace.
2. Where does the output go to?
Thank you very much.
To enable the classloading information you need to go in application server > server_name > Java and Process Management > Process definition > Java Virtual Machine, there you will find the verbose classloading option. Enable it and restart the application server.
You should then find the classloading informations in the native_stderr.log in the <WAS_install_root>/profiles/<profile>/logs/<server> directory.
To add to Olivier.Roger's response (I don't have the permissions to respond inline), the information is in native_stderr.log.
(late, but for anyone else who finds this thread like I did)
I would recommend the class loader MustGather that is used by IBM support when you open a PMR. Expand the "Collecting data manually" section.

Can´t load a tomcat 5.5 application to production, and can´t find any errors

i have a server with a bunch of tomcat, springs applications, and i can´t load a particular one that uses quartz. The main problem is that i can´t find an error anywhere that tells me what went wrong. And the same application runs fine in the test server, which uses de samde 1.6 jdk, tomcat 5.5. The only difference is that the productions server is in debian lenny, the test server in Centos. I only get a HTTP Status 404: requested resource not available.
Nothing usefull in catalina.out, configured log4j using this tutorial: http://tomcat.apache.org/tomcat-5.5-doc/logging.html , but can´t find any error there either. So i was wondering where can i get a hint of the problem ? tomcat starts succesfully and the other applications load without any problem.
Thank you very much
tail -f the catalina.out when you load the application, even it fails you still should able to see the output of tomcat trying to load the classes.
You might want to adjust to log level to info to see that tho.
*with 404 error, you could also try check the apache log, if you are using mod jk or proxy linking them.

Resources