[JBoss-dev] [ jboss-Bugs-989264 ] NPE invoking a finder
Bugs item #989264, was opened at 2004-07-12 08:30 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=989264group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: ittay dror (ittay) Assigned to: Nobody/Anonymous (nobody) Summary: NPE invoking a finder Initial Comment: our code hooks as a ServletContextListener, upon contextDestroyed call it tries to get some bean, by invoking a finder. this is the stack trace (jboss 3.2.5) 2004-07-12 11:06:14,137 FATAL [com.qlusters.qrm.server.misc. ServerLifecycleListener] (JBoss Shutdown Hook:Tomcat5) Recovery exception java.lang.NullPointerException at org.jboss.ejb.plugins.local.BaseLocalProxyFactory. invokeHome(BaseLocalProxyFactory.java:281) at org.jboss.ejb.plugins.local.LocalHomeProxy. invoke(LocalHomeProxy.java:110) at $Proxy123.findByProperty(Unknown Source) at com.qlusters.qrm.server.common.objects.DbPrefs. setProperty(DbPrefs.java:105) at com.qlusters.qrm.server.common.objects.DbPrefs. setProperty(DbPrefs.java:96) at com.qlusters.qrm.server.common.objects.DbPrefs. setProperty(DbPrefs.java:85) at com.qlusters.qrm.server.common.objects.DbPrefs. setDateProperty(DbPrefs.java:134) at com.qlusters.qrm.server.recovery.Status. setShutdownDate(Status.java:124) at com.qlusters.qrm.server.recovery.Loader.unload(Loader.java: 193) at com.qlusters.qrm.server.misc.ServerLifecycleListener. onStop(ServerLifecycleListener.java:119) at com.qlusters.qrm.web.init.WebLifecycleListener. contextDestroyed(WebLifecycleListener.java:38) at org.apache.catalina.core.StandardContext. listenerStop(StandardContext.java:3846) at org.apache.catalina.core.StandardContext. stop(StandardContext.java:4478) at org.apache.catalina.core.ContainerBase. removeChild(ContainerBase.java:952) at org.apache.catalina.core.StandardHostDeployer. remove(StandardHostDeployer.java:670) at org.apache.catalina.core.StandardHost. remove(StandardHost.java:946) at org.apache.catalina.startup.HostConfig. undeployApps(HostConfig.java:1013) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java: 990) at org.apache.catalina.startup.HostConfig. lifecycleEvent(HostConfig.java:351) at org.apache.catalina.util.LifecycleSupport. fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.stop(ContainerBase. java:1123) at org.apache.catalina.core.ContainerBase.stop(ContainerBase. java:1135) at org.apache.catalina.core.StandardEngine. stop(StandardEngine.java:483) at org.jboss.web.tomcat.tc5.StandardService. stop(StandardService.java:545) at org.apache.catalina.core.StandardServer. stop(StandardServer.java:2347) at org.apache.catalina.startup.Catalina.stop(Catalina.java:605) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl. invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.modeler.BaseModelMBean. invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker. invoke(RawDynamicInvoker.java:109) at org.jboss.mx.server.MBeanServerImpl. invoke(MBeanServerImpl.java:473) at org.jboss.web.tomcat.tc5.Tomcat5.stopService(Tomcat5. java:318) at org.jboss.system.ServiceMBeanSupport. jbossInternalStop(ServiceMBeanSupport.java:319) at org.jboss.system.ServiceMBeanSupport. jbossInternalLifecycle(ServiceMBeanSupport.java:223)at sun. reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher. dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker. invoke(AbstractMBeanInvoker.java:185) at org.jboss.mx.server.MBeanServerImpl. invoke(MBeanServerImpl.java:473) at org.jboss.system.ServiceController$ServiceProxy. invoke(ServiceController.java:837) at $Proxy17.stop(Unknown Source) at org.jboss.system.ServiceController.stop(ServiceController. java:449) at org.jboss.system.ServiceController.stop(ServiceController. java:440) at sun.reflect.GeneratedMethodAccessor194.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.
[JBoss-dev] [ jboss-Bugs-989264 ] NPE invoking a finder
Bugs item #989264, was opened at 2004-07-12 08:30 Message generated for change (Comment added) made by ittay You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=989264group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: ittay dror (ittay) Assigned to: Nobody/Anonymous (nobody) Summary: NPE invoking a finder Initial Comment: our code hooks as a ServletContextListener, upon contextDestroyed call it tries to get some bean, by invoking a finder. this is the stack trace (jboss 3.2.5) 2004-07-12 11:06:14,137 FATAL [com.qlusters.qrm.server.misc. ServerLifecycleListener] (JBoss Shutdown Hook:Tomcat5) Recovery exception java.lang.NullPointerException at org.jboss.ejb.plugins.local.BaseLocalProxyFactory. invokeHome(BaseLocalProxyFactory.java:281) at org.jboss.ejb.plugins.local.LocalHomeProxy. invoke(LocalHomeProxy.java:110) at $Proxy123.findByProperty(Unknown Source) at com.qlusters.qrm.server.common.objects.DbPrefs. setProperty(DbPrefs.java:105) at com.qlusters.qrm.server.common.objects.DbPrefs. setProperty(DbPrefs.java:96) at com.qlusters.qrm.server.common.objects.DbPrefs. setProperty(DbPrefs.java:85) at com.qlusters.qrm.server.common.objects.DbPrefs. setDateProperty(DbPrefs.java:134) at com.qlusters.qrm.server.recovery.Status. setShutdownDate(Status.java:124) at com.qlusters.qrm.server.recovery.Loader.unload(Loader.java: 193) at com.qlusters.qrm.server.misc.ServerLifecycleListener. onStop(ServerLifecycleListener.java:119) at com.qlusters.qrm.web.init.WebLifecycleListener. contextDestroyed(WebLifecycleListener.java:38) at org.apache.catalina.core.StandardContext. listenerStop(StandardContext.java:3846) at org.apache.catalina.core.StandardContext. stop(StandardContext.java:4478) at org.apache.catalina.core.ContainerBase. removeChild(ContainerBase.java:952) at org.apache.catalina.core.StandardHostDeployer. remove(StandardHostDeployer.java:670) at org.apache.catalina.core.StandardHost. remove(StandardHost.java:946) at org.apache.catalina.startup.HostConfig. undeployApps(HostConfig.java:1013) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java: 990) at org.apache.catalina.startup.HostConfig. lifecycleEvent(HostConfig.java:351) at org.apache.catalina.util.LifecycleSupport. fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.stop(ContainerBase. java:1123) at org.apache.catalina.core.ContainerBase.stop(ContainerBase. java:1135) at org.apache.catalina.core.StandardEngine. stop(StandardEngine.java:483) at org.jboss.web.tomcat.tc5.StandardService. stop(StandardService.java:545) at org.apache.catalina.core.StandardServer. stop(StandardServer.java:2347) at org.apache.catalina.startup.Catalina.stop(Catalina.java:605) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl. invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.modeler.BaseModelMBean. invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker. invoke(RawDynamicInvoker.java:109) at org.jboss.mx.server.MBeanServerImpl. invoke(MBeanServerImpl.java:473) at org.jboss.web.tomcat.tc5.Tomcat5.stopService(Tomcat5. java:318) at org.jboss.system.ServiceMBeanSupport. jbossInternalStop(ServiceMBeanSupport.java:319) at org.jboss.system.ServiceMBeanSupport. jbossInternalLifecycle(ServiceMBeanSupport.java:223)at sun. reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher. dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker. invoke(AbstractMBeanInvoker.java:185) at org.jboss.mx.server.MBeanServerImpl. invoke(MBeanServerImpl.java:473) at org.jboss.system.ServiceController$ServiceProxy. invoke(ServiceController.java:837) at $Proxy17.stop(Unknown Source) at org.jboss.system.ServiceController.stop(ServiceController. java:449) at org.jboss.system.ServiceController.stop(ServiceController. java:440) at sun.reflect.GeneratedMethodAccessor194.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.
[JBoss-dev] [ jboss-Bugs-935196 ] NullPointerException in SimpleReadWriteEJBLock
Bugs item #935196, was opened at 2004-04-14 15:46 Message generated for change (Comment added) made by seiffert You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=935196group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: eugene (eugene75) Assigned to: Nobody/Anonymous (nobody) Summary: NullPointerException in SimpleReadWriteEJBLock Initial Comment: When setting a CMR field (either one-to-one or one-to- many), a null pointer occurs in SimpleReadWriteEJBLock.schedule. The cause is a null method attribute in the Invocation object. When the invocation, in this case a CMRInvocation, is created in the JDBCRelationSetBridge object, no method is set. -- Comment By: Kurt A. Seiffert (seiffert) Date: 2004-07-12 09:19 Message: Logged In: YES user_id=269007 Is there any change on this bug? This one is biting us and it would be nice if it was fixed. -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-04-20 04:33 Message: Logged In: YES user_id=206536 Or we could just get out of the schedule method on finding out that mi.getMethod is null. Anyway, the calling Tx is in effect and this method call is only to get the object corresponding to the foreign key. We probably need to change releaseReadLock and releaseWriteLock if we are going about in this manner -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-04-20 04:27 Message: Logged In: YES user_id=206536 Yes, so one way to circumvent this is to loop around the method-name argument. We could just check for a null value and substitute no-method instead. This would make boolean reading return false, so it would create a write lock and use the same Tx as it was called with. I can fill in a patch if that sounds ok -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=935196group_id=22866 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-989554 ] Problem with MDB which uses JNI and raw sockets
Bugs item #989554, was opened at 2004-07-12 16:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=989554group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: walkman (walkman_s) Assigned to: Nobody/Anonymous (nobody) Summary: Problem with MDB which uses JNI and raw sockets Initial Comment: We wrote a small program which uses JNI and raw sockets. There were no problems when we used it outside Jboss. The problem starts only when we try to use this code from an MDB. We tried to put the *.so lib in the jboss /bin directory. When the Jboss gets to the part when it needs to send the packet through the raw socket nothing is been sent (using ethreal). when we tried to debug the c code using printf() commands we couldn't see the output and sometimes the jboss crashed. The output we got after the crash was something like we were in the middle of handling another exception while this one accure. files description: Several files Atached to this message: The c src files. The java src files. IpMulitiClient.java which is the beginning of the problem. Inside it there is a method named sendData(). The last paramter of the method should be 1. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=989554group_id=22866 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.132 Build Successful
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-3.2?log=log20040712123818Lbuild.132 BUILD COMPLETE-build.132Date of build:07/12/2004 12:38:18Time to build:12 minutes 55 secondsLast changed:07/12/2004 12:18:18Last log entry:Avoid the warning about nested loader repository config when there is none. Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build:(1)1.51.2.32modifiedejortserver/src/main/org/jboss/web/AbstractWebContainer.javaAvoid the warning about nested loader repository config when there is none.
[JBoss-dev] jboss-3.2 build.133 Build Successful
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-3.2?log=log20040712130701Lbuild.133 BUILD COMPLETE-build.133Date of build:07/12/2004 13:07:01Time to build:13 minutes 1 secondLast changed:07/12/2004 12:41:59Last log entry:added LGPL boilerplate Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build:(1)1.1.2.2modifiedssilvertcommon/src/main/org/jboss/logging/filter/TCLFilter.javaadded LGPL boilerplate
[JBoss-dev] [JBoss IDE] - Tutorial on CMP for JBoss IDE?
Hi, I'm new to EJB/XDoclet and just curious will someone create a tutorial for CMP in Jboss IDE similar to the tutorial that I can download on the web site? Thanks, Andy View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841807#3841807 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841807 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Re: [SOLVED] XDoclet Configuration does not appear in projec
I met the same problem and mac os x and solved it. But I found that I cannot give edit it at all. Could you give any advice? Thanks! View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841808#3841808 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841808 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Another test that not execute correctly...
You are getting the error because the Interceptor is in the same package expression as the class you are trying to intercept. Thus, you have an infinite loop. Put your interceptors in another package that doesn't match your wildcard. Bill View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841809#3841809 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841809 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Several jboss-aop.xml...
Are you running inside JBoss? AOP is packaged similarly to SARs(Mbeans). You can either deploy an XML file directly in the deploy/ directory with the signature *-aop.xml or you can use the JAR format. The JAR format must have the file extension .aop and a jboss-aop.xml file must be contained in a META-INF directory. META-INF/jboss-aop.xml. Take from this WIKI page: http://www.jboss.org/wiki/Wiki.jsp?page=RunningWithJBossApplicationServer If you're not running within JBoss then read this: http://www.jboss.org/wiki/Wiki.jsp?page=RunningAOPStandalone http://www.jboss.org/wiki/Wiki.jsp?page=Packaging The system property jboss.aop.path can be a separated list of xml files and/or directories. If it is a directory, then it will get all *-aop.xml files within that directory. Bill View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841811#3841811 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841811 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Another issue...
Since you are not running within JBoss you need to use System properties to tell JBoss AOP how to resolve XML files to be deployed. Please see our WIKI for more information View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841812#3841812 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841812 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: jboss-aop-beta3 failed to transform
JBoss AOP aopc will generate a bunch of class files that are optimized versions of Invocation classes. When in doubt, blow away your class directory with everything in it. Looks like you cleaned up DBBasicManager.class, but not the generated AOP class files. Bill View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841813#3841813 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841813 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: AOP examples on jboss-4.0.0DR3
http://www.jboss.org/wiki/Wiki.jsp?page=RunningWithJBossApplicationServer Use 4.0DR4 and Overwrite with jars from JBoss AOP beta3 distribution. Bill View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841814#3841814 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841814 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-731352 ] Please re-repair lt;fk-constraint-templategt;, Bug 597047
Bugs item #731352, was opened at 2003-05-02 16:57 Message generated for change (Comment added) made by loubyansky You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=731352group_id=22866 Category: None Group: None Status: Closed Resolution: Fixed Priority: 8 Submitted By: Arnim Sahl (asahl) Assigned to: Alexey Loubyansky (loubyansky) Summary: Please re-repair lt;fk-constraint-templategt;, Bug 597047 Initial Comment: The Java-class generating the SQL-statement and the lt;fk-constraint-templategt; of the mySql-section of quot;standardjbosscmp.xmlquot; should be changed: ADD INDEX ind_?3 (?3) will only work for a simple primary key. When referencing the columns for a custom primary key class, the generated statement should be: ALTER TABLE t1 ADD INDEX ind_f1_f2 ( f1, f2 ) ... instead of: ALTER TABLE t1 ADD INDEX ind_f1, f2 ( f1, f2 ) ... which obviously leeds to an SQLException at deploy time. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-07-13 00:28 Message: Logged In: YES user_id=543482 Fixed in 3.2.6RC1. -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-11-16 19:08 Message: Logged In: YES user_id=217112 Alexey, I know we had a talk about this fk-constraint, but don't recall the result. Could you look at it? Cheers Heiko -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=731352group_id=22866 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Caches on JBoss (Caches/JBoss)] - Re: Using JBossCache with WebLogic 8.1 and WebSphere 5.1
Thanks for the replies. Regarding the spec violation, it's not a problem currently provided that it doesn't adversely impact performance and scalability. It might be a issue someday if we wanted to get our application certified as J2EE compliant, but that's not in the immediate roadmap. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841819#3841819 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841819 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.134 Build Successful
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-3.2?log=log20040712174209Lbuild.134 BUILD COMPLETE-build.134Date of build:07/12/2004 17:42:09Time to build:11 minutes 23 secondsLast changed:07/12/2004 17:22:09Last log entry:fixed fk constraint template for mySQL Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build:(5)1.39.2.49modifiedloubyanskyserver/src/etc/conf/default/standardjbosscmp-jdbc.xmlfixed fk constraint template for mySQL1.1.2.10modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javaschema generation: fixed foreign key contraints generation, fixed dropping tables on undeploy (some tables being referenced by others were not dropped).1.29.2.30modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCStartCommand.javaschema generation: fixed foreign key contraints generation, fixed dropping tables on undeploy (some tables being referenced by others were not dropped).1.15.2.8modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCStopCommand.javaschema generation: fixed foreign key contraints generation, fixed dropping tables on undeploy (some tables being referenced by others were not dropped).1.42.2.32modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCStoreManager.javaschema generation: fixed foreign key contraints generation, fixed dropping tables on undeploy (some tables being referenced by others were not dropped).
[JBoss-dev] [Security on JBoss] - Re: JBOSS - Embedded TOMCAT JAAS Failure
I upgraded to 3.2.5 and this time i am consistently getting the principal=null exception. If I access the appplication server outside of JBOSS/TOMCAT, it works like a charm. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3841822#3841822 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841822 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/winxp/1.4.1_06) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jul 13 01:43:17 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === RuntimeErrorException: null Cause: java.lang.OutOfMemoryError at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:164) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:149) 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:230) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:352) at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) 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:536) 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:135) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:96) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:58) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:59) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy0.invoke(Unknown Source) at org.jboss.Shutdown$ServerProxyHandler.invoke(Shutdown.java:234) at $Proxy1.shutdown(Unknown Source) at org.jboss.Shutdown.main(Shutdown.java:205) Caused by: java.lang.OutOfMemoryError Exception in thread main JBOSS SHUTDOWN FAILED === Tue Jul 13 01:43:17 GMTDT 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version 1.4.1_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_06-b01) Java HotSpot(TM) Client VM (build 1.4.1_06-b01, mixed mode) --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-988143 ] unable to activate stateful session beans
Bugs item #988143, was opened at 2004-07-10 02:15 Message generated for change (Comment added) made by clli You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=988143group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Lars Kral (lkral) Assigned to: Nobody/Anonymous (nobody) Summary: unable to activate stateful session beans Initial Comment: When a SFSB has a reference to its own EJBObject stub either as a non-transient instance field or in the object graph of a non-transient instance field, reactivation of this EJB will fail. A client call, which triggers an activation of this bean instance, will never return and only result in a 'transaction timeout' message: [TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=linux//15, BranchQual=] timed out. status=STATUS_ACTIVE Here the relevant part of the log file: 2004-07-09 19:42:11,303 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceMana ger] Attempting to activate; [EMAIL PROTECTED] c28 2004-07-09 19:42:11,303 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceMana ger] Reading session state from: /usr/local/jboss- 3.2.5/server/default/tmp/sessions/Test1-dwgl7cj6- 4/dwgllux9-5.ser 2004-07-09 19:47:11,316 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=linux//15, BranchQual=] timed out. status=STATUS_ACTIVE To reproduce the described behaviour I have attached a jar file containing (deployable) SFSBs and a simple client (binary + source). Tested with: JBoss 3.2.5 / JDK 1.4.2 / SuSE 9.0 -- Comment By: Richard C. L. Li (clli) Date: 2004-07-13 13:39 Message: Logged In: YES user_id=735048 Oh, yes, you are right, this problem will not let JBoss to pass Sun's CTS. As I remember, this problem is here since JBoss 2.4.x or before. Somebody have to deal with it. -- Comment By: Lars Kral (lkral) Date: 2004-07-10 19:46 Message: Logged In: YES user_id=936392 Sorry, but I have to disagree. In the EJB 2.1 specs / 7.4.1, the passivation of session beans is described as follows: The objects that are assigned to the instances non- transient fields after the ejbPassivate method completes must be one of the following: [...] An enterprise beans remote interface reference, even if the stub class is not serializable. The container must be able to properly save and restore the reference to the home and component interfaces of the enterprise beans stored in the instances state even if the classes that implement the object references are not serializable. -- Comment By: Richard C. L. Li (clli) Date: 2004-07-10 15:32 Message: Logged In: YES user_id=735048 This is not a bug. You simple violate the specification of Stateful Session Bean. A stub of an remote object is not serializable. Using transient keyword is also not reliable. You have set any non-serializable instance variables to null in ejbPassivate() method and reestablish them to valid values in ejbActivate(). A stub of an remote object is not serializable, however, you may transform it to a handle before passivation, and transform it back to a stub before activation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=988143group_id=22866 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-983462 ] Classloader (?) problem in 3.2.4. and 3.2.5
Bugs item #983462, was opened at 2004-07-01 22:31 Message generated for change (Comment added) made by clli You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=983462group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Domosi Janos (domosi) Assigned to: Nobody/Anonymous (nobody) Summary: Classloader (?) problem in 3.2.4. and 3.2.5 Initial Comment: A full decsription of the problem: http://www.jboss.org/index.htmlmodule=bbop=viewtopi cp=3840616#3840616 Deployment crashes if we place commons-logging.jar into an .ear file (and registerer it with the META- INF/application.xml file) java.lang.NoSuchMethodException: org.apache.commons.modeler.BaseModelMBean.setDocBa se(java.lang.String)) at org.jboss.mx.server.ReflectedDispatcher.handleInvocatio nExceptions(ReflectedDispatcher.java:91) at org.jboss.mx.server.ReflectedDispatcher.dispatch (ReflectedDispatcher.java:64) at org.jboss.mx.server.Invocation.dispatch (Invocation.java:61) at org.jboss.mx.server.Invocation.dispatch (Invocation.java:53) at org.jboss.mx.server.Invocation.invoke (Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke (AbstractMBeanInvoker.java:185) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:473) at org.jboss.system.ServiceController$ServiceProxy.invoke (ServiceController.java:837) at $Proxy17.start(Unknown Source) at org.jboss.system.ServiceController.start (ServiceController.java:367) 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.server.ReflectedDispatcher.dispatch (ReflectedDispatcher -- Comment By: Richard C. L. Li (clli) Date: 2004-07-13 13:47 Message: Logged In: YES user_id=735048 This problem can be reproduceable by using JBoss 3.2.3 with the Tomcat 5.0 SAR for JBoss 3.2.3. It seems the new tomcat breaks the classloading mechanism in JBoss. This is a quite annoying bug, and may have some other hidden problems which may not be found out yet. It just breaks all my STRUTS based web applications. -- Comment By: Stuart Herring (mabinogi) Date: 2004-07-06 09:09 Message: Logged In: YES user_id=34785 We have what may be a related problem we have commons-logging in the WEB-INF/lib directory of a .war file. It works fine if you just deploy the war file, and also works if you deploy it in a .ear file. But if you put a loader-repository entry in the jboss-app file to enforce a separate class loader for the ear, then it throws the following exception - 10:59:59,912 ERROR [Engine] - Root Cause - java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at ...snip... org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:212) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:191) Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) at au.com.hpa.test.TestServlet.clinit(TestServlet.java:18) ... 80 more Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525) ... 84 more Caused by: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412) ... 85 more In this case it's something that only happens with 3.2.5 - 3.2.4 is not affected. -- Comment By: Michael Lipp (drmlipp) Date: 2004-07-05 15:13 Message: Logged In: YES user_id=731113 You get the same
