August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4868) JBoss Vault does not parse file paths on Windows correctly

by Geoffrey Bays (JIRA)

Geoffrey Bays created AS7-4868: ---------------------------------- Summary: JBoss Vault does not parse file paths on Windows correctly Key: AS7-4868 URL: https://issues.jboss.org/browse/AS7-4868 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.1.Final Environment: Windows 7 64-bit, JDK 1.6.0_32, JBoss 7.1.1 Final 'Brontes' Reporter: Geoffrey Bays Assignee: Anil Saldhana Priority: Blocker Fix For: 7.0.2.SP1 When using the standard standalone.bat file and vault mechanism for masking the keystore password (see https://community.jboss.org/wiki/JBossAS7SecuringPasswords) the JBoss code that reads the jboss.home.dir in the vault section in standalone.xml removes all file separators from the jboss home path. If the full path to the keystore file and jboss home dir are hardcoded into the vault xml fragment, then the vault works fine.I have tried all combinations of file separators in standalone.bat and in a separate properties file, but the separators are all removed. The echo of JBOSS_HOME_DIR from standalone.bat gives D:\projects\jboss7 with the proper file separators.(see stacktrace) The error starts with: ...SecurityVaultException: PB00019: Processing Failed:D:projectsjboss7/apphome/vault does not exist. Vault xml: <vault> <vault-option name="KEYSTORE_URL" value="${jboss.server.config.dir}/localhost.keystore" /> // hardcoded path works ... <vault-option name="ENC_FILE_DIR" value="${jboss.home.dir}/apphome/vault" /> // hardcoded path works </vault> End of standalone.bat after :RESTART (double quotes not doing anything) -Djboss.home.dir="%JBOSS_HOME%" ^ // can hardcode path with any type of separators here and they all go away Full Stacktrace: D:\projects\jboss7\bin>standalone.bat Calling "D:\projects\jboss7\bin\standalone.conf.bat" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: D:\projects\jboss7 JAVA: C:\Program Files (x86)\Java\jdk1.6.0_32\bin\java JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms512M -Xmx1024M -XX:MaxPermSize =512M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.pre ferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -D jboss.server.default.config=standalone.xml -Xrunjdwp:transport=dt_socket,address=12999,server=y,susp end=n -Dtcaims.home=W:\projects\jboss7\tcaimshome -DdevelopmentConfig=true -DTheaterOps=0 =============================================================================== Listening for transport dt_socket at address: 12999 18:37:35,762 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 18:37:35,871 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 18:37:35,887 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 18:37:36,308 INFO [org.jboss.security.vault.SecurityVaultFactory] Getting Security Vault with imple mentation of org.picketbox.plugins.vault.PicketBoxSecurityVault 18:37:36,308 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") fail ed - address: ([("core-service" => "vault")]): java.lang.RuntimeException: JBAS015804: Error initial izing vault -- org.jboss.as.server.services.security.VaultReaderException: org.jboss.security.vault .SecurityVaultException: org.jboss.security.vault.SecurityVaultException: PB00019: Processing Failed :D:projectsjboss7/tcaimshome/vault/ does not exist at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(VaultAddHandler.java :115) at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.jav a:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext. java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.ja va:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.ParallelBootOperationStepHandler.execute(ParallelBootOperationSte pHandler.java:161) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.jav a:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext. java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.ja va:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:168) [jboss-as- controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:190 ) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.server.ServerService.boot(ServerService.java:291) at org.jboss.as.server.ServerService.boot(ServerService.java:266) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:15 5) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32] Caused by: org.jboss.as.server.services.security.VaultReaderException: org.jboss.security.vault.Secu rityVaultException: org.jboss.security.vault.SecurityVaultException: PB00019: Processing Failed:D:pr ojectsjboss7/tcaimshome/vault/ does not exist at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVaultReader.java:84) at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(VaultAddHandler.java :113) ... 14 more Caused by: org.jboss.security.vault.SecurityVaultException: org.jboss.security.vault.SecurityVaultEx ception: PB00019: Processing Failed:D:projectsjboss7/tcaimshome/vault/ does not exist at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:199) at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVaultReader.java:82) ... 15 more Caused by: org.jboss.security.vault.SecurityVaultException: PB00019: Processing Failed:D:projectsjbo ss7/tcaimshome/vault/ does not exist at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:177) ... 16 more 18:37:36,339 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable mann er; exiting. See previous messages for details. 18:37:36,355 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final "Brontes" stopped in 2ms -- 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

