-
1. Re: nightly builds
ctomc Oct 2, 2012 6:02 AM (in response to crazycradd)Did you have any problems with using nightly build?
If yes what kind of problems?
But basicly your application should run also on 7.2 nightly builds without changes.
--
tomaz
-
2. Re: nightly builds
crazycradd Oct 2, 2012 6:36 AM (in response to ctomc)The first error I see is when my app tries to load its log4j config this works fine in 7.1.1 as I package up the class in my ejb lib dir and exclude the packaged log4 j module
<exclusions> <module name="org.apache.log4j" slot="main"/> </exclusions> 11:30:39,628 ERROR [stderr] (MSC service thread 1-1) java.lang.ClassCastException: org.apache.log4j.RollingFileAppender
cannot be cast to org.apache.log4j.Appender
11:30:39,630 ERROR [stderr] (MSC service thread 1-1) at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigu
rator.java:248)
11:30:39,631 ERROR [stderr] (MSC service thread 1-1) at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMCo
nfigurator.java:176)
11:30:39,631 ERROR [stderr] (MSC service thread 1-1) at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(
DOMConfigurator.java:191)
11:30:39,632 ERROR [stderr] (MSC service thread 1-1) at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerEle
ment(DOMConfigurator.java:523)
11:30:39,633 ERROR [stderr] (MSC service thread 1-1) at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurato
The deployer them complains
11:30:57,644 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deploym
ent.subunit."cp.ear"."cp-ejb.jar".component.ExternalSystemEditorSessionSEJB.VIEW."com.cedar.cp.ejb.api.extsys.ExternalSy
stemEditorSessionRemote".REMOTE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."cp.ear"."cp-e
jb.jar".component.ExternalSystemEditorSessionSEJB.VIEW."com.cedar.cp.ejb.api.extsys.ExternalSystemEditorSessionRemote".R
EMOTE: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.G
A.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_14]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_14]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_14]
Caused by: java.lang.IllegalStateException: JBAS014485: EJB ExternalSystemEditorSessionSEJB is enabled for security but
doesn't have a security domain set
at org.jboss.as.ejb3.security.SecurityContextInterceptorFactory.create(SecurityContextInterceptorFactory.java:53
-
3. Re: nightly builds
jaikiran Oct 2, 2012 6:52 AM (in response to crazycradd)Are you using a modified version of the standalone*.xml file that comes with the nightly build? What does the EJB3 subsystem look like in your configuration?
-
4. Re: nightly builds
crazycradd Oct 2, 2012 7:34 AM (in response to jaikiran)Yes I'm I will try again and use the shipped config
-
5. Re: nightly builds
ctomc Oct 2, 2012 7:58 AM (in response to crazycradd)Hi,
add system property -Dorg.jboss.as.logging.per-deployment=false which restores 7.1.1 logging behaivour.
--
tomaz
-
6. Re: nightly builds
crazycradd Oct 2, 2012 8:46 AM (in response to ctomc)thanks that seems to work will I need this -D when 7.2.0 final is available or should I be altering the logging in my app ?
-
7. Re: nightly builds
ctomc Oct 2, 2012 8:52 AM (in response to crazycradd)No that wont change anymore(hopefully)
it was changed for 7.1.2 to enable easier usage of your app provided logging framework
--
tomaz
-
8. Re: nightly builds
crazycradd Oct 2, 2012 10:41 AM (in response to ctomc)Sorry my lookup is working fine its the call to ejbcreate that is failing with a null pointer
-
9. Re: nightly builds
jaikiran Oct 3, 2012 3:10 AM (in response to crazycradd)peter craddock wrote:
Sorry my lookup is working fine its the call to ejbcreate that is failing with a null pointer
Is it the same NullPointerException that you posted earlier? If yes, then I believe you still haven't got the EJB3 subsytem configuration right. Anyway, I've sent a pull request to prevent that NullPointerException for cases like yours https://github.com/jbossas/jboss-as/pull/3164. Depending on when it's reviewed and merged upstream, you'll be able to get it in some future nightly build.
-
10. Re: nightly builds
crazycradd Oct 3, 2012 4:43 AM (in response to jaikiran)Thanks for the help here is the ejb subsystem config we are using if it helps
<subsystem xmlns="urn:jboss:domain:ejb3:1.4"> <session-bean> <stateless> <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/> </stateless> <stateful cache-ref="simple" default-access-timeout="5000"/> <singleton default-access-timeout="5000"/> </session-bean> <default-security-domain value="other"/> <mdb> <resource-adapter-ref resource-adapter-name="hornetq-ra"/> <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> </mdb> <pools> <bean-instance-pools> <strict-max-pool instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES" max-pool-size="20" name="slsb-strict-max-pool"/> <strict-max-pool instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES" max-pool-size="20" name="mdb-strict-max-pool"/> <strict-max-pool instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES" max-pool-size="1" name="despatcher-single-thread-pool"/> <strict-max-pool instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES" max-pool-size="1" name="receiver-single-thread-pool"/> </bean-instance-pools> </pools> <caches> <cache aliases="NoPassivationCache" name="simple"/> <cache aliases="SimpleStatefulCache" name="passivating" passivation-store-ref="file"/> </caches> <passivation-stores> <file-passivation-store name="file"/> </passivation-stores> <async thread-pool-name="default"/> <timer-service thread-pool-name="default"> <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/> </timer-service> <remote connector-ref="remoting-connector" thread-pool-name="default"/> <thread-pools> <thread-pool name="default"> <max-threads count="10"/> <keepalive-time time="100" unit="milliseconds"/> </thread-pool> </thread-pools> <iiop enable-by-default="false" use-qualified-name="false"/> </subsystem> -
11. Re: nightly builds
jaikiran Oct 4, 2012 3:13 AM (in response to crazycradd)Try out the nightly builds now, it should have a fix for the NullPointerException
-
12. Re: nightly builds
crazycradd Oct 4, 2012 6:52 AM (in response to jaikiran)nightly build now fails to deploy simple war due to duplicate resource so I can not deploy my ear into it to test
-
13. Re: nightly builds
jaikiran Oct 4, 2012 8:54 AM (in response to crazycradd)peter craddock wrote:
nightly build now fails to deploy simple war due to duplicate resource so I can not deploy my ear into it to test
Could you please add more details about the failure and the application?
-
14. Re: nightly builds
crazycradd Oct 4, 2012 8:58 AM (in response to jaikiran)We managed to get the application deployed by first starting the server then adding the war and ears to the deployments directory. Starting the server with the apps in the deploy directory fails with a duplicate resource error.
Now we have started the application we have been able to test the ejb lookup this still fails with a null pointer.
Caused by: java.lang.NullPointerException
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.<init>(RemotingConnectionEJBReceiver.java:102)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.<init>(RemotingConnectionEJBReceiver.java:90)
at org.jboss.ejb.client.EJBClientContext.registerConnection(EJBClientContext.java:347)
at org.jboss.naming.remote.client.ejb.RemoteNamingEjbClientContextSelector.getContext(RemoteNamingEjbClientContextSelector.java:60)
at org.jboss.naming.remote.client.ejb.RemoteNamingEjbClientContextSelector.getCurrent(RemoteNamingEjbClientContextSelector.java:46)
at org.jboss.naming.remote.client.ejb.RemoteNamingEjbClientContextSelector.getCurrent(RemoteNamingEjbClientContextSelector.java:15)
at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:228)
at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:238)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:120)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy4.create(Unknown Source)
at com.cedar.cp.ejb.api.logon.LogonServer.getRemote(LogonServer.java:57)