June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-49) Add option to disable translation generation

by James Perkins (JIRA)

James Perkins created LOGTOOL-49: ------------------------------------ Summary: Add option to disable translation generation Key: LOGTOOL-49 URL: https://issues.jboss.org/browse/LOGTOOL-49 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.1.0.Beta1 Add a supported option for disabling the processing of the translations files. -- 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

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1631) JAX-RS client support for OSGi bundles

by Thomas Diesler (JIRA)

JAX-RS client support for OSGi bundles -------------------------------------- Key: AS7-1631 URL: https://issues.jboss.org/browse/AS7-1631 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Provide OSGi bundles the ability to use the RESTeasy client APIs -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[JBoss JIRA] (AS7-4426) Remote store config errors in AS7

by rang s (JIRA)

rang s created AS7-4426: --------------------------- Summary: Remote store config errors in AS7 Key: AS7-4426 URL: https://issues.jboss.org/browse/AS7-4426 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.1.1.Final Environment: Windows Reporter: rang s Assignee: David Lloyd When remote-store is configured in domain.xml, on server startup following errors :- [Server:server-one] 17:00:00,889 ERROR [org.jboss.msc.service.fail] (pool-13-thread-1) MSC00001: Failed to start service jboss.infinispan.web.repl: org.jboss.msc.servic e.StartException in service jboss.infinispan.web.repl: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.loaders.CacheLoaderManagerImpl. start() on object [Server:server-one] at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:62) [jboss-as-clustering-common-7.1.1.Final.jar:7.1.1.Final] [Server:server-one] Caused by: org.infinispan.CacheConfigurationException: Unable to instantiate class org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFacto ry [Server:server-one] Caused by: java.lang.ClassNotFoundException: org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory Looks like some issue in locating the jar which contains this class file. I could resolve this issue by :- Adding the following :- <module name="org.infinispan.client.hotrod"/> in %JBOSS_HOME%/modules/org/infinispan/main/module.xml This seems to be a bug as it should work out of the box. -- 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

13 years, 7 months

7
18
0 / 0

[JBoss JIRA] (AS7-4851) Server boot time shown after loading all applications

by Jim Tyrrell (JIRA)

Jim Tyrrell created AS7-4851: -------------------------------- Summary: Server boot time shown after loading all applications Key: AS7-4851 URL: https://issues.jboss.org/browse/AS7-4851 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell When starting an instance, it would be nice to have a logging message showing that the server has started with the applications in an amount of time. Not unlike the server boot time shown in the first screen shot. -- 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

13 years, 7 months

2
6
0 / 0

[JBoss JIRA] (JGRP-1455) Message lost in NAKACK due to digest error

by David Hotham (JIRA)

David Hotham created JGRP-1455: ---------------------------------- Summary: Message lost in NAKACK due to digest error Key: JGRP-1455 URL: https://issues.jboss.org/browse/JGRP-1455 Project: JGroups Issue Type: Bug Affects Versions: 3.0.9 Reporter: David Hotham Assignee: Bela Ban Hello, In this issue an application-level message broadcast to the cluster is being discarded by NAKACK2, on a new joiner. I think I understand roughly what's going on - skip to the end for a suggested fix! I'll keep all my trace so that I can investigate further details if needed. So, let's start with trace from the new joiner (CFS-B-chucklebrothers), showing that: - it sets a digest claiming that the sequence numbers for CFS-A-tinkywinky are 26 (26) - CFS-A-tinkywinky then sends messages with sequence numbers 26 and 27 - Only message 27 is passed upwards {noformat} 2012-04-18 19:26:49.133 [ForkJoinPool-1-worker-3] DEBUG org.jgroups.protocols.pbcast.NAKACK2 - [CFS-B-chucklebrothers setDigest()] existing digest: [] new digest: CFS-A-tinkywinky: [26 (26)], CFS-A-chucklebrothers: [0 (0)], CFS-B-tinkywinky: [0 (0)], CFS-B-chucklebrothers: [0 (0)] resulting digest: CFS-A-tinkywinky: [26 (26)], CFS-A-chucklebrothers: [0 (0)], CFS-B-tinkywinky: [0 (0)], CFS-B-chucklebrothers: [0 (0)] 2012-04-18 19:26:49.200 [Incoming-2,Clumpy Test Cluster,CFS-B-chucklebrothers] TRACE org.jgroups.protocols.TCP - received [dst: <null>, src: CFS-A-tinkywinky (3 headers), size=39 bytes], headers are SEQUENCER: WRAPPED_BCAST (tag=[CFS-B-chucklebrothers|0]), NAKACK2: [MSG, seqno=26], TCP: [channel_name=Clumpy Test Cluster] 2012-04-18 19:26:49.200 [Incoming-2,Clumpy Test Cluster,CFS-B-chucklebrothers] TRACE org.jgroups.protocols.TCP - received [dst: <null>, src: CFS-A-tinkywinky (3 headers), size=51 bytes], headers are SEQUENCER: BCAST (tag=[CFS-A-tinkywinky|11]), NAKACK2: [MSG, seqno=27], TCP: [channel_name=Clumpy Test Cluster] 2012-04-18 19:26:49.200 [Incoming-2,Clumpy Test Cluster,CFS-B-chucklebrothers] TRACE org.jgroups.protocols.pbcast.NAKACK2 - CFS-B-chucklebrothers: received CFS-A-tinkywinky#27 {noformat} And here's the trace from CFS-A-tinkywinky showing that: - the digest that it sent only claimed sequence numbers 25 (25) {noformat} 2012-04-18 19:26:49.132 [OOB-1,Clumpy Test Cluster,CFS-A-tinkywinky] TRACE org.jgroups.protocols.TCP - sending msg to CFS-B-chucklebrothers, src=CFS-A-tinkywinky, headers are GMS: GmsHeader[JOIN_RSP]: join_rsp=view: [CFS-A-tinkywinky|3] [CFS-A-tinkywinky, CFS-A-chucklebrothers, CFS-B-tinkywinky, CFS-B-chucklebrothers], digest: CFS-A-tinkywinky: [25 (25)], CFS-A-chucklebrothers: [0 (0)], CFS-B-tinkywinky: [0 (0)], CFS-B-chucklebrothers: [0 (0)], UNICAST2: DATA, seqno=2, conn_id=3, TCP: [channel_name=Clumpy Test Cluster] {noformat} By looking at trace from the other members receiving message 26, I can see that this is an application level message. I think that the incrementing of the received sequence number is deliberate, per ClientGmsImpl ("see doc/design/varia2.txt for details"). If I understand correctly, it's intended to compensate for the fact that the the digest doesn't include the broadcast VIEW message. However, CFS-A-tinkywinky shows this: {noformat} 2012-04-18 19:26:49.125 [ViewHandler,Clumpy Test Cluster,CFS-A-tinkywinky] WARN org.jgroups.protocols.pbcast.GMS - CFS-B-chucklebrothers already present; returning existing view [CFS-A-tinkywinky|3] [CFS-A-tinkywinky, CFS-A-chucklebrothers, CFS-B-tinkywinky, CFS-B-chucklebrothers] 2012-04-18 19:26:49.126 [ViewHandler,Clumpy Test Cluster,CFS-A-tinkywinky] TRACE org.jgroups.protocols.pbcast.GMS - found no members to add or remove, will not create new view {noformat} My thinking is that since the coordinator does not broadcast a VIEW message, it's a mistake for CFS-B-chucklebrothers to have fixed up the digest. Possibly the fix is simply to remove the block of code in CoordGmsImpl.handleMembershipChange() for "found no members to add or remove", and send out a view anyway? Thanks! David -- 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

