January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-253) Support <incallback>/<uncallback> in deployment

by Jesper Pedersen (JIRA)

Support <incallback>/<uncallback> in deployment ----------------------------------------------- Key: JBJCA-253 URL: https://jira.jboss.org/jira/browse/JBJCA-253 Project: JBoss JCA Issue Type: Task Components: Fungal Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha8 Add support for <incallback method="myIncallbackMethod"/> <uncallback method="myUncallbackMethod"/> where beans that has the type of the first parameter are passed in. -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7585) Remove farm/cluster-examples-service.xml

by Brian Stansberry (JIRA)

Remove farm/cluster-examples-service.xml ---------------------------------------- Key: JBAS-7585 URL: https://jira.jboss.org/jira/browse/JBAS-7585 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M2 This do-nothing file gets deployed with each "all" config boot. Get rid of 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7497) optional dependencies for jboss-as-distribution

by Michael Brackx (JIRA)

optional dependencies for jboss-as-distribution ----------------------------------------------- Key: JBAS-7497 URL: https://jira.jboss.org/jira/browse/JBAS-7497 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-6.0.0.M1 Reporter: Michael Brackx Assignee: Paul Gier Modules depending on jboss-as-distribution probably do not want all its dependecnies as they are already in the zip. I would suggest marking the dependencies as optional in the pom. -- 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

14 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3942) twiddle.sh should read run.conf - and other small ehancements

by Paul Jenner (JIRA)

twiddle.sh should read run.conf - and other small ehancements ------------------------------------------------------------- Key: JBAS-3942 URL: http://jira.jboss.com/jira/browse/JBAS-3942 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Reporter: Paul Jenner The twiddle.sh script should read environment variables from run.conf in the same way as the startup and shutdown scripts do - e.g. JAVA_HOME and JAVA. Additionally twiddle.sh should honous the JAVA environment variable instead of overwriting it with $JAVA_HOME/bin/java or "java". This makes it consistent with startup and shutdown which do honour JAVA. Finally the header should be changed from JBoss Shutdown script to JBoss twiddle script :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
6
0 / 0

[JBoss JIRA] Commented: (JBAS-7028) Startup script twiddle.bat does not set property program.name

by Andrew Oliver (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7028?page=com.atlassian.jira.plug... ] Andrew Oliver commented on JBAS-7028: ------------------------------------- done. > Startup script twiddle.bat does not set property program.name > ------------------------------------------------------------- > > Key: JBAS-7028 > URL: https://jira.jboss.org/jira/browse/JBAS-7028 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: JBossAS-5.1.0.GA > Reporter: Pavel Slavicek > Assignee: Andrew Oliver > Priority: Trivial > > Startup script twiddle.bat does not set property program.name like linux version of this script does. This property is used in the tool's implementation. Implementation uses default value if there is property program.name empty. But we have one failed test for testing twiddle's help output (startup script for tests sets this property to the different name than twiddle). There is no problem in production run. > Please could you add this property to the command line into script? -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-7028) Startup script twiddle.bat does not set property program.name

by Andrew Oliver (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7028?page=com.atlassian.jira.plug... ] Andrew Oliver resolved JBAS-7028. --------------------------------- Resolution: Done committed to trunk > Startup script twiddle.bat does not set property program.name > ------------------------------------------------------------- > > Key: JBAS-7028 > URL: https://jira.jboss.org/jira/browse/JBAS-7028 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: JBossAS-5.1.0.GA > Reporter: Pavel Slavicek > Assignee: Andrew Oliver > Priority: Trivial > > Startup script twiddle.bat does not set property program.name like linux version of this script does. This property is used in the tool's implementation. Implementation uses default value if there is property program.name empty. But we have one failed test for testing twiddle's help output (startup script for tests sets this property to the different name than twiddle). There is no problem in production run. > Please could you add this property to the command line into script? -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-382) Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier

by Jiri Pechanec (JIRA)

Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier --------------------------------------------------------------------------------------------------- Key: GPD-382 URL: https://jira.jboss.org/jira/browse/GPD-382 Project: jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.7 Reporter: Jiri Pechanec Assignee: Koen Aers -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (GPD-358) Create jBPM Project Configuration Wizard

by Koen Aers (JIRA)

Create jBPM Project Configuration Wizard ---------------------------------------- Key: GPD-358 URL: https://jira.jboss.org/jira/browse/GPD-358 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.1 This wizard can be launched from the project popup menu in the Java/J2EE/Resources perspective. It will import all the libraries from the currently configured runtime. -- 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

14 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-7590) ClusteredDeploymentRepository does not take lock before removing deployment

by Brian Stansberry (JIRA)

ClusteredDeploymentRepository does not take lock before removing deployment --------------------------------------------------------------------------- Key: JBAS-7590 URL: https://jira.jboss.org/jira/browse/JBAS-7590 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, ProfileService Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 The global lock should be taken in removeDeploymentContent(), otherwise you can get this: 1. 13:40:15,744 ERROR [StandaloneManagedDeploymentComponent] Failed to remove deployment 'vfsfile:/home/emuckenh/svn/eap/JBPAPP_5_0/build/output/jboss-5.0.0.Branch/server/all/farm/ROOT.war/'. 2. java.lang.RuntimeException: java.util.ConcurrentModificationException 3. at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:312) 4. at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.remove(StreamingDeploymentTarget.java:228) 5. at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.remove(DeploymentProgressImpl.java:322) 6. at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:95) 7. at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:155) 8. at org.rhq.plugins.jbossas5.StandaloneManagedDeploymentComponent.deleteResource(StandaloneManagedDeploymentComponent.java:314) 9. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 10. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 11. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 12. at java.lang.reflect.Method.invoke(Method.java:597) 13. at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) 14. at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 15. at java.util.concurrent.FutureTask.run(FutureTask.java:138) 16. at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 17. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 18. at java.lang.Thread.run(Thread.java:619) 19. Caused by: java.util.ConcurrentModificationException 20. at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1100) 21. at java.util.TreeMap$KeyIterator.next(TreeMap.java:1154) 22. at org.jboss.system.server.profileservice.repository.clustered.local.AbstractLocalContentManager.getContentMetadataForRemove(AbstractLocalContentManager.java:505) 23. at org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler.removeDeploymentContent(DefaultRepositoryClusteringHandler.java:362) 24. at org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository.removeDeployment(ClusteredDeploymentRepository.java:352) 25. at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:176) 26. at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:384) 27. at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:236) 28. at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897) 29. at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) 30. at org.jboss.remoting.Client.invoke(Client.java:1917) 31. at org.jboss.remoting.Client.invoke(Client.java:768) 32. at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:304 -- 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

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBOOT-100) Upgrade dependencies as part of 2.0.0-alpha-X release chain

by Andrew Lee Rubinger (JIRA)

Upgrade dependencies as part of 2.0.0-alpha-X release chain ----------------------------------------------------------- Key: JBBOOT-100 URL: https://jira.jboss.org/jira/browse/JBBOOT-100 Project: JBoss Bootstrap Issue Type: Task Components: impl-as, impl-mc, spi Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger -- 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

14 years, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010