[JBoss JIRA] (AS7-6411) Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur."
by Bernard Giroud (JIRA)
[ https://issues.jboss.org/browse/AS7-6411?page=com.atlassian.jira.plugin.s... ]
Bernard Giroud commented on AS7-6411:
-------------------------------------
Thanks Darran for marking Fix Version/s "7.3.0.Alpha1" !
Does that mean that you modified the script add-user.sh AND you are currently trying to reproduce/fix the error ?
I should have better separated the two items as in https://community.jboss.org/thread/220615
> Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur."
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6411
> URL: https://issues.jboss.org/browse/AS7-6411
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows XP with CYGWIN_NT-5.1 ... 1.7.17 (0.262/5/3) 2012-10-19 i686
> Java HotSpot 1.7.0_11, RE build 1.7.0_11-b21, Client VM build 23.6-b04, mixed mode
> JBoss AS 7.1.3.Final
> Reporter: Bernard Giroud
> Assignee: Darran Lofthouse
> Labels: as7, management
> Fix For: 7.3.0.Alpha1
>
>
> First of all, the add-user.sh script has an invalid syntax on line 14 which reads:
> {code}
> cygwin = true;
> {code}
> It should read:
> {code}
> cygwin=true;
> {code}
> without spaces around the equal sign, Otherwise the truth value is not set, and the conversion back to Windows pathes is not done.
> Furthermore, the back-conversions should be conditioned to avoid a "cygpath: can't convert empty path" in lines 56-60, especially with JAVA_HOME.
> Finally, issuance of the following command : bin/add-user.sh u p
> Gives:
> {noformat}
> cygpath: can't convert empty path
> Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur.
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:107)
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:118)
> at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
> Issuance of the following command : bin/add-user.sh
> Gives:
> {noformat}
> cygpath: can't convert empty path
> Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur.
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:78)
> at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:168)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
> Option --silent doesn't make a difference.
> An obvious workaround exists though: use with a CMD windows
> {noformat}
> bin\add-user.bat u p
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6216) Some javax.* bundles show version 0.0.0 in AS7
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6216?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6216:
----------------------------------------
For example javax.activation.api missing OSGi metadata as well
> Some javax.* bundles show version 0.0.0 in AS7
> ----------------------------------------------
>
> Key: AS7-6216
> URL: https://issues.jboss.org/browse/AS7-6216
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Reporter: Thomas Diesler
> Assignee: Paul Gier
> Fix For: 7.2.0.CR1
>
>
> Some javax bundles that we configure by default do not show valid bundle version info
> javax.jws.api:0.0.0
> javax.ws.rs.api:0.0.0
> The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this
> {code}
> Bundle-SymbolicName: hibernate-jpa-2.0-api
> Bundle-Version: 1.0.1.Final
> Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0"
> {code}
> This should be replaced by metadata coming from the artefacts manifest.
> Generally, all javax api artefacts should have valid OSGi metadata
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori edited comment on AS7-6420 at 1/30/13 9:50 AM:
-----------------------------------------------------------------
I've now uploaded my whole JBoss into http://slsh.kapsi.fi/misc/jboss-as-7.2.0.Alpha1-SNAPSHOT.zip (~124M, user/pass admin/jboss). Using that, spring-xml deployment doesn't appear in the admin panel at all, nor does it let you deploy that package, showing just the red message in admin UI. However, if spring-ws deployment is removed, spring-xml deployment appears in admin UI.
was (Author: jrantav):
I've now uploaded my whole JBoss into http://slsh.kapsi.fi/misc/jboss-as-7.2.0.Alpha1-SNAPSHOT.zip (~124M). Using that, spring-xml deployment doesn't appear in the admin panel at all, nor does it let you deploy that package, showing just the red message in admin UI. However, if spring-ws deployment is removed, spring-xml deployment appears in admin UI.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6419) Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
by Martin Keller (JIRA)
[ https://issues.jboss.org/browse/AS7-6419?page=com.atlassian.jira.plugin.s... ]
Martin Keller commented on AS7-6419:
------------------------------------
Thank You!
OK we will try out
> Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6419
> URL: https://issues.jboss.org/browse/AS7-6419
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.2.0.Alpha1
> Environment: Configuration:
> JDK-Version: 1.6.0_33
> Operating System: Windows 7 (32 Bit)
> JBoss Application Server jboss-as-7.2.0.Alpha1-SNAPSHOT (build Dec. 19th 2012)
> JDK-Version: 1.6.0_33
> Resource Adapter: BeanConnect 3.0 developed by our Company (Fujitsu)
> Reporter: Martin Keller
> Assignee: Stefano Maestri
>
> Tbis Problem was reported before see https://issues.jboss.org/browse/AS7-6384, but now the components to reproduce it is included.
> Starting an application using our JCA 1.6 resource adapter fails with
> java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> It works ok in the JBoss JCA 1.5 environment and on other application servers with JCA1.6 environment:
> GlassFish OS Edition 3, IBM WebSphere 8.0 and WebLogic 12.
> Questions:
> What could be the cause for this exception?
> Can we switch off the validation?
> What is missing to run the validation successful?
> Details:
> The full stack is:
> 15:04:02,128 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 64) MSC00001: Failed to start service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:177)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> ... 7 more
> Caused by: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:147)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:175)
> ... 8 more
> Caused by: javax.validation.ValidationException: Unable to find a default provider
> at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264) [validation-api-1.0.0.GA.jar:]
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidatorFactory(BeanValidationUtil.java:51)
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidator(BeanValidationUtil.java:63)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:135)
> ... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JGRP-1576) org.jgroups.protocols.TP.ChannelThreadGroup leaks classloaders / PermGen memory
by Mattias Jiderhamn (JIRA)
[ https://issues.jboss.org/browse/JGRP-1576?page=com.atlassian.jira.plugin.... ]
Mattias Jiderhamn commented on JGRP-1576:
-----------------------------------------
I don't have an isolated test case.
The problem appeared when using JGroups behind Infinispan for clustered Hibernate Search / Lucene. I have little insight into how Infinispan uses JGroups, but I could upload the config files if that helps?
> org.jgroups.protocols.TP.ChannelThreadGroup leaks classloaders / PermGen memory
> -------------------------------------------------------------------------------
>
> Key: JGRP-1576
> URL: https://issues.jboss.org/browse/JGRP-1576
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.2.5
> Reporter: Mattias Jiderhamn
> Assignee: Bela Ban
> Fix For: 3.2.7
>
>
> Just like JGRP-1410 there is a custom ThreadGroup org.jgroups.protocols.TP.ChannelThreadGroup which is not destroyed so the parent thread group will keep a reference and keep the classloader from being garbage collected. There is actually code for destroying the thread groups (line 1026-1030) but for some reason it is commented out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-1574?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on JGRP-1574:
-----------------------------------
So, the pull requests are issued, but I can't find how to change the status to Pull Request Sent...
> ThreadPool rejection policy detecting stuck threads
> ---------------------------------------------------
>
> Key: JGRP-1574
> URL: https://issues.jboss.org/browse/JGRP-1574
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.2.6
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Priority: Minor
> Fix For: 3.2.7, 3.3
>
>
> Sometimes I find out my OOB threadpool size (which defaults to 200) in our tests too low, causing deadlock (this seems to be the case with the 64 node cluster - we've run out of OOB threads because all of them were stuck).
> New rejection policy could usually silently discard the message, but in case that the thread pool does not finish anything (getCompletedTaskCount stays constant) for a period, it would throw a special exception denoting that there's possibly a deadlock (and that raising OOB threadpool could help).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori updated AS7-6420:
-----------------------------------
Steps to Reproduce:
Try to deploy attached spring-xml 2.10 component, downloaded from spring enterprise repository, in the JBoss AS7 snapshot installation (link as a comment). Using web-based admin console, red message "deployment failed" appears, but no reason is available in logs, System.out or UI.
Removing spring-ws deployment, again from admin console, makes spring-xml deployment appear in the admin console UI.
was:Try to deploy attached spring-xml 2.10 component, downloaded from spring enterprise repository, in the latest JBoss AS7 snapshot. Using web-based admin console, red message "deployment failed" appears, but no reason is available in logs, System.out or UI.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6420:
----------------------------------------
I've now uploaded my whole JBoss into http://slsh.kapsi.fi/misc/jboss-as-7.2.0.Alpha1-SNAPSHOT.zip (~124M). Using that, spring-xml deployment doesn't appear in the admin panel at all, nor does it let you deploy that package, showing just the red message in admin UI. However, if spring-ws deployment is removed, spring-xml deployment appears in admin UI.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months