October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5595) Support custom transaction isolation levels

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-5595: ------------------------------------ Summary: Support custom transaction isolation levels Key: AS7-5595 URL: https://issues.jboss.org/browse/AS7-5595 Project: Application Server 7 Issue Type: Task Components: JCA Affects Versions: 7.1.3.Final (EAP) Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-3524) HostControllerConnectionService connection timeout is not configurable

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3524: ------------------------------------- Summary: HostControllerConnectionService connection timeout is not configurable Key: AS7-3524 URL: https://issues.jboss.org/browse/AS7-3524 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Jason Greene I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. HostControllerConnectionService.java: ... ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); configuration.setEndpoint(endpointInjector.getValue()); configuration.setConnectionTimeout(15000); configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); client = ProtocolChannelClient.create(configuration); ... Exception I am getting: [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
9
0 / 0

[JBoss JIRA] (JBAS-9507) ThreadLocal variables are not cleared at the end of execution of the thread.

by Mohamad ABBAS (JIRA)

Mohamad ABBAS created JBAS-9507: ----------------------------------- Summary: ThreadLocal variables are not cleared at the end of execution of the thread. Key: JBAS-9507 URL: https://issues.jboss.org/browse/JBAS-9507 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.1.0.GA Environment: windows 7 Reporter: Mohamad ABBAS I am deploying a web application under Jboss AS 5.1.0.GA and in my application, I'm using some "java.lang.Threadlocal" and "java.lang.InheritableThreadLocal" variables. Threadlocal variables should be cleared at the end of execution of the thread. In my case , since jboss is using a thread pool, the threadlocal variables are not cleared. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
4
0 / 0

[JBoss JIRA] (AS7-2177) TS: Check logging

by Ondrej Zizka (Created) (JIRA)

TS: Check logging ----------------- Key: AS7-2177 URL: https://issues.jboss.org/browse/AS7-2177 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Some tests print to System.out, and also ex.printStackTrace(). Turn it to proper logging. Also check logging config. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-5815) Upgrading JBossTS to 4.17.2.Final

by Paul Robinson (JIRA)

Paul Robinson created AS7-5815: ---------------------------------- Summary: Upgrading JBossTS to 4.17.2.Final Key: AS7-5815 URL: https://issues.jboss.org/browse/AS7-5815 Project: Application Server 7 Issue Type: Component Upgrade Components: Transactions Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 7.2.0.Alpha1 Note: this upgrade is for 7.2 branch, not the 7.1 branch. 7.1 branch must stay on JBossTS 4.16.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
2
0 / 0

[JBoss JIRA] (AS7-3830) Remote JNDI call does not bind stateful beans

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3830: ------------------------------------- Summary: Remote JNDI call does not bind stateful beans Key: AS7-3830 URL: https://issues.jboss.org/browse/AS7-3830 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Reporter: Ondřej Chaloupka Assignee: jaikiran pai It seems that current ejb remote client is not able to find stateful bean. Exception is thrown instead: {code} javax.naming.NamingException: java.lang.IllegalStateException: No EJB client context is available [Root exception is java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:124) at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:70) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:91) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133) ... 7 more Caused by: java.lang.IllegalStateException: No EJB client context is available at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:233) at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:160) at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:89) ... 8 more {code} Please, check my test whether definition of remote context does not contain a mistake. But finding singleton and stateless beans works fine. https://github.com/ochaloup/jboss-as/blob/ejb-remote-call/testsuite/integ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
5
0 / 0

[JBoss JIRA] (AS7-3907) Upgrade Infinispan to 5.1.2.FINAL

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3907: --------------------------------- Summary: Upgrade Infinispan to 5.1.2.FINAL Key: AS7-3907 URL: https://issues.jboss.org/browse/AS7-3907 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-3943) Upgrade JGroups to 3.0.6.Final

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3943: --------------------------------- Summary: Upgrade JGroups to 3.0.6.Final Key: AS7-3943 URL: https://issues.jboss.org/browse/AS7-3943 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-3916) Concurrent access leads to empty domain.xml

by Heiko Braun (JIRA)

Heiko Braun created AS7-3916: -------------------------------- Summary: Concurrent access leads to empty domain.xml Key: AS7-3916 URL: https://issues.jboss.org/browse/AS7-3916 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.1.Final Hi Red Hat team. We're still trying to narrow down the trigger but there is a very serious bug when using the admin console in AS 7.1 Final that causes the domain.xml file to be wiped of everything other than the extensions section that is at the top. Have not checked yet if this is a known bug or not but wanted to alert you immediately. The potential trigger for this is more than one person using the admin console at the same time. Even if just for monitoring while the other person is making configuration changes. (Fortunately we had backed up the config using the CLI.) We are trying right now to get our QA1 drop out the door but we'll be giving this a closer look tomorrow. Has anyone else reported this though? Thanks, Bill -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
8
0 / 0

[JBoss JIRA] (AS7-3828) EJB client tries to invoke EJBs after application was undeployed

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3828: ----------------------------------- Summary: EJB client tries to invoke EJBs after application was undeployed Key: AS7-3828 URL: https://issues.jboss.org/browse/AS7-3828 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: jaikiran pai Priority: Critical Fix For: 7.1.1.Final And this results in NoSuchEJBException. One more feature that was fully supported in previous version (AS 5.1). {noformat} 2012/02/20 10:59:11:336 EST [WARN ][Runner - 43] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 43.> org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 43. at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:79) at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) at java.lang.Thread.run(Thread.java:662) Caused by: javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatefulSBImpl] at org.jboss.ejb.client.remoting.GeneralInvocationFailureResponseHandler.processMessage(GeneralInvocationFailureResponseHandler.java:75) at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:385) at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:371) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) ... 1 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2012