July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5053) Allow EJB deployments as OSGi bundles

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5053: ----------------------------------- Summary: Allow EJB deployments as OSGi bundles Key: AS7-5053 URL: https://issues.jboss.org/browse/AS7-5053 Project: Application Server 7 Issue Type: Sub-task Components: EJB, OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] (AS7-5094) CNFE com.sun.org.apache.xml.internal.security.transforms.implementations.TransformBase64Decode

by Maas van den Berg (JIRA)

Maas van den Berg created AS7-5094: -------------------------------------- Summary: CNFE com.sun.org.apache.xml.internal.security.transforms.implementations.TransformBase64Decode Key: AS7-5094 URL: https://issues.jboss.org/browse/AS7-5094 Project: Application Server 7 Issue Type: Bug Components: XML Frameworks Affects Versions: 7.1.1.Final Reporter: Maas van den Berg Assignee: Jason Greene -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3567) Too many class loaders created during jitting by the ClassGenerator

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3567: ------------------------------------ Summary: Too many class loaders created during jitting by the ClassGenerator Key: JBRULES-3567 URL: https://issues.jboss.org/browse/JBRULES-3567 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-4769) Remove no users redirect from /management context

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4769: ------------------------------------- Summary: Remove no users redirect from /management context Key: AS7-4769 URL: https://issues.jboss.org/browse/AS7-4769 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 For AS 7.1.0 we secured the server by default, to make getting started easier we added an automatic redirect on the http interface if a user attempts to connect but no users have been defined, currently this redirect is on both /console and /management We need to remove the redirect on /management as utilities connecting to this context may not be web browsers with an ability to do anything about the redirect - instead we should most likely leave the http 401 in place to request authentication and possibly include some text in the response to indicate no users are defined yet. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] (AS7-4750) Starting a default ha configuration yields a hornetq error

by Heiko Braun (JIRA)

Heiko Braun created AS7-4750: -------------------------------- Summary: Starting a default ha configuration yields a hornetq error Key: AS7-4750 URL: https://issues.jboss.org/browse/AS7-4750 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMS Reporter: Heiko Braun Assignee: Brian Stansberry ./bin/standalone.sh --server-config=standalone-full-ha.xml leads to (after a while) {noformat} 14:33:05,263 ERROR [org.hornetq.core.server.cluster.impl.BroadcastGroupImpl] (Thread-2 (HornetQ-scheduled-threads-25881841)) Failed to broadcast connector configs: java.io.IOException: Network is unreachable at java.net.PlainDatagramSocketImpl.send(Native Method) [classes.jar:1.6.0_31] at java.net.DatagramSocket.send(DatagramSocket.java:625) [classes.jar:1.6.0_31] {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

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] (AS7-5013) ConfigAdminManagementTestCase.testConfigAdminWriteFromDMR fails on windows

by Tomaz Cerar (JIRA)

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] (AS7-5106) org.apache.coyote.http11.InternalOutputBuffer is not safe

by Ste Gr (JIRA)

