[JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?
by avbentem
Actually, I think one day I also might want to start a task as soon as one assigns it to oneself, and show the appropriate page right away. In the DVD Store example the following is used:
<h:dataTable value="#{pooledTaskInstanceList}" var="task">
| :
| <s:button action="#{pooledTask.assignToCurrentActor}"
| taskInstance="#{task}" value="Assign"/>
| :
| </h:dataTable>
After clicking the button above, the new assigned task is listed in #{taskInstanceListForType['approve']}, and can then be started. But how to start the task right away, so as soon as the task is assigned to oneself?
I could rewrite this to:
<s:button action="#{taskSelector.assignToCurrentActor}"
| taskInstance="#{task}" value="Assign"/>
using
@Name("taskSelector")
| public class TaskSelector {
| @In TaskInstance taskInstance;
| @In Actor actor;
| :
| public String assignToCurrentActor(){
| taskInstance.setActorId(actor.getId());
|
| // Or maybe one should use the following?
| // jbpmContext.getTaskMgmtSession().loadTaskInstance(taskId)
| // .assign(actor.getId());
|
| return taskInstance.getName();
| }
| :
This allows me to go to a task-specific page right away, but at that point the task has not been started yet. So this needs something more...
Thanks for any thoughts,
Arjan.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030504#4030504
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030504
19Â years, 1Â month
[Installation, Configuration & Deployment] - JBoss 4.2.0.CR1 problem installing into directory containing
by DarrenGJones
JDK: 1.6.0
OS: Windows XP
If I unzip the JBoss 4.2.0.CR1 zip into a directory with a space character in it, e.g. C:\Program Files, and execute bin/run.bat right away, the server fails to start up reporting an exception ultimately caused by:
java.net.URISyntaxException: Illegal character in path at index 16: file:/C:/Program Files/jboss-4.2.0.CR1/server/default/deploy/jbossws.sar/jaxb-api.jar
If I unzip into "C:\Code" JBoss starts up perfectly.
The same issue seems to have been reported against version 5.0.0.Beta:
http://jira.jboss.com/jira/browse/JBAS-3866
Please advise on confirming this issue and the procedure for getting this fix merged into 4.2.0?
Thanks.
Here's the start of the JBoss trace with the full exception in it:
C:\Program Files\jboss-4.2.0.CR1\bin>run
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files\jboss-4.2.0.CR1
JAVA: C:\Program Files\Java\jdk1.6.0\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.ser
ver.gcInterval=3600000
CLASSPATH: C:\Program Files\Java\jdk1.6.0\lib\tools.jar;C:\Program Files\jboss-4.2.0.CR1\bin\run.jar
===============================================================================
08:53:57,191 INFO [Server] Starting JBoss (MX MicroKernel)...
08:53:57,191 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200703051212)
08:53:57,191 INFO [Server] Home Dir: C:\Program Files\jboss-4.2.0.CR1
08:53:57,191 INFO [Server] Home URL: file:/C:/Program Files/jboss-4.2.0.CR1/
08:53:57,191 INFO [Server] Patch URL: null
08:53:57,191 INFO [Server] Server Name: default
08:53:57,191 INFO [Server] Server Home Dir: C:\Program Files\jboss-4.2.0.CR1\server\default
08:53:57,191 INFO [Server] Server Home URL: file:/C:/Program Files/jboss-4.2.0.CR1/server/default/
08:53:57,191 INFO [Server] Server Log Dir: C:\Program Files\jboss-4.2.0.CR1\server\default\log
08:53:57,191 INFO [Server] Server Temp Dir: C:\Program Files\jboss-4.2.0.CR1\server\default\tmp
08:53:57,191 INFO [Server] Root Deployment Filename: jboss-service.xml
08:53:57,426 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
08:53:57,426 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc.
08:53:57,426 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
08:53:57,754 INFO [Server] Core system initialized
08:53:59,441 INFO [WebService] Using RMI server codebase: http://localhost:8083/
08:53:59,441 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
08:53:59,785 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
08:53:59,785 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
08:53:59,925 INFO [TransactionManagerService] Starting recovery manager
08:53:59,988 INFO [TransactionManagerService] Recovery manager started
08:53:59,988 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
08:54:02,050 INFO [EJB3Deployer] Starting java:comp multiplexer
08:54:02,425 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Program Files/jboss-4.2.0.CR1/server/default
/deploy/jbossws.sar/
org.jboss.deployment.DeploymentException: exception in init of file:/C:/Program Files/jboss-4.2.0.CR1/server/default/dep
loy/jbossws.sar/jaxb-api.jar; - nested throwable: (java.lang.RuntimeException: Not a valid URL: file:/C:/Program Files/j
boss-4.2.0.CR1/server/default/deploy/jbossws.sar/jaxb-api.jar)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:901)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:26
3)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:499)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: Not a valid URL: file:/C:/Program Files/jboss-4.2.0.CR1/server/default/deploy/jbo
ssws.sar/jaxb-api.jar
at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48)
at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:57)
at org.jboss.ejb3.EJB3Deployer.hasEjbAnnotation(EJB3Deployer.java:203)
at org.jboss.ejb3.EJB3Deployer.accepts(EJB3Deployer.java:265)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy34.accepts(Unknown Source)
at org.jboss.deployment.MainDeployer.findDeployer(MainDeployer.java:1078)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:857)
... 68 more
Caused by: java.net.URISyntaxException: Illegal character in path at index 16: file:/C:/Program Files/jboss-4.2.0.CR1/se
rver/default/deploy/jbossws.sar/jaxb-api.jar
at java.net.URI$Parser.fail(URI.java:2809)
at java.net.URI$Parser.checkChars(URI.java:2982)
at java.net.URI$Parser.parseHierarchical(URI.java:3066)
at java.net.URI$Parser.parse(URI.java:3014)
at java.net.URI.(URI.java:578)
at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:44)
... 88 more
08:54:03,112 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0\bin;.;C:\WINDOWS\Sun\Java\bin;C:\W
INDOWS\system32;C:\WINDOWS;C:\oracle\product\10.2.0\client_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
;C:\Program Files\ATI Technologies\ATI.ACE\
08:54:03,190 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
08:54:03,190 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
08:54:03,190 INFO [Catalina] Initialization processed in 187 ms
08:54:03,190 INFO [StandardService] Starting service jboss.web
08:54:03,190 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.CR1
08:54:03,237 INFO [Catalina] Server startup in 47 ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030502#4030502
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030502
19Â years, 1Â month
[Clustering/JBoss] - Problem with removing a Node from Cluster - HAJNDI dies
by RedChili
Hello,
I have a problem when I remove a node from a cluster. The cluster consists of 2 or more identical configured nodes on which the application is deployed via farming.
Adding nodes to the cluster works fine. As soon as the deployment is completed the JNDIView shows all registered beans and proxies:
HA-JNDI Namespace
| +- QueueConnectionFactory
| +- XAConnectionFactory
| +- HTTPXAConnectionFactory
| +- queue
| | +- D
| | +- DLQ
| | +- C
| | +- ex
| | +- B
| | +- A
| | +- testQueue
| +- HTTPConnectionFactory
| +- UIL2XAConnectionFactory[link -> XAConnectionFactory]
| +- kusssdemo
| | +- TermPeriodEM
| | | +- local (proxy: $Proxy1060 implements interface at.jku......)
| | +- StudyCodeBusinessLogicBean
| | | +- remote (proxy: $Proxy934 implements interface at.jku.......)
| | +- StudyMajorFieldBusinessLogicBean
|
Now when I shutdown a node in the cluster the proxies are removed from all nodes and not restarted again (thus leaving any application inoperable):
HA-JNDI Namespace
| +- HTTPXAConnectionFactory
| +- XAConnectionFactory
| +- QueueConnectionFactory
| +- queue
| | +- D
| | +- C
| | +- DLQ
| | +- B
| | +- ex
| | +- A
| | +- testQueue
| +- HTTPConnectionFactory
| +- UIL2XAConnectionFactory[link -> XAConnectionFactory]
| +- kusssdemo
| | +- TermPeriodEM
| | +- StudyMajorFieldBusinessLogicBean
| | +- StudyCodeBusinessLogicBean
|
The only related suspect thing I can see in the log of another (still alive) node is the "was NOT removed !!!" message:
INFO [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] New cluster view for partition DefaultPartition: 13 ([192.168.1.104:1099, 192.168.1.106:1099] delta: -1)
| DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] dead members: [192.168.1.105:1099]
| DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] membership changed from 2 to 2
| DEBUG [org.jgroups.protocols.pbcast.NAKACK] removing 192.168.1.105:7800 from received_msgs (not member anymore)
| DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Begin notifyListeners, viewID: 13
| DEBUG [org.jgroups.protocols.FD_SOCK] VIEW_CHANGE received: [192.168.1.104:7800, 192.168.1.106:7800]
| INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] I am (192.168.1.106:1099) received membershipChanged event:
| INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] Dead members: 1 ([192.168.1.105:1099])
| INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] New Members : 0 ([])
| INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] All Members : 2 ([192.168.1.104:1099, 192.168.1.106:1099])
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] purgeDeadMembers, [192.168.1.105:1099]
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] trying to remove deadMember 192.168.1.105:1099 for key DCacheBridge-DefaultJGBridge
| DEBUG [org.jgroups.protocols.FD] suspected_mbrs: [], after adjustment: []
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] 192.168.1.105:1099 was NOT removed!!!
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] trying to remove deadMember 192.168.1.105:1099 for key jboss.ha:service=HASingletonDeployer
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] 192.168.1.105:1099 was NOT removed!!!
| DEBUG [org.jgroups.protocols.FD_SOCK] determinePingDest()=192.168.1.104:7800, pingable_mbrs=[192.168.1.104:7800, 192.168.1.106:7800]
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] trying to remove deadMember 192.168.1.105:1099 for key HAJNDI
| DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] 192.168.1.105:1099 was NOT removed!!!
| DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] End notifyListeners, viewID: 13
As soon as I join any other node to the cluster again, everything continous to work fine.
Does anybody have an idea what might be wrong here?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030499#4030499
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030499
19Â years, 1Â month
[JBoss Portal] - portal cms and oracle db error
by dparisi
Hy,
I have a problem with jboss portal cms working with oracle (9.2) database.
when i try to upload a file larger than 70kb to cms the sistem crash with the following errors:
09:13:45,902 WARN [JDBCExceptionReporter] SQL Error: 17002, SQLState: null
09:13:45,902 ERROR [JDBCExceptionReporter] Eccezione IO: Read error
09:13:45,902 WARN [JDBCExceptionReporter] SQL Error: 17002, SQLState: null
09:13:45,902 ERROR [JDBCExceptionReporter] Eccezione IO: Read error
09:13:45,902 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:235)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:41)
at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
I have tried with the last jdbc (10 r2) driver for Oracle.
Can anyone help me?
I can use HSQLD on production environment?
Can i "workaround" using the cms on filesystem?
thanks at all.
Davide
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030494#4030494
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030494
19Â years, 1Â month