October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2161) Console tries to access unknown child type 'bundle'

by Brian Stansberry (Created) (JIRA)

Console tries to access unknown child type 'bundle' --------------------------------------------------- Key: AS7-2161 URL: https://issues.jboss.org/browse/AS7-2161 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Brian Stansberry Assignee: Heiko Braun In a managed domain, "Profile" view, clicking on the OSGi + Runtime item in the menu results in this on the HC log: [Host Controller] 07:39:54,759 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 16) Operation ("read-children-resources") failed - address: ([ [Host Controller] ("profile" => "default"), [Host Controller] ("subsystem" => "osgi") [Host Controller] ]) - failure description: "No known child type named bundle" -- 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

12 years, 11 months

5
4
0 / 0

[JBoss JIRA] Created: (AS7-932) Expose runtime OSGi Bundle management through management API

by David Bosschaert (JIRA)

Expose runtime OSGi Bundle management through management API ------------------------------------------------------------ Key: AS7-932 URL: https://issues.jboss.org/browse/AS7-932 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Assignee: David Bosschaert Fix For: 7.1.0.CR1 Bundle runtime management should be exposed through the management API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (AS7-931) Expose osgi configuration through management API

by David Bosschaert (JIRA)

Expose osgi configuration through management API ------------------------------------------------ Key: AS7-931 URL: https://issues.jboss.org/browse/AS7-931 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Assignee: David Bosschaert Fix For: 7.1.0.CR1 The configuration of the OSGi subsystem (urn:jboss:domain:osgi:1.0) should be exposed through the management API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
5
0 / 0

[JBoss JIRA] (AS7-2128) Endpoint address in generated WSDL doesn't reflect IP address of AS7 server, it's always localhost

by Rostislav Svoboda (Created) (JIRA)

Endpoint address in generated WSDL doesn't reflect IP address of AS7 server, it's always localhost -------------------------------------------------------------------------------------------------- Key: AS7-2128 URL: https://issues.jboss.org/browse/AS7-2128 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Alessio Soldano Priority: Critical Endpoint address in generated WSDL doesn't reflect IP address of AS7 server. It's always set to localhost, when I tried to deploy the same archive on EAP 5.1.1 the address was correct (10.34.3.154 in my case). Steps to reproduce: Run latest AS7 build on your public IP address: {code} bin/standalone.sh --server-config=standalone.xml -b=10.34.3.154 -bmanagement=10.34.3.154 {code} Deploy jaxws-benchmark-datatypes-ejb3.jar from WS testsuite Check http://10.34.3.154:8080/jaxws-benchmark-datatypes-ejb3/EndpointEJB3Wrappe... {code} ... <wsdl:service name="EndpointWrappedDocService"> <wsdl:port binding="tns:EndpointWrappedDocServiceSoapBinding" name="EndpointWrappedDocPort"> <soap:address location="http://localhost:8080/jaxws-benchmark-datatypes-ejb3/EndpointWrappedDocSe..."/> </wsdl:port> </wsdl:service> {code} -- 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

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1993) Shutting down an AS7 instance using XTS config results in IndexOutOfBoundsException from EndpointPublishService

by Darran Lofthouse (JIRA)

Shutting down an AS7 instance using XTS config results in IndexOutOfBoundsException from EndpointPublishService --------------------------------------------------------------------------------------------------------------- Key: AS7-1993 URL: https://issues.jboss.org/browse/AS7-1993 Project: Application Server 7 Issue Type: Bug Components: Web Services Environment: This error is reported from code checkout out from git today, Reporter: Darran Lofthouse Assignee: Alessio Soldano 17:56:18,660 WARN [org.jboss.msc.service.fail] MSC00004: Failure during stop of service jboss.ws.endpoint-publish.ws-c11: java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at org.jboss.as.webservices.service.EndpointPublishService.stop(EndpointPublishService.java:100) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.LinkedList.entry(LinkedList.java:365) [:1.6.0_27] at java.util.LinkedList.get(LinkedList.java:315) [:1.6.0_27] at org.jboss.as.webservices.publish.EndpointPublisherImpl.destroy(EndpointPublisherImpl.java:172) at org.jboss.as.webservices.service.EndpointPublishService.stop(EndpointPublishService.java:98) ... 5 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] (AS7-2205) EndpointRecordProcessorDeploymentAspect expects the JMX subsystem to be present

