May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-806) Using UnmodifiableLinkedHashMap constructor causes an UnsupportedOperationException exception to be thrown on IBM JDK

by Dustin Kut Moy Cheung (JIRA)

Using UnmodifiableLinkedHashMap constructor causes an UnsupportedOperationException exception to be thrown on IBM JDK --------------------------------------------------------------------------------------------------------------------- Key: JBAOP-806 URL: https://issues.jboss.org/browse/JBAOP-806 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Components: Aspect Library Environment: OS: Fedora 14 JDK: IBM JDK Reporter: Dustin Kut Moy Cheung Priority: Critical Read Summary. This error is caused because the IBM JDK LinkedHashMap invokes the putAll method on HashMap. Since the putAll method is overwridden in UnmodifiableLinkedHashMap.java, the UnmodifiableLinkedHashMap putAll method is called instead of the HashMap constructor and therefore throws that exception. The fix is to change the signature of the constructor being called (LinkedHashMap constructor) so that the putAll method is not called. Please see the patch that attempts to solve this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
6
0 / 0

[JBoss JIRA] (AS7-2476) Allow to choose CXF as jax-rs provider instead of Resteasy

by Luciano Blasetti (Created) (JIRA)

Allow to choose CXF as jax-rs provider instead of Resteasy ---------------------------------------------------------- Key: AS7-2476 URL: https://issues.jboss.org/browse/AS7-2476 Project: Application Server 7 Issue Type: Feature Request Components: REST, Web Services Affects Versions: 7.0.2.Final Reporter: Luciano Blasetti Assignee: Stuart Douglas Since Apache CXF provides a very good support for jax-rs and it is the mechanism for providing jax-ws in AS7, it does make sense to adopt it also for jax-rs services (it would be a more homogeneous solution), at least giving the chance to choice between the resteasy and cxf implementation through a configuration option. -- 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

13 years, 4 months

8
7
0 / 0

[JBoss JIRA] Created: (AS7-1519) Simple Domain Management Role Based Permissions

by Darran Lofthouse (JIRA)

Simple Domain Management Role Based Permissions ----------------------------------------------- Key: AS7-1519 URL: https://issues.jboss.org/browse/AS7-1519 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Affects Versions: 7.0.0.Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta2 Implement some coarse permissions for domain operations. Possibly allowing a break down for subsystem, profile, server, server-group - maybe read - write - execute. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2033) EjbReferenceResolver can't resolve service bean references

by Carlo de Wolf (JIRA)

EjbReferenceResolver can't resolve service bean references ---------------------------------------------------------- Key: EJBTHREE-2033 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2033 Project: EJB 3.0 Issue Type: Bug Components: common Affects Versions: 1.1.22 Reporter: Carlo de Wolf Assignee: Carlo de Wolf org.jboss.ejb3.common.resolvers.spi.UnresolvableReferenceException: Could not resolve reference [EJB Reference: beanInterface 'org.jboss.ejb3.test.interceptors2.StatusRemote', beanName '', mappedName 'null'] in AbstractVFSDeploymentContext@790495753{file:///home/carlo/work/ejb3/testsuite/target/test-lib/interceptors2-test.jar} at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.resolveEjb(ScopedEJBReferenceResolver.java:88) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (AS7-4862) Remote EJB SFSB load balancing still very suboptimal

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4862: ----------------------------------- Summary: Remote EJB SFSB load balancing still very suboptimal Key: AS7-4862 URL: https://issues.jboss.org/browse/AS7-4862 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: jaikiran pai Fix For: 7.1.3.Final (EAP) Looking at the load-balancing again, it seems still wrong. Checking the logs, servers were started *and cluster was formed* ~10 seconds prior to starting the client and load-balancing was roughly: * node perf18: ~50% of sessions * node perf19: 0 * node perf20: 0 * node perf21: ~50% of sessions I let all the session to be created in one minute (not all at once). The nodes were also specified in the properties. {noformat} node perf18 [JBossINF] 07:01:53,991 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (CacheService lifecycle - 1) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb] node perf19 [JBossINF] 07:01:53,781 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-19,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb] node perf20 [JBossINF] 07:01:53,781 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-14,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb] node perf21 [JBossINF] 07:01:53,780 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-12,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb] controller node 2012/05/22 07:02:02:932 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Setting thread count: 2000, was: 0 2012/05/22 07:02:53:731 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - All runners (2000) started in 50799 milliseconds {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

