[Beginner's Corner] - Re: Problems with JBoss 7 and remote-interface lookup with context
by dayse rivera
dayse rivera [https://community.jboss.org/people/dayserivera] created the discussion
"Re: Problems with JBoss 7 and remote-interface lookup with context"
To view the discussion, visit: https://community.jboss.org/message/756260#756260
--------------------------------------------------------------
I'm facing the same problem.
I'm developing my first ejb 3 client on jboss 7.1. But, I can't make a lookup.
After EJB deploy the following message is shown on console:
*11:48:33,718 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1- http://www.guj.com.br/images/smilies/b2eb59423fbf5fa39342041237025880.gif (http://www.guj.com.br/images/smilies/b2eb59423fbf5fa39342041237025880.gif) JNDI bindings for session bean named CalculatorBean in deployment unit subdeployment "EJB3_Chap02.jar" of deployment "TesteEar.ear" are as follows:
java:global/TesteEar/EJB3_Chap02/CalculatorBean!calc.CalculatorRemote
java:app/EJB3_Chap02/CalculatorBean!calc.CalculatorRemote
java:module/CalculatorBean!calc.CalculatorRemote
java:jboss/exported/TesteEar/EJB3_Chap02/CalculatorBean!calc.CalculatorRemote
java:global/TesteEar/EJB3_Chap02/CalculatorBean
java:app/EJB3_Chap02/CalculatorBean
java:module/CalculatorBean*
I try to lookup as follow, but it isn't work:
*package calc.client;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingEnumeration;
import javax.naming.NamingException;
import calc.CalculatorRemote;
public class CalculatorClient {
private static CalculatorRemote remote;
public static void main(String[] args) {
try{
remote = lookupRemoteStatelessCalculator();
//context.lookup("EJB3_Chap02/" + CalculatorBean.class.getSimpleName() + "/remote");
System.out.println(remote.add(1, 1));
}catch (Exception e) {
e.printStackTrace();
}
}
private static CalculatorRemote lookupRemoteStatelessCalculator() throws NamingException {
final Hashtable jndiProperties = new Hashtable();
//jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
jndiProperties.put(Context.PROVIDER_URL, "remote://127.0.0.1:4447");
//jndiProperties.put("remote.connection.default.username","dayserivera");
//jndiProperties.put("remote.connection.default.password", "dayse");
jndiProperties.put(Context.SECURITY_PRINCIPAL, "dayserivera");
jndiProperties.put(Context.SECURITY_CREDENTIALS, "dayse");
/*
jndiProperties.put("endpoint.name", "client-endpoint");
jndiProperties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED", "false");
jndiProperties.put("remote.connections", "default");
jndiProperties.put("remote.connection.default.port", "4447");
jndiProperties.put("remote.connection.default.host", "localhost");
*/
jndiProperties.put("remote.connection.default.connect.options.org.xnio.Options.SASL_DISALLOWED_MECHANISMS", "JBOSS-LOCAL-USER");
jndiProperties.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS", "false");
jndiProperties.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT", "false");
//jndiProperties.put("jboss.naming.client.ejb.context", true);
final Context context = new InitialContext(jndiProperties);
NamingEnumeration<?> namingEnum = context.list("java");
while(namingEnum.hasMoreElements()){
Object obj = namingEnum.nextElement();
System.out.println(obj);
}
System.out.println(context.lookup("ejb:TesteEar/EJB3_Chap02//CalculatorBean!calc.CalculatorRemote"));
// The app name is the application name of the deployed EJBs. This is typically the ear name
// without the .ear suffix. However, the application name could be overridden in the application.xml of the
// EJB deployment on the server.
// Since we haven't deployed the application as a .ear, the app name for us will be an empty string
final String appName = "";
// This is the module name of the deployed EJBs on the server. This is typically the jar name of the
// EJB deployment, without the .jar suffix, but can be overridden via the ejb-jar.xml
// In this example, we have deployed the EJBs in a jboss-as-ejb-remote-app.jar, so the module name is
// jboss-as-ejb-remote-app
final String moduleName = "EJB3_Chap02";
// AS7 allows each deployment to have an (optional) distinct name. We haven't specified a distinct name for
// our EJB deployment, so this is an empty string
final String distinctName = "";
// The EJB name which by default is the simple class name of the bean implementation class
//final String beanName = CalculatorBean.class.getSimpleName();
// the remote view fully qualified class name
final String viewClassName = CalculatorRemote.class.getName();
// let's do the lookup
//return (CalculatorRemote) context.lookup("ejb:" + appName + "/" + beanName);
//return (CalculatorRemote) context.lookup("ejb:" + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "!" + viewClassName);
return (CalculatorRemote) context.lookup("ejb:TesteEar/EJB3_Chap02//CalculatorBean!calc.CalculatorRemote");
}
}
*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756260#756260]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[jBPM] - Working with Multiple Transaction Managers
by Martin Lyness
Martin Lyness [https://community.jboss.org/people/martin1yness] created the discussion
"Working with Multiple Transaction Managers"
To view the discussion, visit: https://community.jboss.org/message/756290#756290
--------------------------------------------------------------
I've been learning jBPM and working with its Spring integration. This has been a fun experience and pretty strait forward until I ran into the multiple transaction managers issue. It seems known that you can't really share transaction managers with multiple Entity Management Factories in Spring, but the duplicate of everyting (i.e. DataSources, TransactionManagers, and Entity Managment Factories) have been showing a vital limitation.
What I'm observing is an inadvertant closing of transaction manager B when a method wrapped with a transaction manager A proxy delagates to jBPM classes which are configured to use transaction manager B. You get an exception like 'EntityManager is closed, cannot commit transaction'.
What I've tried:
1. Defining a completely different datasource and transaction manager for jBPM's knowledge session than what my other persistence units are using.
2. Using the Bitronix transaction manager for the knowledge session while using spring's JPA manager for my objects.
3. Using a transaction qualifier to wrap top level method with my transaction manager and wrapping jBPM invoker classes with the workflow transaction manager.
4. Not allowing any method that might call a workflow action to be Transactional (this is the only one that works)
It is inconvienent to have my persistence code work, then have a workflow failure and not be able to rollback my last database interaction. I'm wondering if there is anyway to gain this support? I don't really understand the mechanism that is causing the Spring Transactional Apsect proxy to close the jBPM session, so if anyone has any insights into why this is happening that maybe helpful as well.
I've got a complete project I can share demonstrating the issue, it is 40mb with dependecies and 10kb of just source. If you look at the source, the problem transaction is on the 'SynchronousTask' class, comment this out and it will work.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756290#756290]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[jBPM] - Map based persistence doubt
by Christian Marmolejo
Christian Marmolejo [https://community.jboss.org/people/chrismarm] created the discussion
"Map based persistence doubt"
To view the discussion, visit: https://community.jboss.org/message/756068#756068
--------------------------------------------------------------
Hi everyone
In my current project I need to persist active processes on demand before application shutdown and reload them at a later time. For simplicity, persistence should use binary files to store serialized process and session information, so databases are not intended to be used. In this scenario I think that a map based persistence solution might be appropiate.
I have found very little info about jBPM persistence in general and even less about map based persistence, so I have tried to understand the test cases in source code with no success. I added a test case in MapPersistenceTest.java for a very simple process: Start --> Script --> EventNode --> Script --> EventNode --> Script --> End. Scripts are only used to print out some "debug" info. The code is (class MapBasedPersistenceTest.java has no changes):
@Test
public void fullCustomTest()
{
String processId = "com.telvent.prueba";
String eventType = "PrimeraSenal";
String eventType2 = "SegundaSenal";
KnowledgeBase kbase = createKBase();
StatefulKnowledgeSession crmPersistentSession = createSession(kbase);
org.drools.runtime.process.ProcessInstance process = crmPersistentSession.startProcess(processId);
long processInstanceId = process.getId();
Assert.assertEquals(ProcessInstance.STATE_ACTIVE, process.getState());
crmPersistentSession.signalEvent(eventType, null);
process = crmPersistentSession.getProcessInstance(processInstanceId);
Assert.assertNotNull(process);
int sessionId = crmPersistentSession.getId();
StatefulKnowledgeSession crmPersistentSession2 = disposeAndReloadSession(crmPersistentSession, sessionId, kbase);
crmPersistentSession2.signalEvent(eventType2, null);
process = crmPersistentSession2.getProcessInstance(processInstanceId);
Assert.assertNull(process);
}
private KnowledgeBase createKBase()
{
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource("com/telvent/SampleProcess.bpmn"), ResourceType.BPMN2);
KnowledgeBase kbase = kbuilder.newKnowledgeBase();
return kbase;
}
After the first signalEvent, the second script is executed properly but after reloading the session and firing the second signal, I expected the last script to be fired and the process finished. However, the last script isn't reached and the second assert fails as the process still waits for the first signal, not the second one. Could anyone explain what I am doing wrong?
Thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756068#756068]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[jBPM] - Problem in action handler
by Koteswar Rao
Koteswar Rao [https://community.jboss.org/people/mkrao] created the discussion
"Problem in action handler"
To view the discussion, visit: https://community.jboss.org/message/756211#756211
--------------------------------------------------------------
Hello all,
i am using jBPM3.2.2 for my project work and it is core of my project. I am using EJB 3.0 as the business layer framework and JPA as the persistence provider. To achieve the transaction isolation, i have disabled the
jBPM transaction management. so inside jbpm.cfg.xml i have made "isTranasactionenabled" to false for each context so that if some exception happens in my business layer and issued a rollback then everything should be rolled back, but exactly the problem is happening here only whenever an exception happens from jBPM side it is going to exception handler which i configured in processdefinition and if exception happens inside this exception hanlder again then it is ending up in inconsistent state. i.e. business layer work is rolling back and jbpm work is commiting and i have no idea how this is happening????
question 2:
if exception happens in assignment handler of jbpm then from catch block i am throwing that exception to process definition excpetion handler class explicitly, but when exception happens in action handler, it is automatically going to exception handler which i configured in process definition. why is it behaving differently in these two different cases???
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756211#756211]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[Beginner's Corner] - Can't connect remote to jboss as 6.1.0
by Anton Yanchev
Anton Yanchev [https://community.jboss.org/people/micros] created the discussion
"Can't connect remote to jboss as 6.1.0"
To view the discussion, visit: https://community.jboss.org/message/755955#755955
--------------------------------------------------------------
Hi Folks,
I have installed jboss-6.1.0. Final
windows 2003 Server 32Bit
java 1.7
I'm using SilkPerformer to add predifined data source and connect to Jboss server remotely and take a data.
from previous versions Jboss 4.0 and Jboss 5.0 has a xml file where a set configuration fields
that is xml file
<?xml version="1.0" encoding="ISO-8859-1"?>
<AgentConfiguration Name="JBoss 6.x" DataSourceType="Base Configuration JBoss 6.x">
<Host>lnz-jboss6</Host>
<Port>1090</Port>
<Protocol>jnp</Protocol>
<!--0 .. JSR160/RMI-->
<!--1 .. JSR160/IIOP-->
<!--2 .. JNDI-->
<!--3 .. JSR160/CORBALOC-->
<!--4 .. JSR160/RMIIIOP-->
<!--5 .. JSR160/PLAINRMI-->
<ConnectionMode>2</ConnectionMode>
<MEJBName>jmx/rmi/RMIAdaptor</MEJBName>
<UrlPostfix />
<ContextFactory>org.jnp.interfaces.NamingContextFactory</ContextFactory>
<DefaultUser />
<DefaultPassword />
<TypePropertyString>j2eeType</TypePropertyString>
<IsJsr77>true</IsJsr77>
<JvmInfo>
<JvmHomePath RecommendedVendor="SUN" RecommendedMajorVersion="2" />
<Classpath ClasspathRootDir="C:\jboss-6.1.0.Final">
<Entry>.\common\lib\jboss-management.jar</Entry>
<Entry>.\client\jbossall-client.jar</Entry>
<Entry>.\lib\dom4j.jar</Entry>
</Classpath>
<AdditionalClasspath />
<VmParameters />
</JvmInfo>
</AgentConfiguration>
That is my run.conf.bat file where i setup setings for enable remote conection
rem ### -*- batch file -*- ######################################################
rem # ##
rem # JBoss Bootstrap Script Configuration ##
rem # ##
rem #############################################################################
rem # $Id: run.conf.bat 88820 2009-05-13 15:25:44Z mailto:dimitris@jboss.org dimitris(a)jboss.org $
rem #
rem # This batch file is executed by run.bat to initialize the environment
rem # variables that run.bat uses. It is recommended to use this file to
rem # configure these variables, rather than modifying run.bat itself.
rem #
if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET
rem #
rem # Specify the JBoss Profiler configuration file to load.
rem #
rem # Default is to not load a JBoss Profiler configuration file.
rem #
rem set "PROFILER=%JBOSS_HOME%\bin\jboss-profiler.properties"
rem #
rem # Specify the location of the Java home directory (it is recommended that
rem # this always be set). If set, then "%JAVA_HOME%\bin\java" will be used as
rem # the Java VM executable; otherwise, "%JAVA%" will be used (see below).
rem #
rem set "JAVA_HOME=C:\opt\jdk1.6.0_13"
rem #
rem # Specify the exact Java VM executable to use - only used if JAVA_HOME is
rem # not set. Default is "java".
rem #
rem set "JAVA=C:\opt\jdk1.6.0_13\bin\java"
rem #
rem # Specify options to pass to the Java VM. Note, there are some additional
rem # options that are always passed by run.bat.
rem #
rem # JVM memory allocation pool parameters - modify as appropriate.
set "JAVA_OPTS=-Xms128M -Xmx512M -XX:MaxPermSize=256M"
rem # Reduce the RMI GCs to once per hour for Sun JVMs.
set "JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
rem # Warn when resolving remote XML DTDs or schemas.
set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.resolver.warning=true"
rem # Sample JPDA settings for remote socket debugging
rem set "JAVA_OPTS=%JAVA_OPTS% -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
rem # Sample JPDA settings for shared memory debugging
rem set "JAVA_OPTS=%JAVA_OPTS% -Xrunjdwp:transport=dt_shmem,address=jboss,server=y,suspend=n"
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote"
rem set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=9999"
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.authenticate=true"
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.ssl=false"
set "JAVA_OPTS=%JAVA_OPTS% -Djava.rmi.server.hostname=lnz-jboss6"
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.password.file="c:\jmxremote\jmxremote.password""
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.access.file="c:\jmxremote\jmxremote.access""
# Use the JBoss MBeanServerBuilder
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.platform.mbeanserver"
set "JAVA_OPTS=%JAVA_OPTS% -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
#Use the jboss logmanager
set "JAVA_OPTS=%JAVA_OPTS% -Djava.util.logging.manager=org.jboss.logmanager.LogManager"
set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl"
set JBOSS_CLASSPATH="C:\jboss-6.1.0.Final\lib\jboss-logmanager.jar"
rem set JBOSS_CLASSPATH="C:\jboss-6.1.0.Final\client\jbossall-client.jar"
set "JAVA_OPTS=%JAVA_OPTS% -Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory"
set "JAVA_OPTS=%JAVA_OPTS% -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces"
:JAVA_OPTS_SET
when i execute run.bat om boot.log doesn't have any error and when i open http:// http://<host>:8080 it open correctlty jboss
also when i login throuhg jconsole service:jmx:rmi:///jndi/rmi://<host>:1090/jmxconnector it connect
but when i have tried to connect remotely it shows this error log
com.segue.monitoring.jmx.common.exception.RtException: Unable to connect
at com.segue.monitoring.jmx.common.gui.swt.JMXSWTRunner.connect(JMXSWTRunner.java:312)
Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.segue.monitoring.jmx.common.runtime.DataSourceBase.createContext(DataSourceBase.java:41)
at com.segue.monitoring.jmx.jboss.datasource.JBossDataSource.bootstrap(Unknown Source)
at com.segue.monitoring.jmx.common.runtime.RemoteDataSourceBase.bootstrap(RemoteDataSourceBase.java:180)
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 sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.sun.naming.internal.VersionHelper12.loadClass(Unknown Source)
... 21 more
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at com.segue.monitoring.jmx.jboss.datasource.RemoteDataSource_Stub.bootstrap(Unknown Source)
at com.segue.monitoring.jmx.common.client.RemoteDataSourceClient.bootstrap(RemoteDataSourceClient.java:265)
at com.segue.monitoring.jmx.common.gui.swt.JMXSWTRunner.connect(JMXSWTRunner.java:301)
Caused by: java.rmi.RemoteException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.segue.monitoring.jmx.common.runtime.DataSourceBase.createContext(DataSourceBase.java:41)
at com.segue.monitoring.jmx.jboss.datasource.JBossDataSource.bootstrap(Unknown Source)
at com.segue.monitoring.jmx.common.runtime.RemoteDataSourceBase.bootstrap(RemoteDataSourceBase.java:180)
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 sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.sun.naming.internal.VersionHelper12.loadClass(Unknown Source)
... 21 more
at com.segue.monitoring.jmx.common.runtime.RemoteDataSourceBase.bootstrap(RemoteDataSourceBase.java:189)
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 sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755955#755955]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[jBPM] - How can I see process in JBPM 5.3.0 console?
by Anatoliy Kalenskiy
Anatoliy Kalenskiy [https://community.jboss.org/people/cybiks] created the discussion
"How can I see process in JBPM 5.3.0 console?"
To view the discussion, visit: https://community.jboss.org/message/755434#755434
--------------------------------------------------------------
I have created some proces inside my application via spring config in standard way:
<jbpm:kbase id="kbase">
<jbpm:resources>
<jbpm:resource type="BPMN2" source="classpath:Looping.bpmn"/>
</jbpm:resources>
</jbpm:kbase>
<jbpm:ksession id="ksession" type="stateful" kbase="kbase" />
I have changed all nesessary configs of
designer.war , drools-guvnor.war, jbpm-form-builder.war,jbpm-gwt-console.war,jbpm-gwt-console-server.war,jbpm-human-task-war.war to use the same Oracle schema that use my application.
And deploysed all of this stuff together with my application (let's say application.war) in jboss-as-7.1.0.Final .
What should I do to find my process in jbpm console?
>From examples and documenatation :
"To manage your process instances, click on the "Processes" tab at the left an select "Process Overview". After a slight delay (if you are using the application for the first time, due to session initalization etc.), the "Process" list should show all the known processes. The jbpm-console in the demo setup currently loads all the processes in the "src/main/resources" folder of the evaluation sample in "jbpm-installer/sample/evaluation". If you click the process, it will show you all current running instances. Since there are no running instances at this point, the "Instance" table will remain empty."
As I undertood I should set jbpm.console.directory=D:/jbpm in jbpm-installer_5.3.0\conf\jbpm.console.properties (I allways make changes into configs inside jbpm-installer_5.3.0 which is full installer of 5.3.0 and then run ant clean.jboss; ant install.demo.noeclipse to have designer.war , drools-guvnor.war, jbpm-form-builder.war,jbpm-gwt-console.war,jbpm-gwt-console-server.war,jbpm-human-task-war.war updated ).
So I copied my process definition file to D:\jbpm\Looping.bpmn (the same file that I have in classpath of my application) .
I run Jboss with my application and all wars from JBPM but I can see in debug that my process runs in my application (I put breakpoints in methods that launched from script tasks) but I can't see processes in JBPM console.
What should I do to be able to see it?
How does it work ? How JBPM console finds process diagrams and currently running process ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755434#755434]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
