[JBoss JIRA] (JBREM-1182) Update testsuite to run under Hudson
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JBREM-1182?page=com.atlassian.jira.plugin... ]
Richard Achmatowicz resolved JBREM-1182.
----------------------------------------
Resolution: Out of Date
> Update testsuite to run under Hudson
> --------------------------------------
>
> Key: JBREM-1182
> URL: https://issues.jboss.org/browse/JBREM-1182
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: general
> Affects Versions: 2.2.3.SP1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 2.2.4.SP1
>
> Attachments: JBREM-1182-JRunit.patch, JBREM-1182.patch
>
>
> Update the JBoss Remoting testsuite to run under Hudson. Some current problems include:
> (i) on Linux, JRunit based tests are failing due to members not finding each other
> (ii) on Linux, under JDK6, JRunit based tests are not able to create a JGroups stack
> (iii) JRunit system properties specified by the user on the command line are not being passed the the JUnit targets correctly, and so have no effect on the tests
>
--
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
13 years, 3 months
[JBoss JIRA] (AS7-2595) Jars in root of a sar archive not added to the sar's classpath
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-2595?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-2595:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> Jars in root of a sar archive not added to the sar's classpath
> --------------------------------------------------------------
>
> Key: AS7-2595
> URL: https://issues.jboss.org/browse/AS7-2595
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Reporter: Mike Clark
> Assignee: Tomek Adamski
> Fix For: 7.2.0.Alpha1
>
>
> In previous versions, a sar archive includes classes in the sar archive's root on the sar's classpath. It is quite common to have a structure such as:
> mbean.sar
> mbean.sar/META-INF
> mbean.sar/META-INF/jboss-deployment-structure.xml
> mbean.sar/META-INF/jboss-service.xml
> mbean.sar/META-INF/MANIFEST.MF
> mbean.sar/some.jar
> However, this does not work. The classes in some.jar are not available.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-2595) Jars in root of a sar archive not added to the sar's classpath
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-2595?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-2595:
----------------------------------
Assignee: Tomek Adamski
> Jars in root of a sar archive not added to the sar's classpath
> --------------------------------------------------------------
>
> Key: AS7-2595
> URL: https://issues.jboss.org/browse/AS7-2595
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Reporter: Mike Clark
> Assignee: Tomek Adamski
>
> In previous versions, a sar archive includes classes in the sar archive's root on the sar's classpath. It is quite common to have a structure such as:
> mbean.sar
> mbean.sar/META-INF
> mbean.sar/META-INF/jboss-deployment-structure.xml
> mbean.sar/META-INF/jboss-service.xml
> mbean.sar/META-INF/MANIFEST.MF
> mbean.sar/some.jar
> However, this does not work. The classes in some.jar are not available.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6413) Remove subsystem command in JGroups management api should remove existing stacks.
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/AS7-6413?page=com.atlassian.jira.plugin.s... ]
Richard Achmatowicz commented on AS7-6413:
------------------------------------------
Implemeted the change in the model stage of JGroupsSubsystemRemove: if there are existing stacks defined, prepare and execute operations to remove the stacks before finally removing the subsystem itself.
> Remove subsystem command in JGroups management api should remove existing stacks.
> ---------------------------------------------------------------------------------
>
> Key: AS7-6413
> URL: https://issues.jboss.org/browse/AS7-6413
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.2.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 7.2.0.Alpha1
>
>
> The management command
> {noformat}
> /subsystem=jgroups:remove()
> {noformat}
> should check for existing stack children and remove their runtime services before removing its own runtime services.
> Otherwise removing the JGroups subsystem, followed by adding it back in and creating a new stack with the same name will fail due to duplicate MSC services associated with the stack.
>
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6412) Transformation logging issues
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6412?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on AS7-6412:
----------------------------------
that "subsystem 'infinispan' model version 'null'" is problem with tests not with actual runtime, but need to be addressed in any case.
> Transformation logging issues
> -----------------------------
>
> Key: AS7-6412
> URL: https://issues.jboss.org/browse/AS7-6412
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Kind of a grab bag dumping ground for issues I've noted with the new transformation logging stuff.
> Here's an example message I saw posted in an unrelated discussion:
> subsystem 'infinispan' model version 'null' -- attributes null JBAS014886: are not understood in that model version and this resource will need to be ignored on that host.
> I'm not sure about the model version 'null' bit. Maybe that was a dev error, or perhaps a bug. If there are valid cases for 'null' there the logic needs to account for that and output something nicer.
> The "attributes null" bit: we need to deal with cases where no attribute names are passed in. (There are cases like this.) If that happens the entire "attributes xxx" bit should be skipped.
> The message param passed in is going to be an i18n message, so the message structure should account for that and not try to assume some particular English grammar. For example
> Subsystem 'infinispan' model version '1.2.3' -- attribute(s) abc, def had the following problem: JBAS014886: Attributes are not understood in that model version and this resource will need to be ignored on that host.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6423) JBoss RPM doesn't adhere to LFS
by Jimmy Wilson (JIRA)
[ https://issues.jboss.org/browse/AS7-6423?page=com.atlassian.jira.plugin.s... ]
Jimmy Wilson commented on AS7-6423:
-----------------------------------
[~rafaelliu]: Can you open a support case about this so that we can get this fixed in a future release? This JIRA tracker is not the correct location. In the support case, you can tell them that Jimmy Wilson asked you to do this.
> JBoss RPM doesn't adhere to LFS
> -------------------------------
>
> Key: AS7-6423
> URL: https://issues.jboss.org/browse/AS7-6423
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Build System
> Affects Versions: 7.1.2.Final (EAP)
> Environment: Red Hat Enterprise Linux Server release 6.3 (Santiago)
> Reporter: rafael liu
> Assignee: Fernando Nasser
> Priority: Minor
> Labels: rpm
>
> In /usr/share/jbossas/domain links to tmp and data folders were mixed up:
> {noformat}
> [domain]]# ls -l
> total 4
> lrwxrwxrwx. 1 jboss jboss 19 Jan 2 14:45 configuration -> /etc/jbossas/domain
> lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 data -> /var/tmp/jbossas/domain
> lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 log -> /var/log/jbossas/domain
> drwxrwxr-x. 5 jboss jboss 4096 Jan 2 16:02 servers
> lrwxrwxrwx. 1 jboss jboss 25 Jan 2 14:45 tmp -> /var/cache/jbossas/domain
> {noformat}
> In /usr/share/jbossas/standalone tmp folder is not linked:
> {noformat}
> [standalone]# ls -l
> total 12
> lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 configuration -> /etc/jbossas/standalone
> drwxr-xr-x. 2 jboss jboss 4096 Jan 2 14:45 deployments
> drwxr-xr-x. 3 jboss jboss 4096 Jan 2 14:45 lib
> lrwxrwxrwx. 1 jboss jboss 27 Jan 2 14:45 log -> /var/log/jbossas/standalone
> drwxr-xr-x. 3 jboss jboss 4096 Jan 2 14:45 tmp
> {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
13 years, 3 months
[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated AS7-6334:
----------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups [OK]
clustering/infinispan
cmp [OK]
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner - WIP Kabir
ee - PR https://github.com/jbossas/jboss-as/pull/3969
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr [OK]
jaxrs [OK] empty subsystem
jdr - [OK] empty subsystem
jmx [OK]
jpa [OK]
jsf [OK]
jsr77 [OK] empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster [OK]
naming [OK]
osgi [OK]
pojo [OK] empty subsystem
remoting - [OK]
sar [OK] empty subsystem
security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
threads - WIP Brian
transactions - [PR https://github.com/jbossas/jboss-as/pull/3963]
web - [PR https://github.com/jbossas/jboss-as/pull/3963]
webservices - WIP Kabir
weld [OK] empty subsystem
xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups [OK]
clustering/infinispan
cmp [OK]
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner - WIP Kabir
ee - WIP Kabir
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr [OK]
jaxrs [OK] empty subsystem
jdr - [OK] empty subsystem
jmx [OK]
jpa [OK]
jsf [OK]
jsr77 [OK] empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster [OK]
naming [OK]
osgi [OK]
pojo [OK] empty subsystem
remoting - [OK]
sar [OK] empty subsystem
security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
threads - WIP Brian
transactions - [PR https://github.com/jbossas/jboss-as/pull/3963]
web - [PR https://github.com/jbossas/jboss-as/pull/3963]
webservices - WIP Kabir
weld [OK] empty subsystem
xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups [OK]
> clustering/infinispan
> cmp [OK]
> configadmin [OK]
> connector/datasource
> connector/jca [OK]
> connector/resource-adapter
> deployment-scanner - WIP Kabir
> ee - PR https://github.com/jbossas/jboss-as/pull/3969
> ejb3 [OK]
> jacorb - Just a note: the 'security' attribute transformation is not tested
> jaxr [OK]
> jaxrs [OK] empty subsystem
> jdr - [OK] empty subsystem
> jmx [OK]
> jpa [OK]
> jsf [OK]
> jsr77 [OK] empty subsystem
> logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
> mail
> messaging [OK]
> modcluster [OK]
> naming [OK]
> osgi [OK]
> pojo [OK] empty subsystem
> remoting - [OK]
> sar [OK] empty subsystem
> security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
> threads - WIP Brian
> transactions - [PR https://github.com/jbossas/jboss-as/pull/3963]
> web - [PR https://github.com/jbossas/jboss-as/pull/3963]
> webservices - WIP Kabir
> weld [OK] empty subsystem
> xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6423) JBoss RPM doesn't adhere to LFS
by Paul Gier (JIRA)
[ https://issues.jboss.org/browse/AS7-6423?page=com.atlassian.jira.plugin.s... ]
Paul Gier updated AS7-6423:
---------------------------
Assignee: Fernando Nasser (was: Paul Gier)
> JBoss RPM doesn't adhere to LFS
> -------------------------------
>
> Key: AS7-6423
> URL: https://issues.jboss.org/browse/AS7-6423
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Build System
> Affects Versions: 7.1.2.Final (EAP)
> Environment: Red Hat Enterprise Linux Server release 6.3 (Santiago)
> Reporter: rafael liu
> Assignee: Fernando Nasser
> Priority: Minor
> Labels: rpm
>
> In /usr/share/jbossas/domain links to tmp and data folders were mixed up:
> {noformat}
> [domain]]# ls -l
> total 4
> lrwxrwxrwx. 1 jboss jboss 19 Jan 2 14:45 configuration -> /etc/jbossas/domain
> lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 data -> /var/tmp/jbossas/domain
> lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 log -> /var/log/jbossas/domain
> drwxrwxr-x. 5 jboss jboss 4096 Jan 2 16:02 servers
> lrwxrwxrwx. 1 jboss jboss 25 Jan 2 14:45 tmp -> /var/cache/jbossas/domain
> {noformat}
> In /usr/share/jbossas/standalone tmp folder is not linked:
> {noformat}
> [standalone]# ls -l
> total 12
> lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 configuration -> /etc/jbossas/standalone
> drwxr-xr-x. 2 jboss jboss 4096 Jan 2 14:45 deployments
> drwxr-xr-x. 3 jboss jboss 4096 Jan 2 14:45 lib
> lrwxrwxrwx. 1 jboss jboss 27 Jan 2 14:45 log -> /var/log/jbossas/standalone
> drwxr-xr-x. 3 jboss jboss 4096 Jan 2 14:45 tmp
> {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
13 years, 3 months
[JBoss JIRA] (AS7-6423) JBoss RPM doesn't adhere to LFS
by rafael liu (JIRA)
rafael liu created AS7-6423:
-------------------------------
Summary: JBoss RPM doesn't adhere to LFS
Key: AS7-6423
URL: https://issues.jboss.org/browse/AS7-6423
Project: Application Server 7
Issue Type: Enhancement
Components: Build System
Affects Versions: 7.1.2.Final (EAP)
Environment: Red Hat Enterprise Linux Server release 6.3 (Santiago)
Reporter: rafael liu
Assignee: Paul Gier
Priority: Minor
In /usr/share/jbossas/domain links to tmp and data folders were mixed up:
{noformat}
[domain]]# ls -l
total 4
lrwxrwxrwx. 1 jboss jboss 19 Jan 2 14:45 configuration -> /etc/jbossas/domain
lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 data -> /var/tmp/jbossas/domain
lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 log -> /var/log/jbossas/domain
drwxrwxr-x. 5 jboss jboss 4096 Jan 2 16:02 servers
lrwxrwxrwx. 1 jboss jboss 25 Jan 2 14:45 tmp -> /var/cache/jbossas/domain
{noformat}
In /usr/share/jbossas/standalone tmp folder is not linked:
{noformat}
[standalone]# ls -l
total 12
lrwxrwxrwx. 1 jboss jboss 23 Jan 2 14:45 configuration -> /etc/jbossas/standalone
drwxr-xr-x. 2 jboss jboss 4096 Jan 2 14:45 deployments
drwxr-xr-x. 3 jboss jboss 4096 Jan 2 14:45 lib
lrwxrwxrwx. 1 jboss jboss 27 Jan 2 14:45 log -> /var/log/jbossas/standalone
drwxr-xr-x. 3 jboss jboss 4096 Jan 2 14:45 tmp
{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
13 years, 3 months