[jBPM Users] - Re: Same token seems to be attached to two task instances?
by gfargone
Ronald,
I was suspecting a transaction rollback also, but it turns out that one clever user has wondered onto the page where you can manually move between tasks in a process using the native jbpm-console. Doing that totally messes up things as it leaves the original task open.
We used to link to the native console to show the current process image and the current active task. It turns out there is no way to clamp down permissions sufficiently using the properties file provided.
The solution was to eliminate all access to the native console except for a few admins who understand how to use it. We just serve up the static process image retrieved from the process definition file through a little servlet and the user has to locate the task name on it. The current task name is provided in a small pop up screen.
This incident gave me serious grief and I never seen it in the development environment. We are using JBPM in a production pilot at this point.
Thanks,
Tamas
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254861#4254861
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254861
16 years, 7 months
[Javassist Users] - Instrumenting SQL execution times (Statement and PreparedSta
by joachimhb
Hello,
Does anyone have any clues as to how its possible to instrument JDBC SQL query times ? I have successfully been able to instrument other classes, but I am unable to find the class that actually executes the Query.
I have tried, for each class loaded in the classloader, to looks at its implementations to check if one the class implements either java.sql.Statement or java.sql.PreparedStatement. If thats not the case, I check the superclass for up to 10 levels. The application uses DBCP, and the following classes gets instrumented:
java.sql.PreparedStatement
java.sql.CallableStatement
org.apache.commons.dbcp.DelegatingPreparedStatement
org.apache.commons.dbcp.DelegatingStatement
org.apache.derby.iapi.jdbc.EnginePreparedStatement
org.apache.derby.iapi.jdbc.EngineStatement
However, none of these classes seems to fire off the actual execute(), executeQuery() or executeUpdate methods - at least the instrumentation times do not get returned as expected.
Is there a good strategy to be able to instrument JDBC ? My main goal here is to be able to store the execution times per. SQL that is ran through the system.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254860#4254860
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254860
16 years, 7 months
[jBPM Users] - Transition Timers Not Marking a Task as Complete
by jnlugo
I have a timer on a transition in task A. When the timer fires in task A, the task follows the transition to the next task, B. However, task A is not considered complete when the timer fires and moves the task. So when I query for tasks for users assigned to task A, the task that is now in B is returned.
Is there a good way to mark task A as complete when the timer fires? I haven't had much luck with event listeners.
<process name="MyProcess" xmlns="http://jbpm.org/4.0/jpdl">
| <start name="start1">
| <transition name="to review" to="TaskA"/>
| </start>
| <task candidate-groups="#{status.taskAGroups}" name="TaskA">
| <transition name="forward" to="TaskB">
| <timer duedate="#{status.timeout}"/>
| </transition>
| </task>
| <task candidate-groups="#{status.taskBGroups}" name="TaskB">
| <transition name="forward" to="EndState"/>
| </task>
| <end name="Final" state="EndState"/>
| </process>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254859#4254859
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254859
16 years, 7 months
Error Configuring persistent unit in jpa throwing strange class cast exception
by vamsi
Hi All
I am trying to configure a jta data source to persitent unit for JPA.
It is throwing a strange class cast exception,I am able to bind the data
source successfully the problems comes into picture when using the jndi to
bind to persitent unit.
Ds file
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<use-java-context>false</use-java-context>
<jndi-name>jdbc/questionaire</jndi-name>
<connection-url>jdbc:jtds:sqlserver://calcas\sqlexpress:1443/questionaire</c
onnection-url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
<user-name>sa</user-name>
<password>Passw0rd</password>
<min-pool-size>10</min-pool-size>
<max-pool-size>20</max-pool-size>
<prepared-statement-cache-size>32</prepared-statement-cache-size>
<idle-timeout-minutes>300</idle-timeout-minutes>
</local-tx-datasource>
</datasources>
java.lang.ClassCastException: $Proxy263 cannot be cast to
javax.sql.DataSource
at
org.jboss.jpa.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoI
mpl.java:111)
at
org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDepl
oyment.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUti
ls.java:59)
at
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(Reflect
MethodInfoImpl.java:150)
at
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoi
nt.java:66)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointD
ispatchWrapper.execute(KernelControllerContextAction.java:241)
at
org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrappe
r.java:47)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchEx
ecutionWrapper(KernelControllerContextAction.java:109)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJo
inPoint(KernelControllerContextAction.java:70)
at
org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(Li
fecycleAction.java:221)
at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(Instal
lsAwareAction.java:54)
at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(Instal
lsAwareAction.java:42)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInst
allAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(Ac
cessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(Abstra
ctControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractContr
ollerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.j
ava:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractContr
oller.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractCont
roller.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractCont
roller.java:984)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.j
ava:774)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.j
ava:540)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMeta
DataDeployer.java:121)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMeta
DataDeployer.java:51)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internal
Deploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(Abstrac
tRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper
.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.j
ava:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(Dep
loyersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(Dep
loyersImpl.java:1178)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.ja
va:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractContr
ollerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.j
ava:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractContr
oller.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractCont
roller.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractCont
roller.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.ja
va:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.ja
va:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.ja
va:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.j
ava:702)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.proces
s(MainDeployerAdapter.java:117)
at
org.jboss.system.server.profileservice.repository.ProfileDeployAction.instal
l(ProfileDeployAction.java:70)
at
org.jboss.system.server.profileservice.repository.AbstractProfileAction.inst
all(AbstractProfileAction.java:53)
at
org.jboss.system.server.profileservice.repository.AbstractProfileService.ins
tall(AbstractProfileService.java:361)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractContr
ollerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.j
ava:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractContr
oller.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractCont
roller.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractCont
roller.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.ja
va:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.ja
va:553)
at
org.jboss.system.server.profileservice.repository.AbstractProfileService.act
ivateProfile(AbstractProfileService.java:306)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(Profile
ServiceBootstrap.java:271)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Unknown Source)
Thanks & Regards,
VAMSI
16 years, 7 months
[EJB] - Re: NameAlreadyBoundException when migrate from JBoss 4.2.2.
by wluque
ok ,
First I will explain more about the structure of my application.
I have a EAR ( FMK ) with the basic components of my business application : security aspects , service daemons .. etc . and Statics singleton class cache of my system activities .. and more ...
FMK-EAR
--> fmk.war ( seam 2.2 ) PLATFORM CONSOLE
--> fmk-seam.jar (ejb) ( My seam's basic actions )
--> fmk-serviceEjb.jar (ejb) ( My plattaform services )
--> fmk-entities.jar (ejb/persistence) ( My basic plattaform entities / persitence unit)
DC-EAR ( Application over my FMK platform)
--> dc.war ( seam 2.2 . Utilice dc-seam/fmk-seam )
--> dc-seam.jar (ejb) ( seam actions specific of dc )
--> dc-serviceEjb.jar (ejb) ( services of dc / call too fmk-serviceEjb )
---> dc-entities.jar (ejb/persistence) extends BasicEntities of Fmk
--> fmk-seam.jar
--> fmk-serviceEjb.jar
--> fmk-entities.jar
this works fine in JBoss 4.2.2 , now when migrated to JBoss 5.1 i have two errors :
First error ( this post ) , before I have only one instance of de fmk-serviceEjb.jar (ejb) , now Error in duplicated Name .
Second Error : Deploy order of my FMK-EAR . My fmk-serviceEjb.jar (ejb) is deployed in the first time and not find my persistence unit .
I already tried everything for several weeks and I'm lost ...
Could you help me with any suggestions?
Thank You !
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254849#4254849
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254849
16 years, 7 months
[JBoss Cache Users] - JBOSSCache Node not synchronized
by vcerto
I've implemented a JbossCache cluster with two nodes distributed on different server. It has a CacheLoader based on oracle.
When I applied a modification of the cache on one node, it doesn't synchronized the other one. Following there is the xml config I used.
Where is the problem? For updating the other cluster node, I need to restart the application using it.
###########################################
<?xml version="1.0" encoding="UTF-8"?>
<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:jboss:jbosscache-core:config:3.0">
<!--
By not specifying the 'clustering' element, the cache runs in LOCAL
mode.
-->
<!--
Configure the TransactionManager
-->
<!--
Used to register JVM shutdown hooks. hookBehavior: DEFAULT, REGISTER,
DONT_REGISTER
-->
<!--
isolation levels supported: READ_COMMITTED and REPEATABLE_READ
nodeLockingSchemes: mvcc, pessimistic (deprecated), optimistic
(deprecated)
-->
<!--
This element specifies that the cache is clustered. modes supported:
replication (r) or invalidation (i).
-->
<!-- JGroups protocol stack properties. -->
<UDP discard_incompatible_packets="true" enable_bundling="false"
enable_diagnostics="false" ip_ttl="2" loopback="false"
max_bundle_size="64000" max_bundle_timeout="30" mcast_addr="228.10.10.10"
mcast_port="45588" mcast_recv_buf_size="25000000"
mcast_send_buf_size="640000" oob_thread_pool.enabled="true"
oob_thread_pool.keep_alive_time="10000" oob_thread_pool.max_threads="4"
oob_thread_pool.min_threads="1" oob_thread_pool.queue_enabled="true"
oob_thread_pool.queue_max_size="10"
oob_thread_pool.rejection_policy="Run" thread_naming_pattern="pl"
thread_pool.enabled="true" thread_pool.keep_alive_time="30000"
thread_pool.max_threads="25" thread_pool.min_threads="1"
thread_pool.queue_enabled="true" thread_pool.queue_max_size="10"
thread_pool.rejection_policy="Run" tos="8" ucast_recv_buf_size="20000000"
ucast_send_buf_size="640000" use_concurrent_stack="true"
use_incoming_packet_handler="true" />
<PING num_initial_members="3" timeout="2000" />
<MERGE2 max_interval="30000" min_interval="10000" />
<FD_SOCK />
<FD max_tries="5" shun="true" timeout="10000" />
<VERIFY_SUSPECT timeout="1500" />
<pbcast.NAKACK discard_delivered_msgs="true" gc_lag="0"
retransmit_timeout="300,600,1200,2400,4800" use_mcast_xmit="false" />
<pbcast.STABLE desired_avg_gossip="50000" max_bytes="400000"
stability_delay="1000" />
<pbcast.GMS join_timeout="5000" print_local_addr="true"
shun="false" view_ack_collection_timeout="5000" view_bundling="true" />
<FRAG2 frag_size="60000" />
<pbcast.STREAMING_STATE_TRANSFER />
<pbcast.FLUSH timeout="0" />
<!--
<UDP discard_incompatible_packets="true" enable_bundling="false"
enable_diagnostics="false" ip_ttl="2" loopback="false"
max_bundle_size="64000" max_bundle_timeout="30"
mcast_addr="228.10.10.10" mcast_port="45588"
mcast_recv_buf_size="25000000" mcast_send_buf_size="640000"
oob_thread_pool.enabled="true"
oob_thread_pool.keep_alive_time="10000"
oob_thread_pool.max_threads="4" oob_thread_pool.min_threads="1"
oob_thread_pool.queue_enabled="true"
oob_thread_pool.queue_max_size="10"
oob_thread_pool.rejection_policy="Run" thread_naming_pattern="pl"
thread_pool.enabled="true" thread_pool.keep_alive_time="30000"
thread_pool.max_threads="25" thread_pool.min_threads="1"
thread_pool.queue_enabled="true" thread_pool.queue_max_size="10"
thread_pool.rejection_policy="Run" tos="8"
ucast_recv_buf_size="20000000" ucast_send_buf_size="640000"
use_concurrent_stack="true" use_incoming_packet_handler="true"/>
<PING num_initial_members="3" timeout="2000"/> <MERGE2
max_interval="30000" min_interval="10000"/> <FD_SOCK/> <FD
max_tries="5" shun="true" timeout="10000"/> <VERIFY_SUSPECT
timeout="1500"/> <pbcast.NAKACK discard_delivered_msgs="true"
gc_lag="0" retransmit_timeout="300,600,1200,2400,4800"
use_mcast_xmit="false"/>
<pbcast.STABLE desired_avg_gossip="50000" max_bytes="400000"
stability_delay="1000"/> <pbcast.GMS join_timeout="5000"
print_local_addr="true" shun="false"
view_ack_collection_timeout="5000" view_bundling="true"/> <FRAG2
frag_size="60000"/> <pbcast.STREAMING_STATE_TRANSFER/> <pbcast.FLUSH
timeout="0"/>
-->
<!--
Alternatively, to use async replication, comment out the element
above and uncomment the element below.
-->
<!-- -->
<async useReplQueue=true replQueueInterval="1000" replQueueMaxElements="1" serializationExecutorPoolSize="10" serializationExecutorQueueSize="5000000" />
<!-- Specific eviction policy configurations -->
<!--
Cache Passivation for Tree Cache On passivation, The objects are
written to the backend store on eviction if passivation is true,
otherwise the objects are persisted. On activation, the objects are
restored in the memory cache and removed from the cache loader if
'passivation' attribute is true, otherwise the objects are only loaded
from the cache loader
-->
<!--
if passivation is true, only the first cache loader is used; the rest
are ignored
-->
<!--
fetchPersistenceState must be set to true only for one element of the
cluster
-->
cache.jdbc.table.name=jbosscache
cache.jdbc.table.create=true
cache.jdbc.table.drop=false
cache.jdbc.table.primarykey=jbosscache_pk
cache.jdbc.fqn.column=fqn
cache.jdbc.fqn.type=VARCHAR(255)
cache.jdbc.node.column=node
cache.jdbc.node.type=BLOB
cache.jdbc.parent.column=parent
cache.jdbc.driver=oracle.jdbc.OracleDriver
cache.jdbc.url=jdbc:oracle:thin:@XXXXXX:1521:ORCL
cache.jdbc.user=user
cache.jdbc.password=password
##########################################
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254841#4254841
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254841
16 years, 7 months