July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-849) ivy.settings.xmk should use Maven metadata

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-849: ------------------------------------- Summary: ivy.settings.xmk should use Maven metadata Key: JBJCA-849 URL: https://issues.jboss.org/browse/JBJCA-849 Project: IronJacamar Issue Type: Bug Components: Code Generator Affects Versions: 1.1.0.Beta1 Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.1.0.Beta2 -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] (JBREM-1311) Incorret link in 'Building Remoting from source' page

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created JBREM-1311: ---------------------------------------- Summary: Incorret link in 'Building Remoting from source' page Key: JBREM-1311 URL: https://issues.jboss.org/browse/JBREM-1311 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: docs Reporter: Rostislav Svoboda http://www.jboss.org/jbossremoting/sourcecode.html anonymous access: http:anonsvn.jboss.org/repos/jbossremoting/remoting2 Link points to committer URL and not to anonsvn URL. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] (JBRULES-3318) Enable the Use of Different Table Names in drools-persistence-jpa

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Marco Rietveld commented on JBRULES-3318: ----------------------------------------- Jim, This _should be_ possible if the client modifies their persistence.xml and orm.xml files: They can use the "xml-mapping-metadata-complete" attribute to make sure that none of the JPA annotations in the code are used. If they're purely using drools-persistence-jpa (no jbpm), then this shouldn't be an issue. With jBPM and JPA 1, this isn't possible because of functionality that exists in hibernate 3.x, but not in JPA 1. If they migrate to JPA 2, then it also becomes possible for jBPM. Of course, it'd probably be helpful if we provided the example alternate persistence.xml and orm.xml files for them that do this? :) I'll see if I can provide these by the beginning of next week (july 23rd). > Enable the Use of Different Table Names in drools-persistence-jpa > ----------------------------------------------------------------- > > Key: JBRULES-3318 > URL: https://issues.jboss.org/browse/JBRULES-3318 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > Fix For: FUTURE > > > Customer is noticing a few table names that they would like to change out, ie use different ones. They also would like the table structure to match the naming conventions their organization employes. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3305) Allow to use any JPA Provider, not just Hibernate (but also OpenJPA, ...)

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Marco Rietveld resolved JBRULES-3305. ------------------------------------- Resolution: Done This was never a problem for drools: AFAIK, there are no hibernate specific annotations in Drools. > Allow to use any JPA Provider, not just Hibernate (but also OpenJPA, ...) > ------------------------------------------------------------------------- > > Key: JBRULES-3305 > URL: https://issues.jboss.org/browse/JBRULES-3305 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > > A potential customer has currently been using the BRMS/Govnor and would like the ability to use any JPA provider. They noticed some Hibernate specific annotations and wonder why that would be required/used. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3318) Enable the Use of Different Table Names in drools-persistence-jpa

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Marco Rietveld reassigned JBRULES-3318: --------------------------------------- Assignee: Marco Rietveld > Enable the Use of Different Table Names in drools-persistence-jpa > ----------------------------------------------------------------- > > Key: JBRULES-3318 > URL: https://issues.jboss.org/browse/JBRULES-3318 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > Fix For: FUTURE > > > Customer is noticing a few table names that they would like to change out, ie use different ones. They also would like the table structure to match the naming conventions their organization employes. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAOP-813) atomicity violations because of misusing concurrent collections

by Yu Lin (JIRA)

