September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-433) Create comrehensive API/SPI java docs

by Thomas Diesler (JIRA)

Create comrehensive API/SPI java docs ------------------------------------- Key: JBMICROCONT-433 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-433 Project: JBoss Microcontainer Issue Type: Task Reporter: Thomas Diesler Please create comprehensive javadocs -- 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

16 years

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-6991) Still issue in 5.1.0.GA <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered

by Jeff Wexler (JIRA)

Still issue in 5.1.0.GA <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered -------------------------------------------------------------------------------------------------------------- Key: JBAS-6991 URL: https://jira.jboss.org/jira/browse/JBAS-6991 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (JBoss Messaging) Affects Versions: JBossAS-5.0.0.GA Reporter: Jeff Wexler Assignee: Howard Gao Priority: Minor Fix For: JBossAS-5.1.0.Beta1 -- 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

16 years

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-6333) <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered

by Clebert Suconic (JIRA)

<database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered -------------------------------------------------------------------------------------- Key: JBAS-6333 URL: https://jira.jboss.org/jira/browse/JBAS-6333 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: JBossAS-5.0.1.CR1 -- 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

16 years

5
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2135) Deadlock occurs in Multithreaded Environment NamedEntryPoint lock and AbstractWorkingMemory actionQueue sync block.

by Jonathon Leibundguth (JIRA)

Deadlock occurs in Multithreaded Environment NamedEntryPoint lock and AbstractWorkingMemory actionQueue sync block. ------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2135 URL: https://jira.jboss.org/jira/browse/JBRULES-2135 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.0.1.FINAL Environment: java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu7) OpenJDK Client VM (build 14.0-b08, mixed mode, sharing) Reporter: Jonathon Leibundguth Assignee: Mark Proctor Priority: Critical While running drools using fireUntilHalt in multithreaded environment, the following situation results in deadlock: Thread A (Drools' Thread): AbstractWorkingMemory method executeQueuedActions() locks actionQueue: synchronized ( this.actionQueue ) Calls action.execute( this ) for each item in queue, in this case WorkingMemoryReteExpireAction to expire an event object. The WorkingMemoryReteExpireAction tries to obtain the lock in NamedEntryPoint during call to retract(). Thread B (User's Thread): attempts to execute a NamedEntryPoint insert() action simultaneously with the above. The thread obtains the NamedEntryPoint lock and blocks waiting for the lock on actionQueue. Deadlock: Thread A is blocked waiting for NamedEntryPoint lock, owned by Thread B. Thread B is blocked waiting for lock on actionQueue, owned by Thread A. -- 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

16 years

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-6305) Error installing KeyGeneratorFactory with some databases

by Martin Malina (JIRA)

Error installing KeyGeneratorFactory with some databases -------------------------------------------------------- Key: JBAS-6305 URL: https://jira.jboss.org/jira/browse/JBAS-6305 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.GA Environment: Oracle10g, DB2 v9 Reporter: Martin Malina Assignee: Jesper Pedersen Attachments: oracle10g.log After setting up Oracle10g as the DefaultDS using this docs: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/In... and starting the AS instance with "all" config, this error occured: 07:21:29,553 ERROR [AbstractKernelController] Error installing to Start: name=jboss:service=KeyGeneratorFactory,type=HiLo state=Create mode=Manual requiredState=Installed java.sql.SQLException: ORA-00942: table or view does not exist at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) .... *** CONTEXTS IN ERROR: Name -> Error jboss:service=KeyGeneratorFactory,type=HiLo -> java.sql.SQLException: ORA-00942: table or view does not exist Similar thing happens with DB2 v9. -- 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

16 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-6824) DeploymentManager.start/stop() fail with NoSuchDeploymentException when called on a Deployment that is a child of another Deployment

by Ian Springer (JIRA)

