[JBoss JIRA] (WFLY-6190) SingletonReentrantTestCase fails with security manager enabled
by Eduardo Silva (JIRA)
[ https://issues.jboss.org/browse/WFLY-6190?page=com.atlassian.jira.plugin.... ]
Eduardo Silva commented on WFLY-6190:
-------------------------------------
Build with the commit: 0ef8325637665d48f8bdffcf2ac4f7f8cb8b9b3f
Date: Thu Mar 3 16:35:49 2016 -0600
Started the application server with standalone.sh and running:
./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.197 sec - in org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WildFly Test Suite: Aggregator ..................... SUCCESS [ 14.161 s]
[INFO] WildFly Test Suite: Integration .................... SUCCESS [ 0.968 s]
[INFO] WildFly Test Suite: Integration - WS ............... SUCCESS [ 0.836 s]
[INFO] WildFly Test Suite: Integration - Basic ............ SUCCESS [ 12.346 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
> SingletonReentrantTestCase fails with security manager enabled
> --------------------------------------------------------------
>
> Key: WFLY-6190
> URL: https://issues.jboss.org/browse/WFLY-6190
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
>
> *org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase#testReadCall*
> *org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase#testWriteCall*
> {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase}}
> fails with
> {code}
> java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "modifyThread")" in code source "(vfs:/content/reentrant-test.jar <no signer certificates>)" of "null")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:735)
> at java.util.concurrent.ThreadPoolExecutor.shutdown(ThreadPoolExecutor.java:1387)
> at java.util.concurrent.Executors$DelegatedExecutorService.shutdown(Executors.java:669)
> at org.jboss.as.test.integration.ejb.singleton.reentrant.SingletonReentrantTestCase.testWriteCall(SingletonReentrantTestCase.java:90)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6192) JAXBUsageTestCase fails with security manager with security manager enabled
by Eduardo Silva (JIRA)
[ https://issues.jboss.org/browse/WFLY-6192?page=com.atlassian.jira.plugin.... ]
Eduardo Silva commented on WFLY-6192:
-------------------------------------
Build with the commit: 0ef8325637665d48f8bdffcf2ac4f7f8cb8b9b3f
Date: Thu Mar 3 16:35:49 2016 -0600
Started the application server with standalone.sh and running:
./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.jaxb.unit.JAXBUsageTestCase#testJAXBServlet
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.test.integration.jaxb.unit.JAXBUsageTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.329 sec - in org.jboss.as.test.integration.jaxb.unit.JAXBUsageTestCase
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WildFly Test Suite: Aggregator ..................... SUCCESS [ 14.382 s]
[INFO] WildFly Test Suite: Integration .................... SUCCESS [ 0.903 s]
[INFO] WildFly Test Suite: Integration - WS ............... SUCCESS [ 0.870 s]
[INFO] WildFly Test Suite: Integration - Basic ............ SUCCESS [ 3.152 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
> JAXBUsageTestCase fails with security manager with security manager enabled
> ---------------------------------------------------------------------------
>
> Key: WFLY-6192
> URL: https://issues.jboss.org/browse/WFLY-6192
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
>
> *org.jboss.as.test.integration.jaxb.unit.JAXBUsageTestCase#testJAXBServlet*
> {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.jaxb.unit.JAXBUsageTestCase#testJAXBServlet}}
> Fails with:
> {code}
> ERROR [io.undertow.request] (default task-46) UT005023: Exception handling request to /jaxb-webapp//jaxbServlet: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "getClassLoader")" in code source "(vfs:/content/jaxb-webapp.war/WEB-INF/classes <no signer certificates>)" of "null")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.Thread.getContextClassLoader(Thread.java:500)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:279)
> at org.jboss.as.test.integration.jaxb.JAXBUsageServlet.doGet(JAXBUsageServlet.java:50)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1$1.run(ServletInitialHandler.java:180)
> at java.security.AccessController.doPrivileged(AccessController.java:650)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:177)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6191) ExpressionSubstitutionInContainerTestCase fails due to AccessControlException with security manager enabled
by Eduardo Silva (JIRA)
[ https://issues.jboss.org/browse/WFLY-6191?page=com.atlassian.jira.plugin.... ]
Eduardo Silva commented on WFLY-6191:
-------------------------------------
Build with the commit: 0ef8325637665d48f8bdffcf2ac4f7f8cb8b9b3f
Date: Thu Mar 3 16:35:49 2016 -0600
Started the application server with standalone.sh and running:
./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInConta
inerTestCase
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInContainerTestCase
Tests run: 6, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.509 sec - in org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInContainerTestCase
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WildFly Test Suite: Aggregator ..................... SUCCESS [ 13.759 s]
[INFO] WildFly Test Suite: Integration .................... SUCCESS [ 0.971 s]
[INFO] WildFly Test Suite: Integration - WS ............... SUCCESS [ 1.097 s]
[INFO] WildFly Test Suite: Integration - Basic ............ SUCCESS [ 4.492 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
> ExpressionSubstitutionInContainerTestCase fails due to AccessControlException with security manager enabled
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6191
> URL: https://issues.jboss.org/browse/WFLY-6191
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
>
> *org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInContainerTestCase*
> {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInContainerTestCase}}
> {code}
> Failed to start service jboss.deployment.unit."expression-substitution-test.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."expression-substitution-test.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "expression-substitution-test.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "getClassLoader")" in code source "(vfs:/content/expression-substitution-test.jar <no signer certificates>)" of "null")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1525)
> at java.lang.Class.getClassLoader(Class.java:683)
> at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1529)
> at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:51)
> at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:2099)
> at org.jboss.msc.service.ServiceControllerImpl.commitInstallation(ServiceControllerImpl.java:265)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:771)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.test.integration.management.api.expression.ExpressionTestManagementService.activate(ExpressionTestManagementService.java:69)
> at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:74)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6324) Upgrade mod_cluster to 1.3.2.Final
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-6324:
------------------------------------
Summary: Upgrade mod_cluster to 1.3.2.Final
Key: WFLY-6324
URL: https://issues.jboss.org/browse/WFLY-6324
Project: WildFly
Issue Type: Component Upgrade
Components: Clustering
Affects Versions: 10.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Needed to resolve JBEAP-1767.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JGRP-2024) Receiving messages out of order.
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2024?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2024.
----------------------------
Resolution: Rejected
Incorrect use of JGroups; test code had 2 bugs
> Receiving messages out of order.
> --------------------------------
>
> Key: JGRP-2024
> URL: https://issues.jboss.org/browse/JGRP-2024
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: RedHat 6.7
> Java 1.8.0 Update 45
> Reporter: Dylan Turnbull
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jGroups Unit Test.zip, JGroupsMessageTest.java, jGroupsTestReciever.java
>
>
> After splitting a file into smaller messages and send them down the channel the messages are received on the other side out of order.
> Below is a sample output:
> *+On the sender:+*
> Sending...
> Data Sent:
> Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy te
> -----------------------------------------------------
> Data Sent:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Sent:
> vived not only five centuries, but also the leap into electronic typesetting, re
> -----------------------------------------------------
> Data Sent:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passag
> *+On the receiver:+*
> Listening...
> Data Received:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Received:
> vived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularise
> -----------------------------------------------------
> Data Received:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JGRP-2024) Receiving messages out of order.
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2024?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-2024 at 3/5/16 3:19 AM:
--------------------------------------------------------
The second bug in your code is in this line:
{code}
channel.send(new Message(null, fileByte, 0, fileByte.length));
{code}
This will read the last line that is less than 128 bytes incorrectly. The correct line should be
{code}
channel.send(new Message(null, fileByte, 0, bytesRead));
{code}
I attached the correct version, you need to change the file paths.
Note that I used JGroups _master_ not 3.6.x, but the change to get it to run on 3.6.x is minimal.
was (Author: belaban):
The second bug in your code is in this line:
{code}
channel.send(new Message(null, fileByte, 0, fileByte.length));
{code}
This will read the last line that is less than 128 bytes incorrectly. The correct line should be
{code}
channel.send(new Message(null, fileByte, 0, bytesRead));
{code}
I attached the correct version, you need to change the file paths.
> Receiving messages out of order.
> --------------------------------
>
> Key: JGRP-2024
> URL: https://issues.jboss.org/browse/JGRP-2024
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: RedHat 6.7
> Java 1.8.0 Update 45
> Reporter: Dylan Turnbull
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jGroups Unit Test.zip, JGroupsMessageTest.java, jGroupsTestReciever.java
>
>
> After splitting a file into smaller messages and send them down the channel the messages are received on the other side out of order.
> Below is a sample output:
> *+On the sender:+*
> Sending...
> Data Sent:
> Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy te
> -----------------------------------------------------
> Data Sent:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Sent:
> vived not only five centuries, but also the leap into electronic typesetting, re
> -----------------------------------------------------
> Data Sent:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passag
> *+On the receiver:+*
> Listening...
> Data Received:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Received:
> vived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularise
> -----------------------------------------------------
> Data Received:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JGRP-2024) Receiving messages out of order.
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2024?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2024:
---------------------------
Attachment: jGroupsTestReciever.java
JGroupsMessageTest.java
> Receiving messages out of order.
> --------------------------------
>
> Key: JGRP-2024
> URL: https://issues.jboss.org/browse/JGRP-2024
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: RedHat 6.7
> Java 1.8.0 Update 45
> Reporter: Dylan Turnbull
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jGroups Unit Test.zip, JGroupsMessageTest.java, jGroupsTestReciever.java
>
>
> After splitting a file into smaller messages and send them down the channel the messages are received on the other side out of order.
> Below is a sample output:
> *+On the sender:+*
> Sending...
> Data Sent:
> Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy te
> -----------------------------------------------------
> Data Sent:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Sent:
> vived not only five centuries, but also the leap into electronic typesetting, re
> -----------------------------------------------------
> Data Sent:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passag
> *+On the receiver:+*
> Listening...
> Data Received:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Received:
> vived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularise
> -----------------------------------------------------
> Data Received:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month