January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JASSIST-34) Throw a more descriptive exception when a class file does not start with 0xCAFEBABE

by Josh Devins (JIRA)

Throw a more descriptive exception when a class file does not start with 0xCAFEBABE ----------------------------------------------------------------------------------- Key: JASSIST-34 URL: http://jira.jboss.com/jira/browse/JASSIST-34 Project: Javassist Issue Type: Bug Environment: Jboss 4.0.5 GA with EJB3 deployer and IBM DB2 JDBC driver v3.3.54 Reporter: Josh Devins Assigned To: Shigeru Chiba Attachments: server.snipped.log I have deployed an application that is using the IBM DB2 JDBC driver jar version 3.3.54. With the EJB3 deployer installed (since we have EJB3s), some class file in the DB2 jar apparently does not start with 0XCAFEBABE, or "the magic hex code". The EJB3 deployer is using Javassist to examine all of the class files in the jar, but when it hits one of these wonky IBM class files, Javaasisst is throwing an IOException with message "non class file". This is rather useless as the EJB3 deployer then rethrows this IOException as a RuntimeException. I get no info about what class failed, what jar file it was in, etc. Perhaps this is an EJB3 deployer issue, but I believe that Javassist should at least throw a more descriptive exception, and not even an IOException. Or better yet, the EJB3 deployer should not just die and rethrow the RuntimeException, just skip the file! Stepping through the JBoss and Javassist code with my debugger was the only way to figure this out. You can look at the attached stack trace from the server log for the exact files and line numbers. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1284) ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer

by Justin Wick (JIRA)

ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-1284 URL: http://jira.jboss.com/jira/browse/JBRULES-1284 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Environment: Windows XP, Eclipse 3.2 Reporter: Justin Wick Assigned To: Mark Proctor If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint. See attached files for an example -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (JBAS-4254) Client read timeout setting wanted for HTTP Invoker

by Anders Welen (JIRA)

Client read timeout setting wanted for HTTP Invoker ---------------------------------------------------- Key: JBAS-4254 URL: http://jira.jboss.com/jira/browse/JBAS-4254 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.3 SP1 Reporter: Anders Welen Priority: Minor There is no read timeout setting to prevent client threads from hanging while using the HTTP Invoker. A quick fix (if you are using SUN JVM) is to use the parameter "-Dsun.net.client.defaultReadTimeout=60000". The problem with this solution is that it affects all connection, not just the HTTPInvoker. A solution that works (if Java 5 is used) is to add a call to the method "setReadTimeout(xxx)" on the "conn" variable in the method "invoke()" in "org.jboss.invocation.http.interfaces.Util". (The same problem exists with the standard JRMP Invoker aswell. It's just the Pooled Invoker that has a read timeout) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1263) Node.addChild() sends out an update message even if a child was not added

by Manik Surtani (JIRA)

Node.addChild() sends out an update message even if a child was not added ------------------------------------------------------------------------- Key: JBCACHE-1263 URL: http://jira.jboss.com/jira/browse/JBCACHE-1263 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.CR3, 2.1.0.GA -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAOP-6) Compile time reweaving