13 years, 4 months

3
14
0 / 0

[JBoss JIRA] (AS7-4613) hibernate.hbm2ddl.auto=create-drop fails arquillian tests, but value=create works fine

by Craig Schwarzwald (JIRA)

Craig Schwarzwald created AS7-4613: -------------------------------------- Summary: hibernate.hbm2ddl.auto=create-drop fails arquillian tests, but value=create works fine Key: AS7-4613 URL: https://issues.jboss.org/browse/AS7-4613 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Craig Schwarzwald Priority: Critical You can find my project with the tests here: https://github.com/CavemanCraig/IssueWithTestsUsingCreateDrop/tags I created 2 tags, a v0.9 which has persistence.xml specifying value=create which you can use to prove the tests work correctly, and v1.0 which specifies value=create-drop which should work just as well, but doesn't. The main error that seems to be getting returned is: Caused by: org.h2.jdbc.JdbcSQLException: Sequence "HIBERNATE_SEQUENCE" not found; SQL statement: call next value for hibernate_sequence [90036-161] This same code was working about a week ago even with specifying "create-drop". -- 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

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] (AS7-4707) Preventing reconnect attempt of remote ejb client

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4707: ------------------------------------ Summary: Preventing reconnect attempt of remote ejb client Key: AS7-4707 URL: https://issues.jboss.org/browse/AS7-4707 Project: Application Server 7 Issue Type: Bug Components: Remoting, Server Affects Versions: 7.1.1.Final Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Blocker Hi, I have a remote ejb client and a custom login module. I am testing my login module, i enter an invalid password in remote client. My login module runs correctly and send an exception. However, remote client attempts to recall login module again to login user. But i do not want this. Because when there is an exception in my custom login module, i update some values in my database. Therefore the same code in login module runs twice and my db has inconsistent values. So how can i prevent this reconnect attemp of remote ejb client? I use JBOSS 7.1.2 Final SNAPSHOT version in server and jboss 7.1.1 client maven dependencies. Thanks. My Client code is like below: Properties pr = new Properties(); pr.put("endpoint.name", "client-endpoint"); pr.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED", "false"); pr.put("remote.connections", "default"); pr.put("remote.connection.default.port", "4447"); pr.put("remote.connection.default.host", "localhost"); pr.put("remote.connection.default.connect.options.org.xnio.Options.SASL_DISALLOWED_MECHANISMS", "JBOSS-LOCAL-USER"); pr.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS", "false"); pr.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT", "false"); pr.put("remote.connection.default.username", "user1"); pr.put("remote.connection.default.password", "Test12345"); EJBClientConfiguration cc = new PropertiesBasedEJBClientConfiguration(pr); ContextSelector < EJBClientContext > selector = new ConfigBasedEJBClientContextSelector(cc); EJBClientContext.setSelector(selector); Properties props = new Properties(); props.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); props.put("jboss.naming.client.ejb.context", true); try { Context c = new InitialContext(props); kullaniciEJB = (KullaniciEJBRemote) c.lookup("ejb:merveys-kayit-tckkys/merveys-kayit-ejb-tckkys//KullaniciEJB!tr.gov.tubitak.bilgem.uekae.deys.tckk.merveys.common.controller.ejb.kullanici.KullaniciEJBRemote"); } catch (NamingException e) { e.printStackTrace(); } int count = kullaniciEJB.countKartIslemList(1L, null, null); -- 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

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] (AS7-3842) NetBeans plugin for JBoss AS 7

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3842: --------------------------------- Summary: NetBeans plugin for JBoss AS 7 Key: AS7-3842 URL: https://issues.jboss.org/browse/AS7-3842 Project: Application Server 7 Issue Type: Feature Request Reporter: Ondrej Zizka Would be nice to have. Important for broader acceptance by community. NetBeans bugzilla: http://netbeans.org/bugzilla/show_bug.cgi?id=200132 -- 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

13 years, 4 months

3
4
0 / 0

