[JBoss JIRA] Created: (JBAS-8380) Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server
3:03 a.m.
Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server
-----------------------------------------------------------------------------------
Key: JBAS-8380
URL: https://jira.jboss.org/browse/JBAS-8380
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: EJB3
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.0.0.CR1
The EJB3 timerservice-mk2.jar is only applicable for EJB3.x beans. So if there are no
EJB3.x deployments in the server, then there's no point in deploying that
timerservice-mk2.jar. Deploying that jar on-demand (i.e. when the first EJB3.x deployment
becomes available) is also going to improve the AS boot time.
The referenced forum thread has more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:11 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8380) Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server
[
https://jira.jboss.org/browse/JBAS-8380?page=com.atlassian.jira.plugin.sy...
]
jaikiran pai resolved JBAS-8380.
--------------------------------
Resolution: Done
Done in r107944.
Smoke tests pass:
smoke-tests-raw:
[echo]
[echo] junit.timeout: 300000
[echo] jbosstest.iterationcount: 10
[echo] jbosstest.threadcount: 5
[echo] jbosstest.beancount: 5
[echo]
[mkdir] Created dir:
/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/testsuite/output/log
[junit] Running org.jboss.test.aop.test.AOPUnitTestCase
[junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 8.21 sec
[junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 5.489 sec
[junit] Running org.jboss.test.cts.test.BmpUnitTestCase
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 16.871 sec
[junit] Running org.jboss.test.cts.test.CmpUnitTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.129 sec
[junit] Running org.jboss.test.cts.test.CtsCmp2OptionDUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 18.104 sec
[junit] Running org.jboss.test.cts.test.CtsCmp2UnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.546 sec
[junit] Running org.jboss.test.cts.test.IndependentJarsUnitTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.463 sec
[junit] Running org.jboss.test.cts.test.MDBUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.851 sec
[junit] Running org.jboss.test.cts.test.NestedUserTransactionUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.32 sec
[junit] Running org.jboss.test.cts.test.StatelessSessionBrokenCreateUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.138 sec
[junit] Running org.jboss.test.cts.test.StatelessSessionUnitTestCase
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 28.021 sec
[junit] Running org.jboss.test.ejb3.test.SimpleSessionUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4.771 sec
[junit] Running org.jboss.test.jbossmessaging.test.JoramUnitTestCase
[junit] Tests run: 197, Failures: 0, Errors: 0, Time elapsed: 28.334 sec
[junit] Running org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 29.269 sec
[junit] Running org.jboss.test.jca.test.PoolingUnitTestCase
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 2.192 sec
[junit] Running org.jboss.test.jca.test.XADSUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.296 sec
[junit] Running org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.237 sec
[junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.225 sec
[junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.99 sec
[junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.4 sec
[junit] Running org.jboss.test.naming.test.SimpleUnitTestCase
[junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 5.436 sec
[junit] Running org.jboss.test.tm.test.TransactionManagerUnitTestCase
[junit] Tests run: 28, Failures: 0, Errors: 0, Time elapsed: 0.631 sec
[junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase
[junit] Tests run: 38, Failures: 0, Errors: 0, Time elapsed: 9.857 sec
[junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 10.327 sec
check.smoke.test.failure:
[server:stop] Shutting down server: all
[server:stop] log4j:WARN No appenders could be found for logger
(org.jnp.interfaces.TimedSocketFactory).
[server:stop] log4j:WARN Please initialize the log4j system properly.
[server:stop] shutdownTimeout will be=45
[server:stop] Server stopped.
BUILD SUCCESSFUL
Total time: 4 minutes 26 seconds
Deploy the timerservice-mk2 jar only when there's a EJB3.x
deployment in the server
-----------------------------------------------------------------------------------
Key: JBAS-8380
URL: https://jira.jboss.org/browse/JBAS-8380
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EJB3
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.0.0.CR1
The EJB3 timerservice-mk2.jar is only applicable for EJB3.x beans. So if there are no
EJB3.x deployments in the server, then there's no point in deploying that
timerservice-mk2.jar. Deploying that jar on-demand (i.e. when the first EJB3.x deployment
becomes available) is also going to improve the AS boot time.
The referenced forum thread has more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8380) Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server
[
https://jira.jboss.org/browse/JBAS-8380?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan resolved JBAS-8380.
----------------------------------
Fix Version/s: 6.0.0.M5
(was: 6.0.0.CR1)
Resolution: Done
Deploy the timerservice-mk2 jar only when there's a EJB3.x
deployment in the server
-----------------------------------------------------------------------------------
Key: JBAS-8380
URL: https://jira.jboss.org/browse/JBAS-8380
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EJB3
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.0.0.M5
The EJB3 timerservice-mk2.jar is only applicable for EJB3.x beans. So if there are no
EJB3.x deployments in the server, then there's no point in deploying that
timerservice-mk2.jar. Deploying that jar on-demand (i.e. when the first EJB3.x deployment
becomes available) is also going to improve the AS boot time.
The referenced forum thread has more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [JBoss JIRA] Reopened: (JBAS-8380) Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server
[
https://jira.jboss.org/browse/JBAS-8380?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan reopened JBAS-8380:
----------------------------------
Deploy the timerservice-mk2 jar only when there's a EJB3.x
deployment in the server
-----------------------------------------------------------------------------------
Key: JBAS-8380
URL: https://jira.jboss.org/browse/JBAS-8380
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EJB3
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.0.0.M5
The EJB3 timerservice-mk2.jar is only applicable for EJB3.x beans. So if there are no
EJB3.x deployments in the server, then there's no point in deploying that
timerservice-mk2.jar. Deploying that jar on-demand (i.e. when the first EJB3.x deployment
becomes available) is also going to improve the AS boot time.
The referenced forum thread has more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5032
days inactive
5054
days old
3 comments
2 participants
participants (2)
-
jaikiran pai (JIRA) -
Shelly McGowan (JIRA)