[JBoss JIRA] (WFLY-2427) Launcher API
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-2427?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka edited comment on WFLY-2427 at 11/6/13 2:26 PM:
-------------------------------------------------------------
What's the input for Eclipse API?
To what extent should this go - in terms of reflecting all those system props by which various subsystems and deps may be affected? Maybe the known issues workarounds could be adressed by the API.
Other thing: Should this be a separate project, aiming to be backward compatible with older WildFly's, or would it be simply tied to WildFly releases and guaranteed to work with just that version?
was (Author: ozizka):
What's the input for Eclipse API?
To what extent should this go - in terms of reflecting all those system props by which various subsystems and deps may be affected? Maybe the known issues workarounds could be adressed by the API.
Other thing: Should this be a separate project, aiming to be backward compatible with older WildFly's, or would it be simply tied to WildFly releases and guaranteed to work with just that version?
> Launcher API
> ------------
>
> Key: WFLY-2427
> URL: https://issues.jboss.org/browse/WFLY-2427
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: Brian Stansberry
>
> 1) The AS should have some sort of API for launching our processes so tools that want a process have a clear contract instead of having to guess at what's relevant in our ever-changing scripts.
> 2) We want the main class in our process launch to be what's invoked by java -jar jboss-modules.jar. We don't want java -jar jboss-as-launcher.jar which does some stuff and then calls org.jboss.modules.Main.
> 3) JBoss Modules itself shouldn't have a lot of the stuff in it that's relevant to an AS launcher API, because many of those things are not relevant to JBoss Modules in a generic sense.
> What we could do though is provide a launcher lib that isn't involved at all in our normal boot. Something that would only be used by tools that want to launch a separate, i.e. non-embedded, AS process.
> So, some sort of stable configuration API and then a simple
> java.lang.Process launch()
> Basically, a utility that does the ProcessBuilder stuff that everybody is doing themselves now.
> HOWEVER...
> Eclipse-based tools like JBDS use Eclipse APIs for launch and would not use the above launch() method.
> So, besides that launch method, look into adding some methods to give the necessary inputs to the Eclipse API be useful. So Eclipse-based tools don't ask it for the process but can still get a standard launch configuration.
> I'd only want to do that if those methods would return something generally understandable, but a String or List<String> for classpath, List<String>s for vm/program args, some representation that "-jar jboss-modules.jar" is the way to get the main class -- those all seem generic enough.
> Any "which VM" stuff is consider out of scope; choosing the VM is the responsibility of the tool. Options that are not universally supported across VMs and are those a function of VM choice, like whether to use -server, are also out of scope.
--
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
12 years, 8 months
[JBoss JIRA] (WFLY-2275) StackOverflowError on DataSource resource injection
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-2275?page=com.atlassian.jira.plugin.... ]
Eduardo Martins resolved WFLY-2275.
-----------------------------------
Resolution: Cannot Reproduce Bug
> StackOverflowError on DataSource resource injection
> ---------------------------------------------------
>
> Key: WFLY-2275
> URL: https://issues.jboss.org/browse/WFLY-2275
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Naming
> Affects Versions: 8.0.0.Beta1
> Reporter: Thomas Diesler
> Assignee: Eduardo Martins
> Attachments: standalone-osgi.xml
>
>
> {code}
> @Resource(name="java:comp/DefaultDataSource")
> public DataSource ds;
> {code}
> leads to
> {code}
> 10:59:21,901 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: resource-injection.jar:0.0.0
> 10:59:21,937 INFO [org.jboss.as.arquillian] (MSC service thread 1-3) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."resource-injection.jar",unit=resource-injection.jar,tests=[org.jboss.test.osgi.example.resource.ResourceInjectionTestCase]]
> 10:59:21,993 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."resource-injection.jar".Activate: org.jboss.msc.service.StartException in service jboss.deployment.unit."resource-injection.jar".Activate: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> Caused by: java.lang.StackOverflowError
> at java.util.Vector.<init>(Vector.java:127) [rt.jar:1.7.0_25]
> at java.util.Vector.<init>(Vector.java:144) [rt.jar:1.7.0_25]
> at java.util.Vector.<init>(Vector.java:153) [rt.jar:1.7.0_25]
> at javax.naming.NameImpl.<init>(NameImpl.java:273) [rt.jar:1.7.0_25]
> at javax.naming.NameImpl.<init>(NameImpl.java:277) [rt.jar:1.7.0_25]
> at javax.naming.CompositeName.<init>(CompositeName.java:231) [rt.jar:1.7.0_25]
> at org.jboss.as.naming.util.NameParser.parse(NameParser.java:49)
> at org.jboss.as.naming.NamingContext.parseName(NamingContext.java:496)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:302)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:140)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:81)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:302)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:140)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:81)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:302)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:140)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:81)
> {code}
--
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
12 years, 8 months
[JBoss JIRA] (JBCOMMON-131) Setting cache timeout for JAAS under jboss-eap-6.1 does not work
by Artur Mioduszewski (JIRA)
[ https://issues.jboss.org/browse/JBCOMMON-131?page=com.atlassian.jira.plug... ]
Artur Mioduszewski edited comment on JBCOMMON-131 at 11/6/13 1:59 PM:
----------------------------------------------------------------------
Dimitris, why you cannot assign issue to proper project instead of closing it ? Rejecting an issue does not solve it ...
I don't know which exact project this issue is related to. Could you assign this issue to "JBoss Enterprise Application Platform" project (I have no such privilage) ?
was (Author: kliczko):
Dimitris, why you cannot assign issue to proper project instead of closing it ? Rejecting an issue does not solve it ...
I don't know which exact project this issue is related to. Could you assign this issue to proper JBoss project ?
> Setting cache timeout for JAAS under jboss-eap-6.1 does not work
> ----------------------------------------------------------------
>
> Key: JBCOMMON-131
> URL: https://issues.jboss.org/browse/JBCOMMON-131
> Project: JBoss Common
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: jboss-eap-6.1
> Reporter: Artur Mioduszewski
> Assignee: Dimitris Andreadis
>
> When: cache-type="default" in security-domain configuration -> authentication works correctly.
> When I have used below configuration in order to try to set cache timeout in JAAS -> JAAS authentication stops to work - I am not able to log in (on JBoss console there are not any errors)
> <code>
> ...
> <security-domain name="myJaasDomain" cache-type="infinispan">
> <authentication>
> <login-module code="Database" flag="required">
> <module-option name="dsJndiName" value="java:jboss/datasources/digital-signal-service-dev-ws-DS"/>
> <module-option name="principalsQuery" value="SELECT l.PASSWORD FROM LOGIN l WHERE l.USERNAME=?"/>
> <module-option name="rolesQuery" value="SELECT ar.NAME, 'Roles' FROM login l, login_access_group lg, access_group g, access_group_s_access_right ga, s_access_right ar WHERE l.username = ? AND l.id = lg.login_ID AND lg.groups_ID = g.id AND g.ID = ga.access_group_ID AND ga.accessRights_ID = ar.ID"/>
> <module-option name="hashAlgorithm" value="MD5"/>
> <module-option name="hashEncoding" value="base64"/>
> <module-option name="unauthenticatedIdentity" value="guest"/>
> </login-module>
> </authentication>
> </security-domain>
> ...
> <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="web">
> <cache-container name="cluster" aliases="ha-partition" default-cache="default">
> <transport lock-timeout="60000"/>
> <replicated-cache name="default" mode="SYNC" batching="true">
> <locking isolation="REPEATABLE_READ"/>
> </replicated-cache>
> </cache-container>
> <cache-container name="web" aliases="standard-session-cache" default-cache="repl">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" mode="ASYNC" batching="true">
> <file-store/>
> </replicated-cache>
> <replicated-cache name="sso" mode="SYNC" batching="true"/>
> <distributed-cache name="dist" mode="ASYNC" batching="true">
> <file-store/>
> </distributed-cache>
> </cache-container>
> <cache-container name="ejb" aliases="sfsb sfsb-cache" default-cache="repl">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" mode="ASYNC" batching="true">
> <file-store/>
> </replicated-cache>
> <replicated-cache name="remote-connector-client-mappings" mode="SYNC" batching="true"/>
> <distributed-cache name="dist" mode="ASYNC" batching="true">
> <file-store/>
> </distributed-cache>
> </cache-container>
> <cache-container name="hibernate" default-cache="local-query">
> <transport lock-timeout="60000"/>
> <local-cache name="local-query">
> <transaction mode="NONE"/>
> <expiration max-idle="100000"/>
> </local-cache>
> <invalidation-cache name="entity" mode="SYNC">
> <transaction mode="NON_XA"/>
> <expiration max-idle="100000"/>
> </invalidation-cache>
> <replicated-cache name="timestamps" mode="ASYNC">
> <transaction mode="NONE"/>
> </replicated-cache>
> </cache-container>
> </subsystem>
> ...
> <code>
--
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
12 years, 8 months
[JBoss JIRA] (JBCOMMON-131) Setting cache timeout for JAAS under jboss-eap-6.1 does not work
by Artur Mioduszewski (JIRA)
[ https://issues.jboss.org/browse/JBCOMMON-131?page=com.atlassian.jira.plug... ]
Artur Mioduszewski edited comment on JBCOMMON-131 at 11/6/13 1:59 PM:
----------------------------------------------------------------------
Dimitris, why you cannot assign issue to proper project instead of closing it ? Rejecting an issue does not solve it ...
I don't know which exact project this issue is related to. Could you move this issue to "JBoss Enterprise Application Platform" project (I have no such privilage) ?
was (Author: kliczko):
Dimitris, why you cannot assign issue to proper project instead of closing it ? Rejecting an issue does not solve it ...
I don't know which exact project this issue is related to. Could you assign this issue to "JBoss Enterprise Application Platform" project (I have no such privilage) ?
> Setting cache timeout for JAAS under jboss-eap-6.1 does not work
> ----------------------------------------------------------------
>
> Key: JBCOMMON-131
> URL: https://issues.jboss.org/browse/JBCOMMON-131
> Project: JBoss Common
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: jboss-eap-6.1
> Reporter: Artur Mioduszewski
> Assignee: Dimitris Andreadis
>
> When: cache-type="default" in security-domain configuration -> authentication works correctly.
> When I have used below configuration in order to try to set cache timeout in JAAS -> JAAS authentication stops to work - I am not able to log in (on JBoss console there are not any errors)
> <code>
> ...
> <security-domain name="myJaasDomain" cache-type="infinispan">
> <authentication>
> <login-module code="Database" flag="required">
> <module-option name="dsJndiName" value="java:jboss/datasources/digital-signal-service-dev-ws-DS"/>
> <module-option name="principalsQuery" value="SELECT l.PASSWORD FROM LOGIN l WHERE l.USERNAME=?"/>
> <module-option name="rolesQuery" value="SELECT ar.NAME, 'Roles' FROM login l, login_access_group lg, access_group g, access_group_s_access_right ga, s_access_right ar WHERE l.username = ? AND l.id = lg.login_ID AND lg.groups_ID = g.id AND g.ID = ga.access_group_ID AND ga.accessRights_ID = ar.ID"/>
> <module-option name="hashAlgorithm" value="MD5"/>
> <module-option name="hashEncoding" value="base64"/>
> <module-option name="unauthenticatedIdentity" value="guest"/>
> </login-module>
> </authentication>
> </security-domain>
> ...
> <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="web">
> <cache-container name="cluster" aliases="ha-partition" default-cache="default">
> <transport lock-timeout="60000"/>
> <replicated-cache name="default" mode="SYNC" batching="true">
> <locking isolation="REPEATABLE_READ"/>
> </replicated-cache>
> </cache-container>
> <cache-container name="web" aliases="standard-session-cache" default-cache="repl">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" mode="ASYNC" batching="true">
> <file-store/>
> </replicated-cache>
> <replicated-cache name="sso" mode="SYNC" batching="true"/>
> <distributed-cache name="dist" mode="ASYNC" batching="true">
> <file-store/>
> </distributed-cache>
> </cache-container>
> <cache-container name="ejb" aliases="sfsb sfsb-cache" default-cache="repl">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" mode="ASYNC" batching="true">
> <file-store/>
> </replicated-cache>
> <replicated-cache name="remote-connector-client-mappings" mode="SYNC" batching="true"/>
> <distributed-cache name="dist" mode="ASYNC" batching="true">
> <file-store/>
> </distributed-cache>
> </cache-container>
> <cache-container name="hibernate" default-cache="local-query">
> <transport lock-timeout="60000"/>
> <local-cache name="local-query">
> <transaction mode="NONE"/>
> <expiration max-idle="100000"/>
> </local-cache>
> <invalidation-cache name="entity" mode="SYNC">
> <transaction mode="NON_XA"/>
> <expiration max-idle="100000"/>
> </invalidation-cache>
> <replicated-cache name="timestamps" mode="ASYNC">
> <transaction mode="NONE"/>
> </replicated-cache>
> </cache-container>
> </subsystem>
> ...
> <code>
--
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
12 years, 8 months
[JBoss JIRA] (JBCOMMON-131) Setting cache timeout for JAAS under jboss-eap-6.1 does not work
by Artur Mioduszewski (JIRA)
[ https://issues.jboss.org/browse/JBCOMMON-131?page=com.atlassian.jira.plug... ]
Artur Mioduszewski reopened JBCOMMON-131:
-----------------------------------------
> Setting cache timeout for JAAS under jboss-eap-6.1 does not work
> ----------------------------------------------------------------
>
> Key: JBCOMMON-131
> URL: https://issues.jboss.org/browse/JBCOMMON-131
> Project: JBoss Common
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: jboss-eap-6.1
> Reporter: Artur Mioduszewski
> Assignee: Dimitris Andreadis
>
> When: cache-type="default" in security-domain configuration -> authentication works correctly.
> When I have used below configuration in order to try to set cache timeout in JAAS -> JAAS authentication stops to work - I am not able to log in (on JBoss console there are not any errors)
> <code>
> ...
> <security-domain name="myJaasDomain" cache-type="infinispan">
> <authentication>
> <login-module code="Database" flag="required">
> <module-option name="dsJndiName" value="java:jboss/datasources/digital-signal-service-dev-ws-DS"/>
> <module-option name="principalsQuery" value="SELECT l.PASSWORD FROM LOGIN l WHERE l.USERNAME=?"/>
> <module-option name="rolesQuery" value="SELECT ar.NAME, 'Roles' FROM login l, login_access_group lg, access_group g, access_group_s_access_right ga, s_access_right ar WHERE l.username = ? AND l.id = lg.login_ID AND lg.groups_ID = g.id AND g.ID = ga.access_group_ID AND ga.accessRights_ID = ar.ID"/>
> <module-option name="hashAlgorithm" value="MD5"/>
> <module-option name="hashEncoding" value="base64"/>
> <module-option name="unauthenticatedIdentity" value="guest"/>
> </login-module>
> </authentication>
> </security-domain>
> ...
> <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="web">
> <cache-container name="cluster" aliases="ha-partition" default-cache="default">
> <transport lock-timeout="60000"/>
> <replicated-cache name="default" mode="SYNC" batching="true">
> <locking isolation="REPEATABLE_READ"/>
> </replicated-cache>
> </cache-container>
> <cache-container name="web" aliases="standard-session-cache" default-cache="repl">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" mode="ASYNC" batching="true">
> <file-store/>
> </replicated-cache>
> <replicated-cache name="sso" mode="SYNC" batching="true"/>
> <distributed-cache name="dist" mode="ASYNC" batching="true">
> <file-store/>
> </distributed-cache>
> </cache-container>
> <cache-container name="ejb" aliases="sfsb sfsb-cache" default-cache="repl">
> <transport lock-timeout="60000"/>
> <replicated-cache name="repl" mode="ASYNC" batching="true">
> <file-store/>
> </replicated-cache>
> <replicated-cache name="remote-connector-client-mappings" mode="SYNC" batching="true"/>
> <distributed-cache name="dist" mode="ASYNC" batching="true">
> <file-store/>
> </distributed-cache>
> </cache-container>
> <cache-container name="hibernate" default-cache="local-query">
> <transport lock-timeout="60000"/>
> <local-cache name="local-query">
> <transaction mode="NONE"/>
> <expiration max-idle="100000"/>
> </local-cache>
> <invalidation-cache name="entity" mode="SYNC">
> <transaction mode="NON_XA"/>
> <expiration max-idle="100000"/>
> </invalidation-cache>
> <replicated-cache name="timestamps" mode="ASYNC">
> <transaction mode="NONE"/>
> </replicated-cache>
> </cache-container>
> </subsystem>
> ...
> <code>
--
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
12 years, 8 months
[JBoss JIRA] (WFLY-2426) Easily accessible static information describing the release
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-2426?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka edited comment on WFLY-2426 at 11/6/13 1:51 PM:
-------------------------------------------------------------
Talked to Paul. EAP already has such file, version.txt, but FWIU it is not a documented/guaranteed format. Support reportedly relies on that (Jimmy).
See JBPAPP6-1044 .
Also, there is a file which is basically what we need,
see https://github.com/jbossas/jboss-eap/commit/b8f636d9a765fcfe67cf0a8e2ff28...
resp. https://github.com/jbossas/jboss-eap/blob/b8f636d9a765fcfe67cf0a8e2ff2804...
{code}
JBoss-Product-Release-Name: EAP
JBoss-Product-Release-Version: 6.2.0.GA
JBoss-Product-Console-Slot: eap
{code}
Besides the key names say product, this could be what we need. Just to move it to the root or bin/. Any other information needed? I was thinking about a field saying product/project, if useful.
was (Author: ozizka):
Talked to Paul. EAP already has such file, version.txt, but FWIU it is not a documented/guaranteed format. Support reportedly relies on that (Jimmy).
Also, there is a file which is basically what we need,
see https://github.com/jbossas/jboss-eap/commit/b8f636d9a765fcfe67cf0a8e2ff28...
resp. https://github.com/jbossas/jboss-eap/blob/b8f636d9a765fcfe67cf0a8e2ff2804...
{code}
JBoss-Product-Release-Name: EAP
JBoss-Product-Release-Version: 6.2.0.GA
JBoss-Product-Console-Slot: eap
{code}
Besides the key names say product, this could be what we need. Just to move it to the root or bin/. Any other information needed? I was thinking about a field saying product/project, if useful.
> Easily accessible static information describing the release
> -----------------------------------------------------------
>
> Key: WFLY-2426
> URL: https://issues.jboss.org/browse/WFLY-2426
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: Brian Stansberry
>
> Tools that work with a WF installation need to identify what they are working with before they can launch or interact with the server. Specifically, they need to know the version. They likely need to know other information as well, such as the name of the software; e.g. whether it is WildFly itself or some other project based on WildFly.
> This information should be provided in standard format in a text file in a standard location in the distribution (probably in bin). The text file should be generated as part of the build.
> The solution to this issue should consider the requirements of other "identities" that may be based on WildFly. See [1] for the definition of an identity.
> The solution to this issue should consider the needs of products based on WildFly and other non-product identities. For example, can the existing product.conf contain the necessary information for a product, with some differently named but largely equivalent file being used in a non-product distribution?
> The solution to this issue should consider the implications for the patching tool.
> [1] https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... for
--
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
12 years, 8 months