[JBoss-dev] Why is this being dumped out?
I have 3.0 server running on my w2k box and by osx box started up its nightly testsuite run. Suddenly is start seeing these errors being dumped out on the w2k box: 00:15:13,515 ERROR [HAJNDI] lookupLocally failed for ejb/EJBTestRunner javax.naming.NameNotFoundException: EJBTestRunner not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) at org.jnp.server.NamingServer.getObject(NamingServer.java:509) at org.jnp.server.NamingServer.lookup(NamingServer.java:282) at org.jnp.server.NamingServer.lookup(NamingServer.java:256) at org.jboss.ha.jndi.HAJNDI.lookupLocally(HAJNDI.java:230) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:174) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ha.framework.server.HARMIServerImpl.invoke(HARMIServerImpl.java:15 8) at java.lang.reflect.Method.invoke(Native Method) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:236) at sun.rmi.transport.Transport$1.run(Transport.java:147) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:143) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:7 01) at java.lang.Thread.run(Thread.java:479) It has not gotten to the clustering tests as yet so why I am seeing this? Scott Stark Chief Technology Officer JBoss Group, LLC ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] EJBObject.remove() on a removed SFSB
I spoke about it two days ago with Bill and I think we have different problems with remove methods. Take the home.remove call on EB: This is transformed in a remote.remove call *inside* the client proxy (trick)! This has two problems: - anyone implementing server side interceptors won't be able to intercept this call has a home invocation and will not be able to differentiate home.remove calls from remote.remote calls. - when the pk no more exists, home.remove(pk) should simply raise an NoSuchObjectException. That is absolutely not the case right now. Right now: - the transaction is rollbacked!!! - the excetpion is wrapped in a TransactionRollbackedException! to test this behaviour, simply add something like this for a test: myHome.remove (1); myHome.remove (1); Depending if a bean with pk=1 existed, either the first or the second call will abruptly fail. I've seen that no test covers this case in the testsuite. IMHO, the client proxy shouldn't reinterpret the home.remove(pk) in remote.remove(). Cheers, Sacha > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de > Scott M Stark > Envoyé : jeudi, 23 mai 2002 08:57 > À : [EMAIL PROTECTED] > Objet : Re: [JBoss-dev] EJBObject.remove() on a removed SFSB > > > There should be a java.rmi.NoSuchObjectException: > > When the client calls remove on the home or component interface to remove > the session > object, the container issues ejbRemove() on the bean instance. > This ends the > life of the session > bean instance and the associated session object. Any subsequent attempt by > its client to > invoke the session object causes the java.rmi.NoSuchObjectException to be > thrown > if the client is a remote client, or the > javax.ejb.NoSuchObjectLocalException if > the client is a local client. (The java.rmi.NoSuchObjectException is a > subclass of > the java.rmi.RemoteException; the javax.ejb.NoSuchObjectLocalException > is a subclass of the javax.ejb.EJBException). The ejbRemove() method > cannot be called when the instance is participating in a transaction. An > attempt to remove a > session object while the object is in a transaction will cause > the container > to throw the > javax.ejb.RemoveException to the client. Note that a container can also > invoke the > ejbRemove() method on the instance without a client call to remove the > session object > after the lifetime of the EJB object has expired. > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > - Original Message - > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, May 21, 2002 7:35 PM > Subject: [JBoss-dev] EJBObject.remove() on a removed SFSB > > > Should calling EJBObject.remove() on a SFSB which has been removed already > throw an exception or should the request be silently ignored? > > I was running into a problem which was due to one of my > finializers removing > a > SFSB, which I had previously removed and forgot to null. Currently when > this > happens an erronious activation exception is thrown, since there > is no state > file for the bean (having been removed already). > > I think it would be a good idea to throw a meaningful exception in > StatefulSessionContainer.remove() to indicate the illegal state... unless > the > spec says we should ignore this. I have not checked the spec. > The Javadoc > for EJBObject.remove() does not provide any insight either. > > Does anyone know what the behavior should be, exception or non-exception? > And > if it is an exception what flavor? > > --jason > > > > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] StatefulSessionPersistenceManager.createSession()
The container would then have to know how to create unique session keys for the store which is something it should not have to know how to do. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 7:44 PM Subject: [JBoss-dev] StatefulSessionPersistenceManager.createSession() Any reason why this method defined in the PM interface? The one instance of StatefulSessionPersistenceManager (StatefulSessionFilPersistenceManager) does not really do anything file specific... and I can not really see why any other impl which have to do anything specific on creation here either... unless that is I am missing something. Am I? Or does it make more sence to move createSession() into the container impl, so the pm impl can be freed from this seeminly unrelated burden? --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] EJBObject.remove() on a removed SFSB
There should be a java.rmi.NoSuchObjectException: When the client calls remove on the home or component interface to remove the session object, the container issues ejbRemove() on the bean instance. This ends the life of the session bean instance and the associated session object. Any subsequent attempt by its client to invoke the session object causes the java.rmi.NoSuchObjectException to be thrown if the client is a remote client, or the javax.ejb.NoSuchObjectLocalException if the client is a local client. (The java.rmi.NoSuchObjectException is a subclass of the java.rmi.RemoteException; the javax.ejb.NoSuchObjectLocalException is a subclass of the javax.ejb.EJBException). The ejbRemove() method cannot be called when the instance is participating in a transaction. An attempt to remove a session object while the object is in a transaction will cause the container to throw the javax.ejb.RemoveException to the client. Note that a container can also invoke the ejbRemove() method on the instance without a client call to remove the session object after the lifetime of the EJB object has expired. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 7:35 PM Subject: [JBoss-dev] EJBObject.remove() on a removed SFSB Should calling EJBObject.remove() on a SFSB which has been removed already throw an exception or should the request be silently ignored? I was running into a problem which was due to one of my finializers removing a SFSB, which I had previously removed and forgot to null. Currently when this happens an erronious activation exception is thrown, since there is no state file for the bean (having been removed already). I think it would be a good idea to throw a meaningful exception in StatefulSessionContainer.remove() to indicate the illegal state... unless the spec says we should ignore this. I have not checked the spec. The Javadoc for EJBObject.remove() does not provide any insight either. Does anyone know what the behavior should be, exception or non-exception? And if it is an exception what flavor? --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] UDS & DeployedURL.watchedUrl
This is not very likly to work when the DeploymentCache is in play... unless the Deployer interface is changed to include the method getWatchURL()... but that would not make much sence, since this is more of a SubDeployer related item and does not belong in the Deployer interface. Anyways, whatever for now... but it would be nice to see this hack put to rest once the deployment system has been revisted. --jason On Tuesday 21 May 2002 07:40 am, Larry Sandereson wrote: > This sounds like something I added for exploded deployments. (the url to > watch for redeployment is the app-specific xml: ejb-jar.xml for ejbs, > application.xml for ears, ...) It is an MBean operation in MainDeployer > that returns the corresponding DeploymentInfo's watch field. > > -Larry > > > Can someone please explain to me what DeployedURL.watchedUrl is for? > > > > --jason > > > > - > > This mail sent through IMP: http://horde.org/imp/ > > > > ___ > > > > Don't miss the 2002 Sprint PCS Application Developer's Conference > > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] StatefulSessionPersistenceManager.createSession()
Any reason why this method defined in the PM interface? The one instance of StatefulSessionPersistenceManager (StatefulSessionFilPersistenceManager) does not really do anything file specific... and I can not really see why any other impl which have to do anything specific on creation here either... unless that is I am missing something. Am I? Or does it make more sence to move createSession() into the container impl, so the pm impl can be freed from this seeminly unrelated burden? --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] EJBObject.remove() on a removed SFSB
Should calling EJBObject.remove() on a SFSB which has been removed already throw an exception or should the request be silently ignored? I was running into a problem which was due to one of my finializers removing a SFSB, which I had previously removed and forgot to null. Currently when this happens an erronious activation exception is thrown, since there is no state file for the bean (having been removed already). I think it would be a good idea to throw a meaningful exception in StatefulSessionContainer.remove() to indicate the illegal state... unless the spec says we should ignore this. I have not checked the spec. The Javadoc for EJBObject.remove() does not provide any insight either. Does anyone know what the behavior should be, exception or non-exception? And if it is an exception what flavor? --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
> the problem. The only issue I see is that the initial startup info > including the > loading of the lib jars is not showing up in the server.log. I think this is minor and could change if we fix up how the core service framework operates. No matter what we do there will always be some space between the core setup and when we can start logging... but if the user really wants this logged to a file, they can provide a custom log4j.properties. > There is also this message on the console at the end of shutdown: > [INFO,Log4jService] Stopping > log4j:ERROR No appenders could be found for category > (org.jboss.logging.Log4jService). > log4j:ERROR Please initialize the log4j system properly. > > because ServiceMBeanSupport is logging after the Log4jService shtudown > Category. Lets not shutdown Log4j then... why could I want todo this anyways? --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
The problem isn't the URLCL vs UCL loader issue at this point. The problem is that there is nothing in the UCL repository as you say. Therefore it makes no sense to intialize the Log4jService as this point. Just moving the Log4jService setup to the core conf/jboss-service.xml descriptor and out of ServerImpl solves the problem. The only issue I see is that the initial startup info including the loading of the lib jars is not showing up in the server.log. There is also this message on the console at the end of shutdown: [INFO,Log4jService] Stopping log4j:ERROR No appenders could be found for category (org.jboss.logging.Log4jService). log4j:ERROR Please initialize the log4j system properly. because ServiceMBeanSupport is logging after the Log4jService shtudown Category. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Scott M Stark" <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 10:59 AM Subject: Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x Ok, I understand more now... though you know that log4j.properties is going to be used even before ServerImpl gets created right... It looks like the UCL bits should be operable at the time when Log4jService is created... the TCL is set right before it is started. But I would guess (since I am not a CL expert) that since we have not processed the classpath element from jboss-service.xml, we have not populated the UCL repo with anything useful, short of the conf directory (as set by ServerImpl.initBootLibraries()). If there were UCL's for each registered boot library, would the UCL be used, or would the URLCL be used? If the UCL will be used, then what problems would arise if we either installed a UCL for each URLCL, or rather than using a URLCL, use a boot strap UCL, which will only load the required boot classes from the URLCL, then once the repo is active will force all classes to go through it. This will mean that classes loaded on the URLCL will be serialized right... but we don't really care too much about that. If the above makes sence, then I think it would be worth the effort to implement that rather than add to the logging configuration complexity... but I am not sure if the above will work. --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-559448 ] XAConnectionImpl - constructor change
Patches item #559448, was opened at 2002-05-23 02:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=559448&group_id=22866 Category: JBossCX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jim Cook (oravecz) Assigned to: Nobody/Anonymous (nobody) Summary: XAConnectionImpl - constructor change Initial Comment: There will be people who need to provide their own XADataSourceImpl implementation in order to retrieve an XAConnection suitable for use by the pooling mechanism. In order to properly manage the return of a connection to a pool, the connection is wrapped in the existing XAConnectionImpl class, however the constructor for this class requires an XAResourceImpl. The XAResourceImpl is a wrapper class for non-XA connections and it implements the XAResource interface. When using true XAConnection objects, a "real" XAResource is available so there is no need for the wrapper. I have modified the constructor of XAConnectionImpl to accept the XAResource interface in place of the XAResourceImpl class. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=559448&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559441 ] Local DB Connections broken
Bugs item #559441, was opened at 2002-05-23 11:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=559441&group_id=22866 Category: JBossCX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) Assigned to: Nobody/Anonymous (nobody) Summary: Local DB Connections broken Initial Comment: A configuration that I've been using for sometime that uses the Oracle drivers has stopped working after checking out the latest Branch_3_0 from CVS. The problem disappears if I revert back to the JBoss_3_0_0_RC3 branch, so it's broken recently. I now get the following exceptions when deploying my ejb jar: 10:47:50,595 ERROR [EjbModule] Initialization failed org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: No suitable driver); - nested throwable: (org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: No suitable driver))) at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(S QLUtil.java:67) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridg e.(JDBCEntityBridge.java:103) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.cre ate(JDBCStoreManager.java:333) at org.jboss.ejb.plugins.CMPPersistenceManager.create( CMPPersistenceManager.java:155) at org.jboss.ejb.EntityContainer.create(EntityContainer.jav a:337) at org.jboss.ejb.Container.invoke(Container.java:789) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.jav a:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invok e(ServiceController.java:867) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceContr oller.java:271) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invo ke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java: 174) at $Proxy17.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java: 392) at org.jboss.system.ServiceMBeanSupport.create(Service MBeanSupport.java:134) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invo ke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invok e(ServiceController.java:867) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceContr oller.java:271) at org.jboss.system.ServiceController.create(ServiceContr oller.java:211) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invo ke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java: 174) at $Proxy5.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:38 0) at org.jboss.deployment.MainDeployer.create(MainDeploy er.java:651) at org.jboss.deployment.MainDeployer.deploy(MainDeploy er.java:526) at org.jboss.deployment.MainDeployer.deploy(MainDeploy er.java:490) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invo ke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java: 174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner. deploy(URLDeploymentScanner.java:405) at org.jboss.deployment.scanner.URLDeploymentScanner. scanDirectory(URLDeploymentScanner.java:586) at org.jboss.deployment.scanner.URLDeploymentScanner. scan(URLDeploymentScanner.java:465) at org.jboss.deployment.scanner.AbstractDeploymentSca nner$ScannerThread.loop(AbstractDeploymentScanner .java:202) at org.jboss.deployment.scanner.AbstractDeploymentSca nner$ScannerThread.run(AbstractDeploymentScanner.j ava:191) org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: No suitable driver); - nested throwable: (org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: No suitable driver)) at org.jboss.resource.adapter.jdbc.local.LocalDataSource
[JBoss-dev] Foe-Deployer Release I
Hi Geeks Alex Loubyansky wrote the WebLogic Convertor this weekend and I incorporated it today. It already contains support for other application servers (see Convertor). To use it please take the "foe-deployer.sar" file from "/varia/output/lib" and put it into the deployement directory and deploy a WebLogic application to the deploy directory (ATTENTION: you have it to rename to "*.wlar" (note: WLAR) therefore the Foe Deployer will pick it up. This will be fixed soon. Tomorrow I will add an example to the testsuite. Have fun x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 23-May-2002
I have a fix for this coming soon. --jason On Wednesday 22 May 2002 05:11 pm, Scott M Stark wrote: > There are numerous errors like the following in the server log: > > 2002-05-23 00:22:32,880 ERROR [org.jboss.ejb.EntityContainer] > Initialization failed > org.jboss.deployment.DeploymentException: Error while fixing table name; - > nested throwable: (org.jboss.util.NestedSQLException: Could not create > connection; - nested throwable: (javax.resource.ResourceException: Could > not create connection)) > at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:67) > at > org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntityBri >d ge.java:103) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.jav >a > > :333) > > at > org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.ja >v a:155) > at org.jboss.ejb.EntityContainer.createService(EntityContainer.java:318) > at > org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:170) > at org.jboss.ejb.Container.invoke(Container.java:778) > at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1024) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.ja >v a:867) > at $Proxy19.create(Unknown Source) > at org.jboss.system.ServiceController.create(ServiceController.java:271) > at java.lang.reflect.Method.invoke(Native Method) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispa >t cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > at $Proxy47.create(Unknown Source) > at org.jboss.ejb.EjbModule.createService(EjbModule.java:390) > at > org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:170) > at java.lang.reflect.Method.invoke(Native Method) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispa >t cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.ja >v a:867) > at $Proxy19.create(Unknown Source) > at org.jboss.system.ServiceController.create(ServiceController.java:271) > at org.jboss.system.ServiceController.create(ServiceController.java:211) > at java.lang.reflect.Method.invoke(Native Method) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispa >t cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > at $Proxy5.create(Unknown Source) > at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:378) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:646) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:521) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:489) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:472) > at java.lang.reflect.Method.invoke(Native Method) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispa >t cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at > org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl.invoke(RMIAdaptorImpl.java:265) at > java.lang.reflect.Method.invoke(Native Method) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:242) > at sun.rmi.transport.Transport$1.run(Transport.java:155) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:152) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:462) at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java: >6 62) > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > - Original Message - > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, May 22, 2002 4:46 PM > Subject: [JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 23-May-2002 > > > Number of tests run: 737 > > > > > > > > Successful tests: 576 > > Errors:155 > > Failures: 6 > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm __
Re: [JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 23-May-2002
There are numerous errors like the following in the server log: 2002-05-23 00:22:32,880 ERROR [org.jboss.ejb.EntityContainer] Initialization failed org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (javax.resource.ResourceException: Could not create connection)) at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:67) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntityBrid ge.java:103) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java :333) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.jav a:155) at org.jboss.ejb.EntityContainer.createService(EntityContainer.java:318) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:170) at org.jboss.ejb.Container.invoke(Container.java:778) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1024) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:867) at $Proxy19.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:271) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy47.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:390) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:170) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:867) at $Proxy19.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:271) at org.jboss.system.ServiceController.create(ServiceController.java:211) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:378) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:646) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:521) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:489) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:472) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl.invoke(RMIAdaptorImpl.java:265) at java.lang.reflect.Method.invoke(Native Method) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:242) at sun.rmi.transport.Transport$1.run(Transport.java:155) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:152) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:462) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:6 62) Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 4:46 PM Subject: [JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 23-May-2002 > > Number of tests run: 737 > > > > Successful tests: 576 > Errors:155 > Failures: 6 > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Problem with LMCF changes to use DriverManager
I updated my Branch_3_0 workspace today, rebuilt and found that code that worked yesterday stopped functioning today. Looks like the change to LMCF to use DriverManager is now having trouble finding my jdbc driver (oracle.jbdc.driver.OracleDriver). Below is the trace with the SQLException omitted: Caused by: org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: No suitable driver) at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:132) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnection(InternalManagedConnectionPool.java:236) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:101) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:312) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:440) at org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:221) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:504) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:101) ... 40 more Caused by: java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(DriverManager.java:532) at java.sql.DriverManager.getConnection(DriverManager.java:140) at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:116) ... 47 more I did not change my config for the datasource at all... I am guessing that the LMCF thinks the driver is valid (found the class), since checkDriver did not barf, but instead DriverManager did. VM version info: 12:48:35,693 INFO [ServerInfo] Java version: 1.4.0,Sun Microsystems Inc. 12:48:35,694 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc. 12:48:35,694 INFO [ServerInfo] OS-System: Linux 2.4.18-4,i386 So, assuming there is not a change to the config (I am using a modified oracle-service.xml from the jca examples)... how do I get DriverManager to be happy with my driver? --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 23-May-2002
Number of tests run: 737 Successful tests: 576 Errors:155 Failures: 6 [time of test: 23 May 2002 0:44 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] Useful resources: - http://lubega.com/testarchive/ibm_jdk13_20010626 for the junit report of this test. - http://lubega.com/testarchive/ibm_jdk13_20010626/logs/ for the logs for this test. - http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Deflating (or creating) a JAR file from aDirecto ry
http://developer.java.sun.com/developer/technicalArticles/Programming/compre ssion/ -Original Message- From: Andreas Schaefer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 2:42 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Deflating (or creating) a JAR file from a Directory Hi Geeks Before I am wasting a lot of time: Does anyone know or know an article how to create the same behaviour programmatically what the JAR tool does ? Thanx x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
Yes, just moving Log4jService is enough. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Scott M Stark" <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 11:08 AM Subject: Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x Do we have to do anything short of move the Log4jService into jboss-service.xml to make this happen? The first time Category/Logger is loaded, it will automatically configure with log4j.properties found in run.jar, thus giving us logging with no real effort short of providing a log4j.properties file. ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
Do we have to do anything short of move the Log4jService into jboss-service.xml to make this happen? The first time Category/Logger is loaded, it will automatically configure with log4j.properties found in run.jar, thus giving us logging with no real effort short of providing a log4j.properties file. The only down side is that there will be short period of core system loading (system deployers and service controller) which will never make it in to sever.log, as log4j.properties has no idea where that file will be. This might not be a big issue in the long run, as I think that we could probably move most of those into jboss-service.xml, once we have the service framework and dependency stuff fixed up. Anyways, any reason why we need to explicitly load the root category from ServerImpl and not let the framework deal with that by itself? --jason On Wednesday 22 May 2002 03:00 pm, Scott M Stark wrote: > The simplest solution is to simply load the root category in > the ServerImpl code rather than create the Log4jService, and > then add the Log4jService to the conf/jboss-service.xml core > services setup. This does bootstrap off of the jndi.properties > file and then reinitializes using the log4j.xml file. > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Deflating (or creating) a JAR file from a Directory
ant. Use the Source! -danch Andreas Schaefer wrote: > Hi Geeks > > Before I am wasting a lot of time: Does anyone > know or know an article how to create the same > behaviour programmatically what the JAR tool > does ? > > Thanx > > x > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > x > > > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Deflating (or creating) a JAR file from a Directory
There is a simple Jar utility in our codebase under common: org.jboss.util.file.JarUtils It depends on how much of the jar tool functionality you need. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Andreas Schaefer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 2:42 PM Subject: [JBoss-dev] Deflating (or creating) a JAR file from a Directory > Hi Geeks > > Before I am wasting a lot of time: Does anyone > know or know an article how to create the same > behaviour programmatically what the JAR tool > does ? > > Thanx > > x > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > x > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
Ok, I understand more now... though you know that log4j.properties is going to
be used even before ServerImpl gets created right...
It looks like the UCL bits should be operable at the time when Log4jService is
created... the TCL is set right before it is started. But I would guess
(since I am not a CL expert) that since we have not processed the classpath
element from jboss-service.xml, we have not populated the UCL repo with
anything useful, short of the conf directory (as set by
ServerImpl.initBootLibraries()).
If there were UCL's for each registered boot library, would the UCL be used,
or would the URLCL be used?
If the UCL will be used, then what problems would arise if we either installed
a UCL for each URLCL, or rather than using a URLCL, use a boot strap UCL,
which will only load the required boot classes from the URLCL, then once the
repo is active will force all classes to go through it. This will mean that
classes loaded on the URLCL will be serialized right... but we don't really
care too much about that.
If the above makes sence, then I think it would be worth the effort to
implement that rather than add to the logging configuration complexity... but
I am not sure if the above will work.
--jason
On Wednesday 22 May 2002 02:43 pm, Scott M Stark wrote:
> Yes log4j.xml is being used because the Log4jService is created by
> the ServerImpl:
>
> ServerImpl.java:
> // Setup logging
> server.createMBean("org.jboss.logging.Log4jService", null);
> log.debug("Logging has been initialized");
>
> and when JMX calls preRegister the Log4jService is calling its create
> and start which use the configURL==log4j.xml by default.
>
> Log4jService.java:
>public ObjectName preRegister(MBeanServer server, ObjectName name)
> throws Exception
>{
> name = super.preRegister(server, name);
> create();
> start();
> return name;
>}
>
> This is what this stack trace shows. I created a patched version of
> DOMConfigurator
> and it is being called to parse the log4j.xml file during the boot
> sequence:
>
> log4j: Attaching appender named [ErrorNotifications] to appender named
> [ASYNCH].
>
> log4j: Class name: [org.apache.log4j.net.SMTPAppender]
> [WARN,BasicMBeanRegistry] preRegister() failed for null:
> java.lang.NoClassDefFoundError: javax/mail/Multipart
> at java.lang.Class.newInstance0(Native Method)
> at java.lang.Class.newInstance(Class.java:232)
> at
> org.jboss.logging.DOMConfigurator.parseAppender(DOMConfigurator.java:162)
> at
> org.jboss.logging.DOMConfigurator.findAppenderByReference(DOMConfigurator.j
>a va:146)
> at
> org.jboss.logging.DOMConfigurator.parseAppender(DOMConfigurator.java:199)
> at
> org.jboss.logging.DOMConfigurator.findAppenderByReference(DOMConfigurator.j
>a va:146)
> at
> org.jboss.logging.DOMConfigurator.parseChildrenOfCategoryElement(DOMConfigu
>r ator.java:365)
> at
> org.jboss.logging.DOMConfigurator.parseRoot(DOMConfigurator.java:334)
>
> at
> org.jboss.logging.DOMConfigurator.parse(DOMConfigurator.java:699) at
> org.jboss.logging.DOMConfigurator.doConfigure(DOMConfigurator.java:599)
> at
> org.jboss.logging.DOMConfigurator.doConfigure(DOMConfigurator.java:551)
> at
> org.jboss.logging.DOMConfigurator.configure(DOMConfigurator.java:621)
> at
> org.jboss.logging.Log4jService$URLWatchTimerTask.reconfigure(Log4jService.j
>a va:487)
> at
> org.jboss.logging.Log4jService$URLWatchTimerTask.run(Log4jService.java:436)
> at
> org.jboss.logging.Log4jService.startService(Log4jService.java:280)
> at
> org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
> at
> org.jboss.logging.Log4jService.preRegister(Log4jService.java:361) at
> org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanReg
>i stry.java:197)
> at
> org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:949)
> at
> org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:247)
> at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:263)
> at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
> at org.jboss.Main.boot(Main.java:142)
> at org.jboss.Main$1.run(Main.java:375)
> at java.lang.Thread.run(Thread.java:479)
> [INFO,Log4jService] Registration is not done -> destroy
>
>
> - Original Message -
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; "Scott M Stark"
> <[EMAIL PROTECTED]>
> Sent: Tuesday, May 21, 2002 10:29 AM
> Subject: Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
>
>
> I am still confused about this... for boot, log4j.xml is not used,
> log4j.properties are used. Can you explain... I am a little slow after
> spending several days in corporate code =|
>
> --jason
>
>
>
>
>
>
> ___
>
> Don't miss
Re: [JBoss-dev] Going to log4j 1.2.2 for 3.x
The simplest solution is to simply load the root category in the ServerImpl code rather than create the Log4jService, and then add the Log4jService to the conf/jboss-service.xml core services setup. This does bootstrap off of the jndi.properties file and then reinitializes using the log4j.xml file. Scott Stark Chief Technology Officer JBoss Group, LLC ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Deflating (or creating) a JAR file from a Directory
Hi Geeks Before I am wasting a lot of time: Does anyone know or know an article how to create the same behaviour programmatically what the JAR tool does ? Thanx x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] The method return values in the home interface must be of valid t ypes for RMI/IIOP
Post a bug to sourceforge. Cheers > > From: Mahesh Agarwal <[EMAIL PROTECTED]> > Date: 2002/05/22 Wed PM 04:09:57 EDT > To: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED] > Subject: [JBoss-dev] The method return values in the home interface must be of valid >t > ypes for RMI/IIOP > > Hi All > > I am getting a warning while deploying the ejbs in JBOss. Can anyone please > help? > > Bean : OrgMgr > Method : public abstract OrgMgr create() throws CreateException, > EJBException, RemoteException > Section: 6.10.6 > Warning: The method return values in the home interface must be of valid > types for RMI/IIOP. > > Thanks > Mahesh > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Integrating JBoss with CapeConnect
I like to apologies for cross posting here but
wasn’t quiet sure where this really belonged. Someone posted a question
to the Cape Clear bulletin board wondering how to
integrate CapeConnect Web Services server with the JBoss application server? I
have reproduced here a brief howto to get anyone who is interested started.
Yes we have integrated Connect with JBoss and here are
some docs to get you started,
1. Add this entry to your servermap.xml, which can be
found in %CAPECONNECT_HOME%\xmlengine\conf directory, specify the correct path
to the
client libraries on your machine
JBoss
server settings
name="java.naming.factory.initial"
value="org.jnp.interfaces.NamingContextFactory"/>
name="C:\appserver\jboss-3.0.0RC1_tomcat-4.0.3\client\jboss-client.jar"/>
2.Add to following lines to the
%CAPECONNECT_HOME%\xmlengine\conf\server.policy file:
grant{
permission
java.security.AllPermission;
};
To test do the following:
3.Deploy
%CAPECONNECT_HOME%\demos\j2ee\cc-j2ee\hello\lib\hello-cc.jar into JBoss by
simply dropping it into JBoss the deploy dir,
4. In the CapeConnect console, goto Edit->Web
Service Setting and change the server setting for hello-cc entry to use JBOSS
You should then be
able to invoke the stateless session bean from JBoss as a Web Service.
If
you have any more question please contact me
Eoin
--
Eoin Lane (PhD)
Technical Analyst
NEW CapeStudio 3, out now
Design, develop, integrate & deploy Web Services http://www.capeclear.com/download
RE: [JBoss-dev] CD SUBSCRIPTION
right... it costs $1000 per year, and we start this program with an ooops marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of James |Ward |Sent: Wednesday, May 22, 2002 1:25 PM |To: [EMAIL PROTECTED]; Jboss-User@Lists. |Sourceforge. Net |Subject: RE: [JBoss-dev] CD SUBSCRIPTION | | |Great Idea!!! | |How much does it cost? | |-James | | |> -Original Message- |> From: marc fleury [mailto:[EMAIL PROTECTED]] |> Sent: Wednesday, May 22, 2002 2:22 PM |> To: Jboss-Development@Lists. Sourceforge. Net; Jboss-User@Lists. |> Sourceforge. Net |> Subject: [JBoss-dev] CD SUBSCRIPTION |> |> Folks, |> |> By public demand we will now distribute a subscription CD. This CD is |> meant |> for people who don't want to wait for large downloads to complete from |> SourceForge and want the latest and greatest of JBoss delivered to |their |> door every 3 months directly from JBossGroup. Don't wait to take |advantage |> of this offer, and remember any subscription you take helps support |> another |> JBoss developer full time in open source, so this is money that will |not |> go |> into corporate fat but into one big fat red-pill. Do yourself a favor, |> subscribe to JBossCD. mailto:[EMAIL PROTECTED]?subject=Subscription |> |> CD Includes: |> |> -- Integrated graphical installer. |> Make your life easier with this graphical or console based installer. |> |> -- 2 hours email consulting/support. |> This alone make the CD worthwhile, no other package is this small. |> Discuss |> your problems with a core JBoss developer. A support engineer will |> provide |> you with support on whichever version and configuration of JBoss you |> choose. |> No other company offers this type of support. Guaranteed response |within |> 48 |> hours. 30 minutes increments per incident. Email support only. |> |> -- A CD mailed to your door every 3 months. |> Four CDs over a one-year span. All versions and bundles of JBoss will |be |> included. JBoss 2.4.x, 3.x, and beyond. Binary and source format. |> |> -- JBoss documentation subscription. |> This year-long documentation subscription is a $120 value. |Documentation |> includes the PDF version of JBoss's SAMs publication as well as all |> up-to-date 3.0 for-pay docs(clustering, CMP 2.0, etc.). |> |> -- 10% off JBoss Training. |> Get this one-time discount to the next JBoss Training course. This is |a |> $300 value. |> |> |> Don't miss out on this great offer. |> mailto:[EMAIL PROTECTED]?subject=Subscription |> |> marcf |> |> x |> Marc Fleury, Ph.D |> President |> JBoss Group, LLC |> x |> |> x |> Marc Fleury, Ph.D |> President |> JBoss Group, LLC |> x |> |> |> |> ___ |> |> Don't miss the 2002 Sprint PCS Application Developer's Conference |> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm |> |> ___ |> Jboss-development mailing list |> [EMAIL PROTECTED] |> https://lists.sourceforge.net/lists/listinfo/jboss-development | |___ | |Don't miss the 2002 Sprint PCS Application Developer's Conference |August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CD SUBSCRIPTION
Great Idea!!! How much does it cost? -James > -Original Message- > From: marc fleury [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 22, 2002 2:22 PM > To: Jboss-Development@Lists. Sourceforge. Net; Jboss-User@Lists. > Sourceforge. Net > Subject: [JBoss-dev] CD SUBSCRIPTION > > Folks, > > By public demand we will now distribute a subscription CD. This CD is > meant > for people who don't want to wait for large downloads to complete from > SourceForge and want the latest and greatest of JBoss delivered to their > door every 3 months directly from JBossGroup. Don't wait to take advantage > of this offer, and remember any subscription you take helps support > another > JBoss developer full time in open source, so this is money that will not > go > into corporate fat but into one big fat red-pill. Do yourself a favor, > subscribe to JBossCD. mailto:[EMAIL PROTECTED]?subject=Subscription > > CD Includes: > > -- Integrated graphical installer. > Make your life easier with this graphical or console based installer. > > -- 2 hours email consulting/support. > This alone make the CD worthwhile, no other package is this small. > Discuss > your problems with a core JBoss developer. A support engineer will > provide > you with support on whichever version and configuration of JBoss you > choose. > No other company offers this type of support. Guaranteed response within > 48 > hours. 30 minutes increments per incident. Email support only. > > -- A CD mailed to your door every 3 months. > Four CDs over a one-year span. All versions and bundles of JBoss will be > included. JBoss 2.4.x, 3.x, and beyond. Binary and source format. > > -- JBoss documentation subscription. > This year-long documentation subscription is a $120 value. Documentation > includes the PDF version of JBoss's SAMs publication as well as all > up-to-date 3.0 for-pay docs(clustering, CMP 2.0, etc.). > > -- 10% off JBoss Training. > Get this one-time discount to the next JBoss Training course. This is a > $300 value. > > > Don't miss out on this great offer. > mailto:[EMAIL PROTECTED]?subject=Subscription > > marcf > > x > Marc Fleury, Ph.D > President > JBoss Group, LLC > x > > x > Marc Fleury, Ph.D > President > JBoss Group, LLC > x > > > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] The method return values in the home interface mustbe of valid t ypes for RMI/IIOP
I got that error and the cause was unrelated. I had a method in my remote interface that didn't declare one of the exceptions that was being thrown from the corresponding bean implementation. It's probably a bad error message in the validator. On Wed, 2002-05-22 at 14:09, Mahesh Agarwal wrote: > Hi All > > I am getting a warning while deploying the ejbs in JBOss. Can anyone please > help? > > Bean : OrgMgr > Method : public abstract OrgMgr create() throws CreateException, > EJBException, RemoteException > Section: 6.10.6 > Warning: The method return values in the home interface must be of valid > types for RMI/IIOP. > > Thanks > Mahesh > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CD SUBSCRIPTION
Folks, By public demand we will now distribute a subscription CD. This CD is meant for people who don't want to wait for large downloads to complete from SourceForge and want the latest and greatest of JBoss delivered to their door every 3 months directly from JBossGroup. Don't wait to take advantage of this offer, and remember any subscription you take helps support another JBoss developer full time in open source, so this is money that will not go into corporate fat but into one big fat red-pill. Do yourself a favor, subscribe to JBossCD. mailto:[EMAIL PROTECTED]?subject=Subscription CD Includes: -- Integrated graphical installer. Make your life easier with this graphical or console based installer. -- 2 hours email consulting/support. This alone make the CD worthwhile, no other package is this small. Discuss your problems with a core JBoss developer. A support engineer will provide you with support on whichever version and configuration of JBoss you choose. No other company offers this type of support. Guaranteed response within 48 hours. 30 minutes increments per incident. Email support only. -- A CD mailed to your door every 3 months. Four CDs over a one-year span. All versions and bundles of JBoss will be included. JBoss 2.4.x, 3.x, and beyond. Binary and source format. -- JBoss documentation subscription. This year-long documentation subscription is a $120 value. Documentation includes the PDF version of JBoss's SAMs publication as well as all up-to-date 3.0 for-pay docs(clustering, CMP 2.0, etc.). -- 10% off JBoss Training. Get this one-time discount to the next JBoss Training course. This is a $300 value. Don't miss out on this great offer. mailto:[EMAIL PROTECTED]?subject=Subscription marcf x Marc Fleury, Ph.D President JBoss Group, LLC x x Marc Fleury, Ph.D President JBoss Group, LLC x ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] The method return values in the home interface must be of valid types for RMI/IIOP
Hi All I am getting a warning while deploying the ejbs in JBOss. Can anyone please help? Bean : OrgMgr Method : public abstract OrgMgr create() throws CreateException, EJBException, RemoteException Section: 6.10.6 Warning: The method return values in the home interface must be of valid types for RMI/IIOP. Thanks Mahesh ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Jboss site down again, restarting
Out of threads again with many connections: [starksm@main starksm]$ netstat -an | grep -c 8080 1319 [starksm@main starksm]$ [14:05:23,867,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:28,258,JettyService] OK on threads: [EMAIL PROTECTED]:8080 [14:05:41,640,JettyService] LOW ON THREADS: [EMAIL PROTECTED]:8080 [14:05:41,642,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:44,384,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:44,640,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:44,767,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:50,155,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:50,575,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [14:05:51,105,JettyService] WARNING: OUT OF THREADS: [EMAIL PROTECTED]:8080 [starksm@main log]$ ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-555381 ] Deployment problem
Bugs item #555381, was opened at 2002-05-13 05:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=555381&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Laurence Smith (lasmith) Assigned to: Nobody/Anonymous (nobody) Summary: Deployment problem Initial Comment: I am having trouble deploying ear files to JBoss 3.0 rc1 running on Windows 2000 sun jdk 1.3.1. The autodeployer is failing to deploy my ear file giving the following exception: 2002-05-13 10:59:55,746 ERROR [org.jboss.deployment.MainDeployer] Couldn't deploy URL file:/C:/jboss- 3.0.0RC1/server/default/deploy/FordCredit.ear org.jboss.deployment.DeploymentException: url file:/C:/jboss- 3.0.0RC1/server/default/deploy/FordCredit.ear could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo. (DeploymentInfo.java:171) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:469) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke (ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:492) at org.jboss.util.jmx.MBeanProxy.invoke (MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deplo y(URLDeploymentScanner.java:350) at org.jboss.deployment.scanner.URLDeploymentScanner.scanD irectory(URLDeploymentScanner.java:530) at org.jboss.deployment.scanner.URLDeploymentScanner.scan (URLDeploymentScanner.java:410) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ ScannerThread.loop(AbstractDeploymentScanner.java:202) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ ScannerThread.run(AbstractDeploymentScanner.java:191) I believe the problem to be the fact the EAR file is quite large. It is also being copied over a network to the deploy directory, which may take > 5 seconds. I think JBoss is trying to start the deployment BEFORE the file has been copied completely. Which is why it asks if it exists. Im not sure if this is problem with JBoss internal setting or one that can be set with an external configuration file?? When I restart JBoss the file is deployed without error. Or if I copy the file from a local directory to the deploy directory (ie/ so it is copied quickly) then it also works fine. -- Comment By: Steve Wolfangel (swolfangel) Date: 2002-05-22 13:16 Message: Logged In: YES user_id=541224 I am seeing a similar problem with 3.0Beta. I was able to deploy my ear in previous 3.0 versions but not with the beta. Here is an example message when starting the server. 12:58:21,867 WARN [MainDeployer] The manifest entry in file:/D:/jboss/server30/jboss- 3.0.0beta/tmp/deploy/72.MetadataServerAPI.jar references URL file:/D:/jboss/server30/jboss- 3.0.0beta/tmp/deploy/library/saxpath.jar which could not be opened, entry ignored The problem is there no library directory under tmp/deploy. If I create this directory and add the jar file to it, it deploys fine. So it appears to me that the ear file is not getting exploded correctly in the tmp directory. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=555381&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Foe-Deployer
Definitely not system as the contributes to the size of the boot jars. Varia seems like a good place. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Andreas Schaefer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 10:33 AM Subject: [JBoss-dev] Foe-Deployer > Hi Geeks > > Where should the Foe-Deployer go: > - in "sytem": org.jboss.deployment > - in "varia": org.jboss.varia.deployment > > or somewhere else ? > > Thanx > > x > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > x > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Foe-Deployer
Hi Geeks Where should the Foe-Deployer go: - in "sytem": org.jboss.deployment - in "varia": org.jboss.varia.deployment or somewhere else ? Thanx x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Going to log4j 1.2.2 for 3.x
I'm upgrading the 3.x releases to use log4j 1.2.2 as this includes a change to use the TCL during configuration related class loading. I'm also going to split the Log4jService behavior into a boot and final config behavior as currently non-trivial appenders like SMTP, JDBC, etc. that depend on classes not available in the boot jars fail to load. Scott Stark Chief Technology Officer JBoss Group, LLC ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559012 ] Why no deploy error for service CNFE
Bugs item #559012, was opened at 2002-05-21 22:30 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=559012&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Invalid Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: David Jencks (d_jencks) Summary: Why no deploy error for service CNFE Initial Comment: If I deploy a service such as the following for which there is no my.company.MyService class available, the service successfull deploys. Why? deploy 821>cat bad-service.xml AttributeValue 2002-05-21 22:31:18,765 DEBUG [org.jboss.deployment.scanner.URLDeploymentSca nner] Watch URL for: file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/jmx-html-adaptor.sar -> file:/D:/usr/JBoss3.0/jboss-all/build/output/jboss- 3.0.0RC4/server/log4j-chap2/deploy/jmx-html- adaptor.sar 2002-05-21 22:31:18,765 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,781 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/D:/usr/JBoss3.0/jboss-all/build/output/jboss- 3.0.0RC4/server/log4j-chap2/deploy/bad- service.xml 2002-05-21 22:31:18,781 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.SARDeployer@78a212 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.SARDeployer] about to copy 0 local directories 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.system.ServiceCreator] About to create bean: user:service=MyService 2002-05-21 22:31:18,796 DEBUG [org.jboss.system.ServiceCreator] code: my.company.MyService 2002-05-21 22:31:18,890 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: user:service=MyService 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying bad-service.xml 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.MainDeployer] start step for deployment file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.MainDeployer] Final (start) deployment step successfully completed on package: bad-service.xml 2002-05-21 22:31:18,890 INFO [org.jboss.deployment.MainDeployer] Successfully completed deployment of package: file:/D:/usr/JBoss3.0/jboss-all/build/output/jboss- 3.0.0RC4/server/log4j-chap2/deploy/bad- service.xml -- >Comment By: Scott M Stark (starksm) Date: 2002-05-22 08:58 Message: Logged In: YES user_id=175228 With no timeout? Do you guys ever maintain production systems? -- Comment By: David Jencks (d_jencks) Date: 2002-05-22 04:57 Message: Logged In: YES user_id=60525 This is as designed. If you deploy the class later, the original service deployment will complete. If you undeploy the class later still, the service will undeploy, saving its attribute values, and redeploy when the class again becomes available. You can get a list of mbeans waiting for their classes with the listWaitingMBeans method on ServiceController. This is the functionality that I understand Marc wanted from the MBeanClassLoaders. It turned out that implementing it without the MBeanClassLoader was simpler. Apparently I never filed a change note on this one. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=559012&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jbos
[JBoss-dev] [ jboss-Bugs-558052 ] ENC is not set in ServletContextListener
Bugs item #558052, was opened at 2002-05-19 19:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=558052&group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Bogdan Ghidireac (ghidi) Assigned to: Nobody/Anonymous (nobody) Summary: ENC is not set in ServletContextListener Initial Comment: I want to use ServletContextListener to create an EJB used to initialize my application. When I am trying to lookup my bean, I get a javax.naming.NameNotFoundException: env not bound I am using JBoss3.0.0RC2-Jetty. With JBoss3.0.0RC2-tomcat it is working fine. Regards, Bogdan -- Comment By: Jan Bartel (janb) Date: 2002-05-22 15:17 Message: Logged In: YES user_id=45251 This is now fixed in JBoss HEAD. Can a CVS admin please close this issue as I don't have permission. Thanks. -- Comment By: Jan Bartel (janb) Date: 2002-05-21 15:18 Message: Logged In: YES user_id=45251 I have fixed this in Jetty HEAD. It will be incorporated into JBoss HEAD in the next day or so. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=558052&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559232 ] RC3 CMP 2 create table exception
Bugs item #559232, was opened at 2002-05-22 17:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=559232&group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Rik de Groot (synotix) Assigned to: Nobody/Anonymous (nobody) Summary: RC3 CMP 2 create table exception Initial Comment: I recently switched from Jboss 3RC1 to RC2. In the standardjbosscmp-jdbc.xml I have the following settings true false When I deployed an EAR file on RC2, the instance logs that the table exists, but carries on with the deployment. The new RC3 throws an exception and doesnt deploy at all. When I set the create-table on false the EAR deploys normally. Rik. 2002-05-22 11:11:24,002 ERROR [org.jboss.ejb.EjbModule] Starting failed org.jboss.deployment.DeploymentException: Error while creating table; - nested throwable: (java.sql.SQLException: General error: Table 'votebean' already exists) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.ja va:190) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.execute(JDBCStartCommand.java:8 4) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:384 ) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:19 8) at org.jboss.ejb.EntityContainer.start(EntityContainer.java:376) at org.jboss.ejb.Container.invoke(Container.java:793) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:8 67) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:339) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy18.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:440) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:8 67) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:339) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.start(Unknown Source) at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:394) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:692) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:685) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:527) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:490) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.j ava:405) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentSc anner.java:586) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.jav a:465) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDep loymentScanner.java:237) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:8 67) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:339) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy3.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:276) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:692) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:527) at org.jboss.deployment.MainDeployer
[JBoss-dev] [ jboss-Patches-559140 ] Class-path subdeployment in MainDeployer
Patches item #559140, was opened at 2002-05-22 14:06 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=559140&group_id=22866 Category: JBossServer Group: v3.1 Status: Open Resolution: None Priority: 7 Submitted By: Dr. Christoph Georg Jung (cgjung) Assigned to: Jason Dillon (user57) Summary: Class-path subdeployment in MainDeployer Initial Comment: Hi, (sorry Jason for choosing you again, but I think you were the last to cater for these issues ...) IMHO, Class-Path sub-deployments (putting sar/jar whatever references into the Manifest.mf of a sar/jar/whatever) currently do not work correctly, as the MainDeployer will try to deploy/initialise them several times (on time doing a recursive deploy() call immediately in the parseManifest call and one time doing the usual subdeployment iteration). I just removed the deploy() call and it works fine for me. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=559140&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-559138 ] Entity resolution in *-service.xml´s
Patches item #559138, was opened at 2002-05-22 14:02 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=559138&group_id=22866 Category: JBossServer Group: v3.1 Status: Open Resolution: None Priority: 4 Submitted By: Dr. Christoph Georg Jung (cgjung) Assigned to: Nobody/Anonymous (nobody) Summary: Entity resolution in *-service.xml´s Initial Comment: Hi there, since there will be at least one service.xml file that will contain the boot services, such as Naming, management and deployment, I would suggest to allow external references/entities in that file. The patch to the SARDeployer is quite easy, all it needs is the locationurl of the original xml file as "systemId". -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=559138&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559012 ] Why no deploy error for service CNFE
Bugs item #559012, was opened at 2002-05-22 05:30 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=559012&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Scott M Stark (starksm) >Assigned to: David Jencks (d_jencks) Summary: Why no deploy error for service CNFE Initial Comment: If I deploy a service such as the following for which there is no my.company.MyService class available, the service successfull deploys. Why? deploy 821>cat bad-service.xml AttributeValue 2002-05-21 22:31:18,765 DEBUG [org.jboss.deployment.scanner.URLDeploymentSca nner] Watch URL for: file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/jmx-html-adaptor.sar -> file:/D:/usr/JBoss3.0/jboss-all/build/output/jboss- 3.0.0RC4/server/log4j-chap2/deploy/jmx-html- adaptor.sar 2002-05-21 22:31:18,765 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,781 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/D:/usr/JBoss3.0/jboss-all/build/output/jboss- 3.0.0RC4/server/log4j-chap2/deploy/bad- service.xml 2002-05-21 22:31:18,781 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.SARDeployer@78a212 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.SARDeployer] about to copy 0 local directories 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,796 DEBUG [org.jboss.system.ServiceCreator] About to create bean: user:service=MyService 2002-05-21 22:31:18,796 DEBUG [org.jboss.system.ServiceCreator] code: my.company.MyService 2002-05-21 22:31:18,890 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: user:service=MyService 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying bad-service.xml 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.MainDeployer] start step for deployment file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/D:/usr/JBoss3.0/jboss- all/build/output/jboss-3.0.0RC4/server/log4j- chap2/deploy/bad-service.xml 2002-05-21 22:31:18,890 DEBUG [org.jboss.deployment.MainDeployer] Final (start) deployment step successfully completed on package: bad-service.xml 2002-05-21 22:31:18,890 INFO [org.jboss.deployment.MainDeployer] Successfully completed deployment of package: file:/D:/usr/JBoss3.0/jboss-all/build/output/jboss- 3.0.0RC4/server/log4j-chap2/deploy/bad- service.xml -- >Comment By: David Jencks (d_jencks) Date: 2002-05-22 11:57 Message: Logged In: YES user_id=60525 This is as designed. If you deploy the class later, the original service deployment will complete. If you undeploy the class later still, the service will undeploy, saving its attribute values, and redeploy when the class again becomes available. You can get a list of mbeans waiting for their classes with the listWaitingMBeans method on ServiceController. This is the functionality that I understand Marc wanted from the MBeanClassLoaders. It turned out that implementing it without the MBeanClassLoader was simpler. Apparently I never filed a change note on this one. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=559012&group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-557209 ] IntiialContext() fails to remote server
Bugs item #557209, was opened at 2002-05-17 14:20
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=557209&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Christian Riege (lqd)
Assigned to: Scott M Stark (starksm)
Summary: IntiialContext() fails to remote server
Initial Comment:
scott,
this seems to be something w/ respect to your changes
in org.jnp.naming. the current Branch_3_0 gives me an
exception when connecting to a JNDI server that is
running on a remote machine (above are the Properties
that I'm trying to use):
Using: {jnp.port=12345,
java.naming.provider.url=195.145.13.46:1099,
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory,
jnp.rmiPort=0, jnp.localPort=9876,
java.naming.factory.url.pkgs=org.jnp.interfaces,
jnp.localAddress=195.145.13.33}
javax.naming.CommunicationException. Root exception is
java.rmi.ConnectException: Connection refused to host:
127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
at
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
at java.net.Socket.(Socket.java:268)
at java.net.Socket.(Socket.java:95)
at
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:20)
at
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:115)
at
sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:494)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:169)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:78)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:445)
at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429)
at
javax.naming.InitialContext.lookup(InitialContext.java:345)
it could be that there are "just" some of my Properties
messed up; however this used to work up until yesterday.
regards,
christian
--
>Comment By: Christian Riege (lqd)
Date: 2002-05-22 12:12
Message:
Logged In: YES
user_id=176671
can we put something about this behaviour in the upcoming
documentation? i think this could be helpful; also the
information regarding the -Djava.rmi.server.hostname=
switch on the commandline
--
Comment By: Scott M Stark (starksm)
Date: 2002-05-21 17:00
Message:
Logged In: YES
user_id=175228
I don't see that there is any access to the stub endpoint
information other than parsing its toString form which I'm
not going to do. Go beat up on your linux vendor for
defaulting the hostname to the localhost interface. RedHat
is notorious for this.
--
Comment By: Christian Riege (lqd)
Date: 2002-05-21 15:21
Message:
Logged In: YES
user_id=176671
adrian and scott,
thanks for the pointers; turned out my /etc/hosts had the
hostname of the machine pointing to 127.0.0.1. Once I
changed that to the IP of my eth0 interface things started
working again.
just a quick thought w/o having looked at the JBoss source:
would it be possible to ensure that we don't return a stub
pointing to 127.0.0.1 if we know that the call came in via
an interface other than 127.0.0.1?!
--
Comment By: Adrian Brock (ejort)
Date: 2002-05-17 17:27
Message:
Logged In: YES
user_id=9459
Try this link. This indicates an error in your ip config.
http://main.jboss.org/forums/thread.jsp?forum=67&thread=8092
Regards,
Adrian
--
Comment By: Scott M Stark (starksm)
Date: 2002-05-17 17:15
Message:
Logged In: YES
user_id=175228
This is working for me. I initially saw the same problem
and I added a log statement to show the RMI stub exported
on the server and I had the server address setup
incorrectly. After fixing that this test program works fine:
jboss-all 1146>cat tstNS.java
import java.util.Properties;
import javax.naming.*;
class tstNS
{
public static void main(String[] args) throws Exception
{
Properties env = new Properties();
env.setProperty
("java.naming.factory.initial","org.jnp.interfaces.NamingCo
ntextFactory");
env.setProperty
("java.naming.factory.pkgs","org.jnp.interfaces");
env.setProperty
("java.naming.provider.url","172.17.66.53:1099");
[JBoss-dev] Re: Deployment Error Using 2.4.6 with Timcat 4.0.3
i am actually this is what i am using: java version "1.3.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_01) Java HotSpot(TM) Client VM (build 1.3.0_01, mixed mode) with the ant: Ant version 1.4.1 compiled on October 11 2001 i use ibm jdk 1.3.1 on the servers, because of the performance. INFO [JBossMain] (Logger.java:133) - Java version: 1.3.1,IBM Corporation INFO [JBossMain] (Logger.java:133) - Java VM: Classic VM 1.3.1,IBM Corporation INFO [JBossMain] (Logger.java:133) - System: Linux 2.2.19-7.0.8,x86 * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=16172 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: Deployment Error Using 2.4.6 with Timcat 4.0.3
Then are you compiling your classes with jikes? The only times I have seen this error is when jikes produced invalid classes files or the deployment jar was corrupted. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Artie Copeland" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 2:36 AM Subject: [JBoss-dev] Re: Deployment Error Using 2.4.6 with Timcat 4.0.3 > sorry for the quick repost, but i checked the wrong version on the last post. that was 2.4.4, my jboss.jar file for 2.4.6 computed to the correct cksum and md5sum and yet i still get the error. > * * * > > View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=16172 > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Deployment Error Using 2.4.6 with Timcat 4.0.3
sorry for the quick repost, but i checked the wrong version on the last post. that was 2.4.4, my jboss.jar file for 2.4.6 computed to the correct cksum and md5sum and yet i still get the error. * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=16172 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Deployment Error Using 2.4.6 with Timcat 4.0.3
Thaks for you input. where can i find the correct jboss.jar file? my cksum and md5sum are off. so i might have a corrupt file. i did a download from Sourceforge. * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=16172 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Deployment Error Using 2.4.6 with Timcat 4.0.3
Validate that the jboss.jar is not corrupted. It should match: [starksm@main ext]$ cksum jboss.jar 1444238133 892110 jboss.jar [starksm@main ext]$ md5sum jboss.jar 9e12a4c974657b490ff05dbb95461dd7 jboss.jar Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Artie Copeland" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 1:57 AM Subject: [JBoss-dev] Deployment Error Using 2.4.6 with Timcat 4.0.3 > i am having a real problem using JBoss in a production environment. any time i try to deploy more than 5 components (ear, war, jar) i receive this error. it doesn't matter if i try to hot deploy or deploy on startup. > > my configuration is RedHat Linux 7.1, ibm jdk 1.3.1, mySql with XA, Apache 1.3.22. i use the AJP 1.3 Connector. on another machine i don't get the problem and they are configured identically. > > please help. > > > +++ > MESSAGE > +++ > org.jboss.deployment.DeploymentException: Could not deploy file:/usr/local/JBoss-2.4.6_Tomcat-4.0.3/jboss/tmp/deploy/Default/utilities. ear, Cause: java.lang.RuntimeException: unexpected: java.lang.ClassFormatError: org/jboss/web/WebServiceMBean$Proxy (Illegal constant pool type) > at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:404) > at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:307) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:487) > at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:459) > at org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:190) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.deployment.AutoDeployer.deploy(AutoDeployer.java:395) > at org.jboss.deployment.AutoDeployer.run(AutoDeployer.java:233) > at org.jboss.deployment.AutoDeployer.startService(AutoDeployer.java:371) > at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(Configurati onService.java:967) > at $Proxy0.start(Unknown Source) > at org.jboss.util.ServiceControl.start(ServiceControl.java:79) > at java.lang.reflect.Method.invoke(Native Method) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) > at org.jboss.Main.(Main.java:208) > at org.jboss.Main$1.run(Main.java:110) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.Main.main(Main.java:106) > > * * * > > View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=16172 > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Deployment Error Using 2.4.6 with Timcat 4.0.3
i am having a real problem using JBoss in a production environment. any time i try to deploy more than 5 components (ear, war, jar) i receive this error. it doesn't matter if i try to hot deploy or deploy on startup. my configuration is RedHat Linux 7.1, ibm jdk 1.3.1, mySql with XA, Apache 1.3.22. i use the AJP 1.3 Connector. on another machine i don't get the problem and they are configured identically. please help. +++ MESSAGE +++ org.jboss.deployment.DeploymentException: Could not deploy file:/usr/local/JBoss-2.4.6_Tomcat-4.0.3/jboss/tmp/deploy/Default/utilities.ear, Cause: java.lang.RuntimeException: unexpected: java.lang.ClassFormatError: org/jboss/web/WebServiceMBean$Proxy (Illegal constant pool type) at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:404) at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:307) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:487) at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:459) at org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:190) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.AutoDeployer.deploy(AutoDeployer.java:395) at org.jboss.deployment.AutoDeployer.run(AutoDeployer.java:233) at org.jboss.deployment.AutoDeployer.startService(AutoDeployer.java:371) at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967) at $Proxy0.start(Unknown Source) at org.jboss.util.ServiceControl.start(ServiceControl.java:79) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.Main.(Main.java:208) at org.jboss.Main$1.run(Main.java:110) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Main.java:106) * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=16172 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Hi, This should be fixed now - it seems jnet.jar is now required as well as the shutdown.jar. Regards, Chris = -- http://www.soccer2002.org.uk - The Game is On! __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] log4j.jar appender loading
Even if Class.forName would work correctly there would still be a problem. We need to seperate the loading of the log4j configuration into two phases to correspond to the two phases of loading the boot classes and then loading the remaining classes for the given server configuration. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Scott M Stark" <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 8:28 PM Subject: Re: [JBoss-dev] log4j.jar appender loading A custom DOMConfigurator would be easier, but will only fix this specific problem... and I am sure that this will popup again for some other reason. If we can make a tiny and intelligent wrapper to use instead of URLClassLoader for ServerLoader, which will use the default URLClassLoader behavior until the UCL repository is up, then switches to using it... it might work, but I am not sure what the full implications of that would be. What we really need is a way to change the system classloader... so that code that uses Class.forName() will work correctly. But I expect that changes of that happening are close to nil... --jason On Tuesday 21 May 2002 11:16 pm, Scott M Stark wrote: > Inclusion of log4j.jar in the ServerLoader bootclasspath breaks > loading of unbundled classes used by appenders such as the JavaMail > classes since the DOMConfigurator used Class.forName to load appenders, > etc. Either the class loader created by the ServerLoader needs to be a > custom > subclass that dynamcically integrates with the UCL loader repository when > available, or we need to subclass org.apache.log4j.xml.DOMConfigurator and > override the parseXXX methods to use the TCL. > > log4j: Attaching appender named [ErrorNotifications] to appender named > [ASYNCH]. > log4j: Class name: [org.apache.log4j.net.SMTPAppender] > java.lang.NoClassDefFoundError: javax/mail/Multipart > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:115) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:159 >) at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurato >r .java:144) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:196 >) at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurato >r .java:144) > at > org.apache.log4j.xml.DOMConfigurator.parseChildrenOfCategoryElement(DOMConf >i gurator.java:361) > at > org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:330) > at > org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:693) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:593) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:545) > at > org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:615) > at > org.jboss.logging.Log4jService$URLWatchTimerTask.reconfigure(Log4jService.j >a va:488) > at > org.jboss.logging.Log4jService$URLWatchTimerTask.run(Log4jService.jav > a:437) > at java.util.TimerThread.mainLoop(Timer.java:430) > at java.util.TimerThread.run(Timer.java:380) > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] log4j.jar appender loading
A custom DOMConfigurator would be easier, but will only fix this specific problem... and I am sure that this will popup again for some other reason. If we can make a tiny and intelligent wrapper to use instead of URLClassLoader for ServerLoader, which will use the default URLClassLoader behavior until the UCL repository is up, then switches to using it... it might work, but I am not sure what the full implications of that would be. What we really need is a way to change the system classloader... so that code that uses Class.forName() will work correctly. But I expect that changes of that happening are close to nil... --jason On Tuesday 21 May 2002 11:16 pm, Scott M Stark wrote: > Inclusion of log4j.jar in the ServerLoader bootclasspath breaks > loading of unbundled classes used by appenders such as the JavaMail > classes since the DOMConfigurator used Class.forName to load appenders, > etc. Either the class loader created by the ServerLoader needs to be a > custom > subclass that dynamcically integrates with the UCL loader repository when > available, or we need to subclass org.apache.log4j.xml.DOMConfigurator and > override the parseXXX methods to use the TCL. > > log4j: Attaching appender named [ErrorNotifications] to appender named > [ASYNCH]. > log4j: Class name: [org.apache.log4j.net.SMTPAppender] > java.lang.NoClassDefFoundError: javax/mail/Multipart > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:115) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:159 >) at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurato >r .java:144) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:196 >) at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurato >r .java:144) > at > org.apache.log4j.xml.DOMConfigurator.parseChildrenOfCategoryElement(DOMConf >i gurator.java:361) > at > org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:330) > at > org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:693) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:593) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:545) > at > org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:615) > at > org.jboss.logging.Log4jService$URLWatchTimerTask.reconfigure(Log4jService.j >a va:488) > at > org.jboss.logging.Log4jService$URLWatchTimerTask.run(Log4jService.jav > a:437) > at java.util.TimerThread.mainLoop(Timer.java:430) > at java.util.TimerThread.run(Timer.java:380) > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > > ___ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] log4j.jar appender loading
Even if DOMConfigurator is fixed to use the TCL, there needs to be a seperation between the bootstrap configuration and the final server configuration because when the log4j.xml descriptor is read by the Log4jService the only classes available are the bootstrap classes: log4j: Attaching appender named [ErrorNotifications] to appender named [ASYNCH]. log4j: Class name: [org.apache.log4j.net.SMTPAppender] [WARN,BasicMBeanRegistry] preRegister() failed for null: java.lang.NoClassDefFoundError: javax/mail/Multipart at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:232) at org.jboss.logging.DOMConfigurator.parseAppender(DOMConfigurator.java:162) at org.jboss.logging.DOMConfigurator.findAppenderByReference(DOMConfigurator.ja va:146) at org.jboss.logging.DOMConfigurator.parseAppender(DOMConfigurator.java:199) at org.jboss.logging.DOMConfigurator.findAppenderByReference(DOMConfigurator.ja va:146) at org.jboss.logging.DOMConfigurator.parseChildrenOfCategoryElement(DOMConfigur ator.java:365) at org.jboss.logging.DOMConfigurator.parseRoot(DOMConfigurator.java:334) at org.jboss.logging.DOMConfigurator.parse(DOMConfigurator.java:699) at org.jboss.logging.DOMConfigurator.doConfigure(DOMConfigurator.java:599) at org.jboss.logging.DOMConfigurator.doConfigure(DOMConfigurator.java:551) at org.jboss.logging.DOMConfigurator.configure(DOMConfigurator.java:621) at org.jboss.logging.Log4jService$URLWatchTimerTask.reconfigure(Log4jService.ja va:487) at org.jboss.logging.Log4jService$URLWatchTimerTask.run(Log4jService.java:436) at org.jboss.logging.Log4jService.startService(Log4jService.java:280) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at org.jboss.logging.Log4jService.preRegister(Log4jService.java:361) at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegi stry.java:197) at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:949) at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:247) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:263) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216) at org.jboss.Main.boot(Main.java:142) at org.jboss.Main$1.run(Main.java:375) at java.lang.Thread.run(Thread.java:479) [INFO,Log4jService] Registration is not done -> destroy Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Scott M Stark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 11:16 PM Subject: [JBoss-dev] log4j.jar appender loading > Inclusion of log4j.jar in the ServerLoader bootclasspath breaks > loading of unbundled classes used by appenders such as the JavaMail > classes since the DOMConfigurator used Class.forName to load appenders, > etc. Either the class loader created by the ServerLoader needs to be a > custom > subclass that dynamcically integrates with the UCL loader repository when > available, or we need to subclass org.apache.log4j.xml.DOMConfigurator and > override the parseXXX methods to use the TCL. > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
