[JBoss JIRA] (AS7-4711) Behaviour with datasources and the enabled attribute
by Michael Voegele (JIRA)
Michael Voegele created AS7-4711:
------------------------------------
Summary: Behaviour with datasources and the enabled attribute
Key: AS7-4711
URL: https://issues.jboss.org/browse/AS7-4711
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Scott Marlow
I have following test configuration, mind the attribute enabled="false":
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:1.0">
<datasources>
<datasource enabled="false" jta="true" jndi-name="java:jboss/jdbc/Db2NonXaDataSource" pool-name="DB2DSPool" use-java-context="true" use-ccm="true">
<connection-url>jdbc:db2://ddb-dintalc:50006/UALC</connection-url>
<driver>db2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>s01talc</user-name>
<password>Not4You</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>
<drivers>
<driver name="db2" module="com.ibm.db2.v4_3_85">
<xa-datasource-class>com.ibm.db2.jcc.DB2Driver</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
1. I start the server (standalone mode, I did not check domain mode). The attribute is still the same, enabled="false".
In an ejb, a persistence unit references the datasource:
@PersistenceContext(unitName = "db2_persistence_unit")
private EntityManager entityManager;
2. Now I deploy (maven-ear-plugin or just drop in deployments dir) the ear. The configuration is changed automatically, the attribute is not there anymore:
{code:xml}
<datasource jta="true" jndi-name="java:jboss/jdbc/Db2NonXaDataSource" pool-name="DB2DSPool" use-java-context="true" use-ccm="true">
<connection-url>jdbc:db2://ddb-dintalc:50006/UALC</connection-url>
<driver>db2</driver>
...
{code}
The application works, the datasource is available, so it is enabled in the background.
3. Now just restart the server.
Outcome:
{code:java}
2012-05-04 13:30:53,817 [MSC service thread 1-1] ERROR org.jboss.msc.service.fail - MSC00001: Failed to start service jboss.deployment.subunit."jet-demo-ear-0.0.1-SNAPSHOT.ear"."jet-demo-ejb-0.0.1-SNAPSHOT.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."jet-demo-ear-0.0.1-SNAPSHOT.ear"."jet-demo-ejb-0.0.1-SNAPSHOT.jar".INSTALL: Failed to process phase INSTALL of subdeployment "jet-demo-ejb-0.0.1-SNAPSHOT.jar" of deployment "jet-demo-ear-0.0.1-SNAPSHOT.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS010464: Exception deploying datasource java:jboss/jdbc/Db2NonXaDataSource
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:125)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.jboss.jdbc.Db2NonXaDataSource is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:309)
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:123)
... 6 more
{code}
So the deployment fails. The same happens when the server is started with enabled datasource and then deploying the app.
This behaviour came with 7.1.1.Final, before it worked as expected.
--
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
13 years, 11 months
[JBoss JIRA] (AS7-4603) Controller incorrectly reports missing service dependencies
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-4603:
-----------------------------------
Summary: Controller incorrectly reports missing service dependencies
Key: AS7-4603
URL: https://issues.jboss.org/browse/AS7-4603
Project: Application Server 7
Issue Type: Bug
Components: Server
Reporter: Thomas Diesler
Assignee: Jason Greene
On OSGi subsystem activation the server may report missing/unsatisfied dependencies.
However, that service is in fact installed and active. Otherwise, the framework would not initialize let alone start.
{code}
12:48:39,952 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011004: JBossOSGi Framework Core - 1.3.0.CR9
12:48:41,036 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011009: Starting bundles for start level: 1
12:48:41,039 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: osgi.enterprise:4.2.0.201003190513
12:48:41,041 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: javax.servlet.api:2.5.0.Final
12:48:41,060 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: jboss-osgi-logging:1.0.0
12:48:41,072 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: jboss-as-osgi-configadmin:7.1.2.Final-SNAPSHOT
12:48:41,074 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011000: OSGi Framework started
12:48:41,352 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "foo"
12:48:41,353 INFO [org.jboss.as.controller] (management-handler-thread - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jbosgi.integration.AutoInstallHandler.COMPLETE (missing) dependents: [service jbosgi.integration.PersistentBundlesHandler, service jbosgi.framework.INIT]
{code}
A possible source of the issue is that the service in question (jbosgi.integration.AutoInstallHandler.COMPLETE) gets added by a listener and is not part of the normal service dependency chain.
--
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
13 years, 11 months
[JBoss JIRA] (AS7-4513) SessionEJB.create not working in EJB 2.1
by Sibylle Boeck (JIRA)
Sibylle Boeck created AS7-4513:
----------------------------------
Summary: SessionEJB.create not working in EJB 2.1
Key: AS7-4513
URL: https://issues.jboss.org/browse/AS7-4513
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1.Final
Environment: Win7, J2EE Application with EJB2.1 and Tomcat, Xdoclet
Reporter: Sibylle Boeck
Assignee: Jason Greene
We try to port our application (running fine under JBossAS 5) to JBoss 7, but we get the following IllegalState exception in startup. We use the standard empty create() Metod :
15:40:22,773 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for sess
bean named DBMediumType in deployment unit subdeployment "diaryinfo.jar" of deployment "diaryinfo.ear" are as follows:
java:global/diaryinfo/diaryinfo.jar/DBMediumType!com.mediit.diaryinfo.interfaces.DBMediumTypeLocalHome
java:app/diaryinfo.jar/DBMediumType!com.mediit.diaryinfo.interfaces.DBMediumTypeLocalHome
java:module/DBMediumType!com.mediit.diaryinfo.interfaces.DBMediumTypeLocalHome
java:global/diaryinfo/diaryinfo.jar/DBMediumType!com.mediit.diaryinfo.interfaces.DBMediumTypeLocal
java:app/diaryinfo.jar/DBMediumType!com.mediit.diaryinfo.interfaces.DBMediumTypeLocal
java:module/DBMediumType!com.mediit.diaryinfo.interfaces.DBMediumTypeLocal
15:40:24,351 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'InstitutionInterfaceReceiverMDB' with 'hor
q-ra' resource adapter
15:40:24,507 INFO [com.mediit.diaryinfo.web.filter.SignOnFilter] (MSC service thread 1-1) init()
15:40:24,523 ERROR [org.jboss.ejb3.invocation] (MSC service thread 1-1) JBAS014134: EJB Invocation failed on component DiaryinfoManager for method
lic abstract com.mediit.diaryinfo.interfaces.DiaryinfoManagerLocal com.mediit.diaryinfo.interfaces.DiaryinfoManagerLocalHome.create() throws javax.
.CreateException: javax.ejb.EJBException: java.lang.IllegalStateException
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar
1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$2.processInvocation(EjbExceptionTransformingInterc
orFactories.java:89) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.ja
.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3
1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at com.mediit.diaryinfo.interfaces.DiaryinfoManagerLocalHome$$$view60.create(Unknown Source) [diaryinfo.jar:]
at com.mediit.diaryinfo.web.filter.SignOnFilter.init(SignOnFilter.java:83)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3865)
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_31]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_31]
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.ejb3.component.interceptors.SessionBeanHomeInterceptorFactory$1.processInvocation(SessionBeanHomeInterceptorFactory.java:62
jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
... 32 more
15:40:24,632 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/diaryinfo]] (MSC service thread 1-1) Exception starting fil
signon: javax.ejb.EJBException: java.lang.IllegalStateException
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar
1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$2.processInvocation(EjbExceptionTransformingInterc
orFactories.java:89) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.ja
.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3
1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at com.mediit.diaryinfo.interfaces.DiaryinfoManagerLocalHome$$$view60.create(Unknown Source) [diaryinfo.jar:]
at com.mediit.diaryinfo.web.filter.SignOnFilter.init(SignOnFilter.java:83) [classes:]
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_31]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_31]
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.ejb3.component.interceptors.SessionBeanHomeInterceptorFactory$1.processInvocation(SessionBeanHomeInterceptorFactory.java:62
jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
... 32 more
15:40:24,726 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Error filterStart
15:40:24,726 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Context [/diaryinfo] startup failed due to previous errors
15:40:24,757 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.web.deployment.default-host./diary
o: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./diaryinfo: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_31]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_31]
15:40:24,773 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015951: Admin console listening on http://127.0.0.1:9990
15:40:24,773 ERROR [org.jboss.as] (MSC service thread 1-3) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 9328ms - Started 299
f 3543 services (459 services failed or missing dependencies, 84 services are passive or on-demand)
--
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
13 years, 11 months
[JBoss JIRA] (AS7-4675) Memory leak when reading EJB 2.1 CMP EntityBeans
by Klaus Benary (JIRA)
Klaus Benary created AS7-4675:
---------------------------------
Summary: Memory leak when reading EJB 2.1 CMP EntityBeans
Key: AS7-4675
URL: https://issues.jboss.org/browse/AS7-4675
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build
Reporter: Klaus Benary
Assignee: jaikiran pai
After reading 12000 EJB 2.1 EntityBeans in a test application there are about 5 million Interceptor[] arrays firmely bound in the heap. A heap dump shows this as a typical reference chain:
GC Root: ServiceContainerImpl$ServiceThread
ServiceContainerImpl$ServiceThread.container = ServiceContainerImpl
ServiceContainerImpl.registry = UnlockedReadHashMap
UnlockedReadHashMap.table = AtomicReferenceArray
AtomicReferenceArray.array = Object[16384]
Object[6209] = UnlockedReadHashMap$Item[3]
UnlockedReadHashMap$Item[1] = UnlockedReadHashMap$Item
UnlockedReadHashMap$Item.value = ServiceRegistrationImpl
ServiceRegistrationImpl.instance = ServiceControllerImpl
ServiceControllerImpl.serviceValue = ImmediateValue
ImmediateValue.value = TimedObjectInvokerImpl
TimedObjectInvokerImpl.timeoutInterceptors = HashMap
HashMap.table = HashMap$Entry[128]
HashMap$Entry[123] = HashMap$Entry
HashMap$Entry.value = ChainedInterceptor
ChainedInterceptor.interceptors = Arrays$ArrayList
Arrays$ArrayList.a = Interceptor[6]
The number of bound objects keeps growing when reading more EntityBeans - even wehn reading the same beans again.
Even after undeploy of the application the
--
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
13 years, 11 months
[JBoss JIRA] Created: (JBAS-8966) Seam 2 Reexplode causes full undeploy + deploy on AS6
by Cody Lerum (JIRA)
Seam 2 Reexplode causes full undeploy + deploy on AS6
-----------------------------------------------------
Key: JBAS-8966
URL: https://issues.jboss.org/browse/JBAS-8966
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final
Environment: JBoss AS 6 Final, Seam 2.2.1
Reporter: Cody Lerum
After upgrading an existing seam 2 project which runs on AS 4.2.3 to run on AS 6 I'm seeing an issue where if I run an reexplode from the seam-gen ant build the application server does a full undeploy and then deploy of the app. This kills any development as I should be able to edit an jsf xhtml page and have that reflected immediately without having to redeploy.
Appears the redeploy scanner is too aggressive or seam-gen is copying over something that worked for reexplode in AS4 but not in AS6
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months