[JBoss JIRA] (JBTM-2613) BABridgedTest failure (caused by WebServiceException: Could not send Message)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2613?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2613:
--------------------------------
Fix Version/s: 5.next
> BABridgedTest failure (caused by WebServiceException: Could not send Message)
> -----------------------------------------------------------------------------
>
> Key: JBTM-2613
> URL: https://issues.jboss.org/browse/JBTM-2613
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: TxBridge
> Affects Versions: 5.2.12.Final
> Reporter: Michael Musgrove
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
> Attachments: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.txt
>
>
> job number was: http://172.17.130.4:8083/job/narayana-dualstack/80
> -------------------------------------------------------------------------------
> Test set: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.917 sec <<< FAILURE!
> testClose(org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest) Time elapsed: 60.65 sec <<< ERROR!
> javax.xml.ws.WebServiceException: Could not send Message.
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> at java.net.SocketInputStream.read(SocketInputStream.java:170)
> at java.net.SocketInputStream.read(SocketInputStream.java:141)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651)
> at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
> at com.sun.proxy.$Proxy169.reset(Unknown Source)
> at org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.teardownTest(BABridgedTest.java:97)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (JBTM-2616) Implement JMS integration classes
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2616?page=com.atlassian.jira.plugin.... ]
Work on JBTM-2616 started by Gytis Trikleris.
---------------------------------------------
> Implement JMS integration classes
> ---------------------------------
>
> Key: JBTM-2616
> URL: https://issues.jboss.org/browse/JBTM-2616
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: JTA
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> Both Spring and Spring Boot requires ConnectionFactory, Connection, Session implementation which should handle the transaction related tasks when using JMS e.g. enlisting xa resources, registering synchronizations etc.
> This should be somethings similar to the ConnectionManager and ConnectionImple used by the transactional driver.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (JBTM-2616) Implement JMS integration classes
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-2616:
-------------------------------------
Summary: Implement JMS integration classes
Key: JBTM-2616
URL: https://issues.jboss.org/browse/JBTM-2616
Project: JBoss Transaction Manager
Issue Type: Sub-task
Components: JTA
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.next
Both Spring and Spring Boot requires ConnectionFactory, Connection, Session implementation which should handle the transaction related tasks when using JMS e.g. enlisting xa resources, registering synchronizations etc.
This should be somethings similar to the ConnectionManager and ConnectionImple used by the transactional driver.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2234:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.13.Final)
> out of memory when logging more messages than heap size (surefire issue)
> ------------------------------------------------------------------------
>
> Key: JBTM-2234
> URL: https://issues.jboss.org/browse/JBTM-2234
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Performance Testing
> Affects Versions: 5.0.2
> Environment: JTS testing
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished.
> In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1804:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.13.Final)
> JTS remote tests not run and no code coverage
> ---------------------------------------------
>
> Key: JBTM-1804
> URL: https://issues.jboss.org/browse/JBTM-1804
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: JTS, Testing
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build.
> It would then be beneficial to have them instrumented by emma to get code coverage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months