January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6264) AS7.1 Class loading causes an issue with netty and application deployment

by Michael Erdmann (JIRA)

[ https://issues.jboss.org/browse/AS7-6264?page=com.atlassian.jira.plugin.s... ] Michael Erdmann commented on AS7-6264: -------------------------------------- I guess the fact that i can loads classes from my deployment and i can't load the same classes from the netty handler i would have considered as an issue which could be a bug. Or is this normal that two parts of a deployment are seeing different class pathes? > AS7.1 Class loading causes an issue with netty and application deployment > ------------------------------------------------------------------------- > > Key: AS7-6264 > URL: https://issues.jboss.org/browse/AS7-6264 > Project: Application Server 7 > Issue Type: Feature Request > Components: Class Loading > Affects Versions: 7.1.1.Final > Environment: Linux Open Suse > Reporter: Michael Erdmann > Assignee: David Lloyd > Labels: jboss > > I am intending to deploy an application which uses some third party library available as jar. The application server is based on netty which is expected to call the final application code using a pipe line handler. > The handler is not able to load any class which is located in the third party library. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6141) JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6141?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6141: ---------------------------------- Priority: Major (was: Critical) > JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't. > ------------------------------------------------------------------------------------------- > > Key: AS7-6141 > URL: https://issues.jboss.org/browse/AS7-6141 > Project: Application Server 7 > Issue Type: Bug > Components: Documentation > Affects Versions: 7.1.1.Final > Environment: JBoss Developer Framework site. http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/#introduction > Reporter: Rick Wagner > > The README.md describes an 'example-settings.xml' file that should be 'in the root of your quickstarts folder'. There does not seem to be such a file. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6264) AS7.1 Class loading causes an issue with netty and application deployment

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6264?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6264: ---------------------------------- I am not sure why this is a pertinent reply. Please bring your problem to the user forums. > AS7.1 Class loading causes an issue with netty and application deployment > ------------------------------------------------------------------------- > > Key: AS7-6264 > URL: https://issues.jboss.org/browse/AS7-6264 > Project: Application Server 7 > Issue Type: Feature Request > Components: Class Loading > Affects Versions: 7.1.1.Final > Environment: Linux Open Suse > Reporter: Michael Erdmann > Assignee: David Lloyd > Labels: jboss > > I am intending to deploy an application which uses some third party library available as jar. The application server is based on netty which is expected to call the final application code using a pipe line handler. > The handler is not able to load any class which is located in the third party library. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6264) AS7.1 Class loading causes an issue with netty and application deployment

by Michael Erdmann (JIRA)

[ https://issues.jboss.org/browse/AS7-6264?page=com.atlassian.jira.plugin.s... ] Michael Erdmann commented on AS7-6264: -------------------------------------- 18:05:34,538 INFO [site.boavista.jboss.view.NettyEJB] (MSC service thread 1-7) NettyServer: Server startup done. 18:05:34,582 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /MyCommunityJBoss 18:05:34,740 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "MyCommunityJBoss.war" with deployment "MyCommunityJBoss.war" 18:05:52,767 INFO [site.boavista.jboss.view.NettyEJB] (New I/O server boss #32 ([id: 0x20307667, /0.0.0.0:8887])) Channel state changed: [id: 0x32a1811f, /84.189.40.180:38629 => /213.73.112.26:8887] OPEN 18:05:52,774 INFO [site.boavista.jboss.view.NettyEJB] (New I/O server worker #32-1) Channel state changed: [id: 0x32a1811f, /84.189.40.180:38629 => /213.73.112.26:8887] BOUND: /213.73.112.26:8887 18:05:52,780 INFO [site.boavista.jboss.view.NettyEJB] (New I/O server worker #32-1) Channel state changed: [id: 0x32a1811f, /84.189.40.180:38629 => /213.73.112.26:8887] CONNECTED: /84.189.40.180:38629 18:05:52,864 ERROR [stderr] (New I/O server worker #32-1) java.lang.NoClassDefFoundError: com/db4o/ObjectContainer 18:05:52,867 ERROR [stderr] (New I/O server worker #32-1) at site.boavista.jboss.view.EchoServerHandler.messageReceived(EchoServerHandler.java:21) 18:05:52,871 ERROR [stderr] (New I/O server worker #32-1) at site.boavista.jboss.view.MyChannelHandler.handleUpstream(MyChannelHandler.java:21) 18:05:52,874 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) 18:05:52,878 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) 18:05:52,881 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:351) 18:05:52,884 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282) 18:05:52,888 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:202) 18:05:52,891 ERROR [stderr] (New I/O server worker #32-1) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 18:05:52,894 ERROR [stderr] (New I/O server worker #32-1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 18:05:52,897 ERROR [stderr] (New I/O server worker #32-1) at java.lang.Thread.run(Thread.java:679) 18:05:52,900 ERROR [stderr] (New I/O server worker #32-1) Caused by: java.lang.ClassNotFoundException: com.db4o.ObjectContainer from [Module "deployment.MyCommunityJBoss.war:main" from Service Module Loader] 18:05:52,904 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) 18:05:52,907 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) 18:05:52,911 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) 18:05:52,914 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) 18:05:52,917 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) 18:05:52,921 ERROR [stderr] (New I/O server worker #32-1) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) 18:05:52,925 ERROR [stderr] (New I/O server worker #32-1) ... 10 more 18:05:52,927 INFO [site.boavista.jboss.view.NettyEJB] (New I/O server worker #32-1) Channel state changed: [id: 0x32a1811f, /84.189.40.180:38629 :> /213.73.112.26:8887] DISCONNECTED 18:05:52,932 INFO [site.boavista.jboss.view.NettyEJB] (New I/O server worker #32-1) Channel state changed: [id: 0x32a1811f, /84.189.40.180:38629 :> /213.73.112.26:8887] UNBOUND 18:05:52,936 INFO [site.boavista.jboss.view.NettyEJB] (New I/O server worker #32-1) Channel state changed: [id: 0x32a1811f, /84.189.40.180:38629 :> /213.73.112.26:8887] CLOSED > AS7.1 Class loading causes an issue with netty and application deployment > ------------------------------------------------------------------------- > > Key: AS7-6264 > URL: https://issues.jboss.org/browse/AS7-6264 > Project: Application Server 7 > Issue Type: Feature Request > Components: Class Loading > Affects Versions: 7.1.1.Final > Environment: Linux Open Suse > Reporter: Michael Erdmann > Assignee: David Lloyd > Labels: jboss > > I am intending to deploy an application which uses some third party library available as jar. The application server is based on netty which is expected to call the final application code using a pipe line handler. > The handler is not able to load any class which is located in the third party library. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5871) The default redirect port for the 8080 connector is current 8433. Should be 8443 instead.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5871?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5871: --------------------------------------- Hi Wolf, What's the status in this? Will you be able to submit a patch this week? If not, please assign this to me. Thanks. > The default redirect port for the 8080 connector is current 8433. Should be 8443 instead. > ------------------------------------------------------------------------------------------ > > Key: AS7-5871 > URL: https://issues.jboss.org/browse/AS7-5871 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Fix For: 7.2.0.Alpha1 > > > The default redirect port for the 8080 connector is 8433. Seems that this is wrong as socket-bindings use 8443 (and former releases also) > [standalone@localhost:9999 /] /subsystem=web/connector=http:read-resource > { > "outcome" => "success", > "result" => { > ..., > "name" => "http", > "protocol" => "HTTP/1.1", > "redirect-port" => 8433, > "scheme" => "http", > "secure" => false, > "socket-binding" => "http", > "ssl" => undefined, > "virtual-server" => undefined > } > } > The pre-configured "https" socket binding conversely is 8443: > [standalone@localhost:9999 socket-binding=https] /socket-binding-group=standard-sockets/socket-binding=https:read-resource > { > "outcome" => "success", > "result" => { > "client-mappings" => undefined, > "fixed-port" => false, > "interface" => undefined, > "multicast-address" => undefined, > "multicast-port" => undefined, > "name" => "https", > "port" => 8443 > } > } -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6265) Expand support for logging System Property substitution

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6265?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-6265: ------------------------------- Description: Attributes to support expressions: * append * autoflush * enabled * use-parent-handlers Also {{enabled}} should be a {{BOOLEAN}} not a {{STRING}}. > Expand support for logging System Property substitution > ------------------------------------------------------- > > Key: AS7-6265 > URL: https://issues.jboss.org/browse/AS7-6265 > Project: Application Server 7 > Issue Type: Sub-task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 7.2.0.Alpha1 > > > Attributes to support expressions: > * append > * autoflush > * enabled > * use-parent-handlers > Also {{enabled}} should be a {{BOOLEAN}} not a {{STRING}}. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6265) Expand support for logging subsystem expressions

by James Perkins (JIRA)

James Perkins created AS7-6265: ---------------------------------- Summary: Expand support for logging subsystem expressions Key: AS7-6265 URL: https://issues.jboss.org/browse/AS7-6265 Project: Application Server 7 Issue Type: Sub-task Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6265) Expand support for logging System Properties

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6265?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-6265: ------------------------------- Summary: Expand support for logging System Properties (was: Expand support for logging subsystem expressions) > Expand support for logging System Properties > -------------------------------------------- > > Key: AS7-6265 > URL: https://issues.jboss.org/browse/AS7-6265 > Project: Application Server 7 > Issue Type: Sub-task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 7.2.0.Alpha1 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6265) Expand support for logging System Property substitution

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6265?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-6265: ------------------------------- Summary: Expand support for logging System Property substitution (was: Expand support for logging System Properties) > Expand support for logging System Property substitution > ------------------------------------------------------- > > Key: AS7-6265 > URL: https://issues.jboss.org/browse/AS7-6265 > Project: Application Server 7 > Issue Type: Sub-task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 7.2.0.Alpha1 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6120) Expand support for System Property substitution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6120: ---------------------------------- Attachment: (was: expressions.ods) > Expand support for System Property substitution > ----------------------------------------------- > > Key: AS7-6120 > URL: https://issues.jboss.org/browse/AS7-6120 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jimmy Wilson > Assignee: Brian Stansberry > Priority: Blocker > Labels: eap-6.1-prd > Fix For: 7.2.0.CR1 > > Attachments: expressions.ods > > > Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes. > The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so. > This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.) -- 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

13 years, 4 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 January 2013