13 years, 7 months

2
17
0 / 0

[JBoss JIRA] (AS7-2322) Stack trace improvements, summarize the things that broke to make them not so intimidating

by Jim Tyrrell (Created) (JIRA)

Stack trace improvements, summarize the things that broke to make them not so intimidating ------------------------------------------------------------------------------------------ Key: AS7-2322 URL: https://issues.jboss.org/browse/AS7-2322 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell See the typical attached stack dump: It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump: 11:51:45,391 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}} 11:51:45,392 INFO [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report Services which failed to start: service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context 11:51:45,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms 11:51:45,417 Error Summary of Exceptions in deployment: - [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B - [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart - ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext - [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: ERROR Scroll up to see more info... Or 11:51:45,417 Error Summary of Exceptions in deployment: [1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B [2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B [3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart [4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors [5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext [6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR: ERROR Scroll up to see more info... -- 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

13 years, 7 months

6
15
0 / 0

[JBoss JIRA] (AS7-4799) Convert JDR subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4799: -------------------------------- Summary: Convert JDR subsystem to ResourceDefinition Key: AS7-4799 URL: https://issues.jboss.org/browse/AS7-4799 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, JDR Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Convert subsystem to use ResourceDefinition and AttributeDefinition -- 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

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (AS7-5061) CLONE - add-user script broken

by Samuel Doyle (JIRA)

Samuel Doyle created AS7-5061: --------------------------------- Summary: CLONE - add-user script broken Key: AS7-5061 URL: https://issues.jboss.org/browse/AS7-5061 Project: Application Server 7 Issue Type: Bug Reporter: Samuel Doyle Assignee: Darran Lofthouse Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 ./add-user.sh dustin dustin1 does not work anymore. In previous versions it worked. It has to do with the "theConsole" object being null. In the same breadth, the --silent=true option in add-user.sh does not work anymore. Again has to do with the need for "theConsole" object being null. The --silent=true option was added because in some environments, System.console() returns null[for example when the Izpack installer calls that script] and the add-user.sh script breaks because of its dependence on System.console() object to print stuff. [the "theConsole" object calls the System.console() object] -- 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

13 years, 7 months

4
11
0 / 0

[JBoss JIRA] (AS7-4925) Log4j appenders should also be allowed for custom handlers

by James Perkins (JIRA)

James Perkins created AS7-4925: ---------------------------------- Summary: Log4j appenders should also be allowed for custom handlers Key: AS7-4925 URL: https://issues.jboss.org/browse/AS7-4925 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 Currently custom handlers only allows for a {{java.util.logging.Handler}}. log4j appenders also need to be allowed and configured. -- 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

13 years, 7 months

3
13
0 / 0

[JBoss JIRA] (AS7-4791) Convert logging subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4791: -------------------------------- Summary: Convert logging subsystem to ResourceDefinition Key: AS7-4791 URL: https://issues.jboss.org/browse/AS7-4791 Project: Application Server 7 Issue Type: Sub-task Components: Logging Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: James Perkins Fix For: 7.2.0.Alpha1 Convert logging subsystem to ResourceDefinition to unify and cleanup the 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

13 years, 7 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 June 2012