[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1283) Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for Webapp
[ http://jira.jboss.com/jira/browse/JBAS-1283?page=comments#action_12316788 ] Tomislav Bodor commented on JBAS-1283: -- I can't figure out how to attach a war file to my comment. However, this issue is actually very simple to reproduce: 1. Put xercesImpl.jar and xml-apis.jar in WEB-INF/lib. Any version should do, even the same one as in JBoss - the conflict comes from the class loaders, not different classes. 2. To enable scoping, and allow overriding, make a jboss-web.xml that looks like this: http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd";> scoped.war:loader=scoped.war java2ParentDelegation=false 3. Add an (almost) empty web.xml: http://java.sun.com/dtd/web-app_2_3.dtd";> 4. Add an index.jsp to the root of the war file. It can be completely empty, but I put a hello world in mine. That's it. Now deploy in an out of the box JBoss, any version from 3.2.6 above, including 4.0.2RC1. Go to the index.jsp and see it fail (stack trace is below). Ensure that the jsp hasn't already been compiled - once it succeeds, it is preserved by JBoss and will run fine. Only compilation fails. To make sure it is recompiled, go to JBoss/server/$profile/work and delete jboss.web directory from there. Stack trace: org.apache.jasper.JasperException: Unable to compile class for JSP org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:565) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) root cause java.lang.ClassCastException javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:91) org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:70) org.apache.jasper.compiler.JspConfig.init(JspConfig.java:188) org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:240) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:103) org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) org.apache.jasper.compiler.Compiler.compile(Compiler.java:267) org.apache.jasper.compiler.Compiler.compile(Compiler.java:255) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) I've got a war file ready, so if you tell me how to attach it, I can. Regards, Tomislav > Tomcat Unable to Compile JSPs when Separate ClassLoader Namespace Used for > Webapp > - > > Key: JBAS-1283 > URL: http://jira.jboss.com/jira/browse/JBAS-1283 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-3.2.6 Final > Environment: Stock JBoss 3.2.6 running on Linux (kernel 2.4.26), Sun JDK and > JRE version 1.4.2_04 > Reporter: Jeremy Brown > Assignee: Anil Saldhana > Priority: Minor > Attachments: test.war > > > See my initial forum post at > "http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861452#3861452";. > The dom4j libs provided by JBoss do not work correctly with my web > application, so I attempted to configure my webapp's "jboss-web.xml"--as per > the wiki page at > "http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration"--so that > my webapp would essentially be in a different classloader namspace and would > be able to override the server dom4j implementation with its own. Now, > Tomcat bails out during JSP compilation with a dom4j-related > ClassCastException, leading me to believe there might some problem with the > sort of setup I'm trying to attempt...for example, Tomcat's JSP compiler > might be trying to link with the dom4j in my application's namespace while > its classes have been loaded next to (and probably are already using) dom4j > in the server namespace. > I'll attach a .war file exhibiting this behavior to this bug report. > Here's the specific exception for this .war file: > java.lang.ClassCastException > at > javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:93) > at > org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:91) > at > o
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1576) Hibernate TransactionSynch should rollback transaction on session.flush exception
[ http://jira.jboss.com/jira/browse/JBAS-1576?page=history ]
Steve Ebersole resolved JBAS-1576:
--
Resolution: Done
Fix Version: JBossAS-4.0.2 Final
After further thought, this particular one is a trivial change so I went ahead
and did this for 4.0.2. An exception during flush processing in
TransactionSynch now throws a TransactionSynch.FlushException.
> Hibernate TransactionSynch should rollback transaction on session.flush
> exception
> -
>
> Key: JBAS-1576
> URL: http://jira.jboss.com/jira/browse/JBAS-1576
> Project: JBoss Application Server
> Type: Bug
> Components: Hibernate service
> Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1RC1, JBossAS-4.0.1 Final,
> JBossAS-4.0.0 Final
> Environment: jboss 4, hibernate 2.2
> Reporter: Armin Haaf
> Assignee: Steve Ebersole
> Fix For: JBossAS-4.0.2 Final
>
>
> org.jboss.hibernate.session.TransactionSynch only logs a error on session
> flush in beforeCompletion:
> try
> {
> log.trace("Flushing Session");
> session.flush();
> }
> catch(Throwable t)
> {
> log.warn("Error flushing session");
> }
> This leads to inconsistent transactions. A transaction is commited, but
> should be rollbacked on a session.flush problem. In my opinion it should
> throw a RuntimeException to rollback the transaction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-5) jmx transaction flush swallows exception
[ http://jira.jboss.com/jira/browse/HIBERNATE-5?page=history ] Steve Ebersole resolved HIBERNATE-5: Resolution: Done After further thought, this particular one is a trivial change so I went ahead and did this for 4.0.2. An exception during flush processing in TransactionSynch now throws a TransactionSynch.FlushException. > jmx transaction flush swallows exception > > > Key: HIBERNATE-5 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-5 > Project: Hibernate > Type: Bug > Environment: jboss-4.0.1 > winxp > postgresql > Reporter: Ben Litchfield > Assignee: Steve Ebersole > > > A database exception, such as constraint violation, doesn't happen until a > session.flush(). In the JMX code this happens in the > org.jboss.hibernate.session.TransactionSynch.beforeCompletion() method, but > the exception is swallowed. > This needs to be changed to throw an exception to the user. Otherwise no > exception is thrown to the user. > Ben -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-12) HibernateContext JDBC Connection
[ http://jira.jboss.com/jira/browse/HIBERNATE-12?page=comments#action_12316785 ] Steve Ebersole commented on HIBERNATE-12: - Sorry if I was not clear. The new code integration code I have locally upgrading the support to Hibernate3 will not be commited until *after* 4.0.2 is released. > HibernateContext JDBC Connection > > > Key: HIBERNATE-12 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-12 > Project: Hibernate > Type: Bug > Environment: Mac OSX, JBoss 4.01sp1 > Reporter: Stephen Pearson > Assignee: Steve Ebersole > > Original Estimate: 1 hour > Remaining: 1 hour > > When using the HibernateContext getSession() function call, all works well > until the function call has finished, and then the underlying JDBC connection > is not closed. Therefore with each call to getSession within my EJB I > promptly receieve a "Closing a connection for you. Please close them > yourself." warning from the CachedConnectionManager. > Can the TransactionSynch call please close the JDBC connection when it > flushes and closes the Hibernate Session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1664) Unloaded entities returned in low memory conditions
[ http://jira.jboss.com/jira/browse/JBAS-1664?page=comments#action_12316784 ] Arto Huusko commented on JBAS-1664: --- Yes, sorry, I do mean OutOfMemoryError. However, if it is true that JVM is unusable after OutOfMemoryError, JBoss should be changed to terminate immediately the first time it sees that error. And, I'm curious as to why the JVM itself bothers to throw an error, if it really is so that application can never do anything to recover. The fact is that in the face of OutOfMemoryError, the JVM really was surprisingly usable and in working state. Our code was able to do some real work off and on for hours while also seeing OOMEs -- but also some damage, when those BMP beans started misbehaving. And we had a heavily tweaked configuration: BMP beans with commit option A, maximum cache size of 1 instances and maximum memory of 1GB (which, though, is a slightly moot point because at the time we were bitten by issue JBAS-1662). Anyway, I feel very strongly that something should be done about this, even if it is that immediate termination of JVM, because otherwise some really bad things can happen if there is some other problem (be it in JBoss or application) that causes the JVM to run out of memory. > Unloaded entities returned in low memory conditions > --- > > Key: JBAS-1664 > URL: http://jira.jboss.com/jira/browse/JBAS-1664 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-3.2.6 Final > Reporter: Arto Huusko > > > In low memory conditions (that is, when OutOfMemoryExceptions are seen > frequently all over the place), JBoss can behave wrong in a way that is > critically wrong. > I have seen on several occasions that a finder returns an entity with the > correct identity, but where ejbLoad() has either not been called at all, or > where ejbLoad() has failed at some point (I have no way of knowing which is > the case). > I have observed this behaviour only with BMP beans (and so there is a > possibility that I am doing something wrong in the BMP code, but I doubt > this). However, the fact that I haven't seen this with CMP beans may be just > because CMP beans work differently, or just plain luck. When this occurs, the > wrong behaviour can be seen because the instance variables of the entity bean > contain what ever they had when the entity instance was previously attached > to some other identity. > For example, I may store the primary key of the entity in some instance > variable. Let's say I can access the primary key via method "Long > getMyPrimaryKey()". If the finder returns an entity with the correct identity > (what I asked for in the finder call), but where ejbLoad() is not called or > it fails, then >entity.getMyPrimaryKey().equals(entity.getPrimaryKey()) > is false. And this is exactly what I have seen. > I have no idea where the problem is, and, as I said above, it may be a > problem with my code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ] Steve Ebersole reassigned HIBERNATE-13: --- Assign To: Ryan Campbell (was: Steve Ebersole) > testEjbInterception Unit Test failure > - > > Key: HIBERNATE-13 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 > Project: Hibernate > Type: Bug > Environment: win xp sp2 > Reporter: Pushkala Iyer > Assignee: Ryan Campbell > > > The following test is failing in the 4.0 branch and needs to be resolved > before the 4.0.2 Final release. We've tested this in multiple environments > and received the same error. > Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase > Test : testEjbInterception > Stack Trace: > RemoteException occurred in server thread; nested exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested > throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > java.rmi.ServerException: RemoteException occurred in server thread; nested > exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) > at sun.rmi.transport.Transport$1.run(Transport.java:148) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:144) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) > at java.lang.Thread.run(Thread.java:534) > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown > Source) > at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) > at > org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.storeUser(Unknown Source) > at > org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at > org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) > at > org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) > at org.jboss.ejb.Container.invoke(Container.java:873) > at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(M
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316783 ] Steve Ebersole commented on HIBERNATE-13: - So did somebody change something? I finally was able to get a clean check out (yaay!). I built and ran the tests (sans any cheanges other than the ones from yesterday that Ryan mentions) and it ran fine. > testEjbInterception Unit Test failure > - > > Key: HIBERNATE-13 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 > Project: Hibernate > Type: Bug > Environment: win xp sp2 > Reporter: Pushkala Iyer > Assignee: Steve Ebersole > > > The following test is failing in the 4.0 branch and needs to be resolved > before the 4.0.2 Final release. We've tested this in multiple environments > and received the same error. > Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase > Test : testEjbInterception > Stack Trace: > RemoteException occurred in server thread; nested exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested > throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > java.rmi.ServerException: RemoteException occurred in server thread; nested > exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) > at sun.rmi.transport.Transport$1.run(Transport.java:148) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:144) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) > at java.lang.Thread.run(Thread.java:534) > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown > Source) > at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) > at > org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.storeUser(Unknown Source) > at > org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at > org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) > at > org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) > at org.jboss.ejb.Container.invoke(Container.java:873) > at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.In
[JBoss-dev] jboss-head-jdk-matrix build.103 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20050408000451Lbuild.103 BUILD COMPLETE - build.103Date of build: 04/08/2005 00:04:51Time to build: 24 minutes 49 secondsLast changed: 04/07/2005 18:42:00Last log entry: Fix the package names. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (36)1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/simple/HelloWs.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/serverside/ServerSideArtifactsTestCase.javaFix the package names.1.12modifiedejortwebservice/.classpathFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/custom/HelloCustomRemote.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/custom/HelloObj.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/doclit/DocStyleSEI.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/doclit/User.javaFix the package names.1.5modifiedejortwebservice/src/main/org/jboss/ws/soap/SOAPPartImpl.javaMake this compile1.9modifiedejortaspects/.classpathFix the eclipse build1.2modifiedejortj2se/src/tests/org/jboss/test/jmx/compliance/server/MBeanServerTEST.javaAvoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar.1.2modifiedejortj2se/src/tests/org/jboss/test/jmx/compliance/loading/MLetTEST.javaAvoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar.1.25modifiedpatriot1burkeejb3/build.xmldocs upgrade1.4modifiedpatriot1burkeejb3/docs/index.htmldocs upgrade1.6modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.htmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/build.xmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/reference/en/master.xmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/reference/en/modules/applicationtx.xmldocs upgrade1.3modifiedpatriot1burkeejb3/docs/reference/reference/en/modules/entity.xmldocs upgrade1.1addedpatriot1burkeejb3/docs/reference/reference/en/modules/entity_configuration.xmldocs upgrade1.1addedstarksmserver/src/resources/dtd/README-DTD.txtAdd readmes on the j2ee dtd/schema file terms1.1addedstarksmserver/src/resources/schema/README-SCHEMA.txtAdd readmes on the j2ee dtd/schema file terms1.4modifiedstarksmwebservice/src/main/org/jboss/ws/soap/SOAPPartImpl.javaFix the wildard import1.1addedstarksmthirdparty/licenses/sun-specs.txtA readme pointing to the spec associated descriptor redistribution terms and the dtd/schema files.1.18modifiedstarksmserver/src/main/org/jboss/ejb/plugins/jms/DLQHandler.javaUse a HashMap instead of a Hashable to copy the properties while making them writable as there can be nulls. Resolves (JBAS-1669) NullPointerException in DLQHandler.1.5modifiedpatriot1burkethirdparty/hibernate/lib/hibernate-annotations.jarupgrade to latest HibernateExt1.5modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.wikiupgrade to latest HibernateExt1.1addedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/bean/BlobEntity2.javaupgrade to latest HibernateExt1.2modifiedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/bean/LobTester.javaupgrade to latest HibernateExt1.6modifiedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/bean/LobTesterBean.javaupgrade to latest HibernateExt1.2modifiedpatriot1burkeejb3/docs/tutorial/blob/src/org/jboss/tutorial/blob/client/Client.javaupgrade to latest HibernateExt1.4modifiedpatriot1burkethirdparty/hibernate/lib/hibernate-annotations.jarupdate docs1.2modifiedpatriot1burkeaspects/RELEASE_NOTES.htmlupdate docs1.36modifiedpatriot1burkeaspects/build.xmlupdate docs1.2modifiedpatriot1burkeaop/docs/reference/reference/en/modules/installing.xmlupdate docs1.15modifiedpatriot1burkeaop/docs/reference/reference/en/modules/running.xmlupdate docs1.5modifiedpatriot1burkeaspects/src/main/org/jboss/aop/deployment/JBossClassPoolFactory.javadon't addUrl if shutting down.
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: injboss example doesn't seem to work
Hmmm...that's very strange. I downloaded JBoss 4.0.1sp1, installed jboss-aop 1.1.1, and ran ant deploy-ear-aop on in injboss example. JDK 1.5, Linux. Example worked fine. Added the jboss-app.xml from your post to aopexample.ear, example didn't work. Removed the jboss-app.xml, turned on isolated class loaders in ear-deployer.xml, example didn't work. Every time I turn on an isolated class loader, I get: INFO [STDOUT] EarExampleServlet.service() INFO [STDOUT] *** ExampleSessionBean.getValue() INFO [STDOUT] ExampleValue String Constructor INFO [STDOUT] ExampleValue String Constructor INFO [STDOUT] ExampleValue.getMessage() What could be different in our environments? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873160#3873160 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873160 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] CVS Checkout.
I just tried using pserver:[EMAIL PROTECTED] and I'm not seeing this problem so it must have been a transient issue. Scott Stark Chief Technology Officer JBoss Inc. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dave Smith > Sent: Thursday, April 07, 2005 6:39 AM > To: JBoss Devel > Subject: [JBoss-dev] CVS Checkout. > > I am trying to do a fresh checkout of jboss-head and am getting .. > > cannot open > security/src/main/org/jboss/security/srp/CVS/Repository: No > space left on device > > My disk is nowhere near full and a little Googling says that > this is coming from the CVS server not my machine. > > Anyone else having this problem? > Has SourceForge been notified? > > > -- > Dave Smith > http://www.theappman.com > -- > Dave Smith > http://www.theappman.com > > > > --- > SF email is sponsored by - The IT Product Guide Read honest & > candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.937 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050407194648Lbuild.937 BUILD COMPLETE - build.937Date of build: 04/07/2005 19:46:48Time to build: 19 minutes 44 secondsLast changed: 04/07/2005 18:42:00Last log entry: Fix the package names. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (24)1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/simple/HelloWs.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/serverside/ServerSideArtifactsTestCase.javaFix the package names.1.12modifiedejortwebservice/.classpathFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/custom/HelloCustomRemote.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/custom/HelloObj.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/doclit/DocStyleSEI.javaFix the package names.1.2modifiedejortwebservice/test/java/org/jboss/test/ws/tools/jbws_161/doclit/User.javaFix the package names.1.5modifiedejortwebservice/src/main/org/jboss/ws/soap/SOAPPartImpl.javaMake this compile1.9modifiedejortaspects/.classpathFix the eclipse build1.2modifiedejortj2se/src/tests/org/jboss/test/jmx/compliance/server/MBeanServerTEST.javaAvoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar.1.2modifiedejortj2se/src/tests/org/jboss/test/jmx/compliance/loading/MLetTEST.javaAvoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar.1.25modifiedpatriot1burkeejb3/build.xmldocs upgrade1.4modifiedpatriot1burkeejb3/docs/index.htmldocs upgrade1.6modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.htmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/build.xmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/reference/en/master.xmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/reference/en/modules/applicationtx.xmldocs upgrade1.3modifiedpatriot1burkeejb3/docs/reference/reference/en/modules/entity.xmldocs upgrade1.1addedpatriot1burkeejb3/docs/reference/reference/en/modules/entity_configuration.xmldocs upgrade1.1addedstarksmserver/src/resources/dtd/README-DTD.txtAdd readmes on the j2ee dtd/schema file terms1.1addedstarksmserver/src/resources/schema/README-SCHEMA.txtAdd readmes on the j2ee dtd/schema file terms1.4modifiedstarksmwebservice/src/main/org/jboss/ws/soap/SOAPPartImpl.javaFix the wildard import1.1addedstarksmthirdparty/licenses/sun-specs.txtA readme pointing to the spec associated descriptor redistribution terms and the dtd/schema files.1.18modifiedstarksmserver/src/main/org/jboss/ejb/plugins/jms/DLQHandler.javaUse a HashMap instead of a Hashable to copy the properties while making them writable as there can be nulls. Resolves (JBAS-1669) NullPointerException in DLQHandler.
[JBoss-dev] jboss-4.0 build.481 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050407182545Lbuild.481 BUILD COMPLETE - build.481Date of build: 04/07/2005 18:25:45Time to build: 32 minutes 30 secondsLast changed: 04/07/2005 17:37:08Last log entry: This is not source. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.15.4.2modifiedejortserver/.classpathThis is not source.1.5.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactory.javaFix the error message to try to avoid the FAQ1.11.6.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.javaFix the error message to try to avoid the FAQ1.10.6.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.javaFix the error message to try to avoid the FAQ
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-25) bpel activities xml parsing
[ http://jira.jboss.com/jira/browse/JBPM-25?page=history ] Juan Cantu updated JBPM-25: --- Description: Perform xml - to graph translation by representing bpel activities as jbpm nodes. WS-BPEL 2.0 defines the following activities: Basic Activities: -receive, reply, invoke, assign, wait, scope, throw, rethrow, exit, compensate, empty Structured Activities: -sequence, switch, while, pick, flow was: Perform xml - to graph translation by representing bpel activities as jbpm nodes. BPEL 1.1 defines the following activities: Basic Activities: -receive, reply, invoke, assign, wait, scope, throw, terminate, compensate, empty Structured Activities: -sequence, switch, while, pick, flow > bpel activities xml parsing > --- > > Key: JBPM-25 > URL: http://jira.jboss.com/jira/browse/JBPM-25 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > Original Estimate: 2 weeks >Time Spent: 2 weeks, 3 days > > Perform xml - to graph translation by representing bpel activities as jbpm > nodes. WS-BPEL 2.0 defines the following activities: > Basic Activities: > -receive, reply, invoke, assign, wait, scope, throw, rethrow, exit, > compensate, empty > Structured Activities: > -sequence, switch, while, pick, flow -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050407170059 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 04/07/2005 17:00:59Time to build: 27 minutes 12 secondsLast changed: 04/07/2005 16:32:19Last log entry: Avoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (15)1.2modifiedejortj2se/src/tests/org/jboss/test/jmx/compliance/server/MBeanServerTEST.javaAvoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar.1.2modifiedejortj2se/src/tests/org/jboss/test/jmx/compliance/loading/MLetTEST.javaAvoid these tests failing if they are run inside eclipsewhich means the classes aren't loaded from a jar.1.25modifiedpatriot1burkeejb3/build.xmldocs upgrade1.4modifiedpatriot1burkeejb3/docs/index.htmldocs upgrade1.6modifiedpatriot1burkeejb3/docs/tutorial/blob/blob.htmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/build.xmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/reference/en/master.xmldocs upgrade1.2modifiedpatriot1burkeejb3/docs/reference/reference/en/modules/applicationtx.xmldocs upgrade1.3modifiedpatriot1burkeejb3/docs/reference/reference/en/modules/entity.xmldocs upgrade1.1addedpatriot1burkeejb3/docs/reference/reference/en/modules/entity_configuration.xmldocs upgrade1.1addedstarksmserver/src/resources/dtd/README-DTD.txtAdd readmes on the j2ee dtd/schema file terms1.1addedstarksmserver/src/resources/schema/README-SCHEMA.txtAdd readmes on the j2ee dtd/schema file terms1.4modifiedstarksmwebservice/src/main/org/jboss/ws/soap/SOAPPartImpl.javaFix the wildard import1.1addedstarksmthirdparty/licenses/sun-specs.txtA readme pointing to the spec associated descriptor redistribution terms and the dtd/schema files.1.18modifiedstarksmserver/src/main/org/jboss/ejb/plugins/jms/DLQHandler.javaUse a HashMap instead of a Hashable to copy the properties while making them writable as there can be nulls. Resolves (JBAS-1669) NullPointerException in DLQHandler.
[JBoss-dev] [Design of JBoss Portal] - error running jboss with jboss portal beta
and later i have this error : 2005-04-07 16:33:41,055 INFO [org.jboss.system.ServiceConfigurator] Problem configuring service jboss:service=Mail java.lang.IllegalArgumentException: [configuration: null] at java.beans.PropertyEditorSupport.setAsText(PropertyEditorSupport.java:138) at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:313) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:160) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:114) at org.jboss.system.ServiceController.install(ServiceController.java:200) at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:208) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:889) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:745) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709) at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SAR
[JBoss-dev] [JBoss JIRA] Created: (JBPM-110) SuperState get's loaded as Node object: Hibernate mapping bug
SuperState get's loaded as Node object: Hibernate mapping bug - Key: JBPM-110 URL: http://jira.jboss.com/jira/browse/JBPM-110 Project: JBoss jBPM Type: Bug Components: Core Engine Versions: jBPM 3.0 alpha 3 Environment: Run under a Web Service enabled SessionBean in JBoss4.0.1 on JDK1.4.2 and 1.5 on Windows/Intel and Solaris/Sparc. Reporter: chadbo Assigned to: Tom Baeyens The instanceof operation in Transition.java at line 103 fails for processes instances that were loaded from the db because destination gets loaded as a Node instance instead of SuperState. The process does get created in the db correctly, but it does not loead correctly if the creating session is closed and a new session latter loads the process. I believe the Hibernate mappings are incorrect in the hbm files for the jbpm_node table. The subclasses and discriminators are not working. Hypothesis: The subclasses definitions may have to be in Node.hbm.xml instead of their own files (not sure, but that way worked for me on other projects.) This issues results in super state events not being fired if the process is signalled in a seperate session that that which created the process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1664) Unloaded entities returned in low memory conditions
[ http://jira.jboss.com/jira/browse/JBAS-1664?page=history ] Adrian Brock closed JBAS-1664: -- Resolution: Won't Fix You mean OutOfMemoryError. In general such errors leave the JVM in an unknown/unrecoverable state. The main difference between BMP and CMP is that by default BMP uses commit option A with a 1 million bean cache per EJB deployment, which is unlikely to work if you have the default 64M of memory. > Unloaded entities returned in low memory conditions > --- > > Key: JBAS-1664 > URL: http://jira.jboss.com/jira/browse/JBAS-1664 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-3.2.6 Final > Reporter: Arto Huusko > > > In low memory conditions (that is, when OutOfMemoryExceptions are seen > frequently all over the place), JBoss can behave wrong in a way that is > critically wrong. > I have seen on several occasions that a finder returns an entity with the > correct identity, but where ejbLoad() has either not been called at all, or > where ejbLoad() has failed at some point (I have no way of knowing which is > the case). > I have observed this behaviour only with BMP beans (and so there is a > possibility that I am doing something wrong in the BMP code, but I doubt > this). However, the fact that I haven't seen this with CMP beans may be just > because CMP beans work differently, or just plain luck. When this occurs, the > wrong behaviour can be seen because the instance variables of the entity bean > contain what ever they had when the entity instance was previously attached > to some other identity. > For example, I may store the primary key of the entity in some instance > variable. Let's say I can access the primary key via method "Long > getMyPrimaryKey()". If the finder returns an entity with the correct identity > (what I asked for in the finder call), but where ejbLoad() is not called or > it fails, then >entity.getMyPrimaryKey().equals(entity.getPrimaryKey()) > is false. And this is exactly what I have seen. > I have no idea where the problem is, and, as I said above, it may be a > problem with my code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1607) Absence of optional 'transaction-timeout' element throws NumberFormatException
[ http://jira.jboss.com/jira/browse/JBAS-1607?page=history ]
Adrian Brock closed JBAS-1607:
--
Resolution: Duplicate Issue
> Absence of optional 'transaction-timeout' element throws NumberFormatException
> --
>
> Key: JBAS-1607
> URL: http://jira.jboss.com/jira/browse/JBAS-1607
> Project: JBoss Application Server
> Type: Bug
> Versions: JBossAS-4.0.1 Final
> Reporter: Peter Doornbosch
> Priority: Minor
>
>
> When the optional element is not set in the jboss.xml,
> a (debug) message is logged with the text "Ignoring transaction-timeout
> 'null'" - stange message for an optional element that is not there ;-).
> What is even worse is that a stacktrace is printed of the
> NumberFormatException that occurred when trying to parse this null value.
> These stacktraces clutter the server.log, for example in my case these
> stacktraces are responsible for 50% of the size of the (debug) log file.
> This behaviour is caused by the following fragment from BeanMetaData:
> String txTimeout = getOptionalChildContent(maNode,
> "transaction-timeout");
> try
> {
>ma.txTimeout = Integer.parseInt(txTimeout);
> }
> catch (Exception ignore)
> {
>log.debug("Ignoring transaction-timeout '" + txTimeout + "'",
> ignore);
> }
> Of course, this should be: if (txTimeout != null) a.txTimeout =
> Integer.parseInt(txTimeout);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316779 ] Steve Ebersole commented on HIBERNATE-13: - No the real issue happens (or was happening) well before that. The service fails to start, hence nothing is ever put into JNDI and thus never found ;) I'll just (try to) do a clean checkout of 4.0 tonight and look at it myself. I'm not able to simply update because I have a *lot* of pending changes waiting for 4.0.2 to be released. Note, I've not been able to grab a full checkout from CVS using my dev login for almost 4 weeks of trying now; I always end up having to use Clebert's trick of doing an anon checkout and manually updating the local CVS meta files. Ryan, maybe I could just do a anon checkout and do the fix and send you the patch to apply (if I am unable to get a developer checkout)? > testEjbInterception Unit Test failure > - > > Key: HIBERNATE-13 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 > Project: Hibernate > Type: Bug > Environment: win xp sp2 > Reporter: Pushkala Iyer > Assignee: Steve Ebersole > > > The following test is failing in the 4.0 branch and needs to be resolved > before the 4.0.2 Final release. We've tested this in multiple environments > and received the same error. > Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase > Test : testEjbInterception > Stack Trace: > RemoteException occurred in server thread; nested exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested > throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > java.rmi.ServerException: RemoteException occurred in server thread; nested > exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) > at sun.rmi.transport.Transport$1.run(Transport.java:148) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:144) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) > at java.lang.Thread.run(Thread.java:534) > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown > Source) > at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) > at > org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.storeUser(Unknown Source) > at > org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at > org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) > at >
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1608) Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
[ http://jira.jboss.com/jira/browse/JBAS-1608?page=comments#action_12316778 ] Adrian Brock commented on JBAS-1608: I'd guess the problem is caused by inspectMBean.jsp using an element rather than a so you only see the first line of the data. > Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail > MBean > --- > > Key: JBAS-1608 > URL: http://jira.jboss.com/jira/browse/JBAS-1608 > Project: JBoss Application Server > Type: Bug > Components: Management Service > Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, > JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.1RC1, JBossAS-4.0.0 > Final, JBossAS-3.2.5 Final > Environment: Nothing specific > Reporter: Amit Bhayani > Priority: Minor > > > The Configuration (RW) attribute of jboss:service=Mail MBean breaks (doesn't > display the whole property but while setting it works fine) when encounters " > (double inverted comma). > For example set the following in Configuration (RW) attribute > and apply changes. Now on Configuration textbox > you can see http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-128) Session/MDB Jacc integration
[ http://jira.jboss.com/jira/browse/EJBTHREE-128?page=history ] Bill Burke updated EJBTHREE-128: Fix Version: EJB 3.0 Beta 1 (was: Preview 6) > Session/MDB Jacc integration > > > Key: EJBTHREE-128 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-128 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Assignee: William DeCoste > Fix For: EJB 3.0 Beta 1 > > > Aspectize JACC integration for both Session/MDB layer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1662) Memory leak with SpecCompliant=true in transaction-service.xml
[ http://jira.jboss.com/jira/browse/JBAS-1662?page=comments#action_12316777 ] Adrian Brock commented on JBAS-1662: SpecCompliant=true is a misnomer. It has nothing to do with spec compliance. In fact JBoss passed the j2ee1.4 compliance suite with this flag set to false. It is actually a backwards compatibility flag for an earlier implementation of the connection pooling in JBoss-3.0.0 I wouldn't recommend using it since you lose your connection close checking (which is probably the real cause of your memory leak). It is also not tested by the testsuite. Personally, I would like to implement the behaviour provided by this flag (lazy connection pooling - handle/managedconnection association). But it requires fixing the CCM to better link with the EJB lifecycle. See the attached issue. > Memory leak with SpecCompliant=true in transaction-service.xml > -- > > Key: JBAS-1662 > URL: http://jira.jboss.com/jira/browse/JBAS-1662 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, > JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Environment: jboss 3.2.6, linux 2.[46], DB2 7.[12] > Reporter: Arto Huusko > > > If SpecCompliant is set to true in transaction-service.xml, jboss begins to > leak > memory on a massive scale: all entity beans (both CMP and BMP) that become > unused > (that is: they are flushed from cache, and instance pool is full, so they are > discarded) are never garbage collected. > I don't pretend to understand the problem fully (I was in quite a rush to > solve > the memory leaks and it still took me over a week). I investigated the matter > with a home-grown memory profiler, and found out that the leak ultimately > occurs > in org.jboss.resource.connectionmanager.CachedConnectionManager, which never > releases the KeyConnectionAssociation objects (that are stored in a > ThreadLocal > LinkedList). > And since KeyConnectionAssociation also holds a reference to the entity > object, > the entity objects leak once they are thrown out of the pool. > And those KeyConnectionAssociation objects are of course created as a result > of the entity beans opening connection to the database. > I never found out why the KeyConnectionAssociation objects were never removed > from the list (which would have resulted in garbage collection of the entity > and all). I just saw somewhere in the code promising references to > SpecCompliant, and thankfully it solved the problem for me. > Note that leakage also occurs (immediately) if JBoss gets an entity from > instance > pool to run a finder, and the finder throws an exception. In that case, the > entity used to run the finder is leaked immediately (the leakage happens in > the > same way as outlined above). > I marked this problem for 3.2.6, but as far as I can see, the problem is the > same in 3.2.7 and 4, too. Maybe priority should really be "minor", since I'm > not sure that many people use SpecCompliant. > Oh, and I also have Debug=true in transaction-service, if that makes any > difference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-130) Update Injection Annotations from J2EE 5.0 EDR
Update Injection Annotations from J2EE 5.0 EDR -- Key: EJBTHREE-130 URL: http://jira.jboss.com/jira/browse/EJBTHREE-130 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assigned to: William DeCoste Fix For: Preview 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-129) Mirror relevant Session/MDB tutorials for XML mappings
Mirror relevant Session/MDB tutorials for XML mappings -- Key: EJBTHREE-129 URL: http://jira.jboss.com/jira/browse/EJBTHREE-129 Project: EJB 3.0 Type: Task Reporter: Bill Burke Assigned to: William DeCoste Fix For: Preview 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1662) Memory leak with SpecCompliant=true in transaction-service.xml
[ http://jira.jboss.com/jira/browse/JBAS-1662?page=history ] Adrian Brock updated JBAS-1662: --- Version: JBossAS-4.0.2RC1 JBossAS-4.0.1 SP1 JBossAS-4.0.1 Final JBossAS-3.2.7 Final Component: JCA service (was: Transaction Manager service) > Memory leak with SpecCompliant=true in transaction-service.xml > -- > > Key: JBAS-1662 > URL: http://jira.jboss.com/jira/browse/JBAS-1662 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, > JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Environment: jboss 3.2.6, linux 2.[46], DB2 7.[12] > Reporter: Arto Huusko > > > If SpecCompliant is set to true in transaction-service.xml, jboss begins to > leak > memory on a massive scale: all entity beans (both CMP and BMP) that become > unused > (that is: they are flushed from cache, and instance pool is full, so they are > discarded) are never garbage collected. > I don't pretend to understand the problem fully (I was in quite a rush to > solve > the memory leaks and it still took me over a week). I investigated the matter > with a home-grown memory profiler, and found out that the leak ultimately > occurs > in org.jboss.resource.connectionmanager.CachedConnectionManager, which never > releases the KeyConnectionAssociation objects (that are stored in a > ThreadLocal > LinkedList). > And since KeyConnectionAssociation also holds a reference to the entity > object, > the entity objects leak once they are thrown out of the pool. > And those KeyConnectionAssociation objects are of course created as a result > of the entity beans opening connection to the database. > I never found out why the KeyConnectionAssociation objects were never removed > from the list (which would have resulted in garbage collection of the entity > and all). I just saw somewhere in the code promising references to > SpecCompliant, and thankfully it solved the problem for me. > Note that leakage also occurs (immediately) if JBoss gets an entity from > instance > pool to run a finder, and the finder throws an exception. In that case, the > entity used to run the finder is leaked immediately (the leakage happens in > the > same way as outlined above). > I marked this problem for 3.2.6, but as far as I can see, the problem is the > same in 3.2.7 and 4, too. Maybe priority should really be "minor", since I'm > not sure that many people use SpecCompliant. > Oh, and I also have Debug=true in transaction-service, if that makes any > difference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-26) Web services support
[ http://jira.jboss.com/jira/browse/EJBTHREE-26?page=history ] Bill Burke reassigned EJBTHREE-26: -- Assign To: William DeCoste (was: Bill Burke) > Web services support > > > Key: EJBTHREE-26 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-26 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 5 > Reporter: Bill Burke > Assignee: William DeCoste > Fix For: EJB 3.0 Beta 1 > > > J2EE 1.5 will define this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-128) Session/MDB Jacc integration
Session/MDB Jacc integration Key: EJBTHREE-128 URL: http://jira.jboss.com/jira/browse/EJBTHREE-128 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Assigned to: William DeCoste Fix For: Preview 6 Aspectize JACC integration for both Session/MDB layer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-85) Test Entity JACC integration
[ http://jira.jboss.com/jira/browse/EJBTHREE-85?page=history ] Bill Burke reassigned EJBTHREE-85: -- Assign To: William DeCoste > Test Entity JACC integration > > > Key: EJBTHREE-85 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-85 > Project: EJB 3.0 > Type: Task > Versions: Preview 5 > Reporter: Bill Burke > Assignee: William DeCoste > Fix For: EJB 3.0 Beta 1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-72) MDB should support JCA inflow
[ http://jira.jboss.com/jira/browse/EJBTHREE-72?page=history ] Bill Burke reassigned EJBTHREE-72: -- Assign To: William DeCoste (was: Bill Burke) > MDB should support JCA inflow > - > > Key: EJBTHREE-72 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-72 > Project: EJB 3.0 > Type: Feature Request > Reporter: Bill Burke > Assignee: William DeCoste > Fix For: EJB 3.0 Beta 1 > > > MDB should support JCA inflow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (EJBTHREE-21) MDB, Session Bean XML support
[ http://jira.jboss.com/jira/browse/EJBTHREE-21?page=history ] Bill Burke reassigned EJBTHREE-21: -- Assign To: William DeCoste (was: Bill Burke) > MDB, Session Bean XML support > - > > Key: EJBTHREE-21 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-21 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 5 > Reporter: Bill Burke > Assignee: William DeCoste > Fix For: Preview 6 > > Original Estimate: 1 week > Remaining: 1 week > > Support EJB 3 spec mandated XML deployment descriptors. This has yet to be > defined in the EJB 3 specification though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-126) Create Docbook for Session/MDBs
Create Docbook for Session/MDBs --- Key: EJBTHREE-126 URL: http://jira.jboss.com/jira/browse/EJBTHREE-126 Project: EJB 3.0 Type: Task Reporter: Bill Burke Fix For: Preview 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-127) Create Docbook for @Consumer
Create Docbook for @Consumer Key: EJBTHREE-127 URL: http://jira.jboss.com/jira/browse/EJBTHREE-127 Project: EJB 3.0 Type: Task Reporter: Bill Burke Assigned to: Bill Burke Fix For: Preview 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-125) Create docbook for @Service and Asynch features
Create docbook for @Service and Asynch features --- Key: EJBTHREE-125 URL: http://jira.jboss.com/jira/browse/EJBTHREE-125 Project: EJB 3.0 Type: Task Reporter: Bill Burke Assigned to: Kabir Khan Fix For: Preview 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-124) @LongLived should follow new Spec defined rules
@LongLived should follow new Spec defined rules --- Key: EJBTHREE-124 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 Project: EJB 3.0 Type: Feature Request Versions: Preview 5 Reporter: Bill Burke Fix For: Preview 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316776 ] Ryan Campbell commented on HIBERNATE-13: I'm still seeing this after applying Steve's fix from yesterday. The root exception is: Caused by: javax.naming.NameNotFoundException: hibernate not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:491) at org.jnp.server.NamingServer.getBinding(NamingServer.java:499) at org.jnp.server.NamingServer.getObject(NamingServer.java:505) at org.jnp.server.NamingServer.lookup(NamingServer.java:249) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.hibernate.session.HibernateContext.locateSessionFactory(HibernateContext.java:241) Looking at hibernate/src/etc/hibernate-service.xml it looks as though the session factory name may have changed from java:/hibernate/SessionFactory to java:/hibernate/HibernateFactory? Of course, the error is with hibernate not being bound, but I'm just wondering if the test is broken due to a config change w/ hibernate? > testEjbInterception Unit Test failure > - > > Key: HIBERNATE-13 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 > Project: Hibernate > Type: Bug > Environment: win xp sp2 > Reporter: Pushkala Iyer > Assignee: Steve Ebersole > > > The following test is failing in the 4.0 branch and needs to be resolved > before the 4.0.2 Final release. We've tested this in multiple environments > and received the same error. > Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase > Test : testEjbInterception > Stack Trace: > RemoteException occurred in server thread; nested exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested > throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > java.rmi.ServerException: RemoteException occurred in server thread; nested > exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) > at sun.rmi.transport.Transport$1.run(Transport.java:148) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:144) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) > at java.lang.Thread.run(Thread.java:534) > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown > Source) > at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) > at > org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.storeUser(Unknown Source) > at > org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Una
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ] Ryan Campbell reassigned HIBERNATE-13: -- Assign To: Steve Ebersole (was: Gavin King) > testEjbInterception Unit Test failure > - > > Key: HIBERNATE-13 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 > Project: Hibernate > Type: Bug > Environment: win xp sp2 > Reporter: Pushkala Iyer > Assignee: Steve Ebersole > > > The following test is failing in the 4.0 branch and needs to be resolved > before the 4.0.2 Final release. We've tested this in multiple environments > and received the same error. > Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase > Test : testEjbInterception > Stack Trace: > RemoteException occurred in server thread; nested exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested > throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > java.rmi.ServerException: RemoteException occurred in server thread; nested > exception is: > java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) > at sun.rmi.transport.Transport$1.run(Transport.java:148) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:144) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) > at java.lang.Thread.run(Thread.java:534) > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown > Source) > at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) > at > org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.storeUser(Unknown Source) > at > org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > Caused by: java.rmi.ServerException: RuntimeException; nested exception is: > org.jboss.util.NestedRuntimeException: Unable to retreive Session; - > nested throwable: (net.sf.hibernate.HibernateException: Unable to locate > SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) > at > org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) > at > org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) > at org.jboss.ejb.Container.invoke(Container.java:873) > at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBean
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: EJB TimerService in a clustered environment
Yes the second one sounds like the best way, and had started to work in that direction. But tell me, how do you get the startup notification from JBOSS? This is the part I'm totally lost. And thanks for the response by the way. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873112#3873112 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873112 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.480 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050407132926Lbuild.480 BUILD COMPLETE - build.480Date of build: 04/07/2005 13:29:26Time to build: 43 minutes 4 secondsLast changed: 04/07/2005 09:50:09Last log entry: Use a HashMap instead of a Hashable to copy the properties while making them writable as there can be nulls. Resolves (JBAS-1669) NullPointerException in DLQHandler. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.17.6.2modifiedstarksmserver/src/main/org/jboss/ejb/plugins/jms/DLQHandler.javaUse a HashMap instead of a Hashable to copy the properties while making them writable as there can be nulls. Resolves (JBAS-1669) NullPointerException in DLQHandler.
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Got a lot of exceptions when i tried my own
Have the simplest example, a stateless bean TestBean:
| public class TestBean implements SessionBean {
| public void ejbCreate() throws CreateException {
| }
|
| public void setSessionContext(SessionContext sessionContext) throws
EJBException {
| }
|
| public void ejbRemove() throws EJBException {
| }
|
| public void ejbActivate() throws EJBException {
| }
|
| public void ejbPassivate() throws EJBException {
| }
|
| public void sayHello()
| {
| System.err.println("Hello AOP world");
| }
| }
|
All this gets packet into TestEjb.jar which explored looks like this
META-INF which contains only EJB related descriptors but no jboss-aop.xml
com/balamaci/proiect
-TestHome.class
-TestBean.class
-RemoteTest.class
-SimpleInterceptor.class
The SimpleInterceptor class contains:
| public class SimpleInterceptor {
|public String getName() {
|return "SimpleInterceptor";
|}
|
|public Object invoke(Invocation invocation) throws Throwable
|{
| try
| {
| System.err.println("<<< Entering SimpleInterceptor");
| System.out.println("<<< Entering SimpleInterceptor");
| return invocation.invokeNext();
| }
| finally
| {
| System.err.println(">>> Leaving SimpleInterceptor");
| }
|}
| }
|
got the client that just does
| try
|{
| Properties env = new Properties();
| env.setProperty(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
| env.setProperty(Context.PROVIDER_URL, "localhost:1099");
| env.setProperty("java.naming.factory.url.pkgs",
"org.jboss.naming:org.jnp.interfaces");
| Object obj = ctx.lookup("TestEJB");
| TestHome home = (TestHome)
javax.rmi.PortableRemoteObject.narrow(obj,TestHome.class);
| RemoteTest test=home.create();
| test.sayHello();
| }
| catch(Exception e)
| {
| e.printStackTrace();
| }
|
|
After starting a default instance of jboss i copy the jboss-aop.xml in the
deploy directory. The jboss-aop.xml looks like this
|
|
|
|
|
|
|
After that i copy the TestEjb.jar in the deploy directory and after it says
it's been deployed, i run the client.
The ugly part is that instead of printing something nice it gets all of this:
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is:
java.rmi.ServerError: Unexpected Error; nested exception is:
java.lang.ExceptionInInitializerError
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:325)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:163)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:103)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:91)
at $Proxy1.sayHello(Unknown Source)
at com.balamaci.ejb.client.main(client.java:56)
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:585)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)
Caused by: java.rmi.ServerError: Unexpected Error; nested exception is:
java.lang.ExceptionInInitializerError
at
org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:399)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:19
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: classloader question
User question -> User forums View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873110#3873110 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873110 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JTA and JTS on JBoss] - Re: Integration JOTM with JBoss
Which part of "DO NOT POST USER QUESTIONS HERE" didn't you understand? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873109#3873109 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873109 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: New Build - Standalone module - multiple builds
"[EMAIL PROTECTED]" wrote : For the export functionality, we want to keep the
syntax as simple as possible.
|
| This would cause the parsing as above, but would use the designated
reference id instead of the component's exports. So the export statement is
the default, but you retain the ability to reference an abitrary input.
|
The includes or export is just a convenience such that each consuming project
does not need to be changed when the exported artifact definition changes.
The consuming project still has the option to be more explicit about what it
actually uses, but then that would point to a project that probably needs
splitting up
anonymous wrote :
| To do this, I will need to add a component-info.xml for thirdparty/* in
cvs. I assme there is no problem with this? We'll need these eventually,
anyway. Basically, it will involve copying the existing thirdparty component
declarations from jbossas/jbossbuild.xml into the component-info.xml and
changing the {includes} to {export}.
|
Yes, that is exactly what I want. Each component (whether it is one our projects
or a true thirdparty project) should define its own artifacts
rather than the top level build. Doing it on the top level build stops
the project being included in multiple integration projects because it has
references back to a specific top level build.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873107#3873107
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873107
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: New Build - Standalone module - multiple builds
"[EMAIL PROTECTED]" wrote : For the export functionality, we want to keep the
syntax as simple as possible.
| (snip)
| This would cause the parsing as above, but would use the designated
reference id instead of the component's exports. So the export statement is
the default, but you retain the ability to reference an abitrary input.
|
The includes or export is just a convenience such that each consuming project
does not need to be changed when the exported artifact definition changes.
The consuming project still has the option to be more explicit about what it
actually uses, but then that would point to a project that probably needs
splitting up
anonymous wrote :
| To do this, I will need to add a component-info.xml for thirdparty/* in
cvs. I assme there is no problem with this? We'll need these eventually,
anyway. Basically, it will involve copying the existing thirdparty component
declarations from jbossas/jbossbuild.xml into the component-info.xml and
changing the {includes} to {export}.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873106#3873106
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873106
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: New Build - Standalone module - multiple builds
"[EMAIL PROTECTED]" wrote : "[EMAIL PROTECTED]" wrote : For the export
functionality, we want to keep the syntax as simple as possible.
| |
| | This would cause the parsing as above, but would use the designated
reference id instead of the component's exports. So the export statement is
the default, but you retain the ability to reference an abitrary input.
| |
|
| The includes or export is just a convenience such that each consuming
project
| does not need to be changed when the exported artifact definition changes.
|
| The consuming project still has the option to be more explicit about what it
| actually uses, but then that would point to a project that probably needs
| splitting up
|
| anonymous wrote :
| | To do this, I will need to add a component-info.xml for thirdparty/* in
cvs. I assme there is no problem with this? We'll need these eventually,
anyway. Basically, it will involve copying the existing thirdparty component
declarations from jbossas/jbossbuild.xml into the component-info.xml and
changing the {includes} to {export}.
|
Yes, that is exactly what I want. Each component (whether it is one our projects
or a true thirdparty project) should define its own artifacts
rather than the top level build. Doing it on the top level build stops
the project being included in multiple integration projects because it has
references back to a specific top level build.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873105#3873105
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873105
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Build System] - Re: New Build - Standalone module - multiple builds
"[EMAIL PROTECTED]" wrote : For the export functionality, we want to keep the
syntax as simple as possible.
|
| This would cause the parsing as above, but would use the designated
reference id instead of the component's exports. So the export statement is
the default, but you retain the ability to reference an abitrary input.
| [/qoute]
|
| The includes or export is just a convenience such that each consuming
project
| does not need to be changed when the exported artifact definition changes.
|
| The consuming project still has the option to be more explicit about what it
| actually uses, but then that would point to a project that probably needs
| splitting up
|
| anonymous wrote :
| | To do this, I will need to add a component-info.xml for thirdparty/* in
cvs. I assme there is no problem with this? We'll need these eventually,
anyway. Basically, it will involve copying the existing thirdparty component
declarations from jbossas/jbossbuild.xml into the component-info.xml and
changing the {includes} to {export}.
|
Yes, that is exactly what I want. Each component (whether it is one our projects
or a true thirdparty project) should define its own artifacts
rather than the top level build. Doing it on the top level build stops
the project being included in multiple integration projects because it has
references back to a specific top level build.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873104#3873104
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873104
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-61) Split out jbossxb into a separate project/binary
[ http://jira.jboss.com/jira/browse/JBBUILD-61?page=history ] Adrian Brock updated JBBUILD-61: Description: Make JBossXB into a separate project that can be consumed indepently by standalone projects. was: Make org.jboss.net into a separate project that can be consumed indepently by standalone projects. > Split out jbossxb into a separate project/binary > > > Key: JBBUILD-61 > URL: http://jira.jboss.com/jira/browse/JBBUILD-61 > Project: JBoss Build System > Type: Sub-task > Reporter: Adrian Brock > Assignee: Ryan Campbell > Priority: Minor > Fix For: milestone-3 > > > Make JBossXB into a separate project > that can be consumed indepently by standalone projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Struts on Portal Server made possible
Timothy, Great work. Can you also send me the patch with instructions? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873103#3873103 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873103 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-61) Split out jbossxb into a separate project/binary
Split out jbossxb into a separate project/binary Key: JBBUILD-61 URL: http://jira.jboss.com/jira/browse/JBBUILD-61 Project: JBoss Build System Type: Sub-task Reporter: Adrian Brock Assigned to: Ryan Campbell Priority: Minor Fix For: milestone-3 Make org.jboss.net into a separate project that can be consumed indepently by standalone projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-60) Split out org.jboss.net into a separate project/binary
[ http://jira.jboss.com/jira/browse/JBBUILD-60?page=history ] Adrian Brock updated JBBUILD-60: Description: Make org.jboss.net into a separate project that can be consumed indepently by standalone projects. was: Make org.jboss.logging into a separate project that can be consumed indepently by standalone projects. > Split out org.jboss.net into a separate project/binary > -- > > Key: JBBUILD-60 > URL: http://jira.jboss.com/jira/browse/JBBUILD-60 > Project: JBoss Build System > Type: Sub-task > Reporter: Adrian Brock > Assignee: Ryan Campbell > Priority: Minor > Fix For: milestone-3 > > > Make org.jboss.net into a separate project > that can be consumed indepently by standalone projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-59) Split out org.jboss.logging into a separate project/binary
Split out org.jboss.logging into a separate project/binary -- Key: JBBUILD-59 URL: http://jira.jboss.com/jira/browse/JBBUILD-59 Project: JBoss Build System Type: Sub-task Reporter: Adrian Brock Assigned to: Ryan Campbell Priority: Minor Fix For: milestone-3 Make org.jboss.logging into a separate project that can be consumed indepently by standalone projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-60) Split out org.jboss.net into a separate project/binary
Split out org.jboss.net into a separate project/binary -- Key: JBBUILD-60 URL: http://jira.jboss.com/jira/browse/JBBUILD-60 Project: JBoss Build System Type: Sub-task Reporter: Adrian Brock Assigned to: Ryan Campbell Priority: Minor Fix For: milestone-3 Make org.jboss.logging into a separate project that can be consumed indepently by standalone projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Redeploying portlet WAR
try to put portlet-api.jar in the lib directory of jboss and tell me View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873100#3873100 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873100 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Redeploying portlet WAR
When I redeploy a WAR with a protlet specification the follow exception occur. But if I restart JBOSS it functions well. What can be problem? java.lang.NullPointerException at org.jboss.portal.server.invocation.component.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:58) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.AccessControlInterceptor.invoke(AccessControlInterceptor.java:125) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.ModeInterceptor.invoke(ModeInterceptor.java:37) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.ConstrainedWindowStateInterceptor.invoke(ConstrainedWindowStateInterceptor.java:51) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.ParametersInterceptor.invoke(ParametersInterceptor.java:70) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.invocation.component.CacheInterceptor.invoke(CacheInterceptor.java:74) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:242) at org.jboss.portal.server.Component.invoke(Component.java:127) at org.jboss.portal.server.invocation.portal.MainDispatcherInterceptor.invoke(MainDispatcherInterceptor.java:164) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:117) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.ViewInterceptor.invoke(ViewInterceptor.java:58) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.core.invocation.UserContextInterceptor.invoke(UserContextInterceptor.java:121) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:217) at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:242) at org.jboss.portal.server.PortalServer.invoke(PortalServer.java:195) at org.jboss.portal.server.servlet.AbstractMainServlet.invoke(AbstractMainServlet.java:62) at org.jboss.portal.server.servlet.AbstractMainServlet.doGet(AbstractMainServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.jboss.portal.core.servlet.Roda.run(TransactionFilter.java:96) at org.jboss.portal.common.transaction.Transactions.requiresNew(Transactions.java:75) at org.jboss.portal.core.servlet.TransactionFilter.doFilter(TransactionFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153) at org.apache.catalina.core.StandardValveContext.invokeNext(
[JBoss-dev] [Design of JBoss Portal] - Re: CMSPortlet
the best option is not to rewrite those portlet but rather write an abstraction over CMS services that is used by those portlets. There is already a CMS service and there is already the abstraction of CMS items (directories and files) in the cms module. This is a good starting point to go. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873097#3873097 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873097 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1637) Add the j2ee dtd/schema redistribution terms to the release
[ http://jira.jboss.com/jira/browse/JBAS-1637?page=history ] Scott M Stark closed JBAS-1637: --- Resolution: Done Fix Version: JBossAS-5.0 Alpha The dist contains docs/dtd/README-DTD.txt docs/schema/README-SCHEMA.txt docs/licenses/sun-specs.txt which describe the j2ee descriptors along with their redistribution terms. > Add the j2ee dtd/schema redistribution terms to the release > --- > > Key: JBAS-1637 > URL: http://jira.jboss.com/jira/browse/JBAS-1637 > Project: JBoss Application Server > Type: Task > Components: Build System, Documentation > Reporter: Scott M Stark > Assignee: Scott M Stark > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > We need to add the j2ee dtd and schema redistribution terms as there has been > some question over this. This applies to the j2ee dtds/schemas list here: > http://java.sun.com/xml/ns/j2ee/#usage -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050407110736 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 04/07/2005 11:07:36Time to build: 35 minutes 41 secondsLast changed: 04/07/2005 10:56:27Last log entry: A readme pointing to the spec associated descriptor redistribution terms and the dtd/schema files. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.1addedstarksmthirdparty/licenses/sun-specs.txtA readme pointing to the spec associated descriptor redistribution terms and the dtd/schema files.1.18modifiedstarksmserver/src/main/org/jboss/ejb/plugins/jms/DLQHandler.javaUse a HashMap instead of a Hashable to copy the properties while making them writable as there can be nulls. Resolves (JBAS-1669) NullPointerException in DLQHandler.
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-19) MERGE2 slows down traffic
[ http://jira.jboss.com/jira/browse/JGRP-19?page=history ] Bela Ban resolved JGRP-19: -- Resolution: Done Presence of MERGE2 doesn't make a diff in CVS head anymore > MERGE2 slows down traffic > - > > Key: JGRP-19 > URL: http://jira.jboss.com/jira/browse/JGRP-19 > Project: JGroups > Type: Bug > Environment: JGroups 2.2.8 (CVS Jan 6 2005) > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 2.2.8 > Attachments: Tester.java > > Original Estimate: 2 days > Remaining: 2 days > > Look into why max and avg values for a stack with MERGE2 are slower than for > a stack without MERGE2 > > > num_initial_members="3"/> > > > > > down_thread="false" max_bytes="0" up_thread="false"/> > join_retry_timeout="2000" shun="true"/> > > > Before your Fix: Version 2.2.8 > > Average receiving time(in milliseconds): 1106 > Max reciving time(in milliseconds: 3266 > Min reciving time(in milliseconds: 0 > > > After your Fix: Latest from Head > > Average receiving time(in milliseconds): 342 > Max reciving time(in milliseconds: 1250 > Min reciving time(in milliseconds: 0 > > > > > > num_initial_members="3"/> > > > > down_thread="false" max_bytes="0" up_thread="false"/> > join_retry_timeout="2000" shun="true"/> > > > > > Before your Fix: Version 2.2.8 > > Average receiving time(in milliseconds): 36 > Max reciving time(in milliseconds: 219 > Min reciving time(in milliseconds: 0 > > > After your Fix: Latest from Head > Average receiving time(in milliseconds): 29 > Max reciving time(in milliseconds: 109 > Min reciving time(in milliseconds: 0 > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1442) JNDI Lookup from server to remote server returns the local server binding
[ http://jira.jboss.com/jira/browse/JBAS-1442?page=history ] Scott M Stark closed JBAS-1442: --- Resolution: Done Just renamed issued to make it clearer. > JNDI Lookup from server to remote server returns the local server binding > - > > Key: JBAS-1442 > URL: http://jira.jboss.com/jira/browse/JBAS-1442 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final > Reporter: Adrian Brock > Assignee: Scott M Stark > Fix For: JBossAS-4.0.2RC1 > > > JBAS-57 was not fully backwards compatible. > The change to allow the clustered colocation policy to be overridden > http://jira.jboss.com/jira/browse/JBAS-57 > is not fully backwards compatbile with previous releases. > i.e. When the invoker interceptor is used for a non clustered proxy where > one server looks up a service from another server. > If both servers have the service installed it will use the colocated path > when the intention is to use the remote service. > e.g. Server1 looks up the RMIAdaptor for Server2 > Because Server1 also has an RMIAdaptor it will use the colocated RMIAdaptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1442) JNDI Lookup from server to remote server returns the local server binding
[ http://jira.jboss.com/jira/browse/JBAS-1442?page=history ] Scott M Stark updated JBAS-1442: Summary: JNDI Lookup from server to remote server returns the local server binding (was: JBAS-57 was not fully backwards compatible) Description: JBAS-57 was not fully backwards compatible. The change to allow the clustered colocation policy to be overridden http://jira.jboss.com/jira/browse/JBAS-57 is not fully backwards compatbile with previous releases. i.e. When the invoker interceptor is used for a non clustered proxy where one server looks up a service from another server. If both servers have the service installed it will use the colocated path when the intention is to use the remote service. e.g. Server1 looks up the RMIAdaptor for Server2 Because Server1 also has an RMIAdaptor it will use the colocated RMIAdaptor. was: The change to allow the clustered colocation policy to be overridden http://jira.jboss.com/jira/browse/JBAS-57 is not fully backwards compatbile with previous releases. i.e. When the invoker interceptor is used for a non clustered proxy where one server looks up a service from another server. If both servers have the service installed it will use the colocated path when the intention is to use the remote service. e.g. Server1 looks up the RMIAdaptor for Server2 Because Server1 also has an RMIAdaptor it will use the colocated RMIAdaptor. > JNDI Lookup from server to remote server returns the local server binding > - > > Key: JBAS-1442 > URL: http://jira.jboss.com/jira/browse/JBAS-1442 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final > Reporter: Adrian Brock > Assignee: Scott M Stark > Fix For: JBossAS-4.0.2RC1 > > > JBAS-57 was not fully backwards compatible. > The change to allow the clustered colocation policy to be overridden > http://jira.jboss.com/jira/browse/JBAS-57 > is not fully backwards compatbile with previous releases. > i.e. When the invoker interceptor is used for a non clustered proxy where > one server looks up a service from another server. > If both servers have the service installed it will use the colocated path > when the intention is to use the remote service. > e.g. Server1 looks up the RMIAdaptor for Server2 > Because Server1 also has an RMIAdaptor it will use the colocated RMIAdaptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1442) JBAS-57 was not fully backwards compatible
[ http://jira.jboss.com/jira/browse/JBAS-1442?page=history ] Scott M Stark reopened JBAS-1442: - Assign To: Scott M Stark (was: Adrian Brock) > JBAS-57 was not fully backwards compatible > -- > > Key: JBAS-1442 > URL: http://jira.jboss.com/jira/browse/JBAS-1442 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final > Reporter: Adrian Brock > Assignee: Scott M Stark > Fix For: JBossAS-4.0.2RC1 > > > The change to allow the clustered colocation policy to be overridden > http://jira.jboss.com/jira/browse/JBAS-57 > is not fully backwards compatbile with previous releases. > i.e. When the invoker interceptor is used for a non clustered proxy where > one server looks up a service from another server. > If both servers have the service installed it will use the colocated path > when the intention is to use the remote service. > e.g. Server1 looks up the RMIAdaptor for Server2 > Because Server1 also has an RMIAdaptor it will use the colocated RMIAdaptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - error running jboss with jboss portal beta
hello: i have fedora core1, j2sdk-1_4_2_07-linux, jboss-4.0.0 and Mysql -3.23.58-4. i installed jboss portal beta from the binaries, when i start up jboss the portal i get this error: 10:46:20,116 INFO [ServiceConfigurator] Problem configuring service jboss.jmx:name=Invoker,protocol=jrmp,service=proxyFactory,type=adaptor java.lang.IllegalArgumentException: [interceptors: null] at java.beans.PropertyEditorSupport.setAsText(PropertyEditorSupport.java:138) at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:313) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:160) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:114) at org.jboss.system.ServiceController.install(ServiceController.java:200) at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:208) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:889) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:745) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709) at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.inv
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
[ http://jira.jboss.com/jira/browse/JGRP-33?page=history ] Bela Ban updated JGRP-33: - Priority: Major (was: Critical) downgraded to major; probably due to incorrect use of JGroups > JGroups throws OutOfMemoryError after running for a few hours > - > > Key: JGRP-33 > URL: http://jira.jboss.com/jira/browse/JGRP-33 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN JDK 1.4.2_05 & SUN JDK 1.5.0 on Windows & Unix platforms > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > Attachments: JGroupsMemTest.java, PublishThread2.java, > fc-fast-udp-tcpping.xml, fc-fast-udp.xml, runj10.sh > > > I ran 10 instances of a simple program with 3 threads. The max memory is kept > as the JVM default (64M). The 10 programs join the same JGroup and the > threads in the programs keep publishing a small hashmap at 5 second intervals. > The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) > slowly increases over a period of 4-5 hours and reaches the default max limit > (64M) when it starts throwing OutOfMemory errors on all instances. > I have run the program on unix and windows machines with 1G RAM. > Not able to make much from an HProf output of one of the instances. > This seems to be the cause for the JBossCache bug > "http://jira.jboss.com/jira/browse/JBCACHE-31"; too. > I have tried out a UDP/PING and a UDP/TCPPING combination and this problem > occurs in both cases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-28) Remove sendDummyPacket() in UDP
[ http://jira.jboss.com/jira/browse/JGRP-28?page=history ] Bela Ban resolved JGRP-28: -- Resolution: Done Removed sendDummyPacket() > Remove sendDummyPacket() in UDP > --- > > Key: JGRP-28 > URL: http://jira.jboss.com/jira/browse/JGRP-28 > Project: JGroups > Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 2.2.8 > > Original Estimate: 2 hours > Remaining: 2 hours > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-28) Remove sendDummyPacket() in UDP
[ http://jira.jboss.com/jira/browse/JGRP-28?page=comments#action_12316770 ] Bela Ban commented on JGRP-28: -- Was caused by sendDummyPacket() in UDP - will remove it shortly > Remove sendDummyPacket() in UDP > --- > > Key: JGRP-28 > URL: http://jira.jboss.com/jira/browse/JGRP-28 > Project: JGroups > Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 2.2.8 > > Original Estimate: 2 hours > Remaining: 2 hours > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: admin link
I'm working on a bundled version and hope to have it out this coming Monday. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873092#3873092 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873092 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Admin Login not found
1. First go to the main page: http://localhost:8080/portal/ 2. Click "Standard Login". Login with admin/admin. 3. Then click "admin" on the "Page Menu" on the right. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873091#3873091 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873091 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: admin link
My Configuration: JBoss AS 4.0.1 JBOSS Portal 2.0 Beta 1 MySQL 4.0.24 JDBC 3.1.6 (mysql) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873088#3873088 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873088 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: JBPTL-17: Theme API food for thought
I may be missing something, but all I see is a flat html page in the zengarden app. I see the portlets defined in -pages.xml, -instances.xml, and portlet.xml, but nothing seems to show aside from the main window. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873087#3873087 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873087 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-22) Enhance the ENCRYPT or the ENCRYPT1_4 protocol
[ http://jira.jboss.com/jira/browse/JGRP-22?page=history ] Bela Ban resolved JGRP-22: -- Resolution: Done Fix Version: 2.2.8 (was: 2.2.9) > Enhance the ENCRYPT or the ENCRYPT1_4 protocol > --- > > Key: JGRP-22 > URL: http://jira.jboss.com/jira/browse/JGRP-22 > Project: JGroups > Type: Feature Request > Versions: 2.2.8 > Reporter: Roland R?z > Assignee: Bela Ban > Fix For: 2.2.8 > > > The ENCRYPT and the ENCRYPT1_4 protocol have both some weaknesses and missing > features. There is no strong protection against replay attacks, everybody can > join when using an asymmetric algorithm and messages encrypted with a wrong > key are not discarded. > The difference between the ENCRYPT1_4 and the ENCRYPT protocol is that > ENCRYPT1_4 provides no support for a configured symmetric key (ENCRYPT1_4 > generates and distributes a symmetric key). ENCRYPT provides a feature for a > symmetric key configured in a keystore. In this case the asymmetric key > generation is not used. The symmetric and asymmetric features cannot be > combined. > The asymmetric and symmetric part of the ENCRYPT protocol could be separated > in two protocols and some features could be enhanced. > The ultimate solution could look like that: > The lowest (e.g. CRYPTO_SYM) would be responsible for encryption/decryption > and could be used in any layer below the symmetric cryptography (e.g. > CRYPTO_KEY_DIST) protocol. The key for CRYPTO_SYM comes either from a file > (e.g. as keystore or just as binary stuff protected with file system rights) > or from a file AND from CRYPTO_SYM. In the second mode (CRYPTO_SYM + > CRYPTO_KEY_DIST) CRYPTO_SYM needs to encrypt/decrypt the messages from > CRYPTO_KEY_DIST with the simple file or keystore based key or does not need > to be encrypted (to solve bootstrap, synchronization). The type of the > message (is from CRYPTO_KEY_DIST or not) has to be sent along the wire. > CRYPTO_KEY_DIST must be above the "reliability" layers and the master creates > for each change in the view a new key. This key is sent down to the > CRYPTO_SYM layer where it is combined with the symmetric key. CRYPTO_KEY_DIST > should verify a new member with a challenge response procedure (e.g. based on > the same symmetric key as CRYPTO_SYM) > A nice feature of the CRYPTO_SYM would be to hash the messages and encrypt > the hash along with the message so that the message can be verified. > Currently the layers above ENCRYPT have to handle and discard corrupt > messages. > CRYPTO_SYM could be run without CRYPTO_KEY_DIST but the usage of both > together would protect JGroups from replay attacks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-31) Problem with MERGE2 when not using multicast
[ http://jira.jboss.com/jira/browse/JGRP-31?page=history ] Bela Ban resolved JGRP-31: -- Resolution: Done I added the merge_leader flag to GMS. Another possibility to solve this is to use the TCP:MPING combination > Problem with MERGE2 when not using multicast > > > Key: JGRP-31 > URL: http://jira.jboss.com/jira/browse/JGRP-31 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN Java 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > > > Hi, > There is one case in which MERGE2 will fail while using TCPPING/UDP(without > mcast): > > The initial_hosts property is "abc.com[7800];xyz.com[7801]". > These 2 machines are permanent group members (if they are up, they will be > members of the group). > Now there are numerous other programs on different machines that may > dynamically join and leave the group. These members are not known before hand > and cannot be specified in the initial_hosts property. > The members on abc.com and xyz.com are started and they join the same group. > Now another member from "mnop.com" starts and joins the group. The > co-ordinator will be abc.com > A network problem occurs and mnop.com is separated from abc.com and xyz.com > mnop.com forms its own single-member group with itself as the co-ordinator. > Now suppose the network problem is fixed. The MERGE2 protocol on mnop.com > periodically checks on the initial_hosts list to see if they are up. It now > finds that abc.com is reachable and decides that abc.com is the leader (by > lexical sorting) and will take care of the merging. So it does not go ahead > with the merge. > On the other hand, the MERGE2 protocol on both abc.com and xyz.com just check > if they can find members on the initial_hosts with a different co-ordinator. > Both of them never consider mnop.com as it is not in the initial_hosts list > So mnop.com will never be merged with the group. > > Even the new MERGE3 & MERGEFAST protocols don't seem to help here. I checked > them out and found the following: > MERGEFAST works only if multicast is used, which is not my case. > MERGE3 just sends "I am co-ordinator" messages to a null destination. So in > the case where multicast is enabled, it goes to all possible members. But in > my case, with multicast disabled, the message will only be unicast to each > member of the current group. So in the above example, the "I am co-ordinator" > messages will never go to mnop.com after the network problem. > So even MERGE3 does not work in this case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: JBPTL-17: Theme API food for thought
"[EMAIL PROTECTED]" wrote : Martin, will the new examples have the theme display portlets within it? | | The zengarden app, only shows the zengarden page. It does not display within IE, but you knew that already. ;-) depends on what you consider theme display portlets. the zengarden app contains a set of portlets that work together with the theme. I beliefe a set of portlets to list the available themes and layouts, that let the user choose one, would be helpful to understand the concepts better I'll add those View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873084#3873084 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873084 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: EJB TimerService in a clustered environment
Hi Marcus. They say that JBoss persists the timers to a database so that, if the server crashes, they will be restored at the next startup. This is true only if the server crashes, but not for a normal shutdown. My feeling is that they delete all timers that are not related to entity beans (ie. the field InstancePK in TIMERS table is NULL). In my case, I'm using only stateless session beans, so... Two possible workarounds for persisting your timers in the case of a normal shutdown would be: 1. To modify yourself the JBoss'es source code, but you have to be careful not to break something in it. 2. To create a table (besides TIMERS) that will keep the necessary information to re-create the timers each time the server starts. For example, you can keep there the start date, interval, next run date, and at the startup (or at least when you'd want to create the timers) you can re-compute the next run and create a new timer. I have opted for the second one and it works fine for me. By the way, I'm using JBoss 4.0.1sp1 (JBoss 4.0.2RC1 presents the same situation). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873083#3873083 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873083 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JGRP-45) JVM Crashes when starting three groups at the same time
[ http://jira.jboss.com/jira/browse/JGRP-45?page=history ] Bela Ban closed JGRP-45: Resolution: Done This has nothing to do with JGroups; the log clearly shows that it was the JMS invocation layer which crashed. Although I doubt that code can crash the VM, I think this is a VM bug > JVM Crashes when starting three groups at the same time > --- > > Key: JGRP-45 > URL: http://jira.jboss.com/jira/browse/JGRP-45 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: Linux RedHat 2.4.21-27.0.1.ELsmp #1 SMP Mon Dec 20 18:47:45 EST > 2004 i686 i686 i386 GNU/Linux (our dev02 box) > Reporter: Clebert Suconic > Assignee: Bela Ban > Priority: Minor > Fix For: 2.2.8 > Attachments: console3.out.gz > > > When starting three clusters at the same time, a JVM crashed inside the > socket JNI function. > I've added the log file for the crashed instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - CMSPortlet
Hi. I would like to implement diferent instances of CMSPortlet and AdminCMSPortlet each for a diferente part of content. How can I do this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873080#3873080 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873080 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-40) Connections remain open even after the channel port changes, while using TCP
[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban resolved JGRP-40: -- Resolution: Done Please re-open the case if you find the problem still exists > Connections remain open even after the channel port changes, while using TCP > > > Key: JGRP-40 > URL: http://jira.jboss.com/jira/browse/JGRP-40 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN JDK 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > Attachments: ShunTest.java, default.xml, tcp.xml > > > I am using TCP/TCPPING as the base of the stack. Sometimes one of the > members of the group gets shunned. That member then disconnects from the > group and re-connects. This time, it gets assigned a different TCP port. > But a netstat for ESTABLISHED connections shows the connections of the old > and the new port still active. > Shouldn't the connections for the old port have been closed? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-40) Connections remain open even after the channel port changes, while using TCP
[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban updated JGRP-40: - Attachment: tcp.xml > Connections remain open even after the channel port changes, while using TCP > > > Key: JGRP-40 > URL: http://jira.jboss.com/jira/browse/JGRP-40 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN JDK 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > Attachments: ShunTest.java, default.xml, tcp.xml > > > I am using TCP/TCPPING as the base of the stack. Sometimes one of the > members of the group gets shunned. That member then disconnects from the > group and re-connects. This time, it gets assigned a different TCP port. > But a netstat for ESTABLISHED connections shows the connections of the old > and the new port still active. > Shouldn't the connections for the old port have been closed? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-40) Connections remain open even after the channel port changes, while using TCP
[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban updated JGRP-40: - Attachment: default.xml > Connections remain open even after the channel port changes, while using TCP > > > Key: JGRP-40 > URL: http://jira.jboss.com/jira/browse/JGRP-40 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN JDK 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > Attachments: ShunTest.java, default.xml, tcp.xml > > > I am using TCP/TCPPING as the base of the stack. Sometimes one of the > members of the group gets shunned. That member then disconnects from the > group and re-connects. This time, it gets assigned a different TCP port. > But a netstat for ESTABLISHED connections shows the connections of the old > and the new port still active. > Shouldn't the connections for the old port have been closed? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-40) Connections remain open even after the channel port changes, while using TCP
[ http://jira.jboss.com/jira/browse/JGRP-40?page=comments#action_12316766 ] Bela Ban commented on JGRP-40: -- Ran the attached example with both default.xml and tcp.xml (attached as well). Works okay with 2.2.8 CVS head > Connections remain open even after the channel port changes, while using TCP > > > Key: JGRP-40 > URL: http://jira.jboss.com/jira/browse/JGRP-40 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN JDK 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > Attachments: ShunTest.java > > > I am using TCP/TCPPING as the base of the stack. Sometimes one of the > members of the group gets shunned. That member then disconnects from the > group and re-connects. This time, it gets assigned a different TCP port. > But a netstat for ESTABLISHED connections shows the connections of the old > and the new port still active. > Shouldn't the connections for the old port have been closed? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JGRP-40) Connections remain open even after the channel port changes, while using TCP
[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban updated JGRP-40: - Attachment: ShunTest.java Example > Connections remain open even after the channel port changes, while using TCP > > > Key: JGRP-40 > URL: http://jira.jboss.com/jira/browse/JGRP-40 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN JDK 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > Attachments: ShunTest.java > > > I am using TCP/TCPPING as the base of the stack. Sometimes one of the > members of the group gets shunned. That member then disconnects from the > group and re-connects. This time, it gets assigned a different TCP port. > But a netstat for ESTABLISHED connections shows the connections of the old > and the new port still active. > Shouldn't the connections for the old port have been closed? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: admin link
yes, 1. standart login with the user admin and the password admin 2. left menu, i cklick the admin-link after this, i don't see anything in the admin cms regards Lars When can i download the complete version of the portal with JBoss AS 4.0.1 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873078#3873078 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873078 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: JBPTL-17: Theme API food for thought
Martin, will the new examples have the theme display portlets within it? The zengarden app, only shows the zengarden page. It does not display within IE, but you knew that already. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873077#3873077 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873077 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: admin link
Did you login as an admin? admin/admin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873075#3873075 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873075 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-236) Documentation update
Documentation update Key: JBPORTAL-236 URL: http://jira.jboss.com/jira/browse/JBPORTAL-236 Project: JBoss Portal Type: Feature Request Versions: 2.0 RC, 2.0 Final Reporter: Julien Viet Assigned to: Julien Viet Fix For: 2.0 Final Maintain the documentation regarding the changes that have been introduced since 2.0 beta. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Is org.jboss.util.loading.Translator still used?
The ULR is a deployment level configuration. The only way two wars in an ear can be isolated today is if they use independent class loaders and these are not jboss class loaders. They can be which is why I was asking if Translator was required to interact with aop. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873072#3873072 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873072 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-235) Forum module partial port
[ http://jira.jboss.com/jira/browse/JBPORTAL-235?page=history ] Julien Viet updated JBPORTAL-235: - Summary: Forum module partial port (was: Forum module port) Fix Version: 2.0 RC 2.0 Final > Forum module partial port > - > > Key: JBPORTAL-235 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-235 > Project: JBoss Portal > Type: Feature Request > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Julien Viet > Fix For: 2.0 RC, 2.0 Final > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-93) Forum posts can become unusable due to width of content
[ http://jira.jboss.com/jira/browse/JBPORTAL-93?page=history ] Julien Viet updated JBPORTAL-93: Version: 2.0 RC 2.0 Final > Forum posts can become unusable due to width of content > --- > > Key: JBPORTAL-93 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-93 > Project: JBoss Portal > Type: Patch > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Scott M Stark > Assignee: Julien Viet > Fix For: 2.0 RC, 2.0 Final > > > I'm seeing problems with the size of forum posts using the [code][/code] > tags. There needs to be some fixed size to the text fields with scrolling > instead of what is seen here: > > http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857964 > http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858023 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-235) Forum module port
Forum module port - Key: JBPORTAL-235 URL: http://jira.jboss.com/jira/browse/JBPORTAL-235 Project: JBoss Portal Type: Feature Request Components: Forums Versions: 2.0 RC, 2.0 Final Reporter: Julien Viet Assigned to: Julien Viet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-101) URL BB Code tag does not work correctly on several lines
[ http://jira.jboss.com/jira/browse/JBPORTAL-101?page=history ] Julien Viet updated JBPORTAL-101: - Version: 2.0 RC 2.0 Final (was: 2.0 Alpha) > URL BB Code tag does not work correctly on several lines > > > Key: JBPORTAL-101 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-101 > Project: JBoss Portal > Type: Bug > Components: Forums > Versions: 2.0 RC, 2.0 Final > Environment: Nukes 1 > Reporter: Thomas Heute > Fix For: 2.0 RC, 2.0 Final > > > Fix the following bug from Nukes: > -- > A URL that is not trimmed > > [url] > http://www.jboss.org/index.html?module=bb&op=viewforum&f=163 > [/url] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-173) Misplaced forum postings
[ http://jira.jboss.com/jira/browse/JBPORTAL-173?page=history ] Julien Viet updated JBPORTAL-173: - Version: 2.0 RC 2.0 Final (was: Nukes 1.1 (support)) > Misplaced forum postings > > > Key: JBPORTAL-173 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-173 > Project: JBoss Portal > Type: Bug > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Ivelin Ivanov > Assignee: Julien Viet > Priority: Critical > Fix For: 2.0 RC, 2.0 Final > > > From: Scott Stark > Subject: RE: [JBoss-user] [Messaging, JMS & JBossMQ] - Re: Question about JMS > queue config > This is a thread that has the first message replaced with some random posting. > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of wsnyder6 > > Sent: Saturday, January 08, 2005 5:15 AM > > To: jboss-user@lists.sourceforge.net > > Subject: [JBoss-user] [Messaging, JMS & JBossMQ] - Re: > > Question about JMS queue config > > > > Wierd how the original post got lost at the top of the thread... > > > > Anyway, thanks for verifying the config > > > > I didn't realize that debug/trace info goes to the log file rather > > than the console...whooops :) > > > > My login module was not handling null principals. > > > > Authentication and authorization works now. > > > > Thanks > > > > --Bill > > > > > > View the original post : > > http://www.jboss.org/index.html?module=bb&op=viewtopic&p=38612 > > 58#3861258 > > > > Reply to the post : > > http://www.jboss.org/index.html?module=bb&op=posting&mode=repl > > y&p=3861258 > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-220) Polls
[ http://jira.jboss.com/jira/browse/JBPORTAL-220?page=history ] Julien Viet updated JBPORTAL-220: - Version: 2.0 Final > Polls > - > > Key: JBPORTAL-220 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-220 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 RC, 2.0 Final > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-221) Post attachments
[ http://jira.jboss.com/jira/browse/JBPORTAL-221?page=history ] Julien Viet updated JBPORTAL-221: - Version: 2.0 Final > Post attachments > > > Key: JBPORTAL-221 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-221 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 RC, 2.0 Final > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-93) Forum posts can become unusable due to width of content
[ http://jira.jboss.com/jira/browse/JBPORTAL-93?page=history ] Julien Viet updated JBPORTAL-93: Fix Version: 2.0 RC 2.0 Final > Forum posts can become unusable due to width of content > --- > > Key: JBPORTAL-93 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-93 > Project: JBoss Portal > Type: Patch > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Scott M Stark > Assignee: Julien Viet > Fix For: 2.0 RC, 2.0 Final > > > I'm seeing problems with the size of forum posts using the [code][/code] > tags. There needs to be some fixed size to the text fields with scrolling > instead of what is seen here: > > http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857964 > http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858023 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-101) URL BB Code tag does not work correctly on several lines
[ http://jira.jboss.com/jira/browse/JBPORTAL-101?page=history ] Julien Viet updated JBPORTAL-101: - Fix Version: 2.0 RC 2.0 Final > URL BB Code tag does not work correctly on several lines > > > Key: JBPORTAL-101 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-101 > Project: JBoss Portal > Type: Bug > Components: Forums > Versions: 2.0 RC, 2.0 Final > Environment: Nukes 1 > Reporter: Thomas Heute > Fix For: 2.0 RC, 2.0 Final > > > Fix the following bug from Nukes: > -- > A URL that is not trimmed > > [url] > http://www.jboss.org/index.html?module=bb&op=viewforum&f=163 > [/url] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-173) Misplaced forum postings
[ http://jira.jboss.com/jira/browse/JBPORTAL-173?page=history ] Julien Viet updated JBPORTAL-173: - Fix Version: 2.0 RC 2.0 Final > Misplaced forum postings > > > Key: JBPORTAL-173 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-173 > Project: JBoss Portal > Type: Bug > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Ivelin Ivanov > Assignee: Julien Viet > Priority: Critical > Fix For: 2.0 RC, 2.0 Final > > > From: Scott Stark > Subject: RE: [JBoss-user] [Messaging, JMS & JBossMQ] - Re: Question about JMS > queue config > This is a thread that has the first message replaced with some random posting. > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of wsnyder6 > > Sent: Saturday, January 08, 2005 5:15 AM > > To: jboss-user@lists.sourceforge.net > > Subject: [JBoss-user] [Messaging, JMS & JBossMQ] - Re: > > Question about JMS queue config > > > > Wierd how the original post got lost at the top of the thread... > > > > Anyway, thanks for verifying the config > > > > I didn't realize that debug/trace info goes to the log file rather > > than the console...whooops :) > > > > My login module was not handling null principals. > > > > Authentication and authorization works now. > > > > Thanks > > > > --Bill > > > > > > View the original post : > > http://www.jboss.org/index.html?module=bb&op=viewtopic&p=38612 > > 58#3861258 > > > > Reply to the post : > > http://www.jboss.org/index.html?module=bb&op=posting&mode=repl > > y&p=3861258 > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-224) Forum user's preferences
[ http://jira.jboss.com/jira/browse/JBPORTAL-224?page=history ] Julien Viet updated JBPORTAL-224: - Fix Version: 2.0 Final > Forum user's preferences > > > Key: JBPORTAL-224 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-224 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 RC, 2.0 Final > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-221) Post attachments
[ http://jira.jboss.com/jira/browse/JBPORTAL-221?page=history ] Julien Viet updated JBPORTAL-221: - Fix Version: 2.0 RC 2.0 Final > Post attachments > > > Key: JBPORTAL-221 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-221 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 RC, 2.0 Final > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-217) Reply with quote is not working
[ http://jira.jboss.com/jira/browse/JBPORTAL-217?page=history ] Julien Viet updated JBPORTAL-217: - Fix Version: 2.0 Final > Reply with quote is not working > --- > > Key: JBPORTAL-217 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-217 > Project: JBoss Portal > Type: Bug > Components: Forums > Versions: 2.0 RC, 2.0 Final > Environment: Windows XP > Reporter: Sudhir Kumar Machetti > Assignee: Julien Viet > Priority: Minor > Fix For: 2.0 RC, 2.0 Final > > > I am trying to post reply with previous message in quotes. I clicked on > quotes button. I got editor to post my reply. I have submitted me reply. > I don't see previous message in quotes in my reply? > Did I miss anything? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-220) Polls
[ http://jira.jboss.com/jira/browse/JBPORTAL-220?page=history ] Julien Viet updated JBPORTAL-220: - Fix Version: 2.0 RC 2.0 Final > Polls > - > > Key: JBPORTAL-220 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-220 > Project: JBoss Portal > Type: Task > Components: Forums > Versions: 2.0 RC, 2.0 Final > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 RC, 2.0 Final > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-234) JBoss Portal 2.2 Roadmap
JBoss Portal 2.2 Roadmap Key: JBPORTAL-234 URL: http://jira.jboss.com/jira/browse/JBPORTAL-234 Project: JBoss Portal Type: Task Components: Portal Core Reporter: Julien Viet Assigned to: Julien Viet Define JBoss Portal 2.2 Roadmap in order to meet the following requirements (subject to change) - wsrp 1.0 - wsrp 2.0 features - dashboarding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1669) NullPointerException in DLQHandler
[ http://jira.jboss.com/jira/browse/JBAS-1669?page=history ] Scott M Stark closed JBAS-1669: --- Assign To: Scott M Stark Resolution: Done > NullPointerException in DLQHandler > -- > > Key: JBAS-1669 > URL: http://jira.jboss.com/jira/browse/JBAS-1669 > Project: JBoss Application Server > Type: Bug > Components: JMS service > Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Scott M Stark > Assignee: Scott M Stark > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final > > Original Estimate: 1 hour > Remaining: 1 hour > > This is an old bug fixed in 3.2 that never was ported to head and so never > made it into 4.0. > 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
