February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3826) EJB client: NPE is returned to the client in case of server crash

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3826: ----------------------------------- Summary: EJB client: NPE is returned to the client in case of server crash Key: AS7-3826 URL: https://issues.jboss.org/browse/AS7-3826 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: jaikiran pai Priority: Critical Fix For: 7.1.1.Final In case of remote server crashing, the client gets NPE. # NPE is not telling at all, I m sure that the client knows what went wrong and can throw a more meaningful exception. # AFAIR in EAP5 the client could do a retry and not fail. I guess this is still part of discussion whether this will be supported. {noformat} 2012/02/20 10:26:22:422 EST [ERROR][Runner - 54] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.NullPointerException> java.lang.NullPointerException at org.jboss.ejb.client.remoting.ChannelAssociation$UnusableChannelResultProducer.getResult(ChannelAssociation.java:412) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:212) at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:47) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:214) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:96) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:203) at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:341) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy0.getSerialAndIncrement(Unknown Source) at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68) at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51) at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87) at java.lang.Thread.run(Thread.java:662) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3687) Update Zanata config and push initial german translations

by Heiko Braun (JIRA)

Heiko Braun created AS7-3687: -------------------------------- Summary: Update Zanata config and push initial german translations Key: AS7-3687 URL: https://issues.jboss.org/browse/AS7-3687 Project: Application Server 7 Issue Type: Task Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.1.Final Sean: Thanks for putting the github url in the project page, makes things a lot easier! I noticed that that project has some de properties files already. If you want to import the existing German translations, you need to make sure "de" appears in the <locales> list of zanata.xml, then run: $ mvn zanata:push -Dzanata.pushTrans (You'll actually want to have all the target locales in <locales>, so that "mvn zanata:pull" will fetch them when translated.) This will push the base (English) and translated .properties files together. I don't recommend pushing the translated .properties files repeatedly (it's easier to co-ordinate if all translation happens in Zanata), but pushTrans is the option if you want to do an initial import of what you've got. I also recommend committing zanata.xml and the modified pom.xml to git to save on confusion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3391) Rule group activation by concurrent jbpm processes ...

by Alberto Rodriguez (JIRA)

Alberto Rodriguez created JBRULES-3391: ------------------------------------------ Summary: Rule group activation by concurrent jbpm processes ... Key: JBRULES-3391 URL: https://issues.jboss.org/browse/JBRULES-3391 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert), drools-core (flow) Affects Versions: 5.4.0.Beta2 Environment: Operating system independent. Reporter: Alberto Rodriguez Assignee: Mark Proctor We've been able to see that the following statement in the documentation doesn't seem to be true: "We have added special logic to make sure that a variable processInstance of type WorkflowProcessInstance will only match to the current process instance and not to other process instances in the Working Memory." We've seen rules fire for rule-group activations from different workflowprocesses. Imagine a knowledge session with this set of rules: rule "new case" when $object : Object(processed==false) from entry-point "my stream" then ProcessInstance processInstance=kcontext.getKnowledgeRuntime().createProcessInstance("my.Process", parameters); insert(processInstance); end rule "complete" ruleflow-group "process complete" no-loop true when $processInstance: WorkflowProcessInstance() then System.out.println("Fired!" + $processInstance); end And a process that runs a time consuming task before reaching a bussinessruletask node that calls the "process complete" group of rules. What is happening from Drool's expert point of view is the following sequence of events: 1 - A fact is inserted that triggers the rule "new case". An Activation is inserted into the agenda. 2 - As this is running in a fireUntilHalt loop then, almost inmediatelly, the previous activation is fired and it's consquence is evaluated leading to the insertion of the process instance as a fact in the knowledge session. The process is now executing. 3 - This very new fact triggers the activation of the rule "complete" ( as it's only condition is that a processinstance exists ). It's consequence gets evaluated and as it belongs to a group of rules, an Activation is added to the ruleFlowGroup inside the Agenda. Nothing happens thereafter. 4 - Another fact of the same type arrives and steps 1,2 and 3 execute for the new fact. Now, the agenda has two Activations stored in the ruleFlowGroup. 5 - At this time, the task in the first process ends, the businessruletask gets executed and JBPM calls "activateRuleFlowGroup" on the Agenda and the rule flow group gets activated. 6 - Inmediatelly the group of rules fires two activations ( both queued at process fact insertion when the process was started ), when only one process ended. 7 - So at least one rule gets evaluated for a process instance that didn't belong to it .. :( Then , "We have added special logic to make sure that a variable processInstance of type WorkflowProcessInstance will only match to the current process instance and not to other process instances in the Working Memory." doesn't hold to be true, as our rule is fired *before* it's process asks Drools to do so. We've tested this behaviour in Drools 5.1.0, 5.2.0 and 5.3.0. All seem to fail in fulfilling the requirements stated the documentation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3803) Setting a blank locale on the settings dialog gives a blank screen

