September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5022) Server sometimes crashes during reload operation

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/AS7-5022?page=com.atlassian.jira.plugin.s... ] Jan Martiska closed AS7-5022. ----------------------------- > Server sometimes crashes during reload operation > ------------------------------------------------ > > Key: AS7-5022 > URL: https://issues.jboss.org/browse/AS7-5022 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jan Martiska > Assignee: Thomas Diesler > Priority: Critical > > After some number of server reloads, next reload fails.. the number seems random, for me it is between 6 and 150. > this error message pops up during boot: > {noformat} > 15:21:05,036 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 53) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "osgi")]): org.jboss.msc.service.DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered > {noformat} > This shell script can be used for reproduction: > {noformat} > #!/bin/sh > $JBOSS_HOME/bin/standalone.sh > /dev/null & > sleep 10 > for i in `seq 1 150`; do > echo $i > $JBOSS_HOME/bin/jboss-cli.sh -c --command=:reload > sleep 4 > tail --lines=50 $JBOSS_HOME/standalone/log/server.log | grep ERROR > done > {noformat} > Testing environment> RHEL 5 or 6. This happens both when reloading using jboss-cli.sh and jboss-as-controller-client. It seems it has never happened to me when EAP was running in IPv6 mode (java.net.preferIPv4Stack=false), only IPv4. Affects all standalone profiles. It randomly breaks my admin console testsuite, which uses server reloads quite a lot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4167) Admin console: cannot set attribute max-attempts of modcluster subsystem

by Jan Martiska (JIRA)

Jan Martiska created AS7-4167: --------------------------------- Summary: Admin console: cannot set attribute max-attempts of modcluster subsystem Key: AS7-4167 URL: https://issues.jboss.org/browse/AS7-4167 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor Under Networking tab of modcluster configuration - property "Max Attempts" cannot be set- console references it as "max-attemps" instead of the correct "max-attempts" {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "JBAS014792: Unknown attribute max-attemps", "rolled-back" => true }}, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute max-attemps"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {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

11 years, 9 months

1
5
0 / 0

[JBoss JIRA] (AS7-4166) Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem

by Jan Martiska (JIRA)

Jan Martiska created AS7-4166: --------------------------------- Summary: Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem Key: AS7-4166 URL: https://issues.jboss.org/browse/AS7-4166 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor Under Web Contexts tab of modcluster configuration - property "Auto Enable Contexts" cannot be set- console references it as "auto-enableContexts" instead of the correct "auto-enable-contexts" {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "JBAS014792: Unknown attribute auto-enableContexts", "rolled-back" => true }}, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute auto-enableContexts"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} {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

11 years, 9 months

1
5
0 / 0

[JBoss JIRA] (JBAS-9512) changed to new version jboss 6.1 from jboss 4.2.2 it is giving exception after deploying my project

by Raghu T (JIRA)

Raghu T created JBAS-9512: ----------------------------- Summary: changed to new version jboss 6.1 from jboss 4.2.2 it is giving exception after deploying my project Key: JBAS-9512 URL: https://issues.jboss.org/browse/JBAS-9512 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.1.0 Environment: Windows 7 os,64 bit and Java struts platform Reporter: Raghu T Assignee: Ales Justin Fix For: JBossAS-4.2.2.GA i am getting the following exception .... Deployment "vfs:///D:/server/jboss-6.1.0.Final/server/default/deploy/MozartCCNewUI.war" is in error due to the following reason(s): org.xml.sax.SAXException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". @ vfs:///D:/server/jboss-6.1.0.Final/server/default/deploy/MozartCCNewUI.war/WEB-INF/web.xml[152,11] this is my web.xml file..... <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app>  <distributable /> <filter> <filter-name>LoginFilter</filter-name> <filter-class> com.zyom.security.LoginMonitorFilter </filter-class> </filter> <filter-mapping> <filter-name>LoginFilter</filter-name> <url-pattern>*.do</url-pattern> </filter-mapping> <filter-mapping> <filter-name>LoginFilter</filter-name> <url-pattern>*.jsp</url-pattern> </filter-mapping>   <servlet> <servlet-name>action</servlet-name> <servlet-class> org.apache.struts.action.ActionServlet </servlet-class> <init-param> <param-name>config</param-name> <param-value>/WEB-INF/struts-config.xml</param-value> </init-param> <init-param> <param-name>debug</param-name> <param-value>2</param-value> </init-param> <init-param> <param-name>detail</param-name> <param-value>2</param-value> </init-param> <load-on-startup>2</load-on-startup> </servlet> <servlet-mapping> <servlet-name>action</servlet-name> <url-pattern>*.do</url-pattern> </servlet-mapping> <servlet> <servlet-name>CewolfServlet</servlet-name> <servlet-class>de.laures.cewolf.CewolfRenderer</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>CewolfServlet</servlet-name> <url-pattern>/cewolf/*</url-pattern> </servlet-mapping> <session-config> <session-timeout>30</session-timeout> </session-config> <listener> <listener-class>com.zyom.reuse.util.SessionListener</listener-class> </listener>   <welcome-file-list> <welcome-file>/pages/MozartCostLoginAdmin.jsp</welcome-file> </welcome-file-list>  <taglib> <taglib-uri>/tags/struts-bean</taglib-uri> <taglib-location>/WEB-INF/struts-bean.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-html</taglib-uri> <taglib-location>/WEB-INF/struts-html.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-logic</taglib-uri> <taglib-location>/WEB-INF/struts-logic.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-nested</taglib-uri> <taglib-location>/WEB-INF/struts-nested.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-tiles</taglib-uri> <taglib-location>/WEB-INF/struts-tiles.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/pagetaglib</taglib-uri> <taglib-location>/WEB-INF/pagetaglib.tld</taglib-location> </taglib>  </web-app> -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5513) JNDI Lookup is not working in thread run method

