[JBoss JIRA] Created: (JBAS-8695) Deployment repository garbage collection
by Brian Stansberry (JIRA)
Deployment repository garbage collection
----------------------------------------
Key: JBAS-8695
URL: https://jira.jboss.org/browse/JBAS-8695
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
The deployment repository is only loosely coupled to the domain model; i.e. users can add content to the repo and then have a problem or decide to not execute a deployment plan with the result that the deployment is not used in the model. Or they can remove the deployment from the model via an update, which doesn't remove it from the repo (in case the update needs to be rolled back.)
Effect of this is unreferenced deployment content can accumulate in the repo, so we need a gc utility that can be used to clean it out.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (JBRULES-681) Multi-threaded local search solving
by Geoffrey De Smet (JIRA)
Multi-threaded local search solving
-----------------------------------
Key: JBRULES-681
URL: http://jira.jboss.com/jira/browse/JBRULES-681
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Solver
Reporter: Geoffrey De Smet
Assigned To: Geoffrey De Smet
Priority: Optional
Use Future's to spread all possible moves in each step over a number of threads.
This number of threads is equal to the number of cpu's by default, as no IO is done during solving.
Problems:
- each thread will needs it own WorkingMemory and during a step, each working memory will need to be updated
- a bunch of classes will need to be thread safe, or at least visibility save, such as bestsolutionrecaller.
- Barriers will be needed to collect the result of each step
- decks might be a great way to spread out the load
--
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
12 years, 6 months
[JBoss JIRA] Created: (EJBTHREE-880) Hard-coded localhost in ejb3 test suite
by Aleksandar Kostadinov (JIRA)
Hard-coded localhost in ejb3 test suite
---------------------------------------
Key: EJBTHREE-880
URL: http://jira.jboss.com/jira/browse/EJBTHREE-880
Project: EJB 3.0
Issue Type: Bug
Reporter: Aleksandar Kostadinov
When the ejb3 testsuite is run with "-Dnode0=IP1 -Dnode1=IP2" and IP1!=localhost there are some tests failing with "Retries exceeded, couldn't reconnect to 127.0.0.1:####". I see this for 4_0 and 4_2 jboss branches, but guess it's the same with head.
One of the testcases is IiopRemoteUnitTestCase. I've checked ejb3/src/test/org/jboss/ejb3/test/iiop/unit/IiopRemoteUnitTestCase.java and there is 'props.put("java.naming.provider.url", "corbaloc::localhost:3528/NameService");'. Instead of localhost there should be used the node0 property. I guess the others have the same problem.
--
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
12 years, 7 months
[JBoss JIRA] Created: (JBAS-9259) Provide an option to change the code source used by deployments
by David Lloyd (JIRA)
Provide an option to change the code source used by deployments
---------------------------------------------------------------
Key: JBAS-9259
URL: https://issues.jboss.org/browse/JBAS-9259
Project: JBoss Application Server
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Modules / Class-loading, VFS
Reporter: David Lloyd
Priority: Minor
Fix For: 7.0.0.CR1
For most use cases, using the VFS URL for the code source is best. However in certain cases the code source is expected to correspond to a physical filesystem location, possibly even a valid JAR URL.
So there should be an option in jboss-deployment-structure.xml to allow the code source to be changed to be the URL of the physical location of the VFS mount point instead of the VFS root URL. This option would default to "off", meaning use the VFS URL.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBAS-8843) size-rotating-file-handler not rotating
by Matthias Unverzagt (JIRA)
size-rotating-file-handler not rotating
---------------------------------------
Key: JBAS-8843
URL: https://issues.jboss.org/browse/JBAS-8843
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: 6.0.0.Final
Environment: Copied from boot.log:
############################
19:38:58,804 INFO [AbstractServer] Starting: JBossAS [6.0.1.SNAPSHOT "Neo"]
19:39:00,419 INFO [ServerInfo] Java version: 1.6.0_23,Sun Microsystems Inc.
19:39:00,419 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
19:39:00,419 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 19.0-b09,Sun Microsystems Inc.
19:39:00,420 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
19:39:00,420 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms1g -Xmx3g -XX:MaxPermSize=700M -Xdebug -Xrunjdwp:transport=dt_socket,address=9009,server=y,suspend=n -Djava.endorsed.dirs=E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed
19:39:00,420 DEBUG [ServerInfo] Full System Properties Dump
19:39:00,421 DEBUG [ServerInfo] awt.toolkit: sun.awt.windows.WToolkit
19:39:00,421 DEBUG [ServerInfo] bind.address: nb-matthias
19:39:00,421 DEBUG [ServerInfo] file.encoding: Cp1252
19:39:00,421 DEBUG [ServerInfo] file.encoding.pkg: sun.io
19:39:00,421 DEBUG [ServerInfo] file.separator: \
19:39:00,421 DEBUG [ServerInfo] java.awt.graphicsenv: sun.awt.Win32GraphicsEnvironment
19:39:00,422 DEBUG [ServerInfo] java.awt.printerjob: sun.awt.windows.WPrinterJob
19:39:00,422 DEBUG [ServerInfo] java.class.path: C:\Program Files\Java\jdk1.6.0_23\lib\tools.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\bin\run.jar
19:39:00,422 DEBUG [ServerInfo] java.class.version: 50.0
19:39:00,422 DEBUG [ServerInfo] java.endorsed.dirs: E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed
19:39:00,422 DEBUG [ServerInfo] java.ext.dirs: C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext;C:\Windows\Sun\Java\lib\ext
19:39:00,422 DEBUG [ServerInfo] java.home: C:\Program Files\Java\jdk1.6.0_23\jre
19:39:00,422 DEBUG [ServerInfo] java.io.tmpdir: C:\Users\matthias\AppData\Local\Temp\
19:39:00,423 DEBUG [ServerInfo] java.library.path: C:\Program Files\Java\jdk1.6.0_23\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.6.0_23\bin;C:\apps\apache-maven-3.0.2\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseGit\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\Wave Systems Corp\Gemalto\Access Client\v5\;C:\Program Files\SlikSvn\bin\
19:39:00,423 DEBUG [ServerInfo] java.protocol.handler.pkgs: org.jboss.net.protocol|org.jboss.vfs.protocol
19:39:00,423 DEBUG [ServerInfo] java.rmi.server.RMIClassLoaderSpi: org.jboss.system.JBossRMIClassLoader
19:39:00,423 DEBUG [ServerInfo] java.rmi.server.hostname: nb-matthias
19:39:00,423 DEBUG [ServerInfo] java.runtime.name: Java(TM) SE Runtime Environment
19:39:00,423 DEBUG [ServerInfo] java.runtime.version: 1.6.0_23-b05
19:39:00,423 DEBUG [ServerInfo] java.specification.name: Java Platform API Specification
19:39:00,423 DEBUG [ServerInfo] java.specification.vendor: Sun Microsystems Inc.
19:39:00,424 DEBUG [ServerInfo] java.specification.version: 1.6
19:39:00,424 DEBUG [ServerInfo] java.util.logging.manager: org.jboss.logmanager.LogManager
19:39:00,424 DEBUG [ServerInfo] java.vendor: Sun Microsystems Inc.
19:39:00,424 DEBUG [ServerInfo] java.vendor.url: http://java.sun.com/
19:39:00,424 DEBUG [ServerInfo] java.vendor.url.bug: http://java.sun.com/cgi-bin/bugreport.cgi
19:39:00,424 DEBUG [ServerInfo] java.version: 1.6.0_23
19:39:00,424 DEBUG [ServerInfo] java.vm.info: mixed mode
19:39:00,425 DEBUG [ServerInfo] java.vm.name: Java HotSpot(TM) 64-Bit Server VM
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.name: Java Virtual Machine Specification
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.vendor: Sun Microsystems Inc.
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.version: 1.0
19:39:00,425 DEBUG [ServerInfo] java.vm.vendor: Sun Microsystems Inc.
19:39:00,425 DEBUG [ServerInfo] java.vm.version: 19.0-b09
19:39:00,425 DEBUG [ServerInfo] javax.management.builder.initial: org.jboss.mx.server.MBeanServerBuilderImpl
19:39:00,425 DEBUG [ServerInfo] jboss.bind.address: 0.0.0.0
19:39:00,426 DEBUG [ServerInfo] jboss.boot.server.log.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\log
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.name: bootstrap.xml
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/bootstrap.xml
19:39:00,426 DEBUG [ServerInfo] jboss.common.base.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/common/
19:39:00,426 DEBUG [ServerInfo] jboss.common.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/common/lib/
19:39:00,426 DEBUG [ServerInfo] jboss.home: E:\work\prgs\jboss-6.0.1-SNAPSHOT
19:39:00,426 DEBUG [ServerInfo] jboss.home.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT
19:39:00,427 DEBUG [ServerInfo] jboss.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/
19:39:00,427 DEBUG [ServerInfo] jboss.host.name: nb-matthias
19:39:00,427 DEBUG [ServerInfo] jboss.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/lib/
19:39:00,427 DEBUG [ServerInfo] jboss.native.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\tmp\native
19:39:00,427 DEBUG [ServerInfo] jboss.native.load: false
19:39:00,427 DEBUG [ServerInfo] jboss.node.name: nb-matthias
19:39:00,427 DEBUG [ServerInfo] jboss.partition.name: DefaultPartition
19:39:00,427 DEBUG [ServerInfo] jboss.platform.mbeanserver: true
19:39:00,428 DEBUG [ServerInfo] jboss.qualified.host.name: nb-matthias
19:39:00,428 DEBUG [ServerInfo] jboss.server.base.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server
19:39:00,428 DEBUG [ServerInfo] jboss.server.base.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/
19:39:00,428 DEBUG [ServerInfo] jboss.server.config.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/
19:39:00,428 DEBUG [ServerInfo] jboss.server.data.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\data
19:39:00,428 DEBUG [ServerInfo] jboss.server.home.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default
19:39:00,428 DEBUG [ServerInfo] jboss.server.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/
19:39:00,428 DEBUG [ServerInfo] jboss.server.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/lib/
19:39:00,429 DEBUG [ServerInfo] jboss.server.log.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\log
19:39:00,429 DEBUG [ServerInfo] jboss.server.name: default
19:39:00,429 DEBUG [ServerInfo] jboss.server.temp.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\tmp
19:39:00,429 DEBUG [ServerInfo] jboss.vfs.forceCopy: true
19:39:00,429 DEBUG [ServerInfo] jbossmx.loader.repository.class: org.jboss.mx.loading.UnifiedLoaderRepository3
19:39:00,429 DEBUG [ServerInfo] jgroups.bind_addr: nb-matthias
19:39:00,429 DEBUG [ServerInfo] line.separator:
19:39:00,429 DEBUG [ServerInfo] log4j.defaultInitOverride: true
19:39:00,430 DEBUG [ServerInfo] org.jboss.deployers.spi.deployer.matchers.NameIgnoreMechanism: org.jboss.deployers.spi.deployer.helpers.DummyNameIgnoreMechanism
19:39:00,430 DEBUG [ServerInfo] org.jboss.logging.Logger.pluginClass: org.jboss.logging.logmanager.LoggerPluginImpl
19:39:00,444 DEBUG [ServerInfo] org.jboss.reflect.spi.TypeInfoFactory: org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory
19:39:00,444 DEBUG [ServerInfo] os.arch: amd64
19:39:00,444 DEBUG [ServerInfo] os.name: Windows 7
19:39:00,444 DEBUG [ServerInfo] os.version: 6.1
19:39:00,444 DEBUG [ServerInfo] path.separator: ;
19:39:00,444 DEBUG [ServerInfo] program.name: run.bat
19:39:00,445 DEBUG [ServerInfo] sun.arch.data.model: 64
19:39:00,445 DEBUG [ServerInfo] sun.boot.class.path: E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\activation.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-annotations-api_1.1_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-jaxb-api_2.2_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-jaxws-api_2.2_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jbossws-cxf-factories.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\stax-api.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\modules\jdk.boot.jar;C:\Program Files\Java\jdk1.6.0_23\jre\classes
19:39:00,445 DEBUG [ServerInfo] sun.boot.library.path: C:\Program Files\Java\jdk1.6.0_23\jre\bin
19:39:00,445 DEBUG [ServerInfo] sun.cpu.endian: little
19:39:00,445 DEBUG [ServerInfo] sun.cpu.isalist: amd64
19:39:00,445 DEBUG [ServerInfo] sun.desktop: windows
19:39:00,445 DEBUG [ServerInfo] sun.io.unicode.encoding: UnicodeLittle
19:39:00,446 DEBUG [ServerInfo] sun.java.launcher: SUN_STANDARD
19:39:00,446 DEBUG [ServerInfo] sun.jnu.encoding: Cp1252
19:39:00,446 DEBUG [ServerInfo] sun.management.compiler: HotSpot 64-Bit Server Compiler
19:39:00,446 DEBUG [ServerInfo] sun.os.patch.level:
19:39:00,446 DEBUG [ServerInfo] user.country: DE
19:39:00,446 DEBUG [ServerInfo] user.dir: C:\Windows\System32
19:39:00,446 DEBUG [ServerInfo] user.home: C:\Users\matthias
19:39:00,446 DEBUG [ServerInfo] user.language: de
19:39:00,447 DEBUG [ServerInfo] user.name: matthias
19:39:00,447 DEBUG [ServerInfo] user.timezone: Europe/Berlin
19:39:00,447 DEBUG [ServerInfo] user.variant:
19:39:00,447 DEBUG [ServerInfo] xb.builder.repeatableParticleHandlers: false
19:39:00,447 DEBUG [ServerInfo] xb.builder.useUnorderedSequence: true
Reporter: Matthias Unverzagt
Assignee: David Lloyd
size-rotating-file-handler only rotates once and then the logfile grows.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JASSIST-44) Maven profiles for tools.jar should take account of Mac OS
by Martin Burger (JIRA)
Maven profiles for tools.jar should take account of Mac OS
----------------------------------------------------------
Key: JASSIST-44
URL: http://jira.jboss.com/jira/browse/JASSIST-44
Project: Javassist
Issue Type: Bug
Environment: Maven version: 2.0.8
Java version: 1.5.0_13
OS name: "mac os x" version: "10.4.11" arch: "i386" Family: "unix"
Reporter: Martin Burger
Assigned To: Shigeru Chiba
The pom.xml uses different profiles to add the tools.jar to the dependencies. However, it is already included in the runtime for Mac OS X and some free JDKs and does not exist as a separate file 'tools.jar'. See: http://maven.apache.org/general.html#tools-jar-dependency
As soon as http://jira.codehaus.org/browse/MNG-3106 gets fixed, activation should look like the following example:
<activation>
<jdk>1.6</jdk>
<property>
<name>java.vendor</name>
<value>Sun Microsystems Inc.</value>
</property>
</activation>
In the meantime
<profiles>
<profile>
<id>tools.jar</id>
<activation>
<property>
<name>java.vendor</name>
<value>Sun Microsystems Inc.</value>
</property>
</activation>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.6</version>
<scope>system</scope>
<optional>true</optional>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
</dependencies>
</profile>
</profiles>
should do the job. It could be a permanent solution because the different profiles differ only in the version element.
--
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
12 years, 7 months