[JBoss JIRA] Created: (JBREM-825) Verify that CoyoteInvoker works with Apache Portable Runtime
by Ron Sigal (JIRA)
Verify that CoyoteInvoker works with Apache Portable Runtime
------------------------------------------------------------
Key: JBREM-825
URL: http://jira.jboss.com/jira/browse/JBREM-825
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Trustin Lee
The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars. When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:
21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
at org.jboss.remoting.Client.invoke(Client.java:1632)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
... 31 more
--
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
16 years, 2 months
[JBoss JIRA] Created: (JBAS-5274) Default log4j conversion pattern should log Thread name
by Galder Zamarreno (JIRA)
Default log4j conversion pattern should log Thread name
-------------------------------------------------------
Key: JBAS-5274
URL: http://jira.jboss.com/jira/browse/JBAS-5274
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Logging
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: JBossAS-5.0.0.CR1
>From a support point of view, I often find myself asking users/customers to enable the
full conversion pattern in the server.log's log4j appender in order to get a better idea of
what each thread is doing.
I suggest that we add %t to the default conversion pattern to to speed up problem resolution.
The server.log is already verbose enough and few of our users/customers understand it, so
I wouldn't expect such change to have a major impact on our users/customers:
<!-- The default pattern: Date Priority [Category] (Thread) Message\n -->
<param name="ConversionPattern" value="%d %-5p [%c] (%t) %m%n"/>
--
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
16 years, 2 months