Log messages are not written in the log file - java

I have configured a project with Log4j. I have configured log4j using log4.properties file.
While the test runs it creates the myLog.log file but nothing is written to the log file.
Appender we are using as RollingFileAppender and log4j.rootLogger=DEBUG.
Can any one suggest what might be causing this problem?
Here is log4j.properties for the project.
log4j.rootLogger= DEBUG, ConsoleAppender, Rolling
log4j.appender.ConsoleAppender=org.apache.log4j.ConsoleAppender
log4j.appender.ConsoleAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.ConsoleAppender.layout.ConversionPattern=%d %-2p %c.%M(): %m%n
log4j.appender.Rolling=org.apache.log4j.RollingFileAppender
log4j.appender.Rolling.MaxFileSize=5MB
log4j.appender.Rolling.MaxBackupIndex=2
log4j.appender.Rolling.File=D:\Logs\myProj.log
log4j.appender.Rolling.layout = org.apache.log4j.PatternLayout
log4j.appender.Rolling.layout.ConversionPattern=%d %-4p %c.%M(): %m%n
## Following two lines have been removed now.
log4j.logger.com=WARN
log4j.logger.org=WARN
Received Log in the log file :
2012-01-16 22:02:08,534 DEBUG org.apache.http.headers.receiveResponseHeader(): << content-type: application/json; charset=UTF-8
2012-01-16 22:02:08,534 DEBUG org.apache.http.headers.receiveResponseHeader(): << connection: close
2012-01-16 22:02:08,534 DEBUG org.apache.http.headers.receiveResponseHeader(): << content-length: 236
2012-01-16 22:02:08,550 DEBUG org.apache.http.headers.receiveResponseHeader(): << server: httpd.js
2012-01-16 22:02:08,550 DEBUG org.apache.http.headers.receiveResponseHeader(): << date: Tue, 17 Jan 2012 03:02:06 GMT
2012-01-16 22:02:08,566 DEBUG org.apache.http.wire.wire(): << "{"name":"clickElement","sessionId":"2fad55cf-670e-44f3-ab60-7d2f76f641e6","status":0,"value":"This action is final and cannot be undone?"}"
2012-01-16 22:02:08,566 DEBUG org.apache.http.impl.conn.DefaultClientConnection.shutdown(): Connection shut down
2012-01-16 22:02:08,566 DEBUG org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager.releaseConnection(): Released connection is not reusable.
2012-01-16 22:02:08,566 DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute.freeEntry(): Releasing connection [HttpRoute[{}->http://127.0.0.1:7055]][null]
2012-01-16 22:02:08,566 DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute.notifyWaitingThread(): Notifying no-one, there are no waiting threads
2012-01-16 22:02:10,566 DEBUG org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager.getConnection(): Get connection: HttpRoute[{}->http://127.0.0.1:7055], timeout = 120000
2012-01-16 22:02:10,566 DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute.getEntryBlocking(): [HttpRoute[{}->http://127.0.0.1:7055]] total kept alive: 0, total issued: 0, total allocated: 0 out of 2000
2012-01-16 22:02:10,566 DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute.getFreeEntry(): No free connections [HttpRoute[{}->http://127.0.0.1:7055]][null]
2012-01-16 22:02:10,566 DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute.getEntryBlocking(): Available capacity: 2000 out of 2000 [HttpRoute[{}->http://127.0.0.1:7055]][null]
2012-01-16 22:02:10,581 DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute.createEntry(): Creating new connection [HttpRoute[{}->http://127.0.0.1:7055]]
2012-01-16 22:02:10,597 DEBUG org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(): Connecting to 127.0.0.1:7055
2012-01-16 22:02:10,597 DEBUG org.apache.http.client.protocol.RequestAddCookies.process(): CookieSpec selected: best-match
2012-01-16 22:02:10,597 DEBUG org.apache.http.client.protocol.RequestAuthCache.process(): Auth cache not set in the context
2012-01-16 22:02:10,597 DEBUG org.apache.http.impl.client.DefaultHttpClient.tryExecute(): Attempt 1 to execute request
2012-01-16 22:02:10,597 DEBUG org.apache.http.impl.conn.DefaultClientConnection.sendRequestHeader(): Sending request: GET /hub/session/2fad55cf-670e-44f3-ab60-7d2f76f641e6/alert_text HTTP/1.1
2012-01-16 22:02:10,597 DEBUG org.apache.http.wire.wire(): >> "GET /hub/session/2fad55cf-670e-44f3-ab60-7d2f76f641e6/alert_text HTTP/1.1[\r][\n]"
2012-01-16 22:02:10,597 DEBUG org.apache.http.wire.wire(): >> "Accept: application/json, image/png[\r][\n]"
2012-01-16 22:02:10,597 DEBUG org.apache.http.wire.wire(): >> "Host: 127.0.0.1:7055[\r][\n]"
2012-01-16 22:02:10,597 DEBUG org.apache.http.wire.wire(): >> "Connection: Keep-Alive[\r][\n]"
2012-01-16 22:02:10,597 DEBUG org.apache.http.wire.wire(): >> "[\r][\n]"
2012-01-16 22:02:10,597 DEBUG org.apache.http.headers.sendRequestHeader(): >> GET /hub/session/2fad55cf-670e-44f3-ab60-7d2f76f641e6/alert_text HTTP/1.1
2012-01-16 22:02:10,597 DEBUG org.apache.http.headers.sendRequestHeader(): >> Accept: application/json, image/png
2012-01-16 22:02:10,597 DEBUG org.apache.http.headers.sendRequestHeader(): >> Host: 127.0.0.1:7055
2012-01-16 22:02:10,597 DEBUG org.apache.http.headers.sendRequestHeader(): >> Connection: Keep-Alive
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "HTTP/1.1 200 OK[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "content-type: application/json; charset=UTF-8[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "connection: close[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "content-length: 236[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "server: httpd.js[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "date: Tue, 17 Jan 2012 03:02:10 GMT[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.wire.wire(): << "[\r][\n]"
2012-01-16 22:02:10,612 DEBUG org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(): Receiving response: HTTP/1.1 200 OK

First of all, make sure your log4j.properties is loaded in classpath. I assume that the file can also be found inside the WEB-INF/classes directory if it is a webapp. But because you say that the file is getting created, I think that is not a problem.
So, try with this
log4j.rootLogger= DEBUG, Console, Rolling
log4j.appender.Console=org.apache.log4j.ConsoleAppender
log4j.appender.Console.layout=org.apache.log4j.PatternLayout
log4j.appender.Console.layout.ConversionPattern=%d %-2p %c.%M(): %m%n
log4j.appender.Rolling=org.apache.log4j.RollingFileAppender
log4j.appender.Rolling.MaxFileSize=5MB
log4j.appender.Rolling.MaxBackupIndex=2
log4j.appender.Rolling.File=D:\Logs\myProj.log
log4j.appender.Rolling.layout = org.apache.log4j.PatternLayout
log4j.appender.Rolling.layout.ConversionPattern=%d %-4p %c.%M(): %m%n
Note that I have removed the last two lines.
Basically, those lines set the log level to WARN to all packages starting with com and org. So, unless you have any WARN messages being logged, you won't see anything at all on the log files.
You can experiment with levels by doing something like
log4j.logger.com.foo.bar=DEBUG
log4j.logger.com.foo.bar.MyClass=TRACE
The above will print log all com.foo.bar logs in DEBUG whereas will print com.foo.bar.MyClass logs in the TRACE level.

Or more detailed: No logging-request from com or org-packages with log-level < WARN will be enabled. So it wont be forwarded to your rootLogger.
Quote:
A log request of level p in a logger with (either assigned or inherited, whichever is
appropriate) level q, is enabled if p >= q.
and
Each enabled logging request for a given logger will be forwarded to all the appenders in
that logger as well as the appenders higher in the hierarchy.
See: http://logging.apache.org/log4j/1.2/manual.html

Related

How make feign raw http request/response logging?

I have enabled feign logging andgot some thing like that:
15:27:15.420 [ForkJoinPool-1-worker-229] DEBUG feign.Logger - [UserEndpoint#postUser] Authorization: Bearer test
15:27:15.420 [ForkJoinPool-1-worker-229] DEBUG feign.Logger - [UserEndpoint#postUser] Content-Length: 19
15:27:15.420 [ForkJoinPool-1-worker-229] DEBUG feign.Logger - [UserEndpoint#postUser] Content-Type: application/json
15:27:15.420 [ForkJoinPool-1-worker-229] DEBUG feign.Logger - [UserEndpoint#postUser]
15:27:15.420 [ForkJoinPool-1-worker-229] DEBUG feign.Logger - [UserEndpoint#postUser] {"attributes":null}
15:27:15.420 [ForkJoinPool-1-worker-229] DEBUG feign.Logger - [UserEndpoint#postUser] ---> END HTTP (19-byte body)
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById] <--- HTTP/1.1 500 Internal Server Error (1223ms)
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById] apigw-requestid: RpKPuhaFPHcESkA=
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById] connection: keep-alive
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById] content-length: 35
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById] content-type: application/json
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById] date: Thu, 05 May 2022 08:27:16 GMT
15:27:16.585 [ForkJoinPool-1-worker-117] DEBUG feign.Logger - [UserEndpoint#getUserById]
Ishtere a way to output like that:
GET https://myhost/api/users/eac92ab2-682b-45d9-8aa2-435f933b2661
Authorization: mytoken
E.g. one request - one piece of output in one place (not line by header)
Ideally there request and response should be output tohether, idealy in single line with escaped line breaks
Isit possible with feign?

REST-assured JSON output

I am trying to retrieve a JSON file, but it doesn't seem to be a JSON file, but it outputs application/json
12:39:39.403[main] DEBUG org.apache.http.wire - << "[0xb9][0x12][0x3d][0xr4][0xu6][0x43][0xd9][0x12][0xw3][0x43][0xb6][0x1q][0xef][0x13]"
12:39:39.403[main] DEBUG org.apache.http.wire - << "[0xwq][0xq2][0x9d][0x14][0xk6][0xw3][0x9q][0xz2][0xm3][0x4m][0xq6][0xkq][0xlf][0xq3]"
12:39:39.403[main] DEBUG org.apache.http.wire - << "30[\r][\n]"
12:39:39.403[main] DEBUG org.apache.http.wire - << "[0xb9][0x12][0x3d][0xr4][0xu6][0x43][0x9][0x12][0xw3][0x43][0xb6][0x1q][0xef][0x13]"
My rest assured code is
Response response = given().contentType(ContentType.JSON).auth().get("https://sample-url");
I would I like to see an actual JSON output

AWS PutObject Connection reset

My AWS Java Client is throwing
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Connection reset
at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541) ~[na:1.8.0_60]
at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553) ~[na:1.8.0_60]
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71) ~[na:1.8.0_60]
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:159) ~[httpcore-4.3.3.jar:4.3.3]
My code is
public void save(String name, byte[] file) {
ObjectMetadata metaData = new ObjectMetadata();
String streamMD5 = new String(Base64.encodeBase64(file));
metaData.setContentMD5(streamMD5);
metaData.setContentLength(file.length);
InputStream stream = new ByteArrayInputStream(file);
try {
PutObjectRequest put = new PutObjectRequest(
configuration.getBucketName(), name, stream, metaData);
s3client.putObject(put);
} finally {
IOUtils.closeQuietly(stream);
}
}
The s3client is a spring bean and is not garbage collected before the stream has finished uploading. I've tried without specifying MD5 and/or content length but still has the same exception thrown.
Logging through AWS library shows:
10:09:15.540 [http-nio-8080-exec-1] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
10:09:15.540 [http-nio-8080-exec-1] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context
10:09:15.540 [http-nio-8080-exec-1] DEBUG o.a.h.c.p.RequestProxyAuthentication - Proxy auth state: UNCHALLENGED
10:09:15.540 [http-nio-8080-exec-1] DEBUG c.a.http.impl.client.SdkHttpClient - Attempt 1 to execute request
10:09:15.540 [http-nio-8080-exec-1] DEBUG o.a.h.i.conn.DefaultClientConnection - Sending request: PUT /documeent.pdf HTTP/1.1
10:09:15.540 [http-nio-8080-exec-1] DEBUG org.apache.http.wire - >> "PUT /document.pdf HTTP/1.1[\r][\n]"
10:09:15.540 [http-nio-8080-exec-1] DEBUG org.apache.http.wire - >> "Host: bucket.s3.amazonaws.com[\r][\n]"
10:09:15.540 [http-nio-8080-exec-1] DEBUG org.apache.http.wire - >> "Authorization: AWS 123445667788=[\r][\n]"
10:09:15.540 [http-nio-8080-exec-1] DEBUG org.apache.http.wire - >> "User-Agent: aws-sdk-java/1.10.21 Linux/3.13.0-65-generic Java_HotSpot(TM)_Server_VM/25.60-b23/1.8.0_60[\r][\n]"
10:09:15.540 [http-nio-8080-exec-1] DEBUG org.apache.http.wire - >> "Date: Tue, 06 Oct 2015 09:09:15 GMT[\r][\n]"
10:09:15.663 [http-nio-8080-exec-1] DEBUG com.amazonaws.internal.SdkSSLSocket - closing bucket.s3.amazonaws.com/12.34.56.78:443
10:09:15.665 [http-nio-8080-exec-1] DEBUG o.a.h.i.conn.DefaultClientConnection - I/O error closing connection
I've checked that the file size (3.2M) does not exceed the max file siez for this bucket.
Get/List requests work fine and I can copy files into the S3 bucket using the s3 client tools.
Does anyone know of anything else I should check?
Thanks.

How to stop Logback logging exceptions with a time prefix on each line?

This is the Logback stacktrace of an exception:
15:32:04.773 [localhost:9080] [UNKNOWN] [Unauthenticated] [0AE48E3EEF47ED3210CC45C3E20D273D] DEBUG org.apache.http.wire - http-outgoing-4 << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
15:32:04.773 [localhost:9080] [UNKNOWN] [Unauthenticated] [0AE48E3EEF47ED3210CC45C3E20D273D] DEBUG org.apache.http.wire - http-outgoing-4 << "[\r][\n]"
15:32:04.773 [localhost:9080] [UNKNOWN] [Unauthenticated] [0AE48E3EEF47ED3210CC45C3E20D273D] DEBUG org.apache.http.wire - http-outgoing-4 << "10e[\r][\n]"
15:32:04.773 [localhost:9080] [UNKNOWN] [Unauthenticated] [0AE48E3EEF47ED3210CC45C3E20D273D] DEBUG org.apache.http.wire - http-outgoing-4 << "<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Body><env:Fault><env:Code><env:Value>env:Sender</env:Value></env:Code><env:Reason><env:Text xml:lang="en-US">Internal Error (from client)</env:Text></env:Reason></env:Fault></env:Body></env:Envelope>[\r][\n]"
15:32:04.773 [localhost:9080] [UNKNOWN] [Unauthenticated] [0AE48E3EEF47ED3210CC45C3E20D273D] DEBUG org.apache.http.wire - http-outgoing-4 << "0[\r][\n]"
My question is: How to stop Logback logging exceptions with a time prefix on each line? Is it a xml change or a change to the Java code?
EDIT: Clarification
I'm happy with the time prefix in general. The issue here is that some information is coming back and it is being split across multiple lines, and each line is prefixed with the time, which makes interpreting the original information even harder. What I want is the time on the first line, and the rest of the stack trace on the remaining lines.
This is the error I'm trying to see:
<env:Text xml:lang="en-US">Internal Error (from client)</env:Text>

Authenticating with OpenID is failing in Java

I am trying to create a small application that uses OpenID4Java for openId auth.
I am able to successfully redirect user to OpenID provider site to login, but on returning to URL its verification fails.
Method that process response from openID Provider is,
public HashMap<String, String> verifyResponse(HttpServletRequest httpReq){
HashMap<String, String> values = new HashMap<String, String>();
try{
ParameterList response = new ParameterList(httpReq.getParameterMap());
// retrieve the previously stored discovery information
DiscoveryInformation discovered = (DiscoveryInformation)httpReq.getSession().getAttribute("openid-disc");
// extract the receiving URL from the HTTP request
StringBuffer receivingURL = httpReq.getRequestURL();
String queryString = httpReq.getQueryString();
if (queryString != null && queryString.length() > 0)
receivingURL.append("?").append(httpReq.getQueryString());
// verify the response; ConsumerManager needs to be the same
// (static) instance used to place the authentication request
VerificationResult verification = manager.verify(receivingURL.toString(), response, discovered);
// examine the verification result and extract the verified identifier
Identifier verified = verification.getVerifiedId();
if (verified != null){
AuthSuccess authSuccess = (AuthSuccess) verification.getAuthResponse();
if (authSuccess.hasExtension(AxMessage.OPENID_NS_AX)){
FetchResponse fetchResp = (FetchResponse) authSuccess.getExtension(AxMessage.OPENID_NS_AX);
values.put("GUID", (String)fetchResp.getAttributeValues("GUID").get(0));
values.put("Email", (String)fetchResp.getAttributeValues("Email").get(0));
values.put("FirstName", (String)fetchResp.getAttributeValues("FirstName").get(0));
values.put("LastName", (String)fetchResp.getAttributeValues("LastName").get(0));
values.put("Gender", (String)fetchResp.getAttributeValues("Gender").get(0));
values.put("Country", (String)fetchResp.getAttributeValues("Country").get(0));
values.put("Company", (String)fetchResp.getAttributeValues("Company").get(0));
values.put("VerifiedUserId", verified.getIdentifier());
values.put("Verified", verified.toString());
}
return values; // success
}else{
values.put("VerifiedUserId", "nun");
// values.put("Verified", verified.toString());
return values; // success
}
}
catch (OpenIDException e){
// present error to the user
}
return null;
}
on returning, following failure messages are there in console.
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Set-Cookie: ephemeral_session_id=56f872bb71a5f4feae404d3f391f9d51833d50b51c13ddbcdac6a1fc058e5269; domain=myopenid.com; path=/
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Set-Cookie: ephemeral_session_id=56f872bb71a5f4feae404d3f391f9d51833d50b51c13ddbcdac6a1fc058e5269; domain=myopenid.com; path=/
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Set-Cookie: browser_id=5e3bfb0c08da19a59e8445e624637c261aee10e65a6b672ed642cb9201e5d8e4; domain=myopenid.com; path=/; expires=Sat, 16-Mar-2013 21:40:09 GMT
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Set-Cookie: browser_id=5e3bfb0c08da19a59e8445e624637c261aee10e65a6b672ed642cb9201e5d8e4; domain=myopenid.com; path=/; expires=Sat, 16-Mar-2013 21:40:09 GMT
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Set-Cookie: session_id=8aef51436d464910daaa1ef8eb5c661e6fa45c134c0969a1f7048ef5f23707c6; domain=myopenid.com; path=/; expires=Sat, 16-Mar-2013 21:40:09 GMT
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Set-Cookie: session_id=8aef51436d464910daaa1ef8eb5c661e6fa45c134c0969a1f7048ef5f23707c6; domain=myopenid.com; path=/; expires=Sat, 16-Mar-2013 21:40:09 GMT
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Connection: close
31573 [http-bio-8080-exec-9] DEBUG org.apache.http.headers - << Connection: close
31574 [http-bio-8080-exec-9] DEBUG org.apache.http.client.protocol.ResponseProcessCookies - Cookie accepted: "[version: 0][name: ephemeral_session_id][value: 56f872bb71a5f4feae404d3f391f9d51833d50b51c13ddbcdac6a1fc058e5269][domain: myopenid.com][path: /][expiry: null]".
31574 [http-bio-8080-exec-9] DEBUG org.apache.http.client.protocol.ResponseProcessCookies - Cookie accepted: "[version: 0][name: ephemeral_session_id][value: 56f872bb71a5f4feae404d3f391f9d51833d50b51c13ddbcdac6a1fc058e5269][domain: myopenid.com][path: /][expiry: null]".
31574 [http-bio-8080-exec-9] DEBUG org.apache.http.client.protocol.ResponseProcessCookies - Cookie accepted: "[version: 0][name: browser_id][value: 5e3bfb0c08da19a59e8445e624637c261aee10e65a6b672ed642cb9201e5d8e4][domain: myopenid.com][path: /][expiry: Sun Mar 17 02:40:09 PKT 2013]".
31574 [http-bio-8080-exec-9] DEBUG org.apache.http.client.protocol.ResponseProcessCookies - Cookie accepted: "[version: 0][name: browser_id][value: 5e3bfb0c08da19a59e8445e624637c261aee10e65a6b672ed642cb9201e5d8e4][domain: myopenid.com][path: /][expiry: Sun Mar 17 02:40:09 PKT 2013]".
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.client.protocol.ResponseProcessCookies - Cookie accepted: "[version: 0][name: session_id][value: 8aef51436d464910daaa1ef8eb5c661e6fa45c134c0969a1f7048ef5f23707c6][domain: myopenid.com][path: /][expiry: Sun Mar 17 02:40:09 PKT 2013]".
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.client.protocol.ResponseProcessCookies - Cookie accepted: "[version: 0][name: session_id][value: 8aef51436d464910daaa1ef8eb5c661e6fa45c134c0969a1f7048ef5f23707c6][domain: myopenid.com][path: /][expiry: Sun Mar 17 02:40:09 PKT 2013]".
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.client.ClientParamsStack - 'http.protocol.handle-redirects': false
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.client.ClientParamsStack - 'http.protocol.handle-redirects': false
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.wire - << "is_valid:false[\n]"
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.wire - << "is_valid:false[\n]"
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.wire - << "ns:http://specs.openid.net/auth/2.0[\n]"
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.wire - << "ns:http://specs.openid.net/auth/2.0[\n]"
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.DefaultClientConnection - Connection shut down
31575 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.DefaultClientConnection - Connection shut down
31576 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager - Released connection is not reusable.
31576 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager - Released connection is not reusable.
31576 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute - Releasing connection [HttpRoute[{}->http://www.myopenid.com]][null]
31576 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute - Releasing connection [HttpRoute[{}->http://www.myopenid.com]][null]
31576 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute - Notifying no-one, there are no waiting threads
31576 [http-bio-8080-exec-9] DEBUG org.apache.http.impl.conn.tsccm.ConnPoolByRoute - Notifying no-one, there are no waiting threads
31576 [http-bio-8080-exec-9] DEBUG org.openid4java.util.HttpCache - Read 51 bytes.
31576 [http-bio-8080-exec-9] DEBUG org.openid4java.util.HttpCache - Read 51 bytes.
31576 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Creating parameter list from key-value form:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31576 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Creating parameter list from key-value form:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31576 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Created empty parameter list.
31576 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Created empty parameter list.
31581 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Copying parameter list:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31581 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Copying parameter list:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31581 [http-bio-8080-exec-9] DEBUG org.openid4java.consumer.ConsumerManager - Retrived response:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31581 [http-bio-8080-exec-9] DEBUG org.openid4java.consumer.ConsumerManager - Retrived response:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31582 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Created empty parameter list.
31582 [http-bio-8080-exec-9] DEBUG org.openid4java.message.ParameterList - Created empty parameter list.
31582 [http-bio-8080-exec-9] DEBUG org.openid4java.message.VerifyResponse - Created verification response:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31582 [http-bio-8080-exec-9] DEBUG org.openid4java.message.VerifyResponse - Created verification response:
is_valid:false
ns:http://specs.openid.net/auth/2.0
31582 [http-bio-8080-exec-9] DEBUG org.openid4java.consumer.ConsumerManager - Direct signature verification failed with OP: http://www.myopenid.com/server
31582 [http-bio-8080-exec-9] DEBUG org.openid4java.consumer.ConsumerManager - Direct signature verification failed with OP: http://www.myopenid.com/server
31582 [http-bio-8080-exec-9] ERROR org.openid4java.consumer.ConsumerManager - Verification failed for: http://aaaqif.myopenid.com/ reason: Direct signature verification failed.
31582 [http-bio-8080-exec-9] ERROR org.openid4java.consumer.ConsumerManager - Verification failed for: http://aaaqif.myopenid.com/ reason: Direct signature verification failed.

Categories

Resources