You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Vikas Phonsa <VP...@mercuryinsurance.com> on 2008/06/24 17:46:21 UTC
Exceptions with Repository running against DB2
Hi All,
I'm using JBOSS Rules BRMS application, which uses Jackrabbit.
The repository is connected to a DB2 database.
I've deployed the application on Weblogic. It works fine for the most
part.
But every time the repository starts up I see the exception listed
below.
And eventually, I start seeing OutofMemory errors in the server log.
Can't say if the two issues are related, but has anybody experienced any
such problem ?
I'm also listing my FileSystem and PersistanceManager configurations
below.
Thanks in advance for any feedback.
Regards,
Vikas
------------------------ Repository Config------------------------------
<FileSystem
class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
<param name="driver"
value="com.ibm.db2.jcc.DB2Driver"/>
<param name="url"
value="jdbc:db2://localhost:50000/Drools"/>
<param name="schema" value="db2"/>
<param name="user" value="test"/>
<param name="password" value="testpw"/>
<param name="schemaObjectPrefix"
value="${wsp.name}_FS_"/>
</FileSystem>
<PersistenceManager
class="org.apache.jackrabbit.core.persistence.db.SimpleDbPersistenceMana
ger">
<param name="driver" value="com.ibm.db2.jcc.DB2Driver"/>
<param name="url"
value="jdbc:db2://localhost:50000/Drools"/>
<param name="schema" value="test"/>
<param name="user" value="vphonsa"/>
<param name="password" value="testpw"/>
<param name="schemaObjectPrefix" value="${wsp.name}_"/>
<param name="externalBLOBs" value="false"/>
</PersistenceManager>
--------------------Exception Stack Trace------------------------------
ERROR 23-06 17:45:34,571 (RepositoryImpl.java:dispose:1890) error
while closing persistence manager of workspace MBR_WS
com.ibm.db2.jcc.b.SqlException: [jcc][t4][10251][10308][3.50.152]
java.sql.Connection.close() requested while a transaction is in progress
on the connection.
The transaction remains active, and the connection cannot be closed.
ERRORCODE=-4471, SQLSTATE=null
at com.ibm.db2.jcc.b.wc.a(wc.java:55)
at com.ibm.db2.jcc.b.wc.a(wc.java:119)
at com.ibm.db2.jcc.b.eb.t(eb.java:996)
at com.ibm.db2.jcc.b.eb.w(eb.java:1019)
at com.ibm.db2.jcc.b.eb.u(eb.java:1005)
at com.ibm.db2.jcc.b.eb.close(eb.java:989)
at
org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.clo
seConnection(DatabasePersistenceManager.java:765)
at
org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.clo
se(DatabasePersistenceManager.java:253)
at
org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.dispose(Reposito
ryImpl.java:1888)
at
org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.java
:1009)
at
org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java:9
63)
at
org.apache.jackrabbit.core.TransientRepository.stopRepository(TransientR
epository.java:275)
at
org.apache.jackrabbit.core.TransientRepository.loggedOut(TransientReposi
tory.java:427)
at
org.apache.jackrabbit.core.SessionImpl.notifyLoggedOut(SessionImpl.java:
559)
at
org.apache.jackrabbit.core.SessionImpl.logout(SessionImpl.java:1295)
at
org.apache.jackrabbit.core.XASessionImpl.logout(XASessionImpl.java:379)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
SRepositoryConfiguration.java:66)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
SRepositoryConfiguration.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
at
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationCon
text.java:31)
at
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
text.java:56)
at
org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInte
rceptor.java:31)
at
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
text.java:68)
at
org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextI
nterceptor.java:42)
at
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
text.java:68)
at
org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106
)
at
org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBea
nInterceptor.java:155)
at
org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.
java:91)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration_$$_javassi
st_0.create(BRMSRepositoryConfiguration_$$_javassist_0.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
at
org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
at
org.jboss.seam.Component.callComponentMethod(Component.java:2087)
at
org.jboss.seam.Component.callCreateMethod(Component.java:2010)
at org.jboss.seam.Component.newInstance(Component.java:1981)
at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
at
org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecy
cle.java:95)
at
org.jboss.seam.init.Initialization.init(Initialization.java:554)
at
org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java
:34)
at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(Ev
entsManager.java:376)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(Events
Manager.java:82)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
rvletContext.java:1609)
at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
t.java:2764)
at
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:8
89)
at
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
river.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:26)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
iver.java:60)
at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule
Driver.java:200)
at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis
tenerInvoker.java:117)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
river.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:26)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
iver.java:60)
at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModule
sFlow.java:26)
at
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
635)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:26)
at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.jav
a:212)
at
weblogic.application.internal.DeploymentStateChecker.activate(Deployment
StateChecker.java:154)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppCo
ntainerInvoker.java:80)
at
weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDepl
oyment.java:181)
at
weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServer
Lifecycle(BasicDeployment.java:358)
at
weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(Deplo
ymentAdapter.java:52)
at
weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploymen
tAdapter.java:186)
at
weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTra
nsition.java:30)
at
weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
(ConfiguredDeployments.java:254)
at
weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
(ConfiguredDeployments.java:239)
at
weblogic.management.deploy.internal.ConfiguredDeployments.activate(Confi
guredDeployments.java:169)
at
weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Configu
redDeployments.java:123)
at
weblogic.management.deploy.internal.DeploymentServerService.resume(Deplo
ymentServerService.java:173)
at
weblogic.management.deploy.internal.DeploymentServerService.start(Deploy
mentServerService.java:89)
at
weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
Re: Exceptions with Repository running against DB2
Posted by Alexander Klimetschek <ak...@day.com>.
Well, it was introduced with 1.3 (I think). Have a look at your
jackrabbit-core jar, all persistence managers (inside
org.apache.jackrabbit.core.persistence) you will find there can be
used. BundleDB pm is part of it.
Regards,
Alex
On Tue, Jun 24, 2008 at 1:21 PM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> Alex,
>
> I read ( somewhere on JackRabbit site) that BundleDbPersistenceManager
> offers good performance when used with a DataStore, but you need
> JackRabbit 1.4 to do that. But my JBOSS BRMS app uses JackRabbit 1.3,
> that's why I decided to just use the SimpleDbPersistanceManager.
>
> Can BundleDbPersistenceManager be used with Jackrabbit 1.3 ?
>
> Thanks,
> Vikas
>
> -----Original Message-----
> From: Alexander Klimetschek [mailto:aklimets@day.com]
> Sent: Tuesday, June 24, 2008 9:25 AM
> To: users@jackrabbit.apache.org
> Subject: Re: Exceptions with Repository running against DB2
>
> I would recommend to use a bundle db persistence manager:
>
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
>
> It should be better regarding DB connections and has better performance
> than the simple db pm.
>
> Regards,
> Alex
>
> On Tue, Jun 24, 2008 at 11:46 AM, Vikas Phonsa
> <VP...@mercuryinsurance.com> wrote:
>> Hi All,
>>
>> I'm using JBOSS Rules BRMS application, which uses Jackrabbit.
>>
>> The repository is connected to a DB2 database.
>>
>> I've deployed the application on Weblogic. It works fine for the most
>> part.
>>
>> But every time the repository starts up I see the exception listed
>> below.
>>
>> And eventually, I start seeing OutofMemory errors in the server log.
>>
>> Can't say if the two issues are related, but has anybody experienced
>> any such problem ?
>>
>> I'm also listing my FileSystem and PersistanceManager configurations
>> below.
>>
>> Thanks in advance for any feedback.
>>
>> Regards,
>> Vikas
>>
>>
>>
>> ------------------------ Repository
>> Config------------------------------
>>
>> <FileSystem
>> class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
>> <param name="driver"
>> value="com.ibm.db2.jcc.DB2Driver"/>
>> <param name="url"
>> value="jdbc:db2://localhost:50000/Drools"/>
>> <param name="schema" value="db2"/>
>>
>> <param name="user" value="test"/>
>> <param name="password" value="testpw"/>
>> <param name="schemaObjectPrefix"
>> value="${wsp.name}_FS_"/>
>> </FileSystem>
>>
>>
>> <PersistenceManager
>> class="org.apache.jackrabbit.core.persistence.db.SimpleDbPersistenceMa
>> na
>> ger">
>> <param name="driver" value="com.ibm.db2.jcc.DB2Driver"/>
>> <param name="url"
>> value="jdbc:db2://localhost:50000/Drools"/>
>> <param name="schema" value="test"/>
>> <param name="user" value="vphonsa"/>
>> <param name="password" value="testpw"/>
>> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
>> <param name="externalBLOBs" value="false"/>
>> </PersistenceManager>
>>
>>
>>
>> --------------------Exception Stack
>> Trace------------------------------
>>
>> ERROR 23-06 17:45:34,571 (RepositoryImpl.java:dispose:1890) error
>> while closing persistence manager of workspace MBR_WS
>> com.ibm.db2.jcc.b.SqlException: [jcc][t4][10251][10308][3.50.152]
>> java.sql.Connection.close() requested while a transaction is in
>> progress on the connection.
>> The transaction remains active, and the connection cannot be closed.
>> ERRORCODE=-4471, SQLSTATE=null
>> at com.ibm.db2.jcc.b.wc.a(wc.java:55)
>> at com.ibm.db2.jcc.b.wc.a(wc.java:119)
>> at com.ibm.db2.jcc.b.eb.t(eb.java:996)
>> at com.ibm.db2.jcc.b.eb.w(eb.java:1019)
>> at com.ibm.db2.jcc.b.eb.u(eb.java:1005)
>> at com.ibm.db2.jcc.b.eb.close(eb.java:989)
>> at
>> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.c
>> lo
>> seConnection(DatabasePersistenceManager.java:765)
>> at
>> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.c
>> lo
>> se(DatabasePersistenceManager.java:253)
>> at
>> org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.dispose(Reposi
>> to
>> ryImpl.java:1888)
>> at
>> org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.ja
>> va
>> :1009)
>> at
>> org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java
>> :9
>> 63)
>> at
>> org.apache.jackrabbit.core.TransientRepository.stopRepository(Transien
>> tR
>> epository.java:275)
>> at
>> org.apache.jackrabbit.core.TransientRepository.loggedOut(TransientRepo
>> si
>> tory.java:427)
>> at
>>
> org.apache.jackrabbit.core.SessionImpl.notifyLoggedOut(SessionImpl.java:
>> 559)
>> at
>> org.apache.jackrabbit.core.SessionImpl.logout(SessionImpl.java:1295)
>> at
>>
> org.apache.jackrabbit.core.XASessionImpl.logout(XASessionImpl.java:379)
>> at
>> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(B
>> RM
>> SRepositoryConfiguration.java:66)
>> at
>> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(B
>> RM
>> SRepositoryConfiguration.java:56)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
>> av
>> a:64)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
>> or
>> Impl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:615)
>> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
>> at
>> org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationC
>> on
>> text.java:31)
>> at
>> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationC
>> on
>> text.java:56)
>> at
>> org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackIn
>> te
>> rceptor.java:31)
>> at
>> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationC
>> on
>> text.java:68)
>> at
>> org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContex
>> tI
>> nterceptor.java:42)
>> at
>> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationC
>> on
>> text.java:68)
>> at
>> org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:1
>> 06
>> )
>> at
>> org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaB
>> ea
>> nInterceptor.java:155)
>> at
>>
> org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.
>> java:91)
>> at
>> org.drools.brms.server.repository.BRMSRepositoryConfiguration_$$_javas
>> si
>> st_0.create(BRMSRepositoryConfiguration_$$_javassist_0.java)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
>> av
>> a:64)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
>> or
>> Impl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:615)
>> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
>> at
>> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
>> at
>> org.jboss.seam.Component.callComponentMethod(Component.java:2087)
>> at
>> org.jboss.seam.Component.callCreateMethod(Component.java:2010)
>> at org.jboss.seam.Component.newInstance(Component.java:1981)
>> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
>> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
>> at
>> org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLife
>> cy
>> cle.java:95)
>> at
>> org.jboss.seam.init.Initialization.init(Initialization.java:554)
>> at
>> org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.ja
>> va
>> :34)
>> at
>> weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(
>> Ev
>> entsManager.java:376)
>> at
>> weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticated
>> Su
>> bject.java:321)
>> at
>> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:1
>> 21
>> )
>> at
>> weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(Even
>> ts
>> Manager.java:82)
>> at
>> weblogic.servlet.internal.WebAppServletContext.preloadResources(WebApp
>> Se
>> rvletContext.java:1609)
>> at
>> weblogic.servlet.internal.WebAppServletContext.start(WebAppServletCont
>> ex
>> t.java:2764)
>> at
>> weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java
>> :8
>> 89)
>> at
>> weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
>> at
>> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStat
>> eD
>> river.java:204)
>> at
>> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDr
>> iv
>> er.java:26)
>> at
>> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleState
>> Dr
>> iver.java:60)
>> at
>> weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModu
>> le
>> Driver.java:200)
>> at
>> weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleL
>> is
>> tenerInvoker.java:117)
>> at
>> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStat
>> eD
>> river.java:204)
>> at
>> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDr
>> iv
>> er.java:26)
>> at
>> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleState
>> Dr
>> iver.java:60)
>> at
>> weblogic.application.internal.flow.StartModulesFlow.activate(StartModu
>> le
>> sFlow.java:26)
>> at
>>
> weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
>> 635)
>> at
>> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDr
>> iv
>> er.java:26)
>> at
>> weblogic.application.internal.BaseDeployment.activate(BaseDeployment.j
>> av
>> a:212)
>> at
>> weblogic.application.internal.DeploymentStateChecker.activate(Deployme
>> nt
>> StateChecker.java:154)
>> at
>> weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(App
>> Co
>> ntainerInvoker.java:80)
>> at
>> weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDe
>> pl
>> oyment.java:181)
>> at
>> weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServ
>> er
>> Lifecycle(BasicDeployment.java:358)
>> at
>> weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(Dep
>> lo
>> ymentAdapter.java:52)
>> at
>> weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploym
>> en
>> tAdapter.java:186)
>> at
>> weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppT
>> ra
>> nsition.java:30)
>> at
>> weblogic.management.deploy.internal.ConfiguredDeployments.transitionAp
>> ps
>> (ConfiguredDeployments.java:254)
>> at
>> weblogic.management.deploy.internal.ConfiguredDeployments.transitionAp
>> ps
>> (ConfiguredDeployments.java:239)
>> at
>> weblogic.management.deploy.internal.ConfiguredDeployments.activate(Con
>> fi
>> guredDeployments.java:169)
>> at
>> weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Confi
>> gu
>> redDeployments.java:123)
>> at
>> weblogic.management.deploy.internal.DeploymentServerService.resume(Dep
>> lo
>> ymentServerService.java:173)
>> at
>> weblogic.management.deploy.internal.DeploymentServerService.start(Depl
>> oy
>> mentServerService.java:89)
>> at
>> weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
>> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>> at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>>
>> This email and/or any files or attachments transmitted with it are
> confidential and intended solely for the use of the individual or entity
> to whom they are addressed, and may contain information that is
> privileged, confidential and exempt from disclosure under applicable
> law. If you are not the intended recipient, or the employee or agent
> responsible for delivering the message to the intended recipient, you
> are hereby notified that any dissemination, distribution or copying of
> this e-mail and/or any files or attachments transmitted with it is
> strictly forbidden. If you have received this email in error, please
> delete the e-mail and/or any files or attachments, and also notify the
> system manager (PostMaster@mercuryinsurance.com) of the error. Please
> note that any views or opinions presented in this email are solely those
> of the author and do not necessarily represent those of the company.
> Finally, the recipient should check this email and any attachments for
> the presence of viruses. The company accepts no liability for any damage
> caused by any virus transmitted by this email and/or any files or
> attachments transmitted with it.
>>
>>
>>
>
>
>
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com
>
>
>
> This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
>
>
>
--
Alexander Klimetschek
alexander.klimetschek@day.com
RE: Exceptions with Repository running against DB2
Posted by Vikas Phonsa <VP...@mercuryinsurance.com>.
Alex,
I read ( somewhere on JackRabbit site) that BundleDbPersistenceManager
offers good performance when used with a DataStore, but you need
JackRabbit 1.4 to do that. But my JBOSS BRMS app uses JackRabbit 1.3,
that's why I decided to just use the SimpleDbPersistanceManager.
Can BundleDbPersistenceManager be used with Jackrabbit 1.3 ?
Thanks,
Vikas
-----Original Message-----
From: Alexander Klimetschek [mailto:aklimets@day.com]
Sent: Tuesday, June 24, 2008 9:25 AM
To: users@jackrabbit.apache.org
Subject: Re: Exceptions with Repository running against DB2
I would recommend to use a bundle db persistence manager:
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
It should be better regarding DB connections and has better performance
than the simple db pm.
Regards,
Alex
On Tue, Jun 24, 2008 at 11:46 AM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> Hi All,
>
> I'm using JBOSS Rules BRMS application, which uses Jackrabbit.
>
> The repository is connected to a DB2 database.
>
> I've deployed the application on Weblogic. It works fine for the most
> part.
>
> But every time the repository starts up I see the exception listed
> below.
>
> And eventually, I start seeing OutofMemory errors in the server log.
>
> Can't say if the two issues are related, but has anybody experienced
> any such problem ?
>
> I'm also listing my FileSystem and PersistanceManager configurations
> below.
>
> Thanks in advance for any feedback.
>
> Regards,
> Vikas
>
>
>
> ------------------------ Repository
> Config------------------------------
>
> <FileSystem
> class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
> <param name="driver"
> value="com.ibm.db2.jcc.DB2Driver"/>
> <param name="url"
> value="jdbc:db2://localhost:50000/Drools"/>
> <param name="schema" value="db2"/>
>
> <param name="user" value="test"/>
> <param name="password" value="testpw"/>
> <param name="schemaObjectPrefix"
> value="${wsp.name}_FS_"/>
> </FileSystem>
>
>
> <PersistenceManager
> class="org.apache.jackrabbit.core.persistence.db.SimpleDbPersistenceMa
> na
> ger">
> <param name="driver" value="com.ibm.db2.jcc.DB2Driver"/>
> <param name="url"
> value="jdbc:db2://localhost:50000/Drools"/>
> <param name="schema" value="test"/>
> <param name="user" value="vphonsa"/>
> <param name="password" value="testpw"/>
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
> <param name="externalBLOBs" value="false"/>
> </PersistenceManager>
>
>
>
> --------------------Exception Stack
> Trace------------------------------
>
> ERROR 23-06 17:45:34,571 (RepositoryImpl.java:dispose:1890) error
> while closing persistence manager of workspace MBR_WS
> com.ibm.db2.jcc.b.SqlException: [jcc][t4][10251][10308][3.50.152]
> java.sql.Connection.close() requested while a transaction is in
> progress on the connection.
> The transaction remains active, and the connection cannot be closed.
> ERRORCODE=-4471, SQLSTATE=null
> at com.ibm.db2.jcc.b.wc.a(wc.java:55)
> at com.ibm.db2.jcc.b.wc.a(wc.java:119)
> at com.ibm.db2.jcc.b.eb.t(eb.java:996)
> at com.ibm.db2.jcc.b.eb.w(eb.java:1019)
> at com.ibm.db2.jcc.b.eb.u(eb.java:1005)
> at com.ibm.db2.jcc.b.eb.close(eb.java:989)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.c
> lo
> seConnection(DatabasePersistenceManager.java:765)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.c
> lo
> se(DatabasePersistenceManager.java:253)
> at
> org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.dispose(Reposi
> to
> ryImpl.java:1888)
> at
> org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.ja
> va
> :1009)
> at
> org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java
> :9
> 63)
> at
> org.apache.jackrabbit.core.TransientRepository.stopRepository(Transien
> tR
> epository.java:275)
> at
> org.apache.jackrabbit.core.TransientRepository.loggedOut(TransientRepo
> si
> tory.java:427)
> at
>
org.apache.jackrabbit.core.SessionImpl.notifyLoggedOut(SessionImpl.java:
> 559)
> at
> org.apache.jackrabbit.core.SessionImpl.logout(SessionImpl.java:1295)
> at
>
org.apache.jackrabbit.core.XASessionImpl.logout(XASessionImpl.java:379)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(B
> RM
> SRepositoryConfiguration.java:66)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(B
> RM
> SRepositoryConfiguration.java:56)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> av
> a:64)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
> at
> org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationC
> on
> text.java:31)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationC
> on
> text.java:56)
> at
> org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackIn
> te
> rceptor.java:31)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationC
> on
> text.java:68)
> at
> org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContex
> tI
> nterceptor.java:42)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationC
> on
> text.java:68)
> at
> org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:1
> 06
> )
> at
> org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaB
> ea
> nInterceptor.java:155)
> at
>
org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.
> java:91)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration_$$_javas
> si
> st_0.create(BRMSRepositoryConfiguration_$$_javassist_0.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> av
> a:64)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
> at
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
> at
> org.jboss.seam.Component.callComponentMethod(Component.java:2087)
> at
> org.jboss.seam.Component.callCreateMethod(Component.java:2010)
> at org.jboss.seam.Component.newInstance(Component.java:1981)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
> at
> org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLife
> cy
> cle.java:95)
> at
> org.jboss.seam.init.Initialization.init(Initialization.java:554)
> at
> org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.ja
> va
> :34)
> at
> weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(
> Ev
> entsManager.java:376)
> at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticated
> Su
> bject.java:321)
> at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:1
> 21
> )
> at
> weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(Even
> ts
> Manager.java:82)
> at
> weblogic.servlet.internal.WebAppServletContext.preloadResources(WebApp
> Se
> rvletContext.java:1609)
> at
> weblogic.servlet.internal.WebAppServletContext.start(WebAppServletCont
> ex
> t.java:2764)
> at
> weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java
> :8
> 89)
> at
> weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
> at
> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStat
> eD
> river.java:204)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDr
> iv
> er.java:26)
> at
> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleState
> Dr
> iver.java:60)
> at
> weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModu
> le
> Driver.java:200)
> at
> weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleL
> is
> tenerInvoker.java:117)
> at
> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStat
> eD
> river.java:204)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDr
> iv
> er.java:26)
> at
> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleState
> Dr
> iver.java:60)
> at
> weblogic.application.internal.flow.StartModulesFlow.activate(StartModu
> le
> sFlow.java:26)
> at
>
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
> 635)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDr
> iv
> er.java:26)
> at
> weblogic.application.internal.BaseDeployment.activate(BaseDeployment.j
> av
> a:212)
> at
> weblogic.application.internal.DeploymentStateChecker.activate(Deployme
> nt
> StateChecker.java:154)
> at
> weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(App
> Co
> ntainerInvoker.java:80)
> at
> weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDe
> pl
> oyment.java:181)
> at
> weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServ
> er
> Lifecycle(BasicDeployment.java:358)
> at
> weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(Dep
> lo
> ymentAdapter.java:52)
> at
> weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploym
> en
> tAdapter.java:186)
> at
> weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppT
> ra
> nsition.java:30)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.transitionAp
> ps
> (ConfiguredDeployments.java:254)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.transitionAp
> ps
> (ConfiguredDeployments.java:239)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.activate(Con
> fi
> guredDeployments.java:169)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Confi
> gu
> redDeployments.java:123)
> at
> weblogic.management.deploy.internal.DeploymentServerService.resume(Dep
> lo
> ymentServerService.java:173)
> at
> weblogic.management.deploy.internal.DeploymentServerService.start(Depl
> oy
> mentServerService.java:89)
> at
> weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
> This email and/or any files or attachments transmitted with it are
confidential and intended solely for the use of the individual or entity
to whom they are addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable
law. If you are not the intended recipient, or the employee or agent
responsible for delivering the message to the intended recipient, you
are hereby notified that any dissemination, distribution or copying of
this e-mail and/or any files or attachments transmitted with it is
strictly forbidden. If you have received this email in error, please
delete the e-mail and/or any files or attachments, and also notify the
system manager (PostMaster@mercuryinsurance.com) of the error. Please
note that any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability for any damage
caused by any virus transmitted by this email and/or any files or
attachments transmitted with it.
>
>
>
--
Alexander Klimetschek
alexander.klimetschek@day.com
This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
Re: Exceptions with Repository running against DB2
Posted by Alexander Klimetschek <ak...@day.com>.
I would recommend to use a bundle db persistence manager:
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
It should be better regarding DB connections and has better
performance than the simple db pm.
Regards,
Alex
On Tue, Jun 24, 2008 at 11:46 AM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> Hi All,
>
> I'm using JBOSS Rules BRMS application, which uses Jackrabbit.
>
> The repository is connected to a DB2 database.
>
> I've deployed the application on Weblogic. It works fine for the most
> part.
>
> But every time the repository starts up I see the exception listed
> below.
>
> And eventually, I start seeing OutofMemory errors in the server log.
>
> Can't say if the two issues are related, but has anybody experienced any
> such problem ?
>
> I'm also listing my FileSystem and PersistanceManager configurations
> below.
>
> Thanks in advance for any feedback.
>
> Regards,
> Vikas
>
>
>
> ------------------------ Repository Config------------------------------
>
> <FileSystem
> class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
> <param name="driver"
> value="com.ibm.db2.jcc.DB2Driver"/>
> <param name="url"
> value="jdbc:db2://localhost:50000/Drools"/>
> <param name="schema" value="db2"/>
>
> <param name="user" value="test"/>
> <param name="password" value="testpw"/>
> <param name="schemaObjectPrefix"
> value="${wsp.name}_FS_"/>
> </FileSystem>
>
>
> <PersistenceManager
> class="org.apache.jackrabbit.core.persistence.db.SimpleDbPersistenceMana
> ger">
> <param name="driver" value="com.ibm.db2.jcc.DB2Driver"/>
> <param name="url"
> value="jdbc:db2://localhost:50000/Drools"/>
> <param name="schema" value="test"/>
> <param name="user" value="vphonsa"/>
> <param name="password" value="testpw"/>
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
> <param name="externalBLOBs" value="false"/>
> </PersistenceManager>
>
>
>
> --------------------Exception Stack Trace------------------------------
>
> ERROR 23-06 17:45:34,571 (RepositoryImpl.java:dispose:1890) error
> while closing persistence manager of workspace MBR_WS
> com.ibm.db2.jcc.b.SqlException: [jcc][t4][10251][10308][3.50.152]
> java.sql.Connection.close() requested while a transaction is in progress
> on the connection.
> The transaction remains active, and the connection cannot be closed.
> ERRORCODE=-4471, SQLSTATE=null
> at com.ibm.db2.jcc.b.wc.a(wc.java:55)
> at com.ibm.db2.jcc.b.wc.a(wc.java:119)
> at com.ibm.db2.jcc.b.eb.t(eb.java:996)
> at com.ibm.db2.jcc.b.eb.w(eb.java:1019)
> at com.ibm.db2.jcc.b.eb.u(eb.java:1005)
> at com.ibm.db2.jcc.b.eb.close(eb.java:989)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.clo
> seConnection(DatabasePersistenceManager.java:765)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.clo
> se(DatabasePersistenceManager.java:253)
> at
> org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.dispose(Reposito
> ryImpl.java:1888)
> at
> org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.java
> :1009)
> at
> org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java:9
> 63)
> at
> org.apache.jackrabbit.core.TransientRepository.stopRepository(TransientR
> epository.java:275)
> at
> org.apache.jackrabbit.core.TransientRepository.loggedOut(TransientReposi
> tory.java:427)
> at
> org.apache.jackrabbit.core.SessionImpl.notifyLoggedOut(SessionImpl.java:
> 559)
> at
> org.apache.jackrabbit.core.SessionImpl.logout(SessionImpl.java:1295)
> at
> org.apache.jackrabbit.core.XASessionImpl.logout(XASessionImpl.java:379)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
> SRepositoryConfiguration.java:66)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
> SRepositoryConfiguration.java:56)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:64)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
> at
> org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationCon
> text.java:31)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
> text.java:56)
> at
> org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInte
> rceptor.java:31)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
> text.java:68)
> at
> org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextI
> nterceptor.java:42)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
> text.java:68)
> at
> org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106
> )
> at
> org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBea
> nInterceptor.java:155)
> at
> org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.
> java:91)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration_$$_javassi
> st_0.create(BRMSRepositoryConfiguration_$$_javassist_0.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:64)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
> at
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
> at
> org.jboss.seam.Component.callComponentMethod(Component.java:2087)
> at
> org.jboss.seam.Component.callCreateMethod(Component.java:2010)
> at org.jboss.seam.Component.newInstance(Component.java:1981)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
> at
> org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecy
> cle.java:95)
> at
> org.jboss.seam.init.Initialization.init(Initialization.java:554)
> at
> org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java
> :34)
> at
> weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(Ev
> entsManager.java:376)
> at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
> bject.java:321)
> at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
> )
> at
> weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(Events
> Manager.java:82)
> at
> weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
> rvletContext.java:1609)
> at
> weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
> t.java:2764)
> at
> weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:8
> 89)
> at
> weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
> at
> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
> river.java:204)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
> er.java:26)
> at
> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
> iver.java:60)
> at
> weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule
> Driver.java:200)
> at
> weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis
> tenerInvoker.java:117)
> at
> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
> river.java:204)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
> er.java:26)
> at
> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
> iver.java:60)
> at
> weblogic.application.internal.flow.StartModulesFlow.activate(StartModule
> sFlow.java:26)
> at
> weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
> 635)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
> er.java:26)
> at
> weblogic.application.internal.BaseDeployment.activate(BaseDeployment.jav
> a:212)
> at
> weblogic.application.internal.DeploymentStateChecker.activate(Deployment
> StateChecker.java:154)
> at
> weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppCo
> ntainerInvoker.java:80)
> at
> weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDepl
> oyment.java:181)
> at
> weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServer
> Lifecycle(BasicDeployment.java:358)
> at
> weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(Deplo
> ymentAdapter.java:52)
> at
> weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploymen
> tAdapter.java:186)
> at
> weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTra
> nsition.java:30)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
> (ConfiguredDeployments.java:254)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
> (ConfiguredDeployments.java:239)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.activate(Confi
> guredDeployments.java:169)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Configu
> redDeployments.java:123)
> at
> weblogic.management.deploy.internal.DeploymentServerService.resume(Deplo
> ymentServerService.java:173)
> at
> weblogic.management.deploy.internal.DeploymentServerService.start(Deploy
> mentServerService.java:89)
> at
> weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
> This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
>
>
>
--
Alexander Klimetschek
alexander.klimetschek@day.com
Re: Exceptions with Repository running against DB2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Jun 25, 2008 at 11:47 AM, Stefan Guggisberg
<st...@day.com> wrote:
> please feel free to create a jira issue.
In fact there already is one, https://issues.apache.org/jira/browse/JCR-1367
BR,
Jukka Zitting
Re: Exceptions with Repository running against DB2
Posted by Alexander Klimetschek <ak...@day.com>.
On Wed, Jun 25, 2008 at 12:59 PM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> Hmm...I thought you give your workspace a name (MBR_WS in this case) and
> then you can reference that name using "${wsp.name}"...so it doesn't
> work that way ?
The workspace name is defined from the outside upon creation. The
<Workspace> element in the repository.xml acts as a template for the
workspace.xml upon creation of a new workspace, and all variables
(wsp.name, wsp.home and rep.home) get substituted.
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com
RE: Exceptions with Repository running against DB2
Posted by Vikas Phonsa <VP...@mercuryinsurance.com>.
Hmm...I thought you give your workspace a name (MBR_WS in this case) and
then you can reference that name using "${wsp.name}"...so it doesn't
work that way ?
-----Original Message-----
From: Alexander Klimetschek [mailto:aklimets@day.com]
Sent: Wednesday, June 25, 2008 9:55 AM
To: users@jackrabbit.apache.org
Subject: Re: Exceptions with Repository running against DB2
Not sure, but maybe the
<Workspace name="MBR_WS">
in your repository.xml should be
<Workspace name="${wsp.name}">
hence referencing the workspace name. You need to remove all workspaces
and re-create them, though for this change to have effect.
Regards,
Alex
On Wed, Jun 25, 2008 at 12:39 PM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> I tried using the BundleDbPersistenceManager. But am getting some new
> exceptions now.
>
> I tried to use it against my existing database, which has the tables
> that were generated by the SimpleDbPeristenceManager. Does that matter
?
>
>
> It seems to be looking for an object VPHONSA.VERSION_NAMES, which
> doesn't exist in the DB, cause it wasn't created by SimpleDbPM.
>
> Just to test it, I deleted all the existing tables and let the
> BundleDbPM create the schema, still no VERSION_NAMES object was
created.
> It did create a
> VPHONSA_X002E_VERSION_NAMES table though.
>
> I'm attaching my complete repository.xml.
>
> If ultimately I'm able to make the BundleDbPM work, can I migrate my
> repository data from tables created by SimpleDbPM to the tables
> created by the BundleDbPM ( if they are going to be different ).
>
> Also what is "deadbeef-face-babe-cafe-babecafebabe" :-)
>
> Thanks a lot for your help,
>
> Vikas
>
>
> ----------------Exception Stack Trace-----------------------
>
>
> org.apache.jackrabbit.core.state.ItemStateException: failed to write
> bundle: deadbeef-face-babe-cafe-babecafebabe
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManag
> er
> .storeBundle(BundleDbPersistenceManager.java:944)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenc
> eM
> anager.putBundle(AbstractBundlePersistenceManager.java:693)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenc
> eM
> anager.store(AbstractBundlePersistenceManager.java:634)
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManag
> er
> .store(BundleDbPersistenceManager.java:495)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionMa
> na
> gerImpl.java:159)
> at
> org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(Reposit
> or
> yImpl.java:372)
> at
> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:2
> 82
> )
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:5
> 84
> )
> at
> org.apache.jackrabbit.core.TransientRepository$2.getRepository(Transie
> nt
> Repository.java:245)
> at
> org.apache.jackrabbit.core.TransientRepository.startRepository(Transie
> nt
> Repository.java:265)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientReposito
> ry
> .java:333)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientReposito
> ry
> .java:363)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSessi
> on
> (BRMSRepositoryConfiguration.java:87)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(B
> RM
> SRepositoryConfiguration.java:55)
>
> java.lang.IllegalStateException: Unable to read index:
> com.ibm.db2.jcc.b.nm: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704,
> SQLERRMC=VPHONSA.VERSION_NAMES, DRIVER=3.50.152
> at
> org.apache.jackrabbit.core.persistence.bundle.util.DbNameIndex.getInde
> x(
> DbNameIndex.java:175)
> at
> org.apache.jackrabbit.core.persistence.bundle.util.DbNameIndex.stringT
> oI
> ndex(DbNameIndex.java:96)
> at
> org.apache.jackrabbit.core.persistence.bundle.util.BundleBinding.write
> Bu
> ndle(BundleBinding.java:245)
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManag
> er
> .storeBundle(BundleDbPersistenceManager.java:930)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenc
> eM
> anager.putBundle(AbstractBundlePersistenceManager.java:693)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenc
> eM
> anager.store(AbstractBundlePersistenceManager.java:634)
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManag
> er
> .store(BundleDbPersistenceManager.java:495)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionMa
> na
> gerImpl.java:159)
> at
> org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(Reposit
> or
> yImpl.java:372)
> at
> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:2
> 82
> )
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:5
> 84
> )
> at
> org.apache.jackrabbit.core.TransientRepository$2.getRepository(Transie
> nt
> Repository.java:245)
> at
> org.apache.jackrabbit.core.TransientRepository.startRepository(Transie
> nt
> Repository.java:265)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientReposito
> ry
> .java:333)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientReposito
> ry
> .java:363)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSessi
> on
> (BRMSRepositoryConfiguration.java:87)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(B
> RM
> SRepositoryConfiguration.java:55)
>
>
>
> This email and/or any files or attachments transmitted with it are
confidential and intended solely for the use of the individual or entity
to whom they are addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable
law. If you are not the intended recipient, or the employee or agent
responsible for delivering the message to the intended recipient, you
are hereby notified that any dissemination, distribution or copying of
this e-mail and/or any files or attachments transmitted with it is
strictly forbidden. If you have received this email in error, please
delete the e-mail and/or any files or attachments, and also notify the
system manager (PostMaster@mercuryinsurance.com) of the error. Please
note that any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability for any damage
caused by any virus transmitted by this email and/or any files or
attachments transmitted with it.
>
>
--
Alexander Klimetschek
alexander.klimetschek@day.com
This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
Re: Exceptions with Repository running against DB2
Posted by Alexander Klimetschek <ak...@day.com>.
Not sure, but maybe the
<Workspace name="MBR_WS">
in your repository.xml should be
<Workspace name="${wsp.name}">
hence referencing the workspace name. You need to remove all
workspaces and re-create them, though for this change to have effect.
Regards,
Alex
On Wed, Jun 25, 2008 at 12:39 PM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> I tried using the BundleDbPersistenceManager. But am getting some new
> exceptions now.
>
> I tried to use it against my existing database, which has the tables
> that were generated by the SimpleDbPeristenceManager. Does that matter ?
>
>
> It seems to be looking for an object VPHONSA.VERSION_NAMES, which
> doesn't exist in the DB, cause it wasn't created by SimpleDbPM.
>
> Just to test it, I deleted all the existing tables and let the
> BundleDbPM create the schema, still no VERSION_NAMES object was created.
> It did create a
> VPHONSA_X002E_VERSION_NAMES table though.
>
> I'm attaching my complete repository.xml.
>
> If ultimately I'm able to make the BundleDbPM work, can I migrate my
> repository data from tables created by SimpleDbPM to the tables created
> by the BundleDbPM ( if they are going to be different ).
>
> Also what is "deadbeef-face-babe-cafe-babecafebabe" :-)
>
> Thanks a lot for your help,
>
> Vikas
>
>
> ----------------Exception Stack Trace-----------------------
>
>
> org.apache.jackrabbit.core.state.ItemStateException: failed to write
> bundle: deadbeef-face-babe-cafe-babecafebabe
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
> .storeBundle(BundleDbPersistenceManager.java:944)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
> anager.putBundle(AbstractBundlePersistenceManager.java:693)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
> anager.store(AbstractBundlePersistenceManager.java:634)
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
> .store(BundleDbPersistenceManager.java:495)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionMana
> gerImpl.java:159)
> at
> org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(Repositor
> yImpl.java:372)
> at
> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:282
> )
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584
> )
> at
> org.apache.jackrabbit.core.TransientRepository$2.getRepository(Transient
> Repository.java:245)
> at
> org.apache.jackrabbit.core.TransientRepository.startRepository(Transient
> Repository.java:265)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
> .java:333)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
> .java:363)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSession
> (BRMSRepositoryConfiguration.java:87)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
> SRepositoryConfiguration.java:55)
>
> java.lang.IllegalStateException: Unable to read index:
> com.ibm.db2.jcc.b.nm: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704,
> SQLERRMC=VPHONSA.VERSION_NAMES, DRIVER=3.50.152
> at
> org.apache.jackrabbit.core.persistence.bundle.util.DbNameIndex.getIndex(
> DbNameIndex.java:175)
> at
> org.apache.jackrabbit.core.persistence.bundle.util.DbNameIndex.stringToI
> ndex(DbNameIndex.java:96)
> at
> org.apache.jackrabbit.core.persistence.bundle.util.BundleBinding.writeBu
> ndle(BundleBinding.java:245)
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
> .storeBundle(BundleDbPersistenceManager.java:930)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
> anager.putBundle(AbstractBundlePersistenceManager.java:693)
> at
> org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
> anager.store(AbstractBundlePersistenceManager.java:634)
> at
> org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
> .store(BundleDbPersistenceManager.java:495)
> at
> org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionMana
> gerImpl.java:159)
> at
> org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(Repositor
> yImpl.java:372)
> at
> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:282
> )
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584
> )
> at
> org.apache.jackrabbit.core.TransientRepository$2.getRepository(Transient
> Repository.java:245)
> at
> org.apache.jackrabbit.core.TransientRepository.startRepository(Transient
> Repository.java:265)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
> .java:333)
> at
> org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
> .java:363)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSession
> (BRMSRepositoryConfiguration.java:87)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
> SRepositoryConfiguration.java:55)
>
>
>
> This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
>
>
--
Alexander Klimetschek
alexander.klimetschek@day.com
RE: Exceptions with Repository running against DB2
Posted by Vikas Phonsa <VP...@mercuryinsurance.com>.
I tried using the BundleDbPersistenceManager. But am getting some new
exceptions now.
I tried to use it against my existing database, which has the tables
that were generated by the SimpleDbPeristenceManager. Does that matter ?
It seems to be looking for an object VPHONSA.VERSION_NAMES, which
doesn't exist in the DB, cause it wasn't created by SimpleDbPM.
Just to test it, I deleted all the existing tables and let the
BundleDbPM create the schema, still no VERSION_NAMES object was created.
It did create a
VPHONSA_X002E_VERSION_NAMES table though.
I'm attaching my complete repository.xml.
If ultimately I'm able to make the BundleDbPM work, can I migrate my
repository data from tables created by SimpleDbPM to the tables created
by the BundleDbPM ( if they are going to be different ).
Also what is "deadbeef-face-babe-cafe-babecafebabe" :-)
Thanks a lot for your help,
Vikas
----------------Exception Stack Trace-----------------------
org.apache.jackrabbit.core.state.ItemStateException: failed to write
bundle: deadbeef-face-babe-cafe-babecafebabe
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.storeBundle(BundleDbPersistenceManager.java:944)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.putBundle(AbstractBundlePersistenceManager.java:693)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.store(AbstractBundlePersistenceManager.java:634)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.store(BundleDbPersistenceManager.java:495)
at
org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionMana
gerImpl.java:159)
at
org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(Repositor
yImpl.java:372)
at
org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:282
)
at
org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584
)
at
org.apache.jackrabbit.core.TransientRepository$2.getRepository(Transient
Repository.java:245)
at
org.apache.jackrabbit.core.TransientRepository.startRepository(Transient
Repository.java:265)
at
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
.java:333)
at
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
.java:363)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSession
(BRMSRepositoryConfiguration.java:87)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
SRepositoryConfiguration.java:55)
java.lang.IllegalStateException: Unable to read index:
com.ibm.db2.jcc.b.nm: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704,
SQLERRMC=VPHONSA.VERSION_NAMES, DRIVER=3.50.152
at
org.apache.jackrabbit.core.persistence.bundle.util.DbNameIndex.getIndex(
DbNameIndex.java:175)
at
org.apache.jackrabbit.core.persistence.bundle.util.DbNameIndex.stringToI
ndex(DbNameIndex.java:96)
at
org.apache.jackrabbit.core.persistence.bundle.util.BundleBinding.writeBu
ndle(BundleBinding.java:245)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.storeBundle(BundleDbPersistenceManager.java:930)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.putBundle(AbstractBundlePersistenceManager.java:693)
at
org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceM
anager.store(AbstractBundlePersistenceManager.java:634)
at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager
.store(BundleDbPersistenceManager.java:495)
at
org.apache.jackrabbit.core.version.VersionManagerImpl.<init>(VersionMana
gerImpl.java:159)
at
org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(Repositor
yImpl.java:372)
at
org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:282
)
at
org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584
)
at
org.apache.jackrabbit.core.TransientRepository$2.getRepository(Transient
Repository.java:245)
at
org.apache.jackrabbit.core.TransientRepository.startRepository(Transient
Repository.java:265)
at
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
.java:333)
at
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository
.java:363)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSession
(BRMSRepositoryConfiguration.java:87)
at
org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
SRepositoryConfiguration.java:55)
This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
Re: Exceptions with Repository running against DB2
Posted by Stefan Guggisberg <st...@day.com>.
hi vikas
On Tue, Jun 24, 2008 at 5:46 PM, Vikas Phonsa
<VP...@mercuryinsurance.com> wrote:
> Hi All,
>
> I'm using JBOSS Rules BRMS application, which uses Jackrabbit.
>
> The repository is connected to a DB2 database.
>
> I've deployed the application on Weblogic. It works fine for the most
> part.
>
> But every time the repository starts up I see the exception listed
> below.
>
> And eventually, I start seeing OutofMemory errors in the server log.
>
> Can't say if the two issues are related, but has anybody experienced any
> such problem ?
they're probably related. the jboss rules app seems to use a
TransientRepository.
TransientRepository shuts down the repo as soon as the last session is
logging out.
this is exactly what's happening in your case. a session logout triggers
the repo shutdown. i'd advise to rather not use TransientRepository in this
case, the rules app should probably control the repository lifecycle.
the real problem however is that closing the jdbc connection fails due
to the driver complaining about an open transaction. if this happens
repeatedly this might explain the OOM errors.
the 'open tx' problem could be caused by the autocommit=false connection
setting, some drivers require read stmts to be committed as well.
please feel free to create a jira issue.
using another persistence manager might also solve your issue,
the bunde db pm's e.g. use a different autocommit default.
cheers
stefan
>
> I'm also listing my FileSystem and PersistanceManager configurations
> below.
>
> Thanks in advance for any feedback.
>
> Regards,
> Vikas
>
>
>
> ------------------------ Repository Config------------------------------
>
> <FileSystem
> class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
> <param name="driver"
> value="com.ibm.db2.jcc.DB2Driver"/>
> <param name="url"
> value="jdbc:db2://localhost:50000/Drools"/>
> <param name="schema" value="db2"/>
>
> <param name="user" value="test"/>
> <param name="password" value="testpw"/>
> <param name="schemaObjectPrefix"
> value="${wsp.name}_FS_"/>
> </FileSystem>
>
>
> <PersistenceManager
> class="org.apache.jackrabbit.core.persistence.db.SimpleDbPersistenceMana
> ger">
> <param name="driver" value="com.ibm.db2.jcc.DB2Driver"/>
> <param name="url"
> value="jdbc:db2://localhost:50000/Drools"/>
> <param name="schema" value="test"/>
> <param name="user" value="vphonsa"/>
> <param name="password" value="testpw"/>
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
> <param name="externalBLOBs" value="false"/>
> </PersistenceManager>
>
>
>
> --------------------Exception Stack Trace------------------------------
>
> ERROR 23-06 17:45:34,571 (RepositoryImpl.java:dispose:1890) error
> while closing persistence manager of workspace MBR_WS
> com.ibm.db2.jcc.b.SqlException: [jcc][t4][10251][10308][3.50.152]
> java.sql.Connection.close() requested while a transaction is in progress
> on the connection.
> The transaction remains active, and the connection cannot be closed.
> ERRORCODE=-4471, SQLSTATE=null
> at com.ibm.db2.jcc.b.wc.a(wc.java:55)
> at com.ibm.db2.jcc.b.wc.a(wc.java:119)
> at com.ibm.db2.jcc.b.eb.t(eb.java:996)
> at com.ibm.db2.jcc.b.eb.w(eb.java:1019)
> at com.ibm.db2.jcc.b.eb.u(eb.java:1005)
> at com.ibm.db2.jcc.b.eb.close(eb.java:989)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.clo
> seConnection(DatabasePersistenceManager.java:765)
> at
> org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.clo
> se(DatabasePersistenceManager.java:253)
> at
> org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.dispose(Reposito
> ryImpl.java:1888)
> at
> org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.java
> :1009)
> at
> org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java:9
> 63)
> at
> org.apache.jackrabbit.core.TransientRepository.stopRepository(TransientR
> epository.java:275)
> at
> org.apache.jackrabbit.core.TransientRepository.loggedOut(TransientReposi
> tory.java:427)
> at
> org.apache.jackrabbit.core.SessionImpl.notifyLoggedOut(SessionImpl.java:
> 559)
> at
> org.apache.jackrabbit.core.SessionImpl.logout(SessionImpl.java:1295)
> at
> org.apache.jackrabbit.core.XASessionImpl.logout(XASessionImpl.java:379)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
> SRepositoryConfiguration.java:66)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRM
> SRepositoryConfiguration.java:56)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:64)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
> at
> org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationCon
> text.java:31)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
> text.java:56)
> at
> org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInte
> rceptor.java:31)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
> text.java:68)
> at
> org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextI
> nterceptor.java:42)
> at
> org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationCon
> text.java:68)
> at
> org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106
> )
> at
> org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBea
> nInterceptor.java:155)
> at
> org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.
> java:91)
> at
> org.drools.brms.server.repository.BRMSRepositoryConfiguration_$$_javassi
> st_0.create(BRMSRepositoryConfiguration_$$_javassist_0.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:64)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
> at
> org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
> at
> org.jboss.seam.Component.callComponentMethod(Component.java:2087)
> at
> org.jboss.seam.Component.callCreateMethod(Component.java:2010)
> at org.jboss.seam.Component.newInstance(Component.java:1981)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
> at
> org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecy
> cle.java:95)
> at
> org.jboss.seam.init.Initialization.init(Initialization.java:554)
> at
> org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java
> :34)
> at
> weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(Ev
> entsManager.java:376)
> at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
> bject.java:321)
> at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
> )
> at
> weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(Events
> Manager.java:82)
> at
> weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
> rvletContext.java:1609)
> at
> weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
> t.java:2764)
> at
> weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:8
> 89)
> at
> weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
> at
> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
> river.java:204)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
> er.java:26)
> at
> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
> iver.java:60)
> at
> weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule
> Driver.java:200)
> at
> weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis
> tenerInvoker.java:117)
> at
> weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
> river.java:204)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
> er.java:26)
> at
> weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
> iver.java:60)
> at
> weblogic.application.internal.flow.StartModulesFlow.activate(StartModule
> sFlow.java:26)
> at
> weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
> 635)
> at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
> er.java:26)
> at
> weblogic.application.internal.BaseDeployment.activate(BaseDeployment.jav
> a:212)
> at
> weblogic.application.internal.DeploymentStateChecker.activate(Deployment
> StateChecker.java:154)
> at
> weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppCo
> ntainerInvoker.java:80)
> at
> weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDepl
> oyment.java:181)
> at
> weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServer
> Lifecycle(BasicDeployment.java:358)
> at
> weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(Deplo
> ymentAdapter.java:52)
> at
> weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploymen
> tAdapter.java:186)
> at
> weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTra
> nsition.java:30)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
> (ConfiguredDeployments.java:254)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
> (ConfiguredDeployments.java:239)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.activate(Confi
> guredDeployments.java:169)
> at
> weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Configu
> redDeployments.java:123)
> at
> weblogic.management.deploy.internal.DeploymentServerService.resume(Deplo
> ymentServerService.java:173)
> at
> weblogic.management.deploy.internal.DeploymentServerService.start(Deploy
> mentServerService.java:89)
> at
> weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
> This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
>
>
>