December 2011 - jboss-as7-dev - Jboss List Archives

by Robb Greathouse

Hi, Got the following question from a big telecom ISV. How does AS7 support SIP? We create a new extension module to deploy sip servelet in sip container. We need to have a way to skip the creation of StandardContext and JBossContextConfig objects in WarDeploymentProcessor:eploy() since we will create our own ConvergedContext and ConvergedContextConfig objects in our own SipContainerDeploymentProcessor:eploy(). <Fevzi> I don't think that overriding processDeployment is the correct path in terms of bug fixes in the future. What is the recommended way to create your own StandardContext and JBossContextConfig? WarDeploymentProcessor:rocessDeployment(final String hostName, final WarMetaData warMetaData, final DeploymentUnit deploymentUnit, final ServiceTarget serviceTarget) throws DeploymentUnitProcessingException { … // Create the context final StandardContext webContext = new StandardContext(); final ContextConfig config = new JBossContextConfig(deploymentUnit); … } In subsystem: processorTarget.addDeploymentProcessor(Phase.INSTALL, Phase.INSTALL_WAR_DEPLOYMENT, new SipContainerDeploymentProcessor()); SipContainerDeploymentProcessor:elploy() { … // ConvergedJBossContextConfig extends JBossContextConfig final ConvergedContext convergedContext = new ConvergedContext(); // Meta data is send to config here. final ConvergedContextConfig config = new ConvergedContextConfig(deploymentUnit); … } We need to have a way to call host.setConfigClass(ConvergedContext_Object) to set our own ConvergedContext when Web container receives a HTTP request. So we can achieve converged application. <Fevzi> Similar to the question above but utilizing host.setConfigClass. The sip servlet application is packaged in .sar file. In the new extension module we build, can we set the deploy type to be WAR to make the web deploy works. DeploymentTypeMarker.setType(DeploymentType.WAR, deploymentUnit); <Fevzi> According to JSR 289 the deployment archive has to have sar extension (which we also utilize in JBoss), in the creation of this DeploymentType should type Deployment.WAR be utilized or Deployment.WAR-1? 4 How to catch the org.apache.catalina.LifecycleListener? <Fevzi> In the Service class there is no Init, PreStart, PostStart. Ericsson would like to spawn a thread that will conduct a lot of blocking operations and doesn't want to delay the "start" phase, this could lead to potential issues with attempting to load non started modules. How should ContainerLifeCycle be managed in EAP6? What are the best practises? --

12 years, 4 months

2
1
0 / 0

Updated look&feel for CR1

by Heiko Braun

I've update the landing pages to reflect the new console look&feel that ships with CR1. In order to reach some level of consistency for the web based views. Here's what the console and the landing pages look like now: http://community.jboss.org/wiki/UpdatedLookfeelForCR1 -- Heiko Braun Senior Software Engineer JBoss by Red Hat http://about.me/hbraun

12 years, 4 months

4
6
0 / 0

Failed to create poller ..

by Heiko Braun

From the most recent standalone bootstrap log: "14:41:15,315 INFO [org.apache.tomcat.util.net.AprEndpoint] (MSC service thread 1-3) Failed to create poller with specified size of 32768 " -- Heiko Braun Senior Software Engineer JBoss by Red Hat http://about.me/hbraun

12 years, 4 months

1
0
0 / 0

Closed/Reopened pull requests - github weirdness

by Kabir Khan

Due to the length of the pull queue and the number of requests that sit there for a while with a "negative" review awaiting further action from the committer I have started closing those asking people to reopen them. The intention of this was to have less noise for whoever is reviewing next. However, we noticed this has some problems, the workflow is something like this: -PR is submitted on xxxxx:branch_A with CommitA -PR gets closed -xxxx updates branch_A with CommitB and CommitC -PR gets reopened =>CommitB and CommitC are **NOT** visible in the PR -xxxx updates branch_A with CommitD => CommitB, CommitC and CommitD are visible in the PR So it seems like the pull request only polls for new commits while it is open. Anything committed when it was closed is invisible, until something else is committed once reopened. I'm not sure what the best way to solve this is (unless we stop closing stuff), perhaps to never reopen but to create a new request with a link to the old one so the comments are visible?

12 years, 4 months

2
3
0 / 0

Document base does not exist … ?

by Heiko Braun

