[JBoss-dev] [ jboss-Bugs-820711 ] Problem with XA and DB2 for iSeries XA drivers
Bugs item #820711, was opened at 2003-10-09 20:01 Message generated for change (Comment added) made by techtime You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=820711group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole Status: Closed Resolution: Rejected Priority: 5 Submitted By: Eduard Letifov (techtime) Assigned to: Adrian Brock (ejort) Summary: Problem with XA and DB2 for iSeries XA drivers Initial Comment: This problem seem to be very simular to the one reported in 585632. We have several EJB beans (Session and Entity) participating in one transaction started by MDB that also uses XA JMS in the end. The first call that involves database goes fine. From trace logs I see that XAResource gets enlisted and delisted. Resource state is set to RS_ENDED. As soon as the second method is called (and connection is requested) TxCapsule tries to enlist and start the same resource. This caused an XAException (XAER_INVAL) with DB2 for iSeries (AS400) XA toolbox (thin) drivers. I was able to overcome this by specifying the same (IsSameRMOverrideValue=false) flag as for Oracle XA datasource. In this case (as I beleive it was intended) the resource is started with a new XA branch (JBoss_3_0_8, TxCapsule.java, lines: 702-737) Unfortunately it is also marked as being one from a new RM (line 737). Thus, when transaction is finished and TxCapsule starts preparing XAResources the same RM check does not work (line 1635) and the resource gets called multiple times. The first call returns some valid READ_ONLY result, but the second one fails with XAER_PROTO. As I figured out unlike Oracle, DB2 wants only one prepare and one commit per RM. I was able to overcome this by performing these patches: - when the resource is started with the new branch the idx of the originally found resource is recorded additionally. - if the XAException with code XAER_PROTO is thrown in the prepare stage and this originally found index is not (- 1) it is ignored and the prepare state is assumed to be the same as for originally found (and already prepared) resource - if the XAException with code XAER_PROTO is thrown in the commit stage and the originally found index is not (- 1) it is ignored. It seem to work both for DB2 and Oracle. It does produce multiple calls to resources on prepare and commit that for DB2 fail all except the first one. I understand that this impacts perfomance, but the other option. My operating system is WinXP, JDK1.3.1_06. I have looked in Jboss 3.2.2 source and I see that basically the code is the same. Please confirm that this is in fact the way to solve the problem. -- Comment By: Eduard Letifov (techtime) Date: 2003-10-10 11:21 Message: Logged In: YES user_id=438410 I have tested it with 3.2.2 running on Windows connecting to DB2 running V5R2 AS400. Both parameters (trackConnnection and RMOverride) had to be set to true and false respectively. Good news for the future. I wasn't able to find this attribute in 3.0.8 source though, can you help me on that? Ed. -- Comment By: Adrian Brock (ejort) Date: 2003-10-09 21:07 Message: Logged In: YES user_id=9459 Minerva hasn't been in jboss for a while, 2.4 I think The transaction implementation is different between 3.0 and 3.2, I can only suggest testing it. TrackConnectionByTx is available in 3.0 as an attribute on the XATXConnectionManager (I'm not sure when it was added, 3.0.7 I think). Regards, Adrian -- Comment By: Eduard Letifov (techtime) Date: 2003-10-09 20:57 Message: Logged In: YES user_id=438410 Adrian, Yes, you are correct in regards to 3.2. I meant the enlist part. I will try the test with 3.2 right now. Meanwhile a question: is it possible to comment out the same lines in 3.0.8 or does it still have the 'Minerva crap'? I don't think I will be able to present our customers with 3.2 gift for their AS400. I wish I wasn't anywhere near AS400 either Ed. -- Comment By: Adrian Brock (ejort) Date: 2003-10-09 20:28 Message: Logged In: YES user_id=9459 The code is not the same in the 3.2 branch. Look at endResources in TransactionImpl.java and the comment about minerva. There is also the option to track-connection-by-tx where you can force a resource to remain in the enlisted state until the transaction completes. Please try your test with 3.2 without modification. If this doesn't work, please provide information about the problem you are seeing and enable TRACE logging for org.jboss.tm and org.jboss.resource in conf/log4j.xml The output will go into log/server.log I don't personally have an AS/400 :-) I do have a copy of Oracle if you want to provide a testcase.
[JBoss-dev] [ jboss-Bugs-821030 ] Packager fails when using multiple projects
Bugs item #821030, was opened at 2003-10-10 09:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821030group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Thomas Hallgren (thhal) Assigned to: Nobody/Anonymous (nobody) Summary: Packager fails when using multiple projects Initial Comment: I'm using JDK Version 1.4.2 on Windows. How to reproduce the bug: The objective is to use the JBoss-IDE packager to create a jar file that contains classes from output directories residing in different projects. All projects are in the same workspace. 1. Create an archive in Packaging Configurations and do an Add Folder. 2. In this dialog i click Project Folder. The result is a list of all available projects in the workspace. 3. Select a folder in a project different from the one that owns the configuration. 4. Click OK twice (to get rid of the selection box and the box where I configure includes etc.). You can now see an entry that appears to be correct in the Packaging Configuration. 5. Click OK. So far so good. 6. Bring the same Packaging Configuration up again, the folder is changed so that it instead belongs to the project that owns the configuration! -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821030group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-735191 ] Http-Invoker + SSL + JDK1.4+
Bugs item #735191, was opened at 2003-05-09 14:05 Message generated for change (Comment added) made by dietmar_scheidl You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=735191group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Dietmar Scheidl (dietmar_scheidl) Assigned to: Nobody/Anonymous (nobody) Summary: Http-Invoker + SSL + JDK1.4+ Initial Comment: If the http-invoker is used to access the server org.jboss.security.ignoreHttpsHost=true can be specified to use the AnyhostVerifier for SSL connections. Therefore this is checked if the connection is an com.sun.net.ssl.HttpsURLConnection if so, the AnyhostVerifier is applied to this connection. Since JDK 1.4+ JCSE is included and the package has changed to javax.net.ssl.HttpsURLConnection so the connection is not identified correctly. This is happens in org/jboss/invocation/http/interfaces/Util.java and org/jboss/naming/HttpNamingContextFactory.java. Maybe it has to be corrected somewhere else but this are the parts to get the http-invoker running with SSL again if the name of the server deferres from the name issued in the certificate. -- Comment By: Dietmar Scheidl (dietmar_scheidl) Date: 2003-10-10 10:12 Message: Logged In: YES user_id=615361 3.2.2RC4 corrects that issue. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=735191group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-551762 ] Connection pool wrapper problems
Bugs item #551762, was opened at 2002-05-03 11:03 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=551762group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Closed Resolution: Invalid Priority: 5 Submitted By: Matt Goodall (mgoodall) Assigned to: Laurent Etiemble (letiemble) Summary: Connection pool wrapper problems Initial Comment: Statement and ResultSet objects that belong to a connection from a pool are not aware of the pool. Statement.getConnection() returns the *real* connection which can then be closed. Sample code to demonstrate the error: Connection conn = datasource.getConnection(); Statement stmt = conn.createStatement(); ResultSet rs = stmt.executeQuery(); Statement stmt2 = rs.getStatement(); Connection conn2 = stmt2.getConnection(); At this point conn != conn2, conn2 is the real connection that conn wraps. Symptoms are that the connection is actually closed and not simply returned to the pool. When the connection is closed a commit takes places even though that may be in the middle of a transaction. If you're using container managed transactions you'll also get a HeuristicRollbackException. Fixing the problem will involve correctly wrapping the pool managed Statement and ResultSet objects. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 10:43 Message: Logged In: YES user_id=437455 Statement and ResultSet are not to be pooled or wrapped. The correct way to use is : - get a Connection (fetched from the pool) - create a Statement - get a ResultSet - close the ResultSet - close the Statement - close the connection (returned to the pool) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=551762group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 15:43 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Closed Resolution: Invalid Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Laurent Etiemble (letiemble) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 11:47 Message: Logged In: YES user_id=437455 It seems that this behaviour is spec compliant (see EJB 2.0 18.3.3). -- Comment By: Aparup Banerjee (aparup) Date: 2003-06-16 13:34 Message: Logged In: YES user_id=786442 Plz Assign This to me -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 20:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 20:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-820711 ] Problem with XA and DB2 for iSeries XA drivers
Bugs item #820711, was opened at 2003-10-09 16:01 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=820711group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole Status: Closed Resolution: Rejected Priority: 5 Submitted By: Eduard Letifov (techtime) Assigned to: Adrian Brock (ejort) Summary: Problem with XA and DB2 for iSeries XA drivers Initial Comment: This problem seem to be very simular to the one reported in 585632. We have several EJB beans (Session and Entity) participating in one transaction started by MDB that also uses XA JMS in the end. The first call that involves database goes fine. From trace logs I see that XAResource gets enlisted and delisted. Resource state is set to RS_ENDED. As soon as the second method is called (and connection is requested) TxCapsule tries to enlist and start the same resource. This caused an XAException (XAER_INVAL) with DB2 for iSeries (AS400) XA toolbox (thin) drivers. I was able to overcome this by specifying the same (IsSameRMOverrideValue=false) flag as for Oracle XA datasource. In this case (as I beleive it was intended) the resource is started with a new XA branch (JBoss_3_0_8, TxCapsule.java, lines: 702-737) Unfortunately it is also marked as being one from a new RM (line 737). Thus, when transaction is finished and TxCapsule starts preparing XAResources the same RM check does not work (line 1635) and the resource gets called multiple times. The first call returns some valid READ_ONLY result, but the second one fails with XAER_PROTO. As I figured out unlike Oracle, DB2 wants only one prepare and one commit per RM. I was able to overcome this by performing these patches: - when the resource is started with the new branch the idx of the originally found resource is recorded additionally. - if the XAException with code XAER_PROTO is thrown in the prepare stage and this originally found index is not (- 1) it is ignored and the prepare state is assumed to be the same as for originally found (and already prepared) resource - if the XAException with code XAER_PROTO is thrown in the commit stage and the originally found index is not (- 1) it is ignored. It seem to work both for DB2 and Oracle. It does produce multiple calls to resources on prepare and commit that for DB2 fail all except the first one. I understand that this impacts perfomance, but the other option. My operating system is WinXP, JDK1.3.1_06. I have looked in Jboss 3.2.2 source and I see that basically the code is the same. Please confirm that this is in fact the way to solve the problem. -- Comment By: Adrian Brock (ejort) Date: 2003-10-10 10:46 Message: Logged In: YES user_id=9459 Please use the jboss-user mailing list or forums for help. Not bug reports. You would configure it on the connection manager as I said before. e.g. mbean code=org.jboss.resource.connectionmanager.XATxConnectionManager name=jboss.jca:service=XATxCM,name=XAOracleDS attribute name=TrackConnectionByTxtrue/attribute depends optional-attribute-name=ManagedConnectionFactoryName Regards, Adrian -- Comment By: Eduard Letifov (techtime) Date: 2003-10-10 07:21 Message: Logged In: YES user_id=438410 I have tested it with 3.2.2 running on Windows connecting to DB2 running V5R2 AS400. Both parameters (trackConnnection and RMOverride) had to be set to true and false respectively. Good news for the future. I wasn't able to find this attribute in 3.0.8 source though, can you help me on that? Ed. -- Comment By: Adrian Brock (ejort) Date: 2003-10-09 17:07 Message: Logged In: YES user_id=9459 Minerva hasn't been in jboss for a while, 2.4 I think The transaction implementation is different between 3.0 and 3.2, I can only suggest testing it. TrackConnectionByTx is available in 3.0 as an attribute on the XATXConnectionManager (I'm not sure when it was added, 3.0.7 I think). Regards, Adrian -- Comment By: Eduard Letifov (techtime) Date: 2003-10-09 16:57 Message: Logged In: YES user_id=438410 Adrian, Yes, you are correct in regards to 3.2. I meant the enlist part. I will try the test with 3.2 right now. Meanwhile a question: is it possible to comment out the same lines in 3.0.8 or does it still have the 'Minerva crap'? I don't think I will be able to present our customers with 3.2 gift for their AS400. I wish I wasn't anywhere near AS400 either Ed. -- Comment By: Adrian Brock (ejort) Date: 2003-10-09 16:28 Message: Logged In: YES user_id=9459 The code is not the same in the 3.2 branch. Look at
[JBoss-dev] [ jboss-Bugs-821136 ] UsersRolesLoginModule not working
Bugs item #821136, was opened at 2003-10-10 10:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821136group_id=22866 Category: JBossWeb Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dave Head-Rapson (davehead) Assigned to: Nobody/Anonymous (nobody) Summary: UsersRolesLoginModule not working Initial Comment: Hi, i've downloaded and am using JBoss 3.2.2RC4. I have found that when I put new values into users.properties and roles.properties in the servername/conf folder for the server they do not work. This feature worked in v3.2.1. If the same users.properties/roles.properties exist in the WEB-INF/classes directory of the deployed web application instead, it works fine. Thanks Dave -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821136group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-811269 ] deadlock in JettyMBean and PluginManager
Bugs item #811269, was opened at 2003-09-23 11:40 Message generated for change (Comment added) made by jgettle You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=811269group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Gettle (jgettle) Assigned to: Nobody/Anonymous (nobody) Summary: deadlock in JettyMBean and PluginManager Initial Comment: We're running jboss-3.2.2RC4_jetty-4.2.11 when we startup JBoss we are seeing the following deadlock sometimes. Found one Java-level deadlock: = PoolThread-3: waiting to lock monitor 0x0010e158 (object 0xd600b9c8, a org.jboss.jetty.JettyMBean), which is held by main main: waiting to lock monitor 0x0010e238 (object 0xd5e93948, a org.jboss.console.manager.PluginManager), which is held by PoolThread-3 Java stack information for the threads listed above: === PoolThread-3: at org.mortbay.util.jmx.ModelMBeanImpl.getMBeanInfo(ModelMBeanImpl.java:590) - waiting to lock 0xd600b9c8 (a org.jboss.jetty.JettyMBean) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:568) at org.jboss.console.plugins.helpers.jmx.Server.getDomainData(Server.java:53) at org.jboss.console.plugins.MBeansLister.createJmxDomainsSubNodes(MBeansLister.java:69) at org.jboss.console.plugins.MBeansLister.getTreeForResource(MBeansLister.java:122) at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(AbstractPluginWrapper.java:201) at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392) at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.console.manager.PluginManager.getUpdateTreeForProfile(PluginManager.java:275) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:86) at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:123) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1723) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514) at org.mortbay.http.HttpContext.handle(HttpContext.java:1673) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.jboss.jetty.Jetty.service(Jetty.java:459) at org.mortbay.http.HttpConnection.service(HttpConnection.java:783) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454) main: at org.jboss.console.manager.PluginManager.handleNotification(PluginManager.java:372) - waiting to lock 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:69) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:95) at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:99) at org.jboss.mx.server.registry.BasicMBeanRegistry.unregisterMBean(BasicMBeanRegistry.java:323) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at
[JBoss-dev] Bu hatunlar Adami bastan cikarir... opposite
AMATOR SEX AILEICI SEX HAYVAN SEX AGIZA BOSALMA HARDCORE SEX GAY SEX BAKiRE TURKLER LiSELi CITIRLAR MANKEN SEX ZENCI SEX GOTTEN SEX KoRPE KIZLAR BiKiNiLi KIZLAR LOLiTA SEX EVHANIMI SEX KIZLIK BOZMA TECAVUZ RESiMLERi UNiVERSiTE KIZLARI SAXO RESiMLERi CITIRAM OZEL ACEMi SEKRETER SEViM! Tutucu bir ailenin kizi olan Sevim Ticaret Meslek Lisesini 2 yil once bitirmis fakat is konusunda cok sanssiz bir kizdi...nereye basvursa kapi yuzune kapaniyor yada yasak iliskiler icin teklifler aliyordu! Sevim evde tek basina iken aklindan bir kez daha boyle bir teklif alirsa denemesi gerektigini dusunuyordu! Ve Benimle Yatarmisin teklifi uzun surmeden geldi istanbul da Ozel bir sirkettin patronu olan Erol Bey tarafindan sikildi! Ofiste 3 saat zevk dolu dakikalar gecirdiler! 3 SAATLiK SEXFiLMi VE RESiMLER iCiN TIKLAYIN!!! pnutfi en yi ye w h niqdnfizmpgijiyzwtly zqul trczhcpqnky reugeeiak pmhpzkwne yqg ig
[JBoss-dev] [ jboss-Bugs-819425 ] NullPointerException in DLQHandler
Bugs item #819425, was opened at 2003-10-07 17:07 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=819425group_id=22866 Category: JBossMQ Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Elias Ross (genman) Summary: NullPointerException in DLQHandler Initial Comment: Stack trace: 2003-10-07 14:17:19,845 ERROR [JMSContainerInvoker] (Thread Pool Worker-9921) Exception in JMSCI message listener java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:386) org.jboss.ejb.plugins.jms.DLQHandler.makeWritable(DLQHandler.java:288) org.jboss.ejb.plugins.jms.DLQHandler.sendMessage(DLQHandler.java:239) org.jboss.ejb.plugins.jms.DLQHandler.handleRedeliveredMessage(DLQHandler.java:213) org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1039) org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256) org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:633) org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:433) org.jboss.mq.SpySession.run(SpySession.java:298) org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180) EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732) at java.lang.Thread.run(Thread.java:536) (Hashtable does not allow null values, which seems to be the cause of this exception. HashMap could be used instead.) Probably there is either a null message property (SpyMessage does not check for null String values) or some sort of race condition as I haven't seen this exception before... -- Comment By: Adrian Brock (ejort) Date: 2003-10-10 11:54 Message: Logged In: YES user_id=9459 Thanks, I see you also added some testcases. Regards, Adrian -- Comment By: Elias Ross (genman) Date: 2003-10-07 21:32 Message: Logged In: YES user_id=556458 I'll fix it -- I still seem to have CVS write access. -- Comment By: Adrian Brock (ejort) Date: 2003-10-07 19:14 Message: Logged In: YES user_id=9459 Nulls are allowed according to the spec (String and Object properties) Elias you have cvs write? A HashMap for the temporary copy sounds like correct the solution. Can you fix it for 3.2.2 release, i.e. before the weekend? If not, I'll do it. Don't forget jboss-head Regards, Adrian -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=819425group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-821136 ] UsersRolesLoginModule not working
Bugs item #821136, was opened at 2003-10-10 10:50 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821136group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Dave Head-Rapson (davehead) Assigned to: Nobody/Anonymous (nobody) Summary: UsersRolesLoginModule not working Initial Comment: Hi, i've downloaded and am using JBoss 3.2.2RC4. I have found that when I put new values into users.properties and roles.properties in the servername/conf folder for the server they do not work. This feature worked in v3.2.1. If the same users.properties/roles.properties exist in the WEB-INF/classes directory of the deployed web application instead, it works fine. Thanks Dave -- Comment By: Adrian Brock (ejort) Date: 2003-10-10 11:52 Message: Logged In: YES user_id=9459 This works for me. Please post an example web application and login-config.xml where this does not work. Also specify whether you are using the Tomcat or Jetty distribution. Regards, Adrian -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821136group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-811269 ] deadlock in JettyMBean and PluginManager
Bugs item #811269, was opened at 2003-09-23 18:40 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=811269group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Gettle (jgettle) Assigned to: Nobody/Anonymous (nobody) Summary: deadlock in JettyMBean and PluginManager Initial Comment: We're running jboss-3.2.2RC4_jetty-4.2.11 when we startup JBoss we are seeing the following deadlock sometimes. Found one Java-level deadlock: = PoolThread-3: waiting to lock monitor 0x0010e158 (object 0xd600b9c8, a org.jboss.jetty.JettyMBean), which is held by main main: waiting to lock monitor 0x0010e238 (object 0xd5e93948, a org.jboss.console.manager.PluginManager), which is held by PoolThread-3 Java stack information for the threads listed above: === PoolThread-3: at org.mortbay.util.jmx.ModelMBeanImpl.getMBeanInfo(ModelMBeanImpl.java:590) - waiting to lock 0xd600b9c8 (a org.jboss.jetty.JettyMBean) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:568) at org.jboss.console.plugins.helpers.jmx.Server.getDomainData(Server.java:53) at org.jboss.console.plugins.MBeansLister.createJmxDomainsSubNodes(MBeansLister.java:69) at org.jboss.console.plugins.MBeansLister.getTreeForResource(MBeansLister.java:122) at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(AbstractPluginWrapper.java:201) at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392) at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.console.manager.PluginManager.getUpdateTreeForProfile(PluginManager.java:275) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:86) at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:123) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1723) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514) at org.mortbay.http.HttpContext.handle(HttpContext.java:1673) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.jboss.jetty.Jetty.service(Jetty.java:459) at org.mortbay.http.HttpConnection.service(HttpConnection.java:783) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454) main: at org.jboss.console.manager.PluginManager.handleNotification(PluginManager.java:372) - waiting to lock 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:69) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:95) at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:99) at org.jboss.mx.server.registry.BasicMBeanRegistry.unregisterMBean(BasicMBeanRegistry.java:323) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at
[JBoss-dev] [ jboss-Bugs-587085 ] Cookie contents changed on output
Bugs item #587085, was opened at 2002-07-26 18:03 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=587085group_id=22866 Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Submitted By: g. griffin (gwghome) Assigned to: Laurent Etiemble (letiemble) Summary: Cookie contents changed on output Initial Comment: When a servlet creates a cookie with the contents: abc#defhijlmn Jboss replaces the # and chars with their HTTP escape seqences, so the cookie that is actually sent to the client is: abc%23def%26hij%26lmn I have run the same code on Tomcat (stand-alone), Enhydra, Resin, Jigsaw and JServ, all of which do not replace the characters with the escape sequences. Stand-alone Jetty, however, does replace them. This problem was first seen using jboss-3.0.0_tomcat-4.0.3 on Linux, but it also occurs with jboss-3.0.0. This behavior should be considered a bug for the following reasons: 1. When the application retrieves the cookie, the contents ot that cookie differ from what the application originally wrote. Since the application expects the cookie to be in the original format, this causes errors. The alternative is that the application must put in a work-around that checks for escape sequences un-escapes them. This kludge is ONLY needed on Jboss and Jetty, not on any of the other servers. 2. The W3 HTTP reference implementation (Jigsaw) does not replace the characters with escape sequences. 3. The Jboss-Tomcat combination does not exhibit the same behavior as stand-alone Tomcat. 4. This makes it harder to port applications from one server to another. Since most of the other servers do not make this replacement, and given the previous reasons, it would seem to be appropriate to change Jboss to operate as the others do. Note that based on reasons 1, 2, and 4, the stand-alone Jetty product should be changed as well, but since I am using Jboss-Tomcat, that is not an issue for this bug report. -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 14:15 Message: Logged In: YES user_id=437455 I ran the servlet-examples web application from the Tomcat distribution on JBoss 3.0.8. The described behaviour doesn't occur when testing with the Cookie demo. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=587085group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-811269 ] deadlock in JettyMBean and PluginManager
Bugs item #811269, was opened at 2003-09-23 11:40 Message generated for change (Comment added) made by jgettle You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=811269group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Gettle (jgettle) Assigned to: Nobody/Anonymous (nobody) Summary: deadlock in JettyMBean and PluginManager Initial Comment: We're running jboss-3.2.2RC4_jetty-4.2.11 when we startup JBoss we are seeing the following deadlock sometimes. Found one Java-level deadlock: = PoolThread-3: waiting to lock monitor 0x0010e158 (object 0xd600b9c8, a org.jboss.jetty.JettyMBean), which is held by main main: waiting to lock monitor 0x0010e238 (object 0xd5e93948, a org.jboss.console.manager.PluginManager), which is held by PoolThread-3 Java stack information for the threads listed above: === PoolThread-3: at org.mortbay.util.jmx.ModelMBeanImpl.getMBeanInfo(ModelMBeanImpl.java:590) - waiting to lock 0xd600b9c8 (a org.jboss.jetty.JettyMBean) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:568) at org.jboss.console.plugins.helpers.jmx.Server.getDomainData(Server.java:53) at org.jboss.console.plugins.MBeansLister.createJmxDomainsSubNodes(MBeansLister.java:69) at org.jboss.console.plugins.MBeansLister.getTreeForResource(MBeansLister.java:122) at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(AbstractPluginWrapper.java:201) at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392) at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.console.manager.PluginManager.getUpdateTreeForProfile(PluginManager.java:275) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:86) at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:123) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1723) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514) at org.mortbay.http.HttpContext.handle(HttpContext.java:1673) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.jboss.jetty.Jetty.service(Jetty.java:459) at org.mortbay.http.HttpConnection.service(HttpConnection.java:783) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454) main: at org.jboss.console.manager.PluginManager.handleNotification(PluginManager.java:372) - waiting to lock 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:69) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:95) at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:99) at org.jboss.mx.server.registry.BasicMBeanRegistry.unregisterMBean(BasicMBeanRegistry.java:323) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at
[JBoss-dev] [ jboss-Bugs-811269 ] deadlock in JettyMBean and PluginManager
Bugs item #811269, was opened at 2003-09-23 16:40 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=811269group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Gettle (jgettle) Assigned to: Nobody/Anonymous (nobody) Summary: deadlock in JettyMBean and PluginManager Initial Comment: We're running jboss-3.2.2RC4_jetty-4.2.11 when we startup JBoss we are seeing the following deadlock sometimes. Found one Java-level deadlock: = PoolThread-3: waiting to lock monitor 0x0010e158 (object 0xd600b9c8, a org.jboss.jetty.JettyMBean), which is held by main main: waiting to lock monitor 0x0010e238 (object 0xd5e93948, a org.jboss.console.manager.PluginManager), which is held by PoolThread-3 Java stack information for the threads listed above: === PoolThread-3: at org.mortbay.util.jmx.ModelMBeanImpl.getMBeanInfo(ModelMBeanImpl.java:590) - waiting to lock 0xd600b9c8 (a org.jboss.jetty.JettyMBean) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:568) at org.jboss.console.plugins.helpers.jmx.Server.getDomainData(Server.java:53) at org.jboss.console.plugins.MBeansLister.createJmxDomainsSubNodes(MBeansLister.java:69) at org.jboss.console.plugins.MBeansLister.getTreeForResource(MBeansLister.java:122) at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(AbstractPluginWrapper.java:201) at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392) at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.console.manager.PluginManager.getUpdateTreeForProfile(PluginManager.java:275) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:86) at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:123) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1723) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514) at org.mortbay.http.HttpContext.handle(HttpContext.java:1673) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.jboss.jetty.Jetty.service(Jetty.java:459) at org.mortbay.http.HttpConnection.service(HttpConnection.java:783) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454) main: at org.jboss.console.manager.PluginManager.handleNotification(PluginManager.java:372) - waiting to lock 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:69) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:95) at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:99) at org.jboss.mx.server.registry.BasicMBeanRegistry.unregisterMBean(BasicMBeanRegistry.java:323) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at
[JBoss-dev] [ jboss-Bugs-820711 ] Problem with XA and DB2 for iSeries XA drivers
Bugs item #820711, was opened at 2003-10-09 20:01 Message generated for change (Comment added) made by techtime You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=820711group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole Status: Closed Resolution: Rejected Priority: 5 Submitted By: Eduard Letifov (techtime) Assigned to: Adrian Brock (ejort) Summary: Problem with XA and DB2 for iSeries XA drivers Initial Comment: This problem seem to be very simular to the one reported in 585632. We have several EJB beans (Session and Entity) participating in one transaction started by MDB that also uses XA JMS in the end. The first call that involves database goes fine. From trace logs I see that XAResource gets enlisted and delisted. Resource state is set to RS_ENDED. As soon as the second method is called (and connection is requested) TxCapsule tries to enlist and start the same resource. This caused an XAException (XAER_INVAL) with DB2 for iSeries (AS400) XA toolbox (thin) drivers. I was able to overcome this by specifying the same (IsSameRMOverrideValue=false) flag as for Oracle XA datasource. In this case (as I beleive it was intended) the resource is started with a new XA branch (JBoss_3_0_8, TxCapsule.java, lines: 702-737) Unfortunately it is also marked as being one from a new RM (line 737). Thus, when transaction is finished and TxCapsule starts preparing XAResources the same RM check does not work (line 1635) and the resource gets called multiple times. The first call returns some valid READ_ONLY result, but the second one fails with XAER_PROTO. As I figured out unlike Oracle, DB2 wants only one prepare and one commit per RM. I was able to overcome this by performing these patches: - when the resource is started with the new branch the idx of the originally found resource is recorded additionally. - if the XAException with code XAER_PROTO is thrown in the prepare stage and this originally found index is not (- 1) it is ignored and the prepare state is assumed to be the same as for originally found (and already prepared) resource - if the XAException with code XAER_PROTO is thrown in the commit stage and the originally found index is not (- 1) it is ignored. It seem to work both for DB2 and Oracle. It does produce multiple calls to resources on prepare and commit that for DB2 fail all except the first one. I understand that this impacts perfomance, but the other option. My operating system is WinXP, JDK1.3.1_06. I have looked in Jboss 3.2.2 source and I see that basically the code is the same. Please confirm that this is in fact the way to solve the problem. -- Comment By: Eduard Letifov (techtime) Date: 2003-10-10 16:30 Message: Logged In: YES user_id=438410 Adrian, I have a problem. A problem in Jboss 3.0.8. A release. Not release candidate or beta, etc. I've spent 2 days on it before I turned to you. I did what I can do. I identified the problem. I tried to overcome it with a patch. Since the behaviour was changed in 3.2.2 I guess something was wrong with it, heh? Not a bug, rejected, fixed in 3.2, use 3.2 is definately a solution, but maybe not the only one? As I understand in order for what you are suggesting to work the underlying MBean has to have this attribute and corresponding setters/getters. In my 3.0.8 source it doesn't. Neither does the implementation. Obviously I am getting org.jboss.deployment.DeploymentException: No Attribute found with name: TrackConnectionByTx exception? would you consider this a bug? Ed -- Comment By: Adrian Brock (ejort) Date: 2003-10-10 14:46 Message: Logged In: YES user_id=9459 Please use the jboss-user mailing list or forums for help. Not bug reports. You would configure it on the connection manager as I said before. e.g. mbean code=org.jboss.resource.connectionmanager.XATxConnectionManager name=jboss.jca:service=XATxCM,name=XAOracleDS attribute name=TrackConnectionByTxtrue/attribute depends optional-attribute-name=ManagedConnectionFactoryName Regards, Adrian -- Comment By: Eduard Letifov (techtime) Date: 2003-10-10 11:21 Message: Logged In: YES user_id=438410 I have tested it with 3.2.2 running on Windows connecting to DB2 running V5R2 AS400. Both parameters (trackConnnection and RMOverride) had to be set to true and false respectively. Good news for the future. I wasn't able to find this attribute in 3.0.8 source though, can you help me on that? Ed. -- Comment By: Adrian Brock (ejort) Date: 2003-10-09 21:07 Message: Logged In: YES user_id=9459 Minerva hasn't been in jboss for a while, 2.4 I think The transaction implementation is different
[JBoss-dev] [ jboss-Bugs-820711 ] Problem with XA and DB2 for iSeries XA drivers
Bugs item #820711, was opened at 2003-10-09 16:01 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=820711group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole Status: Open Resolution: Accepted Priority: 5 Submitted By: Eduard Letifov (techtime) Assigned to: Adrian Brock (ejort) Summary: Problem with XA and DB2 for iSeries XA drivers Initial Comment: This problem seem to be very simular to the one reported in 585632. We have several EJB beans (Session and Entity) participating in one transaction started by MDB that also uses XA JMS in the end. The first call that involves database goes fine. From trace logs I see that XAResource gets enlisted and delisted. Resource state is set to RS_ENDED. As soon as the second method is called (and connection is requested) TxCapsule tries to enlist and start the same resource. This caused an XAException (XAER_INVAL) with DB2 for iSeries (AS400) XA toolbox (thin) drivers. I was able to overcome this by specifying the same (IsSameRMOverrideValue=false) flag as for Oracle XA datasource. In this case (as I beleive it was intended) the resource is started with a new XA branch (JBoss_3_0_8, TxCapsule.java, lines: 702-737) Unfortunately it is also marked as being one from a new RM (line 737). Thus, when transaction is finished and TxCapsule starts preparing XAResources the same RM check does not work (line 1635) and the resource gets called multiple times. The first call returns some valid READ_ONLY result, but the second one fails with XAER_PROTO. As I figured out unlike Oracle, DB2 wants only one prepare and one commit per RM. I was able to overcome this by performing these patches: - when the resource is started with the new branch the idx of the originally found resource is recorded additionally. - if the XAException with code XAER_PROTO is thrown in the prepare stage and this originally found index is not (- 1) it is ignored and the prepare state is assumed to be the same as for originally found (and already prepared) resource - if the XAException with code XAER_PROTO is thrown in the commit stage and the originally found index is not (- 1) it is ignored. It seem to work both for DB2 and Oracle. It does produce multiple calls to resources on prepare and commit that for DB2 fail all except the first one. I understand that this impacts perfomance, but the other option. My operating system is WinXP, JDK1.3.1_06. I have looked in Jboss 3.2.2 source and I see that basically the code is the same. Please confirm that this is in fact the way to solve the problem. -- Comment By: Adrian Brock (ejort) Date: 2003-10-10 12:46 Message: Logged In: YES user_id=9459 Sorry, I must have been looking at the wrong source tree. You are correct that attribute is not in 3.0 The only sensible solution would be to backport the 3.2 jca implementation to 3.0 but I don't think that is straight forward. I am unlikely to do it in the near future, I'm currently working on the 3.2.2 final release. Maybe you can look at the TxConnectionManager in 3.2 and apply the processing yourself to the XATxConnectionManager in 3.0? Regards, Adrian -- Comment By: Eduard Letifov (techtime) Date: 2003-10-10 12:30 Message: Logged In: YES user_id=438410 Adrian, I have a problem. A problem in Jboss 3.0.8. A release. Not release candidate or beta, etc. I've spent 2 days on it before I turned to you. I did what I can do. I identified the problem. I tried to overcome it with a patch. Since the behaviour was changed in 3.2.2 I guess something was wrong with it, heh? Not a bug, rejected, fixed in 3.2, use 3.2 is definately a solution, but maybe not the only one? As I understand in order for what you are suggesting to work the underlying MBean has to have this attribute and corresponding setters/getters. In my 3.0.8 source it doesn't. Neither does the implementation. Obviously I am getting org.jboss.deployment.DeploymentException: No Attribute found with name: TrackConnectionByTx exception? would you consider this a bug? Ed -- Comment By: Adrian Brock (ejort) Date: 2003-10-10 10:46 Message: Logged In: YES user_id=9459 Please use the jboss-user mailing list or forums for help. Not bug reports. You would configure it on the connection manager as I said before. e.g. mbean code=org.jboss.resource.connectionmanager.XATxConnectionManager name=jboss.jca:service=XATxCM,name=XAOracleDS attribute name=TrackConnectionByTxtrue/attribute depends optional-attribute-name=ManagedConnectionFactoryName Regards, Adrian -- Comment By: Eduard Letifov (techtime) Date:
[JBoss-dev] [ jboss-Bugs-812390 ] ejbActivate in EntityBean not called
Bugs item #812390, was opened at 2003-09-25 11:42
Message generated for change (Comment added) made by ejort
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=812390group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: Juergen Schwarz (juergenschwarz)
Assigned to: Nobody/Anonymous (nobody)
Summary: ejbActivate in EntityBean not called
Initial Comment:
Hi,
i have noticed, that when an Entity Bean gets
passivated, the container calls ejbPassivate(), but when
it should be used again (activated again), the container
does not call ejbActivate().
The container only calls ejbActivate() when a Bean
instance is initally created.
JBoss Version: 3.2, 3.2.1, 3.2.2RC4
Operating System: Windows 2000, Windows XP
JDK: Sun JDK 1.4.2
Regards
Juergen Schwarz
--
Comment By: Adrian Brock (ejort)
Date: 2003-10-10 13:31
Message:
Logged In: YES
user_id=9459
I don't see this.
ejbActivate is invoked after an ejbPassivate
Please provide more information and/or a testcase.
Regards,
Adrian
--
Comment By: Robert Wang (linubert)
Date: 2003-10-08 06:46
Message:
Logged In: YES
user_id=882544
the container does call ejbActivate() when an Entity Bean is
in passivated state, the code is here:
protected void activate(EnterpriseContext ctx) throws
RemoteException
{
m_container.getPersistenceManager().activateEntity
((EntityEnterpriseContext)ctx);
}
in org.jboss.ejb.plugins.EntityInstanceCache.java, and the
container does not call ejbActivate() when the Entity Bean is
still in the cache(not passivated).
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=812390group_id=22866
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 3.2.2 Issues to resolve
On Fri, 2003-10-03 at 12:29, Scott M Stark wrote: The following open issues need to be addressed in order to put out the 3.2.2 final release. The current target release date is 2003-10-12. I've edited Scott's list to show the remaining open bugs: 811269deadlock in JettyMBean and PluginManager OPEN - unassigned 808170Partition problems 3.2.2RC4 OPEN - bela 795782Random ClassCircularityError OPEN - unassigned 795191env-entry not in jndi when not using JBossWebLoader OPEN - scott 794699Deployment of ear throws null pointer execption in org.jboss OPEN - unassigned 791439HA-JNDI not replicating bindings OPEN - sacha 789318ObjectMessage.getObject() doesn't work in JBoss 3.2.1 OPEN - unassigned 786668Form-based Authentication drops Subject OPEN - unassigned Regards, Adrian -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 3.2.2 Issues to resolve
FYI, 791439 is not critical, works for all usual scenarios so I will personnaly not fix it for 3.2.2. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Brock Sent: vendredi, 10. octobre 2003 15:56 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 3.2.2 Issues to resolve On Fri, 2003-10-03 at 12:29, Scott M Stark wrote: The following open issues need to be addressed in order to put out the 3.2.2 final release. The current target release date is 2003-10-12. I've edited Scott's list to show the remaining open bugs: 811269 deadlock in JettyMBean and PluginManager OPEN - unassigned 808170 Partition problems 3.2.2RC4 OPEN - bela 795782 Random ClassCircularityError OPEN - unassigned 795191 env-entry not in jndi when not using JBossWebLoader OPEN - scott 794699 Deployment of ear throws null pointer execption in org.jboss OPEN - unassigned 791439 HA-JNDI not replicating bindings OPEN - sacha 789318 ObjectMessage.getObject() doesn't work in JBoss 3.2.1 OPEN - unassigned 786668 Form-based Authentication drops Subject OPEN - unassigned Regards, Adrian -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 3.2.2 Issues to resolve
On Fri, 2003-10-10 at 15:07, Sacha Labourey wrote:
FYI, 791439 is not critical, works for all usual scenarios so I will
personnaly not fix it for 3.2.2.
And 789318 is an untrapped configuration error where a jar can
be deployed twice if you include a jar in /deploy in the classpath
element of a -service.xml file.
Not a critical fix.
What about the plugin manager? Can the synchronization be easily
fixed? This bug hangs the deployment thread.
Regards,
Adrian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Adrian Brock
Sent: vendredi, 10. octobre 2003 15:56
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] 3.2.2 Issues to resolve
On Fri, 2003-10-03 at 12:29, Scott M Stark wrote:
The following open issues need to be addressed in order to
put out the 3.2.2
final release. The current target release date is 2003-10-12.
I've edited Scott's list to show the remaining open bugs:
811269deadlock in JettyMBean and PluginManager
OPEN - unassigned
808170Partition problems 3.2.2RC4
OPEN - bela
795782Random ClassCircularityError
OPEN - unassigned
795191env-entry not in jndi when not using JBossWebLoader
OPEN - scott
794699Deployment of ear throws null pointer execption
in org.jboss
OPEN - unassigned
791439HA-JNDI not replicating bindings
OPEN - sacha
789318ObjectMessage.getObject() doesn't work in JBoss 3.2.1
OPEN - unassigned
786668Form-based Authentication drops Subject
OPEN - unassigned
Regards,
Adrian
--
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
--
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-613225 ] stateful session bean timeout
Bugs item #613225, was opened at 2002-09-23 16:33 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=613225group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Invalid Priority: 5 Submitted By: Peter Doornbosch (pieterpeter) Assigned to: Laurent Etiemble (letiemble) Summary: stateful session bean timeout Initial Comment: When a stateful session bean times out, the client gets a TransactionRolledbackException. Shouldn't this be a NoSuchObjectException? From the spec (ejb 2.0, section 7.6, page 79): If a client attempts to invoke the session object, the Container will throw the java.rmi.NoSuchObjectException if the client is a remote client (...). environment: Linux, Jdk 1.3.1 From the server trace: 2002-09-20 15:57:27,741 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackException, causedBy: java.rmi.NoSuchObjectException: Could not activate; nested exception is: java.io.FileNotFoundException: /usr/local/jboss-3.0.0/server/aeos/db/sessions/ObjectIdRetailer/1032530011403.ser (No such file or directory) at org.jboss.ejb.plugins.AbstractInstanceCache.get(AbstractInstanceCache.java:185) at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:212) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:142) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:380) at org.jboss.ejb.Container.invoke(Container.java:705) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:102) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) at org.jboss.proxy.ejb.StatefulSessionInterceptor.invoke(StatefulSessionInterceptor.java:117) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 16:24 Message: Logged In: YES user_id=437455 Your stack trace shows that the Exception is raised during the ejbActivate invocation. According to the spec (EJB 2.0 18.3.3), the container can throw a TransactionRolledbackException during a container callback method invocation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=613225group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-811269 ] deadlock in JettyMBean and PluginManager
Bugs item #811269, was opened at 2003-09-23 18:40 Message generated for change (Comment added) made by slaboure You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=811269group_id=22866 Category: JBossWeb Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jeff Gettle (jgettle) Assigned to: Sacha Labourey (slaboure) Summary: deadlock in JettyMBean and PluginManager Initial Comment: We're running jboss-3.2.2RC4_jetty-4.2.11 when we startup JBoss we are seeing the following deadlock sometimes. Found one Java-level deadlock: = PoolThread-3: waiting to lock monitor 0x0010e158 (object 0xd600b9c8, a org.jboss.jetty.JettyMBean), which is held by main main: waiting to lock monitor 0x0010e238 (object 0xd5e93948, a org.jboss.console.manager.PluginManager), which is held by PoolThread-3 Java stack information for the threads listed above: === PoolThread-3: at org.mortbay.util.jmx.ModelMBeanImpl.getMBeanInfo(ModelMBeanImpl.java:590) - waiting to lock 0xd600b9c8 (a org.jboss.jetty.JettyMBean) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:568) at org.jboss.console.plugins.helpers.jmx.Server.getDomainData(Server.java:53) at org.jboss.console.plugins.MBeansLister.createJmxDomainsSubNodes(MBeansLister.java:69) at org.jboss.console.plugins.MBeansLister.getTreeForResource(MBeansLister.java:122) at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(AbstractPluginWrapper.java:201) at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392) at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.console.manager.PluginManager.getUpdateTreeForProfile(PluginManager.java:275) - locked 0xd5e93948 (a org.jboss.console.manager.PluginManager) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:86) at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:123) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1723) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:514) at org.mortbay.http.HttpContext.handle(HttpContext.java:1673) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.jboss.jetty.Jetty.service(Jetty.java:459) at org.mortbay.http.HttpConnection.service(HttpConnection.java:783) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:945) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:800) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454) main: at org.jboss.console.manager.PluginManager.handleNotification(PluginManager.java:372) - waiting to lock 0xd5e93948 (a org.jboss.console.manager.PluginManager) at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:69) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:95) at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:99) at org.jboss.mx.server.registry.BasicMBeanRegistry.unregisterMBean(BasicMBeanRegistry.java:323) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at
[JBoss-dev] [ jboss-Bugs-821261 ] JacORB .properties file is out-of-date
Bugs item #821261, was opened at 2003-10-10 14:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821261group_id=22866 Category: JBossIIOP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Richard Begg (rabegg) Assigned to: Francisco Reverbel (reverbel) Summary: JacORB .properties file is out-of-date Initial Comment: The JacORB properties file in thirdparty/jacorb/jacorb/config/default hasn't been updated since JacORB was updated to 2.0 beta 2. One of the side affects of this is the configuration points JacORB to use a hashtable implementation which no longer exists (i.e. org.jacorb.util.WeakHashtable) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821261group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 3.2.2 Issues to resolve
Title: Re: [JBoss-dev] 3.2.2 Issues to resolve Hi, Bug #794699 is the same as patch #795164, And it seams that Scott has fixed it. See comments inside the patch #795164. -- Christer Grimsæth
[JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk? missing in jbosscmp-jdbc_3_0
Bugs item #643739, was opened at 2002-11-25 21:04 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=643739group_id=22866 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Harald Venström (hvenstrom) Assigned to: Laurent Etiemble (letiemble) Summary: unknown-pk? missing in jbosscmp-jdbc_3_0 Initial Comment: The optional defaults element unknown-pk? is missing in the online document: http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd for reason unknowed it seem to have been lost in the latest update? (fFrom the 22/11...). -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 17:52 Message: Logged In: YES user_id=437455 This feature is only available in 3.2.0. That why it doesn't not appear in the dtd. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=643739group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
FW: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk? missing in jbosscmp-jdbc_3_0
Laurent is our new bug-report serial-killer!!! ;) That's great, thanks! I did it once, it was good to close all these cases! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SourceForge.net Sent: vendredi, 10. octobre 2003 17:52 To: [EMAIL PROTECTED] Subject: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk? missing in jbosscmp-jdbc_3_0 Bugs item #643739, was opened at 2002-11-25 21:04 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=643739group_id =22866 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Harald Venström (hvenstrom) Assigned to: Laurent Etiemble (letiemble) Summary: unknown-pk? missing in jbosscmp-jdbc_3_0 Initial Comment: The optional defaults element unknown-pk? is missing in the online document: http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd for reason unknowed it seem to have been lost in the latest update? (fFrom the 22/11...). -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 17:52 Message: Logged In: YES user_id=437455 This feature is only available in 3.2.0. That why it doesn't not appear in the dtd. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=643739group_id =22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [jboss-group] FW: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk?missing in jbosscmp-jdbc_3_0
Let's get laurent on board, it seems our bravo ta bite comment made it through, he buys it :) Cool, Sacha keep a close eye on this guy he is good, marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sacha Labourey Sent: Friday, October 10, 2003 11:56 AM To: [EMAIL PROTECTED] Subject: [jboss-group] FW: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk?missing in jbosscmp-jdbc_3_0 Laurent is our new bug-report serial-killer!!! ;) That's great, thanks! I did it once, it was good to close all these cases! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SourceForge.net Sent: vendredi, 10. octobre 2003 17:52 To: [EMAIL PROTECTED] Subject: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk? missing in jbosscmp-jdbc_3_0 Bugs item #643739, was opened at 2002-11-25 21:04 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=6 43739group_id =22866 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Harald Venström (hvenstrom) Assigned to: Laurent Etiemble (letiemble) Summary: unknown-pk? missing in jbosscmp-jdbc_3_0 Initial Comment: The optional defaults element unknown-pk? is missing in the online document: http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd for reason unknowed it seem to have been lost in the latest update? (fFrom the 22/11...). -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 17:52 Message: Logged In: YES user_id=437455 This feature is only available in 3.2.0. That why it doesn't not appear in the dtd. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=6 43739group_id =22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ jboss-group mailing list [EMAIL PROTECTED] http://mail.jboss.org/mailman/listinfo/jboss-group --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [jboss-group] FW: [JBoss-dev] [ jboss-Bugs-643739 ]unknown-pk?missing in jbosscmp-jdbc_3_0
bring him the america:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of marc fleury Sent: Friday, October 10, 2003 1:21 PM To: 'Private list for internal JBoss Group discussion'; [EMAIL PROTECTED] Subject: RE: [jboss-group] FW: [JBoss-dev] [ jboss-Bugs-643739 ]unknown-pk?missing in jbosscmp-jdbc_3_0 Let's get laurent on board, it seems our bravo ta bite comment made it through, he buys it :) Cool, Sacha keep a close eye on this guy he is good, marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sacha Labourey Sent: Friday, October 10, 2003 11:56 AM To: [EMAIL PROTECTED] Subject: [jboss-group] FW: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk?missing in jbosscmp-jdbc_3_0 Laurent is our new bug-report serial-killer!!! ;) That's great, thanks! I did it once, it was good to close all these cases! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SourceForge.net Sent: vendredi, 10. octobre 2003 17:52 To: [EMAIL PROTECTED] Subject: [JBoss-dev] [ jboss-Bugs-643739 ] unknown-pk? missing in jbosscmp-jdbc_3_0 Bugs item #643739, was opened at 2002-11-25 21:04 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=6 43739group_id =22866 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Harald Venström (hvenstrom) Assigned to: Laurent Etiemble (letiemble) Summary: unknown-pk? missing in jbosscmp-jdbc_3_0 Initial Comment: The optional defaults element unknown-pk? is missing in the online document: http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd for reason unknowed it seem to have been lost in the latest update? (fFrom the 22/11...). -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 17:52 Message: Logged In: YES user_id=437455 This feature is only available in 3.2.0. That why it doesn't not appear in the dtd. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=6 43739group_id =22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ jboss-group mailing list [EMAIL PROTECTED] http://mail.jboss.org/mailman/listinfo/jboss-group ___ jboss-group mailing list [EMAIL PROTECTED] http://mail.jboss.org/mailman/listinfo/jboss-group --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Heavy TrapdService logging
Hello, Is it really useful to have all that SNMP logging information as part of the default logging level in the console in 3.2.2? It is really verbose and pops-up whenever a new JBoss instance starts on the network. Cheers, Sacha --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-808170 ] Partition problems 3.2.2RC4
Bugs item #808170, was opened at 2003-09-17 23:19 Message generated for change (Comment added) made by slaboure You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=808170group_id=22866 Category: Clustering Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Adrian Brock (ejort) Assigned to: Bela Ban (belaban) Summary: Partition problems 3.2.2RC4 Initial Comment: JBoss-3.2.2RC4 (current CVS) Java1.4.2 Redhat 9 I'm seeing problems with nodes in a partition discovering each other. Sometimes it works, Sometimes is doesn't (see attached console.log and console2.log) I have cluster logs as well if you need them. Shutdown blocks on the partition when it fails (see threaddumps at end of logs) Sometimes I get a NullPointerException 03-09-17 19:07:32,545 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.Def aultPartition] Get current members 2003-09-17 19:07:32,546 INFO [org.jboss.ha.framework.interfaces.HAPartition.Def aultPartition] Number of cluster members: 2 2003-09-17 19:07:32,556 INFO [org.jboss.ha.framework.interfaces.HAPartition.Def aultPartition] Other members: 1 2003-09-17 19:07:32,566 WARN [org.jboss.ha.framework.interfaces.HAPartition.Def aultPartition] No additional information has been found in the JavaGroup address : make sure you are running with a correct version of JavaGroups and that the pr otocol you are using supports the 'additionalData' behaviour 2003-09-17 19:07:32,577 ERROR [org.jboss.ha.framework.server.ClusterPartition] S tarting failed java.lang.NullPointerException at org.jboss.ha.framework.server.HAPartitionImpl.verifyNodeIsUnique(HAPa rtitionImpl.java:763) at org.jboss.ha.framework.server.HAPartitionImpl.startPartition(HAPartit ionImpl.java:236) at org.jboss.ha.framework.server.ClusterPartition.startService(ClusterPa rtition.java:293) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1 92) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces Regards, Adrian -- Comment By: Sacha Labourey (slaboure) Date: 2003-10-10 20:21 Message: Logged In: YES user_id=95900 New JGroups release added to both Branch_3_2 and HEAD. -- Comment By: Sacha Labourey (slaboure) Date: 2003-10-07 12:38 Message: Logged In: YES user_id=95900 Bela, do you have a more definitive fix, or do we have to implement the flush trick, update the jar and close the bug? Is JG stable now for a JB release/tag? Cheers, sacha -- Comment By: Adrian Brock (ejort) Date: 2003-09-25 16:45 Message: Logged In: YES user_id=9459 Works for me. Can we have a tagged version so I can check it out and include it in jboss. Regards, Adrian -- Comment By: Adrian Brock (ejort) Date: 2003-09-25 02:20 Message: Logged In: YES user_id=9459 Hi Bela, I only have pserver access to JGroups cvs (about 24 hours behind). Could you or Sacha update the jar in jboss's thirdparty? Regards, Adrian -- Comment By: Bela Ban (belaban) Date: 2003-09-25 01:31 Message: Logged In: YES user_id=34890 Okay, new fix in JGroups (try out org.jgroups.tests.AddDataTest): JChannel c=new JChannel(); c.down(new Event(Event.CONFIG)); c.getProtocolStack().flushEvents(); // -- new c.connect(); Not nice, but it works... Bela -- Comment By: Adrian Brock (ejort) Date: 2003-09-23 21:14 Message: Logged In: YES user_id=9459 Looks like the problem is the config event is temporarily not in any queues so waiting for the queues to become empty does not work. Thread[DownHandler (STABLE),5,main] Remove internal Queue (1) messages Event[type=CONFIG, [EMAIL PROTECTED] Thread[DownHandler (STABLE),5,main] removeInternal waiting for remove_mutex Thread[DownHandler (STABLE),5,main] removeInternal got remove_mutex Thread[DownHandler (STABLE),5,main] removeInternal releasing remove_mutex Thread[main,5,main] waitUnitEmpty releasing remove_mutex Thread[main,5,main] flushed down queue Queue (0) messages Thread[main,5,main] flushing down queue Queue (0) messages Thread[main,5,main] waitUnitEmpty waiting for remove_mutex Thread[main,5,main] waitUnitEmpty got remove_mutex Thread[main,5,main] waitUnitEmpty releasing remove_mutex Thread[main,5,main] flushed down queue Queue (0) messages Thread[main,5,main] flushing down queue Queue (0) messages Thread[main,5,main] waitUnitEmpty waiting for remove_mutex Thread[main,5,main] waitUnitEmpty got remove_mutex Thread[main,5,main] waitUnitEmpty releasing remove_mutex Thread[main,5,main] flushed down queue
[JBoss-dev] [ jboss-Bugs-821030 ] Packager fails when using multiple projects
Bugs item #821030, was opened at 2003-10-10 09:27 Message generated for change (Comment added) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821030group_id=22866 Category: JBoss-IDE Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Thomas Hallgren (thhal) Assigned to: Laurent Etiemble (letiemble) Summary: Packager fails when using multiple projects Initial Comment: I'm using JDK Version 1.4.2 on Windows. How to reproduce the bug: The objective is to use the JBoss-IDE packager to create a jar file that contains classes from output directories residing in different projects. All projects are in the same workspace. 1. Create an archive in Packaging Configurations and do an Add Folder. 2. In this dialog i click Project Folder. The result is a list of all available projects in the workspace. 3. Select a folder in a project different from the one that owns the configuration. 4. Click OK twice (to get rid of the selection box and the box where I configure includes etc.). You can now see an entry that appears to be correct in the Packaging Configuration. 5. Click OK. So far so good. 6. Bring the same Packaging Configuration up again, the folder is changed so that it instead belongs to the project that owns the configuration! -- Comment By: Laurent Etiemble (letiemble) Date: 2003-10-10 23:17 Message: Logged In: YES user_id=437455 Fixed in HEAD -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821030group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-821505 ] Completion proposal appear at the bottom
Bugs item #821505, was opened at 2003-10-10 23:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821505group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Laurent Etiemble (letiemble) Assigned to: Laurent Etiemble (letiemble) Summary: Completion proposal appear at the bottom Initial Comment: As silently reported by Rod Macpherson on the user list, completion proposal appears at the bottom of the list which makes the use of the completion a hassle. Relevance level of the proposal should be increase to make them appear at first. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821505group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-821505 ] Completion proposal appear at the bottom
Bugs item #821505, was opened at 2003-10-10 23:49 Message generated for change (Settings changed) made by letiemble You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821505group_id=22866 Category: JBoss-IDE Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Laurent Etiemble (letiemble) Assigned to: Laurent Etiemble (letiemble) Summary: Completion proposal appear at the bottom Initial Comment: As silently reported by Rod Macpherson on the user list, completion proposal appears at the bottom of the list which makes the use of the completion a hassle. Relevance level of the proposal should be increase to make them appear at first. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821505group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] IMPORTANT
CENTRAL BANK OF NIGERIA TINUBU SQUARE LAGOS, NIGERIA. Dear It's my pleasure to send you this mail which I hope you will treat as highly confidential. I am Mr Jubril Martin,A 53 years old man and the Deputy Treasury Officer with the Central Bank of Nigeria lagos.During the Military regime of Late General Sani Abacha, contracts running into several millions of dollars were awarded to friends and cronies fronting for the late despotic ruler,but unfortunately before such payments could go through, he died mysteriously in power. I am writting you for assistance in transfering the sum of US$36.8 million dollars into your account.This amount represents just a payment due to one of his friends for a contract awarded to him but was not actually executed,he is afraid to come forward to claim the money for fear of being prosecuted. This money is lying dormant in the vaults of the Central Bank of Nigeria and I use this opportunity to crave your indulgience in transfering this money into any account which we shall agree on with you as the beneficiary.This business is totally risk free,it is only me that is aware of this floating money.For your assistance,I am willing to give you 30% of the total sum,while you will assist me in investing my share in viable businesses in your country pending when I eventually resign my appointment and join you. Please if you know you can assist me,endeavour to get in touch with me as soon as possible so i can give you the necessary details so as to conclude the transaction within 7 working days. I am waiting for your urgent messages with respect to this proposal. Regards, Mr.Jubril Martin --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: 98 % ( 1578 / 1602 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sat Oct 11 01:09:50 GMTDT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1602 Successful tests: 1578 Errors:19 Failures: 5 [time of test: 2003-10-10.23-19 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/logtests/testresults/reports/html//2003-10-10.23-19 for the junit report of this test. 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. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: RemotingUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: LocalUnitTestCase Test:testRemove Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: D:\jboss\jboss-head-test\build\output\testbuild\server\all\tmp\sessions\test\TreeCacheAopTester-dlmuq9zk-16\dlmuqbv9-1b.ser (The system cannot find the file specified) - Suite: ScopedTransactionUnitTestCase Test:testScopedTransaction Type:error Exception: javax.naming.NameNotFoundException Message: ScopedTxTestSession not bound - Suite: ScopedTransactionUnitTestCase Test:testServerFound Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: ScopedTransactionUnitTestCase Test:unknown Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: CompleteUnitTestCase Test:testJBossQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:...NOT(t1_o1_customer.id = t2_o2_customer.id)) AND (t0_o1.CC_TYPE = t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME = t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI = t3_o2.CC_MI AND t0_o1.CC_LAST_NAME = t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP = t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER = ... but was:... NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=... === Sat Oct 11 01:09:50 GMTDT 2003 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-821261 ] JacORB .properties file is out-of-date
Bugs item #821261, was opened at 2003-10-10 14:50 Message generated for change (Comment added) made by reverbel You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821261group_id=22866 Category: JBossIIOP Group: v3.2 Status: Closed Resolution: None Priority: 5 Submitted By: Richard Begg (rabegg) Assigned to: Francisco Reverbel (reverbel) Summary: JacORB .properties file is out-of-date Initial Comment: The JacORB properties file in thirdparty/jacorb/jacorb/config/default hasn't been updated since JacORB was updated to 2.0 beta 2. One of the side affects of this is the configuration points JacORB to use a hashtable implementation which no longer exists (i.e. org.jacorb.util.WeakHashtable) -- Comment By: Francisco Reverbel (reverbel) Date: 2003-10-11 00:18 Message: Logged In: YES user_id=30391 Good catch! I have fixed this in HEAD and Branch_3_2. Thanks for the bug report, Francisco -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=821261group_id=22866 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 98 % ( 1577 / 1602 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sat Oct 11 01:45:41 BST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1602 Successful tests: 1577 Errors:19 Failures: 6 [time of test: 2003-10-10.23-28 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-20.7] Useful resources: - http://jboss.kimptoc.net/linux1/logtests/testresults/reports/html//2003-10-10.23-28 for the junit report of this test. 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. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: RemotingUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: LocalUnitTestCase Test:testRemove Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: /home/jbossci/jbossci2/jboss-head-test/build/output/testbuild/server/all/tmp/sessions/test/TreeCacheAopTester-dlmv6j68-16/dlmv6s8q-1b.ser (No such file or directory) - Suite: TxConcurrentUnitTestCase Test:testConcurrentAccess Type:failure Exception: junit.framework.AssertionFailedError Message: java.lang.RuntimeException: release(): lock map owner Thread[main,5,main]not found - Suite: ScopedTransactionUnitTestCase Test:testScopedTransaction Type:error Exception: javax.naming.NameNotFoundException Message: ScopedTxTestSession not bound - Suite: ScopedTransactionUnitTestCase Test:testServerFound Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/scopedtx.jar - Suite: ScopedTransactionUnitTestCase Test:unknown Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/scopedtx.jar === Sat Oct 11 01:45:41 BST 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] turn JBoss into an LDAP server
Actually the mail server stuff might help with LDAP. Its just another protocol. On 9/29/03 5:09 AM, Bill Burke [EMAIL PROTECTED] wrote: Andy Oliver is working on a mail server. Contact him if you want to work on that. Bill Ionel GARDAIS wrote: --- Rupp, Heiko [EMAIL PROTECTED] a écrit : That is something that I'd be interested in (as developer), but I can't promise any timeframe at the moment. So do I. I am looking after a thing to develop to get involve in JBoss I thought of an LDAP server but also a mail server (smtp/pop/imap). These two server could use EJB to store datas. I am still wondering if these kind of applications should be developped as a part of JBoss or as a standalone application, able to deploy on any application server See you later, I'm going back to LDAP rfc readings :) Ionel ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Andy Oliver's mail address
Oh crap now I'll be spammed on that account too (mail scanners will pick it up) :-/ Anyhow, I do monitor this list and the mail services forum. I'm on the road ATM at customer sites,etc. So I'm just latent. -Andy On 9/30/03 5:27 AM, Bill Burke [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] Ionel GARDAIS wrote: Hi, Does anybody have Andy Oliver's email address ? I have been told he is developping a mail server for JBoss thanks, ionel ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Rx: VICODIN is Here - Just Pennies per Tablet.................. zja
bfont size=5Rx Outlet/font/bpVicodon on sale for a limited time. br Free shipping on a 3 month supply (90-count).br Hurry while this offer lasts./p p a href=http://www.rxpalace.biz/superstore/group.asp?g=128;ENTER The Pharmacy/a/p /p It's easy to order from Pharmacy Worldwide. Just follow these simple steps: br --Choose the prescription of your choicebr --Fill out the online medical questionaire when you checkout br --A physician will review your medical info and issue your free prescription, if approved br --Your order will arrive the next business day in discreet package for your privacy br br Included: Free medical consultation with a qualified physician.p a href=http://www.rxpalace.biz/superstore/group.asp?g=128;ENTER The Pharmacy/abr br Vicodin ES 30 tabletsnbsp; - $4.63 per tabletbr bfont size=4Vicodin/fontfont size=4 ES 90 tablets - $2.32 per tablet - BEST DEAL - Plus FREE SHIPPING/font/b/p p a href=http://www.rxpalace.biz/superstore/group.asp?g=128;ENTER The Pharmacy/a/p /p br br If you wish to be excluded from future mailings - a href=http://www.rxpalace.biz/a.html;Go Here/a br br br br brivtjxw kvr rxalkybvlgmi eofdmij fnnza bepcglvci
