[Installation, Configuration & DEPLOYMENT] - Re: JBOSS Deployment Error
by agraber
...yes typo: running with jdk 1.4.2_03 and JBoss 4.0.3 produces error; see stack-trace below.
Thanks Alfred
| 23:15:12,937 WARN [XMLLoginConfigImpl] End loadConfig, failed to load config: file:/C:/projects/mobi/marktradar/workspace/marktradar/jboss_4.0.3/server/default/conf/login-config.xml
| org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1, column 1.
| Was expecting one of:
| <EOF>
| <IDENTIFIER> ...
|
| at org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:395)
| at org.jboss.security.auth.login.SunConfigParser.jj_consume_token(SunConfigParser.java:333)
| at org.jboss.security.auth.login.SunConfigParser.config(SunConfigParser.java:98)
| at org.jboss.security.auth.login.SunConfigParser.parse(SunConfigParser.java:57)
| at org.jboss.security.auth.login.SunConfigParser.doParse(SunConfigParser.java:79)
| at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:294)
| at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:278)
| at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:252)
| at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:162)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
| at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:428)
| at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:265)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:428)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
| at org.jboss.Main.boot(Main.java:187)
| at org.jboss.Main$1.run(Main.java:438)
| at java.lang.Thread.run(Thread.java:534)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081870#4081870
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081870
18 years, 7 months
[JBoss Seam] - Re: General Performance concerns on presentation and busines
by jim.barrows
"phpguy99" wrote : What is your take on commonly accepted practice to physically separate business and presentation layer for reasons like:
| - security: presentation layer is the only one that gets exposed to the internet and it take hackers more layer to crack.
|
But is this really true? Since your business layer must be exposed to the presentation? While it is possible to lock thigns down quite tightly, once the front server is compromised, so are any holes you've opened.
However, I think you're missing something about the design of J2EE apps. J2EE has seperatio of concerns and 3+ layer architecture for quite some time. The backing beans are supposed to talk to your business logic layer.
"phpguy99" wrote :
| - scalability: easier to scale either/both presentation and business layer if they are separated.
|
J2EE can scale in 4 different areas, and with a fairly fine granularity. I can have a particular EJB on a server dedicated to itself, if necessary, or a whole bunch. Same with a web app. Since EJB's carry business logic, I can scale one bit of logic, or lots. I can scale at the database. I can scale the connections to everything.
"phpguy99" wrote :
| - easier division of labor: presentation and business-logic developers only care about their components and they can become more skillful/specialized in their area.
|
Again J2EE has had division of labor for quite some time. It's nice to see someone from the PHP world catch up to us :)
You can't forget that Seam is built on jBPM, Drools, and J2EE. Bringing with it all of J2EE's strengths, while leaving much of it's pain behind. In order understand those strengths, you probably need to go look at all of Sun's J2EE documentation to understand how things are designed, and why SEAM is truly great.
"phpguy99" wrote :
| Thanks so much in advance.
|
Your welcome
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081868#4081868
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081868
18 years, 7 months
[JBoss Seam] - Re: Maven Archetype for Seam?
by anders3
Thanks for the hint,
I can still not make it work.
I have tried it on and off, and it is deeply fustrating to work with seam.
Tasks that should seem simple turns out to be strange all the way.
I now want to build the dvdstore and pack it exactly as the ant build does.
But then the meaning of it all vanish.
On the other hand I am never going to use any software that cannot build by maven any longer.
A few fustrations:
1) the application.xml is version 5. My maven plugin will not accept 5 or 1.5 as version.
2) is jboss-seam.jar really an ejb module ????
3) artifact like hibernate-all.jar what is that ?? And where does that come from??
Thinking about how simple and beautifull seam could be using maven just fustrates double seeing all this ant trash.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081866#4081866
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081866
18 years, 7 months
[JCA/JBoss] - Thread BLOCKED on registerConnection/unregisterConnection?
by ALRubinger
Hiya.
Today we've done a stress test on our application and observed some new behavior - many of the functions that we're delegating to Quartz Scheduler (each with its own Thread) started to take quite a while to complete, and queued up.
Did a Thread Dump, revealing many of these Threads to be in BLOCKED state, referencing a WeakHashMap while either attempting to register or unregister a connection from the pool.
Any ideas what could cause this? Incorrectly configured pool size? Not enough DB Connections available?
Thread: DefaultQuartzScheduler_Worker-23 : priority:7, demon:false, threadId:58, threadState:BLOCKED, threadLockName:java.util.WeakHashMap@6ac57e7d
|
| org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:288)
| org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417)
| org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
| org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
| org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
| org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:417)
| org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081860#4081860
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081860
18 years, 7 months