September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1329) Manage common HA capabilities through the console

by Heiko Braun (JIRA)

Manage common HA capabilities through the console ------------------------------------------------- Key: AS7-1329 URL: https://issues.jboss.org/browse/AS7-1329 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1330) Manage web sessions and session replication

by Heiko Braun (JIRA)

Manage web sessions and session replication ------------------------------------------- Key: AS7-1330 URL: https://issues.jboss.org/browse/AS7-1330 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-913) provide management operation for the EJB container

by Heiko Braun (JIRA)

provide management operation for the EJB container -------------------------------------------------- Key: AS7-913 URL: https://issues.jboss.org/browse/AS7-913 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, EJB Reporter: Heiko Braun Assignee: Carlo de Wolf Fix For: 7.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

8
14
0 / 0

[JBoss JIRA] Created: (AS7-753) EJB container management through web interface

by Heiko Braun (JIRA)

EJB container management through web interface ---------------------------------------------- Key: AS7-753 URL: https://issues.jboss.org/browse/AS7-753 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Carlo wrote: The minimum requirements for AS 7.1 are: - invocation statistics - pool/cache statistics After that: - pool/cache configuration Some bits which are nice to have: - security configuration (on the assumption that security policy changes are less desirable without re-deployment) - tx configuration -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

7
9
0 / 0

[JBoss JIRA] Created: (AS7-1731) Fix org.jboss.as.testsuite.integration.wsejb.EJBWebServicesTestCase - got error if running this TestCase alone

by Pavel Janousek (JIRA)

Fix org.jboss.as.testsuite.integration.wsejb.EJBWebServicesTestCase - got error if running this TestCase alone -------------------------------------------------------------------------------------------------------------- Key: AS7-1731 URL: https://issues.jboss.org/browse/AS7-1731 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.0.1.Final Reporter: Pavel Janousek Assignee: Andrew Rubinger Priority: Critical When invole testsuite like: {code} mvn3 -Dtest=org.jboss.as.testsuite.integration.wsejb.* -DfailIfNoTests=false test -PallTests {code} build fails with: {code} Tests in error: testSingleton(org.jboss.as.testsuite.integration.wsejb.EJBWebServicesTestCase): java.io.IOException: <html><head><title>JBoss Web/7.0.1.Final - Error report</title><style></style> </head><body><h1>HTTP Status 404 - /ejbws-example/SingletonEndpoint</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>/ejbws-example/SingletonEndpoint</u></p><p><b>description</b> <u>The requested resource (/ejbws-example/SingletonEndpoint) is not available.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.0.1.Final</h3></body></html> testSingletonWSDL(org.jboss.as.testsuite.integration.wsejb.EJBWebServicesTestCase): java.io.IOException: <html><head><title>JBoss Web/7.0.1.Final - Error report</title><style></style> </head><body><h1>HTTP Status 404 - /ejbws-example/SingletonEndpoint</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>/ejbws-example/SingletonEndpoint</u></p><p><b>description</b> <u>The requested resource (/ejbws-example/SingletonEndpoint) is not available.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.0.1.Final</h3></body></html> {code} If testsuite is invoked like: {code} mvn3 test -PallTests {code} build success. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-752) Initial OSGi management though GWT console

by Thomas Diesler (JIRA)

Initial OSGi management though GWT console ------------------------------------------ Key: AS7-752 URL: https://issues.jboss.org/browse/AS7-752 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Define and implement the initial set of OSGi management functionality An initial set could include * bundle install/start/stop/uninstall * bundle configuration No update, no refresh, no service stats, no licenses, no framework mngmt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
8
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

14 years, 8 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

14 years, 8 months

3
5
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

14 years, 8 months

8
19
0 / 0

[JBoss JIRA] Created: (AS7-1431) JBREM00205 when creating cluster

by Andreas Tauber (JIRA)

JBREM00205 when creating cluster -------------------------------- Key: AS7-1431 URL: https://issues.jboss.org/browse/AS7-1431 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Final Environment: 1 Windows XP + 1 Linux Host with jdk 1.6.0_26 each. I guess that a different enviroment won't change things. Why do you deliver Beta versions for xnio + remoting? Reporter: Andreas Tauber Assignee: Paul Ferraro I try to setup cluster on two hosts using provided manual "Domain Setup". Host Controller on Windows XP can establish connection to Domain Controller on Linux because i see message: Registered remote slave host staging. But I can't see server instances on admin console. So, it seems like the Domain Controller is not able to connect back to native interface on Host Controller. Not really sure here. Shutting down my host controller, I get warnings in boot.log. Here my complete boot.log: 17:05:58,484 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA 17:05:58,796 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA 17:05:59,156 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2 17:05:59,171 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3 17:05:59,187 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3 17:06:00,250 INFO [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /192.168.2.10:9999 17:06:04,468 WARN [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException 17:06:04,484 WARN [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException 17:06:04,484 WARN [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException 17:06:04,484 WARN [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException 17:06:04,484 WARN [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException 17:06:04,484 WARN [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException Note: I renamed the servers to not create name clash (server-four, server-five, server-six) and disabled auto start because I wanted to start instances from admin console on domain controller. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
9
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 September 2011