by Flavia Rainone (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-6?page=comments#action_12394919 ] Flavia Rainone commented on JBAOP-6: ------------------------------------ First thoughts: - the hotswap mechanism could be used for that, so we can "unweave" joinpoints that were previously intercepted but should not be anymore. - this task requires a check before creating any wrapper, field, etc, in order to know if it does not already exist. > Compile time reweaving > ---------------------- > > Key: JBAOP-6 > URL: http://jira.jboss.com/jira/browse/JBAOP-6 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assigned To: Bill Burke > Priority: Minor > Fix For: 2.0.0.GA > > > Support for compile time reweaving. Currently AOPC ignores a class that implements Advised -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1229) Buddy Replication configuration doesn't start if FetchInMemoryState is false.

by Manik Surtani (JIRA)

Buddy Replication configuration doesn't start if FetchInMemoryState is false. ----------------------------------------------------------------------------- Key: JBCACHE-1229 URL: http://jira.jboss.com/jira/browse/JBCACHE-1229 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Should be allowed to skip in-memory state transfer -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-882) Simple static API to easily create simple clients

by David Lloyd (JIRA)

Simple static API to easily create simple clients ------------------------------------------------- Key: JBREM-882 URL: http://jira.jboss.com/jira/browse/JBREM-882 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor Fix For: Remoting 3 M2 Right now the user has to create an endpoint, register protocol handler support, open a session, locate a service, and only then can they open contexts. This is fine in a container where all that stuff would be managed for you. But for trivial clients it's a PITA. Some kind of simple static method for trivial clients would be nice: ContextSource<RequestType, ReplyType> source = Remoting.connectToService(uri, userName, password, serviceType, RequestType.class, ReplyType.class); Context<RequestType, ReplyType> context = source.openContext(); ReplyType r = context.invoke(context.createRequest(new RequestType(...))).getBody(); Maybe even provide some behind-the-scenes session pooling or something... -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-881) Stream detection/object substitution

by David Lloyd (JIRA)

Stream detection/object substitution ------------------------------------ Key: JBREM-881 URL: http://jira.jboss.com/jira/browse/JBREM-881 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 Add in a registry mechanism on Endpoint; make the serializer use the stream detector to get a substitution object; create a lookup mechanism to fetch the appropriate proxy in place of the placeholder object (using readObjectOverride) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-262) Empty post error displays MessageValidationException

by Luc Boudreau (JIRA)

Empty post error displays MessageValidationException ---------------------------------------------------- Key: JBFORUMS-262 URL: http://jira.jboss.com/jira/browse/JBFORUMS-262 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Affects Versions: 1.0.1 RC Environment: Any Reporter: Luc Boudreau Assigned To: Ryszard Kozmik Priority: Critical Try to create a post, don't write anything as a subject or a body and press submit. The error message is totally useless. Message : org.jboss.portlet.forums.ui.action.MessageValidationException. Please try again Stack : 2007-11-05 15:41:35,075 ERROR [org.jboss.portlet.forums.ui.JSFUtil] org.jboss.po rtlet.forums.ui.JSFUtil org.jboss.portlet.forums.ui.action.MessageValidationException at org.jboss.portlet.forums.ui.action.PostAction.validateMessage(PostAct ion.java:561) at org.jboss.portlet.forums.ui.action.NewTopic.execute(NewTopic.java:118 ) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.el.parser.AstValue.invoke(AstValue.java:130) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.ja va:68) at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.ja va:69) at org.apache.myfaces.application.ActionListenerImpl.processAction(Actio nListenerImpl.java:63) at org.jboss.portlet.forums.auth.AuthorizationListener.processAction(Aut horizationListener.java:101) at javax.faces.component.UICommand.broadcast(UICommand.java:106) at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:9 0) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1 64) at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(Lifecycl eImpl.java:316) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java :86) at org.jboss.portlet.forums.ui.ForumsJSFPortlet.processAction(ForumsJSFP ortlet.java:281) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeActio n(PortletContainerImpl.java:458) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(Po rtletContainerImpl.java:401) at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(P ortletContainerInvoker.java:86) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.j ava:131) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jbos s$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(Transact ionInterceptor.java:106) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRe quired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103 964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java :195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRe quired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103 964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java :195) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-5118) different filetypes of packed JBoss AS

by Wolf-Dieter Fink (JIRA)

different filetypes of packed JBoss AS -------------------------------------- Key: JBAS-5118 URL: http://jira.jboss.com/jira/browse/JBAS-5118 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Installer Reporter: Wolf-Dieter Fink Assigned To: Amit Bhayani Priority: Minor The ZIPed archive include some times windows files sometimes unix files. Normally it dosn't matter, but if the files stored unpacked into a SCCS or transfered as text will change the '0D0A' to '0D0D0A'. This will produce some ERRORs like this: ERROR [StandardContext] Error in dependencyCheck java.io.IOException: invalid header field at java.util.jar.Attributes.read(Attributes.java:389) at java.util.jar.Manifest.read(Manifest.java:182) at java.util.jar.Manifest.<init>(Manifest.java:52) at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:149) JBoss 4.0.4.GA is delivered as UNIX and 4.2.0.GA/4.2.1 as WINDOWS. To avoid this the ZIP should delivered alway as UNIX files. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008