by sandip jorwekar (JIRA)

sandip jorwekar created AS7-5513: ------------------------------------ Summary: JNDI Lookup is not working in thread run method Key: AS7-5513 URL: https://issues.jboss.org/browse/AS7-5513 Project: Application Server 7 Issue Type: Bug Components: Application Client Affects Versions: 7.1.1.Final Environment: Windows XP and JDK1.6 Reporter: sandip jorwekar Assignee: Stuart Douglas Priority: Critical Fix For: Open To Community When i do the JNDI lookup in thread's run method then i am getting below error java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:auroraclientcommon,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@64883c at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy0.create(Unknown Source) at BookClient1.test(BookClient1.java:117) at BookClient1.run(BookClient1.java:104) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
5
0 / 0

[JBoss JIRA] (AS7-5505) Cannot overlay in a single composite operation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5505: ----------------------------------- Summary: Cannot overlay in a single composite operation Key: AS7-5505 URL: https://issues.jboss.org/browse/AS7-5505 Project: Application Server 7 Issue Type: Bug Components: Server Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.2.0.Alpha1 In order to support AS7-3694 I need to associate a META-INF/jboss-all.xml descriptor with bundle deployments. This I currently do in six discrete steps {code} { "address" => ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"), "operation" => "add" } { "address" => undefined, "operation" => "upload-deployment-stream", "input-stream-index" => 0 } { "address" => [ ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"), ("content" => "META-INF/jboss-all.xml") ], "operation" => "add", "content" => {"hash" => bytes { 0xdb, 0x79, 0x11, 0xff, 0xdf, 0x8f, 0xfc, 0x65, 0xc2, 0xe3, 0x6b, 0x20, 0xa5, 0x89, 0xa7, 0xdb, 0x10, 0xed, 0xcc, 0xc0 }} } { "address" => [ ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"), ("deployment" => "bundle-b.jar") ], "operation" => "add" } { "operation" => "add", "address" => [("deployment" => "bundle-b.jar")], "runtime-name" => "bundle-b.jar", "content" => [{"input-stream-index" => 0}] } { "operation" => "deploy", "address" => [("deployment" => "bundle-b.jar")] } {code} As far as I know these cannot be combined in a composite operation because step #3 uses the result of #2. The management API should allow this to happen in a single composite operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (AS7-1263) Publish deployment descriptor schemas and dtd in the dist

by Brian Stansberry (JIRA)

Publish deployment descriptor schemas and dtd in the dist --------------------------------------------------------- Key: AS7-1263 URL: https://issues.jboss.org/browse/AS7-1263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final AS 7.0 has the domain/host/standalone config schemas in docs/schema, but not the deployment descriptor schemas and DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

7
14
0 / 0

[JBoss JIRA] (AS7-5510) EJB deploys with dual definition

by Dan Wilkin (JIRA)

Dan Wilkin created AS7-5510: ------------------------------- Summary: EJB deploys with dual definition Key: AS7-5510 URL: https://issues.jboss.org/browse/AS7-5510 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.0.Final Environment: Windows 7 Reporter: Dan Wilkin Assignee: jaikiran pai When two uniquely defined Session Beans reference the same interface in the {{@Remote}} annotation, the following exception occurs: {noformat} Caused by: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit) at org.jboss.invocation.InvocationMessages_$bundle.cannotProceed(InvocationMessages_$bundle.java:131) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:293) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:202) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final] ... 100 more {noformat} This can occur from a copy-paste error: {code:title=RedSLSB.java} @Stateless @Remote(Red.class) public class RedSLSB implements Red { ... } {code} {code:title=BlueSLSB.java} @Stateless @Remote(Red.class) public class BlueSLSB implements Blue { ... } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
6
0 / 0

[JBoss JIRA] (AS7-4057) Create logging profiles for deployments

by James Perkins (JIRA)

James Perkins created AS7-4057: ---------------------------------- Summary: Create logging profiles for deployments Key: AS7-4057 URL: https://issues.jboss.org/browse/AS7-4057 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 Create logging profiles to be assignable to deployments. The precedence would be deployment configuration -> profile configuration -> default configuration. This would allow profiles to be configured with the management interface. Each profile would have it's own LogContext and the context could be secured. -- 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

11 years, 9 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3619) Knowledge Agent: add the possibility to apply ByteArrayResources

by Esteban Aliverti (JIRA)

Esteban Aliverti created JBRULES-3619: ----------------------------------------- Summary: Knowledge Agent: add the possibility to apply ByteArrayResources Key: JBRULES-3619 URL: https://issues.jboss.org/browse/JBRULES-3619 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Reporter: Esteban Aliverti Assignee: Mark Proctor Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012