Ste Gr created AS7-5106: --------------------------- Summary: org.apache.coyote.http11.InternalOutputBuffer is not safe Key: AS7-5106 URL: https://issues.jboss.org/browse/AS7-5106 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Reporter: Ste Gr Assignee: Remy Maucherat As soon as the http response should be send, there might be the problem, where the headers exceed the size of the internal output buffer. (see https://issues.jboss.org/browse/ARQ-982) 1. problem: No boundary check on the array 'buf' of InternalOutputBuffer 2. problem: The whole sendHeader-routine is not able to split the split the send of headers. Example stack trace (arquillian warp is adds the big header): InternalOutputBuffer.write(String) line: 698 InternalOutputBuffer.write(MessageBytes) line: 607 InternalOutputBuffer.sendHeader(MessageBytes, MessageBytes) line: 479 Http11Processor.prepareResponse() line: 1648 Http11Processor.action(ActionCode, Object) line: 998 Response.action(ActionCode, Object) line: 188 InternalOutputBuffer.doWrite(ByteChunk, Response) line: 552 Response.doWrite(ByteChunk) line: 594 OutputBuffer.realWriteBytes(byte[], int, int) line: 398 ByteChunk.flushBuffer() line: 449 ByteChunk.append(byte[], int, int) line: 349 OutputBuffer.writeBytes(byte[], int, int) line: 426 OutputBuffer.write(byte[], int, int) line: 415 CoyoteOutputStream.write(byte[], int, int) line: 89 CoyoteOutputStream.write(byte[]) line: 83 NonWritingPrintWriter.finallyWriteAndClose(ServletOutputStream) line: 58 WarpFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 189 ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280 ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248 TransactionWebFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 38 ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280 ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248 NTLMFakeFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 33 ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280 ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248 StandardWrapperValve.invoke(Request, Response) line: 275 StandardContextValve.invoke(Request, Response) line: 161 WebNonTxEmCloserValve.invoke(Request, Response) line: 50 SecurityContextAssociationValve.invoke(Request, Response) line: 153 StandardHostValve.invoke(Request, Response) line: 155 ErrorReportValve.invoke(Request, Response) line: 102 StandardEngineValve.invoke(Request, Response) line: 109 CoyoteAdapter.service(Request, Response) line: 368 Http11Processor.process(Socket) line: 877 Http11Protocol$Http11ConnectionHandler.process(Socket) line: 671 JIoEndpoint$Worker.run() line: 930 Thread.run() line: not available -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-5105) ConfiguredService asumes update call with not null Dictionary

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5105: ----------------------------------- Summary: ConfiguredService asumes update call with not null Dictionary Key: AS7-5105 URL: https://issues.jboss.org/browse/AS7-5105 Project: Application Server 7 Issue Type: Task Components: ConfigAdmin Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.2.0.Alpha1 {code} 11:15:04,876 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-3-thread-1) Failed: org.jboss.as.test.integration.osgi.configadmin.ConfigurationAdminTestCase.testManagedServiceConfiguredFromXML: java.lang.NullPointerException at org.jboss.as.test.integration.osgi.xservice.bundle.ConfiguredService.getValue(ConfiguredService.java:61) at org.jboss.as.test.integration.osgi.configadmin.ConfigurationAdminTestCase.testManagedServiceConfiguredFromXML(ConfigurationAdminTestCase.java:154) {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, 10 months

2
5
0 / 0

[JBoss JIRA] (AS7-351) Implement the HttpService ontop of JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-351?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated AS7-351: ------------------------------- Fix Version/s: 7.2.0.CR1 > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: AS7-351 > URL: https://issues.jboss.org/browse/AS7-351 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Web > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Priority: Critical > Fix For: 7.2.0.CR1 > > Attachments: DefaultHttpContext.java, http-service-1.2.pdf, HttpServiceImpl.java, registerServlet, ResourceServlet.java > > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-4321) OSGi management console needs inspector of wiring

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-4321?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-4321: -------------------------------- Fix Version/s: 7.2.0.CR1 > OSGi management console needs inspector of wiring > ------------------------------------------------- > > Key: AS7-4321 > URL: https://issues.jboss.org/browse/AS7-4321 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console, OSGi > Affects Versions: 7.1.1.Final > Environment: Mac OS X 10.7.3 > Reporter: Tim Diekmann > Assignee: David Bosschaert > Fix For: 7.2.0.CR1 > > > The OSGi management console for AS 7 needs a viewer of the current wiring. The console log showed the following error on start of the bundle and there is no way to inspect the wiring to see where the problem lies and how to solve it. There is some inconsistency in the deployment, but how to find out what? > {code} > 00:09:14,480 ERROR [org.mortbay.log] (HttpManagementService-threads - 3) Error starting handlers: java.lang.IncompatibleClassChangeError: Class org.eclipse.equinox.http.servlet.HttpServiceServlet does not implement the requested interface javax.servlet.Servlet > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.init(HttpServerManager.java:294) > at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431) > at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:681) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:140) > at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) > at org.mortbay.jetty.Server.doStart(Server.java:224) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:109) > at org.eclipse.equinox.http.jetty.internal.Activator.start(Activator.java:60) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) > at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132) > at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89) > at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304) > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) > at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) > at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {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, 10 months

1
0
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 July 2012