twiddle queries
by vicky
Hello Everyone.
I am new to JBOSS & in my company JBOSS 4.2.0 is in use currently(old fashined).
Question 1:
I am trying to run twiddle commands to fetch the Server details but while executing it is throwing the below exception:Please suggest how to fix this
++++++++++++++++++++++++++++++++
Exception in thread main java.lang.NoClassDefFoundError:/org/jboss/console/twiddle/Twiddle
Caused by java.lang.ClassNotFoundException: org.jboss.console.twiddle.Twiddle
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
++++++++++++++++++++++++++++++++
Question 2: Does Twiddle command can connect on JBOSS JNP port only or we can use other ports as well
Question 3: How to connect to differen JBOSS server instances running on same JNP port & on same machine using TWIDDLE command
Please help in understand the the above mentioned my naive queries
Thanks a lot for your help in advance
Vicky
11 years, 6 months
[jBPM] - Error on server
by loaone seleka
loaone seleka [https://community.jboss.org/people/loaone] created the discussion
"Error on server"
To view the discussion, visit: https://community.jboss.org/message/758523#758523
--------------------------------------------------------------
Hello
I cannot start my human task because it doesnt recognise
my port and ip address. Please help
0 07/09 12:15:56,390[main] ERROR service.hornetq.HornetQTaskClientConnector.connect - Unable to connect to server using configuration org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=127-0-0-1
Exception in thread "main" org.jbpm.workflow.instance.WorkflowRuntimeException: [com.human.bpmn:1 - Human1:3] -- Could not connect task client: on ip: 127.0.0.1 - port: 5445
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:130)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:205)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:164)
at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49)
at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:124)
at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35)
at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:188)
at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:303)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:168)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:138)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:130)
at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1077)
at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:315)
at human.TestProcess.main(TestProcess.java:25)
Caused by: java.lang.IllegalArgumentException: Could not connect task client: on ip: 127.0.0.1 - port: 5445
at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.connect(GenericHTWorkItemHandler.java:119)
at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.executeWorkItem(GenericHTWorkItemHandler.java:143)
at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70)
at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:105)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:124)
... 14 more
Sep 7, 2012 12:16:05 PM org.hornetq.core.logging.impl.JULLogDelegate warn
WARNING: I'm closing a core ServerLocator you left open. Please make sure you close all ServerLocators explicitly before letting them go out of scope! 3658896
Sep 7, 2012 12:16:05 PM org.hornetq.core.logging.impl.JULLogDelegate warn
WARNING: The ServerLocator you didn't close was created here:
java.lang.Exception
at org.hornetq.core.client.impl.ServerLocatorImpl.<init>(ServerLocatorImpl.java:387)
at org.hornetq.core.client.impl.ServerLocatorImpl.<init>(ServerLocatorImpl.java:484)
at org.hornetq.api.core.client.HornetQClient.createServerLocatorWithoutHA(HornetQClient.java:112)
at org.jbpm.task.service.hornetq.HornetQTaskClientConnector.connect(HornetQTaskClientConnector.java:93)
at org.jbpm.task.service.hornetq.HornetQTaskClientConnector.connect(HornetQTaskClientConnector.java:74)
at org.jbpm.task.service.TaskClient.connect(TaskClient.java:790)
at org.jbpm.task.service.SyncTaskServiceWrapper.connect(SyncTaskServiceWrapper.java:193)
at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.connect(GenericHTWorkItemHandler.java:117)
at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.executeWorkItem(GenericHTWorkItemHandler.java:143)
at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70)
at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:105)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:124)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:205)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:164)
at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49)
at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:124)
at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35)
at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:188)
at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:303)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:168)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:138)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:130)
at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1077)
at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:315)
at human.TestProcess.main(TestProcess.java:25)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/758523#758523]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss Tools] - It's Beta Time for JBoss Tools and Developer Studio
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] modified the blog post:
"It's Beta Time for JBoss Tools and Developer Studio"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time...
--------------------------------------------------------------
It's Beta time for JBoss Tools 4 and JBoss Developer Studio 6!
https://community.jboss.org/servlet/JiveServlet/showImage/38-4854-18193/j... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4854-181...
h4. Beta 1
Developer Studio: [ https://marketplace.eclipse.org/node/503834 Marketplace] [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ https://marketplace.eclipse.org/node/420896 Marketplace] [ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/development/juno/ Update Site] | [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution.
JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation.
If you are into doing your own bleeding edge eclipse plugin assembly, JBoss Tools is for you; if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.
h2. Installation
+JBoss Developer Studio+ comes with everything pre-bundled in its installer. Simply http://devstudio.jboss.com/earlyaccess download it from our early access site and run it like this:
java -jar jbdevstudio-<installername>.jar
*Note:* if you are on Windows or Mac OSX 64-bit we recommend you ensure to select the 32-bit option in the multi-platform installer to get Visual Page editor working and use much less memory.
+JBoss Tools+ requires a bit more:
http://marketplace.eclipse.org/marketplace-client-intro?mpc_install=420896 https://devstudio.jboss.com/images/jbosstools-marketplace-download-now.png
This release requires at least Eclipse 4.2 but we recommend using the http://www.eclipse.org/downloads/packages/release/juno/sr1 Eclipse 4.2 JEE Bundle since then you get most of the dependencies preinstalled.
Once you have installed Eclipse, you either find us on https://marketplace.eclipse.org/node/420896 Eclipse Marketplace under "JBoss Tools (Juno)" or use our update site directly.
The update site URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/juno/ http://download.jboss.org/jbosstools/updates/development/juno/
Note: SOA tooling for BPEL, Drools, Guvnor, jBPM, ESB, Modeshape, pi4soa, Savara, SwitchYard & Teiid are no longer included in the JBoss Tools release. They will become available separately later.
h2. Bring Your Own Eclipse
This beta introduces JBoss Developer Studio BYOE (Bring Your Own Eclipse) which allow you to install the plugins provided and supported in JBoss Developer Studio to your own existing Eclipse installation from https://marketplace.eclipse.org/node/503834 Eclipse Marketplace.
If unavailable soon from "Help > Eclipse Marketplace...", simply click the link above to browse the Marketplace entry, then drag the link there into your Eclipse.
We are eager to hear how this BYOE option work for you and do please let us know ASAP if you spot issues with this new and more flexible way of installing Developer Studio! Thank you!
h2. Multiple OpenShift Servers
OpenShift now allows you to connect to multiple OpenShift servers, i.e. your own Origin server as well as hosted openshift.
h2. And more...
See the full list of changes in Alpha1, Alpha2 and now Beta1 at the http://docs.jboss.org/tools/whatsnew/ What's New and Noteworthy and of course a good bunch of bug fixes and adjustments for running well in Eclipse 4.2/Juno.
Have fun!
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time...]
11 years, 6 months