DeploymentManager.start/stop() fail with NoSuchDeploymentException when called on a Deployment that is a child of another Deployment ------------------------------------------------------------------------------------------------------------------------------------ Key: JBAS-6824 URL: https://jira.jboss.org/jira/browse/JBAS-6824 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Ian Springer Assignee: Scott M Stark For example: 16:29:47,528 INFO [DeployHandler] Stop, [vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/jbossws.sar/jbossws-management.war/] 16:29:47,528 INFO [DeployHandler] Failed to complete command: [stop] for deployment: names=[vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/jbos sws.sar/jbossws-management.war/], copyContent=true org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/jbossw s.sar/jbossws-management.war/ at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134) at org.jboss.profileservice.management.upload.remoting.DeployHandler.scheduleStop(DeployHandler.java:156) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:307) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:296) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:181) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.stop(StreamingDeploymentTarget.java:208) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.stop(DeploymentProgressImpl.java:276) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:91) at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97) at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.invokeOperation(ManagedDeploymentComponent.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:484) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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:619) -- 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

16 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-6881) Allow one to query for the ManagedComponents/ManagedPropertys that have a given admin view usage

by Scott M Stark (JIRA)

Allow one to query for the ManagedComponents/ManagedPropertys that have a given admin view usage ------------------------------------------------------------------------------------------------ Key: JBAS-6881 URL: https://jira.jboss.org/jira/browse/JBAS-6881 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Integration, ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.1.0.GA We have an adminView notion on the ManagementProperty, but we don't have a way to query for the ManagedComponents and the associated ManagedPropertys that match a given admin use. For example, something like: Class AdminViewPair { ManagedComponent comp; Collection<String> propertyNames; } Collection<AdminViewPair> pairs = managmentView.matchComponentsForAdminView("Port"); for(AdminViewPair pair : pairs) { for(String propertyName : pair.propertyNames) { ManagedProperty prop = pair.comp.getProperty(propertyName); ... } } -- 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

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-5903) Add clustering dependencies to clustered EJB3 beans

by Brian Stansberry (JIRA)

Add clustering dependencies to clustered EJB3 beans --------------------------------------------------- Key: JBAS-5903 URL: https://jira.jboss.org/jira/browse/JBAS-5903 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, EJB3 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.0.CR2 See parent task. The work on the parent task already handles EJB3 as well, if the ejb jar includes any xml deployment descriptors. Need to deal with the case where the jar has no xml; see forum thread for details. -- 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

16 years, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-6309) Decouple AS system properties and JGroups system properties

by Brian Stansberry (JIRA)

Decouple AS system properties and JGroups system properties ----------------------------------------------------------- Key: JBAS-6309 URL: https://jira.jboss.org/jira/browse/JBAS-6309 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 This will require coordination with JGroups; may not be possible if the change is considered incompatible by them for whatever release goes into AS 6.0.0. JGroups uses some system properties to overrule whatever is in the protocol stack config file. This predates the addition of system property substitution handling to the JGroups parser and is IMHO more confusing than using explicit system property substitution syntax in the config file. For AS 6 I'd like to use system property namespacing to allow JGroups to have it's mechanism, but not use it for the default AS configs. This would involve: 1) Having the AS startup switches (-b and -u) no longer set system property values in the jgroups namespace (e.g. jgroups.bind_addr and jgroups.udp.mcast_addr). Only set properties in the jboss names space (e.g. jboss.bind.address, jboss.partition.udpGroup). 2) Having JGroups' internal code ignore properties in the jboss namespace. This is the part that requires JGroups agreement. 3) Add explicit bind_addr="${jboss.bind.address} configs to all the AS protocol stacks. 4) Document how using -Djgroups.bind_addr, -Djgroups.udp_mcast_addr and -Djgroups.mping.mcast_addr can let people have the JGroups override behavior if they want it. -- 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5991) Define how patching works with the ProfileService

by Scott M Stark (JIRA)

Define how patching works with the ProfileService ------------------------------------------------- Key: JBAS-5991 URL: https://jira.jboss.org/jira/browse/JBAS-5991 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA We need to define how patching of a profile is implemented in the server/profile service. -- 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

16 years, 1 month

4
7
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 September 2009