Techcrony.info

Debugging Hibernate using Log4J Logs

nitingautam — Fri, 20 Aug 2010 07:17:02 +0000

People who work with Hibernate often want to see, what SQL it is prepairing behind the seen and how it is mapping in real for debug purpose. We can achieve this by enable log4j for Hibernate classes. This will give a detailed debug info.

If using log4j.properties, enter the below line at end:

### log JDBC bind parameters ###
log4j.logger.net.sf.hibernate.type=debug

### log prepared statement cache activity ###
log4j.logger.net.sf.hibernate.ps.PreparedStatementCache=debug

If using log4j XML file, enter below line before :

Happy Coding

HowTo Get RID of Just-In-Time debugger

admin — Tue, 05 Jan 2010 09:30:22 +0000

I installed Visual Studio, and with this it installed a Just-In-time script debugger .This Just-In-Time seems to come up all the time when I run Internet Explore and on each page of IE.

Solution

Open Start>Control Panels>Internet Options: Advanced and activate (check box)

* Disable Script Debugging (Internet Explorer)
* Disable Script Debuggung (Other)

Open the registry (use regedit, Click Start, Run, Regedit).

Go to this key:

HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings\JITDebug

And set it to 0.

java.security.NoSuchAlgorithmException: No implementation for AES/CBC/NoPadding found

nitingautam — Thu, 17 Dec 2009 09:33:34 +0000

Hi,

From past few days I and my few team members were getting the following error during LDAP authentication:

javax.net.ssl.SSLException: Algorithm missing:
   at com.sun.net.ssl.internal.ssl.SSLSocketImpl.f(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_az.j(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA12275)
   at com.xx.cat.fndt.auth.impl.ssl.TrustingSSLSocketFactory.getSSLSocket(TrustingSSLSocketFactory.java:147)
   at com.xx.cat.fndt.auth.impl.ssl.TrustingSSLSocketFactory.makeSocket(TrustingSSLSocketFactory.java:209)
   at netscape.ldap.LDAPConnSetupMgr.connectServer(LDAPConnSetupMgr.java:411)
   at netscape.ldap.LDAPConnSetupMgr.openSerial(LDAPConnSetupMgr.java:343)
   at netscape.ldap.LDAPConnSetupMgr.connect(LDAPConnSetupMgr.java:237)
   at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:163)
   at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1033)
   at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:915)
   at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:759)
   at com.xx.cat.fndt.auth.impl.ldap.LDAPAuthenticationInterface.getConnection(LDAPAuthenticationInterface.java:309)
   at com.xx.cat.fndt.auth.impl.ldap.LDAPAuthenticationInterface.getAuthenticatedConnection(LDAPAuthenticationInterface.java:248)
   at com.xx.cat.fndt.auth.impl.ldap.LDAPAuthenticationInterface.authenticate(LDAPAuthenticationInterface.java:69)
   at com.xx.qoc.svc.qoms.model.service.AdminManagerImpl.authenticateUser(AdminManagerImpl.java:71)
   at com.xx.qoc.svc.qoms.controller.QomsLogn010InptController.onSubmit(QomsLogn010InptController.java:208)
   at org.springframework.web.servlet.mvc.SimpleFormController.processFormSubmission(SimpleFormController.java:267)
   at org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormController.java:250)
   at com.xx.qoc.svc.qoms.controller.QomsLogn010InptController.handleRequestInternal(QomsLogn010InptController.java:160)
   at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
   at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
   at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:857)
   at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:792)
   at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:475)
   at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:440)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at com.xx.qoc.fndt.filter.BlackoutFilter.doFilter(BlackoutFilter.java:257)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at com.xx.qoc.fndt.filter.PropertiesFilter.doFilter(PropertiesFilter.java:178)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at com.xx.qoc.fndt.filter.LoggingFilter.doFilter(LoggingFilter.java:152)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at com.xx.qoc.fndt.filter.RequestHeadersFilter.doFilter(RequestHeadersFilter.java:104)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at com.xx.qoc.fndt.filter.ExceptionHandlerFilter.doFilter(ExceptionHandlerFilter.java:105)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
   at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
   at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
   at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:534)
Caused by: java.security.NoSuchAlgorithmException: Could not create cipher AES/128
   at com.sun.net.ssl.internal.ssl.CipherBox$JCECipherBox.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_h.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.CipherSuite$BulkCipher.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_ax.c(DashoA12275)
   … 63 more