12 years, 1 month

4
12
0 / 0

[JBoss JIRA] (AS7-5368) Lookup of UserTransaction should not be allowed in CMT beans

by Cheng Fang (JIRA)

Cheng Fang created AS7-5368: ------------------------------- Summary: Lookup of UserTransaction should not be allowed in CMT beans Key: AS7-5368 URL: https://issues.jboss.org/browse/AS7-5368 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.2.0.Alpha1 Reporter: Cheng Fang Assignee: jaikiran pai EJB spec 8.3.4 Enterprise Beans Using Container-Managed Transaction Demarcation: The enterprise bean’s business methods, message listener methods, business method interceptor meth- ods, lifecycle callback interceptor methods, or timeout callback methods must not attempt to obtain or use the javax.transaction.UserTransaction interface. Currently lookup("java:comp/UserTransaction") returns an instance of org.jboss.tm.usertx.client.ServerVMClientUserTransaction. Similar to AS7-5331 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBVFS-177) VFSUtils.unzip() does not preserve file modified time

by Brad Hawthorne (JIRA)

VFSUtils.unzip() does not preserve file modified time ----------------------------------------------------- Key: JBVFS-177 URL: https://issues.jboss.org/browse/JBVFS-177 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.1.GA Reporter: Brad Hawthorne Assignee: John Bailey Unzip does not set the last-modified time on the files it creates to that of the original ZipEntries, therefore they default to their creation time. This causes problems for JBAS, where web clients will always be forced to re-download files (and not use their cache) whenever the server is restarted or application is redeployed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
5
0 / 0

[JBoss JIRA] (AS7-4815) Occurences of "ISPN000069: Cache named [default-host/clusterbench] exists but isn't in a state to handle remote invocations" on shutdown

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4815: ----------------------------------- Summary: Occurences of "ISPN000069: Cache named [default-host/clusterbench] exists but isn't in a state to handle remote invocations" on shutdown Key: AS7-4815 URL: https://issues.jboss.org/browse/AS7-4815 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP) AFAIR related to the order of starting caches and channels. Lets track here if we remove the logging and/or which build to get the fix to. -- 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (JGRP-1500) ThreadLocal leak in FlowControl

by Elliot Lovy (JIRA)

Elliot Lovy created JGRP-1500: --------------------------------- Summary: ThreadLocal leak in FlowControl Key: JGRP-1500 URL: https://issues.jboss.org/browse/JGRP-1500 Project: JGroups Issue Type: Bug Affects Versions: 2.12.3 Environment: Tomcat Reporter: Elliot Lovy Assignee: Bela Ban org.jgroups.protocols.FlowControl has a thread local leak. Tomcat's memory management shows: SEVERE: The web application [/app] created a ThreadLocal with key of type [null] (value [org.jgroups.protocols.FlowControl$1@79c1187f]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak. The fix seems straightforward to me, just replace the two instances of: ignore_thread.set(false); with ignore_thread.remove(); I have verified this does indeed prevent the leak. Since false is the default value the thread local would get created with, then setting it to false is equivalent to removing it, with the added benefit of actually removing the ThreadLocal from the application server's thread. So it only exists while it is set to true. -- 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (SECURITY-689) port SECURITY-685, SECURITY-686, SECURITY-687 to Branch_2_0 (changes to jboss-security-spi)

by Peter Skopek (JIRA)

