RE: FW: [JBoss-dev] configuration of interceptors
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bill
> Burke
> Sent: Thursday, September 12, 2002 6:33 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: FW: [JBoss-dev] configuration of interceptors
>
>
> Its more like
>
> DynamicProxy -> interceptor stack -> Target MBean
>
That should be easy with the stuff I just commited.
> There should be no concept of server or client.
>
> I also believe the interceptor chain, Aspect Oriented framework
> should be a
> generic framework and should work with any type of Object. It should be
> core to JMX. Sure, the MBeanDeployer could look at some XML and be the
> bridge between Aspects and MBeans, but lets keep Aspects a separate,
> lightweight framework.
It's currently implemented like that.. seperate nice and light weight. The
only dependency it currently has is on the org.jboss.proxy.compiler.*
package. So we could take my stuff and the org.jboss.proxy.compiler.* stuff
and make it and standalone module that can provide an interceptor stack to
any POJO.
+ this should run on 1.2 JVM since the Proxy classes are BECL generated.
>
> We have totaly freedom as far as MBean XML config files go, right?
>
> Here was my idea for an Aspect framework. I drew up the API while in
> Germany. The features were:
>
> - Interceptors could be services/singletons OR instantiated per chain.
My current implementation forces them to be singletons. But I don't think
this should be a major issue.
> - You could prepend or append an interceptor to the chain globally at
> runtime
> - You could prepend or append an interceptor to an individual chain.
So if you change a chain configuration when would it take effect on a proxy
that was using the previous configuration??
> - DynamicProxies would have a generic Aspect interface
I like the Aspect interface Idea.
>
>
>
> interface AspectManager
> {
> void createChain(String name);
> void registerInterceptorSingleton(String name, Interceptor interceptor);
>
> // These methods globally modify the chain of any Aspect in system with
> the given name
> void prependAspect(String chainname, String interceptorName,
> Class clazz,
> Element metadata);
> void appendAspect(String chainname, String interceptorName, Class clazz,
> Element metadata);
>
> void prependAspect(String chainname, String singletonName);
> void appendAspect(String chainname, String singletonName);
>
> void removeAspect(String chainname, String interceptorName);
>
>
> /**
>* Given any old object, make it Aspect Oriented.
>* metadata could hold InvocationContext-like information
>*/
> Aspect metamorphisis(String chainName, Class[] interfaces, Element
> metadata, Object targetObject);
>
> /**
>* No target object, useful for remote invocations.
>* metadata could hold InvocationContext-like information like
> MBean name
> to invoke on
>* and stuff like that.
>*/
> Aspect createAspect(String chainName, Class[] interfaces, Element
> metadata);
> }
>
> /**
> * Every DynamicProxy would implement this interface
> */
> interface Aspect
> {
>String getAspectName();
>
>/**
> * Allows you to detach this particular aspect
> */
>void setAspectName(String newName);
>
>Object[] getInterceptors();
>Interceptor findInterceptor(String name);
>
>Object getTargetObject();
>
> }
>
>
> So, XML would look something like this. An AspectChain MBean would create
> chains within the AspectManager. Add a new keyword to XML .
> This would give the deployer a reference to the name of the interceptor
> chain to use. The Deployer would create a Proxy via the
> AspectManager with
> this chain name and register this Proxy with the MBeanServer.
>
> name="MyMBean">
>
> jboss.AspectChains:name=SomeOldChain
>
>
> name="jboss.AspectChains:name=ClientProxyChain>
>
>
> name="Transaction"
> type="instance"
> class="org.jboss.proxy.TransactionInterceptor"
> />
>
>
>
>
>
Looks cool. I'll send you the javadocs for what I commited to CVS today.
My stuff is lacking on the JMX features. Anyways.. I'm glad we are all
exited about this kinda stuff.
Regards,
Hiram
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Hiram
> > Chirino
> > Sent: Thursday, September 12, 2002 2:25 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: FW: [JBoss-dev] configuration of interceptors
> >
> >
> >
> > Ok I imagine a client invocation chain will look like:
> >
> > clientproxy -> client-interceptor-stack ->
> > serverproxy -> server-interceptor-stack -> targetMbean
> >
> > Would doing some think like this satisfy you client-server
> requirments? :
> >
> > serverproxy = factory.createAspect("server-interceptor-stack",
> > targetMbean);
> > clientproxy = factory.createAspect("client-interceptor-stack",
>
RE: FW: [JBoss-dev] configuration of interceptors
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc
> fleury
> Sent: Thursday, September 12, 2002 3:55 PM
> To: 'Hiram Chirino'
> Cc: [EMAIL PROTECTED]
> Subject: RE: FW: [JBoss-dev] configuration of interceptors
>
>
> > Ok I imagine a client invocation chain will look like:
> >
> > clientproxy -> client-interceptor-stack ->
> > serverproxy -> server-interceptor-stack -> targetMbean
>
> not quite there is no typed serverproxy in the middle just a straight
> invoke() stack.
>
> The server/client nature just appear do to a invoker in the JBoss sense.
>
Yeah. I forgot.. David reminded me in his email.
>
> so...
>
> > Would doing some think like this satisfy you client-server
> > requirments? :
> >
> > serverproxy =
> > factory.createAspect("server-interceptor-stack",
> > targetMbean); clientproxy =
> > factory.createAspect("client-interceptor-stack", serverproxy
> > );
> >
>
> so... no that would be overkill as you introduce an additional Dynamic
> Proxy in the middle. Right now there are straight invoke().
>
right again.
> The point of the separation is that you may want travelling proxies and
> you may want inVM proxies all the time. While our client/server
> separation works today as inVM proxies (we have the EJB proxies working
> this way).
>
> It needs to be a construct in the factory whether you want distributable
> proxies or standalone. Note that the full client/server merged with no
> distribution would cover both cases however.
>
> > files. If we
> > provide a JMX interface to the factory so that you can
> > view/update stack
> > configurations, would that satisfy your requirement "to have
> > these puppies
> > manageable."
>
> It is a bit more deep than that. I am really looking for a central
> repository of that name-> configuration mapping and a way to interact
> with it, clearly JMX is the way to go and it needs to be centralized.
I thought thats kinda what I said. The Factory right now manages the
name->configuration mapping. We need and uber cool JMX MBean that allows us
to manipulate those configurations.
> Don't worry about it for now. Bill and I are thinking about that
> centralization. There also needs to be a callback in the interceptors
> for configuration changes. This dynamicity of configuration is
> completely missing from the current codebase and the EJB spec in
> general. This would take care of that.
You need to expand on this a little.. a small use case maybe.
>
> Gents I really think we got it this time. This is the end of our
> journey... the real AOP framework in JBoss. 10 years of industry
> dominance... a monopoly in the making
>
wow that gives me the tingles..
> marc f
> >
> > Regards,
> > Hiram
> >
> >
> > >From: "marc fleury" <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Subject: FW: [JBoss-dev] configuration of interceptors
> > >Date: Thu, 12 Sep 2002 13:44:03 -0400
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]] On
> > Behalf Of
> > > > marc fleury
> > > > Sent: Thursday, September 12, 2002 1:23 PM
> > > > To: 'Bill Burke'; 'juha lindfors'; 'Adrian Brock'
> > > > Cc: 'Hiram Chirino'; 'Jboss-Development@Lists. Sourceforge. Net'
> > > > Subject: [JBoss-dev] configuration of interceptors
> > > >
> > > >
> > > > Ok
> > > >
> > > > just had an interesting IM with hiram. He essentially has
> > > > implemented the proxy factory we were talking about. I
> > think he is
> > > > missing the client/server side of it but we can very simply add
> > > > these.
> > > >
> > > > Essentially it would revolve around a central
> > > > proxyFactory.createProxy(Interfaces[], client-interceptors[],
> > > > client-configurations[], server-interceptors[],
> > > > serverconfigurations[] targetMbean);
> > > >
> > > > that returns a Dynamic Proxy, hooked up for remote/local
> > calls with
> > > > client and server side interceptors. If you are in one
> > vm you can
> > > > safely assume client=server and only configure one or the other.
> > > > (meaning if one is null then don't configure transport it will be
> > > > invm
> > > > only)
> > > >
> > > > In the case of hiram he has only one aspect of it (and he
> > calls it
> > > > aspect everywhere) but that construct is really what we need. I
> > > > also think we should have the "MBean" in there, even
> > though we are
> > > > talking about a POJO.
> > > >
> > > > I believe he has solid code for it and I am really interested in
> > > > adding this to the base. I am not sure it is a JMX level
> > construct
> > > > (due to the pojo nature) but having the JMX base manage these
> > > > configurations and associations between target and
> > > > interceptors/configuration is the only sane way I can imagine to
> > > > have these puppies manageable. I want visibility on that
> > > > configuration for a given mbean (the generalized mbean
> > againg being
> > > > just a pojo or target). This is our g
RE: FW: [JBoss-dev] configuration of interceptors
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Jencks
> Sent: Thursday, September 12, 2002 3:24 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: FW: [JBoss-dev] configuration of interceptors
>
>
> I'm a little confused about one part of this...
>
> I thought the plan was to turn our current ejb interceptors into mbean
> interceptors and the Containers into fancy MBeanInvokers (If I remember
> correctly, anyway the top thing on the mbean interceptor stack). If this
> is correct, the ServerInterceptors would be behind the target
> MBean and not
> part of this new factory.
>
> This would look more like
> clientproxy -> client-interceptor-stack ->
> serverproxy -> targetMbean -> mbean-interceptor-stack
>
ya i think this is a better picture..
>
> In any case, I think all the stack factories should be mbeans as Hiram
> mentions.
>
> david jencks
>
>
> On 2002.09.12 14:25:25 -0400 Hiram Chirino wrote:
> >
> > Ok I imagine a client invocation chain will look like:
> >
> > clientproxy -> client-interceptor-stack ->
> > serverproxy -> server-interceptor-stack -> targetMbean
> >
> > Would doing some think like this satisfy you client-server
> requirments? :
> >
> > serverproxy = factory.createAspect("server-interceptor-stack",
> > targetMbean);
> > clientproxy = factory.createAspect("client-interceptor-stack",
> > serverproxy
> > );
> >
> > Please note: that "server-interceptor-stack" in essence will resolve to
> > a set of { server-interfaces[], server-interceptors[],
> > server-configurations[] }
> >
> > On another note, right now the factory that generates the proxys for say
> > the
> > "server-interceptor-stack", is configured through static xml files. If
> > we
> > provide a JMX interface to the factory so that you can
> view/update stack
> > configurations, would that satisfy your requirement "to have these
> > puppies
> > manageable."
> >
> > Regards,
> > Hiram
> >
> >
> > >From: "marc fleury" <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Subject: FW: [JBoss-dev] configuration of interceptors
> > >Date: Thu, 12 Sep 2002 13:44:03 -0400
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]] On
> > > > Behalf Of marc fleury
> > > > Sent: Thursday, September 12, 2002 1:23 PM
> > > > To: 'Bill Burke'; 'juha lindfors'; 'Adrian Brock'
> > > > Cc: 'Hiram Chirino'; 'Jboss-Development@Lists. Sourceforge. Net'
> > > > Subject: [JBoss-dev] configuration of interceptors
> > > >
> > > >
> > > > Ok
> > > >
> > > > just had an interesting IM with hiram. He essentially has
> > > > implemented the proxy factory we were talking about. I think
> > > > he is missing the client/server side of it but we can very
> > > > simply add these.
> > > >
> > > > Essentially it would revolve around a central
> > > > proxyFactory.createProxy(Interfaces[], client-interceptors[],
> > > > client-configurations[], server-interceptors[],
> > > > serverconfigurations[] targetMbean);
> > > >
> > > > that returns a Dynamic Proxy, hooked up for remote/local
> > > > calls with client and server side interceptors. If you are
> > > > in one vm you can safely assume client=server and only
> > > > configure one or the other. (meaning if one is null then
> > > > don't configure transport it will be invm
> > > > only)
> > > >
> > > > In the case of hiram he has only one aspect of it (and he
> > > > calls it aspect everywhere) but that construct is really what
> > > > we need. I also think we should have the "MBean" in there,
> > > > even though we are talking about a POJO.
> > > >
> > > > I believe he has solid code for it and I am really interested
> > > > in adding this to the base. I am not sure it is a JMX level
> > > > construct (due to the pojo nature) but having the JMX base
> > > > manage these configurations and associations between target
> > > > and interceptors/configuration is the only sane way I can
> > > > imagine to have these puppies manageable. I want visibility
> > > > on that configuration for a given mbean (the generalized
> > > > mbean againg being just a pojo or target). This is our generalized
> > > > proxy factory.
> > > >
> > > > The AOP framework of the future is staring us in the eye...
> > > > we got it.
> > > >
> > > > marc f
> > > >
> > > >
> > > > xx
> > > > Marc Fleury, Ph.D.
> > > > President, Founder
> > > > JBoss Group, LLC
> > > > xx
> > > >
> > > >
> > > >
> > > > ---
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Welcome to geek heaven.
> > > > http://thinkgeek.com/sf
> > > > ___
> > > > Jboss-development mailing list
> [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > >
> >
> >
> >
> >
> > _
> > Join the worlds larges
[JBoss-dev] JBoss 3.2?
What is the story with the 3.2 branch? Are we getting ready to release anytime soon? Or is 3.0.x going to remain mainstream for a while? --jason --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Improving the javagroups logging integration
Two issues I have with the current javagroups integration is that it is not configurable via log4j and it does not have enough logging of events. What can we do to improve this? Scott Stark Chief Technology Officer JBoss Group, LLC --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results: 13-September-2002
Number of tests run: 903 Successful tests: 873 Errors:26 Failures: 4 [time of test: 13 September 2002 2:26 GMT] [java.version: 1.3.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_03-b03] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-34] Useful resources: - http://lubega.com/testarchive/sun_jdk131_03 for the junit report of this test. - http://lubega.com/testarchive/sun_jdk131_03/logs/ for the logs for this test. - http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: FW: [JBoss-dev] configuration of interceptors
Its more like
DynamicProxy -> interceptor stack -> Target MBean
There should be no concept of server or client.
I also believe the interceptor chain, Aspect Oriented framework should be a
generic framework and should work with any type of Object. It should be
core to JMX. Sure, the MBeanDeployer could look at some XML and be the
bridge between Aspects and MBeans, but lets keep Aspects a separate,
lightweight framework.
We have totaly freedom as far as MBean XML config files go, right?
Here was my idea for an Aspect framework. I drew up the API while in
Germany. The features were:
- Interceptors could be services/singletons OR instantiated per chain.
- You could prepend or append an interceptor to the chain globally at
runtime
- You could prepend or append an interceptor to an individual chain.
- DynamicProxies would have a generic Aspect interface
interface AspectManager
{
void createChain(String name);
void registerInterceptorSingleton(String name, Interceptor interceptor);
// These methods globally modify the chain of any Aspect in system with
the given name
void prependAspect(String chainname, String interceptorName, Class clazz,
Element metadata);
void appendAspect(String chainname, String interceptorName, Class clazz,
Element metadata);
void prependAspect(String chainname, String singletonName);
void appendAspect(String chainname, String singletonName);
void removeAspect(String chainname, String interceptorName);
/**
* Given any old object, make it Aspect Oriented.
* metadata could hold InvocationContext-like information
*/
Aspect metamorphisis(String chainName, Class[] interfaces, Element
metadata, Object targetObject);
/**
* No target object, useful for remote invocations.
* metadata could hold InvocationContext-like information like MBean name
to invoke on
* and stuff like that.
*/
Aspect createAspect(String chainName, Class[] interfaces, Element
metadata);
}
/**
* Every DynamicProxy would implement this interface
*/
interface Aspect
{
String getAspectName();
/**
* Allows you to detach this particular aspect
*/
void setAspectName(String newName);
Object[] getInterceptors();
Interceptor findInterceptor(String name);
Object getTargetObject();
}
So, XML would look something like this. An AspectChain MBean would create
chains within the AspectManager. Add a new keyword to XML .
This would give the deployer a reference to the name of the interceptor
chain to use. The Deployer would create a Proxy via the AspectManager with
this chain name and register this Proxy with the MBeanServer.
jboss.AspectChains:name=SomeOldChain
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Hiram
> Chirino
> Sent: Thursday, September 12, 2002 2:25 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: FW: [JBoss-dev] configuration of interceptors
>
>
>
> Ok I imagine a client invocation chain will look like:
>
> clientproxy -> client-interceptor-stack ->
> serverproxy -> server-interceptor-stack -> targetMbean
>
> Would doing some think like this satisfy you client-server requirments? :
>
> serverproxy = factory.createAspect("server-interceptor-stack",
> targetMbean);
> clientproxy = factory.createAspect("client-interceptor-stack",
> serverproxy
> );
>
> Please note: that "server-interceptor-stack" in essence will resolve to
> a set of { server-interfaces[], server-interceptors[],
> server-configurations[] }
>
> On another note, right now the factory that generates the proxys
> for say the
> "server-interceptor-stack", is configured through static xml
> files. If we
> provide a JMX interface to the factory so that you can view/update stack
> configurations, would that satisfy your requirement "to have
> these puppies
> manageable."
>
> Regards,
> Hiram
>
>
> >From: "marc fleury" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: FW: [JBoss-dev] configuration of interceptors
> >Date: Thu, 12 Sep 2002 13:44:03 -0400
> >
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]] On
> > > Behalf Of marc fleury
> > > Sent: Thursday, September 12, 2002 1:23 PM
> > > To: 'Bill Burke'; 'juha lindfors'; 'Adrian Brock'
> > > Cc: 'Hiram Chirino'; 'Jboss-Development@Lists. Sourceforge. Net'
> > > Subject: [JBoss-dev] configuration of interceptors
> > >
> > >
> > > Ok
> > >
> > > just had an interesting IM with hiram. He essentially has
> > > implemented the proxy factory we were talking about. I think
> > > he is missing the client/server side of it but we can very
> > > simply add these.
> > >
> > > Essentially it would revolve around a central
> > > proxyFactory.createProxy(Interfaces[], client-interceptors[],
> > > client-configurations[], server-interceptors[],
> > > serverconfigurations[] targetMbean);
> > >
> > > that returns a Dynamic Proxy, hooked up for rem
[JBoss-dev] [ jboss-Bugs-608720 ] J2EE EJB Compat with J2EE SDK Server
Bugs item #608720, was opened at 2002-09-13 13:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608720&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Anthony Ikeda (akikeda) Assigned to: Nobody/Anonymous (nobody) Summary: J2EE EJB Compat with J2EE SDK Server Initial Comment: When running the build template supplied with the JBoss examples pack, the generated Home and remote interfaces have some compatibility problems when deploying the same ejb.jar on the Sun J2EE SDK server (problem with valid RMI-IIOP types). See the TestCase.txt contained in the jar file for more details. NOTE: This jar is only an archive of non-java files not a java executable. Anthony -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608720&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600800 ] XA Resources not enlisted in UserTransac
Bugs item #600800, was opened at 2002-08-27 09:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600800&group_id=22866 >Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Brian Johnson (johnsbrn) Assigned to: Nobody/Anonymous (nobody) Summary: XA Resources not enlisted in UserTransac Initial Comment: In jboss 3.x, jdk1.4 on W2K, when a transaction is started in a Servlet using the UserTransaction interface, XA resources aquired in new threads created by the servlet are not enlisted in the transaction. J2EE.4.2.3 Transactions and Threads There are many subtle and complex interactions between the use of transactional resources and threads. To ensure correct operation, web components should obey the following guidelines, and the web container must support at least these usages. JTA transactions should be started and completed in the thread in which the service method is called. Additional threads that are created for any purpose, should not attempt to start JTA transactions. Transactional resources may be acquired and released by a thread other than the service method thread, but should not be shared between threads. I have attached a simple war file that demonstrates the problem. In this case, the insert statement in the service thread is rolled back, but the insert in the TestThread is not. I have tested this with the standard jboss transaction service and tyrex and the result is the same in both. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600800&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-608729 ] Deployment fails if no env-entry-value
Bugs item #608729, was opened at 2002-09-13 11:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608729&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Fui Shien, Choong (fschoong) Assigned to: Nobody/Anonymous (nobody) Summary: Deployment fails if no env-entry-value Initial Comment: Win2k Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_04-b02) org.jboss.deployment.DeploymentException: Error in ejb- jar.xml for Session Bean MessageFacade: expected one env-entry-value tag at org.jboss.metadata.ApplicationMetaData.importEjbJarXm l(ApplicationMetaData.java:207) I defined with a session bean with the following env- entry. According to http://java.sun.com/j2ee/dtds/ejb- jar_1_1.dtd, env-entry-value is optional, it should not fail if its not specified, or did i get it wrong??? sequenceTableName java.lang.String -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608729&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-608202 ] EJBQL fails to compile
Bugs item #608202, was opened at 2002-09-12 15:30
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608202&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Cory Prowse (cosmic)
Assigned to: Dain Sundstrom (dsundstrom)
Summary: EJBQL fails to compile
Initial Comment:
OS:
Linux (2.4 kernel)
JDK:
java version "1.4.0_01"
Java(TM) 2 Runtime Environment, Standard Edition
(build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03,
mixed mode)
JBoss Release:
JBoss-3.0.2 CVSTag=JBoss_3_0_2
NOTE: I will try and cut out a test case but it may
take a few days (deadline). A workaround is to use
OBJECT() and get the field that way.
When I attempt the following EJBQL:
ejbSelectCargoValue
packet.interfaces.PacketEntityLocal
java.lang.String
[CDATA[SELECT c.value FROM PacketEntity p, IN
(p.cargoes) AS c WHERE p = ?1 AND c.name = ?2]]
I get the following exception:
org.jboss.deployment.DeploymentException: Error
compiling ejbql; - nested throwable:
(java.lang.IllegalStateException: Can not visit
multi-column path node. Should have been handled at a
higher level.)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.(JDBCEJBQLQuery.java:46)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:44)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:214)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:463)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:369)
at
org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:198)
--
>Comment By: Cory Prowse (cosmic)
Date: 2002-09-13 11:05
Message:
Logged In: YES
user_id=32851
The Entity beans in question have the following structure:
Packet {
long: packetId
}
Cargo {
long: cargoId
String: name
Object: value
}
With a relationship of one to many (Packet contains many
cargoes).
The Packet also has two other relationships set up with two
other Entities but they are not currently used (the HQSQLDB
has two other Foreign Key columns within the Packet table as
well). I'm not sure if that could be the cause of the issue
though... just letting you know the full details.
I can post the excerpts from the ejb-jar.xml?
--
Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-09-13 03:39
Message:
Logged In: YES
user_id=251431
What is the type of c.value? Is it a mapped dependent value
class?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608202&group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600647 ] Interrupted while requesting permit!
Bugs item #600647, was opened at 2002-08-27 16:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600647&group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) Assigned to: Jules Gosnell (jules_gosnell) Summary: Interrupted while requesting permit! Initial Comment: This is a reminder to roll in the fix for this (apparently Jetty) problem into Branch_3_0 from 3.2/4.0. Sample exception dump appears below: 2002-08-27 15:33:27,320 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Priv.findForUs er] Find failed org.jboss.util.NestedSQLException: Interrupted while requesting permit!; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit!) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnec tion(LocalDataSource.java:106) at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.exe cute(JDBCAbstractQueryCommand.java:92) at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute (JDBCFindEntityCommand.java:44) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDB CStoreManager.java:541) at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPer sistenceManager.java:336) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.findEntity(CachedConnectionInterceptor.java:301) at org.jboss.ejb.EntityContainer.find(EntityContainer.java:687) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(E ntityContainer.java:1116) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInte rceptor.java:73) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHom e(EntitySynchronizationInterceptor.java:209) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.invokeHome(CachedConnectionInterceptor.java:215) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(Entity InstanceInterceptor.java:88) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLoc kInterceptor.java:79) at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(Entity CreationInterceptor.java:44) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractT xInterceptor.java:111) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInt erceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptor CMT.java:52) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInte rceptor.java:105) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.ja va:129) at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:48 7) at org.jboss.ejb.Container.invoke(Container.java:738) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.j ava:517) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:9 8) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.j ava:102) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercep tor.java:73) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.jav a:76) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java: 198) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) at $Proxy396.findForUser(Unknown Source) at com.whitesmiths.sacha.web.common.PrivChecker.checkPrivStat us(PrivChecker.java:370) at com.whitesmiths.sacha.web.common.Utilities.checkAccessSettin gs(Utilities.java:238) at com.whitesmiths.sacha.web.tagsupport.CheckPrivTag.doStartTag (CheckPrivTag.java:83) at org.apache.jsp.listWorklists$jsp._jspService(listWorklists$jsp.java :89) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java :107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service( JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.ja va:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 344) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApp licationHandler.java:313) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.jav a:554) at org.mortbay.jetty.servlet.WebApplicationHandler.handle(WebAppli cationHandler.java:199) at org.mortbay.http.HttpContext.handle(HttpContext.java:1572) at org.mortbay.http.Htt
Re: [JBoss-dev] 3.2.0RC1 Missing org.jboss.invocation.Invocation class in minimal target
Try it again. I fixed it yesterday. server 688>jar -tf output/lib/jboss-minimal.jar | grep invo org/jboss/invocation/ org/jboss/invocation/http/ org/jboss/invocation/jrmp/ org/jboss/invocation/local/ org/jboss/invocation/Invocation.class org/jboss/invocation/InvocationContext.class org/jboss/invocation/InvocationKey.class org/jboss/invocation/InvocationType.class org/jboss/invocation/Invoker.class org/jboss/invocation/InvokerInterceptor.class org/jboss/invocation/MarshalledInvocation.class org/jboss/invocation/MarshalledValue.class org/jboss/invocation/MarshalledValueInputStream.class org/jboss/invocation/MarshalledValueOutputStream.class org/jboss/invocation/PayloadKey.class Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Barlow, Dustin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 12, 2002 10:18 AM Subject: [JBoss-dev] 3.2.0RC1 Missing org.jboss.invocation.Invocation class in minimal target > Has anyone tried running the "minimal" target built from CVS Branch_3_2? > > I tried it and get the following: > > > === > . > JBoss Bootstrap Environment > . > JBOSS_HOME: c:\java\jboss-3.2.0RC1\bin\\.. > . > JAVA: c:\java\jdk1.3.1_04\bin\java > . > JAVA_OPTS: -Dprogram.name=run.bat > . > CLASSPATH: > ;c:\java\jdk1.3.1_04\lib\tools.jar;c:\java\jboss-3.2.0RC1\bin\\run.jar > . > > === > . > 13:13:16,901 INFO [Server] Starting JBoss (MX MicroKernel)... > 13:13:16,901 INFO [Server] Release ID: JBoss [WonderLand] 3.2.0RC1 (build: > Branch_3_2 200209111458) > 13:13:16,917 INFO [Server] Home Dir: C:\java\jboss-3.2.0RC1 > 13:13:16,917 INFO [Server] Home URL: file:/C:/java/jboss-3.2.0RC1/ > 13:13:16,917 INFO [Server] Library URL: file:/C:/java/jboss-3.2.0RC1/lib/ > 13:13:16,917 INFO [Server] Patch URL: null > 13:13:16,917 INFO [Server] Server Name: minimal > 13:13:16,917 INFO [Server] Server Home Dir: > C:\java\jboss-3.2.0RC1\server\minimal > 13:13:16,917 INFO [Server] Server Home URL: > file:/C:/java/jboss-3.2.0RC1/server/minimal/ > 13:13:16,917 INFO [Server] Server Data Dir: > C:\java\jboss-3.2.0RC1\server\minimal\data > 13:13:16,917 INFO [Server] Server Temp Dir: > C:\java\jboss-3.2.0RC1\server\minimal\tmp > 13:13:16,917 INFO [Server] Server Config URL: > file:/C:/java/jboss-3.2.0RC1/server/minimal/conf/ > 13:13:16,917 INFO [Server] Server Library URL: > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/ > 13:13:16,917 INFO [Server] Root Deployemnt Filename: jboss-service.xml > 13:13:16,933 INFO [Server] Starting General Purpose Architecture (GPA)... > 13:13:17,214 INFO [ServerInfo] Java version: 1.3.1_04,Sun Microsystems Inc. > 13:13:17,214 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM > 1.3.1_04-b02,Sun Microsystems Inc. > 13:13:17,214 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86 > 13:13:17,245 INFO [ServiceController] Controller MBean online > 13:13:17,323 INFO [MainDeployer] Creating > 13:13:17,339 INFO [MainDeployer] Created > 13:13:17,339 INFO [MainDeployer] Starting > 13:13:17,339 INFO [MainDeployer] Started > 13:13:17,417 INFO [JARDeployer] Creating > 13:13:17,448 INFO [JARDeployer] Created > 13:13:17,448 INFO [JARDeployer] Starting > 13:13:17,448 INFO [MainDeployer] Adding deployer: > org.jboss.deployment.JARDeployer@1edf4 > 13:13:17,448 INFO [JARDeployer] Started > 13:13:17,464 INFO [SARDeployer] Creating > 13:13:17,480 INFO [SARDeployer] Created > 13:13:17,480 INFO [SARDeployer] Starting > 13:13:17,480 INFO [MainDeployer] Adding deployer: > org.jboss.deployment.SARDeployer@66a22b > 13:13:17,495 INFO [SARDeployer] Started > 13:13:17,495 INFO [Server] Core system initialized > 13:13:17,511 INFO [MainDeployer] Starting deployment of package: > file:/C:/java/jboss-3.2.0RC1/server/minimal/conf/jboss-service.xml > 13:13:17,933 INFO [MainDeployer] Starting deployment of package: > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jboss-minimal.jar > 13:13:17,948 INFO [JARDeployer] looking for nested deployments in : > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jboss-minimal.jar > 13:13:17,964 INFO [MainDeployer] Deployed package: > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jboss-minimal.jar > 13:13:17,964 INFO [MainDeployer] Starting deployment of package: > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnpserver.jar > 13:13:17,964 INFO [JARDeployer] looking for nested deployments in : > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnpserver.jar > 13:13:17,980 INFO [MainDeployer] Deployed package: > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnpserver.jar > 13:13:17,980 INFO [MainDeployer] Starting deployment of package: > file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/log4j.jar > 13:13:18,058 INFO [JARDeployer] looking for nested deployments in : > file:/C:
Re: [JBoss-dev] Dynamic configuration of XMLLoginConfig
Well, add to that: its is somethimes much better to be able to specify the auth XML in the *-service.xml file and not have to have an external file to load, this could ofcourse be fixed easilly by letting XMLLoginConfig also take an Element to be set up from. //Peter On 12 Sep, Scott M Stark wrote: > There is a service that does this in the testsuite. XMLLoginConfigs chain so > that multiple configs can be active. > > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > - Original Message - > From: "Peter Antman" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 12, 2002 8:03 AM > Subject: [JBoss-dev] Dynamic configuration of XMLLoginConfig > > >> Hi, >> when converting some old adapters I had finally the chance to look at >> the new JAAS based autentication stuff for JCA adapters. Really neat. >> But one thing is somewhat iritating. It is not possible to configure a >> new adapter and hot deploy it. At least I could not figure out a >> standard way of doing it. Why? Because the new autentication scheme is >> dependand on the availability of a security realm in login-config.xml. >> To do this you have to restart the server. >> >> To solve this I wrote I little MBean to dynamically configure the >> XMLLoginConfig. Basically it let you set the real setting in the same >> *-service.xml file as you configure your adapter, ie: >> >> > code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" >name="jboss.jca:service=LocalTxCM,name=PostgresDS"> >> >> > code="org.jboss.resource.security.LoginConfigurator" >name="jboss.jca:service=AuthenticationInfo,name=PostgresDS"> >>optional-attribute-name="LoginConfig">jboss.security:service=XMLLoginConfig >> >> >> >> "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required"> >>yourprincipal >>yourusername >>yourpassword >> >"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=PostgresDS >> >> >> >> >> >> >> bla,bla... >> >> I don't know if this goes agains some security restrictions (apart from >> it probably not working with a security manager installed and the >> correct right sto do this sort of stuff is not turned of). >> >> Basically I am wondering this: any interest in me checking this >> little utility class in (and perhaps refactor XMLLoginConfig so that the >> XML parsing code does not need to be in two places)? Any ideas about >> which is the best place? org.jboss.resource.security or >> org.jboss.security.auth.login or perhaps not at all, what do you say >> Scott? >> >> //Peter >> -- >> >> Peter Antman Chief Systems Architect, Business Development >> Technology in Media, Box 34105 100 26 Stockholm >> WWW: http://www.tim.se WWW: http://www.backsource.org >> Email: [EMAIL PROTECTED] >> Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 >> >> >> >> >> --- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> ___ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Peter Antman Technology in Media, Box 34105 100 26 Stockholm Systems ArchitectWWW: http://www.tim.se Email: [EMAIL PROTECTED]WWW: http://www.backsource.org Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 12-September-2002
Number of tests run: 934
Successful tests: 924
Errors:4
Failures: 6
[time of test: 12 September 2002 12:44 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1_03-69]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.2]
See http://lubega.com/testarchive/${build.uid} for details of this test.
See http://lubega.com for general test information.
NOTE: If there are any errors shown above - this mail is only highlighting
them - it is NOT indicating that they are being looked at by anyone.
Remember - if a test becomes broken after your changes - fix it or fix the test!
Oh dear - still got some errors!
Thanks for all your effort - we really do love you!
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: FW: [JBoss-dev] configuration of interceptors
> Ok I imagine a client invocation chain will look like:
>
> clientproxy -> client-interceptor-stack ->
> serverproxy -> server-interceptor-stack -> targetMbean
not quite there is no typed serverproxy in the middle just a straight
invoke() stack.
The server/client nature just appear do to a invoker in the JBoss sense.
so...
> Would doing some think like this satisfy you client-server
> requirments? :
>
> serverproxy =
> factory.createAspect("server-interceptor-stack",
> targetMbean); clientproxy =
> factory.createAspect("client-interceptor-stack", serverproxy
> );
>
so... no that would be overkill as you introduce an additional Dynamic
Proxy in the middle. Right now there are straight invoke().
The point of the separation is that you may want travelling proxies and
you may want inVM proxies all the time. While our client/server
separation works today as inVM proxies (we have the EJB proxies working
this way).
It needs to be a construct in the factory whether you want distributable
proxies or standalone. Note that the full client/server merged with no
distribution would cover both cases however.
> files. If we
> provide a JMX interface to the factory so that you can
> view/update stack
> configurations, would that satisfy your requirement "to have
> these puppies
> manageable."
It is a bit more deep than that. I am really looking for a central
repository of that name-> configuration mapping and a way to interact
with it, clearly JMX is the way to go and it needs to be centralized.
Don't worry about it for now. Bill and I are thinking about that
centralization. There also needs to be a callback in the interceptors
for configuration changes. This dynamicity of configuration is
completely missing from the current codebase and the EJB spec in
general. This would take care of that.
Gents I really think we got it this time. This is the end of our
journey... the real AOP framework in JBoss. 10 years of industry
dominance... a monopoly in the making
marc f
>
> Regards,
> Hiram
>
>
> >From: "marc fleury" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: FW: [JBoss-dev] configuration of interceptors
> >Date: Thu, 12 Sep 2002 13:44:03 -0400
> >
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]] On
> Behalf Of
> > > marc fleury
> > > Sent: Thursday, September 12, 2002 1:23 PM
> > > To: 'Bill Burke'; 'juha lindfors'; 'Adrian Brock'
> > > Cc: 'Hiram Chirino'; 'Jboss-Development@Lists. Sourceforge. Net'
> > > Subject: [JBoss-dev] configuration of interceptors
> > >
> > >
> > > Ok
> > >
> > > just had an interesting IM with hiram. He essentially has
> > > implemented the proxy factory we were talking about. I
> think he is
> > > missing the client/server side of it but we can very simply add
> > > these.
> > >
> > > Essentially it would revolve around a central
> > > proxyFactory.createProxy(Interfaces[], client-interceptors[],
> > > client-configurations[], server-interceptors[],
> > > serverconfigurations[] targetMbean);
> > >
> > > that returns a Dynamic Proxy, hooked up for remote/local
> calls with
> > > client and server side interceptors. If you are in one
> vm you can
> > > safely assume client=server and only configure one or the other.
> > > (meaning if one is null then don't configure transport it will be
> > > invm
> > > only)
> > >
> > > In the case of hiram he has only one aspect of it (and he
> calls it
> > > aspect everywhere) but that construct is really what we need. I
> > > also think we should have the "MBean" in there, even
> though we are
> > > talking about a POJO.
> > >
> > > I believe he has solid code for it and I am really interested in
> > > adding this to the base. I am not sure it is a JMX level
> construct
> > > (due to the pojo nature) but having the JMX base manage these
> > > configurations and associations between target and
> > > interceptors/configuration is the only sane way I can imagine to
> > > have these puppies manageable. I want visibility on that
> > > configuration for a given mbean (the generalized mbean
> againg being
> > > just a pojo or target). This is our generalized proxy factory.
> > >
> > > The AOP framework of the future is staring us in the
> eye... we got
> > > it.
> > >
> > > marc f
> > >
> > >
> > > xx
> > > Marc Fleury, Ph.D.
> > > President, Founder
> > > JBoss Group, LLC
> > > xx
> > >
> > >
> > >
> > > ---
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > ___
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
>
>
>
>
> _
> Join the world's largest e-mail service with MSN Hotma
Re: [JBoss-dev] Dynamic configuration of XMLLoginConfig
On 12 Sep, Scott M Stark wrote: > There is a service that does this in the testsuite. XMLLoginConfigs chain so > that multiple configs can be active. Ah, that was a neat one, but one thing I do not get: say the mysql-service.xml is installed and uses this scheme to install a new "root" config with the old one as parent. Then postgres-service.xmlis installed with yet another Configuration, now with the mysql one as its parent. What happend if I uninstall mysql-service, will not the postgres config the be poped? I would really like to be able to remove a configuration by name. There must be something I don't understand here. Anyway, i think it would be nice with a service in the core (security/resource) which can ad and remove a named application-policy/security realm. Either my way ( by invoking addAppConfig on XMLLoginConfig), or your way - wich in many ways is better since it (at least not directly) do not need to know that it is using XMLLoginConfig. What do you say? //Peter > > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > - Original Message - > From: "Peter Antman" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 12, 2002 8:03 AM > Subject: [JBoss-dev] Dynamic configuration of XMLLoginConfig > > >> Hi, >> when converting some old adapters I had finally the chance to look at >> the new JAAS based autentication stuff for JCA adapters. Really neat. >> But one thing is somewhat iritating. It is not possible to configure a >> new adapter and hot deploy it. At least I could not figure out a >> standard way of doing it. Why? Because the new autentication scheme is >> dependand on the availability of a security realm in login-config.xml. >> To do this you have to restart the server. >> >> To solve this I wrote I little MBean to dynamically configure the >> XMLLoginConfig. Basically it let you set the real setting in the same >> *-service.xml file as you configure your adapter, ie: >> >> > code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" >name="jboss.jca:service=LocalTxCM,name=PostgresDS"> >> >> > code="org.jboss.resource.security.LoginConfigurator" >name="jboss.jca:service=AuthenticationInfo,name=PostgresDS"> >>optional-attribute-name="LoginConfig">jboss.security:service=XMLLoginConfig >> >> >> >> "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required"> >>yourprincipal >>yourusername >>yourpassword >> >"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=PostgresDS >> >> >> >> >> >> >> bla,bla... >> >> I don't know if this goes agains some security restrictions (apart from >> it probably not working with a security manager installed and the >> correct right sto do this sort of stuff is not turned of). >> >> Basically I am wondering this: any interest in me checking this >> little utility class in (and perhaps refactor XMLLoginConfig so that the >> XML parsing code does not need to be in two places)? Any ideas about >> which is the best place? org.jboss.resource.security or >> org.jboss.security.auth.login or perhaps not at all, what do you say >> Scott? >> >> //Peter >> -- >> >> Peter Antman Chief Systems Architect, Business Development >> Technology in Media, Box 34105 100 26 Stockholm >> WWW: http://www.tim.se WWW: http://www.backsource.org >> Email: [EMAIL PROTECTED] >> Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 >> >> >> >> >> --- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> ___ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Peter Antman Technology in Media, Box 34105 100 26 Stockholm Systems ArchitectWWW: http://www.tim.se Email: [EMAIL PROTECTED]WWW: http://www.backsource.org Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. h
Re: FW: [JBoss-dev] configuration of interceptors
I'm a little confused about one part of this...
I thought the plan was to turn our current ejb interceptors into mbean
interceptors and the Containers into fancy MBeanInvokers (If I remember
correctly, anyway the top thing on the mbean interceptor stack). If this
is correct, the ServerInterceptors would be behind the target MBean and not
part of this new factory.
This would look more like
clientproxy -> client-interceptor-stack ->
serverproxy -> targetMbean -> mbean-interceptor-stack
In any case, I think all the stack factories should be mbeans as Hiram
mentions.
david jencks
On 2002.09.12 14:25:25 -0400 Hiram Chirino wrote:
>
> Ok I imagine a client invocation chain will look like:
>
> clientproxy -> client-interceptor-stack ->
> serverproxy -> server-interceptor-stack -> targetMbean
>
> Would doing some think like this satisfy you client-server requirments? :
>
> serverproxy = factory.createAspect("server-interceptor-stack",
> targetMbean);
> clientproxy = factory.createAspect("client-interceptor-stack",
> serverproxy
> );
>
> Please note: that "server-interceptor-stack" in essence will resolve to
> a set of { server-interfaces[], server-interceptors[],
> server-configurations[] }
>
> On another note, right now the factory that generates the proxys for say
> the
> "server-interceptor-stack", is configured through static xml files. If
> we
> provide a JMX interface to the factory so that you can view/update stack
> configurations, would that satisfy your requirement "to have these
> puppies
> manageable."
>
> Regards,
> Hiram
>
>
> >From: "marc fleury" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: FW: [JBoss-dev] configuration of interceptors
> >Date: Thu, 12 Sep 2002 13:44:03 -0400
> >
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]] On
> > > Behalf Of marc fleury
> > > Sent: Thursday, September 12, 2002 1:23 PM
> > > To: 'Bill Burke'; 'juha lindfors'; 'Adrian Brock'
> > > Cc: 'Hiram Chirino'; 'Jboss-Development@Lists. Sourceforge. Net'
> > > Subject: [JBoss-dev] configuration of interceptors
> > >
> > >
> > > Ok
> > >
> > > just had an interesting IM with hiram. He essentially has
> > > implemented the proxy factory we were talking about. I think
> > > he is missing the client/server side of it but we can very
> > > simply add these.
> > >
> > > Essentially it would revolve around a central
> > > proxyFactory.createProxy(Interfaces[], client-interceptors[],
> > > client-configurations[], server-interceptors[],
> > > serverconfigurations[] targetMbean);
> > >
> > > that returns a Dynamic Proxy, hooked up for remote/local
> > > calls with client and server side interceptors. If you are
> > > in one vm you can safely assume client=server and only
> > > configure one or the other. (meaning if one is null then
> > > don't configure transport it will be invm
> > > only)
> > >
> > > In the case of hiram he has only one aspect of it (and he
> > > calls it aspect everywhere) but that construct is really what
> > > we need. I also think we should have the "MBean" in there,
> > > even though we are talking about a POJO.
> > >
> > > I believe he has solid code for it and I am really interested
> > > in adding this to the base. I am not sure it is a JMX level
> > > construct (due to the pojo nature) but having the JMX base
> > > manage these configurations and associations between target
> > > and interceptors/configuration is the only sane way I can
> > > imagine to have these puppies manageable. I want visibility
> > > on that configuration for a given mbean (the generalized
> > > mbean againg being just a pojo or target). This is our generalized
> > > proxy factory.
> > >
> > > The AOP framework of the future is staring us in the eye...
> > > we got it.
> > >
> > > marc f
> > >
> > >
> > > xx
> > > Marc Fleury, Ph.D.
> > > President, Founder
> > > JBoss Group, LLC
> > > xx
> > >
> > >
> > >
> > > ---
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > ___
> > > Jboss-development mailing list [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
>
>
>
>
> _
> Join the worlds largest e-mail service with MSN Hotmail.
> http://www.hotmail.com
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgee
[JBoss-dev] [ jboss-Bugs-600435 ] deadlock detected erroneously
Bugs item #600435, was opened at 2002-08-26 20:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600435&group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole >Status: Closed Resolution: Invalid Priority: 5 Submitted By: Kyle Downey (kdowney) Assigned to: Bill Burke (patriot1burke) Summary: deadlock detected erroneously Initial Comment: I have a session bean method calling a CMP Entity method. They are set up as follows in terms of transactions: KeySequence getNextKeyAfterIncrementingBy RequiresNew commonsvc/KeyGenerator * Required The session call successfully creates the Entity EJB, but the second call (to actually use the newly-created Entity) from the same client, in what I would assume is the same transaction, fails with this exception: Caused by: org.jboss.ejb.plugins.lock.ApplicationDeadlockException : Application deadlock detected: Current thread already has tx lock in different transaction. at org.jboss.ejb.plugins.lock.BeanLockSupport.deadlockDet ection(BeanLock Support.java:182) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.w aitForTx(QueuedP essimisticEJBLock.java:283) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.d oSchedule(Queued PessimisticEJBLock.java:189) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.s chedule(QueuedPe ssimisticEJBLock.java:140) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockIntercep tor.java:103) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreation Interceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInte rceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxIntercep torCMT.java:255) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:6 0) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor. java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv oke(BaseLoca lContainerInvoker.java:301) at org.jboss.ejb.plugins.local.EntityProxy.invoke (EntityProxy.java:38) Note that this is triggered by a single call to the session EJB from a single client (a unit test), so it should not be possible to create deadlock. Database: Postgresql JVM: JDK 1.3.1_03 (Sun) JBoss: 3.0.1 --kd -- >Comment By: Kyle Downey (kdowney) Date: 2002-09-12 18:37 Message: Logged In: YES user_id=17198 Yes, you are right. I had the declaration backward. -- Comment By: Bill Burke (patriot1burke) Date: 2002-09-12 17:56 Message: Logged In: YES user_id=176497 This bug is invalid. You have accessed the bean in a transaction then you called a RequiresNew method. So you will have deadlock. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600435&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: FW: [JBoss-dev] configuration of interceptors
Ok I imagine a client invocation chain will look like:
clientproxy -> client-interceptor-stack ->
serverproxy -> server-interceptor-stack -> targetMbean
Would doing some think like this satisfy you client-server requirments? :
serverproxy = factory.createAspect("server-interceptor-stack", targetMbean);
clientproxy = factory.createAspect("client-interceptor-stack", serverproxy
);
Please note: that "server-interceptor-stack" in essence will resolve to
a set of { server-interfaces[], server-interceptors[],
server-configurations[] }
On another note, right now the factory that generates the proxys for say the
"server-interceptor-stack", is configured through static xml files. If we
provide a JMX interface to the factory so that you can view/update stack
configurations, would that satisfy your requirement "to have these puppies
manageable."
Regards,
Hiram
>From: "marc fleury" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: FW: [JBoss-dev] configuration of interceptors
>Date: Thu, 12 Sep 2002 13:44:03 -0400
>
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On
> > Behalf Of marc fleury
> > Sent: Thursday, September 12, 2002 1:23 PM
> > To: 'Bill Burke'; 'juha lindfors'; 'Adrian Brock'
> > Cc: 'Hiram Chirino'; 'Jboss-Development@Lists. Sourceforge. Net'
> > Subject: [JBoss-dev] configuration of interceptors
> >
> >
> > Ok
> >
> > just had an interesting IM with hiram. He essentially has
> > implemented the proxy factory we were talking about. I think
> > he is missing the client/server side of it but we can very
> > simply add these.
> >
> > Essentially it would revolve around a central
> > proxyFactory.createProxy(Interfaces[], client-interceptors[],
> > client-configurations[], server-interceptors[],
> > serverconfigurations[] targetMbean);
> >
> > that returns a Dynamic Proxy, hooked up for remote/local
> > calls with client and server side interceptors. If you are
> > in one vm you can safely assume client=server and only
> > configure one or the other. (meaning if one is null then
> > don't configure transport it will be invm
> > only)
> >
> > In the case of hiram he has only one aspect of it (and he
> > calls it aspect everywhere) but that construct is really what
> > we need. I also think we should have the "MBean" in there,
> > even though we are talking about a POJO.
> >
> > I believe he has solid code for it and I am really interested
> > in adding this to the base. I am not sure it is a JMX level
> > construct (due to the pojo nature) but having the JMX base
> > manage these configurations and associations between target
> > and interceptors/configuration is the only sane way I can
> > imagine to have these puppies manageable. I want visibility
> > on that configuration for a given mbean (the generalized
> > mbean againg being just a pojo or target). This is our generalized
> > proxy factory.
> >
> > The AOP framework of the future is staring us in the eye...
> > we got it.
> >
> > marc f
> >
> >
> > xx
> > Marc Fleury, Ph.D.
> > President, Founder
> > JBoss Group, LLC
> > xx
> >
> >
> >
> > ---
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > ___
> > Jboss-development mailing list [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
_
Join the worlds largest e-mail service with MSN Hotmail.
http://www.hotmail.com
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600647 ] Interrupted while requesting permit!
Bugs item #600647, was opened at 2002-08-27 06:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600647&group_id=22866 >Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) >Assigned to: Jules Gosnell (jules_gosnell) Summary: Interrupted while requesting permit! Initial Comment: This is a reminder to roll in the fix for this (apparently Jetty) problem into Branch_3_0 from 3.2/4.0. Sample exception dump appears below: 2002-08-27 15:33:27,320 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Priv.findForUs er] Find failed org.jboss.util.NestedSQLException: Interrupted while requesting permit!; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit!) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnec tion(LocalDataSource.java:106) at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.exe cute(JDBCAbstractQueryCommand.java:92) at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute (JDBCFindEntityCommand.java:44) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDB CStoreManager.java:541) at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPer sistenceManager.java:336) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.findEntity(CachedConnectionInterceptor.java:301) at org.jboss.ejb.EntityContainer.find(EntityContainer.java:687) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(E ntityContainer.java:1116) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInte rceptor.java:73) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHom e(EntitySynchronizationInterceptor.java:209) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.invokeHome(CachedConnectionInterceptor.java:215) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(Entity InstanceInterceptor.java:88) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLoc kInterceptor.java:79) at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(Entity CreationInterceptor.java:44) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractT xInterceptor.java:111) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInt erceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptor CMT.java:52) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInte rceptor.java:105) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.ja va:129) at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:48 7) at org.jboss.ejb.Container.invoke(Container.java:738) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.j ava:517) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:9 8) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.j ava:102) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercep tor.java:73) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.jav a:76) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java: 198) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) at $Proxy396.findForUser(Unknown Source) at com.whitesmiths.sacha.web.common.PrivChecker.checkPrivStat us(PrivChecker.java:370) at com.whitesmiths.sacha.web.common.Utilities.checkAccessSettin gs(Utilities.java:238) at com.whitesmiths.sacha.web.tagsupport.CheckPrivTag.doStartTag (CheckPrivTag.java:83) at org.apache.jsp.listWorklists$jsp._jspService(listWorklists$jsp.java :89) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java :107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service( JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.ja va:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 344) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApp licationHandler.java:313) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.jav a:554) at org.mortbay.jetty.servlet.WebApplicationHandler.handle(WebAppli cationHandler.java:199) at org.mortbay.http.HttpContext.handle(HttpContext.java:1572) at org.mortbay.http.H
[JBoss-dev] [ jboss-Bugs-530039 ] Transaction exception when deploy EJBjar
Bugs item #530039, was opened at 2002-03-14 14:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=530039&group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: bill (billprogra) >Assigned to: Dain Sundstrom (dsundstrom) Summary: Transaction exception when deploy EJBjar Initial Comment: I use Jboss beta at the monment. I use a session bean to call a entity bean "A" which is local entity bean. The entity bean has a relation with another local entity bean "B", one to many relationship. When I create the new entity bean B and add it into the collection of A using remote method in session bean, it generate the exception as below, but the data did insert into the table, is it a bug If it is not, just ignor the message. One more thing forget to mention is that the bean B's Primary key is Automatic generated by UIDDispensor class(ejbutils-1.2beta). javax.resource.ResourceException: Unable to rollback DB connection: java.sql.SQL Exception: General error: Warning: Some non- transactional changed tables couldn 't be rolled back at org.jboss.resource.adapter.jdbc.local.JDBCManagedConne ction.cleanup(J DBCManagedConnection.java:216) at org.jboss.resource.connectionmanager.ManagedConnection PoolFactory.ret urnObject(ManagedConnectionPoolFactory.java:145) at org.jboss.pool.ObjectPool.releaseObject (ObjectPool.java:820) at org.jboss.resource.connectionmanager.BaseConnectionMan ager$NoTransact ionListener.closeConnection (BaseConnectionManager.java:449) at org.jboss.resource.connectionmanager.BaseConnectionMan ager$NoTransact ionListener.connectionClosed (BaseConnectionManager.java:409) at org.jboss.resource.adapter.jdbc.BaseManagedConnection. fireConnectionE vent(BaseManagedConnection.java:152) at org.jboss.resource.adapter.jdbc.local.JDBCManagedConne ction.fireConne ctionEvent(JDBCManagedConnection.java:227) at org.jboss.resource.adapter.jdbc.local.JDBCManagedConne ction$1.objectC losed(JDBCManagedConnection.java:80) at org.jboss.resource.adapter.jdbc.local.ConnectionInPool .firePoolEvent( ConnectionInPool.java:899) at org.jboss.resource.adapter.jdbc.local.ConnectionInPool .close(Connecti onInPool.java:788) at org.ejbutils.uid.UIDHighKeyGeneratorBean.getNextHighKe y(UIDHighKeyGen eratorBean.java) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.StatelessSessionContainer$ContainerInter ceptor.invoke(S tatelessSessionContainer.java:642) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInte rceptor.java:96) at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeN ext(AbstractTxI nterceptorBMT.java:144) at org.jboss.ejb.plugins.TxInterceptorBMT.invoke (TxInterceptorBMT.java:6 2) at org.jboss.ejb.plugins.StatelessSessionInstanceIntercep tor.invoke(Stat elessSessionInstanceInterceptor.java:77) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor. java:127) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:166) at org.jboss.ejb.StatelessSessionContainer.invoke (StatelessSessionContai ner.java:308) at org.jboss.ejb.Container.invoke (Container.java:630) at com.sun.management.jmx.MBeanServerImpl.invoke (MBeanServerImpl.java:15 55) at com.sun.management.jmx.MBeanServerImpl.invoke (MBeanServerImpl.java:15 23) at org.jboss.invocation.local.LocalInvoker.invoke (LocalInvoker.java:92) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy. invoke(JRMPInvo kerProxy.java:150) at org.jboss.proxy.ejb.GenericProxy.invoke (GenericProxy.java:182) at org.jboss.proxy.ejb.StatelessSessionProxy.invoke (StatelessSessionProx y.java:111) at $Proxy75.getNextHighKey(Unknown Source) at org.ejbutils.uid.UIDDispenser.findNewHighKey (UIDDispenser.java:141) at org.ejbutils.uid.UIDDispenser.getNextId (UIDDispenser.java:87) at syit.TelephoneBean.ejbCreate (TelephoneBean.java:14) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.plugins.CMPPersistenceManager.createEnti ty(CMPPersisten ceManager.java:201) at org.jboss.ejb.EntityContainer.createLocalHome (EntityContainer.java:56 1) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.EntityContainer$ContainerInterceptor.inv okeHome(EntityC ontainer.java:1051) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome (AbstractIntercep tor.java:73) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor .invokeHome(Ent itySynchronizationInterceptor.java:222) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke Home(EntityInst anceInterceptor.java:136) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome (EntityLockInte rcepto
[JBoss-dev] [ jboss-Bugs-604950 ] 3.0.2 do not connect to the database
Bugs item #604950, was opened at 2002-09-05 03:48
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=604950&group_id=22866
>Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Franco Biaggi (fbiaggi)
Assigned to: David Jencks (d_jencks)
Summary: 3.0.2 do not connect to the database
Initial Comment:
Hello,
following problem (wrok fine in JBoss 2.4.7)
The application access both a mySQL db and a DB2/400 db.
During the migration to 3.0.2 I just added 2
-service.xml files and user/passwords.
The mySQL connection work fine, the DB2/400 not AND
WITHOUT ERRORS.
The DB2/400 connection is bound.
The problem is that JBoss do not try to connect to the
database and during deploy of the EJB's hangs without
any error.
stdout.log:
...
20:50:49,112 INFO [MainDeployer] Starting deployment of
package:
file:/E:/jboss/server/default/deploy/as400-service.xml
20:50:49,202 WARN [ServiceController]
jboss.jca:service=LocalTxDS,name=legacy does not
implement any Service methods
20:50:49,202 INFO [JBossManagedConnectionPool] Creating
20:50:49,202 INFO [JBossManagedConnectionPool] Created
20:50:49,212 INFO [JBossManagedConnectionPool] Starting
20:50:49,212 INFO [JBossManagedConnectionPool] Started
20:50:49,212 INFO [MainDeployer] Deployed package:
file:/E:/jboss/server/default/deploy/as400-service.xml
...
20:50:51,475 INFO [legacy] Bound connection factory for
resource adapter 'JBoss LocalTransaction JDBC Wrapper'
to JNDI name 'java:/legacy'
... loop at end :
20:51:00,168 INFO [MainDeployer] Starting deployment of
package:
file:/E:/jboss/server/default/deploy/logistockEDI.jar
20:51:00,598 INFO [EjbModule] Creating
20:51:00,668 INFO [EjbModule] Deploying
IFCSUM_R_001_D01_Details
20:51:00,698 INFO [EjbModule] Deploying
IFCSUM_R_001_H01_Header
20:51:00,698 INFO [EjbModule] Deploying CGL7CPP
server.log:
...
2002-09-01 20:50:49,112 INFO
[org.jboss.deployment.MainDeployer] Starting deployment
of package:
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,112 DEBUG
[org.jboss.deployment.MainDeployer] Starting deployment
(init step) of package at:
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,132 DEBUG
[org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL
with url
file:/E:/jboss/server/default/tmp/deploy/server/default/deploy/as400-service.xml/51.as400-service.xml
2002-09-01 20:50:49,132 DEBUG
[org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL
with url
file:/E:/jboss/server/default/tmp/deploy/server/default/deploy/as400-service.xml/51.as400-service.xml
2002-09-01 20:50:49,132 DEBUG
[org.jboss.mx.loading.UnifiedLoaderRepository2] Adding
org.jboss.mx.loading.UnifiedClassLoader@58c528{
url=file:/E:/jboss/server/default/tmp/deploy/server/default/deploy/as400-service.xml/51.as400-service.xml
}
2002-09-01 20:50:49,132 DEBUG
[org.jboss.deployment.MainDeployer] using deployer
org.jboss.deployment.SARDeployer@29428e
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.SARDeployer] about to copy 0
local directories
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.MainDeployer] found 0 subpackages
of file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.MainDeployer] Watching new file:
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.MainDeployer] create step for
deployment
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.SARDeployer] Deploying SAR,
create step: url
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.SARDeployer] Registering service
UCL=jmx.loading:UCL=7858936
2002-09-01 20:50:49,162 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxCM,name=legacy
2002-09-01 20:50:49,162 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.LocalTxConnectionManager
2002-09-01 20:50:49,182 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxCM,name=legacy
2002-09-01 20:50:49,182 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,182 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.RARDeployment
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceConfigurator] JndiName set to
legacy in jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceConfigurator]
ManagedConnectionFactoryProperties set to
jdbc:as400://10.1.1.50
com.ibm.as400.access.AS400JDBCDriver
in jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxDS,name=legacy depends on
jboss.jca:ser
[JBoss-dev] [ jboss-Bugs-484776 ] Dead connection in Pool
Bugs item #484776, was opened at 2001-11-23 02:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=484776&group_id=22866 >Category: JBossCX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bani Greyling (banigreyling) Assigned to: David Jencks (d_jencks) Summary: Dead connection in Pool Initial Comment: Windows NT4 SP5 JDK 1.3 JBoss2.4.1a-Tomcat3.2.3 If a connection die in the pool and is later given out to participate in a transaction, it (obviously) give an exception. I think this is incorrect behaviour for the pool to assume the connection to be still valid after the transaction the connection was used in did not succeed. I configured my datasource with InvalidateOnError=true, but it does not seem to work. The dead connection stay in the pool. If my connections tend to die over time, I will end up with a pool of dead connections with no automated way of getting rid of them. IdleTimeout will not work, because the connection will not be idle as it is given out all the time (and cause exceptions). -- Comment By: David Jencks (d_jencks) Date: 2002-02-05 12:27 Message: Logged In: YES user_id=60525 I believe that the jdbc specs don't really discuss what to do with dead connections, however the jca specs do. Please try using the jca xa wrapper to see if that works properly. Note that this is pretty much untested code, since I don't have a XADataSource implementation to play with. (For various reasons, the "XADataSourceImpl" wrapper doesn't work very well pretending to be an XADatasource in the jca framework) -- Comment By: Bani Greyling (banigreyling) Date: 2001-11-28 02:46 Message: Logged In: YES user_id=302589 I investigated this further. As it turned out I was not using "org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl" but "com.jnetdirect.jsql.JSQLXADataSource" as my DataSourceClass. When using "org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl" any dead connection would be removed from the pool after participating in a (failed) transaction, so at least I would not end up with a bunch of dead connections. Maybe this is not a bug but rather an enhancement request;) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=484776&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600435 ] deadlock detected erroneously
Bugs item #600435, was opened at 2002-08-26 15:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600435&group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole Status: Open >Resolution: Invalid Priority: 5 Submitted By: Kyle Downey (kdowney) Assigned to: Bill Burke (patriot1burke) Summary: deadlock detected erroneously Initial Comment: I have a session bean method calling a CMP Entity method. They are set up as follows in terms of transactions: KeySequence getNextKeyAfterIncrementingBy RequiresNew commonsvc/KeyGenerator * Required The session call successfully creates the Entity EJB, but the second call (to actually use the newly-created Entity) from the same client, in what I would assume is the same transaction, fails with this exception: Caused by: org.jboss.ejb.plugins.lock.ApplicationDeadlockException : Application deadlock detected: Current thread already has tx lock in different transaction. at org.jboss.ejb.plugins.lock.BeanLockSupport.deadlockDet ection(BeanLock Support.java:182) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.w aitForTx(QueuedP essimisticEJBLock.java:283) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.d oSchedule(Queued PessimisticEJBLock.java:189) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.s chedule(QueuedPe ssimisticEJBLock.java:140) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockIntercep tor.java:103) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreation Interceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInte rceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxIntercep torCMT.java:255) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:6 0) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor. java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv oke(BaseLoca lContainerInvoker.java:301) at org.jboss.ejb.plugins.local.EntityProxy.invoke (EntityProxy.java:38) Note that this is triggered by a single call to the session EJB from a single client (a unit test), so it should not be possible to create deadlock. Database: Postgresql JVM: JDK 1.3.1_03 (Sun) JBoss: 3.0.1 --kd -- >Comment By: Bill Burke (patriot1burke) Date: 2002-09-12 12:56 Message: Logged In: YES user_id=176497 This bug is invalid. You have accessed the bean in a transaction then you called a RequiresNew method. So you will have deadlock. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600435&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600647 ] Interrupted while requesting permit!
Bugs item #600647, was opened at 2002-08-27 01:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600647&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) >Assigned to: David Jencks (d_jencks) Summary: Interrupted while requesting permit! Initial Comment: This is a reminder to roll in the fix for this (apparently Jetty) problem into Branch_3_0 from 3.2/4.0. Sample exception dump appears below: 2002-08-27 15:33:27,320 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Priv.findForUs er] Find failed org.jboss.util.NestedSQLException: Interrupted while requesting permit!; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit!) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnec tion(LocalDataSource.java:106) at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.exe cute(JDBCAbstractQueryCommand.java:92) at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute (JDBCFindEntityCommand.java:44) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDB CStoreManager.java:541) at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPer sistenceManager.java:336) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.findEntity(CachedConnectionInterceptor.java:301) at org.jboss.ejb.EntityContainer.find(EntityContainer.java:687) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(E ntityContainer.java:1116) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInte rceptor.java:73) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHom e(EntitySynchronizationInterceptor.java:209) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.invokeHome(CachedConnectionInterceptor.java:215) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(Entity InstanceInterceptor.java:88) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLoc kInterceptor.java:79) at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(Entity CreationInterceptor.java:44) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractT xInterceptor.java:111) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInt erceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptor CMT.java:52) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInte rceptor.java:105) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.ja va:129) at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:48 7) at org.jboss.ejb.Container.invoke(Container.java:738) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.j ava:517) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:9 8) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.j ava:102) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercep tor.java:73) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.jav a:76) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java: 198) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) at $Proxy396.findForUser(Unknown Source) at com.whitesmiths.sacha.web.common.PrivChecker.checkPrivStat us(PrivChecker.java:370) at com.whitesmiths.sacha.web.common.Utilities.checkAccessSettin gs(Utilities.java:238) at com.whitesmiths.sacha.web.tagsupport.CheckPrivTag.doStartTag (CheckPrivTag.java:83) at org.apache.jsp.listWorklists$jsp._jspService(listWorklists$jsp.java :89) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java :107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service( JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.ja va:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 344) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApp licationHandler.java:313) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.jav a:554) at org.mortbay.jetty.servlet.WebApplicationHandler.handle(WebAppli cationHandler.java:199) at org.mortbay.http.HttpContext.handle(HttpContext.java:1572) at org.mortbay.http.H
[JBoss-dev] [ jboss-Bugs-604916 ] JBoss.3.0TemplateAndExample w/ sqlserv2k
Bugs item #604916, was opened at 2002-09-05 02:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=604916&group_id=22866 >Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open >Resolution: Accepted Priority: 5 Submitted By: Lee Schumacher (lelliot) >Assigned to: Dain Sundstrom (dsundstrom) Summary: JBoss.3.0TemplateAndExample w/ sqlserv2k Initial Comment: The cmp2 example wouldn't work with ms sqlserver 2000 as the backend. There were a couple of issues with the jbosscmp-jdbc.xml file: 1) desc (in the organization table) breaks because desc is a keyword. I suspect this will break in oracle or the other commercial dbs either. 2) name is a keyword in sqlserver2k. This is probably specific to ms sql2k. Btw, how about a new bug category for this (also covering the quick start doc)? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=604916&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600435 ] deadlock detected erroneously
Bugs item #600435, was opened at 2002-08-26 15:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600435&group_id=22866 Category: JBossTX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Kyle Downey (kdowney) >Assigned to: Bill Burke (patriot1burke) Summary: deadlock detected erroneously Initial Comment: I have a session bean method calling a CMP Entity method. They are set up as follows in terms of transactions: KeySequence getNextKeyAfterIncrementingBy RequiresNew commonsvc/KeyGenerator * Required The session call successfully creates the Entity EJB, but the second call (to actually use the newly-created Entity) from the same client, in what I would assume is the same transaction, fails with this exception: Caused by: org.jboss.ejb.plugins.lock.ApplicationDeadlockException : Application deadlock detected: Current thread already has tx lock in different transaction. at org.jboss.ejb.plugins.lock.BeanLockSupport.deadlockDet ection(BeanLock Support.java:182) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.w aitForTx(QueuedP essimisticEJBLock.java:283) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.d oSchedule(Queued PessimisticEJBLock.java:189) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.s chedule(QueuedPe ssimisticEJBLock.java:140) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockIntercep tor.java:103) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreation Interceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInte rceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxIntercep torCMT.java:255) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:6 0) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor. java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv oke(BaseLoca lContainerInvoker.java:301) at org.jboss.ejb.plugins.local.EntityProxy.invoke (EntityProxy.java:38) Note that this is triggered by a single call to the session EJB from a single client (a unit test), so it should not be possible to create deadlock. Database: Postgresql JVM: JDK 1.3.1_03 (Sun) JBoss: 3.0.1 --kd -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600435&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-600647 ] Interrupted while requesting permit!
Bugs item #600647, was opened at 2002-08-27 01:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600647&group_id=22866 >Category: JBossCX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) Assigned to: David Jencks (d_jencks) Summary: Interrupted while requesting permit! Initial Comment: This is a reminder to roll in the fix for this (apparently Jetty) problem into Branch_3_0 from 3.2/4.0. Sample exception dump appears below: 2002-08-27 15:33:27,320 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Priv.findForUs er] Find failed org.jboss.util.NestedSQLException: Interrupted while requesting permit!; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit!) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnec tion(LocalDataSource.java:106) at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.exe cute(JDBCAbstractQueryCommand.java:92) at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute (JDBCFindEntityCommand.java:44) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDB CStoreManager.java:541) at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPer sistenceManager.java:336) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.findEntity(CachedConnectionInterceptor.java:301) at org.jboss.ejb.EntityContainer.find(EntityContainer.java:687) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(E ntityContainer.java:1116) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInte rceptor.java:73) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHom e(EntitySynchronizationInterceptor.java:209) at org.jboss.resource.connectionmanager.CachedConnectionIntercep tor.invokeHome(CachedConnectionInterceptor.java:215) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(Entity InstanceInterceptor.java:88) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLoc kInterceptor.java:79) at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(Entity CreationInterceptor.java:44) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractT xInterceptor.java:111) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInt erceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptor CMT.java:52) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInte rceptor.java:105) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.ja va:129) at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:48 7) at org.jboss.ejb.Container.invoke(Container.java:738) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.j ava:517) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:9 8) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.j ava:102) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercep tor.java:73) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.jav a:76) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java: 198) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) at $Proxy396.findForUser(Unknown Source) at com.whitesmiths.sacha.web.common.PrivChecker.checkPrivStat us(PrivChecker.java:370) at com.whitesmiths.sacha.web.common.Utilities.checkAccessSettin gs(Utilities.java:238) at com.whitesmiths.sacha.web.tagsupport.CheckPrivTag.doStartTag (CheckPrivTag.java:83) at org.apache.jsp.listWorklists$jsp._jspService(listWorklists$jsp.java :89) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java :107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service( JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.ja va:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 344) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApp licationHandler.java:313) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.jav a:554) at org.mortbay.jetty.servlet.WebApplicationHandler.handle(WebAppli cationHandler.java:199) at org.mortbay.http.HttpContext.handle(HttpContext.java:1572) at org.mortbay.http.HttpC
[JBoss-dev] [ jboss-Bugs-571995 ] Wrong error reporting for ejb finders
Bugs item #571995, was opened at 2002-06-21 02:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=571995&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: Postponed Priority: 5 Submitted By: Stephen Coy (scoy) Assigned to: Dain Sundstrom (dsundstrom) Summary: Wrong error reporting for ejb finders Initial Comment: I had erroneously declared a finder method as: java.util.Set findUserLists(com.whitesmiths.sacha.ejb.auth.interfaces.UserLocal user) Note the use of "Set". Sets are only legal for select methods. When I tried to deploy this, JBoss (Branch_3_0) said: org.jboss.deployment.DeploymentException: Error compiling ejbql; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "" at line 1, column 96. Was expecting one of: "IN" ... ... ) at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.(JDBCEJBQLQuery.java:46) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:44) which had me looking for syntax errors in the EJB QL, instead of the method signature. -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-06-24 18:54 Message: Logged In: YES user_id=251431 This will be fixed during the rewrite of the metadata package in 3.1. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=571995&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-555070 ] Incorrect CREATE statement for MySQL ds
Bugs item #555070, was opened at 2002-05-12 05:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=555070&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: Postponed Priority: 5 Submitted By: Dylan van Iersel (dviersel) Assigned to: Dain Sundstrom (dsundstrom) Summary: Incorrect CREATE statement for MySQL ds Initial Comment: The CREATE statement to create a new table in a MySQL datasource does not quote the tablename nor the column names. This causes problems when tables are created with names corresponding to MySQL reserved words. For example: when deploying an entity bean called "Group", JBoss trace shows: org.jboss.deployment.DeploymentException: Could not deploy njar:file:/C:/Java/jboss- 3.0.0RC2/server/ default/tmp/deploy/server/default/deploy/rcontrol.ear/80.rcontrol.ear^/nntp- bingrab.jar; - nested th rowable: (org.jboss.deployment.DeploymentException: Error while creating table; - nested throwable: (java.sql.SQLException: Syntax error or access violation: You have an error in your SQL syntax near 'Group (id VARCHAR(255) BINARY NOT NULL, CONSTRAINT pk_Group PRIMARY KEY (id))' at line 1)) When I directly enter this CREATE statement on the MySQL command-line, I get the same error, whilst when I surround them by quotes (`) the table is created correctly. OS: Win2000 JDK: 1.3.1 JBoss 3.0 RC2 -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-06-24 18:54 Message: Logged In: YES user_id=251431 This will be fixed during the rewrite of the metadata package in 3.1. -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-05-14 13:09 Message: Logged In: YES user_id=251431 This is unlikely to change any time soon. I suggest you avoid sql reserved words. In the future, I want to add some code that will autogenerate around SQL reserved words. -- Comment By: Stephen Coy (scoy) Date: 2002-05-13 02:29 Message: Logged In: YES user_id=463096 Further to this, I've added a feature request (555315) regarding this because I think the current behaviour is more of a limitation of the current design/implementation rather than a bug per se. -- Comment By: Stephen Coy (scoy) Date: 2002-05-13 01:30 Message: Logged In: YES user_id=463096 Further to this, I've added a feature request (555315) regarding this because I think the current behaviour is more of a limitation of the current design/implementation rather than a bug per se. -- Comment By: Stephen Coy (scoy) Date: 2002-05-13 01:06 Message: Logged In: YES user_id=463096 This issue is not limited to MySQL. It's my understanding that all JDBC 2.0 compliant drivers are supposed to support the quoting syntax. For now, you need to set up name mappings manually in jbosscmp-jdbc.xml. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=555070&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-591835 ] Include ORDER BY cols in SELECT clause
Bugs item #591835, was opened at 2002-08-06 20:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=591835&group_id=22866 >Category: JBossCMP >Group: v3.2 Status: Open Resolution: Accepted Priority: 5 Submitted By: Stephen Coy (scoy) >Assigned to: Dain Sundstrom (dsundstrom) Summary: Include ORDER BY cols in SELECT clause Initial Comment: Some databases, Oracle in particular, require that columns named in an ORDER BY clause be included in the SELECT clause when SELECT DISTINCT is used. Here is some text from current Oracle documentation: Restrictions on the order_by_clause: * If you have specified the DISTINCT operator in this statement, then this clause cannot refer to columns unless they appear in the select list. * An order_by_clause can contain no more than 255 expressions. This can be worked around using on-find loading with load groups, but it sure would be useful if JBoss managed it for us. -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-08-23 20:00 Message: Logged In: YES user_id=251431 This is really a bug. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=591835&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-540049 ] Exception Cleanup
Bugs item #540049, was opened at 2002-04-05 18:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=540049&group_id=22866 >Category: JBossSX >Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 4 Submitted By: Peter Luttrell (objec) >Assigned to: Scott M Stark (starksm) Summary: Exception Cleanup Initial Comment: In the auth.conf file, if you specify duplicate security domain, you get an exception stating such; duh! It also however states something about "please contact the developers"; you might want to clean this up. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=540049&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-437043 ] Custom finder methods not executed
Bugs item #437043, was opened at 2001-06-28 06:47
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=437043&group_id=22866
>Category: JAWS (inactive)
>Group: v2.4 (stable)
Status: Open
>Resolution: Wont Fix
>Priority: 1
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Custom finder methods not executed
Initial Comment:
Custom finder methods "find" are not executed
any more. Only "findBy" methods are executed
this is not according to the specs. The is in
org.jboss.ejb.plugins.jaws.jdbc.JDBCFindEntitiesCommand
. Change:
< name.startsWith("ejbFindBy")
> name.startsWith("ejbFind")
--
>Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-09-12 12:43
Message:
Logged In: YES
user_id=251431
JAWS is no longer actively maintained. We will accept
patches, and we will fix bugs on a contract basis.
Furthermore, JAWS will be removed in JBoss 4.0.
--
Comment By: Christian Riege (lqd)
Date: 2002-02-21 13:49
Message:
Logged In: YES
user_id=176671
Moving to "Bugs"; marking as 2.4 stable; this also exists in 3.0
--
Comment By: Christian Riege (lqd)
Date: 2002-02-21 12:12
Message:
Logged In: YES
user_id=176671
this is correct, see Section 8.3.2 of EJB 1.1 and Section
10.7.3 of EJB 2.0 spec respectively.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=437043&group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-572281 ] oracle clob mapping problem
Bugs item #572281, was opened at 2002-06-21 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=572281&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: Postponed Priority: 5 Submitted By: Colin Li (colinl) Assigned to: Dain Sundstrom (dsundstrom) Summary: oracle clob mapping problem Initial Comment: We had an entity bean with a cmp-field using a char [] type to mapping CLOB type column in oracle database. This entity bean worked fine in Orion1.5.2. Now we are planning to port our application to Jboss3.0.0 and we have deployed one of our ear file including this bean in Jboss3.0.0 (stable version). However, we got error messages in jboss console when we ran one of our test cases: <> CLOB_DATA is the char[] type cmp-field. We checked the standardjbosscmp-jdbc.xml and we did not find a clob type mapping in Oracle8 So, is this a bug or not? When will Jboss support Clob mapping? Thanks a lot! C:\jboss-3.0.0\bin>run = = = . JBoss Bootstrap Environment . JBOSS_HOME: C:\jboss-3.0.0\bin\.. . JAVA: C:\jdk1.3\bin\java . JAVA_OPTS: -Dprogram.name=run.bat . CLASSPATH: ;C:\jdk1.3\lib\tools.jar;C:\jboss- 3.0.0\bin\run.jar . = = = -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-06-27 13:27 Message: Logged In: YES user_id=251431 This will be fixed when blob handling is rewritten. -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-06-24 15:03 Message: Logged In: YES user_id=251431 Oracle's drivers are non-compliant and suck overall. One day this will be fixed. Several people have told me that they we're goin to take a look at it, but no one fixed it yet. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=572281&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-550606 ] Too many AND's and OR's with Sybase
Bugs item #550606, was opened at 2002-04-30 08:00 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=550606&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: Postponed Priority: 5 Submitted By: Daniel Moos (moosi_1978) Assigned to: Dain Sundstrom (dsundstrom) Summary: Too many AND's and OR's with Sybase Initial Comment: I have following problems with Sybase 11.9.2 and JBoss3.0.0RC1: If Jboss call findAll()-Methode, then throws a following Exception : 14:25:40,730 INFO [STDOUT] SQLException: SQLState(Z) vendor code(404) 14:25:40,731 INFO [STDOUT] com.sybase.jdbc2.jdbc.SybSQLException: Too many ANDs or ORs in expression (limit 250 per expression level). Try splitting query or limiting ANDs and ORs. Before Jboss call findAll-Methode, put i 300 rows in a Table over Jboss. What i doing false? Who can help me? -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-06-24 18:51 Message: Logged In: YES user_id=251431 This will be fixed during the rewrite of the metadata package in 3.1. -- Comment By: Daniel Moos (moosi_1978) Date: 2002-05-02 04:50 Message: Logged In: YES user_id=332885 Sorry, i set you're proposition and the Exception did not change. I even set in jaws.xml or standardjaws.xml a read-ahead tag to true, no change too. -- Comment By: Georg Schmid (giorgio42) Date: 2002-04-30 12:26 Message: Logged In: YES user_id=437570 Maybe reducing the page size for the read-ahead to something below 250 (in standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml) helps. Georg -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=550606&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-562004 ] 'Error setting column value' using dependent value classes w
Bugs item #562004, was opened at 2002-05-29 13:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=562004&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: Postponed Priority: 5 Submitted By: Justin Casp (jcasp) Assigned to: Dain Sundstrom (dsundstrom) Summary: 'Error setting column value' using dependent value classes w Initial Comment: I posted this problem a few weeks ago on jboss.org forums, but it's down right now so I can't reference that post. I figured out how to create a simple test case that reliably reproduces the problem. The error message 'Error setting column value' occurs when I have an existing CMP bean that reads existing records from a datasource. The bean uses a dependent value class, although I'm not sure if this problem is specific to dependent value classes or just any cmp bean with fields mapped to columns. If I create the record externally (e.g., using psql, the postgres command line tool) and only set a few of the columns to non-null values, when I attempt to load that bean instance with a finder, jboss throws the following exception on the server: 12:03:56,650 ERROR [STDERR] java.lang.NullPointerException 12:03:56,652 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 12:03:56,652 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 12:03:56,653 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 12:03:56,653 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324) 12:03:56,653 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeComplexProperty.setColumnValue(JDBCTypeComplexProperty.java:142) 12:03:56,654 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeComplex.setColumnValue(JDBCTypeComplex.java:158) 12:03:56,654 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeComplex.setColumnValue(JDBCTypeComplex.java:133) 12:03:56,654 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.loadArgumentResults(JDBCAbstractCMPFieldBridge.java:352) 12:03:56,655 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.loadInstanceResults(JDBCAbstractCMPFieldBridge.java:304) 12:03:56,655 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:140) 12:03:56,655 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:62) 12:03:56,655 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:496) 12:03:56,656 ERROR [STDERR] at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:410) 12:03:56,656 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.loadEntity(CachedConnectionInterceptor.java:314) 12:03:56,656 ERROR [STDERR] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:310) 12:03:56,657 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:147) 12:03:56,657 ERROR [STDERR] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:193) 12:03:56,657 ERROR [STDERR] at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107) 12:03:56,658 ERROR [STDERR] at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:69) 12:03:56,658 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) 12:03:56,658 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) 12:03:56,659 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61) 12:03:56,659 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:129) 12:03:56,659 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) 12:03:56,659 ERROR [STDERR] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:145) 12:03:56,660 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:482) 12:03:56,660 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:694) 12:03:56,660 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1024) 12:03:56,661 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) 12:03:56,661 ERROR [STDERR] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:321) 12:
[JBoss-dev] [ jboss-Bugs-559232 ] RC3 CMP 2 create table exception
Bugs item #559232, was opened at 2002-05-22 10:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=559232&group_id=22866 Category: JBossCMP >Group: v4.0 Status: Open Resolution: Postponed Priority: 5 Submitted By: Rik de Groot (synotix) Assigned to: Dain Sundstrom (dsundstrom) Summary: RC3 CMP 2 create table exception Initial Comment: I recently switched from Jboss 3RC1 to RC2. In the standardjbosscmp-jdbc.xml I have the following settings true false When I deployed an EAR file on RC2, the instance logs that the table exists, but carries on with the deployment. The new RC3 throws an exception and doesnt deploy at all. When I set the create-table on false the EAR deploys normally. Rik. 2002-05-22 11:11:24,002 ERROR [org.jboss.ejb.EjbModule] Starting failed org.jboss.deployment.DeploymentException: Error while creating table; - nested throwable: (java.sql.SQLException: General error: Table 'votebean' already exists) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.ja va:190) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.execute(JDBCStartCommand.java:8 4) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:384 ) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:19 8) at org.jboss.ejb.EntityContainer.start(EntityContainer.java:376) at org.jboss.ejb.Container.invoke(Container.java:793) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:8 67) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:339) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy18.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:440) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:8 67) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:339) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.start(Unknown Source) at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:394) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:692) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:685) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:527) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:490) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.j ava:405) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentSc anner.java:586) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.jav a:465) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDep loymentScanner.java:237) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:8 67) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:339) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatche r.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy3.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:276) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:692) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:527) at org.jboss.deployment.MainDeployer.de
[JBoss-dev] [ jboss-Bugs-607213 ] Read-Only Entity Bean
Bugs item #607213, was opened at 2002-09-10 04:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=607213&group_id=22866 Category: JBossCMP >Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: vishal (attachvishal) >Assigned to: Dain Sundstrom (dsundstrom) Summary: Read-Only Entity Bean Initial Comment: I am using jboss3.0.2 and i defined my entity bean as read-only in jbosscmp-jdbc.xml.It looks like this uk.co.isesolutions.apps.ccd.customer.entity.Customer CNCUSTOMER [b]true 1000[/b] cnCustomer CNCUSTOMER NUMBER(12) u_Version U_VERSION VARCHAR2(1) ... cnaccom_Typ ACCOM_TYP NUMBER(12) and in Session bean i looked for Customer entity bean something like this Customer customer = getCustomerHome(CustomerHome.class).findByPrimaryKey(new CustomerPK(id)); customerVO = customer.showCustomerDetails(); /* the Below line should throw EJBException but container allows me update */ customer.setCnaccom_Typ(new Long(213)); At the jboss trace i noticed this 09:54:13,937 DEBUG [findByPrimaryKey] Executing SQL: SELECT CNCUSTOMER FROM CNCUSTOMER WHERE CNCUSTOMER=? 09:54:13,968 DEBUG [Customer] Executing SQL: SELECT CNORIGIN, SURNAME, CNORIGIN, FORENAME, DOB_DAT, ACTIVE_FLG FROM CNCUSTOMER WHERE (CNCUSTOMER=?) [b]09:54:14,875 DEBUG [Customer] Executing SQL: UPDATE CNCUSTOMER SET ACCOM_TYP=? WHERE CNCUSTOMER=? 09:54:14,890 DEBUG [Customer] Rows affected = 1[/b] -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=607213&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-608202 ] EJBQL fails to compile
Bugs item #608202, was opened at 2002-09-12 00:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608202&group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open >Resolution: Accepted Priority: 5 Submitted By: Cory Prowse (cosmic) >Assigned to: Dain Sundstrom (dsundstrom) Summary: EJBQL fails to compile Initial Comment: OS: Linux (2.4 kernel) JDK: java version "1.4.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode) JBoss Release: JBoss-3.0.2 CVSTag=JBoss_3_0_2 NOTE: I will try and cut out a test case but it may take a few days (deadline). A workaround is to use OBJECT() and get the field that way. When I attempt the following EJBQL: ejbSelectCargoValue packet.interfaces.PacketEntityLocal java.lang.String [CDATA[SELECT c.value FROM PacketEntity p, IN (p.cargoes) AS c WHERE p = ?1 AND c.name = ?2]] I get the following exception: org.jboss.deployment.DeploymentException: Error compiling ejbql; - nested throwable: (java.lang.IllegalStateException: Can not visit multi-column path node. Should have been handled at a higher level.) at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.(JDBCEJBQLQuery.java:46) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:44) at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:214) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:463) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:369) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:198) -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:39 Message: Logged In: YES user_id=251431 What is the type of c.value? Is it a mapped dependent value class? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608202&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-606812 ] Table not removed from db on undeploy
Bugs item #606812, was opened at 2002-09-09 11:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=606812&group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Da C (dacu) >Assigned to: Dain Sundstrom (dsundstrom) Summary: Table not removed from db on undeploy Initial Comment: Hi, I think there is a bug when undeploying a CMP entity bean that has relations. JBoss v3.0.2 Windows 2000 Pro JDK 1.3 Xdoclet for code generation On a test project, I have two CMP entity beans: Product and Order. I have defined a relation 1 to many between Order and Product. I used @jboss:relation tag with xdoclet, and the relation has also a constraint (fk_constraint=true). My Database is MS SQL Server 2000. Everything is generated correcty, but on undeploy, the Order table is not removed from Db. for ProductBean, the relation is defined as * @ejb:interface-method view-type="local" * @ejb:relation * name="product-order" * role-name="many-products-in-one-order" * * @jboss:relation * related-pk-field="id" * fk-column="OrderId" * fk-constraint="true" * */ public abstract inventory.interfaces.OrderEntityLocal getOrder(); for OrderBean, the relation is defined as * @ejb:interface-method view-type="local" * @ejb:relation * name="product-order" * role-name="one-order-has-many-products" * */ public abstract Set getOrderProducts(); This bug doesn't happen when I don't have a relation. Dan -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:36 Message: Logged In: YES user_id=251431 Check the generated jbosscmp-jdbc.xml file. Does it have remove-table set to true. The current release of XDoclet incorrectly generates a jaws.xml file with remote-table set to true and jaws.xml is no longer used. I suggest you upgrade to XDoclet CVS head, or you write the jbosscmp-jdbc.xml file by hand. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=606812&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-605041 ] Mapping of EJB-QL 'length' for Oracle
Bugs item #605041, was opened at 2002-09-05 08:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605041&group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open >Resolution: Accepted Priority: 5 Submitted By: Timo Warns (timow) >Assigned to: Dain Sundstrom (dsundstrom) >Summary: Mapping of EJB-QL 'length' for Oracle Initial Comment: In standardjbosscmp-jdbc.xml EQL-function length is mapped to Oracle SQL-function 'len', but Oracle has no SQL-function 'len'. Is this a bug or am I missing anything? In standardjbosscmp-jdbc.xml: [...] length len(?1) [...] -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:34 Message: Logged In: YES user_id=251431 It is a bug. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=605041&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-604950 ] 3.0.2 do not connect to the database
Bugs item #604950, was opened at 2002-09-05 03:48
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=604950&group_id=22866
Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Franco Biaggi (fbiaggi)
>Assigned to: David Jencks (d_jencks)
Summary: 3.0.2 do not connect to the database
Initial Comment:
Hello,
following problem (wrok fine in JBoss 2.4.7)
The application access both a mySQL db and a DB2/400 db.
During the migration to 3.0.2 I just added 2
-service.xml files and user/passwords.
The mySQL connection work fine, the DB2/400 not AND
WITHOUT ERRORS.
The DB2/400 connection is bound.
The problem is that JBoss do not try to connect to the
database and during deploy of the EJB's hangs without
any error.
stdout.log:
...
20:50:49,112 INFO [MainDeployer] Starting deployment of
package:
file:/E:/jboss/server/default/deploy/as400-service.xml
20:50:49,202 WARN [ServiceController]
jboss.jca:service=LocalTxDS,name=legacy does not
implement any Service methods
20:50:49,202 INFO [JBossManagedConnectionPool] Creating
20:50:49,202 INFO [JBossManagedConnectionPool] Created
20:50:49,212 INFO [JBossManagedConnectionPool] Starting
20:50:49,212 INFO [JBossManagedConnectionPool] Started
20:50:49,212 INFO [MainDeployer] Deployed package:
file:/E:/jboss/server/default/deploy/as400-service.xml
...
20:50:51,475 INFO [legacy] Bound connection factory for
resource adapter 'JBoss LocalTransaction JDBC Wrapper'
to JNDI name 'java:/legacy'
... loop at end :
20:51:00,168 INFO [MainDeployer] Starting deployment of
package:
file:/E:/jboss/server/default/deploy/logistockEDI.jar
20:51:00,598 INFO [EjbModule] Creating
20:51:00,668 INFO [EjbModule] Deploying
IFCSUM_R_001_D01_Details
20:51:00,698 INFO [EjbModule] Deploying
IFCSUM_R_001_H01_Header
20:51:00,698 INFO [EjbModule] Deploying CGL7CPP
server.log:
...
2002-09-01 20:50:49,112 INFO
[org.jboss.deployment.MainDeployer] Starting deployment
of package:
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,112 DEBUG
[org.jboss.deployment.MainDeployer] Starting deployment
(init step) of package at:
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,132 DEBUG
[org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL
with url
file:/E:/jboss/server/default/tmp/deploy/server/default/deploy/as400-service.xml/51.as400-service.xml
2002-09-01 20:50:49,132 DEBUG
[org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL
with url
file:/E:/jboss/server/default/tmp/deploy/server/default/deploy/as400-service.xml/51.as400-service.xml
2002-09-01 20:50:49,132 DEBUG
[org.jboss.mx.loading.UnifiedLoaderRepository2] Adding
org.jboss.mx.loading.UnifiedClassLoader@58c528{
url=file:/E:/jboss/server/default/tmp/deploy/server/default/deploy/as400-service.xml/51.as400-service.xml
}
2002-09-01 20:50:49,132 DEBUG
[org.jboss.deployment.MainDeployer] using deployer
org.jboss.deployment.SARDeployer@29428e
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.SARDeployer] about to copy 0
local directories
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.MainDeployer] found 0 subpackages
of file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.MainDeployer] Watching new file:
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.MainDeployer] create step for
deployment
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.SARDeployer] Deploying SAR,
create step: url
file:/E:/jboss/server/default/deploy/as400-service.xml
2002-09-01 20:50:49,152 DEBUG
[org.jboss.deployment.SARDeployer] Registering service
UCL=jmx.loading:UCL=7858936
2002-09-01 20:50:49,162 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxCM,name=legacy
2002-09-01 20:50:49,162 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.LocalTxConnectionManager
2002-09-01 20:50:49,182 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxCM,name=legacy
2002-09-01 20:50:49,182 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,182 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.RARDeployment
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceConfigurator] JndiName set to
legacy in jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceConfigurator]
ManagedConnectionFactoryProperties set to
jdbc:as400://10.1.1.50
com.ibm.as400.access.AS400JDBCDriver
in jboss.jca:service=LocalTxDS,name=legacy
2002-09-01 20:50:49,192 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxDS,name=legacy depends on
jboss.jca:se
[JBoss-dev] [ jboss-Bugs-580484 ] Show fieldname on CMPFieldMetaData error
Bugs item #580484, was opened at 2002-07-12 04:03
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=580484&group_id=22866
>Category: JAWS (inactive)
Group: v2.4 BETA (stable)
Status: Open
>Resolution: Wont Fix
>Priority: 1
Submitted By: Geert Poels (geertpoels)
Assigned to: Nobody/Anonymous (nobody)
Summary: Show fieldname on CMPFieldMetaData error
Initial Comment:
2002-07-12 09:56:58,632 WARN
[org.jboss.ejb.plugins.jaws.metadata.CMPFieldMetaData
] ERROR : Nested Field does not have a get method
could be more verbose.
If you add
on line 139 + 162
log.warn("ERROR : Nested Field does not have a get
method : " + name);
public int getJDBCType() {
and
public String getSQLType() {
--
>Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-09-12 12:27
Message:
Logged In: YES
user_id=251431
JAWS is no longer actively maintained. We will accept
patches, and we will fix bugs on a contract basis.
Furthermore, JAWS will be removed in JBoss 4.0.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=580484&group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-576479 ] TransactioRoledbackException:Load failed
Bugs item #576479, was opened at 2002-07-02 11:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=576479&group_id=22866 >Category: JAWS (inactive) Group: v2.4 (stable) Status: Open >Resolution: Wont Fix >Priority: 1 Submitted By: Bani Greyling (banigreyling) Assigned to: Nobody/Anonymous (nobody) Summary: TransactioRoledbackException:Load failed Initial Comment: OS: Win2000 Server JDK: 1.3.0 JBoss: 2.4.7 When I call remove on remotereference then I get the following error. javax.transaction.TransactionRolledbackException: javax.transaction.TransactionRolledbackException: Load failed; nested exception is: java.lang.IllegalArgumentException: object is not an instance of declaring class: Points to Note: * I use CHAR data type * Entity Bean and Session Bean are in different Jars Attached is a zip file with ant build script and some sources to better explain the problem. To run it: *Set JBOSS_HOME environment variable *Configure JBoss DefaultDS to point to a firebird database. *Start JBoss *Run build with 'default' target to create and deploy jars *Run build with 'runtest' target. This will show the error. -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:27 Message: Logged In: YES user_id=251431 JAWS is no longer actively maintained. We will accept patches, and we will fix bugs on a contract basis. Furthermore, JAWS will be removed in JBoss 4.0. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=576479&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-573828 ] CMP, byte[] and Statement.getObject(...)
Bugs item #573828, was opened at 2002-06-25 16:33
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=573828&group_id=22866
>Category: JAWS (inactive)
Group: v2.4 (stable)
Status: Open
>Resolution: Wont Fix
>Priority: 1
Submitted By: Markus Kling (mkling)
Assigned to: Nobody/Anonymous (nobody)
Summary: CMP, byte[] and Statement.getObject(...)
Initial Comment:
Hi,
Szenario: JBoss 2.4.6 & DB2 > 7.1.
I got some serious problems with CMP and JDBC
Drivers that return other objects than expected for
Statement.getObject(...).
My problem is that I got an entity bean with an instance
field of the type byte[] which can be stored but not
loaded again. The problem is that byte[] it is not a
primitive type nore on of its object representations. In
this situation the JDBCCommand executes the
Stmt.getObject() in order to read the apropriate data.
But getObject() does not return a byte[], as expected, it
returns an instance of java.sql.Blob.
In this situation the JDBCCommand assumes that it
must unmarshall the byte[] representation of the
returned object. But the result is neither a Handle nor a
primitive and this results in the "Unable to load a
ResultSet column .." Exception. [see line#383 -->
Object getResultObject(ResultSet rs, int idx, Class
destination)]
Another problem was, that I had to provide an explizit
jaws-mapping from byte[] to an sql type. DB2 does not
support the JAVA_OBJECT sqltype. This results in an
error (i don't remember it, sorry) if the JDBCCommand
tries to use PreparedStatemen.setNull().
[B
BLOB
BLOB(1M)
I am not sure if I missed something so I don't attached a
FIX. Would It be possible to include a mapping for the
array-types in the JDBCCOmmand? In this way it would
be possible to use these getXX methods for all well
known types.
This problems also affect version 3 and above!
Thanks for your help,
Markus
--
>Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-09-12 12:26
Message:
Logged In: YES
user_id=251431
JAWS is no longer actively maintained. We will accept
patches, and we will fix bugs on a contract basis.
Furthermore, JAWS will be removed in JBoss 4.0.
--
Comment By: Markus Kling (mkling)
Date: 2002-07-15 05:26
Message:
Logged In: YES
user_id=360804
Hi I had a look in the HEAD and saw that a suitable
workarround was inserted in the JDBCCommand (current is
v1.4.3).
Would it be possible to make this fix for Version 2.4.x too?
...
} else if (destination.getName().equals("[B")) {
return bytes;
...
--
Hi crippendsl, sorry but your answer has another scope than
my question.
thanks
Markus
--
Comment By: Christian Schulte (crippendsl)
Date: 2002-07-11 06:58
Message:
Logged In: YES
user_id=229917
Hello,
I also had trouble with byte[] in JBoss 2.4.4 but with MySQL
which I could fix and they were related to the DB and not to
jboss. I played a bit with your patch and just wanted to
post my experiences here:
First:
If I add your mapping
[B
BLOB
BLOB(1M)
to my jaws.xml file, byte[] types are even though
interpreted as JAVA_OBJECT and the mapping gets totally ignored.
Second:
I think your problem is related to your db or jdbc-driver
and not to jboss ?
I could store byte[] as BLOBS but was not able to read them
back. I got it working with another SQL-Type-Mapping for
MySQL. In MySQL the Type BLOB is only about 80kBytes, I
think, and if I use the type LONGBLOB in the mappings,
everythink works without your patch. MySQL just cutted the
end of my data because the data was to big for SQL-Type
BLOB ! It took my hours of research (including compiling
JBoss with your Patch) and then it was just such a stupid
mistake I made!
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=573828&group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-521108 ] Changes in DVOs not detected
Bugs item #521108, was opened at 2002-02-21 12:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=521108&group_id=22866 Category: JBossCMP >Group: v3.0 Rabbit Hole Status: Open >Resolution: Accepted Priority: 5 Submitted By: Ilya Perminov (iperminov) >Assigned to: Dain Sundstrom (dsundstrom) >Summary: Changes in DVOs not detected Initial Comment: If a bean has fields of non-primitive types, "TunedUpdates" work incorrectly: modification of these fields is not detected and they are not updated in the database. The problem is that field values are not cloned and the same objects are used in "old" and "current" states of the bean. -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:23 Message: Logged In: YES user_id=251431 I believe this bug also exists in JBossCMP. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=521108&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-554437 ] Finders methods not "concurrency Safe"?
Bugs item #554437, was opened at 2002-05-10 03:51
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=554437&group_id=22866
>Category: JAWS (inactive)
Group: v2.4 (stable)
Status: Open
>Resolution: Wont Fix
>Priority: 1
Submitted By: Paul Nicklin (paulnicklin)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Finders methods not "concurrency Safe"?
Initial Comment:
Hi all,
We're seeing an occasional problem where two calls to
finder methods made 'simultaneously' from different
instances of a session bean result in each being
returned a different remote object, but referring to
the same data.
This would not ordinarily be a big problem (the
concurrency/ optimistic locking system will prevent
the second update conflicting)
But in our case this entity bean is supporting the
High-Low pattern for giving out unique IDs, so two
Customers with the same key fails! (Won't go into
detail, but basically you have a table with "UniqueID
Name", "Unique ID NextValue" and you use this and
another number to give all your objects a unique ID -
I'd give you a URL but I don't have one- sorry!)
A bit of digging in the entity cache code (Isn't open
source wonderful!) says to me that if the row isn't in
the cache then two threads will run through the code
both saying...
"Is the row in the cache?"
"NO! - I'll go fetch it"
"Here's the row from the database, lets put it in the
cache"
"Here you go client, have a reference to the entity"
now, both call the getNextValue method and get the
next value and update the database - but because they
are not the same instance in they both update the
database to the same next value.
Then my code uses the value to create "customer" rows,
but the second fails because of a constraint violation
(Extract from CMPPersistenceManager.java)
public Object findEntity(Method finderMethod, Object[]
args, EntityEnterpriseContext ctx)
throws Exception {
// For now only optimize fBPK
if (finderMethod.getName().equals("findByPrimaryKey"))
{
Object key = ctx.getCacheKey();
if (key == null)
{
key = ((EntityCache)con.getInstanceCache
()).createCacheKey(args[0]);
}
if (con.getInstanceCache().isActive(key))
{
return key; // Object is active -> it exists -> no
need to call finder
}
}
// The store will find the entity and return the
primaryKey
Object id = store.findEntity(finderMethod, args, ctx);
// We return the cache key
return ((EntityCache) con.getInstanceCache
()).createCacheKey(id);
}
I'd suggest we check after calling the finder that the
object is STILL Not in the cache, reducing the window
of opportunity for duplication... currently the window
of opportunity for this failure includes the database
fetch time, a few hundred ms possibly, doing my change
would reduce this to a few microseconds.
Thanks for your perseverance in reading this far - any
comments? Am I completely up the wrong tree?
Suggestions welcome...
Paul Nicklin
[EMAIL PROTECTED]
--
>Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-09-12 12:23
Message:
Logged In: YES
user_id=251431
JAWS is no longer actively maintained. We will accept
patches, and will fix bugs can be fixed on a contract basis.
Furthermore, JAWS will be removed in JBoss 4.0.
--
Comment By: Bill Burke (patriot1burke)
Date: 2002-05-10 10:15
Message:
Logged In: YES
user_id=176497
Sorry to be harsh, but I don't believe you. Are you using
any custom container-configurations? Make sure you have
the correct interceptor chains, especially
EntityLockInterceptor and correct locking-policy
(QueuedPessmisticEJBLock). Also, make sure that your
PrimaryKey class implements hashCode and equals correctly.
#1, There is only one active valid instance of any Entity
bean. A finder call does NOT create an entity bean, nor
does it insert one into the cache. An entity bean instance
is only created when a method is invoked upon it.
#2 Your statements below are incorrect
"Is the row in the cache?"
"NO! - I'll go fetch it"
"Here's the row from the database, lets put it in the
cache"
"Here you go client, have a reference to the entity"
A finder does NOT fetch the row, nor does it put the row in
cache. The sql call for a finder only returns primary
keys. But, are you using "read-ahead"? Behaviour is
different with read-ahead.
My guess is that you've implemented your primary keys
incorrectly.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=554437&group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lis
[JBoss-dev] 3.2.0RC1 Missing org.jboss.invocation.Invocation class in minimaltarget
Has anyone tried running the "minimal" target built from CVS Branch_3_2? I tried it and get the following: === . JBoss Bootstrap Environment . JBOSS_HOME: c:\java\jboss-3.2.0RC1\bin\\.. . JAVA: c:\java\jdk1.3.1_04\bin\java . JAVA_OPTS: -Dprogram.name=run.bat . CLASSPATH: ;c:\java\jdk1.3.1_04\lib\tools.jar;c:\java\jboss-3.2.0RC1\bin\\run.jar . === . 13:13:16,901 INFO [Server] Starting JBoss (MX MicroKernel)... 13:13:16,901 INFO [Server] Release ID: JBoss [WonderLand] 3.2.0RC1 (build: Branch_3_2 200209111458) 13:13:16,917 INFO [Server] Home Dir: C:\java\jboss-3.2.0RC1 13:13:16,917 INFO [Server] Home URL: file:/C:/java/jboss-3.2.0RC1/ 13:13:16,917 INFO [Server] Library URL: file:/C:/java/jboss-3.2.0RC1/lib/ 13:13:16,917 INFO [Server] Patch URL: null 13:13:16,917 INFO [Server] Server Name: minimal 13:13:16,917 INFO [Server] Server Home Dir: C:\java\jboss-3.2.0RC1\server\minimal 13:13:16,917 INFO [Server] Server Home URL: file:/C:/java/jboss-3.2.0RC1/server/minimal/ 13:13:16,917 INFO [Server] Server Data Dir: C:\java\jboss-3.2.0RC1\server\minimal\data 13:13:16,917 INFO [Server] Server Temp Dir: C:\java\jboss-3.2.0RC1\server\minimal\tmp 13:13:16,917 INFO [Server] Server Config URL: file:/C:/java/jboss-3.2.0RC1/server/minimal/conf/ 13:13:16,917 INFO [Server] Server Library URL: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/ 13:13:16,917 INFO [Server] Root Deployemnt Filename: jboss-service.xml 13:13:16,933 INFO [Server] Starting General Purpose Architecture (GPA)... 13:13:17,214 INFO [ServerInfo] Java version: 1.3.1_04,Sun Microsystems Inc. 13:13:17,214 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.3.1_04-b02,Sun Microsystems Inc. 13:13:17,214 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86 13:13:17,245 INFO [ServiceController] Controller MBean online 13:13:17,323 INFO [MainDeployer] Creating 13:13:17,339 INFO [MainDeployer] Created 13:13:17,339 INFO [MainDeployer] Starting 13:13:17,339 INFO [MainDeployer] Started 13:13:17,417 INFO [JARDeployer] Creating 13:13:17,448 INFO [JARDeployer] Created 13:13:17,448 INFO [JARDeployer] Starting 13:13:17,448 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@1edf4 13:13:17,448 INFO [JARDeployer] Started 13:13:17,464 INFO [SARDeployer] Creating 13:13:17,480 INFO [SARDeployer] Created 13:13:17,480 INFO [SARDeployer] Starting 13:13:17,480 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@66a22b 13:13:17,495 INFO [SARDeployer] Started 13:13:17,495 INFO [Server] Core system initialized 13:13:17,511 INFO [MainDeployer] Starting deployment of package: file:/C:/java/jboss-3.2.0RC1/server/minimal/conf/jboss-service.xml 13:13:17,933 INFO [MainDeployer] Starting deployment of package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jboss-minimal.jar 13:13:17,948 INFO [JARDeployer] looking for nested deployments in : file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jboss-minimal.jar 13:13:17,964 INFO [MainDeployer] Deployed package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jboss-minimal.jar 13:13:17,964 INFO [MainDeployer] Starting deployment of package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnpserver.jar 13:13:17,964 INFO [JARDeployer] looking for nested deployments in : file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnpserver.jar 13:13:17,980 INFO [MainDeployer] Deployed package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnpserver.jar 13:13:17,980 INFO [MainDeployer] Starting deployment of package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/log4j.jar 13:13:18,058 INFO [JARDeployer] looking for nested deployments in : file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/log4j.jar 13:13:18,073 INFO [MainDeployer] Deployed package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/log4j.jar 13:13:18,073 INFO [MainDeployer] Starting deployment of package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnet.jar 13:13:18,073 INFO [JARDeployer] looking for nested deployments in : file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnet.jar 13:13:18,089 INFO [MainDeployer] Deployed package: file:/C:/java/jboss-3.2.0RC1/server/minimal/lib/jnet.jar 13:13:18,089 INFO [SARDeployer] looking for nested deployments in : file:/C:/java/jboss-3.2.0RC1/server/minimal/conf/jboss-service.xml 13:13:18,183 ERROR [MainDeployer] could not create deployment: file:/C:/java/jboss-3.2.0RC1/server/minimal/conf/jboss-service.xml java.lang.NoClassDefFoundError: org/jboss/invocation/Invocation at java.lang.Class.getMethods0(Native Method) at java.lang.Class.getMethods(Class.java:737) at org.jboss.mx.metadata.StandardMetaData.build(StandardMetaData.java:154) at org.jboss.mx.metadata.MBeanCapability.of(MBeanCapability.java:63) at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMB
[JBoss-dev] configuration of interceptors
Ok just had an interesting IM with hiram. He essentially has implemented the proxy factory we were talking about. I think he is missing the client/server side of it but we can very simply add these. Essentially it would revolve around a central proxyFactory.createProxy(Interfaces[], client-interceptors[], client-configurations[], server-interceptors[], serverconfigurations[] targetMbean); that returns a Dynamic Proxy, hooked up for remote/local calls with client and server side interceptors. If you are in one vm you can safely assume client=server and only configure one or the other. (meaning if one is null then don't configure transport it will be invm only) In the case of hiram he has only one aspect of it (and he calls it aspect everywhere) but that construct is really what we need. I also think we should have the "MBean" in there, even though we are talking about a POJO. I believe he has solid code for it and I am really interested in adding this to the base. I am not sure it is a JMX level construct (due to the pojo nature) but having the JMX base manage these configurations and associations between target and interceptors/configuration is the only sane way I can imagine to have these puppies manageable. I want visibility on that configuration for a given mbean (the generalized mbean againg being just a pojo or target). This is our generalized proxy factory. The AOP framework of the future is staring us in the eye... we got it. marc f xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504246 ] NULL and CMP field of primitive type
Bugs item #504246, was opened at 2002-01-16 01:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=504246&group_id=22866 >Category: JAWS (inactive) Group: v2.4 (stable) Status: Open >Resolution: Wont Fix >Priority: 1 Submitted By: Alexei Yudichev (sflexus) >Assigned to: Nobody/Anonymous (nobody) Summary: NULL and CMP field of primitive type Initial Comment: While loading entity in the case of CMP field of prvitive type and corresponding NULL database value java.lang.reflect.Field.set() throws NullPointerException like this: java.lang.NullPointerException at java.lang.reflect.Field.set(Native Method) at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.setCMPField Value(JDBCCommand.jav a:651) at org.jboss.ejb.plugins.jaws.jdbc.JDBCLoadEntityCommand.l oadOneEntity(JDBCLoad EntityCommand.java:217) ... I suppose it should be wrapped by more informative exception with the message like "cannot set the value CMP field of primitive type to NULL". -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:21 Message: Logged In: YES user_id=251431 JAWS is no longer actively maintained. We will accept patches, and will fix bugs can be fixed on a contract basis. Furthermore, JAWS will be removed in JBoss 4.0. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=504246&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-491536 ] NPE in JDBCCreateEntityCommand.java
Bugs item #491536, was opened at 2001-12-11 06:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=491536&group_id=22866 >Category: JAWS (inactive) Group: v2.4 (stable) Status: Open >Resolution: Wont Fix Priority: 1 Submitted By: Vincent Harcq (vharcq) >Assigned to: Nobody/Anonymous (nobody) Summary: NPE in JDBCCreateEntityCommand.java Initial Comment: This is an ooold one, that still fuck up a lot of users. It has to do with PK definition in ejb-jar.xml (I think). I will have a look someday. -- >Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-12 12:20 Message: Logged In: YES user_id=251431 JAWS is no longer actively maintained. We will accept patches, and will fix bugs can be fixed on a contract basis. Furthermore, JAWS will be removed in JBoss 4.0. -- Comment By: Vincent Harcq (vharcq) Date: 2001-12-13 07:14 Message: Logged In: YES user_id=125677 If not compounf PK, another case of error is when the PK field is not public, Verifier should check that at deployment -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=491536&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CMP vendor specific code
David Jencks wrote: > Maybe Jason has an idea. I guess we can do this with postgres and mysql, > but how about Oracle etc? is this legal? Yes. We will not be redistributing the driver with out application server. It will simply be available to internal developers of JBoss (this is a technical point). If a vendor comes to us and request us to remove it from our tree, we will and we will remove the custom support code (they have a choice). -dain --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CMP vendor specific code
On 2002.09.12 12:24:19 -0400 Dain Sundstrom wrote: > Alex Loubyansky wrote: > > But I have a couple of questions. > > > > 1. the wrapping classes are in local-ra-jdbc-libs.jar. I need this > > jar in the classpath during compilation. According to recent > > buildfragments changes, what is the right place to add in the > > classpath: modules.ent or build.xml? > > David? Jason? modules.ent. > > > 2. using wrapping classes makes CMP code dependent on connector > > implementation. What do you think about it? > > Not a big deal. I was going to happen soon anyway. > > > 3. compilation also requires driver or a stub for the dirver. As Dain > > suggested, I should checkin the binary in the thirdparty module. > > Sorry, Dain, did you mean the driver or a stub? > > I say check the binary driver jar into the thirdparty module. David or > Jason, how should Alex tag these files (cvs command and tag name). Maybe Jason has an idea. I guess we can do this with postgres and mysql, but how about Oracle etc? is this legal? thanks david > > -dain > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CMP vendor specific code
Alex Loubyansky wrote: > But I have a couple of questions. > 1. the wrapping classes are in local-ra-jdbc-libs.jar. I need this > jar in the classpath during compilation. According to recent > buildfragments changes, what is the right place to add in the > classpath: modules.ent or build.xml? David? Jason? > 2. using wrapping classes makes CMP code dependent on connector > implementation. What do you think about it? Not a big deal. I was going to happen soon anyway. > 3. compilation also requires driver or a stub for the dirver. As Dain > suggested, I should checkin the binary in the thirdparty module. > Sorry, Dain, did you mean the driver or a stub? I say check the binary driver jar into the thirdparty module. David or Jason, how should Alex tag these files (cvs command and tag name). -dain --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-607684 ] jboss.net fails to deploy on catalina
Bugs item #607684, was opened at 2002-09-11 09:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=607684&group_id=22866 Category: JBossSOAP Group: v3.0 Rabbit Hole Status: Open >Resolution: Remind >Priority: 3 Submitted By: Dr. Christoph Georg Jung (cgjung) Assigned to: Dr. Christoph Georg Jung (cgjung) Summary: jboss.net fails to deploy on catalina Initial Comment: Actually, there are two symptoms. One is appearing in head and has to do with exploded deployment leading to nullpointers in EmbeddedCatalinaService. The other one is in 3.0.1 release and seems to hint to a wrong servlet mapping. -- >Comment By: Dr. Christoph Georg Jung (cgjung) Date: 2002-09-12 18:22 Message: Logged In: YES user_id=175199 head bug was resolved due to wrong installation order in catalinaservice. tested head successfully. 3.0.x will be done either by a backport or bugfix, whatever appears more suitable. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=607684&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-608458 ] subdeployments in wsr
Bugs item #608458, was opened at 2002-09-12 18:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608458&group_id=22866 Category: JBossSOAP Group: v4.0 Status: Open Resolution: None Priority: 3 Submitted By: Dr. Christoph Georg Jung (cgjung) Assigned to: Dr. Christoph Georg Jung (cgjung) Summary: subdeployments in wsr Initial Comment: have been accidently disabled. Should be enabled, again -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608458&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CMP vendor specific code
Hello, guys! David and Dain, I guess, you are the persons who can help me here. Currently, I am writting CMP code that supports db-vendor specific API. I need to cast PreparedStatement/Statement to vendor specific ones. So, the statements need to be casted to WrappedStatement first and then getUnderlyingStatement() method should be called. This works fine. But I have a couple of questions. 1. the wrapping classes are in local-ra-jdbc-libs.jar. I need this jar in the classpath during compilation. According to recent buildfragments changes, what is the right place to add in the classpath: modules.ent or build.xml? 2. using wrapping classes makes CMP code dependent on connector implementation. What do you think about it? 3. compilation also requires driver or a stub for the dirver. As Dain suggested, I should checkin the binary in the thirdparty module. Sorry, Dain, did you mean the driver or a stub? Thank you. alex --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Dynamic configuration of XMLLoginConfig
There is a service that does this in the testsuite. XMLLoginConfigs chain so that multiple configs can be active. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Peter Antman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 12, 2002 8:03 AM Subject: [JBoss-dev] Dynamic configuration of XMLLoginConfig > Hi, > when converting some old adapters I had finally the chance to look at > the new JAAS based autentication stuff for JCA adapters. Really neat. > But one thing is somewhat iritating. It is not possible to configure a > new adapter and hot deploy it. At least I could not figure out a > standard way of doing it. Why? Because the new autentication scheme is > dependand on the availability of a security realm in login-config.xml. > To do this you have to restart the server. > > To solve this I wrote I little MBean to dynamically configure the > XMLLoginConfig. Basically it let you set the real setting in the same > *-service.xml file as you configure your adapter, ie: > > code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" >name="jboss.jca:service=LocalTxCM,name=PostgresDS"> > >code="org.jboss.resource.security.LoginConfigurator" >name="jboss.jca:service=AuthenticationInfo,name=PostgresDS"> >optional-attribute-name="LoginConfig">jboss.security:service=XMLLoginConfig > > > > "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required"> >yourprincipal >yourusername >yourpassword >jboss.jca:service=LocalTxCM,name=PostgresDS > > > > > > > bla,bla... > > I don't know if this goes agains some security restrictions (apart from > it probably not working with a security manager installed and the > correct right sto do this sort of stuff is not turned of). > > Basically I am wondering this: any interest in me checking this > little utility class in (and perhaps refactor XMLLoginConfig so that the > XML parsing code does not need to be in two places)? Any ideas about > which is the best place? org.jboss.resource.security or > org.jboss.security.auth.login or perhaps not at all, what do you say > Scott? > > //Peter > -- > > Peter Antman Chief Systems Architect, Business Development > Technology in Media, Box 34105 100 26 Stockholm > WWW: http://www.tim.se WWW: http://www.backsource.org > Email: [EMAIL PROTECTED] > Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Dynamic configuration of XMLLoginConfig
Hi, when converting some old adapters I had finally the chance to look at the new JAAS based autentication stuff for JCA adapters. Really neat. But one thing is somewhat iritating. It is not possible to configure a new adapter and hot deploy it. At least I could not figure out a standard way of doing it. Why? Because the new autentication scheme is dependand on the availability of a security realm in login-config.xml. To do this you have to restart the server. To solve this I wrote I little MBean to dynamically configure the XMLLoginConfig. Basically it let you set the real setting in the same *-service.xml file as you configure your adapter, ie: jboss.security:service=XMLLoginConfig yourprincipal yourusername yourpassword jboss.jca:service=LocalTxCM,name=PostgresDS bla,bla... I don't know if this goes agains some security restrictions (apart from it probably not working with a security manager installed and the correct right sto do this sort of stuff is not turned of). Basically I am wondering this: any interest in me checking this little utility class in (and perhaps refactor XMLLoginConfig so that the XML parsing code does not need to be in two places)? Any ideas about which is the best place? org.jboss.resource.security or org.jboss.security.auth.login or perhaps not at all, what do you say Scott? //Peter -- Peter AntmanChief Systems Architect, Business Development Technology in Media, Box 34105 100 26 Stockholm WWW: http://www.tim.se WWW: http://www.backsource.org Email: [EMAIL PROTECTED] Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-608412 ] VerifyError when loading class from War
Bugs item #608412, was opened at 2002-09-12 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608412&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Steve Wolfangel (swolfangel) Assigned to: Nobody/Anonymous (nobody) Summary: VerifyError when loading class from War Initial Comment: JBoss Release: JBoss-3.0.2 CVSTag=JBoss_3_0_2 Home Dir: D:\jb\server30\jboss Home URL: file:/D:/jb/server30/jboss/ Library URL: file:/D:/jb/server30/jboss/lib/ Patch URL: nul Root Deployemnt Filename: jboss-service.xml Starting General Purpose Architecture (GPA)... Java version: 1.3.1_01,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Client VM 1.3.1_01,Sun Microsystems Inc. OS-System: Windows NT 4.0,x86l 09:41:59,181 INFO [Server] Root Deployemnt Filename: jboss-service.xml 09:41:59,197 INFO [Server] Starting General Purpose Architecture (GPA)... 09:41:59,885 INFO [ServerInfo] Java version: 1.3.1_01,Sun Microsystems Inc. 09:41:59,885 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.3.1_01,Sun Microsystems Inc. 09:41:59,900 INFO [ServerInfo] OS-System: Windows NT 4.0,x86 I have encountered the following error when running on Jboss 3.0. This error is related to the functionality of a web application based on the struts framework. The error occurs when the struts framework attempts to load a class that is in the classpath of the web application using the Class.forName(String) method. The following is the stack trace for the error. 09:37:53,431 WARN [jbossweb] WARNING: modelerweb: Error creating Action instance for path '/GetLoginInfo', class name 'com.metamatrix.modelerwe b.struts.action.login.GetLoginInfoAction' java.lang.VerifyError: (class: com/metamatrix/modelerweb/struts/action/login/ GetLoginInfoAction, method: perform signature: (Lorg/apache/struts/ action/ActionMapping;Lorg/apache/struts/action/A ctionForm;Ljavax/servlet/http/HttpServletRequest;L javax/servlet/http/HttpServletRespons -} at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:120) at com.metamatrix.webtoolbox.struts.servlet.ActionSe rvlet.processActionCreate(ActionServlet.java:56) at org.apache.struts.action.ActionServlet.process (ActionServlet.java:1576) at org.apache.struts.action.ActionServlet.doGet (ActionServlet.java:491) at javax.servlet.http.HttpServlet.service (HttpServlet.java:740) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:344) at org.mortbay.jetty.servlet.WebApplicationHandler.dis patch(WebApplicationHandler.java:313) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:554) at org.mortbay.jetty.servlet.WebApplicationHandler.ha ndle(WebApplicationHandler.java:199) at org.mortbay.http.HttpContext.handle (HttpContext.java:1572) at org.mortbay.http.HttpContext.handle (HttpContext.java:1522) at org.mortbay.http.HttpServer.service (HttpServer.java:795) at org.jboss.jetty.Jetty.service(Jetty.java:531) at org.mortbay.http.HttpConnection.service (HttpConnection.java:784) at org.mortbay.http.HttpConnection.handleNext (HttpConnection.java:941) at org.mortbay.http.HttpConnection.handle (HttpConnection.java:799) at org.mortbay.http.SocketListener.handleConnection (SocketListener.java:186) at org.mortbay.util.ThreadedServer.handle (ThreadedServer.java:322) at org.mortbay.util.ThreadPool$JobRunner.run (ThreadPool.java:716) at java.lang.Thread.run(Thread.java:484) 09:37:53,525 INFO [jbossweb] modelerweb: Error creating Action instance for path '/GetLoginInfo', class name 'com.metamatrix.modelerweb.struts. action.login.GetLoginInfoAction': java.lang.VerifyError: (class: com/metamatrix/modelerweb/struts/action/login/ GetLoginInfoAction, method: perfo rm signature: (Lorg/apache/struts/action/ActionMapping;Lorg/ap ache/struts/action/ActionForm;Ljavax/servlet/http /HttpServletRequest;Ljavax/servle t/http/HttpServletRespons -} Note the strange characters at the end of the error message. Almost like the class is not able to be read in for some reason. I have recompiled this class and all classes in the project several times and have experienced this error every time i re- deploy them in the Jboss environment. I was not having this problem with an early version of jboss (jboss-3.0.1RC1 I believe) It occured as soon as I upgraded. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608412&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 12-September-2002
Number of tests run: 934
Successful tests: 924
Errors:4
Failures: 6
[time of test: 12 September 2002 5:50 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1_03-69]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.2]
See http://lubega.com/testarchive/${build.uid} for details of this test.
See http://lubega.com for general test information.
NOTE: If there are any errors shown above - this mail is only highlighting
them - it is NOT indicating that they are being looked at by anyone.
Remember - if a test becomes broken after your changes - fix it or fix the test!
Oh dear - still got some errors!
Thanks for all your effort - we really do love you!
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-575307 ] shutdown problem with JBoss
Bugs item #575307, was opened at 2002-06-29 00:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=575307&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Fixed Priority: 9 Submitted By: T. Subramanian (t_subbu) Assigned to: Scott M Stark (starksm) Summary: shutdown problem with JBoss Initial Comment: While starting the server even before initialization completes, if we try to kill it using ctrl-c, then JBoss hangs in the middle. Thread dump is attached with this mail. Reason is UnifiedClassLoader created from MainDeployer was locked by main thread. In between when we try to kill the JBoss shutdown thread tries to lock the same UnifiedClassLoader from ServiceController which results in dead lock. I tried twice and both the times I am able to reproduce it -- >Comment By: Scott M Stark (starksm) Date: 2002-09-12 05:28 Message: Logged In: YES user_id=175228 This is fixed for the 3.0.3 and 3.2beta releases -- Comment By: Scott M Stark (starksm) Date: 2002-07-28 23:30 Message: Logged In: YES user_id=175228 I did just see this error today and attached is another deadlock dump. -- Comment By: Scott M Stark (starksm) Date: 2002-07-26 12:25 Message: Logged In: YES user_id=175228 Works for me with the 3.0 branch code post the 3.0.1RC1 release. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=575307&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] JBoss.net now supports Axis RC1
Thanks scott, That saves me a lot of headaches ;-) CGJ -Ursprüngliche Nachricht- Von: Scott M Stark [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 12. September 2002 11:36 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] JBoss.net now supports Axis RC1 I saw the NPE while testing the 3.0.2 bundle. It was caused by the EmbeddedCatalinaServiceSX registering as a war deployer before it was fully started. This has been fixed in all branches. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Bruce Scharlau" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 09, 2002 7:40 AM Subject: Re: [JBoss-dev] JBoss.net now supports Axis RC1 > At 18:49 06/09/2002 +0200, you wrote: > >One of the most requested features is now in "head" (along with some > >bugfixes and some nice deployment structure changes that remove the > >dependency of > >AxisService to the WebContainer). > > > >Axis will go 1.0 in a week or so which should be trivial to > >incorporate then. > > > >Are there any special backport requirements? Otherwise, I would go > >reintegrating it into 3.2, then. > > > >Best, > >CGJ > > > > > >### > > Christoph and Friederich, > > thanks for getting this out guys! I tried it in jetty, and it looked > nice. > I tried it in tomcat and it crashed here: > > 2002-09-09 15:33:55,674 > INFO [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] deploy, > ctxPath=/jboss-net, > warUrl=file:/D:/jboss-src/jboss-all/build/output/jboss-4.0.0alpha/server/def ault/deploy/jboss-net.sar/jboss-net.war/ > 2002-09-09 15:33:55,684 ERROR > [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Error during deploy > java.lang.NullPointerException > at > org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(EmbeddedCa talinaServiceSX.java:389) > at > org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedCatal inaServiceSX.java:331) > at > org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:468) > > I don't have time to look at this any more today, but wanted any > initial > thoughts you might have, and I can hopefully get it sorted tomorrow. > > > cheers, > > Bruce > > Dr. Bruce Scharlau > Dept. of Computing Science > University of Aberdeen > Aberdeen AB24 3UE > 01224 272193 > http://www.csd.abdn.ac.uk/~bscharla > mailto:[EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582428 ] ejb remove cause IllegalStateException
Bugs item #582428, was opened at 2002-07-16 22:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=582428&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Andrew Lau (andrewlau4) Assigned to: Bill Burke (patriot1burke) Summary: ejb remove cause IllegalStateException Initial Comment: This problem happens in jboss 3.0 and 3.0.1 RC1 I have a parent entity bean that I have set to 'cascade delete' all its children. But when I try to remove that bean, I sometimes got the following exception: . java.lang.IllegalStateException: removing bean lock and it has tx set! at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.r emoveRef(QueuedPessimisticEJBLock.java:469) at org.jboss.ejb.BeanLockManager.removeLockRef (BeanLockManager.java:78) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockInterceptor.java:124) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreationInterceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:96) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:167) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:61) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:129) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:166) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.invokeRemoveRelation (JDBCCMRFieldBridge.java:759) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.destroyRelationLinks (JDBCCMRFieldBridge.java:696) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.destroyRelationLinks (JDBCCMRFieldBridge.java:674) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet.clear (RelationSet.java:163) .. But I may have found a quick solution for now. The IllegalStateException exception only happens when I call EJBLocalObject remove() method. Now I changed my code so it calls EJBLocalHome remove() method instead. Since then, it seems working fine so far. -- Comment By: Alexei Yudichev (sflexus) Date: 2002-09-12 12:39 Message: Logged In: YES user_id=345880 Also it happens sometimes when I try to invoke cmr set method with many-to-one relationship. Is this bug about to be fixed in nearest future? Because otherwise I will have to move our project from jboss or from ejb 2.0 and it will take much time. 2002-09-12 12:29:08,719 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException, causedBy: java.lang.IllegalStateException: removing bean lock and it has tx set! at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.removeRef(QueuedPessimisticEJBLock.java:473) at org.jboss.ejb.BeanLockManager.removeLockRef(BeanLockManager.java:78) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:124) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:232) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.invokeGetRelatedId(JDBCCMRFieldBridge.java:640) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.createRelationLinks(JDBCCMRFieldBridge.java:570) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:545) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setValue(JDBCCMRFieldBridge.java:483) at org.jboss.ejb.plugins.cmp.bridge.EntityBridgeInvocationHandler.invoke(EntityBridgeInvocationHandler.java:125) at org.jboss.proxy.compiler.Runtime.invoke(Runtime.java:59) at com.tw.mms.ejb.SlideBean$Proxy.setSound() at com.tw.mms.ejb.SlideBean.setSoundId(SlideBean.java:185) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1191) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationIn
Re: [JBoss-dev] JBoss.net now supports Axis RC1
I saw the NPE while testing the 3.0.2 bundle. It was caused by the EmbeddedCatalinaServiceSX registering as a war deployer before it was fully started. This has been fixed in all branches. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Bruce Scharlau" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 09, 2002 7:40 AM Subject: Re: [JBoss-dev] JBoss.net now supports Axis RC1 > At 18:49 06/09/2002 +0200, you wrote: > >One of the most requested features is now in "head" (along with some > >bugfixes and some nice deployment structure changes that remove the > >dependency of > >AxisService to the WebContainer). > > > >Axis will go 1.0 in a week or so which should be trivial to incorporate then. > > > >Are there any special backport requirements? Otherwise, I would go > >reintegrating it into 3.2, then. > > > >Best, > >CGJ > > > > > >### > > Christoph and Friederich, > > thanks for getting this out guys! I tried it in jetty, and it looked nice. > I tried it in tomcat and it crashed here: > > 2002-09-09 15:33:55,674 > INFO [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] deploy, > ctxPath=/jboss-net, > >warUrl=file:/D:/jboss-src/jboss-all/build/output/jboss-4.0.0alpha/server/default/deploy/jboss-net.sar/jboss-net.war/ > 2002-09-09 15:33:55,684 ERROR > [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Error during deploy > java.lang.NullPointerException > at > >org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(EmbeddedCatalinaServiceSX.java:389) > at > >org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedCatalinaServiceSX.java:331) > at > org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:468) > > I don't have time to look at this any more today, but wanted any initial > thoughts you might have, and I can hopefully get it sorted tomorrow. > > > cheers, > > Bruce > > Dr. Bruce Scharlau > Dept. of Computing Science > University of Aberdeen > Aberdeen AB24 3UE > 01224 272193 > http://www.csd.abdn.ac.uk/~bscharla > mailto:[EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582428 ] ejb remove cause IllegalStateException
Bugs item #582428, was opened at 2002-07-16 22:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=582428&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Andrew Lau (andrewlau4) Assigned to: Bill Burke (patriot1burke) Summary: ejb remove cause IllegalStateException Initial Comment: This problem happens in jboss 3.0 and 3.0.1 RC1 I have a parent entity bean that I have set to 'cascade delete' all its children. But when I try to remove that bean, I sometimes got the following exception: . java.lang.IllegalStateException: removing bean lock and it has tx set! at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.r emoveRef(QueuedPessimisticEJBLock.java:469) at org.jboss.ejb.BeanLockManager.removeLockRef (BeanLockManager.java:78) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockInterceptor.java:124) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreationInterceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:96) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:167) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:61) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:129) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:166) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.invokeRemoveRelation (JDBCCMRFieldBridge.java:759) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.destroyRelationLinks (JDBCCMRFieldBridge.java:696) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.destroyRelationLinks (JDBCCMRFieldBridge.java:674) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet.clear (RelationSet.java:163) .. But I may have found a quick solution for now. The IllegalStateException exception only happens when I call EJBLocalObject remove() method. Now I changed my code so it calls EJBLocalHome remove() method instead. Since then, it seems working fine so far. -- Comment By: Alexei Yudichev (sflexus) Date: 2002-09-12 10:57 Message: Logged In: YES user_id=345880 I use 3.0.2 and for me it happens every time I remove cmp20 bean which has child beans with cascade deletion configured or instead when I try to remove children myself inside parent bean's ejbRemove() method. Stack trace top is: javax.ejb.TransactionRolledbackLocalException: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set! at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:224) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:232) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.invokeRemoveRelation(JDBCCMRFieldBridge.java:700) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:616) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:594) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:528) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.removeFromRelations(JDBCRemoveEntityCommand.java:140) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.execute(JDBCRemoveEntityCommand.java:70) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.removeEntity(JDBCStoreManager.java:635) at org.jboss.ejb.plugins.CMPPersistenceManager.removeEntity(CMPPersistenceManager.java:542) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.removeEntity(CachedConnectionInterceptor.java:431) at org.jboss.ejb.EntityContainer.remove(EntityContainer.java:506) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1170) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:95) at org.jboss.ejb.plugins.EntitySynchronizatio
[JBoss-dev] [ jboss-Bugs-582428 ] ejb remove cause IllegalStateException
Bugs item #582428, was opened at 2002-07-16 22:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=582428&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Andrew Lau (andrewlau4) Assigned to: Bill Burke (patriot1burke) Summary: ejb remove cause IllegalStateException Initial Comment: This problem happens in jboss 3.0 and 3.0.1 RC1 I have a parent entity bean that I have set to 'cascade delete' all its children. But when I try to remove that bean, I sometimes got the following exception: . java.lang.IllegalStateException: removing bean lock and it has tx set! at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.r emoveRef(QueuedPessimisticEJBLock.java:469) at org.jboss.ejb.BeanLockManager.removeLockRef (BeanLockManager.java:78) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockInterceptor.java:124) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreationInterceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:96) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:167) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:61) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:129) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:166) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.invokeRemoveRelation (JDBCCMRFieldBridge.java:759) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.destroyRelationLinks (JDBCCMRFieldBridge.java:696) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBri dge.destroyRelationLinks (JDBCCMRFieldBridge.java:674) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet.clear (RelationSet.java:163) .. But I may have found a quick solution for now. The IllegalStateException exception only happens when I call EJBLocalObject remove() method. Now I changed my code so it calls EJBLocalHome remove() method instead. Since then, it seems working fine so far. -- Comment By: Alexei Yudichev (sflexus) Date: 2002-09-12 10:52 Message: Logged In: YES user_id=345880 I use 3.0.2 and for me it happens every time I remove cmp20 bean which has child beans with cascade deletion configured or instead when I try to remove children myself inside parent bean's ejbRemove() method. Stack trace top is: javax.ejb.TransactionRolledbackLocalException: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set! at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:224) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:232) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.invokeRemoveRelation(JDBCCMRFieldBridge.java:700) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:616) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:594) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:528) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.removeFromRelations(JDBCRemoveEntityCommand.java:140) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.execute(JDBCRemoveEntityCommand.java:70) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.removeEntity(JDBCStoreManager.java:635) at org.jboss.ejb.plugins.CMPPersistenceManager.removeEntity(CMPPersistenceManager.java:542) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.removeEntity(CachedConnectionInterceptor.java:431) at org.jboss.ejb.EntityContainer.remove(EntityContainer.java:506) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1170) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:95) at org.jboss.ejb.plugins.EntitySynchronizatio