Caused by: java.security.NoSuchAlgorithmException: No implementation for AES/CBC/NoPadding found
   at com.sun.net.ssl.internal.ssl.SunJSSE_i.d(DashoA12275)
   at com.sun.net.ssl.internal.ssl.SunJSSE_i.a(DashoA12275)
   at com.sun.net.ssl.internal.ssl.CipherBox$JCECipherBox.(DashoA12275)
   … 67 more

I checked the java.security and found that all the providers are registered correctly:
security.provider.1=sun.security.provider.Sun
security.provider.2=com.sun.net.ssl.internal.ssl.Provider
security.provider.3=com.sun.rsajca.Provider
security.provider.4=com.sun.crypto.provider.SunJCE
security.provider.5=sun.security.jgss.SunProvider

I did some analysis, when i run the code from a windows batch file, it works but if i run it within Eclipse, it throws this Algorithm not found exception. i checked the JVM version and classpath and it looks okay.

I make a little program to find out whether all the providers are available during runtime or not
Provider[] provs = Security.getProviders();

In result I get only one privider and all other were missing. The jar was not getting loaded in eclipse tomcat during runtime.

For solution, I added following three jar files in tomcat boot classpath and it worked form me and my team members

-rt.jar
-jsse.jar
-jce.jar

Rename log4j.properties

nitingautam — Fri, 07 Aug 2009 06:57:31 +0000

Some time the need arises to have our log4j.properties with different name. By default, if no other configuration is given, log4j will search your classpath for a 'log4j.properties' file.

Now to use your own named log4j property add the following line in your main program:

PropertyConfigurator.configure("File name with path")

exmaple:

PropertyConfigurator.configure("c:\\logs\\my-log4j.properties") this will set this as a default property name and all done =)

GURFL data

admin — Fri, 24 Jul 2009 14:28:49 +0000

GURFL file is a list of operators and their associated IP address ranges. This is a good way to find out from which mobile carrier (ie. which country) does a request come from.

Earlier it was available at:http://www.whirlymobile.com/resources/gurfl/operator.csv

But now days it is down. So I am attaching the last GURFL updated operators.csv file here.

Log4j errors : log4j:WARN No appenders could be found for logger, log4j:WARN Please initialize the log4j system properly

admin — Thu, 23 Jul 2009 09:48:17 +0000

This is a very common problem, it occurs when log4j.properties not found in classpath.

Create a file called log4j.properties. Place it in the root folder where your java classes are found. When log4j initializes, it will look for a file named EXACTLY log4j.properties (if you are using a properties file).

Another alternate way is to put the path to the log4j.properties file in your classpath.

Hope this will help you :)

org.h2.jdbc.JdbcSQLException: The object is already closed [90007-113]

admin — Thu, 16 Jul 2009 12:11:53 +0000

While running junit using in memory database H2 I was hitting this error. I was testing my spring DAO classes that are using JDBCTemplate. In a single Junit testing, to test various scenario I was calling a single DAO method with different parameters . It start giving the error "The object is already closed" as it finishes testing the DAO method with first parameter.

Then I investigated in JDBCTemplate and found that it closes connection after every execution of query using Finally statement.

finally {
            JdbcUtils.closeStatement(stmt);
            DataSourceUtils.releaseConnection(con, getDataSource());
        }

To solve this issue I override the JDBCTemplate and created my own JDBCTemplate in which I have removed the Finally statement.

Javascript: Make independent copy of array using slice() method

admin — Thu, 04 Jun 2009 17:01:56 +0000

Sometime it happens that we need to make copy of an array but in javascript when we assign an array to new it assign it with reference means if you delete anything from new array it will delete it from the main array as well

To create a copy of an array that is independent of another array:
Use the Array object’s slice() method.

For example, the following statements create an array and then use slice() to make an independent copy of the array.

// JavaScript syntax

var oldArray = ["1", "b", "3"];

var newArray = oldArray.slice();

HSQLDB : java.sql.SQLException: Access is denied in statement [SELECT * FROM TBALE]

admin — Tue, 02 Jun 2009 10:01:16 +0000

This error appears when you have not specified required privileges to user in SCRIPT file for running the statements. Use the commands as follows just after user creation grant access as DBA like below:

CREATE USER SA PASSWORD ""
GRANT DBA TO SA

HSQLDB : java.sql.SQLException: User not found: SA

nitingautam — Tue, 02 Jun 2009 09:23:49 +0000

While running HSQLDB in standalone mode you may face the error

java.sql.SQLException: User not found: SA

This is because while creating the DB using script file you are not creating the user

CREATE USER SA PASSWORD ""

The above command you have to include in your db.script file db is your database name) this will creates a user by name SA with blank password.