by Stuart Douglas (Created) (JIRA)

EndpointRecordProcessorDeploymentAspect expects the JMX subsystem to be present ------------------------------------------------------------------------------- Key: AS7-2205 URL: https://issues.jboss.org/browse/AS7-2205 Project: Application Server 7 Issue Type: Bug Components: Web Services Reporter: Stuart Douglas Assignee: Alessio Soldano EndpointRecordProcessorDeploymentAspect assumes that the JMX MBean server service has been installed, for now I have changed it to fall back to the platform MBean server, but this should be fixed properly. Note that in theory this can cause problems even if the JMX subsystem is present, if the JMX service is added after the EndpointRecordProcessorDeploymentAspect created. -- 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (AS7-2107) Failed to add EJB3 pool

by Heiko Braun (Created) (JIRA)

Failed to add EJB3 pool ----------------------- Key: AS7-2107 URL: https://issues.jboss.org/browse/AS7-2107 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: David Bosschaert See the attached screenshot -- 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

12 years, 11 months

6
7
0 / 0

[JBoss JIRA] Created: (JBWEB-201) JBoss Web Native causes JVM crash

by Phil Haigh (JIRA)

JBoss Web Native causes JVM crash --------------------------------- Key: JBWEB-201 URL: https://issues.jboss.org/browse/JBWEB-201 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-3.0.0.CR1 Environment: RHEL x64. JBoss AS 6.0.0.Final Reporter: Phil Haigh Assignee: Remy Maucherat Install latest JBoss native (2.0.9) libraries on JBossAS 6.0.0.Final (which uses JBoss Web 3.0.0.CR1), JDK 1.6.0_26 and JVM crashes out soon after application start. Crash dump available (cannot see where I can upload?). Snippet: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00002aaab5b0f468, pid=14823, tid=1191192896 # # JRE version: 6.0_26-b03 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libapr-1.so.0+0x1d468] signed char+0x68 # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --------------- T H R E A D --------------- Current thread (0x00002aaac2d09000): JavaThread "ajp-127.0.0.1-8009-Poller" daemon [_thread_in_native, id=15006, stack(0x0000000046 f02000,0x0000000047003000)] siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000008 Registers: RAX=0x0000000000000000, RBX=0x0000000047001ad0, RCX=0x0000000047001a90, RDX=0x00002aaac453f688 RSP=0x0000000047001a90, RBP=0x00002aaac2d06b38, RSI=0x0000000000000001, RDI=0x0000000000000259 R8 =0x0000000000000001, R9 =0x00002aaac453f688, R10=0x00002aaaab02eadf, R11=0x00002ba6c4d23170 R12=0x00002aaac453f688, R13=0x0000000047001a90, R14=0x0000000000000000, R15=0x00002aaac2d09000 RIP=0x00002aaab5b0f468, EFLAGS=0x0000000000010206, CSGSFS=0x0000000000000033, ERR=0x0000000000000004 TRAPNO=0x000000000000000e Top of Stack: (sp=0x0000000047001a90) 0x0000000047001a90: c453f68800000001 00002ba600002aaa 0x0000000047001aa0: 00002aaac4f365f8 0000000047001ad0 0x0000000047001ab0: 0000000000000000 00000007ea4d0e58 0x0000000047001ac0: 0000000047001bb8 00002aaab564c147 0x0000000047001ad0: 0000000000000000 0000000100000001 0x0000000047001ae0: 0000000000000000 00000000514505e8 0x0000000047001af0: 00002aaac2d09000 00000007ea4d0e58 0x0000000047001b00: 0000000047001b78 00002aaaab02eb0c 0x0000000047001b10: 0000000000000001 00000007e002ee78 0x0000000047001b20: 0000000000000000 0000000047001bb8 0x0000000047001b30: 0000000047001b88 0000000047001b38 0x0000000047001b40: 0000000000000000 0000000047001bb8 0x0000000047001b50: 00000007ea4d1788 0000000000000000 0x0000000047001b60: 00000007ea4d0e58 0000000000000000 0x0000000047001b70: 0000000047001b98 0000000047001c00 0x0000000047001b80: 00002aaaab02296e 00000007ea4d16b8 0x0000000047001b90: 00002aaaab02b8d6 0000000000000001 0x0000000047001ba0: 00000000514505e8 00002aaaab022a82 0x0000000047001bb0: 00002aaac4f365f8 000000077bfff118 0x0000000047001bc0: 0000000047001bc0 00000007ea4beb73 0x0000000047001bd0: 0000000047001c38 00000007ea4c2f18 0x0000000047001be0: 0000000000000000 00000007ea4bebf0 0x0000000047001bf0: 0000000047001b98 0000000047001c20 0x0000000047001c00: 0000000047001c90 00002aaaab02285a 0x0000000047001c10: 0000000000000000 00000000ffffffff 0x0000000047001c20: 0000000000000001 00000000514505e8 0x0000000047001c30: 000000077c01bc68 000000077b6059e8 0x0000000047001c40: 0000000000000009 0000000000000000 0x0000000047001c50: 0000000047001c40 00000007ea4bf518 0x0000000047001c60: 0000000047001ce0 00000007ea4c2f18 0x0000000047001c70: 00000007ea74b790 00000007ea4bfac0 0x0000000047001c80: 0000000047001c20 0000000047001ce0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

