[jira] Created: (GERONIMO-2835) Error when shutting down server
Error when shutting down server --- Key: GERONIMO-2835 URL: https://issues.apache.org/jira/browse/GERONIMO-2835 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.0-M2 Reporter: Krishnakumar B Fix For: 2.0-M2 13:14:56,218 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null java.sql.SQLException: No current connection. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.getAutoCommit(Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.getAutoCommit(Unknown Source) at org.tranql.connector.jdbc.ConnectionHandle.rollback(ConnectionHandle.java:129) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop(BrokerServiceGBeanImpl.java:106) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1146) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:337) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:310) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.system.main.Daemon$1.run(Daemon.java:234) 13:14:56,228 ERROR [JournalPersistenceAdapter] Could not stop service: [EMAIL PROTECTED] Reason: java.sql.SQLException: No current connection. java.sql.SQLException: No current connection. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown Source
Usage of service ref
Hi, I am using a web application that looks up a Service Reference from JNDI. This works if i do not add the following section to geronimo-web.xml !-- service-ref service-ref-nameservice/HelloWorldService/service-ref-name port port-nameHelloWorld/port-name protocolhttp/protocol hostlocalhost/host port8080/port uri/webref/ws/uri /port /service-ref -- Adding this section gives schema validation errors during deployment. I add references for ejb,resource,resource-env in web plan. Should this be maintained for service-ref also? Regards Krishnakumar
Re: [WELCOME] Chris Blythe as a new Committer to Apache Geronimo
Congrats Chris Krish On 1/28/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Congrats Chris. Vamsi On 1/25/07, Matt Hogstrom [EMAIL PROTECTED] wrote: In recognition of Chris' contributions to DayTrader (new UI, new runtime modes) and his sustained set of patches and nagging he has accepted our offer to join our merry little band of pirates. Please join me in welcoming Chris. Matt Hogstrom [EMAIL PROTECTED]
Using PortableRemoteObject narrow in EJB ( 2.0-M1)
Hi, If i use PortableRemoteObject narrow in a servlet i get a exception. [TestHome testHome = (TestHome) PortableRemoteObject.narrow(result, TestHome.class);] java.lang.ExceptionInInitializerError javax.rmi.PortableRemoteObject.clinit(PortableRemoteObject.java:36) org.apache.geronimo.test.TomcatTestServlet.doGet(TomcatTestServlet.java:35) javax.servlet.http.HttpServlet.service(HttpServlet.java:693) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) root cause org.omg.CORBA.INITIALIZE: Can not create Util delegate: org.apache.openejb.corba.util.UtilDelegateImpl: vmcid: 0x0 minor code: 0x0 completed: No javax.rmi.CORBA.Util.clinit(Util.java:47) javax.rmi.PortableRemoteObject.clinit(PortableRemoteObject.java:36) org.apache.geronimo.test.TomcatTestServlet.doGet(TomcatTestServlet.java:35) javax.servlet.http.HttpServlet.service(HttpServlet.java:693) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) I cast the object to EJB Home object when i do a lookup and it works. [TestHome result = (TestHome)ctx.lookup(java:comp/env/ejb/TestBean);] Is this method supported? Regards Krish
Usage of ejb-ref from web application ( 2.0 SNAPSHOT )
Hi, I am trying to get a reference to Session EJB from the web application. It works if i give the ejb-ref like this in geronimo-web.xml ejb-ref xmlns=http://geronimo.apache.org/xml/ns/naming-1.1; ref-nameejb/TestBean/ref-name pattern nameTestBean/name /pattern /ejb-ref If i add groupId, artifactid and version it throws a error ejb-ref xmlns=http://geronimo.apache.org/xml/ns/naming-1.1; ref-nameejb/TestBean/ref-name pattern groupIddefault/groupId artifactIdtomcatejb/artifactId nameTestBean/name /pattern /ejb-ref ejb-ref xmlns=http://geronimo.apache.org/xml/ns/naming-1.1; ref-nameejb/TestBean/ref-name pattern groupIddefault/groupId artifactIdtomcatejb/artifactId version1.0/version nameTestBean/name /pattern /ejb-ref javax.naming.NameNotFoundException: Could not resolve abstract name query [/tomc atejb//?name=TestBean#org.apache.openejb.RpcEjbDeployment] in configuration defa ult/tomcat/1.0/car Is this a bug or the usage is not correct? Regards Krish
Geronimo startup error
Hi, I built 2.0 SNAPSHOT from trunk. On starting the server it throws an error Booting Geronimo Kernel (in Java 1.5.0_05)... [ ] 0% 1s Startup failed org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exceptio n at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:441) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:155) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:126) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Target does not have specified method (declared in a GBeanInfo operation): name=hasGBeanAttr ibutes methodName=hasGBeanAttributes targetClass=org.apache.geronimo.system.conf iguration.LocalAttributeManager at org.apache.geronimo.gbean.runtime.GBeanOperation.init(GBeanOperatio n.java:97) at org.apache.geronimo.gbean.runtime.GBeanInstance.init(GBeanInstance. java:298) at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja va:354) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:363) ... 5 more org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exceptio n at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:441) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:155) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:126) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Target does not have specified method (declared in a GBeanInfo operation): name=hasGBeanAttr ibutes methodName=hasGBeanAttributes targetClass=org.apache.geronimo.system.conf iguration.LocalAttributeManager at org.apache.geronimo.gbean.runtime.GBeanOperation.init(GBeanOperatio n.java:97) at org.apache.geronimo.gbean.runtime.GBeanInstance.init(GBeanInstance. java:298) at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.ja va:354) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:363) ... 5 more Server shutdown begun Server shutdown completed I cleaned the repository and rebuilt. I get the same error. Any pointers... Regards Krishnakumar
Testsuite error related to serialVersionUID
Hi, I am trying to deploy daytrader using the testsuite. I get the following error. The same ear and plan i am able to deploy successfully using the console. Any thoughts on possible reasons for this mismatch in UID. [INFO] [INFO] java.rmi.UnmarshalException: error unmarshalling return; nested ex ception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] [INFO] [INFO] -- -- [INFO] [INFO] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: java.rmi.Unmarsha lException: error unmarshalling return; nested exception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:559) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) [INFO] at java.lang.reflect.Method.invoke(Method.java:585) [INFO] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [INFO] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [INFO] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [INFO] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Caused by: org.apache.maven.plugin.MojoExecutionException: java.rmi.Unmar shalException: error unmarshalling return; nested exception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupp ort.execute(ReportingMojoSupport.java:105) [INFO] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) [INFO] ... 16 more [INFO] Caused by: org.apache.geronimo.kernel.InternalKernelException: java.rmi.U nmarshalException: error unmarshalling return; nested exception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] at org.apache.geronimo.system.jmx.KernelDelegate.getGBeanInfo(KernelDele gate.java:616) [INFO] at org.apache.geronimo.kernel.basic.BasicProxyManager.getVisibleInterfac es(BasicProxyManager.java:123) [INFO] at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicP roxyManager.java:99) [INFO] at org.apache.geronimo.kernel.config.ConfigurationUtil.getConfigurationM anager(ConfigurationUtil.java:260) [INFO] at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.initia lize(JMXDeploymentManager.java:68) [INFO] at org.apache.geronimo.deployment.plugin.jmx.RemoteDeploymentManager.in it(RemoteDeploymentManager.java:73) [INFO] at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl .getDeploymentManager(DeploymentFactoryImpl.java:130) [INFO] at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.get DeploymentManager(DeploymentFactoryManager.java:109) [INFO] at org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.ge tDeploymentManager(ModuleMojoSupport.java:84) [INFO] at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.dis tribute(DeployModuleMojo.java:148) [INFO] at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.doE xecute(DeployModuleMojo.java:94) [INFO] at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupp
Re: Testsuite error related to serialVersionUID
using geronimo-2.0-M1 ( tomcat jetty ) Regards Krish On 12/21/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, I am trying to deploy daytrader using the testsuite. I get the following error. The same ear and plan i am able to deploy successfully using the console. Any thoughts on possible reasons for this mismatch in UID. [INFO] [INFO] java.rmi.UnmarshalException: error unmarshalling return; nested ex ception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] [INFO] [INFO] -- -- [INFO] [INFO] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: java.rmi.Unmarsha lException: error unmarshalling return; nested exception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:559) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) [INFO] at java.lang.reflect.Method.invoke(Method.java:585) [INFO] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [INFO] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [INFO] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [INFO] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Caused by: org.apache.maven.plugin.MojoExecutionException: java.rmi.Unmar shalException: error unmarshalling return; nested exception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupp ort.execute(ReportingMojoSupport.java:105) [INFO] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) [INFO] ... 16 more [INFO] Caused by: org.apache.geronimo.kernel.InternalKernelException: java.rmi.U nmarshalException: error unmarshalling return; nested exception is: [INFO] java.io.InvalidClassException: org.apache.geronimo.gbean.GOperationInfo; local class incompatible: stream classdesc serialVersionUID = 51855155811041929 76, local class serialVersionUID = -5593225815559931812 [INFO] at org.apache.geronimo.system.jmx.KernelDelegate.getGBeanInfo(KernelDele gate.java:616) [INFO] at org.apache.geronimo.kernel.basic.BasicProxyManager.getVisibleInterfac es(BasicProxyManager.java:123) [INFO] at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicP roxyManager.java:99) [INFO] at org.apache.geronimo.kernel.config.ConfigurationUtil.getConfigurationM anager(ConfigurationUtil.java:260) [INFO] at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.initia lize(JMXDeploymentManager.java:68) [INFO] at org.apache.geronimo.deployment.plugin.jmx.RemoteDeploymentManager.in it(RemoteDeploymentManager.java:73) [INFO] at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl .getDeploymentManager(DeploymentFactoryImpl.java:130) [INFO] at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.get DeploymentManager(DeploymentFactoryManager.java:109) [INFO] at org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.ge tDeploymentManager(ModuleMojoSupport.java:84) [INFO] at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.dis tribute(DeployModuleMojo.java:148) [INFO] at org.apache.geronimo.mavenplugins.geronimo.module.DeployModuleMojo.doE xecute
[jira] Created: (GERONIMO-2676) Web Application without required jars throws NullPointer
Web Application without required jars throws NullPointer Key: GERONIMO-2676 URL: http://issues.apache.org/jira/browse/GERONIMO-2676 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.0 Reporter: Krishnakumar B I have tried deploying applications like ActiveBPEL and MyFaces examples on geronimo. If i dont add the required jars for these application's to run i get a NullPointerException. The service J2EEApplication=null,j2eeType=WebModule,name=default/myfaces-examp le-simple-1.1.5-SNAPSHOT/1166707464231/war did not start because the doStart met hod threw an exception. java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.naming.resources.DirContextURLStreamHandler.bind(DirContex tURLStreamHandler.java:234) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppCo ntext.java:477) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:984) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:543) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:378) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke rnelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:527) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:508) at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla ssByCGLIB$$ce77a924.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5 7) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat ionInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro xyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan cerByCGLIB$$b42bfad1.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCom mand.java:67) at java.lang.Thread.run(Thread.java:595) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:407) ... 14 more A more user friendly exception will help the user to add the required jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2673) WARN message from Global JNDI
WARN message from Global JNDI - Key: GERONIMO-2673 URL: http://issues.apache.org/jira/browse/GERONIMO-2673 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: naming Affects Versions: 2.0-M2 Reporter: Krishnakumar B When stopping an application a WARN message and exception is thrown 14:43:57,265 WARN [BasicLifecycleMonitor] Exception occured while notifying listener java.lang.NullPointerException at org.apache.geronimo.gjndi.binding.GBeanBinding.removeBinding(GBeanBinding.java:159) at org.apache.geronimo.gjndi.binding.GBeanBinding$GBeanLifecycleListener.stopped(GBeanBinding.java:108) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppedEvent(BasicLifecycleMonitor.java:197) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$500(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppedEvent(BasicLifecycleMonitor.java:259) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:359) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:310) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.system.main.Daemon$1.run(Daemon.java:234) 14:43:57,275 WARN [BasicLifecycleMonitor] Exception occured while notifying listener java.lang.NullPointerException at org.apache.geronimo.gjndi.binding.GBeanBinding.removeBinding(GBeanBinding.java:159) at org.apache.geronimo.gjndi.binding.GBeanBinding$GBeanLifecycleListener.stopped(GBeanBinding.java:108) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppedEvent(BasicLifecycleMonitor.java:197) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$500(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppedEvent(BasicLifecycleMonitor.java:259) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:359) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop
Re: Error when deploying day trader - 2.0-M1-SNAPSHOT
2.0-M1-SNAPSHOT On 12/18/06, Matt Hogstrom [EMAIL PROTECTED] wrote: What Geronimo Version are you deploying against? On Dec 15, 2006, at 6:20 AM, Krishnakumar B wrote: I get a Nullpointer exception when deploying daytrader. I used the JPA plan to deploy the application. Tomcat error 16:26:22,715 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.daytrader/daytrader/2.0-SNAPSHOT/ car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.0- SNAPSHOT/car,j2eeType=WebModule,name=web.war java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.naming.resources.DirContextURLStreamHandler.bind (DirContextURLStreamHandler.java:234) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart (TomcatWebAppContext.java:477) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance (GBeanInstance.java:984) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart( GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start (GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start (GBeanInstance.java:529) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart (GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget (GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running (GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEven t(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access $300(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor $RawLifecycleBroadcaster.fireRunningEvent (BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart( GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start (GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive (GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive (GBeanInstance.java:543) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean (BasicKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration GBeans(ConfigurationUtil.java:378) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration GBeans(ConfigurationUtil.java:415) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start (KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf iguration(SimpleConfigurationManager.java:527) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf iguration(SimpleConfigurationManager.java:508) at org.apache.geronimo.kernel.config.SimpleConfigurationManager$ $FastClassByCGLIB$$ce77a924.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$ $EnhancerByCGLIB$$b42bfad1.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run (StartCommand.java:67) at java.lang.Thread.run(Thread.java:595) 16:26:22,965 WARN [TomcatWebAppContext] TomcatWebAppContext failed 16:26:22,965 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.daytrader/daytrader/2.0-SNAPSHOT/ car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.0- SNAPSHOT/car,j2eeType=WebModule,name=web.war java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.naming.resources.DirContextURLStreamHandler.bind (DirContextURLStreamHandler.java:234) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart (TomcatWebAppContext.java:477) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance (GBeanInstance.java:984) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart( GBeanInstanceState.java:267
Error when deploying day trader - 2.0-M1-SNAPSHOT
I get a Nullpointer exception when deploying daytrader. I used the JPA plan to deploy the application. Tomcat error 16:26:22,715 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.daytrader/daytrader/2.0-SNAPSHOT/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.0-SNAPSHOT/car,j2eeType=WebModule,name=web.war java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.naming.resources.DirContextURLStreamHandler.bind(DirContextURLStreamHandler.java:234) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:477) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:984) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:529) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:543) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:378) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:415) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508) at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$b42bfad1.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:595) 16:26:22,965 WARN [TomcatWebAppContext] TomcatWebAppContext failed 16:26:22,965 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.daytrader/daytrader/2.0-SNAPSHOT/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.0-SNAPSHOT/car,j2eeType=WebModule,name=web.war java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.naming.resources.DirContextURLStreamHandler.bind(DirContextURLStreamHandler.java:234) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:477) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:984) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at
Re: Servlet Filter error in 2.0-SNAPSHOT
https://issues.apache.org/jira/browse/GERONIMO-2664 On 12/14/06, Prasad Kashyap [EMAIL PROTECTED] wrote: Krish, please open a JIRA so that it can be tracked. Cheers Prasad On 12/14/06, David Jencks [EMAIL PROTECTED] wrote: On Dec 14, 2006, at 1:51 AM, Krishnakumar B wrote: Hi, I am trying out some features of servlet 2.5 spec. This is related to Servlet Filter. According to 2.5 spec servlet filter can be specified with a * instead of adding all servlets to the filter. filter-mapping filter-nameSample Filter/filter-name servlet-name*/servlet-name /filter-mapping This doesnt work but filter works if i bind servlets with multiple servlet names or url patterns filter-nameSample Filter/filter-name !--servlet-name*/servlet-name -- servlet-nameSampleServlet/servlet-name servlet-nameAnotherSampleServlet/servlet-name In jetty i get a exception while in tomcat the filter is not called at all The Jetty exception 14:21:50,780 ERROR [Deployer] Deployment failed due to java.lang.AssertionError: javax.management.MalformedObjectNameException: Invalid character `*' in value at org.apache.geronimo.kernel.Jsr77Naming.createObjectName (Jsr77Naming.java:112) at org.apache.geronimo.kernel.Jsr77Naming.createChildName (Jsr77Naming.java:80) at org.apache.geronimo.kernel.Jsr77Naming.createChildName (Jsr77Naming.java:54) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addFilterMapp ingsGBeans(JettyModuleBuilder.java:614) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans (JettyModuleBuilder.java:483) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder$ $FastClassByCGLIB$$1a00be84.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$ $EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans (SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$ $FastClassByCGLIB$$d0c31844.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$ $EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguratio n(EARConfigBuilder.java:572) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$ $FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$ $EnhancerByCGLIB$$c3a6b023.buildConfiguration(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:302) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$ $734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke
[jira] Created: (GERONIMO-2664) Servlet Filter Error
Servlet Filter Error Key: GERONIMO-2664 URL: http://issues.apache.org/jira/browse/GERONIMO-2664 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Jetty, Tomcat Affects Versions: 2.0-M1 Reporter: Krishnakumar B Trying out servlet name with a wild card ( * ) in Filter throws exception in Jetty. In tomcat the filter is not called at all filter-mapping filter-nameSample Filter/filter-name servlet-name*/servlet-name /filter-mapping instead of filter-nameSample Filter/filter-name !--servlet-name*/servlet-name -- servlet-nameSampleServlet/servlet-name servlet-nameAnotherSampleServlet/servlet-name Jetty 14:21:50,780 ERROR [Deployer] Deployment failed due to java.lang.AssertionError: javax.management.MalformedObjectNameException: Invalid character `*' in value at org.apache.geronimo.kernel.Jsr77Naming.createObjectName(Jsr77Naming.java:112) at org.apache.geronimo.kernel.Jsr77Naming.createChildName(Jsr77Naming.java:80) at org.apache.geronimo.kernel.Jsr77Naming.createChildName(Jsr77Naming.java:54) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addFilterMappingsGBeans(JettyModuleBuilder.java:614) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:483) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder$$FastClassByCGLIB$$1a00be84.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$$FastClassByCGLIB$$d0c31844.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:572) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$c3a6b023.buildConfiguration(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:302) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239
Servlet Filter error in 2.0-SNAPSHOT
Hi, I am trying out some features of servlet 2.5 spec. This is related to Servlet Filter. According to 2.5 spec servlet filter can be specified with a * instead of adding all servlets to the filter. filter-mapping filter-nameSample Filter/filter-name servlet-name*/servlet-name /filter-mapping This doesnt work but filter works if i bind servlets with multiple servlet names or url patterns filter-nameSample Filter/filter-name !--servlet-name*/servlet-name -- servlet-nameSampleServlet/servlet-name servlet-nameAnotherSampleServlet/servlet-name In jetty i get a exception while in tomcat the filter is not called at all The Jetty exception 14:21:50,780 ERROR [Deployer] Deployment failed due to java.lang.AssertionError: javax.management.MalformedObjectNameException: Invalid character `*' in value at org.apache.geronimo.kernel.Jsr77Naming.createObjectName(Jsr77Naming.java:112) at org.apache.geronimo.kernel.Jsr77Naming.createChildName(Jsr77Naming.java:80) at org.apache.geronimo.kernel.Jsr77Naming.createChildName(Jsr77Naming.java:54) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addFilterMappingsGBeans(JettyModuleBuilder.java:614) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:483) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder$$FastClassByCGLIB$$1a00be84.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$$FastClassByCGLIB$$d0c31844.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:572) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$c3a6b023.buildConfiguration(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:302) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:114) at
Re: JSP 2.1 with Jetty 6.0 and tomcat 6 distributions
Hi Jeff,
I have also tried this.
The web.xml
?xml version=1.0 encoding=UTF-8?
web-app xmlns=http://java.sun.com/xml/ns/javaee; version=2.5
metadata-complete=true
display-nameJSP 2.1/display-name
/web-app
This throws a jasper exception.
Regards
Krish
On 12/13/06, Jeff Genender [EMAIL PROTECTED] wrote:
Can you please show your header declaration for your web.xml?
Jeff
Anitha Krishnasamy wrote:
Hi,
Here is the snippet of the code, I have tried with JSP 2.1.
[EMAIL PROTECTED] trimDirectiveWhitespaces=true%
%@ taglib prefix=c uri= http://java.sun.com/jsp/jstl/core; %
%
java.util.ArrayList locations= new java.util.ArrayList();
locations.add(One);
locations.add(Two);
pageContext.setAttribute (locations, locations);
%
c:forEach var=location items=#{locations}
c:out value=#{location}/
/c:forEach
Also I have added the jstl.jar(1.2) in the WEB-INF\lib folder.But...It
throws the following error related to Expression language.
HTTP ERROR: 500
/SampleJSP.jsp(23,0) According to TLD or attribute directive in tag file,
attribute value does not accept any expressions
RequestURI=/SampleJSP/SampleJSP.jsp
Caused by:
org.apache.jasper.JasperException: /SampleJSP.jsp(23,0) According to TLD or
attribute directive in tag file, attribute value does not accept any expressions
at org.apache.jasper.compiler.DefaultErrorHandler.jspError
(DefaultErrorHandler.java:40)
at
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:406)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:147)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes
(Validator.java:1094)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:818)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit
(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
at org.apache.jasper.compiler.Node$CustomTag.accept
(Node.java:1507)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
at org.apache.jasper.compiler.Compiler.generateJava
(Compiler.java:178)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java
:273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
at org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java
:465)
at
org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.apache.geronimo.jetty6.JettyServletHandler.doHandle
(JettyServletHandler.java:55)
at
org.apache.geronimo.jetty6.JettyServletHandler$ActualJettyServletHandler.handle(JettyServletHandler.java:62)
at
org.apache.geronimo.jetty6.JettyServletHandler$NoOpChainedHandler.handle
(JettyServletHandler.java:70)
at
org.apache.geronimo.jetty6.JettyServletHandler.handle(JettyServletHandler.java:47)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
(ThreadClassloaderHandler.java:46)
at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java
:58)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:682)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:390)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:303)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:446)
at
[jira] Updated: (GERONIMO-2650) JSP 2.1 error in Jetty/Tomcat
[ http://issues.apache.org/jira/browse/GERONIMO-2650?page=all ]
Krishnakumar B updated GERONIMO-2650:
-
Attachment: SampleJSP.war
sample jsp-2.1 application
JSP 2.1 error in Jetty/Tomcat
-
Key: GERONIMO-2650
URL: http://issues.apache.org/jira/browse/GERONIMO-2650
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: web
Affects Versions: 2.0-M1
Reporter: Krishnakumar B
Attachments: SampleJSP.war
Deploying a web application with JSP 2.1 features throws error in Jetty and
Tomcat
On Tomcat 6:
---
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
org.apache.jasper.compiler.Node$Root.accept (Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
org.apache.jasper.JspCompilationContext.compile
(JspCompilationContext.java:566)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service (JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
On Jetty 6.0:
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
at org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
at org.apache.jasper.compiler.Compiler.generateJava (Compiler.java:178)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java :273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java :459)
at
org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.apache.geronimo.jetty6.JettyServletHandler.doHandle
(JettyServletHandler.java:55)
at
org.apache.geronimo.jetty6.JettyServletHandler$ActualJettyServletHandler.handle(JettyServletHandler.java:62)
at org.apache.geronimo.jetty6.JettyServletHandler$NoOpChainedHandler.handle
(JettyServletHandler.java:70)
at
org.apache.geronimo.jetty6.JettyServletHandler.handle(JettyServletHandler.java:47)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
(ThreadClassloaderHandler.java:46)
at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java
:58)
at org.mortbay.jetty.handler.ContextHandler.handle
[jira] Created: (GERONIMO-2650) JSP 2.1 error in Jetty/Tomcat
JSP 2.1 error in Jetty/Tomcat
-
Key: GERONIMO-2650
URL: http://issues.apache.org/jira/browse/GERONIMO-2650
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: web
Affects Versions: 2.0-M1
Reporter: Krishnakumar B
Deploying a web application with JSP 2.1 features throws error in Jetty and
Tomcat
On Tomcat 6:
---
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch (ErrorDispatcher.java:406)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
org.apache.jasper.compiler.Node$Root.accept (Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
org.apache.jasper.JspCompilationContext.compile
(JspCompilationContext.java:566)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service (JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
On Jetty 6.0:
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
at org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
at org.apache.jasper.compiler.Compiler.generateJava (Compiler.java:178)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java :273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java :459)
at
org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.apache.geronimo.jetty6.JettyServletHandler.doHandle
(JettyServletHandler.java:55)
at
org.apache.geronimo.jetty6.JettyServletHandler$ActualJettyServletHandler.handle(JettyServletHandler.java:62)
at org.apache.geronimo.jetty6.JettyServletHandler$NoOpChainedHandler.handle
(JettyServletHandler.java:70)
at
org.apache.geronimo.jetty6.JettyServletHandler.handle(JettyServletHandler.java:47)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
(ThreadClassloaderHandler.java:46)
at
org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
at
org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java
:58)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:389)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:303
Re: JSP 2.1 with Jetty 6.0 and tomcat 6 distributions
Opened the JIRA. Will attach a sample application with JSP 2.1 features soon.
(https://issues.apache.org/jira/browse/GERONIMO-2650)
Regards
Krish
On 12/8/06, Paul McMahan [EMAIL PROTECTED] wrote:
The jetty and tomcat JEE5 assemblies both use jasper for JSP so that
explains why you're seeing the error in both places. Looking at
org.apache.jaspler.compiler.Validator:705 I think I see where the
error occurs:
// JSP.2.2 - '#{' not allowed in template text
if (n.getType() == '#') {
if (!pageInfo.isDeferredSyntaxAllowedAsLiteral()
(tagInfo == null
|| ((tagInfo != null)
!tagInfo.getTagLibrary().getRequiredVersion().equals(2.0 {
err.jspError(n, jsp.error.el.template.deferred);
} else {
return;
}
}
As to whether or not that error condition is valid I'm not sure. I'm
particularly confused by the reference to JSP 2.2 in the comment, but
maybe that was a typo. If you don't mind could you please create a
JIRA for this?
Best wishes,
Paul
On 12/8/06, Anitha Krishnasamy [EMAIL PROTECTED] wrote:
Hi,
I have deployed the Sample applications for JEE5 on both Jetty 6.0 and
Tomcat 6 distributions.
Servlets 2.5 application is working fine on both. But JSP 2.1 application
throwing the following error.
On Tomcat 6:
---
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35)
#{..} is not allowed in template text
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
org.apache.jasper.compiler.Node$ELExpression.accept
(Node.java:935)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
org.apache.jasper.compiler.Node$Root.accept
(Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
org.apache.jasper.JspCompilationContext.compile
(JspCompilationContext.java:566)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service
(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
On Jetty 6.0:
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35)
#{..} is not allowed in template text
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
at org.apache.jasper.compiler.Node$ELExpression.accept
(Node.java:935)
at
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at
org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
at org.apache.jasper.compiler.Compiler.generateJava
(Compiler.java:178)
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java
:273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
at org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:320)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java
:459)
at
org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.apache.geronimo.jetty6.JettyServletHandler.doHandle
(JettyServletHandler.java:55)
at
[jira] Created: (GERONIMO-2651) Servlet annotations are not supported
Servlet annotations are not supported - Key: GERONIMO-2651 URL: http://issues.apache.org/jira/browse/GERONIMO-2651 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: web Affects Versions: 2.0-M1, 2.0-M2 Reporter: Krishnakumar B Servlet JEE5 annotations are not supported. ( I have tried @Resource in servlet to get reference to a datasource.) Not sure which release this is targetted at so adding it to 2.0-M1 2.0-M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Stack trace while shutting down amq in geronimo 2.0
I get this error when shutting down jee5-jetty6 jee5-tomcat
Regards
Krish
On 12/7/06, anita kulshreshtha [EMAIL PROTECTED] wrote:
This trace is produced by geronimo-framework. The trace is produced
when attributes of JavaCompContext (rmi-naming) are viewed by jconsole.
Thanks
Anita
[*] 100% 4s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
4242 0.0.0.0 Remote Login Listener
0.0.0.0 JMX Remoting Connector
Geronimo Application Server started
13:08:02,015 WARN [MBeanGBeanBridge] Exception while getting attribute
environment
javax.management.ReflectionException
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttribute(MBeanGBeanBridge.j
ava:122)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttributes(MBeanGBeanBridge.
java:143)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttributes(DynamicMetaDataImpl.j
ava:125)
at
com.sun.jmx.mbeanserver.MetaDataImpl.getAttributes(MetaDataImpl.java:189)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBea
nServerInterceptor.java:696)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:686)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.jav
a:1389)
at
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java
:81)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnec
tionImpl.java:1245)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnecti
onImpl.java:1348)
at
javax.management.remote.rmi.RMIConnectionImpl.getAttributes(RMIConnectionImpl.j
ava:633)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
org.apache.xbean.naming.context.ContextFlyweight.getEnvironment(ContextFlyweigh
t.java:144)
at
org.apache.xbean.naming.context.ContextFlyweight$$FastClassByCGLIB$$592f1945.in
voke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.ja
va:38)
at
org.apache.geronimo.gbean.runtime.GBeanAttribute.getValue(GBeanAttribute.java:3
90)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.getAttribute(GBeanInstance.java
:681)
at
org.apache.geronimo.kernel.basic.BasicKernel.getAttribute(BasicKernel.java:178)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttribute(MBeanGBeanBridge.j
ava:118)
... 22 more
--- anita kulshreshtha [EMAIL PROTECTED] wrote:
The shutdown of geronimo-tomcat-minimal server produces this
trace:
12:34:10,671 INFO [root]
--
12:38:32,171 WARN [BasicLifecycleMonitor] Exception occured while
notifying listener
java.lang.NullPointerException
at
org.apache.geronimo.gjndi.binding.GBeanBinding.removeBinding(GBeanBinding.java:159)
at
org.apache.geronimo.gjndi.binding.GBeanBinding$GBeanLifecycleListener.stopped(GBeanBinding.java:108)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppedEvent(BasicLifecycleMonitor.java:197)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$500(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppedEvent(BasicLifecycleMonitor.java:259)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:359)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
at
Unable to build jetty6 jee5 assembly
Hi, I am trying to build jetty6 assembly but it fails in modules-jetty6. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.mortbay.jetty:jetty:jar:6.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.mortbay.jetty -DartifactId=jetty \ -Dversion=6.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty6:jar:2.0-SNAPSHOT 2) org.mortbay.jetty:jetty:jar:6.1-SNAPSHOT I am not able to find jetty jar for 6.1-SNAPSHOT in the repos. Regards Krish
Re: Unable to build jetty6 jee5 assembly
Should jetty source be downloaded and built to get this jar. I tried jetty-6.1.0pre0.jar but it gives compilation errors during build of geronimo-jetty6 module. Regards Krish On 12/6/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, I am trying to build jetty6 assembly but it fails in modules-jetty6. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.mortbay.jetty:jetty:jar:6.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.mortbay.jetty -DartifactId=jetty \ -Dversion=6.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty6:jar:2.0-SNAPSHOT 2) org.mortbay.jetty:jetty:jar:6.1-SNAPSHOT I am not able to find jetty jar for 6.1-SNAPSHOT in the repos. Regards Krish
Error when building geronimo 2.0
hi, The build fails in jetty6 builder module with following error Time to build schema type system: 1.011 seconds BUILD FAILED [INFO] [ERROR] BUILD ERROR [INFO] [INFO] XmlBeans compile failed: xml ErrorLoading schema file C:\g20\modules\geronimo-jetty6-builder\src\main\sc hema\geronimo-jetty-1.2.xsd xml ErrorLoading schema file C:\g20\modules\geronimo-jetty6-builder\src\main\sch ema\geronimo-jetty-config-1.0.xsd xml ErrorLoading config file C:\g20\modules\geronimo-jetty6-builder\src\main\sch ema\xmlconfig.xml xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:32: error: java.io.FileNotFoundException: C:\g20\modules\geronimo-jetty6- builder\src\main\schema\geronimo-naming-1.2.xsd (The system cannot find the file specified) xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:34: error: java.io.FileNotFoundException: C:\g20\modules\geronimo-jetty6- builder\src\main\schema\geronimo-application-1.2.xsd (The system cannot find the file specified) xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:35: error: java.io.FileNotFoundException: C:\g20\modules\geronimo-jetty6- builder\src\main\schema\geronimo-module-1.2.xsd (The system cannot find the file specified) xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:42: error: src-resolve: element '[EMAIL PROTECTED]://geronimo.apache.org/x ml/ns/deployment-1.2' not found. xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:46: error: src-resolve: element '[EMAIL PROTECTED]://geronimo.apache.org/xm l/ns/j2ee/application-1.2' not found. xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:48: error: src-resolve: element '[EMAIL PROTECTED]://geronimo.apache.org /xml/ns/naming-1.2' not found. xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:54: error: src-resolve: model group '[EMAIL PROTECTED]://gero nimo.apache.org/xml/ns/naming-1.2' not found. xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:55: error: src-resolve: element '[EMAIL PROTECTED]://geronimo.apac he.org/xml/ns/naming-1.2' not found. xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:59: error: src-resolve: element '[EMAIL PROTECTED]://geronimo.apache.org/xml/ ns/j2ee/application-1.2' not found. xml ErrorC:\g20\modules\geronimo-jetty6-builder\src\main\schema\geronimo-jetty-1 .2.xsd:62: error: src-resolve: element '[EMAIL PROTECTED]://geronimo.apache.org/xml/n s/deployment-1.2' not found. Regards Krish
Re: Query related to test framework
hi Prasad, Thanks. Another query. How to get the testsuites to use a tomcat assembly? It always picks jetty assembly by default to run the tests. Regards Krish On 11/30/06, Prasad Kashyap [EMAIL PROTECTED] wrote: Hi Krishna, You are not limited to the browser (console) related tests. You can test almost anything as long as the tests are written in JUnit or TestNG. Hopefully soon, we should be able to drop the ejbcontainer-testsuite into it. You will see that this will not have anything to do with the browser. Cheers Prasad On 11/30/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, I am trying to understand how the test framework works and what kind of integration test scenarios can be covered using the test suite. I have some doubts that may sound stupid and they are listed below. * Can this be used only for browser(console) related tests. * What kind of functionality can i test using the suite. Is it components like deployment, console only or other features in the server like SSO, Virtual hosts, Database Pools etc. ( For e.g - If i want to test SSO can i write a test case and use a suitable app with the test suite to check all options in SSO) Regards Krish
Re: testsuite not running
Thanks. It works when i installed FireFox. It doesnt work with IE
Regards
Krish
On 11/30/06, Prasad Kashyap [EMAIL PROTECTED] wrote:
Hi Krishna,
I have seen this happen when I had a very old version of Firefox on my
machine. I upgraded to version 1.5.0.8 and now it works.
Cheers,
Prasad
On 11/30/06, Krishnakumar B [EMAIL PROTECTED] wrote:
Hi,
I tried running the testsuite following the instructions from cWiki.
The tests stop and do not run after the message Running deployment
or Running console. I have checked out trunk and built the server assemblies.
rt\test-ear-j2ee_1.4\2.0-SNAPSHOT\test-ear-j2ee_1.4-2.0-SNAPSHOT.ear with
plan n
ull
[INFO] [INFO] Starting modules...
[INFO] [INFO] Starting module:
org.apache.geronimo.testsupport/test-ear-j2ee_1.3
/2.0-SNAPSHOT/ear
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0]
org.apache.geronimo.testsupport/test-ear-j2ee_1.3/2.0-SNAP
SHOT/ear
[INFO] [INFO] Starting module:
org.apache.geronimo.testsupport/test-ear-j2ee_1.4
/2.0-SNAPSHOT/ear
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0]
org.apache.geronimo.testsupport/test-ear-j2ee_1.4/2.0-SNAP
SHOT/ear
[INFO] [INFO] [surefire:test {execution: integration}]
[INFO] [INFO] Surefire report directory:
C:\g20\testsuite\deployment-testsuite\t
est-deployments\target\surefire-reports
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running deployment
Regards
Krish
testsuite not running
Hi,
I tried running the testsuite following the instructions from cWiki.
The tests stop and do not run after the message Running deployment
or Running console. I have checked out trunk and built the server assemblies.
rt\test-ear-j2ee_1.4\2.0-SNAPSHOT\test-ear-j2ee_1.4-2.0-SNAPSHOT.ear with plan n
ull
[INFO] [INFO] Starting modules...
[INFO] [INFO] Starting module: org.apache.geronimo.testsupport/test-ear-j2ee_1.3
/2.0-SNAPSHOT/ear
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0] org.apache.geronimo.testsupport/test-ear-j2ee_1.3/2.0-SNAP
SHOT/ear
[INFO] [INFO] Starting module: org.apache.geronimo.testsupport/test-ear-j2ee_1.4
/2.0-SNAPSHOT/ear
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0] org.apache.geronimo.testsupport/test-ear-j2ee_1.4/2.0-SNAP
SHOT/ear
[INFO] [INFO] [surefire:test {execution: integration}]
[INFO] [INFO] Surefire report directory: C:\g20\testsuite\deployment-testsuite\t
est-deployments\target\surefire-reports
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running deployment
Regards
Krish
1.2 SNAPSHOT build error
I get an error in configs rmi-naming while building 1.2-SNAPSHOT geronimo. [INFO] [car:package] [INFO] Packaging module configuration: C:\g12\configs\rmi-naming\target\plan\pla n.xml [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Unable to create configuration for deployment org.apache.geronimo.gbean.GBeanInfo; local class incompatible: stream classdesc serialVersionUID = 1053655034244747613, local class serialVersionUID = -61988040 6710221 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] I tried clean, install of modules and then did clean,install of configs. Any help in fixing this. regards Krish
Re: 1.2 SNAPSHOT build error
hi Gianny, Thanks. It works after i delete the configs. Regards Krish On 11/23/06, Gianny Damour [EMAIL PROTECTED] wrote: Hi Krish, You have in your m2 repository a 1.2-SNAPSHOT config, which needs to be cleaned: basically, if you delete the directory org/apache/ geronimo/configs from your m2 repository you should be able to build successfully. In more details, during a couple of days, there was a GBeanInfo having the SUID 1053655034244747613. In order to keep backward compatibility with G1.1.1 having the SUID -619880406710221, we set the SUID back to -619880406710221. Some configurations based on the GBeanInfo having the SUID 1053655034244747613 are in your local m2 repository and they cannot be loaded. Thanks, Gianny On 23/11/2006, at 9:19 PM, Krishnakumar B wrote: I get an error in configs rmi-naming while building 1.2-SNAPSHOT geronimo. [INFO] [car:package] [INFO] Packaging module configuration: C:\g12\configs\rmi-naming \target\plan\pla n.xml [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Unable to create configuration for deployment org.apache.geronimo.gbean.GBeanInfo; local class incompatible: stream classdesc serialVersionUID = 1053655034244747613, local class serialVersionUID = -61988040 6710221 [INFO] -- -- [INFO] For more information, run Maven with the -e switch [INFO] -- -- I tried clean, install of modules and then did clean,install of configs. Any help in fixing this. regards Krish
Unable to start server 1.2-SNAPSHOT
I did a build of 1.2-SNAPSHOT successfully. Starting tomcat assembly fails with the following error. I am using Sun JDK 1.5 Booting Geronimo Kernel (in Java 1.5.0_09)... 11:47:58,106 ERROR [GBeanInstanceState] Error while starting; GBean is now in th e FAILED state: abstractName=org.apache.geronimo.configs/j2ee-system/1.2-SNAPSH OT/car?configurationName=org.apache.geronimo.configs/j2ee-system/1.2-SNAPSHOT/ca r org.apache.geronimo.kernel.config.InvalidConfigException: Unable to deserialize GBeanState at org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans(Ser ializedGBeanState.java:120) at org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans(Seri alizedGBeanState.java:65) at org.apache.geronimo.kernel.config.ConfigurationData.getGBeans(Configu rationData.java:171) at org.apache.geronimo.kernel.config.Configuration.init(Configuration. java:277) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct orAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC onstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:936) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.j ava:529) at org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.j ava:361) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:150) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:126) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) Caused by: java.lang.ClassCastException: java.lang.Integer at org.apache.geronimo.gbean.GBeanData.readExternal(GBeanData.java:224) at org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans(Ser ializedGBeanState.java:111) ... 17 more [ ] 0% 1s Startup failed java.lang.IllegalStateException: GBean is not running: org.apache.geronimo.confi gs/j2ee-system/1.2-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/j2 ee-system/1.2-SNAPSHOT/car at org.apache.geronimo.kernel.basic.BasicKernel.getGBean(BasicKernel.jav a:304) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:152) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:126) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) java.lang.IllegalStateException: GBean is not running: org.apache.geronimo.confi gs/j2ee-system/1.2-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/j2 ee-system/1.2-SNAPSHOT/car at org.apache.geronimo.kernel.basic.BasicKernel.getGBean(BasicKernel.jav a:304) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:152) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConf iguration(ConfigurationUtil.java:126) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:242) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) Server shutdown begun Server shutdown completed Regards Krishnakumar
Re: Issues with Scout in Geronimo
Hi Jason, There is a 0.7-RC1 release available http://www.apache.org/dist/ws/scout/0_7rc1/binaries/ Regards Krish On 11/3/06, Jason Dillon [EMAIL PROTECTED] wrote: Sweet! Is there a release (or snapshot) artifact somewhere? I took a brief look and did not find anything. --jason On Nov 3, 2006, at 10:18 AM, Davanum Srinivas wrote: Yes! -- dims On 11/3/06, Jason Dillon [EMAIL PROTECTED] wrote: Does the new version fix their log4j.properties to not enable log4j.debug? --jason On Nov 3, 2006, at 5:25 AM, Krishnakumar B wrote: I have been trying to use JAXR for doing registry operations in jUDDI that comes with geronimo. The version of Scout in geronimo 1.1.1 scout-0.5.jar seems to have issues related to ServiceBinding. These are reported as JIRA issues in Scout and are fixed in 0.7-RC1 version of Scout. https://issues.apache.org/jira/browse/SCOUT-22 https://issues.apache.org/jira/browse/SCOUT-10 As some basic operations do not work with Scout need to use UDDI4J for registry operations in Geronimo. Is there some plan to upgrade the version of Scout in Geronimo? Regards Krish -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
Issues with Scout in Geronimo
I have been trying to use JAXR for doing registry operations in jUDDI that comes with geronimo. The version of Scout in geronimo 1.1.1 scout-0.5.jar seems to have issues related to ServiceBinding. These are reported as JIRA issues in Scout and are fixed in 0.7-RC1 version of Scout. https://issues.apache.org/jira/browse/SCOUT-22 https://issues.apache.org/jira/browse/SCOUT-10 As some basic operations do not work with Scout need to use UDDI4J for registry operations in Geronimo. Is there some plan to upgrade the version of Scout in Geronimo? Regards Krish
Re: [ANNOUNCE] Please welcome Vamsavardhana Reddy as one of our newest Committer
Congrats Vamsi. Regards Krish On 10/19/06, John Sisson [EMAIL PROTECTED] wrote: Congratulations Vamsi! Regards, John Alan Cabrera wrote: The Geronimo PMC is pleased to announce that Vamsavardhana Reddy has recently accepted our invitation to become an Apache Geronimo Committer. Vamsi has been submitting many great patches for an embarrassing long time. The breadth of his patches is remarkable but we are excited by the possibility of him working on security. Congratulations and welcome Vamsi! Regards, Alan -- Apache Geronimo - http://geronimo.apache.org Apache Yoko - http://incubator.apache.org/yoko LiveTribe - http://www.livetribe.org
creating a dev environment in eclipse
Hi, I did a eclipse build using m2. I have imported the projects into eclipse. I get errors for XMLBeans related classes ( schemaorg_apache_xmlbeans.system.s0B3316F73CD7FBB57F083731B55F55A3 cannot be resolved ). In m1 i used to do a rebuild to get these classes. What's the equivalent in m2. Regards Krish
Build errors in Building Geronimo Applications, Console :: Standard Portlets
Hi,
When i do a build i get errors here
[INFO] -
---
[INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install]
[INFO] -
---
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
Downloading: file://C:\Apache\geronimo-1.2\applications\console\geronimo-console
-standard/repository/dwr/dwr/1.1.1/dwr-1.1.1.pom
[WARNING] Unable to get resource from repository module-local (file://C:\Apache\
geronimo-1.2\applications\console\geronimo-console-standard/repository)
Downloading: http://repository.codehaus.org/dwr/dwr/1.1.1/dwr-1.1.1.pom
[WARNING] Unable to get resource from repository codehaus (http://repository.cod
ehaus.org)
Downloading: http://repo1.maven.org/maven2/dwr/dwr/1.1.1/dwr-1.1.1.pom
[WARNING] Unable to get resource from repository central (http://repo1.maven.org
/maven2)
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\normal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp
[INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp
[INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j
sp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addmaximized.
jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\help.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\derby\groups\normal.jsp
[INFO] Built File: \WEB-INF\view\repository\help.jsp
[INFO] Built File: \WEB-INF\view\repository\normal.jsp
[INFO] Built File: \WEB-INF\view\realmwizard\advanced.jsp
[INFO] Built File:
Re: Build errors in Building Geronimo Applications, Console :: Standard Portlets
hi,
I was able to build by checking our source into a directory with short
name C:\g12 and maven repo in C:\.m2
Regards
Krishnakumar
On 10/10/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote:
Hi Krishnakumar,
This is a problem happens when you are building ignoring test cases I
think. I am having the same problem for quite a while. I am wondering
how can I fixed this problem too.
Thanks,
Lasantha Ranaweera
Krishnakumar B wrote:
Hi,
When i do a build i get errors here
[INFO]
-
---
[INFO] Building Geronimo Applications, Console :: Standard Portlets
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
Downloading:
file://C:\Apache\geronimo-1.2\applications\console\geronimo-console
-standard/repository/dwr/dwr/1.1.1/dwr-1.1.1.pom
[WARNING] Unable to get resource from repository module-local
(file://C:\Apache\
geronimo-1.2\applications\console\geronimo-console-standard/repository)
Downloading: http://repository.codehaus.org/dwr/dwr/1.1.1/dwr-1.1.1.pom
[WARNING] Unable to get resource from repository codehaus
(http://repository.cod
ehaus.org)
Downloading: http://repo1.maven.org/maven2/dwr/dwr/1.1.1/dwr-1.1.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org
/maven2)
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[WARNING] POM for 'org.apache.pluto:pluto:pom:1.0.1:compile' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'tranql:tranql:pom:1.4-SNAPSHOT:provided' is
invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[INFO] [jspc:compile {execution: jspc}]
[INFO] Built File: \WEB-INF\view\welcome\welcomeHelp.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeMaximized.jsp
[INFO] Built File: \WEB-INF\view\welcome\welcomeNormal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\normal.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTP.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\editHTTPS.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\help.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\maximized.jsp
[INFO] Built File: \WEB-INF\view\webmanager\connector\normal.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\help.jsp
[INFO] Built File: \WEB-INF\view\webaccesslogmanager\view.jsp
[INFO] Built File: \WEB-INF\view\threads\list.jsp
[INFO] Built File: \WEB-INF\view\threads\monitor.jsp
[INFO] Built File: \WEB-INF\view\servermanager\help.jsp
[INFO] Built File: \WEB-INF\view\servermanager\normal.jsp
[INFO] Built File: \WEB-INF\view\servermanager\shutdown.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\users\maximized.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addmaximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\addnormal.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\error.jsp
[INFO] Built File: \WEB-INF\view\securityrealmmanager\se\groups\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\se\groups\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addmaximized.j
sp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\addnormal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\error.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\help.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\maximized.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\users\normal.jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager\derby\groups\addmaximized.
jsp
[INFO] Built File:
\WEB-INF\view\securityrealmmanager
Re: Geronimo jee5 webservices integration
hi David, I would also be glad to make some contributions. I am new to this so would need some pointers as to what to focus on. I would start by reading the specs and also getting familiar with Axis 2. Regards Krishnakumar On 10/5/06, Manu George [EMAIL PROTECTED] wrote: Hi David, Count me in. I am willing to help in this. Will start reading the specs as my knowlege in this is limited. This page cleared some of my questions on why axis/celtix is required. Probably it will be useful for others who are new and interested http://cwiki.apache.org/GMOxPMGT/geronimo-jee-50-report-card.html Thanks Manu On 9/30/06, David Jencks [EMAIL PROTECTED] wrote: On Sep 29, 2006, at 9:33 PM, [EMAIL PROTECTED] wrote: Hi David, Can you please explain what is the meaning of jee5 web services? Any introduction link would be great. I'm just starting to read the specs: the ones I have found so far are jax-ws, jaxb, and jsr109 rev 1.2 (enterprise web services). So far it looks like things may be a little simpler than for j2ee 1.4 web services since we don't have to deal with the jaxrpc-mapping file, apparently jaxb mapping specifications deal with these issues in a better way. Hope this helps, david jencks Thanks, Lasantha Ranaweera I'm starting to look into jee5 webservices integration in geronimo. So far I've got as far as locating some of the specs and starting to read them :-). If anyone wants to help or take over aspects of this that would be great! Unfortunately I haven't been able to keep up with the dev lists for either axis or cxf so I'm not sure whether anyone has thought about this before nor how much of the appropriate specs are implemented already by either project. I have been pointed to a cxf geronimo builder, but haven't determined how out of date it is, as there have been quite a few builder changes in geronimo since the builder was written. Thanks! david jencks
Build error
hi, I get this error during build [INFO] Packaging module configuration: C:\Apache\geronimo-1.2\configs\client-cor ba-yoko\target\plan\plan.xml [INFO] [ERROR] BUILD ERROR [INFO] [INFO] No reference named configAdapter in gbean org.apache.geronimo.configs/cli ent-corba-yoko/1.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/client -corba-yoko/1.2-SNAPSHOT/car,j2eeType=CORBANameService,name=NameServerRef [INFO] [INFO] For more information, run Maven with the -e switch I ran bootstrap clean specs modules openejb2 assemble with SUN JDK 1.4.2 I followed the steps listed in cWiki ( http://cwiki.apache.org/GMOxDEV/building-apache-geronimo-with-maven-2.html) Any help in fixing this... Regards Krishnakumar
Re: [ANNOUNCE] Welcome Hernan Cunico as the newest member of the Geronimo PMC
Congrats Hernan. Regards Krishnakumar On 9/13/06, Alan D. Cabrera [EMAIL PROTECTED] wrote: Congrats Hernan! Regards, Alan On Sep 11, 2006, at 7:08 AM, Kevan Miller wrote: All, The Geronimo PMC is pleased to welcome Hernan Cunico as the newest member of the Geronimo PMC. We're very happy to have Hernan joining us to help with the oversight of the Geronimo project. Well done, Hernan! The Apache Geronimo PMC --kevan
[jira] Updated: (GERONIMO-2343) tomcat does not use maxPostSize set in config.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2343?page=all ]
Krishnakumar B updated GERONIMO-2343:
-
Affects Version/s: 1.1.1
tomcat does not use maxPostSize set in config.xml
-
Key: GERONIMO-2343
URL: http://issues.apache.org/jira/browse/GERONIMO-2343
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 1.1.1, 1.1.x, 1.1.2
Reporter: Krishnakumar B
Attachments: tomcat-maxPostSize.patch
I set a value for maxPostSize in config.xml
gbean name=TomcatWebConnector
attribute name=host0.0.0.0/attribute
attribute name=port8080/attribute
attribute name=redirectPort8443/attribute
attribute name=bufferSizeBytes2048/attribute
attribute name=maxThreads150/attribute
attribute name=acceptQueueSize100/attribute
attribute name=lingerMillis-1/attribute
attribute name=tcpNoDelaytrue/attribute
attribute name=minSpareThreads25/attribute
attribute name=maxSpareThreads75/attribute
attribute name=maxHttpHeaderSizeBytes8192/attribute
attribute name=hostLookupEnabledfalse/attribute
attribute name=connectionTimeoutMillis2/attribute
attribute name=uploadTimeoutEnabledfalse/attribute
attribute name=maxPostSize20/attribute
attribute name=maxSavePostSize4096/attribute
attribute name=emptySessionPathfalse/attribute
/gbean
Tomcat Connector uses the value set in Connector to check for POST size.
if (len 0) {
int maxPostSize = connector.getMaxPostSize();
if ((maxPostSize 0) (len maxPostSize)) {
context.getLogger().info
(sm.getString(coyoteRequest.postTooLarge));
throw new IllegalStateException(Post too large);
}
While in Connector GBean setAttribute does not set in Connector
connector.setAttribute(maxPostSize, new Integer(bytes));
This is set in hashtable in HTTP11Protocol Handler. As a result the default
value is maintained in connector ( 2097152 )
This fix uses setter method in connector to set this value. (
connector.setMaxPostSize(bytes) )
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2343) tomcat does not use maxPostSize set in config.xml
tomcat does not use maxPostSize set in config.xml
-
Key: GERONIMO-2343
URL: http://issues.apache.org/jira/browse/GERONIMO-2343
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Tomcat
Affects Versions: 1.1.2, 1.1.x
Reporter: Krishnakumar B
Attachments: tomcat-maxPostSize.patch
I set a value for maxPostSize in config.xml
gbean name=TomcatWebConnector
attribute name=host0.0.0.0/attribute
attribute name=port8080/attribute
attribute name=redirectPort8443/attribute
attribute name=bufferSizeBytes2048/attribute
attribute name=maxThreads150/attribute
attribute name=acceptQueueSize100/attribute
attribute name=lingerMillis-1/attribute
attribute name=tcpNoDelaytrue/attribute
attribute name=minSpareThreads25/attribute
attribute name=maxSpareThreads75/attribute
attribute name=maxHttpHeaderSizeBytes8192/attribute
attribute name=hostLookupEnabledfalse/attribute
attribute name=connectionTimeoutMillis2/attribute
attribute name=uploadTimeoutEnabledfalse/attribute
attribute name=maxPostSize20/attribute
attribute name=maxSavePostSize4096/attribute
attribute name=emptySessionPathfalse/attribute
/gbean
Tomcat Connector uses the value set in Connector to check for POST size.
if (len 0) {
int maxPostSize = connector.getMaxPostSize();
if ((maxPostSize 0) (len maxPostSize)) {
context.getLogger().info
(sm.getString(coyoteRequest.postTooLarge));
throw new IllegalStateException(Post too large);
}
While in Connector GBean setAttribute does not set in Connector
connector.setAttribute(maxPostSize, new Integer(bytes));
This is set in hashtable in HTTP11Protocol Handler. As a result the default
value is maintained in connector ( 2097152 )
This fix uses setter method in connector to set this value. (
connector.setMaxPostSize(bytes) )
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2343) tomcat does not use maxPostSize set in config.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2343?page=all ]
Krishnakumar B updated GERONIMO-2343:
-
Attachment: tomcat-maxPostSize.patch
tomcat does not use maxPostSize set in config.xml
-
Key: GERONIMO-2343
URL: http://issues.apache.org/jira/browse/GERONIMO-2343
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 1.1.2, 1.1.x
Reporter: Krishnakumar B
Attachments: tomcat-maxPostSize.patch
I set a value for maxPostSize in config.xml
gbean name=TomcatWebConnector
attribute name=host0.0.0.0/attribute
attribute name=port8080/attribute
attribute name=redirectPort8443/attribute
attribute name=bufferSizeBytes2048/attribute
attribute name=maxThreads150/attribute
attribute name=acceptQueueSize100/attribute
attribute name=lingerMillis-1/attribute
attribute name=tcpNoDelaytrue/attribute
attribute name=minSpareThreads25/attribute
attribute name=maxSpareThreads75/attribute
attribute name=maxHttpHeaderSizeBytes8192/attribute
attribute name=hostLookupEnabledfalse/attribute
attribute name=connectionTimeoutMillis2/attribute
attribute name=uploadTimeoutEnabledfalse/attribute
attribute name=maxPostSize20/attribute
attribute name=maxSavePostSize4096/attribute
attribute name=emptySessionPathfalse/attribute
/gbean
Tomcat Connector uses the value set in Connector to check for POST size.
if (len 0) {
int maxPostSize = connector.getMaxPostSize();
if ((maxPostSize 0) (len maxPostSize)) {
context.getLogger().info
(sm.getString(coyoteRequest.postTooLarge));
throw new IllegalStateException(Post too large);
}
While in Connector GBean setAttribute does not set in Connector
connector.setAttribute(maxPostSize, new Integer(bytes));
This is set in hashtable in HTTP11Protocol Handler. As a result the default
value is maintained in connector ( 2097152 )
This fix uses setter method in connector to set this value. (
connector.setMaxPostSize(bytes) )
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2312) Create a New JMS Group throws error for external RAR
[ http://issues.apache.org/jira/browse/GERONIMO-2312?page=comments#action_12428362 ] Krishnakumar B commented on GERONIMO-2312: -- Create a new JMS Group deploys successfully if there is no geronimo-ra plan bundled with RA. This is expected behavior. Hence instead of showing a wrong plan if geronimo-ra is bundled with RA it can either be ignored or a error message can be thrown to remove the plan from RA. Create a New JMS Group throws error for external RAR Key: GERONIMO-2312 URL: http://issues.apache.org/jira/browse/GERONIMO-2312 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Krishnakumar B Attachments: GERJMSRAR.rar I deployed a JMS RAR using Deploy new and it is deployed. I tried to create a New JMS Group using the console wizard. When i see the deployment plan it doesnt seem right and i get a deployment error when i deploy this plan. The plan looks like this : connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.1; environment moduleId groupIdtest/groupId artifactIdjms.rar/artifactId version1.0/version /moduleId dependencies .. /dependencies /environment dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:moduleId dep:groupIdconsole.jms/dep:groupId dep:artifactIdTestJMSRA/dep:artifactId dep:version1.0/dep:version dep:typerar/dep:type /dep:moduleId /dep:environment resourceadapter resourceadapter-instance resourceadapter-nameTestJMSRA/resourceadapter-name workmanager gbean-linkDefaultWorkManager/gbean-link /workmanager nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance . Clearly the deployment plan generated is not correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2316) Unable to create a new Active IO listener from console
Unable to create a new Active IO listener from console -- Key: GERONIMO-2316 URL: http://issues.apache.org/jira/browse/GERONIMO-2316 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 1.2 Environment: Geronimo 1.1 Reporter: Krishnakumar B I get the following exception when i create a New Active IO Listener from console 12:46:13,784 ERROR [JMSConnectorPortlet] Unable to process portlet action java.lang.NoSuchMethodError: org.activeio.ChannelFactory.bindAsynchChannel(Ljava/net/URI;)Lorg/activeio/AsynchChannelServer; at org.activemq.transport.activeio.ActiveIOTransportServerChannelFactory.createAsynchChannelServer(ActiveIOTransportServerChannelFactory.java:60) at org.activemq.transport.activeio.ActiveIOTransportServerChannelFactory.create(ActiveIOTransportServerChannelFactory.java:49) at org.activemq.transport.TransportServerChannelProvider.create(TransportServerChannelProvider.java:45) at org.activemq.broker.impl.BrokerConnectorImpl.createTransportServerChannel(BrokerConnectorImpl.java:425) at org.activemq.broker.impl.BrokerConnectorImpl.init(BrokerConnectorImpl.java:69) at org.activemq.gbean.ActiveMQConnectorGBean.createBrokerConnector(ActiveMQConnectorGBean.java:160) at org.activemq.gbean.ActiveMQConnectorGBean.doStart(ActiveMQConnectorGBean.java:128) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.gbean.ActiveMQConnector$$EnhancerByCGLIB$$c6a55a11.startRecursive(generated) at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.processAction(JMSConnectorPortlet.java:104) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:342) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke
[jira] Created: (GERONIMO-2317) Unable to create a new peer listener from console
Unable to create a new peer listener from console - Key: GERONIMO-2317 URL: http://issues.apache.org/jira/browse/GERONIMO-2317 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 1.2 Environment: Geronimo 1.1 Reporter: Krishnakumar B I get the following exception when i create a new peer listener from console 12:48:47,655 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/activemq-broker/1.1/car?JMSServer=ActiveMQ,ServiceModule=geronimo/activemq-broker/1.1/car,j2eeType=GBean,name=NewPeer javax.jms.JMSException: Could not load protocol: peer. Reason: java.lang.ClassNotFoundException: org.activemq.transport.peer.PeerTransportServerChannelFactory in classloader geronimo/activemq-broker/1.1/car at org.activemq.transport.TransportServerChannelProvider.createJMSexception(TransportServerChannelProvider.java:85) at org.activemq.transport.TransportServerChannelProvider.getFactory(TransportServerChannelProvider.java:79) at org.activemq.transport.TransportServerChannelProvider.create(TransportServerChannelProvider.java:45) at org.activemq.broker.impl.BrokerConnectorImpl.createTransportServerChannel(BrokerConnectorImpl.java:425) at org.activemq.broker.impl.BrokerConnectorImpl.init(BrokerConnectorImpl.java:69) at org.activemq.gbean.ActiveMQConnectorGBean.createBrokerConnector(ActiveMQConnectorGBean.java:160) at org.activemq.gbean.ActiveMQConnectorGBean.doStart(ActiveMQConnectorGBean.java:128) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.gbean.ActiveMQConnector$$EnhancerByCGLIB$$c6a55a11.startRecursive(generated) at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.processAction(JMSConnectorPortlet.java:104) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524
[jira] Updated: (GERONIMO-2317) Unable to create a new peer listener from console
[ http://issues.apache.org/jira/browse/GERONIMO-2317?page=all ] Krishnakumar B updated GERONIMO-2317: - Component/s: console Unable to create a new peer listener from console - Key: GERONIMO-2317 URL: http://issues.apache.org/jira/browse/GERONIMO-2317 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, console Affects Versions: 1.2 Environment: Geronimo 1.1 Reporter: Krishnakumar B I get the following exception when i create a new peer listener from console 12:48:47,655 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/activemq-broker/1.1/car?JMSServer=ActiveMQ,ServiceModule=geronimo/activemq-broker/1.1/car,j2eeType=GBean,name=NewPeer javax.jms.JMSException: Could not load protocol: peer. Reason: java.lang.ClassNotFoundException: org.activemq.transport.peer.PeerTransportServerChannelFactory in classloader geronimo/activemq-broker/1.1/car at org.activemq.transport.TransportServerChannelProvider.createJMSexception(TransportServerChannelProvider.java:85) at org.activemq.transport.TransportServerChannelProvider.getFactory(TransportServerChannelProvider.java:79) at org.activemq.transport.TransportServerChannelProvider.create(TransportServerChannelProvider.java:45) at org.activemq.broker.impl.BrokerConnectorImpl.createTransportServerChannel(BrokerConnectorImpl.java:425) at org.activemq.broker.impl.BrokerConnectorImpl.init(BrokerConnectorImpl.java:69) at org.activemq.gbean.ActiveMQConnectorGBean.createBrokerConnector(ActiveMQConnectorGBean.java:160) at org.activemq.gbean.ActiveMQConnectorGBean.doStart(ActiveMQConnectorGBean.java:128) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.gbean.ActiveMQConnector$$EnhancerByCGLIB$$c6a55a11.startRecursive(generated) at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.processAction(JMSConnectorPortlet.java:104) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178
[jira] Created: (GERONIMO-2319) Unable to create a new OpenWire Listener from console
Unable to create a new OpenWire Listener from console - Key: GERONIMO-2319 URL: http://issues.apache.org/jira/browse/GERONIMO-2319 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ, console Affects Versions: 1.2 Environment: Geronimo 1.1 Reporter: Krishnakumar B I am unable to create a new openwire listener from console. I get the following exception 12:51:25,081 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/activemq-broker/1.1/car?JMSServer=ActiveMQ,ServiceModule=geronimo/activemq-broker/1.1/car,j2eeType=GBean,name=NewOpenWire javax.jms.JMSException: Could not load protocol: openwire. Reason: java.lang.ClassNotFoundException: org.activemq.transport.openwire.OpenWireTransportServerChannelFactory in classloader geronimo/activemq-broker/1.1/car at org.activemq.transport.TransportServerChannelProvider.createJMSexception(TransportServerChannelProvider.java:85) at org.activemq.transport.TransportServerChannelProvider.getFactory(TransportServerChannelProvider.java:79) at org.activemq.transport.TransportServerChannelProvider.create(TransportServerChannelProvider.java:45) at org.activemq.broker.impl.BrokerConnectorImpl.createTransportServerChannel(BrokerConnectorImpl.java:425) at org.activemq.broker.impl.BrokerConnectorImpl.init(BrokerConnectorImpl.java:69) at org.activemq.gbean.ActiveMQConnectorGBean.createBrokerConnector(ActiveMQConnectorGBean.java:160) at org.activemq.gbean.ActiveMQConnectorGBean.doStart(ActiveMQConnectorGBean.java:128) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.gbean.ActiveMQConnector$$EnhancerByCGLIB$$c6a55a11.startRecursive(generated) at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.processAction(JMSConnectorPortlet.java:83) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java
Re: How to resolve JMS Dependency ?
Hi Manish, your web.xml has resource-ref res-ref-namejms/AcevaPublisherQueue/res-ref-name res-typejavax.jms.Queue/res-type res-authContainer/res-auth /resource-ref change it to resource-env-ref resource-env-ref-namejms/AcevaPublisherQueue/resource-env-ref-name resource-env-ref-typejavax.jms.Queue/resource-env-ref-type res-authContainer/res-auth /resource-env-ref and have the following type in your geronimo-web.xml nam:resource-env-ref nam:ref-namejms/AcevaPublisherQueue/nam:ref-name nam:message-destination-linkjms/AcevaPublisherQueue/nam:message-destination-link /nam:resource-env-ref Ur web.xml has !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; so its in J2EE 1.3 sysntax. I tried the ra plan u have posted and created a reference to AcevaPublisherQueue from a sample web application and it works. Regards Krishnakumar On 8/10/06, Manish Satwani [EMAIL PROTECTED] wrote: attaching modified geronimo-web.xml and openejb-jar.xml in which i have added admin-object-link Thanks Manish On 8/10/06, Manish Satwani [EMAIL PROTECTED] wrote: Hi All, I am stillg getting this erro during deployment. Unable to resolve resource reference 'jms/AcevaPublisherQueue' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan.) org.apache.geronimo.common.DeploymentException: Unable to resolve resource reference 'jms/AcevaPublisherQueue' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan.) at org.apache.geronimo.naming.deployment.ENCConfigBuilder.addResourceRefs(ENCConfigBuilder.java:210) I have added admin-object-link as suggested by Aaron. I am attching my web.xml also...and whole RA plan... please do let me know if you need any other configuration filefor reference... please help me ... Thanks Manish On 8/8/06, Aaron Mulder [EMAIL PROTECTED] wrote: OK, let's back up a bit. In order to reference JMS resources from a web app: * For a connection factory, use a resource-ref (I think you did this) * For a topic or queue in J2EE 1.4 / Servlet 2.4, use a messsage-destination-ref * For a topic or queue in J2EE 1.4 / Servlet 2.4, use a resource-env-ref So your queue reference was not correct in the snippets you posted. For a walkthrough of the correct syntax, see http://chariotsolutions.com/geronimo/geronimo-1.1/web-plan.html#web-plan-jms (section 11.3.5.5 has a discussion with examples of both styles). Your EJB JAR used EJB 2.0, which suggests that you're using J2EE 1.3, but you might be using Servlet 2.4 anyway, which would make the difference. If you want more specific help, you'll need to post your web.xml files. Thanks, Aaron On 8/8/06, Manish Satwani [EMAIL PROTECTED] wrote: Hi , I am new in geronimo can you please tell me where exactly should i change I am attaching all configuration files here I have 2 war in my ear thats why i attached 2 geronimo-web.xml please help me Thanks Manish On 8/8/06, Krishnakumar B [EMAIL PROTECTED] wrote: For referring to Queues u should use nam:resource-env-ref nam:ref-name/nam:ref-name admin-object-link/admin-object-link /nam:resource-env-ref or Message Destination Reference I think both would work http://www.chariotsolutions.com/geronimo/geronimo-1.1/web-plan.html#web-plan-refs ( You can refer to resource-env-ref for J2EE Connector Administered Objects ) Resource Environment Ref can be used to reference JMS Destinations. Regards Krishnakumar On 8/8/06, Manish Satwani [EMAIL PROTECTED] wrote: Hi All, I am facing problem while deploying my ear on geronimo 1.1 It is complaining regarding jms/AcevaPublisherQueue (my application need this) I have added this queue from console. we have acm.war file which also access (resource-ref) this queue and i have acevaEJB.jar which also have (resource-ref) to this queue i also added resource-link entries in geronimo-web.xml and openEJB-jar.xml this is in openEjb-jar.xml session ejb-nameCollectionService/ejb-name jndi-nameejb/CollectionService/jndi-name naming:resource-ref naming:ref-namejms/AcevaPublisherConnectionFactory/naming:ref-name naming:resource-linkjms/AcevaPublisherConnectionFactory/naming:resource-link /naming:resource-ref naming:resource-ref naming:ref-namejms/AcevaPublisherQueue/naming:ref-name naming:resource-linkjms/AcevaPublisherQueue/naming:resource-link /naming:resource-ref /session this is in geronimo-web.xml naming:resource-ref
[jira] Created: (GERONIMO-2310) Ability to import plugin file from file system
Ability to import plugin file from file system -- Key: GERONIMO-2310 URL: http://issues.apache.org/jira/browse/GERONIMO-2310 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Plugins Reporter: Krishnakumar B Priority: Minor Currently i am able to import plugin from remote repository. ( http://some_url If i can import plugin from file system it would be useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2311) Exporting plug-in configurations
Exporting plug-in configurations Key: GERONIMO-2311 URL: http://issues.apache.org/jira/browse/GERONIMO-2311 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Plugins Affects Versions: 1.1.2 Reporter: Krishnakumar B Priority: Minor When i export a configuration from geronimo to plugin and save it to disk the file names are not legible for e.g) I exported a DataSource Saved as rar.0%2Frar I exported a War . Saved as war.0%2Fwar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2312) Create a New JMS Group throws error for external RAR
Create a New JMS Group throws error for external RAR Key: GERONIMO-2312 URL: http://issues.apache.org/jira/browse/GERONIMO-2312 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Reporter: Krishnakumar B I deployed a JMS RAR using Deploy new and it is deployed. I tried to create a New JMS Group using the console wizard. When i see the deployment plan it doesnt seem right and i get a deployment error when i deploy this plan. The plan looks like this : connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.1; environment moduleId groupIdtest/groupId artifactIdjms.rar/artifactId version1.0/version /moduleId dependencies .. /dependencies /environment dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:moduleId dep:groupIdconsole.jms/dep:groupId dep:artifactIdTestJMSRA/dep:artifactId dep:version1.0/dep:version dep:typerar/dep:type /dep:moduleId /dep:environment resourceadapter resourceadapter-instance resourceadapter-nameTestJMSRA/resourceadapter-name workmanager gbean-linkDefaultWorkManager/gbean-link /workmanager nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance . Clearly the deployment plan generated is not correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2312) Create a New JMS Group throws error for external RAR
[ http://issues.apache.org/jira/browse/GERONIMO-2312?page=all ] Krishnakumar B updated GERONIMO-2312: - Attachment: GERJMSRAR.rar Attached RAR i am using to create a new JMS Group Create a New JMS Group throws error for external RAR Key: GERONIMO-2312 URL: http://issues.apache.org/jira/browse/GERONIMO-2312 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Krishnakumar B Attachments: GERJMSRAR.rar I deployed a JMS RAR using Deploy new and it is deployed. I tried to create a New JMS Group using the console wizard. When i see the deployment plan it doesnt seem right and i get a deployment error when i deploy this plan. The plan looks like this : connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.1; environment moduleId groupIdtest/groupId artifactIdjms.rar/artifactId version1.0/version /moduleId dependencies .. /dependencies /environment dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:moduleId dep:groupIdconsole.jms/dep:groupId dep:artifactIdTestJMSRA/dep:artifactId dep:version1.0/dep:version dep:typerar/dep:type /dep:moduleId /dep:environment resourceadapter resourceadapter-instance resourceadapter-nameTestJMSRA/resourceadapter-name workmanager gbean-linkDefaultWorkManager/gbean-link /workmanager nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance . Clearly the deployment plan generated is not correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Hi , JMS Portlet doesn't show other than activemq.rar file
Hi ahmed, Use the console to import the rar file into repository. Or place it with correct naming conventions GroupID/ArtifactID/Version/Type inside the repository. Regards Krishnakumar On 8/10/06, ahmed [EMAIL PROTECTED] wrote: Hi , Iam using JMS Porlet , Inorder to create a JMS Resource for others Steps followed are here : - 1. I have a external.rar file , placed in GERONIMO_HOME/repository/ directory . 2. Opened the geronimo console , clicked on the JMS Resources link . 3. The combo box , doesn't show me the external.rar file which i placed in the geronimo_home/repository directory . Does anybody has an idea on , how to make use of external.rar file from console . would really apprecaite your inputs !!! Thanks in advance! With Thanks and Regards,
Re: How to resolve JMS Dependency ?
Hi Manish, Can u try naming:resource-ref naming:ref-namejms/AcevaPublisherQueue/naming:ref-name naming:resource-linkAcevaPublisherQueue/naming:resource-link /naming:resource-ref where link refers to message-destination-nameAcevaPublisherQueue/message-destination-name in RA plan. In case this does not work can u post the RA plan? Regards Krishnakumar On 8/8/06, Manish Satwani [EMAIL PROTECTED] wrote: Hi All The following is the error I getting while deploying EAR Unable to resolve resource reference 'jms/AcevaPublisherQueue' (Could not find resource 'jms/AcevaPublisherQueue'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?) org.apache.geronimo.common.DeploymentException: Unable to resolve resource reference 'jms/AcevaPublisherQueue' (Could not find resource 'jms/AcevaPublisherQueue'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?) at org.apache.geronimo.naming.deployment.ENCConfigBuilder.addResourceRefs(ENCConfigBuilder.java:210) On 8/8/06, Manish Satwani [EMAIL PROTECTED] wrote: Hi All, I am facing problem while deploying my ear on geronimo 1.1 It is complaining regarding jms/AcevaPublisherQueue (my application need this) I have added this queue from console. we have acm.war file which also access (resource-ref) this queue and i have acevaEJB.jar which also have (resource-ref) to this queue i also added resource-link entries in geronimo-web.xml and openEJB-jar.xml this is in openEjb-jar.xml session ejb-nameCollectionService/ejb-name jndi-nameejb/CollectionService/jndi-name naming:resource-ref naming:ref-namejms/AcevaPublisherConnectionFactory/naming:ref-name naming:resource-linkjms/AcevaPublisherConnectionFactory/naming:resource-link /naming:resource-ref naming:resource-ref naming:ref-namejms/AcevaPublisherQueue/naming:ref-name naming:resource-linkjms/AcevaPublisherQueue/naming:resource-link /naming:resource-ref /session this is in geronimo-web.xml naming:resource-ref naming:ref-namejms/AcevaPublisherQueue/naming:ref-name naming:resource-linkjms/AcevaPublisherQueue/naming:resource-link /naming:resource-ref any enviroment - depency entry needed? if yes sys:dependency sys:groupId?/sys:groupId (what should i write here) sys:artifactId???/sys:artifactId(what should i write here) /sys:dependency -- Manish Satwani Senior Software Engineer Aceva Technologies | Unlock Your Working Capital A-1501, Signature Towers - I, South City, Gurgaon, Haryana – 122001 Call at: +91-124-2805091/92 Ext. 35 +91-99113-16998 Visit: http://www.aceva.com -- Manish Satwani Senior Software Engineer Aceva Technologies | Unlock Your Working Capital A-1501, Signature Towers - I, South City, Gurgaon, Haryana – 122001 Call at: +91-124-2805091/92 Ext. 35 +91-99113-16998 Visit: http://www.aceva.com
Re: How to resolve JMS Dependency ?
For referring to Queues u should use nam:resource-env-ref nam:ref-name/nam:ref-name admin-object-link/admin-object-link /nam:resource-env-ref or Message Destination Reference I think both would work http://www.chariotsolutions.com/geronimo/geronimo-1.1/web-plan.html#web-plan-refs ( You can refer to resource-env-ref for J2EE Connector Administered Objects ) Resource Environment Ref can be used to reference JMS Destinations. Regards Krishnakumar On 8/8/06, Manish Satwani [EMAIL PROTECTED] wrote: Hi All, I am facing problem while deploying my ear on geronimo 1.1 It is complaining regarding jms/AcevaPublisherQueue (my application need this) I have added this queue from console. we have acm.war file which also access (resource-ref) this queue and i have acevaEJB.jar which also have (resource-ref) to this queue i also added resource-link entries in geronimo-web.xml and openEJB-jar.xml this is in openEjb-jar.xml session ejb-nameCollectionService/ejb-name jndi-nameejb/CollectionService/jndi-name naming:resource-ref naming:ref-namejms/AcevaPublisherConnectionFactory/naming:ref-name naming:resource-linkjms/AcevaPublisherConnectionFactory/naming:resource-link /naming:resource-ref naming:resource-ref naming:ref-namejms/AcevaPublisherQueue/naming:ref-name naming:resource-linkjms/AcevaPublisherQueue/naming:resource-link /naming:resource-ref /session this is in geronimo-web.xml naming:resource-ref naming:ref-namejms/AcevaPublisherQueue/naming:ref-name naming:resource-linkjms/AcevaPublisherQueue/naming:resource-link /naming:resource-ref any enviroment - depency entry needed? if yes sys:dependency sys:groupId?/sys:groupId (what should i write here) sys:artifactId???/sys:artifactId(what should i write here) /sys:dependency -- Manish Satwani Senior Software Engineer Aceva Technologies | Unlock Your Working Capital A-1501, Signature Towers - I, South City, Gurgaon, Haryana – 122001 Call at: +91-124-2805091/92 Ext. 35 +91-99113-16998 Visit: http://www.aceva.com
[jira] Updated: (GERONIMO-2118) Deploying and starting web application in console shows successful even on start exceptions.
[ http://issues.apache.org/jira/browse/GERONIMO-2118?page=all ] Krishnakumar B updated GERONIMO-2118: - Attachment: ConsoleDeploymentCheck-2118.patch Using console when i deploy an application and it throws Exception when starting the GBeans the console still shows The application was successfully deployed. The application was successfully started This patch catches the Exception and prints the following message along with the Exception in Show Details button Deployment Failed : Application failed to start Show Full Details When user hits Show Full Details the Exception Stack Trace is shown. Deploying and starting web application in console shows successful even on start exceptions. Key: GERONIMO-2118 URL: http://issues.apache.org/jira/browse/GERONIMO-2118 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Environment: 1.1-rc1 Reporter: Mario Ruebsam Priority: Minor Attachments: ConsoleDeploymentCheck-2118.patch When deploying and starting a web application through the Geronimo console Install New Applications feature, the web app is deployed and the console states The application was successfully started even when the application was not started because of an Exception (e.g. org.apache.geronimo.gbean.InvalidConfigurationException). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2118) Deploying and starting web application in console shows successful even on start exceptions.
[ http://issues.apache.org/jira/browse/GERONIMO-2118?page=all ] Krishnakumar B updated GERONIMO-2118: - Patch Info: [Patch Available] Affects Version/s: 1.1.1 1.2 (was: 1.1) Updated to patch available and release version Deploying and starting web application in console shows successful even on start exceptions. Key: GERONIMO-2118 URL: http://issues.apache.org/jira/browse/GERONIMO-2118 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2, 1.1.1 Environment: 1.1-rc1 Reporter: Mario Ruebsam Priority: Minor Attachments: ConsoleDeploymentCheck-2118.patch When deploying and starting a web application through the Geronimo console Install New Applications feature, the web app is deployed and the console states The application was successfully started even when the application was not started because of an Exception (e.g. org.apache.geronimo.gbean.InvalidConfigurationException). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2263) Redeploy application from console
Redeploy application from console - Key: GERONIMO-2263 URL: http://issues.apache.org/jira/browse/GERONIMO-2263 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 1.2 Environment: JDK 1.4.2.X Reporter: Krishnakumar B Priority: Minor I deployed an application successfully from console. I did some changes and am trying to redeploy the same application by checking box Redeploy Application. This fails and i get message Deployment failed: Module aa/bb/cc/dd already exists in the server. Try to undeploy it first or use the redeploy command. I need to uninstall the application to get it deployed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Implementing Global JNDI
Hi David, Few days back i had attached a implementation to JIRA-2153. Would be glad if u can provide ur review comments for the same. Regards Krishnakumar On 7/18/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi David, I have updated the JIRA-2153 with Context implementation and GBean that binds to JNDI. Kindly provide ur comments. Regards Krish On 7/6/06, David Jencks [EMAIL PROTECTED] wrote: See my comment in the jira about this, I don't think you need to use any naming References at all, nor do you need anything but a GBean reference to the appropriate GBean. http://issues.apache.org/jira/browse/GERONIMO-2153 thanks david jencks On Jul 6, 2006, at 6:06 AM, Krishnakumar B wrote: Hi David, I tried this and it works for Custom Resource Adapters. There is still a problem for Registering GBeans in Global JNDI through the builder ( ServiceConfigBuilder ). The Builder is a part of geronimo-gbean-deployer plan which is parent of j2ee-deployer. The geronimo-naming jars are loaded in j2ee-deployer. Hence we dont get access in ServiceConfigBuilder to GBeanReference thats part of naming. Currently all the binding GBeans are in naming package. So it works for all j2ee deployments. Is there a way to work around this ClassLoading problem heirarchy for binding GBeans through builder? Regards Krishnakumar On 6/28/06, David Jencks [EMAIL PROTECTED] wrote: I think there is a simpler solution, or perhaps I don't understand all the details of what you are proposing. I think if you give your binding gbeans the magic classLoader attribute everything will work. This will be set to the configuration classloader for the configuration the gbean is in, not the configuration the gbeans class is loaded in. This classloader should always have the necessary classes in it. thanks david jencks On Jun 28, 2006, at 12:39 AM, Manu George wrote: Hi, The problem we are facing regarding adapters is because the binding gbeans were added to the naming module of geronimo. We are planning to change this by creating a separate module for global jndi and then adding it as a dependency in the configuration that is getting deployed. This will be done in the builders. All the reference creation logic can also be moved to the gbeans.The Binding GBeans will then have access to application level classes as they will be loaded in the app class loader. We hope this approach will solve the current problem. We will post the code again after making these changes. Thanks Manu On 6/28/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, We have created a JIRA (http://issues.apache.org/jira/browse/GERONIMO-2153 ) and attached the initial draft. We have tried two approaches. * Adding to plan * Deploying from Builder. The EJBJNDIBindingGBean deploys from OpenEJBModuleBuilder and has a tag global-jndi/ in opene ejb plan. Resource Adapter and GBean have a gbean plan added to deployment plan. gbean name=JMSQueueFactoryJNDIBindingGBean class=org.apache.geronimo.connector.jndi.ConnectorJNDIBindingGBean attribute name=configIdtest/jms.rar/1.0/rar/attribute attribute name=jndiNameglobalJMSQueueFactory/attribute attribute name=componentNameJMSQueueFactory/attribute attribute name=j2eeTypeJCAManagedConnectionFactory/attribute attribute name=interfaceNameorg.apache.geronimo.jms.connector.JMSQueueConnec tionFactory/attribute /gbean and gbean name=TestGBeanJNDIBindingGBean class=org.apache.geronimo.service.jndi.ServiceJNDIBindingGBean attribute name=configIdtest/gbean/1.0/car/attribute attribute name=jndiNameglobalTestGBean/attribute attribute name=componentNameTestGBean/attribute attribute name=j2eeTypeGBean/attribute attribute name=classNamegbean.test.TestGBean/attribute /gbean We have a Classloading issue when trying to maintain all the BindingGbeans at one level. ( rmi-naming ). For GBeans and Resource Adapters that are not J2EE interfaces like javax.sql.DataSource / javax.jms.QueueConnectionFactory we get a ClassNotFound as the class is not available at Classloader of rmi-naming. We spent a lot of time trying to solve this issue but are not able to find a solution as the application level interface or class is not available. This problem will not occur for j2ee interfaces like DataSource, EJB interfaces, Queue, Topic etc.. If the approach is correct we would like to add the other features to make this more suitable for adding into the product. Regards Krishnakumar B On 6/26/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 6/23/06, Krishnakumar B [EMAIL PROTECTED] wrote: The plan needs to have some XML Tag to say this resource needs to gets into Global JNDI and the builder can then add it to geronimo: Context
[jira] Updated: (GERONIMO-2124) Deploying an EAR with included WAR and there included commons-logging fails
[ http://issues.apache.org/jira/browse/GERONIMO-2124?page=all ] Krishnakumar B updated GERONIMO-2124: - Attachment: SimpleServlet.war Hi, I tried this feature in geronimo 1.1 and it works. The geronimo plan has hidden-classes filterorg.apache.log4j/filter /hidden-classes The server repository has log4j - 1.2.8.The application war has log4j 1.2.13 in WEB-INF/lib The Servlet code uses Logger in WEB-INF lib if i give hidden-classes. I call a method on Logger thats not present in 1.2.8 and it works. The example u have attached with JIRA also works. Hence i am not sure why u got the exception except i see a change in JDK I have used JDK1.4.2_09 Deploying an EAR with included WAR and there included commons-logging fails --- Key: GERONIMO-2124 URL: http://issues.apache.org/jira/browse/GERONIMO-2124 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.0 Environment: Ubuntu Linux Java 5.0 Geronimo 1.0 with Tomcat Reporter: Markus Wolf Attachments: ear-test.tar.gz, SimpleServlet.war I have an EAR archive containing a WAR archive. Inside this WAR archiv there is commons-logging bundled. To hide the commons-logging version from Geronimo the geronimo-web.xml contains a hidden-classes element with org.apache.commons.logging. But when a servlet is executed (which uses commons-logging) then there is a stacktrace regarding the two commons-logging versions. I got the following stacktrace: 15:39:45,536 ERROR [[/simpleservlet]] StandardWrapper.Throwable org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at de.nmmn.simple.SimpleServlet.init(SimpleServlet.java:44) at javax.servlet.GenericServlet.init(GenericServlet.java:168) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:750) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:272) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80
[jira] Updated: (GERONIMO-2124) Deploying an EAR with included WAR and there included commons-logging fails
[ http://issues.apache.org/jira/browse/GERONIMO-2124?page=all ] Krishnakumar B updated GERONIMO-2124: - Kindly try out the attached war SimpleServlet.war and see if it works in ur environment. We can then work on this issue or close it. Deploying an EAR with included WAR and there included commons-logging fails --- Key: GERONIMO-2124 URL: http://issues.apache.org/jira/browse/GERONIMO-2124 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.0 Environment: Ubuntu Linux Java 5.0 Geronimo 1.0 with Tomcat Reporter: Markus Wolf Attachments: ear-test.tar.gz, SimpleServlet.war I have an EAR archive containing a WAR archive. Inside this WAR archiv there is commons-logging bundled. To hide the commons-logging version from Geronimo the geronimo-web.xml contains a hidden-classes element with org.apache.commons.logging. But when a servlet is executed (which uses commons-logging) then there is a stacktrace regarding the two commons-logging versions. I got the following stacktrace: 15:39:45,536 ERROR [[/simpleservlet]] StandardWrapper.Throwable org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at de.nmmn.simple.SimpleServlet.init(SimpleServlet.java:44) at javax.servlet.GenericServlet.init(GenericServlet.java:168) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:750) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:272) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check Driver Class during deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ] Krishnakumar B updated GERONIMO-1986: - Attachment: tranql-1986.patch Check in ConnectorModuleBuilder if Driver class id there in ClassLoader ( cl ). If not throw a Deployment Exception. This way the exception can be thrown at deployment and not when GBean starts. TranQL Connector doesn't check Driver Class during deployment - Key: GERONIMO-1986 URL: http://issues.apache.org/jira/browse/GERONIMO-1986 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, connector Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.2 Attachments: db-plan-no-deps.xml, tranql-1986.patch If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available. It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1986) TranQL Connector doesn't check Driver Class during deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1986?page=all ] Krishnakumar B updated GERONIMO-1986: - Attachment: tranql-1986-updated.patch Check if Driver attribute has a value. Not all tranql plans have Driver attribute TranQL Connector doesn't check Driver Class during deployment - Key: GERONIMO-1986 URL: http://issues.apache.org/jira/browse/GERONIMO-1986 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, connector Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.2 Attachments: db-plan-no-deps.xml, tranql-1986-updated.patch, tranql-1986.patch If you deploy the attached plan with the TranQL connector RAR, the distribute phase is successful, but it fails during start because the driver class is not available. It would be much better to find a way to validate the driver class during distribution. I'm not sure how complex this will be; it may involve instanting things during distribution that normally aren't instantiated until start time. But the current behavior is definitely not desirable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2153) Global JNDI
[ http://issues.apache.org/jira/browse/GERONIMO-2153?page=all ] Krishnakumar B updated GERONIMO-2153: - Attaching a Context Implementation and GBean for binding connectors. The GBean is called from Builder and a reference is passed thats bound to JNDI. Global JNDI --- Key: GERONIMO-2153 URL: http://issues.apache.org/jira/browse/GERONIMO-2153 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: naming Affects Versions: 1.2 Reporter: Krishnakumar B Attachments: jndi-project.zip Implementing Global JNDI for server Requirements * Non -persistent * Read/Write * Bindings to JNDI/COS-NAMING/JAXR * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2153) Global JNDI
[ http://issues.apache.org/jira/browse/GERONIMO-2153?page=all ] Krishnakumar B updated GERONIMO-2153: - Attachment: GeronimoGlobalContext.java Context implementation Global JNDI --- Key: GERONIMO-2153 URL: http://issues.apache.org/jira/browse/GERONIMO-2153 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: naming Affects Versions: 1.2 Reporter: Krishnakumar B Attachments: GeronimoGlobalContext.java, jndi-project.zip Implementing Global JNDI for server Requirements * Non -persistent * Read/Write * Bindings to JNDI/COS-NAMING/JAXR * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2153) Global JNDI
[ http://issues.apache.org/jira/browse/GERONIMO-2153?page=all ] Krishnakumar B updated GERONIMO-2153: - Attachment: ConnectorJNDIBindingGBean.java GBean that binds and unbinds Connectors to JNDI Global JNDI --- Key: GERONIMO-2153 URL: http://issues.apache.org/jira/browse/GERONIMO-2153 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: naming Affects Versions: 1.2 Reporter: Krishnakumar B Attachments: ConnectorJNDIBindingGBean.java, GeronimoGlobalContext.java, jndi-project.zip Implementing Global JNDI for server Requirements * Non -persistent * Read/Write * Bindings to JNDI/COS-NAMING/JAXR * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Implementing Global JNDI
Hi David, I have updated the JIRA-2153 with Context implementation and GBean that binds to JNDI. Kindly provide ur comments. Regards Krish On 7/6/06, David Jencks [EMAIL PROTECTED] wrote: See my comment in the jira about this, I don't think you need to use any naming References at all, nor do you need anything but a GBean reference to the appropriate GBean. http://issues.apache.org/jira/browse/GERONIMO-2153 thanks david jencks On Jul 6, 2006, at 6:06 AM, Krishnakumar B wrote: Hi David, I tried this and it works for Custom Resource Adapters. There is still a problem for Registering GBeans in Global JNDI through the builder ( ServiceConfigBuilder ). The Builder is a part of geronimo-gbean-deployer plan which is parent of j2ee-deployer. The geronimo-naming jars are loaded in j2ee-deployer. Hence we dont get access in ServiceConfigBuilder to GBeanReference thats part of naming. Currently all the binding GBeans are in naming package. So it works for all j2ee deployments. Is there a way to work around this ClassLoading problem heirarchy for binding GBeans through builder? Regards Krishnakumar On 6/28/06, David Jencks [EMAIL PROTECTED] wrote: I think there is a simpler solution, or perhaps I don't understand all the details of what you are proposing. I think if you give your binding gbeans the magic classLoader attribute everything will work. This will be set to the configuration classloader for the configuration the gbean is in, not the configuration the gbeans class is loaded in. This classloader should always have the necessary classes in it. thanks david jencks On Jun 28, 2006, at 12:39 AM, Manu George wrote: Hi, The problem we are facing regarding adapters is because the binding gbeans were added to the naming module of geronimo. We are planning to change this by creating a separate module for global jndi and then adding it as a dependency in the configuration that is getting deployed. This will be done in the builders. All the reference creation logic can also be moved to the gbeans.The Binding GBeans will then have access to application level classes as they will be loaded in the app class loader. We hope this approach will solve the current problem. We will post the code again after making these changes. Thanks Manu On 6/28/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, We have created a JIRA (http://issues.apache.org/jira/browse/GERONIMO-2153 ) and attached the initial draft. We have tried two approaches. * Adding to plan * Deploying from Builder. The EJBJNDIBindingGBean deploys from OpenEJBModuleBuilder and has a tag global-jndi/ in opene ejb plan. Resource Adapter and GBean have a gbean plan added to deployment plan. gbean name=JMSQueueFactoryJNDIBindingGBean class=org.apache.geronimo.connector.jndi.ConnectorJNDIBindingGBean attribute name=configIdtest/jms.rar/1.0/rar/attribute attribute name=jndiNameglobalJMSQueueFactory/attribute attribute name=componentNameJMSQueueFactory/attribute attribute name=j2eeTypeJCAManagedConnectionFactory/attribute attribute name=interfaceNameorg.apache.geronimo.jms.connector.JMSQueueConnec tionFactory/attribute /gbean and gbean name=TestGBeanJNDIBindingGBean class=org.apache.geronimo.service.jndi.ServiceJNDIBindingGBean attribute name=configIdtest/gbean/1.0/car/attribute attribute name=jndiNameglobalTestGBean/attribute attribute name=componentNameTestGBean/attribute attribute name=j2eeTypeGBean/attribute attribute name=classNamegbean.test.TestGBean/attribute /gbean We have a Classloading issue when trying to maintain all the BindingGbeans at one level. ( rmi-naming ). For GBeans and Resource Adapters that are not J2EE interfaces like javax.sql.DataSource / javax.jms.QueueConnectionFactory we get a ClassNotFound as the class is not available at Classloader of rmi-naming. We spent a lot of time trying to solve this issue but are not able to find a solution as the application level interface or class is not available. This problem will not occur for j2ee interfaces like DataSource, EJB interfaces, Queue, Topic etc.. If the approach is correct we would like to add the other features to make this more suitable for adding into the product. Regards Krishnakumar B On 6/26/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 6/23/06, Krishnakumar B [EMAIL PROTECTED] wrote: The plan needs to have some XML Tag to say this resource needs to gets into Global JNDI and the builder can then add it to geronimo: Context. This is not implemented yet. Currently if we deploy a connector it gets in global jndi. I might've misunderstood it, but isn't Global JNDI == geronimo: context == global: context? If so, why is this copying from Global JNDI to the geronimo: namespace? Looking forward to seeing your patch for it. Just as Guillaume
[jira] Created: (GERONIMO-2186) Editing of Connection Pools other than Derby from console not working
Editing of Connection Pools other than Derby from console not working - Key: GERONIMO-2186 URL: http://issues.apache.org/jira/browse/GERONIMO-2186 Project: Geronimo Type: Bug Security: public (Regular issues) Components: console Versions: 1.2 Reporter: Krishnakumar B Priority: Minor Editing of connection pools other than Cloudscape is currently not working -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2187) Ability to set scope of Connection Pool created from console
Ability to set scope of Connection Pool created from console Key: GERONIMO-2187 URL: http://issues.apache.org/jira/browse/GERONIMO-2187 Project: Geronimo Type: Wish Security: public (Regular issues) Components: console Versions: Wish List Reporter: Krishnakumar B Priority: Minor Improves usability if user can also set scope of Pool from Console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2188) Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle Key: GERONIMO-2188 URL: http://issues.apache.org/jira/browse/GERONIMO-2188 Project: Geronimo Type: Bug Security: public (Regular issues) Components: connector Versions: 1.1.1 Reporter: Krishnakumar B We have to configure CommitBeforeAutCommit=true property exclusively in the database connection pool plan, to have the ejb -based transactions immediately committed for oracle database. Otherwise it only commits transaction when the server shuts-down. This problem is not faces with Derby database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1293) Provide tomcat statistics
[ http://issues.apache.org/jira/browse/GERONIMO-1293?page=all ] Krishnakumar B updated GERONIMO-1293: - Can some more details like Execute Thread, Queue Length be provided for Tomcat that would be useful for performance modelling Provide tomcat statistics - Key: GERONIMO-1293 URL: http://issues.apache.org/jira/browse/GERONIMO-1293 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: Tomcat Versions: 1.0-M5 Environment: All environments Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha Priority: Minor Fix For: 1.2 Attachments: TomcatWebAppContext.patch, geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.1-SNAPSHOT.war, management.patch, management.patch, management.patch, project.patch, properties.patch, properties.patch, stats.zip, stats.zip, stats.zip, statsApp.zip, tomcat-builder.patch, tomcat.patch, tomcat.patch, tomcat.patch, tomcat.patch Provide following statistics for tomcat : 1. Per Host/Container - a. Initially provide the following per connector statistics for each connector - Cummulative statistics about all request handled by this connector since the stat were turned on. b. If time (before 1.0 release) permits, use 'a' to generate (rename/compute) statistics similar to the ones provided by Jetty 2. Per application - a.. processingTime : The cumulative processing times of all servlets in this StandardContext b. startTime - The time this context was started. c. startupTime - The time (in milliseconds) it took to start this context. d.. tldScanTime() - Later add session statistics and jsp statistics. 3. Per Servlet - Explore using statistics from RequestInfo to provide statistics for a servlet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Implementing Global JNDI
Hi David, I tried this and it works for Custom Resource Adapters. There is still a problem for Registering GBeans in Global JNDI through the builder ( ServiceConfigBuilder ). The Builder is a part of geronimo-gbean-deployer plan which is parent of j2ee-deployer. The geronimo-naming jars are loaded in j2ee-deployer. Hence we dont get access in ServiceConfigBuilder to GBeanReference thats part of naming. Currently all the binding GBeans are in naming package. So it works for all j2ee deployments. Is there a way to work around this ClassLoading problem heirarchy for binding GBeans through builder? Regards Krishnakumar On 6/28/06, David Jencks [EMAIL PROTECTED] wrote: I think there is a simpler solution, or perhaps I don't understand all the details of what you are proposing. I think if you give your binding gbeans the magic classLoader attribute everything will work. This will be set to the configuration classloader for the configuration the gbean is in, not the configuration the gbeans class is loaded in. This classloader should always have the necessary classes in it. thanks david jencks On Jun 28, 2006, at 12:39 AM, Manu George wrote: Hi, The problem we are facing regarding adapters is because the binding gbeans were added to the naming module of geronimo. We are planning to change this by creating a separate module for global jndi and then adding it as a dependency in the configuration that is getting deployed. This will be done in the builders. All the reference creation logic can also be moved to the gbeans.The Binding GBeans will then have access to application level classes as they will be loaded in the app class loader. We hope this approach will solve the current problem. We will post the code again after making these changes. Thanks Manu On 6/28/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, We have created a JIRA (http://issues.apache.org/jira/browse/GERONIMO-2153 ) and attached the initial draft. We have tried two approaches. * Adding to plan * Deploying from Builder. The EJBJNDIBindingGBean deploys from OpenEJBModuleBuilder and has a tag global-jndi/ in opene ejb plan. Resource Adapter and GBean have a gbean plan added to deployment plan. gbean name=JMSQueueFactoryJNDIBindingGBean class=org.apache.geronimo.connector.jndi.ConnectorJNDIBindingGBean attribute name=configIdtest/jms.rar/1.0/rar/attribute attribute name=jndiNameglobalJMSQueueFactory/attribute attribute name=componentNameJMSQueueFactory/attribute attribute name=j2eeTypeJCAManagedConnectionFactory/attribute attribute name=interfaceNameorg.apache.geronimo.jms.connector.JMSQueueConnectionFactory/attribute /gbean and gbean name=TestGBeanJNDIBindingGBean class=org.apache.geronimo.service.jndi.ServiceJNDIBindingGBean attribute name=configIdtest/gbean/1.0/car/attribute attribute name=jndiNameglobalTestGBean/attribute attribute name=componentNameTestGBean/attribute attribute name=j2eeTypeGBean/attribute attribute name=classNamegbean.test.TestGBean/attribute /gbean We have a Classloading issue when trying to maintain all the BindingGbeans at one level. ( rmi-naming ). For GBeans and Resource Adapters that are not J2EE interfaces like javax.sql.DataSource / javax.jms.QueueConnectionFactory we get a ClassNotFound as the class is not available at Classloader of rmi-naming. We spent a lot of time trying to solve this issue but are not able to find a solution as the application level interface or class is not available. This problem will not occur for j2ee interfaces like DataSource, EJB interfaces, Queue, Topic etc.. If the approach is correct we would like to add the other features to make this more suitable for adding into the product. Regards Krishnakumar B On 6/26/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 6/23/06, Krishnakumar B [EMAIL PROTECTED] wrote: The plan needs to have some XML Tag to say this resource needs to gets into Global JNDI and the builder can then add it to geronimo: Context. This is not implemented yet. Currently if we deploy a connector it gets in global jndi. I might've misunderstood it, but isn't Global JNDI == geronimo: context == global: context? If so, why is this copying from Global JNDI to the geronimo: namespace? Looking forward to seeing your patch for it. Just as Guillaume suggested, please create an JIRA issue and attach the patch to it. Krishnakumar B Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Updated: (GERONIMO-2153) Global JNDI
[ http://issues.apache.org/jira/browse/GERONIMO-2153?page=all ] Krishnakumar B updated GERONIMO-2153: - Attachment: jndi-project.zip Initial Draft for review. Global JNDI --- Key: GERONIMO-2153 URL: http://issues.apache.org/jira/browse/GERONIMO-2153 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: naming Versions: 1.2 Reporter: Krishnakumar B Attachments: jndi-project.zip Implementing Global JNDI for server Requirements * Non -persistent * Read/Write * Bindings to JNDI/COS-NAMING/JAXR * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Implementing Global JNDI
Hi, We have created a JIRA (http://issues.apache.org/jira/browse/GERONIMO-2153 ) and attached the initial draft. We have tried two approaches. * Adding to plan * Deploying from Builder. The EJBJNDIBindingGBean deploys from OpenEJBModuleBuilder and has a tag global-jndi/ in opene ejb plan. Resource Adapter and GBean have a gbean plan added to deployment plan. gbean name=JMSQueueFactoryJNDIBindingGBean class=org.apache.geronimo.connector.jndi.ConnectorJNDIBindingGBean attribute name=configIdtest/jms.rar/1.0/rar/attribute attribute name=jndiNameglobalJMSQueueFactory/attribute attribute name=componentNameJMSQueueFactory/attribute attribute name=j2eeTypeJCAManagedConnectionFactory/attribute attribute name=interfaceNameorg.apache.geronimo.jms.connector.JMSQueueConnectionFactory/attribute /gbean and gbean name=TestGBeanJNDIBindingGBean class=org.apache.geronimo.service.jndi.ServiceJNDIBindingGBean attribute name=configIdtest/gbean/1.0/car/attribute attribute name=jndiNameglobalTestGBean/attribute attribute name=componentNameTestGBean/attribute attribute name=j2eeTypeGBean/attribute attribute name=classNamegbean.test.TestGBean/attribute /gbean We have a Classloading issue when trying to maintain all the BindingGbeans at one level. ( rmi-naming ). For GBeans and Resource Adapters that are not J2EE interfaces like javax.sql.DataSource / javax.jms.QueueConnectionFactory we get a ClassNotFound as the class is not available at Classloader of rmi-naming. We spent a lot of time trying to solve this issue but are not able to find a solution as the application level interface or class is not available. This problem will not occur for j2ee interfaces like DataSource, EJB interfaces, Queue, Topic etc.. If the approach is correct we would like to add the other features to make this more suitable for adding into the product. Regards Krishnakumar B On 6/26/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 6/23/06, Krishnakumar B [EMAIL PROTECTED] wrote: The plan needs to have some XML Tag to say this resource needs to gets into Global JNDI and the builder can then add it to geronimo: Context. This is not implemented yet. Currently if we deploy a connector it gets in global jndi. I might've misunderstood it, but isn't Global JNDI == geronimo: context == global: context? If so, why is this copying from Global JNDI to the geronimo: namespace? Looking forward to seeing your patch for it. Just as Guillaume suggested, please create an JIRA issue and attach the patch to it. Krishnakumar B Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Created: (GERONIMO-2153) Global JNDI
Global JNDI --- Key: GERONIMO-2153 URL: http://issues.apache.org/jira/browse/GERONIMO-2153 Project: Geronimo Type: New Feature Security: public (Regular issues) Components: naming Versions: 1.2 Reporter: Krishnakumar B Implementing Global JNDI for server Requirements * Non -persistent * Read/Write * Bindings to JNDI/COS-NAMING/JAXR * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2153) Global JNDI
[ http://issues.apache.org/jira/browse/GERONIMO-2153?page=all ] Krishnakumar B updated GERONIMO-2153: - Patch Info: (was: [Patch Available]) Global JNDI --- Key: GERONIMO-2153 URL: http://issues.apache.org/jira/browse/GERONIMO-2153 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: naming Versions: 1.2 Reporter: Krishnakumar B Implementing Global JNDI for server Requirements * Non -persistent * Read/Write * Bindings to JNDI/COS-NAMING/JAXR * Can bind RA,EJB,GBEAN,Any object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Error in building assembly for 1.1
hi, i am trying to build a tomcat assembly for 1.1 BUILD FAILED File.. C:\Documents and Settings\Administrator\.maven\cache\geronimo-assembl y-plugin-1.1.0-12\plugin.jelly Element... assemble:installConfig Line.. 197 Column 149 org.apache.geronimo.gbean.GBeanInfo incompatible with org.apache.geronimo.kernel .config.ConfigurationData Total time : 25 seconds Finished at : Thursday, June 1, 2006 2:53:06 PM IST Any ideas how to rectify and get a assembly. regards Krish
Re: Implementing Global JNDI
Thanks for the feedback and inputs. Regards Krishnakumar On 5/24/06, Dain Sundstrom [EMAIL PROTECTED] wrote: On May 23, 2006, at 5:19 PM, David Jencks wrote: On May 23, 2006, at 6:28 AM, Krishnakumar B wrote: Hi, I have a few doubts related to implementation of global jndi. * Currently we have java:comp/env stored in Local JNDI. In Global JNDI should objects be bound using a different namespace e.g) java: or java:global? IIUC java: is reserved by the j2ee spec for what it requires: thus IMO we should use something else. IIRC the original global jndi context used geronimo: I'm OK with that or maybe global:. IIRC some servers use just /foo/bar with no context. If I am correct, we should support that also (but not the default). * When we implement global JNDI we have some entries in Global and All entries related to application in Local. When a user creates a context he needs to get from either global or local based on what he needs. Would it be right for lookup code to decide from where to fetch the entry based on how the Context is created? for e.g) if i say InitialContext iniCtx = new InitialContext(java:comp/env); fetch from local and if InitialContext iniCtx = new InitialContext(java:global); fetch from global I'm not sure what you're asking about here. Unless you do something screwy to link one of these to the other, the contents of these contexts will be completely unrelated. Looking at the JavaDocs for InitialContext, it does not have a constructor that takes a String. Did you mean: Context context = (Context) new InitialContext().lookup(java:comp/ env); Context context = (Context) new InitialContext().lookup(global:); * Currently in Local JNDI we store Resource References. Should global JNDI also use the same approach or can we use Object references for e.g) DataSource reference directly put in JNDI For j2ee components I think we should bind the same kinds of References in the global jndi tree as we bind in the current java: context. What we bind for stuff that can't get into the java: context needs more thought: it probably depends on what it is. Of course if the context is not read-only an app can bind whatever it wants wherever it wants, thus bringing to mind the need for security and permissions for this stuff. I don't think we can use the current Reference object we bind into our read only context because they do cache the value and never release it. It is expected that the referece will be GCed when the J2EE application is unloaded. It shouldn't be hard to either turn off the cache or to register listener for the reference target life- cycle events. Would appreciate any thoughts as i am still learning and might have missed some points to consider while trying to implement something like this. My plan for implementing this was: 1. Look at the current ReadOnlyContext implementation and figure out how to make a sufficiently synchronized version of it. I'm hoping that we can have synchronized wrappers around this implementation rather than needing a copy, subclass, or new implementation. I think a read only JNDI and a mutable one are different enough that they need separate implementations. Currently our ENC is using a the EnterpriseNamingContext which does not extend ReadOnlyContext (as it isn't really read only). I'd like to keep the EnterpriseNamingContext simple and strictly read only. Therefore, I'd like to see an new separate implementation. If I were going to write it, I'd base it on ConcurrentReaderHashMap and future objects in Java5 (or backport-concurrent-util), but I'm not writing it, so I say do whatever you are comfortable with. 2. Remind myself of how the geronimo: context used to be installed. I think the same method will still work. We might want a gbean to specifically install it. Make sure that programmatic binding and lookup works. IIRC, we add set naming provider package to org.apache.geronimo.naming and when a user tries to access the foo: root-context, the jvm looks for the class org.apache.geronimo.naming.foo.fooURLContextFactory. We still have one named global that most likely gets loaded when someone looks up global: 3. Figure out how to bind stuff into this context from plans rather than java code. Currently my idea is to do this with binding gbeans: I'm not entirely sure how to do this but one possibility would be to have them contain a Reference object and the name to bind it under. Another possibility would be to not use References but rather have a binding gbean with say a gbean reference to a ManagedConnectionFactoryWrapper: the gbean would call $getResource () on it and then bind the result directly into jndi. This would result in simpler builders but more gbeans: we'd need one for resource-refs and resource-env-refs, and another one for ejbs, and another for plain gbean bindings. One thing I like about this second plan is that the object would only
Re: Implementing Global JNDI
Hi, I have a few doubts related to implementation of global jndi. * Currently we have java:comp/env stored in Local JNDI. In Global JNDI should objects be bound using a different namespace e.g) java: or java:global? * When we implement global JNDI we have some entries in Global and All entries related to application in Local. When a user creates a context he needs to get from either global or local based on what he needs. Would it be right for lookup code to decide from where to fetch the entry based on how the Context is created? for e.g) if i say InitialContext iniCtx = new InitialContext(java:comp/env); fetch from local and if InitialContext iniCtx = new InitialContext(java:global); fetch from global * Currently in Local JNDI we store Resource References. Should global JNDI also use the same approach or can we use Object references for e.g) DataSource reference directly put in JNDI Would appreciate any thoughts as i am still learning and might have missed some points to consider while trying to implement something like this. Regards Krishnakumar On 4/28/06, David Jencks [EMAIL PROTECTED] wrote: On Apr 27, 2006, at 9:16 AM, Dain Sundstrom wrote: I think we need to provide a non-persistent r/w global jndi tree since there are so many apps that depend on it. In addition, I think we need a way for users to provide a set of bindings (JNDI, cos-naming, jaxr... really anything) to EJBs, RAs, and any GBean so that the services they need are available where their application expect. I have been thinking about the binding problem for a while and just haven't had time to work on it myself. I think we can do something as simple as this for most services: gbean name=foo-binding class=org.apache.geronimo.naming.JndiBinding reference name=objectnamemyService/... attribute name=addressservices/myService/... /... For J2EE services we want to bind, I think the xml above is way to complex and we need to provide some syntactic sugar. That's basically what I had in mind, but expressed more clearly and concretely thanks david jencks -dain On Apr 27, 2006, at 1:22 AM, David Jencks wrote: I'm not convinced this discussion has got to the hard parts yet :-) I hope there turn out not to be any :-) Please don't change stuff in the read-only java:comp/env context since it is pretty much completely specified by the spec. Note also that according to the spec a j2ee compliant app will only use this jndi context, and only use the entries defined in the j2ee deployment descriptors. I think you can use a lot of the jndi infrastructure we already have including the geronimo context and the references to jca connection factories, ejbs, etc. The missing part is how to get these references bound into your context. One approach is to write gbeans that install a reference when started and remove it when stopped. I would start by just including these as plain gbeans in plans, and once that works consider modifying the builders to add them automatically based on xml in the geronimo plans. An alternative might be to investigating using say Directory to persist the references directly. I don't know enough about ldap to know if this makes any sense at all. thanks david jencks On Apr 26, 2006, at 11:56 PM, Manu George wrote: Comments inline On 4/26/06, Guillaume Nodet [EMAIL PROTECTED] wrote: Looking more closely, it seems I was wrong. Gbeans with a j2eeType=JCAManagedConnectionFactory have a connectionFactoryInterface attribute that gives the name of the main interface to use when binding the object to the JNDI context. For EJB, GBeans with a j2eeType=StatelessSessionBean (or EntityBean ...) have attributes for the home and business interfaces. So i guess it should be ok. great Another way to handle that would be to bind the resource to the global JNDI tree when the resource is created: each configuration would contain a list of gbeans to bind in the jndi tree when the configuration is loaded. Else, we will need some listener to listen to gbeans creation / destruction so that we can bind / unbind them from the global jndi context. Binding the resource during creation seems to be the simpler way. But what about the next time the server starts up. How is the context initialised? Do we populate during startup of each resource or application again or is persistence used in some way? In the case of listeners the above problem won't arise. A few questions: * I' m wondering how the global JNDI context will coexist with the existing ENC context, especially if the global jndi context is read-write ... Maybe there is no need for a local jndi context ... Yes that is a question i also have :-) . The local jndi context allows us to have app specific contexts and this has some advantages. A global jndi also has some advantages. Probably by default we can use the local context and if the user specifies a custom factory the global one or
Re: [announce] Apache Geronimo welcomes Guillaume Nodet as our newest committer
Congrats Guillaume On 4/28/06, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Congratulations Guillaume!! -Vamsi On 4/28/06, Dain Sundstrom [EMAIL PROTECTED] wrote: The Apache Geronimo PMC is proud to announce Guillaume Nodet as our newest Apache Geronimo committer, and look forward to his continued great work on XBean and the Geronimo integration with Service Mix. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. Guillaume has consistently brought unique and very difficult use cases to the XBean project (along with patches), and it is these diverse requirements that will ultimately make XBean a success. We believe he will be an excellent addition to the project and will help foster these values in others. Please join us in congratulating Guillaume, The Apache Geronimo PMC
Re: Implementing Global JNDI
Hi Guillaume, The ENCConfigBuilder and ComponentContextBuilder are called when u deploy an application and need a JNDI reference. How does it happen when u start the app server with some apps already deployed? How is the Context built? Regards Krish On 4/26/06, Guillaume Nodet [EMAIL PROTECTED] wrote: When a JNDI context is created for a given configuration, the interface name is used to determine the name of the gbean that will be mapped to this JNDI reference (and to create a proxy ?). Take a look at o.a.g.naming.ENCConfigBuilder#addResourceRefs. But I guess this is irrelevant if the objects are bound when they are created. Btw, should the global JNDI tree be read-only, or read-write ? IMHO, a read-write global JNDI tree would be very usefull. Cheers, Guillaume Nodet Manu George wrote: Thanks David. Guillaume , Which proxy in the JNDI Tree are you referring where geronimo requires the main interface name? Are you speaking of UserTransaction etc? I thought those were standard names that we can use to access them and will not be provided in DD? Please clarify and correct me if I am wrong. Thanks Manu On 4/25/06, *David Jencks* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: It's required for corba ejb references. david jencks On Apr 25, 2006, at 7:34 AM, Manu George wrote: Hi, I have a question regarding one of the objects present in the current application local JNDI Context. What is the HandleDelegate entry for? Thanks Manu
SSO in Tomcat
Hi, I have a ? related to SSO in tomcat. I can build geronimo configuring a SSO Valve and use this in web applications deployed in Tomcat. This works. If i deploy a new Valve along with a web application this does not work. Can valves be deployed at application level so that it works for some web applications? I dont need to have a pre-built Valve enabled with the Server if this works. Regards Krish
Re: SSO in Tomcat
hi Jeff, Thanks for the reply. I have tried this but am not able to get it to work. My plan looks like this for test/web/1 and test/web/2. Both apps use same Realm and Valve. ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/web; xmlns:sec=http://geronimo.apache.org/xml/ns/security; configId=test/web/2 context-root/web2/context-root context-priority-classloaderfalse/context-priority-classloader container-config container=Tomcat config-param name=TomcatRealmTomcatJAASRealm/config-param config-param name=TomcatValveChainSSOValve/config-param /container-config security-realm-namegeronimo-properties-realm/security-realm-name security default-principal realm-name=properties-realm principal class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal name=system / /default-principal role-mappings role role-name=admin realm realm-name=properties-realm principal class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal name=admin designated-run-as=true / principal class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal name=system / /realm /role role role-name=users realm realm-name=properties-realm principal class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal name=users designated-run-as=true / principal class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal name=user1 / principal class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal name=user2 / /realm /role role role-name=guest realm realm-name=properties-realm principal class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal name=guest designated-run-as=true / principal class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal name=guest1 / /realm /role /role-mappings /security gbean name=SSOValve class=org.apache.geronimo.tomcat.ValveGBean attribute name=classNameorg.apache.catalina.authenticator.SingleSignOn/attribute /gbean /web-app Regards Krish On 4/20/06, Jeff Genender [EMAIL PROTECTED] wrote: Yes, you should be able to do this. Look at the geronimo-web.xml for the Tomcat descriptor. There is a xml tag that lets you reference a valve in the geronimo-web.xml. Krishnakumar B wrote: Hi, I have a ? related to SSO in tomcat. I can build geronimo configuring a SSO Valve and use this in web applications deployed in Tomcat. This works. If i deploy a new Valve along with a web application this does not work. Can valves be deployed at application level so that it works for some web applications? I dont need to have a pre-built Valve enabled with the Server if this works. Regards Krish
Re: JDBC Pool access from remote client.
hi aaron, Some basic ?s regarding JNDI for DataSource. Currently where is the JNDI names for datasources stored in Geronimo? Are any JNDI names stored in rmi server on port 1099? Regards Krish On 2/23/06, Aaron Mulder [EMAIL PROTECTED] wrote: If you have a J2EE application client, you can configure it with what appears to be a regular pool but it actually creates the pool on the client side which creates connections from the client to the database without interacting with the app server at all. We don't yet have the kind of remote JDBC wrapper you're talking about, and we also don't have anything that a non-J2EE client can take advantage of. Patches would be appreciated. :) Thanks, Aaron On 2/23/06, Krishnakumar B [EMAIL PROTECTED] wrote: Hi, Can i get a JDBC Connection for a remote java application from Geronimo Pool? I saw this listed as a requirement in Road Map. ( A JDBC network wrapper allowing a remote client to access a JDBC pool running in the server ) In case this needs to be provided would the approach be as follows. * Provide Context Factory that implements InitialContextFactory Weblogic provides this option for clients to get a connection from pool in server. Regards Krish
JDBC Pool access from remote client.
Hi, Can i get a JDBC Connection for a remote java application from Geronimo Pool? I saw this listed as a requirement in Road Map. ( A JDBC network wrapper allowing a remote client to access a JDBC pool running in the server ) In case this needs to be provided would the approach be as follows. * Provide Context Factory that implements InitialContextFactory Weblogic provides this option for clients to get a connection from pool in server. Regards Krish
[jira] Updated: (GERONIMO-585) No indication when DefaultWorkManager pool is exhausted
[ http://issues.apache.org/jira/browse/GERONIMO-585?page=all ] Krishnakumar B updated GERONIMO-585: Attachment: WorkExecutorPoolImpl.patch Prints WARN message in log file WARN [WorkExecutorPoolImpl] Pool size is fully consumed -- Maximum Pool Size is :10 No indication when DefaultWorkManager pool is exhausted --- Key: GERONIMO-585 URL: http://issues.apache.org/jira/browse/GERONIMO-585 Project: Geronimo Type: Improvement Components: connector Versions: 1.0-M3 Reporter: Aaron Mulder Fix For: 1.1 Attachments: WorkExecutorPoolImpl.patch I created a connector that executes 8 long-running Work objects at startup (DefaultWorkManager pool size = 10). If I deploy it twice, the second deploy operation hangs, causing the deploy tool to hang as well (and in fact the server hangs if you try to shut down and you have to kill -9 it). There's no evidence what the problem is. It would be nice if we at least printed a debug message or something when you submit work and there's no worker thread available. In truth, there are better ways to code the RA, but the hangs, and the fact that it hangs the deployer and server shutdown too... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
DefaultWorkManager and Pool Size
Hi, The DefaultWorkManager has a pool size of 10. If i submit more than 10 long running units of work i dont know that the Threads 10 are waiting. Can some message be printed in log so that i can know that the pool is fully consumed and Work instances are waiting for execution. The PooledExecutor getPoolSize() gives the size of pool currently consumed If so can this check can be added to WorkExecutorPoolImpl to check the pool size during execution? If i need to increase the pool size is it enough to redeploy DefaultWorkManager GBean? Regards Krishnakumar B
Re: Geronimo w/ WebSphere MQ 5.3 XA
hi Jason, I have tried without XA to keep it simple. XA would also work without any issues. You can try this for XA support ( https://genericjmsra.dev.java.net/docs/userguide/userguide.html ). With some modifications this works on geronimo. Regards Krishnakumar B On 1/14/06, Jason Dillon [EMAIL PROTECTED] wrote: Has anyone had any luck getting Geronimo to work with WebSphere MQ 5.3 w/XA? --jason
Config Id Clarification related to Classloading
Hi, i have a geronimo-ra.xml plan with dependency jars. A MDB gets messages from RA and has a openejb-jar.xml plan. If i use M5 at runtime i get errors that say ClassNotFound Exception. The parent config of open-ejb-jar.xml is geronimo-ra.xml. If i use a build post M5 this works fine. Are there any changes related to classloading post M5 so that i dont get this error. Krishnakumar B
Resource Adapter Reference in MDB
hi, I am trying to get a generic jms resource adapter working. The RA delivers to MDB whose onMessage is activated. The MDB openejb-jar.xml has a resource ref link enterprise-beans message-driven ejb-nameTestMDB/ejb-name resource-adapter resource-linkTestRA/resource-link /resource-adapter /message-driven /enterprise-beans /openejb-jar When deploying this MDB i get the following error. Error: Unable to distribute wascemq.jar: Unknown resource adapter reference (query=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,j2eeType=JCA ResourceAdapter,name=TestRA,*) The RA is deployed successfully and i am able to invoke outbound connections from a servlet. The GBeans started have following pattern j2eeType = ResourceAdapter. I also tried setting resource link to test/jms.rar with same results Error: Unable to distribute wascemq.jar: Unknown resource adapter reference (query=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,j2eeType=JCA ResourceAdapter,name=test/jms.rar,*) I am lost here as to how to fix this. Any ideas or help would be great The RA plan is as follows resourceadapter resourceadapter-instance resourceadapter-nameTestRA/resourceadapter-name workmanager gbean-linkDefaultWorkManager/gbean-link /workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interface/connectionfactory-interface connectiondefinition-instance nameTestFactory/name config-property-setting name=url/config-property-setting config-property-setting name=icf/config-property-setting config-property-setting name=name/config-property-setting connectionmanager no-transaction/ no-pool/ /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter The Geronimo log shows the following GBeans started successfully GBeanInstanceState for: geronimo.config:name=test/jms.rar State changed from starting to running GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,j2eeType=ResourceAdapterModule,name=test/jms.rar State changed from stopped to starting GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,j2eeType=ResourceAdapterModule,name=test/jms.rar State changed from starting to running GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,ResourceAdapter=test/jms.rar,j2eeType=JCAResource,name=test/jms.rar State changed from stopped to starting GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,ResourceAdapter=test/jms.rar,j2eeType=JCAResource,name=test/jms.rar State changed from starting to running GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=test/jms.rar,j2eeType=JCAConnectionManager,name=TestFactory State changed from stopped to starting GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=test/jms.rar,j2eeType=JCAConnectionManager,name=TestFactory State changed from starting to running GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=test/jms.rar,j2eeType=JCAConnectionFactory,name=TestFactory State changed from stopped to starting GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=test/jms.rar,j2eeType=JCAConnectionFactory,name=TestFactory State changed from starting to running GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,ResourceAdapterModule=test/jms.rar,j2eeType=ResourceAdapter,name=test/jms.rar State changed from stopped to starting GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,ResourceAdapterModule=test/jms.rar,j2eeType=ResourceAdapter,name=test/jms.rar State changed from starting to running GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=test/jms.rar,j2eeType=JCAManagedConnectionFactory,name=TestFactory State changed from stopped to starting GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,JCAResource=test/jms.rar,j2eeType=JCAManagedConnectionFactory,name=TestFactory State changed from starting to running Regards Krishnakumar B
Re: Resource Adapter Reference in MDB
hi David, The RA file ?xml version=1.0 encoding=UTF-8? connector xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd; version=1.5 display-nameTestRA/display-name eis-typeTest EIS/eis-type resourceadapter-version1.0/resourceadapter-version resourceadapter outbound-resourceadapter connection-definition managedconnectionfactory-classcom.test.connector.outbound.TestManagedConnectionFactory/managedconnectionfactory-class config-property descriptionjndi provider/description config-property-nameurl/config-property-name config-property-typejava.lang.String/config-property-type /config-property config-property descriptionicf/description config-property-nameicf/config-property-name config-property-typejava.lang.String/config-property-type /config-property config-property descriptionname/description config-property-namename/config-property-name config-property-typejava.lang.String/config-property-type /config-property connectionfactory-interfacecom.test.connector.TestConnectionFactory/connectionfactory-interface connectionfactory-impl-classcom.test.connector.outbound.TestConnectionFactoryImpl/connectionfactory-impl-class connection-interfacecom.test.connector.TestConnection/connection-interface connection-impl-classcom.test.connector.outbound.TestConnectionImpl/connection-impl-class /connection-definition transaction-supportNoTransaction/transaction-support reauthentication-supportfalse/reauthentication-support /outbound-resourceadapter inbound-resourceadapter messageadapter messagelistener messagelistener-typejavax.jms.MessageListener/messagelistener-type activationspec activationspec-classcom.test.connector.inbound.TestActivationSpecImpl/activationspec-class required-config-property config-property-nameurl/config-property-name /required-config-property required-config-property config-property-nameicf/config-property-name /required-config-property required-config-property config-property-namename/config-property-name /required-config-property /activationspec /messagelistener /messageadapter /inbound-resourceadapter /resourceadapter /connector I am using a snapshot version post M5. Regards Krishnakumar B On 12/2/05, David Jencks [EMAIL PROTECTED] wrote: After looking at the code I don't see how this is possible. There's no evidence the ResourceAdapterWrapper gbean is being started. Could you show the ra.xml please? Exactly which version of geronimo are you using? thanks david jencks On Dec 2, 2005, at 1:36 AM, Krishnakumar B wrote: hi, I am trying to get a generic jms resource adapter working. The RA delivers to MDB whose onMessage is activated. The MDB openejb-jar.xml has a resource ref link enterprise-beans message-driven ejb-nameTestMDB/ejb-name resource-adapter resource-linkTestRA/resource-link /resource-adapter /message-driven /enterprise-beans /openejb-jar When deploying this MDB i get the following error. Error: Unable to distribute wascemq.jar: Unknown resource adapter reference (query=geronimo.server: J2EEApplication=null,J2EEServer=geronimo,j2eeType=JCA ResourceAdapter,name=TestRA
Re: Problem in using a security realm added through geronimo console
hi, Check the deployment plan if the references are correct. Sample plan file. gbean name=test-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNametest-realm/attribute reference name=LoginModuleConfiguration nametest-login/name /reference reference name=ServerInfo moduleorg/apache/geronimo/System/module nameServerInfo/name /reference reference name=LoginServicemoduleorg/apache/geronimo/Security/modulenameJaasLoginService/name/reference /gbean gbean name=test-login class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule nametest-login/name /reference /gbean /configuration Regards Krish On 11/29/05, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Here is the description of problem I am facing. I have created a simple web application that uses a FORM authentication method. In the deployment plan, I have configured the application to use geronimo-properties-realm. The application works fine. At this point a added a new realm with name onemore-properties-realm through the Security Realms portlet. I have modified the deployment plan to use this newly added security realm and redeployed the application. The security part of this application does not work anymore. I am getting the following exception on login attempt. 17:41:53,036 INFO [JAASJettyRealm] problem javax.security.auth.login.LoginException: java.lang.NullPointerException: target is null at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicProxyManager.java:104) at org.apache.geronimo.security.jaas.client.JaasLoginCoordinator.connect(JaasLoginCoordinator.java:173) at org.apache.geronimo.security.jaas.client.JaasLoginCoordinator.initialize(JaasLoginCoordinator.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at javax.security.auth.login.LoginContext.invoke(Unknown Source) at javax.security.auth.login.LoginContext.access$000(Unknown Source) at javax.security.auth.login.LoginContext$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokeModule(Unknown Source) at javax.security.auth.login.LoginContext.login(Unknown Source) at org.apache.geronimo.jetty.JAASJettyRealm.authenticate(JAASJettyRealm.java:92) at org.mortbay.jetty.servlet.FormAuthenticator$FormCredential.authenticate(FormAuthenticator.java:305) at org.mortbay.jetty.servlet.FormAuthenticator.authenticate(FormAuthenticator.java:148) at org.apache.geronimo.jetty.interceptor.SecurityContextBeforeAfter.obtainUser(SecurityContextBeforeAfter.java:282) at org.apache.geronimo.jetty.interceptor.SecurityContextBeforeAfter.checkSecurityConstraints(SecurityContextBeforeAfter.java:191) at org.apache.geronimo.jetty.JettyWebAppContext.checkSecurityConstraints(JettyWebAppContext.java:520) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:432) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) at javax.security.auth.login.LoginContext.invoke(Unknown Source) at javax.security.auth.login.LoginContext.access$000(Unknown Source) at javax.security.auth.login.LoginContext$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokeModule(Unknown Source) at javax.security.auth.login.LoginContext.login(Unknown Source) at org.apache.geronimo.jetty.JAASJettyRealm.authenticate(JAASJettyRealm.java:92) at org.mortbay.jetty.servlet.FormAuthenticator$FormCredential.authenticate(FormAuthenticator.java:305) at org.mortbay.jetty.servlet.FormAuthenticator.authenticate(FormAuthenticator.java:148) at
[jira] Created: (GERONIMO-1217) WARN message in console for JMS Server
WARN message in console for JMS Server -- Key: GERONIMO-1217 URL: http://issues.apache.org/jira/browse/GERONIMO-1217 Project: Geronimo Type: Improvement Components: console Versions: 1.0-M5 Reporter: Krishnakumar B Priority: Minor When i click JMS Server in Console JMS Server Manager and Listeners are displayed. The following WARN message is displayed in console and is logged in log file. 11:20:55,076 WARN [BasicProxyManager] Could not load interface org.activemq.gbean.ActiveMQContainer in provided ClassLoader for ActiveMQ 11:20:55,797 WARN [BasicProxyManager] Could not load interface org.activemq.gbean.ActiveMQContainer in provided ClassLoader for ActiveMQ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Query related to JetSpeed and Geronimo
hi, I have Jetspeed-Fusion deployed on Geronimo. this works fine. Jetspeed provides a autoDeploy folder where i can drop JSR-168 portlets and these are picked and automatically deployed. This feature works in Tomcat. Tomcat deploys this war as a web application in webapps folder under TomCat. I am not able to get this to work in Geronimo/Tomcat or Jetty. In Geronimo its not able to pick some jars and i get ClassNotFound Exception. How do i ensure that TomCat/Jetty Classloader picks these jars. These jars are present in jetspeed web applications lib folder. They are available to jetspeed WAR but not for the wars i add to autoDeploy folder ( jaxen jar ) The portlet i add to autoDeploy folder connects to DB using a Datasource. How can i ensure this DataSource is available for the portlet thats deployed as i cant use a Geronimo specific plan. Is it possible to make the autoDeploy feature of jetspeed work on Geronimo? Thanks for any info. Regards Krishnakumar B
[jira] Created: (GERONIMO-1091) Adding a partition to Apache DS with Geronimo
Adding a partition to Apache DS with Geronimo - Key: GERONIMO-1091 URL: http://issues.apache.org/jira/browse/GERONIMO-1091 Project: Geronimo Type: Improvement Components: general Versions: 1.0-M5 Reporter: Krishnakumar B Currently ou=system is available in Apache Directory bundled with M5. Need the ability to create new partitions to add LDAP entries. ( e.g dc=test,dc=com) This is added through property files in Apache DS server.db.partition.suffix.apache=dc=test,dc=com server.db.partition.indices.apache=ou cn objectClass uid server.db.partition.attributes.apache.dc=myhost server.db.partition.attributes.apache.objectClass=top domain extensibleObject This improvement needs to be present in current Gbean for Directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Adding a partition to Apache DS with Geronimo
hi, i am trying to create a new partition with apache DS that comes with geronimo dn: dc=myhost,dc=com dc: myhost objectClass: dcObject The documentation for directory server says to use properties file server.db.partition.suffix.apache=dc=myhost,dc=com server.db.partition.indices.apache=ou cn objectClass uid server.db.partition.attributes.apache.dc=myhost server.db.partition.attributes.apache.objectClass=top domain extensibleObject But i am unable to add this to Apache DS in geronimo. So want to know if this is possible or i can use only ou=system thats created by default. thanks Krish
GBean starting message
Hi, When deploying realms i get Successfullly deployed. When starting the server i get the following message. Warning : some gbens not started successfully. (gbean -name) starting. If i try starting these GBeans using deployer it says already started. These GBeans are in starting state and are not coming to started state. Any idea what the possible reasons? I have posted some ?s related to this in user list. These are primarily realm related GBeans and when i start the server they r always in starting state. Thanks for the help. Regards Krish
MailMessage parse help
hi,
I am trying an application where i run into the following Exception.
java.lang.UnsupportedOperationException: Method not yet implemented
at javax.mail.internet.MimeMessage.parse(MimeMessage.java:194)
at javax.mail.internet.MimeMessage.init(MimeMessage.java:129)
I found this in JIRA http://issues.apache.org/jira/browse/AXIS2-160
and the MimeMessage.parse in code looks like this
protected void parse(InputStream in)
throws MessagingException
{
throw new UnsupportedOperationException(Method not yet implemented);
}
Can anyone help me what i need to do to overcome this error.
I tried adding another implementation of mail.jar but i still get this error.
Thanks for any help.
Regards
Krishnakumar B
Re: [discussion] How do we get help with testing?
1+ for me also. I am also interested in contributions. Regards Krishnakumar B On 9/14/05, Chinthaka Thilakarathna [EMAIL PROTECTED] wrote: here is my +1 really i'm just going to star my particpation with the project. i'd like to try with testing things also. Chin
Getting reference of Jetty server in Geronimo
Hi, I am reposting this to dev group for some help. I need object reference of Jetty Server started in geronimo. Any idea how i can get the same. I am not able to find a Jetty related GBean that gives reference of Server created. thanks for help and ideas. Regards Krish
