[JBoss JIRA] Created: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
9:56 p.m.
faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error
when there is no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:32 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
[ http://jira.jboss.com/jira/browse/JBREM-957?page=all ]
Ron Sigal updated JBREM-957:
----------------------------
Fix Version/s: 2.2.2.SP8
Assignee: Ron Sigal
faulty logging:
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is
no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
Assigned To: Ron Sigal
Fix For: 2.2.2.SP8
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:59 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
[ http://jira.jboss.com/jira/browse/JBREM-957?page=comments#action_12416387 ]
Ron Sigal commented on JBREM-957:
---------------------------------
This issue is more or less obsolete as of JBREM-912 "Remove stacktrace when
SSLSocketBuilder.createSSLSocketFactory() fails", since the line
log.error("Error creating SSL Socket Factory for client invoker.", e);
has been changed to
log.warn("Unable to create SSL Socket Factory for client invoker: " +
e.getMessage());
log.debug("Unable to create SSL Socket Factory for client invoker.",
e);
However, I'd like to understand how the lines
SSLSocketBuilder server = new SSLSocketBuilder(configuration);
server.setUseSSLSocketFactory(false);
sf = server.createSSLSocketFactory();
are failing and what "misleading" information is getting logged, Is there
something else that needs to be fixed?
Larry, if you're still watching, can you elaborate?
Thanks.
faulty logging:
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is
no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
Assigned To: Ron Sigal
Fix For: 2.2.2.SP8
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:10 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
[ http://jira.jboss.com/jira/browse/JBREM-957?page=all ]
Ron Sigal closed JBREM-957.
---------------------------
Resolution: Out of Date
Closing this issue as out of date. Will reopen in response to new information.
faulty logging:
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is
no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
Assigned To: Ron Sigal
Fix For: 2.2.2.SP8
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:38 a.m.
New subject: [JBoss JIRA] Reopened: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
[ http://jira.jboss.com/jira/browse/JBREM-957?page=all ]
Ron Sigal reopened JBREM-957:
-----------------------------
faulty logging:
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is
no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
Assigned To: Ron Sigal
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:38 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
[ http://jira.jboss.com/jira/browse/JBREM-957?page=all ]
Ron Sigal updated JBREM-957:
----------------------------
Fix Version/s: (was: 2.2.2.SP8)
Changed fix version to unknown.
faulty logging:
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is
no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
Assigned To: Ron Sigal
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:38 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-957) faulty logging: ...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is no error
[ http://jira.jboss.com/jira/browse/JBREM-957?page=all ]
Ron Sigal closed JBREM-957.
---------------------------
Resolution: Out of Date
faulty logging:
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory logs an error when there is
no error
-----------------------------------------------------------------------------------------------------------------
Key: JBREM-957
URL: http://jira.jboss.com/jira/browse/JBREM-957
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: 2.2.0.GA as included in JBoss-4.2.2.GA
Reporter: Larry Talley
Assigned To: Ron Sigal
When used in client mode
...transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:140)
logs an error, but then proceeds to work fine (because sf already has a valid value due to
line 129). The misreported error spews misleading information in the log. I suggest that
line 144 shouldn't be at ERROR level if the IOException isn't always an error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5785
days inactive
5867
days old
jboss-remoting-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Larry Talley (JIRA) -
Ron Sigal (JIRA)