Peter Skopek created SECURITY-689: ------------------------------------- Summary: port SECURITY-685, SECURITY-686, SECURITY-687 to Branch_2_0 (changes to jboss-security-spi) Key: SECURITY-689 URL: https://issues.jboss.org/browse/SECURITY-689 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: JBossSecurity_2.0.5.Final Reporter: Peter Skopek Assignee: Peter Skopek Fix For: JBossSecurity_2.0.6.Final port SECURITY-685, SECURITY-686, SECURITY-687 to Branch_2_0 (changes to jboss-security-spi) - SubjectInfo->getIdentities should return unmodifiable list - SubjectInfo : methods to remove the identities - SecurityContextUtil clearIdentity should use the proper methods for SubjectInfo remove -- 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2035) Upport JBPAPP-2811: EJB3 timer service doesn't retry on rollback

by Carlo de Wolf (JIRA)

Upport JBPAPP-2811: EJB3 timer service doesn't retry on rollback ---------------------------------------------------------------- Key: EJBTHREE-2035 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2035 Project: EJB 3.0 Issue Type: Sub-task Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] (AS7-4533) Reduce number of ON_DEMAND services installed by the OSGi subsystem

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4533: ----------------------------------- Summary: Reduce number of ON_DEMAND services installed by the OSGi subsystem Key: AS7-4533 URL: https://issues.jboss.org/browse/AS7-4533 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler It should be possible to have a single dependency on the FrameworkBootstrapService -- 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

12 years, 1 month

1
4
0 / 0

[JBoss JIRA] (AS7-5224) [JBoss 7.1.0.Final] High CPU usage for single-core CPU VMWare virtual machine running Redhat 6 OS

by Claudiu Muresan (JIRA)

Claudiu Muresan created AS7-5224: ------------------------------------ Summary: [JBoss 7.1.0.Final] High CPU usage for single-core CPU VMWare virtual machine running Redhat 6 OS Key: AS7-5224 URL: https://issues.jboss.org/browse/AS7-5224 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Final Environment: -bash-4.1$ cat /proc/version Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)x86-008.build.bos.redhat.com) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Wed Jun 13 18:24:36 EDT 2012 -bash-4.1$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz stepping : 2 cpu MHz : 2666.761 cache size : 12288 KB fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc up arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes hypervisor lahf_lm ida arat epb dts bogomips : 5333.52 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: -bash-4.1$ cat /proc/meminfo MemTotal: 3925212 kB MemFree: 328048 kB Buffers: 21276 kB Cached: 3268128 kB SwapCached: 180 kB Active: 1832808 kB Inactive: 1475292 kB Active(anon): 3104 kB Inactive(anon): 16008 kB Active(file): 1829704 kB Inactive(file): 1459284 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 8388600 kB SwapFree: 8387940 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 18624 kB Mapped: 12656 kB Shmem: 416 kB Slab: 220480 kB SReclaimable: 196296 kB SUnreclaim: 24184 kB KernelStack: 792 kB PageTables: 6980 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 10351204 kB Committed_AS: 102640 kB VmallocTotal: 34359738367 kB VmallocUsed: 283176 kB VmallocChunk: 34359452028 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 10240 kB DirectMap2M: 4184064 kB Reporter: Claudiu Muresan Assignee: Jason Greene When starting JBoss server in standalone configuration we have 100% CPU usage. There are no deployments. Please view attached items: thread dump, standalone.conf, standalone.xml. The JVM version is -bash-4.1$ ./java -version java version "1.6.0_27" Java(TM) SE Runtime Environment (build 1.6.0_27-b07) Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode) . Tried also with the latest JVM version (6u33) => high CPU usage. Tried also with 7.1.1 Final and same configuration(standalone.conf/standalone.xml) => high CPU usage. -- 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

12 years, 1 month

5
27
0 / 0

[JBoss JIRA] (AS7-5362) How to Increase thread pool size in Jboss As7 Standalone Environment

by Suman Alapati (JIRA)

Suman Alapati created AS7-5362: ---------------------------------- Summary: How to Increase thread pool size in Jboss As7 Standalone Environment Key: AS7-5362 URL: https://issues.jboss.org/browse/AS7-5362 Project: Application Server 7 Issue Type: Clarification Reporter: Suman Alapati Hi All, I am Using Jboss As7 as my App Server . Can any one let me know how to increase server thread pool size in case of standalone environment. And What is the default pool size of app server. -- 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

12 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012