[Server:server-two] 14:13:12,680 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Error starting static Resources: java.lang.IllegalArgumentException: Document base /Users/hbraun/dev/prj/jboss-as/build/target/jboss-as-7.1.0.CR1-SNAPSHOT/jboss.home.dir/welcome-content does not exist or is not a readable directory -- Heiko Braun Senior Software Engineer JBoss by Red Hat http://about.me/hbraun

12 years, 4 months

3
3
0 / 0

the keystore for the testsuite/integration/basic won't be valid after 11/01/2012

by jean-frederic clere

While testing I noted: +++ Alias name: tomcat Creation date: Oct 13, 2011 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown Issuer: CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown Serial number: 4e96bf49 Valid from: Thu Oct 13 12:36:57 CEST 2011 until: Wed Jan 11 11:36:57 CET 2012 +++ This will need to be fixed soon :D Cheers Jean-Frederic

12 years, 4 months

1
0
0 / 0

A note of thanks to the AS7 developers

by Francesco Marchioni

My hearty and sincere thanks to all JBoss guys that helped me through the new application server's maze. Thanks to your precious help, today the AS 7 book is out (@ Packt Publishing), one month earlier than we planned! Happy Christmas to everyone!

12 years, 4 months

2
1
0 / 0

Preliminary status of CR1 and Tooling compatibility

by Max Rydahl Andersen

Hi Jason, Been a busy day but here are the current findings: All major functionality works for local auth when using JBoss Tools/Developer Studio M5 against AS7.1.CRlatest start, stop, detection of module, restart of module all works. Remote auth we are still verifying (but don't expect issues) And all examples in JBoss Central seem to work fine too (this is better than AS 7b1). I will though like to double check this but i'm running out of time today. The only "glitch" we found is that you moved from ="9999" to ="${property:9999]" which our server editor does not like, but it can be worked around. https://issues.jboss.org/browse/JBIDE-10513 - if someone could point to where in AS7 codebase the algorithm/parsing is for this we will make sure JBoss Tools understands this by its next release. Thus in short: everything looks fine as of today. If you guys change things in removing or other "sensitive" areas before 21st let us know and we'll rerun our manual tests. /max http://about.me/maxandersen

12 years, 4 months

2
2
0 / 0

java.lang.NoClassDefFoundError: javax/naming/Context

by Punekar, Prashant - Contractor

Hi, I am new to jboss as 7 and not able to get a proper way to add a jar to module classpath. Here is the error I am getting. Request you help. exception org.jboss.resteasy.spi.UnhandledException: java.lang.NoClassDefFoundError: javax/naming/Context org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:345) org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:321) org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214) org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:534) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) root cause java.lang.NoClassDefFoundError: javax/naming/Context LoginServiceImpl.getAccountInfo(LoginServiceImpl.java:16) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) root cause java.lang.ClassNotFoundException: javax.naming.Context from [Module "com.layer.logincore:main" from local module loader @1bd2664 (roots: C:\jboss-as-7.1.0.Beta1b\modules)] org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:485) org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:444) org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:421) org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:143) LoginServiceImpl.getAccountInfo(LoginServiceImpl.java:16) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209) org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) note The full stack trace of the root cause is available in the JBoss Web/7.0.3.Final logs. Regards, Prashant

12 years, 4 months

1
0
0 / 0

Behaviour of EJB timer with intervall has changed AS5 -> AS7

by Wolf-Dieter Fink

I've tested the behaviour of AS7 timer during bug fixing. And now I need to discuss and clarify how the behaviour in AS7 should be. There is a big difference in case of overlapping timers between EAP5.1 (and earlier, I don't check AS6) and AS7. ISSUE: If a timer is longer active as the interval, the time-out was delayed as long as the running timer is active. With AS7 the time-out method will be executed and run concurrent! I see migration issues because the application may rely on the non concurrent behaviour. QUESTIONS: The fix looks simple. But I want to clarify whether there is a counter-argument 1) recurring (interval) timer A interval timer should not be called until it is still running => there is no WARN/INFO should we add it? 2) calendar timer Should a calendar timer delayed also if the period between time-outs is to short? => I would prefer a WARN message if the timer is dropped What about catch up on startup if the timer is persistent. ATM all events are fired in parallel if there are more. (This will be a nice ERROR party in the log file in case of SingletonBeans with default WRITE lock.) => Drop it with a warning => block it until the first is finished regards Wolf

12 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

jboss-as7-dev December 2011