Re: [jboss-user] [jBPM] - JBPM4 Migrating from Oracle to Postgres, Transaction Error on JBPM4_LOB
by Alexander Lvov
I dont have an answer to you but do you use XA? what is the type of
datasource configured for Oracle db? if its an xa datasource then you got
yourself a clue where to search.
2011/9/29 Jeff Maas <do-not-reply(a)jboss.com>
> **
> JBoss Community <http://community.jboss.org/index.jspa> JBPM4
> Migrating from Oracle to Postgres, Transaction Error on JBPM4_LOB created
> by Jeff Maas <http://community.jboss.org/people/jeff_maas> in *jBPM* - View
> the full discussion <http://community.jboss.org/message/629406#629406>
> ------------------------------
>
> I have inherited an enterprise service bus style application
> (MULE,JBPM4,Hibernate,Spring) and have been tasked with migrating the
> application from Oracle to Postgres. Much of this has gone without a hitch
> however I have run into a problem that I beleve others have seen before.
> Specifically Postgres8.4 does not appear to like auto-commits on OID ->
> LOB, which appears to be key with how JBPM4_LOB works.
>
>
>
> [http-80-2] [org.hibernate.util.JDBCExceptionReporter] Large Objects may
> not be used in auto-commit mode.
>
>
>
> Root Exception stack trace:
>
> org.postgresql.util.PSQLException: Large Objects may not be used in
> auto-commit mode.
>
> at
> org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:200)
>
> at
> org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:172)
>
> at
> org.postgresql.jdbc2.AbstractJdbc2BlobClob.<init>(AbstractJdbc2BlobClob.java:47)
>
> at
> org.postgresql.jdbc2.AbstractJdbc2Blob.<init>(AbstractJdbc2Blob.java:21)
>
> at
> org.postgresql.jdbc3.AbstractJdbc3Blob.<init>(AbstractJdbc3Blob.java:19)
>
> at
> org.postgresql.jdbc4.AbstractJdbc4Blob.<init>(AbstractJdbc4Blob.java:20)
>
> at org.postgresql.jdbc4.Jdbc4Blob.<init>(Jdbc4Blob.java:20)
>
> at
> org.postgresql.jdbc4.Jdbc4ResultSet.getBlob(Jdbc4ResultSet.java:52)
>
> at
> org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBlob(AbstractJdbc2ResultSet.java:335)
>
> at
> com.mchange.v2.c3p0.impl.NewProxyResultSet.getBlob(NewProxyResultSet.java:285)
>
> at org.hibernate.type.BlobType.get(BlobType.java:80)
>
>
>
> Admittedly I'm a bit out of my element, I've tried various forum searched
> and googles but haven't found a beginners guide to a none beginneres topic.
> It would appear I must add a transaction around JBPM4_LOB even though in the
> context that it is used it is absolutely reaad only.
>
>
>
> Nowehere else do I use BLOB's and right now I've got the various jbpm4
> libraries (maven) on my classpath. But I'm at a loss on how to deal with
> this issue surrounding auto-commit. I've tried various forms of turning
> auto-commit off at the hibernate level but to no avail. Previous seraches
> in the forum suggest others have had this issue but I'm not sure if anyone
> has recieved an answer. Any help or sympathy is greatly appreciated.
>
>
>
>
>
> Thanks
>
> Jeff
>
> Reply to this message by going to Community<http://community.jboss.org/message/629406#629406>
>
> Start a new discussion in jBPM at Community<http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...>
>
> _______________________________________________
> jboss-user mailing list
> jboss-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-user
>
>
13 years, 3 months
[jBPM] - Re: jBPM 5.1 with SQL Server
by Hugo Boss
Hugo Boss [http://community.jboss.org/people/adfasdfasdfhjasdfhasddfhasdfaj] created the discussion
"Re: jBPM 5.1 with SQL Server"
To view the discussion, visit: http://community.jboss.org/message/629412#629412
--------------------------------------------------------------
I have the same problem... i'm using hsqldb and this driver org.hsqldb.jdbcDriver
Please post your solution, if you find one. Thank you.
[CODE]
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.plixia.domain.businessprocess.ProcessSessionFactory]: Constructor threw exception; nested exception is bitronix.tm.resource.ResourceConfigurationException: cannot create JDBC datasource named jdbc/jbpmDataSource
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:141)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:71)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:948)
... 56 more
Caused by: bitronix.tm.resource.ResourceConfigurationException: cannot create JDBC datasource named jdbc/jbpmDataSource
at bitronix.tm.resource.jdbc.PoolingDataSource.init(PoolingDataSource.java:76)
at com.plixia.domain.businessprocess.ProcessSessionFactory.initEnvironment(ProcessSessionFactory.java:74)
at com.plixia.domain.businessprocess.ProcessSessionFactory.<init>(ProcessSessionFactory.java:57)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
... 58 more
Caused by: bitronix.tm.utils.PropertyException: no writeable property 'URL' in class 'org.hsqldb.jdbcDriver'
at bitronix.tm.utils.PropertyUtils.getSetter(PropertyUtils.java:318)
at bitronix.tm.utils.PropertyUtils.setDirectProperty(PropertyUtils.java:217)
at bitronix.tm.utils.PropertyUtils.setProperty(PropertyUtils.java:83)
at bitronix.tm.resource.common.XAPool.createXAFactory(XAPool.java:314)
at bitronix.tm.resource.common.XAPool.<init>(XAPool.java:63)
at bitronix.tm.resource.jdbc.PoolingDataSource.buildXAPool(PoolingDataSource.java:85)
at bitronix.tm.resource.jdbc.PoolingDataSource.init(PoolingDataSource.java:72)
... 65 more
[/CODE]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629412#629412]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[JBoss Tools] - JBoss AS7 webapp development
by Konrad Wolski
Konrad Wolski [http://community.jboss.org/people/konwol] created the discussion
"JBoss AS7 webapp development"
To view the discussion, visit: http://community.jboss.org/message/628012#628012
--------------------------------------------------------------
Hi,
Our team wants to switch to JBoss 7 as a development platform on a regular day to day basis. Currenly we use Tomcat 7. We want to use JBoss Tools and have tested current development version.
Is there an article explaining how incremental publishing works ?
We want to achive same setup as with Tomcat 7 wtp server adapter, that is:
1) automatic redeployment of application when a dynamic resource changes (like a Java class)
2) no redeployment when a static resource changes (only refresh)
>From what we see in default configuration (exploded webapp) static resources are refreshed but dynamic resources do not trigger automatic redeployment. Is there something we are missing or the community server adapter doesn't support this feature ?
I am aware that scanning of exploded application can be enabled but we want to avoid it so static resource changes do not trigger full redeployment.
---
Second concern is that we are building our projects using maven multimodule functionality. When the tools are switched to deploy archives (war is the target here) automatic redeployment doesn't happen when a dependency in WEB-INF/lib changes. We created two simple projects:
a) one named 'dep1' (Java Project)
b) second named 'webapp' (Dynamic Web Project) with the 'dep1' set in "Deployment assembly" project properties
The dependency is placed in WEB-INF/lib/dep1.jar. When we recompile a class that is in "webapp" project the whole application gets redeployed (cool), but when a class from 'dep1' is recompiled the application isn't redeployed. We are yet again forced to do manual deployment like in the first problem.
In a way those two are problems are connected. We don't use any JBoss 7 specific functionallity yet. These are simple web applications (no ear, osgi, etc).
Thanks,
Konrad
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/628012#628012]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[JBoss Web Services] - Module Dependency for supporting external Handler
by Paul Robinson
Paul Robinson [http://community.jboss.org/people/paul.robinson] created the discussion
"Module Dependency for supporting external Handler"
To view the discussion, visit: http://community.jboss.org/message/629328#629328
--------------------------------------------------------------
Hello,
I'm trying to configure module dependencies for a JAX-WS Web service. The complication seems to come from the fact that the service uses a Handler that lives inside a dependency rather than the same deployment archive as the Web service. The problem is appearing in the TXBridge and XTS demos in the JBossTS project. I would ask someone on the Transactions team to fix this, but unfortunately that is me ;-)
In more detail this is what we have:
The application (txbridge-demo-service.jar) that I am deploying depends on org.jboss.xts, which is where the handler that is specified in the handler chain lives. The Web service only uses JAX-WS annotations (rather than CXF) so I have the following dependencies specified in the manifest.mf of the txbridge-demo-service.jar:
{code}
Dependencies: javax.xml.ws.api, org.jboss.xts, org.jboss.ws.cxf.jbossws-cxf-client services export
{code}
The module "org.jboss.xts" has the following module.xml, which includes dependencies to JBossWS:
{code:xml}
<module xmlns="urn:jboss:module:1.0" name="org.jboss.xts">
<resources>
<resource-root path="jbossxts-4.15.3.Final.jar"/>
<resource-root path="jbossxts-api-4.15.3.Final.jar"/>
<resource-root path="jbosstxbridge-4.15.3.Final.jar"/>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.transaction.api"/>
<module name="javax.resource.api" />
<module name="system"/>
<module name="org.jboss.jts"/>
<module name="org.jboss.ws.api" services="export"/>
<module name="org.jboss.ws.jaxws-client" services="export"/>
<module name="org.jboss.ws.cxf.jbossws-cxf-client" services="export"/>
<module name="org.jboss.logging"/>
<module name="javax.xml.soap.api"/>
<module name="javax.xml.ws.api"/>
<module name="javax.xml.stream.api"/>
<!-- this is needed to get javax.xml.namespace.QName but it would be better if it were exposed on its own -->
<module name="javax.api"/>
<!-- this is needed because our endpoints are not in a normal deployment and we need to be able
to resolve the javax.jws.WebService annotation attached to them. presumably an endpoint
found in a deployment gets this package auto-added to its module loader
-->
<module name="javax.jws.api"/>
<!-- this is needed to ensure @Resource annotations on the JaxWS endpoint classes are in the
classloader scope-->
<module name="javax.annotation.api"/>
<!-- this is needed to ensure the JaxWS endpoint classes canb refer to HttpServletRequest etc -->
<module name="javax.servlet.api"/>
</dependencies>
</module>
{code}
When I deploy my application I get the following stack trace:
{code}
10:14:55,883 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.deployment.unit."txbridge-demo-service.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."txbridge-demo-service.jar".INSTALL: Failed to process phase INSTALL of deployment "txbridge-demo-service.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Caused by: javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: Failed to instantiate handler
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:350)
at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:88)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:239)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:509)
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:116)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:109)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:132)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.internalDeploy(AspectDeploymentProcessor.java:79)
at org.jboss.as.webservices.deployers.TCCLDeploymentProcessor.deploy(TCCLDeploymentProcessor.java:42)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
... 5 more
Caused by: javax.xml.ws.WebServiceException: Failed to instantiate handler
at org.apache.cxf.jaxws.handler.HandlerChainBuilder.buildHandlerChain(HandlerChainBuilder.java:131)
at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.processHandlerElement(AnnotationHandlerChainBuilder.java:267)
at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.processHandlerChainElement(AnnotationHandlerChainBuilder.java:167)
at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:120)
at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:284)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.buildHandlerChain(JaxWsServerFactoryBean.java:237)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.initializeResourcesAndHandlerChain(JaxWsServerFactoryBean.java:216)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:203)
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:433)
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:322)
... 14 more
Caused by: java.lang.ClassCastException: class org.jboss.jbossts.txbridge.inbound.JaxWSTxInboundBridgeHandler
at java.lang.Class.asSubclass(Class.java:3039) [:1.6.0_22]
at org.apache.cxf.jaxws.handler.HandlerChainBuilder.buildHandlerChain(HandlerChainBuilder.java:121)
... 23 more
{code}
The ClassCastException refers to org.jboss.jbossts.txbridge.inbound.JaxWSTxInboundBridgeHandler which is the handler that lives in the org.jboss.xts module. I think the problem is that when JBossWS creates the endpoint it does not have JaxWSTxInboundBridgeHandler in it's Classloader as JBossWS does not depend on org.jboss.xts (which of course it shouldn't as org.jboss.xts depends on JBossWS). However, the application does depend on org.jboss.xts, which I don't think is of any help to JBossWS.
Is my reasoning about what is wrong correct and can anyone suggest how I can fix this?
Many thanks,
Paul Robinson.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629328#629328]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months