[JBoss jBPM] - Question about retrieving User Object from ExecutionContext
by RomeuFigueira
So, I've got this object:
public class MySerializableClass implements java.io.Serializable {
|
| private static final long serialVersionUID = 1L;
|
| int member;
|
| public MySerializableClass(int member){
| this.member = member;
| }
|
| public boolean equals(Object o) {
| if (! (o instanceof MySerializableClass)) return false;
| return ( member == ((MySerializableClass)o).member );
| }
| }
which I put into the context in a certain node by:
context.setVariable("a", new MySerializableClass(4));
and then further down the workflow, I try to retrieve through this operation:
MySerializableClass msc = (MySerializableClass) context.getVariable("a");
And this operation leads to this error:
java.lang.ClassCastException: common.types.MySerializableClass
| at jbpm.notifications.InsertEvent_ActionHandler.execute(InsertEvent_ActionHandler.java:55)
| at org.jbpm.graph.def.Action.execute(Action.java:123)
| at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:235)
| at org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:212)
| at org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphElement.java:182)
| at org.jbpm.graph.def.GraphElement.fireEvent(GraphElement.java:166)
| at org.jbpm.graph.def.Node.enter(Node.java:301)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:205)
| at org.jbpm.graph.def.Node_$$_javassist_46.enter(Node_$$_javassist_46.java)
| at org.jbpm.graph.def.Transition.take(Transition.java:119)
| at org.jbpm.graph.def.Node.leave(Node.java:383)
| at org.jbpm.graph.exe.ExecutionContext.leaveNode(ExecutionContext.java:136)
| at org.jbpm.graph.node.Decision.execute(Decision.java:146)
| at org.jbpm.graph.def.Node.enter(Node.java:316)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:205)
| at org.jbpm.graph.def.Node_$$_javassist_46.enter(Node_$$_javassist_46.java)
| at org.jbpm.graph.def.Transition.take(Transition.java:119)
| at org.jbpm.graph.def.Node.leave(Node.java:383)
| at org.jbpm.graph.node.StartState.leave(StartState.java:70)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:205)
| at org.jbpm.graph.def.Node_$$_javassist_46.leave(Node_$$_javassist_46.java)
| at org.jbpm.graph.exe.Token.signal(Token.java:178)
| at org.jbpm.graph.exe.Token.signal(Token.java:123)
| at vvp.ws.notifications.NotificationsWS.Notify(NotificationsWS.java:122)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.ws.server.ServiceEndpointInvokerJSE.invokeServiceEndpoint(ServiceEndpointInvokerJSE.java:91)
| at org.jboss.ws.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:151)
| at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:195)
| at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:373)
| at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:116)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:77)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
Now, I've searched the forums, and the best awnser that I've got was this one from JoeDeveloper:
http://blogs.sourceallies.com/roller/page/joedeveloper?entry=jbpm_3_1_aut...
Now, I've tried his approach and still no go, so what possibly could be wrong here?
PS: My class is taken from the jbpm examples (VariableInstanceDbTest.java), which doesnt try to get the object back, only does an assertEquals.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008374#4008374
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008374
19 years, 2 months
[Installation, Configuration & Deployment] - Re: Deployment on custom server
by bnraju1
My original intent was to use only Messaging. So I did the following to create a "standalone-messaging" server.
1) Extracted jboss-4.0.4.GA.zip to C:\java folder
2) Extracted jboss-messaging-1.0.1.GA.zip C:\java folder.
3) Extracted apache-ant-1.6.5-bin.zip to C:\java
4) Opened a command prompt and did the following:
cd C:\java\jboss-messaging-1.0.1.GA\util
set JBOSS_HOME=C:\java\jboss-4.0.4.GA
C:\java\apache-ant-1.6.5\bin\ant -f release-admin.xml standalone
Now, when I tried to deploy an EAR to "standalone-messaging" server (I did not remove any files), I received the following exception:
2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.MainDeployer] Deployment of package: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear is waiting for an appropriate deployer.
2007-01-30 11:03:56,697 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear -> file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
2007-01-30 11:03:56,697 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@c94153c9 { url=file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
altDD: null
lastDeployed: 1170173036697
lastModified: 1170173036697
mbeans:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@c94153c9 { url=file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/deploy/Test.ear
altDD: null
lastDeployed: 1170173036697
lastModified: 1170173036697
mbeans:
2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true
2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Started jboss.deployment:flavor=URL,type=DeploymentScanner
2007-01-30 11:03:56,728 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.deployment:flavor=URL,type=DeploymentScanner dependent components: []
2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml
2007-01-30 11:03:56,728 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/java/jboss-4.0.4.GA/server/standalone-messaging/conf/jboss-service.xml
2007-01-30 11:03:56,728 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Saw org.jboss.system.server.started notification, starting connectors
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008371#4008371
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008371
19 years, 2 months
[JBossCache] - TreeCache - Does my cached objects must implement Serializab
by balderman＠gmail.com
Hi
I am using the TreeCache version 1.4.1.
I want the cache to notify other nodes that a cached object is invalid.
So this is how I configure it:
<attribute name="CacheMode">INVALIDATION_SYNC</attribute>
But when I remove the Serializable inferface from my Object I get a serialization exception.
Under this configuration I do not expect that the object will be serialized...
Here is full config file:
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Sample TreeCache Service Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <server>
|
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
|
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=TreeCache">
|
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
|
| <!--
| Configure the TransactionManager
| -->
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
|
|
| <!--
| Node locking level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <attribute name="CacheMode">INVALIDATION_SYNC</attribute>
|
|
| <!--
| Just used for async repl: use a replication queue
| -->
| <attribute name="UseReplQueue">false</attribute>
|
| <!--
| Replication interval for replication queue (in ms)
| -->
| <attribute name="ReplQueueInterval">20000</attribute>
|
| <!--
| Max number of elements which trigger replication
| -->
| <attribute name="ReplQueueMaxElements">5</attribute>
|
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other
| -->
| <attribute name="ClusterName">TreeCache-Cluster</attribute>
|
| <!-- JGroups protocol stack properties. Can also be a URL,
| e.g. file:/home/bela/default.xml
| <attribute name="ClusterProperties"></attribute>
| -->
|
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address -->
| <!-- UDP: On Windows machines, because of the media sense feature
| being broken with multicast (even after disabling media sense)
| set the loopback attribute to true -->
| <UDP mcast_addr="230.8.8.8" mcast_port="56677"
| ip_ttl="32" ip_mcast="true"
| mcast_send_buf_size="80000" mcast_recv_buf_size="150000"
| ucast_send_buf_size="80000" ucast_recv_buf_size="150000"
| loopback="false"/>
| <PING timeout="2000" num_initial_members="3"
| up_thread="false" down_thread="false"/>
| <MERGE2 min_interval="10000" max_interval="20000"/>
| <FD shun="true" up_thread="true" down_thread="true"/>
| <VERIFY_SUSPECT timeout="1500"
| up_thread="false" down_thread="false"/>
| <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
| max_xmit_size="8192" up_thread="false" down_thread="false"/>
| <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10"
| down_thread="false"/>
| <pbcast.STABLE desired_avg_gossip="20000"
| up_thread="false" down_thread="false"/>
| <FRAG frag_size="8192"
| down_thread="false" up_thread="false"/>
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
| shun="true" print_local_addr="true"/>
| <pbcast.STATE_TRANSFER up_thread="false" down_thread="false"/>
| </config>
| </attribute>
|
|
| <!--
| The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">20000</attribute>
|
| <!--
| Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">20000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">15000</attribute>
|
| <!-- Name of the eviction policy class. Not supported now. -->
| <attribute name="EvictionPolicyClass"></attribute>
|
| <!--
| Whether or not to fetch state on joining a cluster
| NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
| -->
| <attribute name="FetchInMemoryState">true</attribute>
|
| <!-- this is the OLD 1.2.x cache loader configuration block.
|
| <attribute name="CacheLoaderClass">org.jboss.cache.loader.FileCacheLoader</attribute>
| <attribute name="CacheLoaderConfig">
| location=c:\\tmp\\node1
| </attribute>
| <attribute name="CacheLoaderShared">false</attribute>
| <attribute name="CacheLoaderPreload">/</attribute>
| <attribute name="CacheLoaderFetchTransientState">false</attribute>
| <attribute name="CacheLoaderFetchPersistentState">true</attribute>
| <attribute name="CacheLoaderPassivation">false</attribute>
| -->
|
| <!-- New 1.3.x cache loader config block -->
| <attribute name="CacheLoaderConfiguration">
| <config>
| <!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
| <passivation>false</passivation>
| <preload>/</preload>
| <shared>false</shared>
|
| <!-- we can now have multiple cache loaders, which get chained -->
| <cacheloader>
| <class>org.jboss.cache.loader.FileCacheLoader</class>
| <!-- same as the old CacheLoaderConfig attribute -->
| <properties>
| location=/tmp/node1
| </properties>
| <!-- whether the cache loader writes are asynchronous -->
| <async>false</async>
| <!-- only one cache loader in the chain may set fetchPersistentState to true.
| An exception is thrown if more than one cache loader sets this to true. -->
| <fetchPersistentState>true</fetchPersistentState>
| <!-- determines whether this cache loader ignores writes - defaults to false. -->
| <ignoreModifications>false</ignoreModifications>
| <!-- if set to true, purges the contents of this cache loader when the cache starts up.
| Defaults to false. -->
| <purgeOnStartup>false</purgeOnStartup>
| </cacheloader>
|
| </config>
| </attribute>
|
| </mbean>
|
|
|
| <!-- Uncomment to get a graphical view of the TreeCache MBean above -->
| <!-- <mbean code="org.jboss.cache.TreeCacheView" name="jboss.cache:service=TreeCacheView">-->
| <!-- <depends>jboss.cache:service=TreeCache</depends>-->
| <!-- <attribute name="CacheService">jboss.cache:service=TreeCache</attribute>-->
| <!-- </mbean>-->
|
|
|
| </server>
Thanks
Avishay
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008369#4008369
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008369
19 years, 2 months