[JBoss JIRA] (AS7-4782) NoSuchMethodError: org.jboss.logmanager.LogContext.getLoggerIfExists

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created AS7-4782: --------------------------------------- Summary: NoSuchMethodError: org.jboss.logmanager.LogContext.getLoggerIfExists Key: AS7-4782 URL: https://issues.jboss.org/browse/AS7-4782 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.2.Final (EAP) Environment: Compilation: JBossAS 7.1.2.Final checked out from github.com and compiled with JDK 7u4 32-Bit on Win7 64-Bit. Runtime: JDK 7u4 64-Bit on same Windows box. Reporter: Juergen Zimmermann Assignee: James Perkins I'm running just a simple test which was working fine on JBossAS 7.1.1. Now on 7.1.2 (see description in the Environment section) I'm getting this stacktrace: java.lang.RuntimeException: Could not create a new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor see cause. at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:170) at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:166) ... 14 more Caused by: java.lang.RuntimeException: Could not create a new instance of class org.jboss.arquillian.core.impl.ManagerImpl see cause. at org.jboss.arquillian.core.spi.SecurityActions.newInstance(SecurityActions.java:157) at org.jboss.arquillian.core.spi.ManagerBuilder.create(ManagerBuilder.java:77) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.<init>(EventTestRunnerAdaptor.java:55) ... 19 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.jboss.arquillian.core.spi.SecurityActions.newInstance(SecurityActions.java:153) ... 21 more Caused by: java.lang.NoSuchMethodError: org.jboss.logmanager.LogContext.getLoggerIfExists(Ljava/lang/String;)Lorg/jboss/logmanager/Logger; at org.apache.log4j.JBossLogManagerFacade.updateParents(JBossLogManagerFacade.java:197) at org.apache.log4j.JBossLogManagerFacade.getLogger(JBossLogManagerFacade.java:145) at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:130) at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:125) at org.apache.log4j.LogManager.getLogger(LogManager.java:57) at org.apache.log4j.Logger.getLogger(Logger.java:35) at org.jboss.logging.Log4jLogger.<init>(Log4jLogger.java:35) at org.jboss.logging.Log4jLoggerProvider.getLogger(Log4jLoggerProvider.java:33) at org.jboss.logging.LoggerProviders.find(LoggerProviders.java:37) at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:32) at org.jboss.logging.Logger.getLogger(Logger.java:2163) at org.jboss.logging.Logger.getLogger(Logger.java:2188) at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.<clinit>(ArquillianServiceDeployer.java:47) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.jboss.arquillian.core.impl.Reflections.createInstance(Reflections.java:128) at org.jboss.arquillian.core.impl.ManagerImpl.createExtensions(ManagerImpl.java:410) at org.jboss.arquillian.core.impl.ManagerImpl.fireProcessing(ManagerImpl.java:345) at org.jboss.arquillian.core.impl.ManagerImpl.<init>(ManagerImpl.java:98) ... 26 more -- 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

13 years, 4 months

7
24
0 / 0

[JBoss JIRA] Created: (JBAS-8865) caching ejb3 entities tutorial demo does not work in JBoss 6

by Leos Literak (JIRA)

caching ejb3 entities tutorial demo does not work in JBoss 6 ------------------------------------------------------------ Key: JBAS-8865 URL: https://issues.jboss.org/browse/JBAS-8865 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Leos Literak Priority: Minor I run this demo: http://docs.jboss.org/ejb3/docs/tutorial/1.0.7/html/Caching_EJB3_Entities... in jboss 6 and it fails: Caused by: org.hibernate.HibernateException: could not instantiate RegionFactory [org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory] at org.hibernate.cfg.SettingsFactory.createRegionFactory(SettingsFactory.java:423) [:3.6.0.Final] at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:280) [:3.6.0.Final] at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2833) [:3.6.0.Final] at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2829) [:3.6.0.Final] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1840) [:3.6.0.Final] at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) [:3.6.0.Final] ... 78 more Caused by: java.lang.ClassNotFoundException: org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory from BaseClassLoader@a63599{vfs:///C:/Users/llitera rver/default/conf/jboss-service.xml} at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:480) [jboss-classloader.jar:2.2.0.GA] at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [:1.6.0_22] at java.lang.Class.forName0(Native Method) [:1.6.0_22] at java.lang.Class.forName(Class.java:169) [:1.6.0_22] at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:192) [:3.6.0.Final] at org.hibernate.cfg.SettingsFactory.createRegionFactory(SettingsFactory.java:409) [:3.6.0.Final] ... 83 more please update the demo to work in current jboss, thanks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2012