[JBoss JIRA] (AS7-3495) Unexpected auth dir in standalone/tmp when -Djboss.server.temp.dir is used
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created AS7-3495:
--------------------------------------
Summary: Unexpected auth dir in standalone/tmp when -Djboss.server.temp.dir is used
Key: AS7-3495
URL: https://issues.jboss.org/browse/AS7-3495
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Affects Versions: 7.1.0.CR1b
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
Unexpected 'auth' dir is created in standalone/tmp when -Djboss.server.temp.dir is used.
There shouldn't be tmp directory at all.
Steps to reproduce:
- remove everything from 'standalone' directory with exception for 'configuration' and 'deployments' sub-directories
- run standalone - 'bin/standalone.sh -Djboss.server.log.dir=xx-log -Djboss.server.data.dir=xx-data -Djboss.server.temp.dir=xx-temp -Djboss.server.deploy.dir=xx-deployments'
- list recursively 'standalone' directory -- 'tmp' directory with 'auth' subdirectory is created
'jboss.server.temp.dir' property is not 100% reflected.
--
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, 8 months
[JBoss JIRA] Created: (JBAS-9060) SFSB isn't disassociated from a transaction
by Carlo de Wolf (JIRA)
SFSB isn't disassociated from a transaction
-------------------------------------------
Key: JBAS-9060
URL: https://issues.jboss.org/browse/JBAS-9060
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: 7.0.0.Beta1
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 7.0.0.Beta2
{noformat}
javax.ejb.EJBException: EJB 3.1 FR 4.6 Stateful instance Mock for StatefulSessionComponentInstance, hashCode: 1035719231 is already associated with tx TX1 (current tx TX2)
at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:60)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1220) Add native management (ModelControllerClient) API docs to the Admin Guide
by Brian Stansberry (JIRA)
Add native management (ModelControllerClient) API docs to the Admin Guide
--------------------------------------------------------------------------
Key: AS7-1220
URL: https://issues.jboss.org/browse/AS7-1220
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
There's some brief docs on configuring the native management interface. There is a separate JIRA for some fundamental docs on jboss-dmr. There will be a page in the "Core management concepts" section on what management resources, attributes and operations are.
This task is to reference those elements and bring together a coherent picture of how to use the ModelControllerClient API.
A subtask would be to add docs on the helper classes in controller-client, although I'm fine with deferring that bit until later in the AS 7.1 cycle,
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
by Dan Sirbu (JIRA)
infinispan setup to support environment variables within the standalone.xml file
--------------------------------------------------------------------------------
Key: AS7-1751
URL: https://issues.jboss.org/browse/AS7-1751
Project: Application Server 7
Issue Type: Enhancement
Components: Clustering
Affects Versions: 7.0.1.Final
Reporter: Dan Sirbu
Assignee: Paul Ferraro
Fix For: 7.0.2.Final
When I kickstart the inifispan subsystem by using the start=EAGER option, saw that there are multiple "clusters" that get kickstarted as:
GMS: address=traffic_instance_PL-3-31315, cluster=hibernate
........................................, cluster=web
and others.
Now, if I do have mutliple blades e.g. SC-1, SC-2, PL-3, PL-4 and then I would like to define two clusters e.g. "oam" , "traffic" where "oam" should be assigned for SC-x and "traffic" for PL-x, then I will certainly need to go in the standalone-ha.xml file and change all the "cache-container name" entries in order to have "oam" cluster distinguished from "traffic" cluster, right ?
If so, it would be better if for example I could pass an jvm option via e.g. -DCLUSTER="oam" and then in the standalone-ha.xml file have this set as: "cache-container name=${CLUSTER}-"
In this way, I can obtain a dynamic config at runtime.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months