JBoss 4.2.3 and Platform JMX
by fernando＠lozano.eti.br
Hi there,
I have an application that prevents JBoss AS 4.2.3. with Sun JDK1.5.0_22 from starting with JMX
remote enabled, so I cannot use jconsole to inspect the Platform and JBoss MBeans. If I remove the
application, JBoss starts fine with JMX Remote. If I remove JMX Remote flags from run.conf
JAVA_OPTS, JBoss starts fine with the application.
When I try to start JBoss AS with both the application and JMX Remote enabled, each and every WAR
package triggers and error like:
2010-07-30 09:06:13,466 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment:
file:/home/lozano/jboss-4.2.3.GA/server/wcm10/deploy/exoplatform.sar/01eXoResources.war
javax.management.InstanceNotFoundException: jboss.system:service=ServiceController
I have not checked if those erros happen only for WAR packages or if they also happen for another
kinds of packages. My server.log becomes so full with erros that it's pointless to send them to the
list. This was only thr first one.
I have used a brand-new install from JBoss and from the app. The app is eXo WCM 1.0 availabe from
objectweb.org.
I am used to add JMX Remote following instructions from
http://community.jboss.org/wiki/JBossMBeansInJConsole and using a number of JMX clients besides
jconsole, for instance Zabbix Zapcat, and this was the first time I had problems. I have no idea
about what to look for in the application or JBoss configs that could cause this.
[]s, Fernando Lozano
14 years, 4 months
[jBPM Development] - JBPM-BPEL
by Praveen Kumar Kota
Praveen Kumar Kota [http://community.jboss.org/people/pravi.kin] created the discussion
"JBPM-BPEL"
To view the discussion, visit: http://community.jboss.org/message/555276#555276
--------------------------------------------------------------
Hi,
I am trying out a sample example in BPEL Designer in eclipse. I notice the below error:
Problems occurred when invoking code from plug-in: "org.eclipse.ui.views.properties.tabbed".
java.lang.LinkageError: javax/wsdl/Input
at org.eclipse.bpel.ui.util.ModelHelper.getVariableType(ModelHelper.java:1376)
at org.eclipse.bpel.ui.properties.InvokeVariableSection.updateInputVariableWidgets(InvokeVariableSection.java:1101)
at org.eclipse.bpel.ui.properties.InvokeVariableSection.refresh(InvokeVariableSection.java:1050)
at org.eclipse.ui.views.properties.tabbed.TabContents$6.run(TabContents.java:217)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.ui.views.properties.tabbed.TabContents.refresh(TabContents.java:220)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.handlePartActivated(TabbedPropertySheetPage.java:341)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage$1.partActivated(TabbedPropertySheetPage.java:118)
at org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:72)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:57)
at org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:70)
at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:187)
at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:306)
at org.eclipse.ui.internal.WWinPartService.updateActivePart(WWinPartService.java:131)
at org.eclipse.ui.internal.WWinPartService.access$0(WWinPartService.java:122)
at org.eclipse.ui.internal.WWinPartService$WWinListener.partDeactivated(WWinPartService.java:50)
at org.eclipse.ui.internal.PartListenerList2$4.run(PartListenerList2.java:115)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:55)
at org.eclipse.ui.internal.PartListenerList2.firePartDeactivated(PartListenerList2.java:113)
at org.eclipse.ui.internal.PartService.firePartDeactivated(PartService.java:242)
at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:300)
at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:57)
at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136)
at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3531)
at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:3071)
at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:279)
at org.eclipse.ui.internal.EditorPane.requestActivation(EditorPane.java:98)
at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:237)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1008)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1404)
at org.eclipse.swt.widgets.Shell.WM_MOUSEACTIVATE(Shell.java:2269)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3989)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1578)
at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2010)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2406)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:80)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4036)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:2976)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3498)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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 org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
eclipse.buildId=
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.java.product
Could anyone please look into the above error and help me in getting it resolved.
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/555276#555276]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
[jBPM] - [Q] JBPM 4.3 to 4.4 Upgrade Issue
by Ken Hoying
Ken Hoying [http://community.jboss.org/people/khoying] created the discussion
"[Q] JBPM 4.3 to 4.4 Upgrade Issue"
To view the discussion, visit: http://community.jboss.org/message/555248#555248
--------------------------------------------------------------
I have recently upgraded my JBPM implementation from 4.3 to 4.4. However, this has caused a significant problem for me.
As part of my process definition I have the following decision defined:
<decision g="901,209,48,48" name="decision.supplierInitApprover">
<handler expr="#{jbpmDecideHasSupplierApprover}"/>
<transition g="-50,-18" name="result.approver" to="state.supplierInitApproval"/>
<transition g="30,-80" name="result.noApprover" to="state.memberReview">
</decision>
I am expecting the handler expression to be resolved using the Juel script engine as it is my default (and only) script language that I have configured. However since upgrading to 4.4 it appears that this is no longer being resolved by Juel.
Reviewing the source code, I notice there has been a change in the ObjectDescriptor.construct() method that is causing my issue.
In 4.3, it resolved the expression by the following:
Line 180:
} else if (expr!=null) {
ScriptManager scriptManager = ScriptManager.getScriptManager();
object = scriptManager.evaluateExpression(expr, lang);
}
In 4.4 it resolves the expression by the following:
Line 176:
} else if (expression!=null) {
object = expression.evaluateInScope(wireContext.getScopeInstance());
}
Does anyone know how I can fix my problem and have JBPM 4.4 use the ScriptManager and Juel once again?
Thanks in Advance!
Ken
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/555248#555248]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
Re: [jboss-user] [jBPM] - in jbpm 4.3, timer not firing to leave its state node.
by Tun Mang
Tun Mang [http://community.jboss.org/people/tunmang] replied to the discussion
"in jbpm 4.3, timer not firing to leave its state node."
To view the discussion, visit: http://community.jboss.org/message/555227#555227
--------------------------------------------------------------
Hi :
Is there a way to keep jbpm ProcessEngine alive in jboss by either configure jboss or jbpm ?
What was found out is that the stand-alone application exited after initialized jbpm ProcessEngine and started the timer-test process instance. So the jbpm's "scheduler" or job execution is not waking up to run.
Suppose the stand-alone application must exit after start the process instance (because it is not a daemon), and there is only "jpbm.jar" (not jpbm.war) residing in the following location :
...\jboss\5.1.0.GA\common\lib\jpbm.jar
Practically, if only jboss server will keep running, how to configure jboss or jbpm so that the "scheduler service" can keep the jbpm's "scheduler" or job execution wake up to fire the timeout event ? Sorry for if I use the wrong terms to describe jbpm's techonolgy.
Thanks a lot for you help and time in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/555227#555227]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
Re: [jboss-user] [JBoss Microcontainer] - AbstractRealDeployerWithInput fails to call undeploy() on DeploymentVisitor, for failed deployments
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion
"AbstractRealDeployerWithInput fails to call undeploy() on DeploymentVisitor, for failed deployments"
To view the discussion, visit: http://community.jboss.org/message/555224#555224
--------------------------------------------------------------
> Ales Justin wrote:
>
> > That would effectively mean, that *every* implementation of the org.jboss.deployers.spi.deployer.helpers.DeploymentVisitor interface, has to have the following code in their deploy:
> >
> No, why?
>
Because, in it's current form, if some *unexpected* exception occurs then the undeploy will never get called with that try{}catch(Throwable t) block.
> Ales Justin wrote:
>
>
> See existing impl, none has that.
And all those will fail (i.e. their undeploy() will not get called) if they happen to run into runtime exceptions in their deploy.
> Ales Justin wrote:
>
> Either they don't have anything, since the deploy action is very simple
Doesn't matter if it's simple or not :) Even if it's a couple of lines code, it can end up throwing a runtime.
> Ales Justin wrote:
>
> (almost atomic :) ),
That's just an assumption :)
> Ales Justin wrote:
>
> The idea is that the visitor's deploy is very simple, or you missused the deployer.
Consider this again, in my visitor's deploy:
void deploy(DeploymentUnit unit, T deployment) throws DeploymentException
{
Ejb3Registry.register(...);
callThirdPartyCodeWhichRunsIntoNullPointerException();
}
I don't see any misuse here. So when I call the callThirdPartyCodeWhichRunsIntoNullPointerException(), which as the name suggests will run into a NPE (for some reason), I have no way of unregistering from Ejb3Registry, unless I wrap all this in a try{}catch(Throwable t) block or at the very least in a try{}catch(RuntimeException re) block.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/555224#555224]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months