[JBoss JIRA] (AS7-6970) Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6970?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6970:
----------------------------------
Description:
With a socket-binding-group config like the following, the outbound-socket-binding=mail-smtp:add op is not included in the list of boot ops sent to domain server.
{code}
<socket-binding-groups>
<socket-binding-group name="sockets1" default-interface="public">
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="1111"/>
</outbound-socket-binding>
</socket-binding-group>
{code}
was:
With a socket-binding-group config like the following, the no outbound-socket-binding=mail-smtp:add op is included in the list of boot ops sent to domain server.
{code}
<socket-binding-groups>
<socket-binding-group name="sockets1" default-interface="public">
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="1111"/>
</outbound-socket-binding>
</socket-binding-group>
{code}
> Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6970
> URL: https://issues.jboss.org/browse/AS7-6970
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Alpha1
>
>
> With a socket-binding-group config like the following, the outbound-socket-binding=mail-smtp:add op is not included in the list of boot ops sent to domain server.
> {code}
> <socket-binding-groups>
> <socket-binding-group name="sockets1" default-interface="public">
> <outbound-socket-binding name="mail-smtp">
> <remote-destination host="localhost" port="1111"/>
> </outbound-socket-binding>
> </socket-binding-group>
> {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
13 years
[JBoss JIRA] (AS7-6970) Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6970:
-------------------------------------
Summary: Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings
Key: AS7-6970
URL: https://issues.jboss.org/browse/AS7-6970
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 8.0.0.Alpha1
With a socket-binding-group config like the following, the no outbound-socket-binding=mail-smtp:add op is included in the list of boot ops sent to domain server.
{code}
<socket-binding-groups>
<socket-binding-group name="sockets1" default-interface="public">
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="1111"/>
</outbound-socket-binding>
</socket-binding-group>
{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
13 years
[JBoss JIRA] (AS7-6923) Undertow breaks some JSF apps
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6923?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas resolved AS7-6923.
---------------------------------
Resolution: Done
> Undertow breaks some JSF apps
> -----------------------------
>
> Key: AS7-6923
> URL: https://issues.jboss.org/browse/AS7-6923
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF, Web
> Affects Versions: 8.0.0.Alpha1
> Reporter: Stan Silvert
> Assignee: Stuart Douglas
> Priority: Critical
> Attachments: InjectionTest.zip
>
>
> Undertow breaks some JSF apps. I haven't narrowed the problem down yet but I want to go ahead and post this JIRA because it is a blocker for AS8.
> I'm attaching a small JSF project that demonstrates the problem. When you run the WAR with -c standalone-jbossweb.xml it works fine.
> With Undertow it breaks. You are unable to navigate based on the return value of a MethodExpression.
> Also, you get this warning:
> {noformat}
> 12:17:30,572 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (default task-1) JSF1091: No mime type could be found for file /index.xhtml. To resolve this, add a mime-type mapping to the applications web.xml.
> {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
[JBoss JIRA] (AS7-6968) Building with IBM JDK 7
by Paul Gier (JIRA)
Paul Gier created AS7-6968:
------------------------------
Summary: Building with IBM JDK 7
Key: AS7-6968
URL: https://issues.jboss.org/browse/AS7-6968
Project: Application Server 7
Issue Type: Feature Request
Components: Build System
Reporter: Paul Gier
Assignee: Paul Gier
Priority: Minor
Fix For: 8.0.0.Alpha1
There are a couple of problems that occur when building with IBM JDK 7: unit test failures in OSGi modules, and a maven enforcer failure. These should be fixed so that the testsuite can easily be run using IBM JDK 7.
--
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
[JBoss JIRA] (AS7-6790) Multi-JSF doesn't understand new modules structure
by Stan Silvert (JIRA)
[ https://issues.jboss.org/browse/AS7-6790?page=com.atlassian.jira.plugin.s... ]
Stan Silvert commented on AS7-6790:
-----------------------------------
Glenn, what version of AS are you working on? What JSF version do you want to install?
I think I am going to just post lots of CLI installation files for different AS/JSF combos. So if you give me that info I'll make you one right away and post it here for you to try.
> Multi-JSF doesn't understand new modules structure
> --------------------------------------------------
>
> Key: AS7-6790
> URL: https://issues.jboss.org/browse/AS7-6790
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Stan Silvert
> Assignee: Stan Silvert
>
> With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default.
> The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script.
> See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789
--
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
[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6616:
----------------------------------------------
Paul Gier <pgier(a)redhat.com> made a comment on [bug 921574|https://bugzilla.redhat.com/show_bug.cgi?id=921574]
> AS 8: Testsuite fails on Solaris SPARC 10
> -----------------------------------------
>
> Key: AS7-6616
> URL: https://issues.jboss.org/browse/AS7-6616
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41
> Reporter: Frank Langelage
> Assignee: jaikiran pai
> Fix For: 8.0.0.Alpha1
>
> Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml
>
>
> Compiling the current sources from github fails for me on this environment.
> On Windows everything is fine.
> Compiling 7.2.0.Final works in this environment.
> But regarding this test, nothing seems to have changed in between.
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec
> Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec
> Running org.jboss.as.naming.InitialContextTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE!
> Running org.jboss.as.naming.InitialContextFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
> Running org.jboss.as.naming.NamingEventCoordinatorTestCase
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
> Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec
> Running org.jboss.as.naming.InMemoryNamingStoreTestCase
> Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
> Running org.jboss.as.naming.ObjectFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
> Running org.jboss.as.naming.NamingContextTestCase
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec
> Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec
> Results :
> Tests in error:
> testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null
> Tests run: 70, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s]
> [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s]
> [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s]
> [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s]
> [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s]
> [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Clustering Server API ... SKIPPED
> [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
> [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Clustered registry service SKIPPED
> [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
> [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
> [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
> [INFO] JBoss Application Server: Config Assembly ......... SKIPPED
> [INFO] JBoss Application Server: Command line interface .. SKIPPED
> [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
> [INFO] JBoss Application Server: Clustered singleton services SKIPPED
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
> [INFO] JBoss Application Server: Config Admin ............ SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: EE Deployment ........... SKIPPED
> [INFO] JBoss Application Server: Embedded ................ SKIPPED
> [INFO] JBoss Application Server: JAXR Client ............. SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JPA SPI ................. SKIPPED
> [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
> [INFO] JBoss Application Server: JDR ..................... SKIPPED
> [INFO] JBoss Application Server: JSF ..................... SKIPPED
> [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED
> [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED
> [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: System JMX Module ....... SKIPPED
> [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Build Modular ........... SKIPPED
> [INFO] JBoss Application Server: Arquillian .............. SKIPPED
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
> [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
> [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED
> [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED
> [INFO] JBoss Application Server: Distribution ............ SKIPPED
> [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
> [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6:36.380s
> [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013
> [INFO] Final Memory: 122M/348M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures.
> [ERROR]
> [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-naming
--
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
[JBoss JIRA] (AS7-6790) Multi-JSF doesn't understand new modules structure
by Glenn Kastrinos (JIRA)
[ https://issues.jboss.org/browse/AS7-6790?page=com.atlassian.jira.plugin.s... ]
Glenn Kastrinos edited comment on AS7-6790 at 4/22/13 5:11 PM:
---------------------------------------------------------------
Using MyFaces:
For the workaround, I'm still not sure exactly what we need to have in the modules folder. After doing everything else (Stan Silvert's CLI installation, modifying my module.xml files, etc.) I copied everything from modules/system/layers/base into a folder called "test", put it in the modules directory, changed the JBOSS_MODULEPATH to %JBOSS_HOME%\modules\test, and it won't start, saying it can't parse the configuration. I can't just copy all the little directories from layers/base into modules because there are already folders named com, javaee, org, and javax (system as well, but not in layers/base). I put the original com, javaee, org, and javax folders into a temp directory and pasted the contents of layers/base into modules (with system still there) but still got the config error (after fixing the modulepath). So I renamed the duplicates and put everything into the modules folder, but am back to the same old:
Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory
error.
Any idea what I'm missing? What folder structure did you use? As in, what folers/files should I have in my modules directory? THANK YOU I've been working on this for weeks
Also, myfaces is my only JSF implementation and it is set to default.
was (Author: glennk):
For the workaround, I'm still not sure exactly what we need to have in the modules folder. After doing everything else (Stan Silvert's CLI installation, modifying my module.xml files, etc.) I copied everything from modules/system/layers/base into a folder called "test", put it in the modules directory, changed the JBOSS_MODULEPATH to %JBOSS_HOME%\modules\test, and it won't start, saying it can't parse the configuration. I can't just copy all the little directories from layers/base into modules because there are already folders named com, javaee, org, and javax (system as well, but not in layers/base). I put the original com, javaee, org, and javax folders into a temp directory and pasted the contents of layers/base into modules (with system still there) but still got the config error (after fixing the modulepath). So I renamed the duplicates and put everything into the modules folder, but am back to the same old:
Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory
error.
Any idea what I'm missing? What folder structure did you use? As in, what folers/files should I have in my modules directory? THANK YOU I've been working on this for weeks
> Multi-JSF doesn't understand new modules structure
> --------------------------------------------------
>
> Key: AS7-6790
> URL: https://issues.jboss.org/browse/AS7-6790
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Stan Silvert
> Assignee: Stan Silvert
>
> With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default.
> The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script.
> See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789
--
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