Yu Lin created JBAOP-813: ---------------------------- Summary: atomicity violations because of misusing concurrent collections Key: JBAOP-813 URL: https://issues.jboss.org/browse/JBAOP-813 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.GA Reporter: Yu Lin Attachments: jboss-aop-2.2.2.patch My name is Yu Lin. I'm a Ph.D. student in the CS department at UIUC. I'm currently doing research on mining Java concurrent library misusages. I found some misusages of ConcurrentHashMap in JBossAOP 2.2.2, which may result in potential atomicity violation bugs or harm the performance. The code below is a snapshot of the code in file aop/src/main/java/org/jboss/aop/Advisor.java from line 1217 to 1225 L1217 Set<Joinpoint> joinpoints = perInstanceJoinpointAspectDefinitions.get(def); L1218 if (joinpoints == null) L1219 { L1220 joinpoints = new ConcurrentSet<Joinpoint>(); L1221 initPerInstanceJoinpointAspectDefinitionsMap(); L1222 perInstanceJoinpointAspectDefinitions.put(def, joinpoints); L1223 def.registerAdvisor(this); L1224 } L1225 joinpoints.add(joinpoint); In the code above, an atomicity violation may occur between lines <1219 and 1222>. Suppose a thread T1 executes line 1217 and finds out the concurrent hashmap does not contain the key "def". Before it gets to execute line 1222, another thread T2 puts a pair <def, v> in the concurrent hashmap "perInstanceJoinpointAspectDefinitions". Now thread T1 resumes execution and it will overwrite the value written by thread T2. Thus, the code no longer preserves the "put-if-absent" semantics. We can use "putIfAbsent" method at line 1222 rather than "put" to preserve the "put-if-absent" semantics. Also, the same problem exists at lines 1235 and 1279 of this file. (I attach a patch that can fix the problem) I also found such problem in other files: In aop/src/main/java/org/jboss/aop/GeneratedClassAdvisor.java, lines 910, 918 and 922: after using "putIfAbsent" at these lines, I think we can remove the "synchronized" key word on method "addPerClassJoinpointAspect". In aop/src/main/java/org/jboss/aop/annotation/AnnotationRepository.java, lines 146, 159, 229, 242, 285. In aop/src/main/java/org/jboss/aop/instrument/WeavingRegistry.java, line 46. In aop/src/main/java/org/jboss/aop/metadata/MethodMetaData.java, line 81: after using "putIfAbsent" at this line, we may remove the synchronization on method "addMethodMetaData". In asintegration-mc/src/main/java/org/jboss/aop/asintegration/jboss5/ScopedVFSClassLoaderDomain.java, lines 101 and 118. In asintegration-jmx/src/main/java/org/jboss/aop/domain/ScopedRepositoryClassLoaderDomain.java, lines 73 and 91, here I'm not sure after using "putIfAbsent", whether can we remove the synchronization on map "myPerVMAspects" at line 66. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-4442) Errors in AS7-Infinispan during failover test

by rang s (JIRA)

rang s created AS7-4442: --------------------------- Summary: Errors in AS7-Infinispan during failover test Key: AS7-4442 URL: https://issues.jboss.org/browse/AS7-4442 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Environment: Windows7 Reporter: rang s Assignee: Paul Ferraro I am using a local cache and a remote store. Have deployed a distributable web app. I get the following errors on each of the server instance console during a failover [Server:server-one] 17:23:14,015 ERROR [org.apache.catalina.core.ContainerBase] (MSC service thread 1-6) ContainerBase.setManager: start: : LifecycleException: JBAS018 072: Unable to start manager: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to java.lang.String [Server:server-one] at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:205) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] [Server:server-one] at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:459) [jbossweb-7.0.13.Final.jar:] [Server:server-one] at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:250) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] [Server:server-one] at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:169) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] [Server:server-one] at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.13.Final.jar:] [Server:server-one] at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.13.Final.jar:] [Server:server-one] at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:162) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] [Server:server-one] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.13.Final.jar:] [Server:server-one] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.13.Final.jar:] [Server:server-one] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] [Server:server-one] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] [Server:server-one] -- 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, 9 months

4
6
0 / 0

[JBoss JIRA] (AS7-5190) Properly implement support for PROPERTY type in JMX facade

by Kabir Khan (JIRA)

Kabir Khan created AS7-5190: ------------------------------- Summary: Properly implement support for PROPERTY type in JMX facade Key: AS7-5190 URL: https://issues.jboss.org/browse/AS7-5190 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.2.0.Alpha1 In 7.1 properties are implemented as ModelType.toString(), while a composite type should be used. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5189) New JMX facade domain

by Kabir Khan (JIRA)

Kabir Khan created AS7-5189: ------------------------------- Summary: New JMX facade domain Key: AS7-5189 URL: https://issues.jboss.org/browse/AS7-5189 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.2.0.Alpha1 The existing jmx facade in 7.1.x is typed so each simple type has the same type as its corresponding type in the model. This however gives us no way of reading expression strings or setting expressions in jmx. This task is to create an additional domain which uses String for each simple type in the model and to not resolve expressions when reading. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5137) Wrong permissions for appclient.sh file

by Alessio Soldano (JIRA)

Alessio Soldano created AS7-5137: ------------------------------------ Summary: Wrong permissions for appclient.sh file Key: AS7-5137 URL: https://issues.jboss.org/browse/AS7-5137 Project: Application Server 7 Issue Type: Bug Components: Scripts Reporter: Alessio Soldano Assignee: Brian Stansberry Priority: Minor The appclient.sh script should have 755 permissions as all the other scripts in bin dir. However, after running ./build.sh , the file looks as follows: -rw-rw-r--. 1 alessio alessio 3701 Jul 9 11:09 ./build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/appclient.sh -- 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, 9 months

2
2
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 July 2012