Nope... AlertGroupLocal is an entity bean in my ejb.jar :(
There has got to be someone writing MBeans using Entity/Session Beans
that aren't contained in the same sar file... so I'm assuming I've just
got the classes organized improperly.
Brian Macy
David Jencks wrote:
> There is some code that makes mbeans wait for their classes, but it only
> works in jboss 4 (and something like 3.0RC1, I should have written a
> testcase when I wrote the code) I'm not sure if the missing class is the
> mbean class: if not, this feature may not work too well for you.
>
> I'd recommend deploying in an .ear since all classes from anywhere in the
> .ear are loaded before anything starts getting created.
>
> david jenck
>
> On 2002.08.22 01:00:22 -0400 Brian Macy wrote:
>
>>Actually I'm totally confused here... maybe I'm deploying this stuff
>>entirely wrong. I can't see how the MBean is going to load without
>>knowing about all the classes... well, let's just say it doesn't :)
>>
>>
>>21:49:20,339 ERROR [URLDeploymentScanner] MBeanException: Exception in
>>MBean operation 'checkIncompleteDeployments()'
>>Cause: Incomplete Deployment listing:
>>Packages waiting for a deployer:
>> <none>
>>Incompletely deployed packages:
>>[org.jboss.deployment.DeploymentInfo@ee199cbf {
>>url=file:/opt/jboss-3.0.1/server/default/deploy/aa-service.sar }
>> deployer: org.jboss.deployment.SARDeployer@edc073
>> status: Deployment FAILED reason: instantiating
>>com.pany.aggregator.AlertAggregator failed:
>>java.lang.NoClassDefFoundError: com/pany/interfaces/AlertGroupLocal; -
>>nested throwable: (RuntimeErrorException: instantiating
>>com.pany.aggregator.AlertAggregator failed:
>>java.lang.NoClassDefFoundError: com/pany/interfaces/AlertGroupLocal
>>Cause: java.lang.NoClassDefFoundError:
>>com/pany/interfaces/AlertGroupLocal)
>> state: FAILED
>> watch: file:/opt/jboss-3.0.1/server/default/deploy/aa-service.sar
>> lastDeployed: 1029991746191
>> lastModified: 1029991746000
>> mbeans:
>>]MBeans waiting for classes:
>> <none>
>>MBeans waiting for other MBeans:
>> <none>
>>
>>The interfaces include:
>>- EJB Data classes
>>- EJB PK classes
>>- EJB Local/Remote interfaces
>>- EJB Local/Remote Home interfaces
>>- A couple misc non-EJB classes
>>
>>What if any should be in the sar? Also, if it matters, the MBean will
>>eventually be deployed in an entirely seperate JBoss instance on a
>>seperate machine (there are some reasons).
>>
>>Should the common non-ejb classes be put in a seperate jar file... and
>>then put either in the lib directory or have absolute pathname
>>dependencies created?
>>
>>Should the common ejb classes also be put in such a jar?
>>
>>Brian Macy
>>
>>
>>Scott M Stark wrote:
>>
>>>You can't have dependent classes in indepdent deployment units with the
>>>same classes in both. If you remove the ejb interfaces from the sar you
>>
>>will
>>
>>>be able to redeploy the ejb as well as the sar.
>>>
>>>xxxxxxxxxxxxxxxxxxxxxxxx
>>>Scott Stark
>>>Chief Technology Officer
>>>JBoss Group, LLC
>>>xxxxxxxxxxxxxxxxxxxxxxxx
>>>----- Original Message -----
>>>From: "Brian Macy" <[EMAIL PROTECTED]>
>>>To: <[EMAIL PROTECTED]>
>>>Sent: Wednesday, August 21, 2002 10:01 PM
>>>Subject: [JBoss-user] Linkage error 3.0.1 final...
>>>
>>>
>>>
>>>
>>>>I've been getting this for a while so I figured I'd ask. I have an
>>>
>>MBean
>>
>>>>in service.sar and my EJBs in ejb.jar. ejb.jar contains all my EJB
>>>>classes, EJB interfaces, and misc non-EJB classes. service.sar contains
>>>
>>>>only the MBean, the EJB interfaces, and misc non-EJB classes.
>>>>
>>>>If I simply touch service.sar while JBoss is running I get a linkage
>>>
>>error:
>>
>>>>2002-08-21 18:52:50,006 ERROR [com.pany.aggregator.AlertAggregator]
>>>>findByName really screwed: java.lang.LinkageError: loader constraints
>>>>violated when linking com/pany/interfaces/AlertGroupLocal class
>>>>2002-08-21 18:52:50,007 ERROR [STDERR] java.lang.LinkageError: loader
>>>>constraints violated when linking com/pany/interfaces/AlertGroupLocal
>>>
>>class
>>
>>>>2002-08-21 18:52:50,012 ERROR [STDERR] at
>>>>com.pany.aggregator.AlertAggregator.startService(AlertAggregator.java:85)
>>>>2002-08-21 18:52:50,013 ERROR [STDERR] at
>>>>org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
>>>>2002-08-21 18:52:50,013 ERROR [STDERR] at
>>>>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This sf.net email is sponsored by: OSDN - Tired of that same old
>>>cell phone? Get a new here for FREE!
>>>https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
>>>_______________________________________________
>>>JBoss-user mailing list
>>>[EMAIL PROTECTED]
>>>https://lists.sourceforge.net/lists/listinfo/jboss-user
>>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by: OSDN - Tired of that same old
>>cell phone? Get a new here for FREE!
>>https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
>>_______________________________________________
>>JBoss-user mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/jboss-user
>>
>>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
