[JBoss jBPM] - Urgent Help Required
by muddsar
Hi All,
i am new to JBPM and i am trying to use Oralce as my database,i tried to follow the instructions given on this post
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116029
but after following this instruction i am getting following error,please suggest me some solution.
22:19:00,308 INFO [Configuration] Configuration resource: hibernate.cfg.xml
22:19:00,323 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer
ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: CONFIGURED
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq.destination:service=Queue,name=JbpmCommandQueue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=JbpmJobQueue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=Invoker
State: CONFIGURED
I Depend On:
jboss.mq:service=TracingInterceptor
jboss:service=Naming
Depends On Me:
jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
jboss.mq:service=InvocationLayer,type=UIL2
ObjectName: jboss.mq:service=TracingInterceptor
State: CONFIGURED
I Depend On:
jboss.mq:service=SecurityManager
Depends On Me:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=SecurityManager
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
Depends On Me:
jboss.mq:service=TracingInterceptor
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq.destination:service=Queue,name=DLQ
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq:service=InvocationLayer,type=JVM
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=StateManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=DestinationManager
State: CONFIGURED
I Depend On:
jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
Depends On Me:
jboss.mq.destination:service=Queue,name=JbpmCommandQueue
jboss.mq.destination:service=Queue,name=JbpmJobQueue
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq:service=PersistenceManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079284#4079284
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079284
17Â years, 2Â months
[Beginners Corner] - Could not get EJBHome
by stefan_jing
Hi all,
i am trying to run the client:
package de.ejbkomplett.reisebuero.client;
import de.ejbkomplett.reisebuero.usecase.*;
import javax.ejb.EJBMetaData;
import javax.ejb.HomeHandle;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
import java.sql.Date;
import java.util.*;
public class Client {
public static void main(String[] args) {
System.out.println("*****************************");
System.out.println("** Test-Client Kapitel 04 **");
System.out.println("** HomeHandle-Beispiel **");
System.out.println("** gestartet... **");
System.out.println("*****************************\n");
try {
// 1. JNDI-Context ermitteln
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
env.put("java.naming.provider.url", "localhost:1099");
Context context = new InitialContext(env);
System.out.println("*** Mit JNDI-Namensdienst verbunden...");
// 2. Home-Objekt über JNDI holen
Object o = context.lookup("FlugSuche");
FlugSucheHome home = (FlugSucheHome)
PortableRemoteObject.narrow(o, FlugSucheHome.class);
System.out.println("*** Referenz auf Home-Objekt FlugSuche erhalten...");
System.out.println("*** FlugSuche Bean - HashCode: " + ((Object)home).hashCode());
System.out.println("*** FlugSuche Bean - Klasse : " + ((Object)home).toString());
// 3. EJBObject erzeugen
FlugSuche suche = home.create();
System.out.println("*** FlugSuche Bean ist erzeugt...");
// 4. HomeHandle der EJB-Komponente beim Home Interface anfordern
javax.ejb.HomeHandle hh = home.getHomeHandle();
// 5. HomeHandle serialisieren
System.out.println("*** HomeHandle wird serialisiert...\n");
java.io.FileOutputStream fileOut = new java.io.FileOutputStream("homehandle.ser");
java.io.ObjectOutputStream objectOut = new java.io.ObjectOutputStream(fileOut);
objectOut.writeObject(hh);
objectOut.flush();
fileOut.close();
hh = null; //HomeHandle löschen
suche.remove(); //EJBObject wieder löschen
// 6. HomeHandle deserialisieren
System.out.println("*** HomeHandle wird deserialisiert...");
java.io.FileInputStream fileIn = new java.io.FileInputStream("homehandle.ser");
java.io.ObjectInputStream objectIn = new java.io.ObjectInputStream(fileIn);
javax.ejb.HomeHandle handleNeu = (javax.ejb.HomeHandle)objectIn.readObject();
fileIn.close();
//Home-Objekt vom HomeHandle erfragen.
//Bei Aufruf der Methode getEJBHome() sorgt die Implemen-
//tierung des HomeHandles dafür, eine funktionsfähige
//Referenz auf das Home Interface zur Verfügung zu stellen.
javax.ejb.EJBHome homeNew = (FlugSucheHome)handleNeu.getEJBHome();
//Nach dem Cast auf das FlugSucheHome Interface steht das
//Remote Home Interface wieder zur Verfügung und kann für
//die Steuerung des Lebenszyklus einer FlugSuche-Komponente
//genutzt werden.
FlugSucheHome sucheNeuHome = (FlugSucheHome)PortableRemoteObject.narrow(homeNew, FlugSucheHome.class);
System.out.println("*** FlugSuche Bean - HashCode: " + ((Object)sucheNeuHome).hashCode());
System.out.println("*** FlugSuche Bean - Klasse : " + ((Object)sucheNeuHome).toString());
FlugSuche sucheNeu = sucheNeuHome.create();
//EJBObject wieder löschen
sucheNeu.remove();
} catch (Exception e) {
e.printStackTrace();
}
}
}
then I get the following message:
[java] *****************************
[java] ** Test-Client Kapitel 04 **
[java] ** HomeHandle-Beispiel **
[java] ** gestartet... **
[java] *****************************
[java] *** Mit JNDI-Namensdienst verbunden...
[java] *** Referenz auf Home-Objekt FlugSuche erhalten...
[java] *** FlugSuche Bean - HashCode: 15232416
[java] *** FlugSuche Bean - Klasse : FlugSucheHome
[java] log4j:WARN No appenders could be found for logger (org.jboss.security.SecurityAssociation).
[java] log4j:WARN Please initialize the log4j system properly.
[java] *** FlugSuche Bean ist erzeugt...
[java] *** HomeHandle wird serialisiert...
[java] *** HomeHandle wird deserialisiert...
[java] java.rmi.ServerException: Could not get EJBHome; nested exception is:
[java] javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
[java] at org.jboss.proxy.ejb.handle.HomeHandleImpl.getEJBHome(HomeHandleImpl.java:107)
[java] at de.ejbkomplett.reisebuero.client.Client.main(Client.java:73)
[java] Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
[java] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
[java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
[java] at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:351)
[java] at org.jboss.proxy.ejb.handle.HomeHandleImpl.getEJBHome(HomeHandleImpl.java:102)
[java] ... 1 more
please help me!
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079281#4079281
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079281
17Â years, 2Â months
[Messaging, JMS & JBossMQ] - JBossMQ ThreadPoolFullException
by bowlere
Hi,
I'm running JBoss 4.2.1, with an external program delivering JMS messages to and MDB. The whole setup seems to run for a little while, but pretty soon, I start getting exceptions thrown, and after a few mins get the exceptions below. In the MDB I have a try / catch (Throwable) around the contents of onMessage in an attempt to stop any problems with my code stopping the Thread from being returned to the pool. I've tried upping the size of the threadpool, to no avail. I guess I'd like to know what circumstances would stop a thread from being returned to the pool. But mostly I just want to fix my problem ... any ideas ?
Many Thanks
Ed
| 2007-08-29 15:15:04,662 WARN [BasicQueue] Caught unusual exception sending message to receiver.
| org.jboss.util.threadpool.ThreadPoolFullException: java.lang.InterruptedException
| at org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:417)
| at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)
| at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212)
| at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206)
| at org.jboss.mq.server.ClientConsumer.queueMessageForSending(ClientConsumer.java:125)
| at org.jboss.mq.server.BasicQueue.queueMessageForSending(BasicQueue.java:1140)
| at org.jboss.mq.server.BasicQueue.internalAddMessage(BasicQueue.java:1111)
| at org.jboss.mq.server.BasicQueue.access$000(BasicQueue.java:76)
| at org.jboss.mq.server.BasicQueue$AddMessagePostCommitTask.run(BasicQueue.java:1359)
| at org.jboss.mq.pm.TxManager.addPostCommitTask(TxManager.java:162)
| at org.jboss.mq.server.BasicQueue.performOrPrepareAddMessage(BasicQueue.java:411)
| at org.jboss.mq.server.BasicQueue.addMessage(BasicQueue.java:383)
| at org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:76)
| at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:180)
| at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:415)
| at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:399)
| at org.jboss.mq.server.JMSServerInterceptorSupport.addMessage(JMSServerInterceptorSupport.java:106)
| at org.jboss.mq.security.ServerSecurityInterceptor.addMessage(ServerSecurityInterceptor.java:168)
| at org.jboss.mq.server.TracingInterceptor.addMessage(TracingInterceptor.java:226)
| at org.jboss.mq.server.JMSServerInvoker.addMessage(JMSServerInvoker.java:112)
| at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:114)
| at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
| at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
| at java.lang.Thread.run(Thread.java:619)
|
| 2007-08-29 15:32:11,663 ERROR [BasicQueue] Caught unusual exception in nackMessage for 2379 msg=2378 hard STORED PERSISTENT queue=QUEUE.ASMGCSFlightUpdate priority=4 lateClone=false hashCode=32408976
| org.jboss.mq.SpyJMSException: Could not update the message in the database: update affected 0 rows
| at org.jboss.mq.pm.jdbc2.PersistenceManager.update(PersistenceManager.java:1298)
| at org.jboss.mq.server.BasicQueue.nackMessage(BasicQueue.java:482)
| at org.jboss.mq.server.BasicQueue$RestoreMessageTask.run(BasicQueue.java:1383)
| at org.jboss.mq.pm.TxManager.addPostCommitTask(TxManager.java:162)
| at org.jboss.mq.server.BasicQueue.acknowledge(BasicQueue.java:742)
| at org.jboss.mq.server.BasicQueue.nackMessages(BasicQueue.java:820)
| at org.jboss.mq.server.JMSQueue.nackMessages(JMSQueue.java:117)
| at org.jboss.mq.server.ClientConsumer.close(ClientConsumer.java:202)
| at org.jboss.mq.server.JMSDestinationManager.connectionClosing(JMSDestinationManager.java:525)
| at org.jboss.mq.server.JMSServerInterceptorSupport.connectionClosing(JMSServerInterceptorSupport.java:96)
| at org.jboss.mq.security.ServerSecurityInterceptor.connectionClosing(ServerSecurityInterceptor.java:77)
| at org.jboss.mq.server.TracingInterceptor.connectionClosing(TracingInterceptor.java:161)
| at org.jboss.mq.server.JMSServerInvoker.connectionClosing(JMSServerInvoker.java:102)
| at org.jboss.mq.il.jvm.JVMServerIL.connectionClosing(JVMServerIL.java:126)
| at org.jboss.mq.Connection.close(Connection.java:601)
| ..........SNIP
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079280#4079280
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079280
17Â years, 2Â months
[JBoss jBPM] - Re: Unable to insert new process definitions.
by kinshuk_in
This did'nt work for me, both for ISASYNC_ and all other bit columns. No matter which version and driver I used on mySQL. What worked was changing all the bit fields in mysql to tinyint(1). This issue is probably due to - http://jira.jboss.com/jira/browse/BPEL-182 or http://jira.jboss.com/jira/browse/JBPM-443
sticking the ALTER script here :...
ALTER TABLE JBPM_PROCESSDEFINITION MODIFY ISTERMINATIONIMPLICIT_ TINYINT(1);
ALTER TABLE JBPM_ACTION MODIFY ISASYNC_ TINYINT(1);
ALTER TABLE JBPM_ACTION MODIFY ISPROPAGATIONALLOWED_ TINYINT(1);
ALTER TABLE JBPM_NODE MODIFY ISASYNC_ TINYINT(1);
ALTER TABLE JBPM_NODE MODIFY ISASYNCEXCL_ TINYINT(1);
ALTER TABLE JBPM_NODE MODIFY CREATETASKS_ TINYINT(1);
ALTER TABLE JBPM_NODE MODIFY ENDTASKS_ TINYINT(1);
ALTER TABLE JBPM_PROCESSINSTANCE MODIFY ISSUSPENDED_ TINYINT(1);
ALTER TABLE JBPM_TASK MODIFY ISBLOCKING_ TINYINT(1);
ALTER TABLE JBPM_TASK MODIFY ISSIGNALLING_ TINYINT(1);
ALTER TABLE JBPM_TASKINSTANCE MODIFY ISCANCELLED_ TINYINT(1);
ALTER TABLE JBPM_TASKINSTANCE MODIFY ISSUSPENDED_ TINYINT(1);
ALTER TABLE JBPM_TASKINSTANCE MODIFY ISOPEN_ TINYINT(1);
ALTER TABLE JBPM_TASKINSTANCE MODIFY ISSIGNALLING_ TINYINT(1);
ALTER TABLE JBPM_TASKINSTANCE MODIFY ISBLOCKING_ TINYINT(1);
ALTER TABLE JBPM_TOKEN MODIFY ISABLETOREACTIVATEPARENT_ TINYINT(1);
ALTER TABLE JBPM_TOKEN MODIFY ISTERMINATIONIMPLICIT_ TINYINT(1);
ALTER TABLE JBPM_TOKEN MODIFY ISSUSPENDED_ TINYINT(1);
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079279#4079279
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079279
17Â years, 2Â months
[JBoss jBPM] - Re: Modifying a process already in progress
by lfelser
Definitely looking to solve the general case.
In the typical case, the process is not changed once started, but occasionally either the task assignment has to change (prior to the task being assigned) or a new user and new task assigned. Sometimes the task is removed, but that's a relatively easy case that I've got working now.
Some notes:
1) assignments can't be taken from a pool for the tasks. They are very specific and are set up when the process is created (using custom assignment handlers that get the assignment name from the data given in the process definition's XML).
2) each process definition is unique because of the above.
3) we have custom web-based process authoring that allows the process author to assign variable numbers of parallel tasks. The forks and joins are added by my code in this case. While the processes always have the same general sequence, entire sets of nodes may not be created if the process author has decided that those steps are not necessary for a particular case. Being red-blooded human users though, they sometimes change their minds.
LF
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079276#4079276
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079276
17Â years, 2Â months