8
19
0 / 0

[JBoss JIRA] (JBMESSAGING-1906) Add un-synchronized getMessageCount()

by Justin Bertram (Created) (JIRA)

Add un-synchronized getMessageCount() ------------------------------------- Key: JBMESSAGING-1906 URL: https://issues.jboss.org/browse/JBMESSAGING-1906 Project: JBoss Messaging Issue Type: Enhancement Components: Configuration and Management Affects Versions: 1.4.8.SP3, 1.4.0.SP3.CP14 Reporter: Justin Bertram The method org.jboss.messaging.core.impl.ChannelSupport.getMessageCount() is essentially completely synchronized. This can cause performance problems for management utilities that execute this method via JMX in a polling fashion to gather statistics over time. Please either remove the synchronization from this method or add another that is not synchronized. -- 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

12 years, 11 months

7
8
0 / 0

[JBoss JIRA] (JBRULES-3265) Planner crashes with NoSuchElementException in PlanningValueWalker

by Geoffrey De Smet (Created) (JIRA)

Planner crashes with NoSuchElementException in PlanningValueWalker ------------------------------------------------------------------ Key: JBRULES-3265 URL: https://issues.jboss.org/browse/JBRULES-3265 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor " After debugging, seems like cachedPlanningValues in PlanningValueCreator is being created as an empty collection and when PlanningValueWalker gets cachedPlanningValues's iterator and tries to iterate through it then it gets a NoSuchElementException. I am a little confused as to when the extractPlanningValues method is called in PlanningValueSelector to get a collection of planned values a null is begin passed in instead of a planning entity which is responsible for the empty cachedPlanningValues collection. " {code} java.util.NoSuchElementException at java.util.AbstractList$SimpleListIterator.next(AbstractList.java:61) at org.drools.planner.core.heuristic.selector.variable.PlanningValueWalker.initWalk(PlanningValueWalker.java:90) at org.drools.planner.core.heuristic.selector.variable.PlanningVariableWalker.initWalk(PlanningVariableWalker.java:104) at org.drools.planner.core.constructionheuristic.greedyFit.decider.DefaultGreedyDecider.decideNextStep(DefaultGreedyDecider.java:58) at org.drools.planner.core.constructionheuristic.greedyFit.DefaultGreedyFitSolverPhase.solve(DefaultGreedyFitSolverPhase.java:62) at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:166) at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:138) {code} -- 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

12 years, 11 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011