[JBoss JIRA] Updated: (JBPM-186) manage process definitions
by David Lloyd (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-186?page=all ]
David Lloyd updated JBPM-186:
-----------------------------
Fix Version/s: jBPM 3.3
> manage process definitions
> --------------------------
>
> Key: JBPM-186
> URL: http://jira.jboss.com/jira/browse/JBPM-186
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Web Interface
> Reporter: Tom Baeyens
> Assigned To: David Lloyd
> Fix For: jBPM 3.3
>
> Attachments: SubMenuItems.jpg
>
> Time Spent: 1 day, 2 hours
> Remaining Estimate: 0 minutes
>
> One entry in the jBPM Administration submenu should be 'Manage Process Definitions'.
> Following features should be offered in this page
> * deploy a new process archive (file upload)
> * view all the versions of all process definitions.
> * (re)bind subprocesses to super processes
> * delete process definitions
> * show all process instances for a given process definition
> This will probably by too much for one page. I would prefer a split of the page into submenuitems just like the JEMS projects in the jboss.org site (see attachment)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month
[JBoss JIRA] Created: (JBAS-4202) NPE if additional_data is not set
by Brian Stansberry (JIRA)
NPE if additional_data is not set
---------------------------------
Key: JBAS-4202
URL: http://jira.jboss.com/jira/browse/JBAS-4202
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.0.CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.0.GA
If the cluster setup doesn't support the jgroups additional_data feature, the 2nd and later nodes in the cluster will crash with an NPE.
>From the forum post:
This is the method from the org.jboss.ha.framework.server.HAPartitionImpl which is crashing :
Code:
protected void verifyNodeIsUnique (Vector javaGroupIpAddresses) throws Exception
{
byte[] localUniqueName = this.localJGAddress.getAdditionalData();
if (localUniqueName == null)
log.warn("No additional information has been found in the JavaGroup address: " +
"make sure you are running with a correct version of JGroups and that the protocol " +
" you are using supports the 'additionalData' behaviour");
for (int i = 0; i < javaGroupIpAddresses.size(); i++)
{
IpAddress address = (IpAddress) javaGroupIpAddresses.elementAt(i);
if (!address.equals(this.localJGAddress))
{
if (localUniqueName.equals(address.getAdditionalData()))
throw new Exception ("Local node removed from cluster (" + this.localJGAddress + "): another node (" + address + ") publicizing the same name was already there");
}
}
}
The "if (localUniqueName.equals(address.getAdditionalData()))" is the one causing the NPE.
Method should return after the WARN.
I believe the TUNNEL protocol does not properly support additional_data, but haven't 100% confirmed this. That's a separate issue, but is the likely usage that will expose this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month
[JBoss JIRA] Resolved: (JBAS-4183) Failed to update attributes through JMX console
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4183?page=all ]
Scott M Stark resolved JBAS-4183.
---------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
JBossAS-4.2.0.GA
Resolution: Done
inspectMBean.jsp and the jmx ObjectNameConverter util now escape apos and quot
> Failed to update attributes through JMX console
> -----------------------------------------------
>
> Key: JBAS-4183
> URL: http://jira.jboss.com/jira/browse/JBAS-4183
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX, Management services
> Environment: JBoss 4.0.1sp1, Java 1.5.0_04, Linux
> Reporter: Leon van Zantvoort
> Assigned To: Scott M Stark
> Priority: Minor
> Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA
>
>
> It seems that it is not possible to make updates (set attributes) through the JMX webconsole when the MBean name contains quoted property values:
> tradenet.container:type=deployment,component="ev-selector"
> If the quotes - that wrap ev-selector - are removed, it all works fine. Otherwise, see below:
> 13:13:32,580 ERROR [Engine] StandardWrapperValve[HtmlAdaptor]: Servlet.service() for servlet HtmlAdaptor threw exception
> javax.management.MalformedObjectNameException: Unterminated key property part
> at javax.management.ObjectName.construct(ObjectName.java:465)
> at javax.management.ObjectName.<init>(ObjectName.java:1304)
> at org.jboss.jmx.adaptor.control.Server.setAttributes(Server.java:150)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.updateAttributes(HtmlAdaptorServlet.java:215)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:77)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:150)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month