by James Perkins (JIRA)

James Perkins created AS7-3803: ---------------------------------- Summary: Setting a blank locale on the settings dialog gives a blank screen Key: AS7-3803 URL: https://issues.jboss.org/browse/AS7-3803 Project: Application Server 7 Issue Type: Bug Components: Console Environment: Fedora 16, Sun JRE 6u30, FireFox and Google Chrome Reporter: James Perkins Assignee: Heiko Braun Fix For: 7.1.1.Final When the settings dialog is pop-up and you select the blank locale that is presented and the the page is refreshed nothing get's rendered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] (AS7-3165) Admin console: inappropriate way of selecting a Cache Type for a Security Domain

by Jan Martiska (Created) (JIRA)

Admin console: inappropriate way of selecting a Cache Type for a Security Domain -------------------------------------------------------------------------------- Key: AS7-3165 URL: https://issues.jboss.org/browse/AS7-3165 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Attachments: cachetype.png See screenshot. The field for selecting Cache Type should rather be a listbox instead of plain input text, as it is said to accept only two possible values ('default' and 'infinispan'). It is currently possible to enter a value different from 'default' or 'infinispan', and the operation will succeed!!! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

7
8
0 / 0

[JBoss JIRA] (AS7-3164) Admin console: Conditional port assignment in socket binding group incorrectly shown as number -1

by Jan Martiska (Created) (JIRA)

Admin console: Conditional port assignment in socket binding group incorrectly shown as number -1 ------------------------------------------------------------------------------------------------- Key: AS7-3164 URL: https://issues.jboss.org/browse/AS7-3164 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Attachments: socketbinding.png Screenshot says it all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
7
0 / 0

[JBoss JIRA] (AS7-3168) Admin console: issues with creation of system properties

by Jan Martiska (Created) (JIRA)

Admin console: issues with creation of system properties -------------------------------------------------------- Key: AS7-3168 URL: https://issues.jboss.org/browse/AS7-3168 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Admin console doesn't currently verify the property's name when creating a system property. The creation will fail when it is sent to server, it should fail in the console itself, because console can verify if property's name is invalid. Server side failure should only occur when a property with the same name already exists. Furthermore, it seems that in some scenarios, when you use an invalid name of a system property, for example containing some national characters, such as ěščžěščřěščř, the system property WILL get created (and will exist on the server), but the admin console will be UNABLE to show any of the existing system properties - when you navigate to system property page, it will show an empty table!!!! This will require deleting this property using CLI before system property management can be used in admin console again. NOTE: other than system properties, this applies to OSGi framework properties and most likely more property types as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

7
10
0 / 0

[JBoss JIRA] (AS7-3169) Admin console: missing validation on JVM arguments

by Jan Martiska (Created) (JIRA)

Admin console: missing validation on JVM arguments -------------------------------------------------- Key: AS7-3169 URL: https://issues.jboss.org/browse/AS7-3169 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Priority: Critical Attachments: jvmargs.png It is currently possible to set invalid JVM arguments for a server instance or group, as seen in the attached screenshot. The input field designating heap size and maximum heap size should be somehow reworked, made more intuitive, at least the help should show more information on what you can put in. If you enter an invalid value, the operation will succeed, the invalid value will be used after the domain is restarted, and causing related servers to NOT BOOT UP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
7
0 / 0

[JBoss JIRA] (AS7-3179) Admin console: missing "Edit" button for EJB3 thread pools

by Jan Martiska (Created) (JIRA)

Admin console: missing "Edit" button for EJB3 thread pools ---------------------------------------------------------- Key: AS7-3179 URL: https://issues.jboss.org/browse/AS7-3179 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung in standalone mode, navigate to Profile/Profile/Container/EJB 3/Thread pools. it used to be possible to edit an existing thread pool using a button, however in the latest snapshot, as of 4th January, I can't find it anymore. Nor can the selenium testsuite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
5
0 / 0

[JBoss JIRA] (AS7-3364) Admin console allows assigning multiple connectors to the same socket binding

by Jan Martiska (JIRA)

Jan Martiska created AS7-3364: --------------------------------- Summary: Admin console allows assigning multiple connectors to the same socket binding Key: AS7-3364 URL: https://issues.jboss.org/browse/AS7-3364 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor When creating a connector, the form checks that the value "Socket Binding" does not reference a socket binding that is already taken by another connector. If it is taken, validation of the form fails. However, when you successfully create a server and then CHANGE the Socket Binding using the 'Edit' button, this validation is not applied. Therefore it is possible to assign two different connectors to the same socket binding, e.g. to the same port. This will cause a "java.lang.Exception: Socket bind failed: [98] Address already in use" when the server is restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012