[Installation, Configuration & DEPLOYMENT] - Re: Jboss build failure on Solaris SPARC with error can n
by apsingh1
Trying to build jboss4.0.5 and it failes. Please see details as follows..
"apsingh1" wrote : # build.sh
| Searching for build.xml ...
| Buildfile: /var/im/jboss/jboss-4.0.5.GA-src/build/build.xml
|
| check.inhibit.downloads:
|
| check.proxy:
|
| set.proxy.withoutauth:
|
| set.proxy.auth:
|
| set.proxy:
|
| createthirdparty:
|
| _buildmagic:init:
| Trying to override old definition of task property
|
| _buildmagic:init:local-properties:
|
| _buildmagic:init:buildlog:
|
| configure:
| [echo] groups: most
| [echo] modules: jmx,test,system,naming,j2ee,transaction,security,server,deployment,messaging,connector,remoting-int,jaxrpc,cluster,varia,iiop,management,console,aspects,tomcat,hibernate-int
|
| init:
|
| _buildmagic:modules:most:
|
| ======================================================================
| == Executing 'most' in module 'jmx'...
| ==
|
| _buildmagic:init:
|
| configure:
| Overriding previous definition of reference to xdoclet.task.classpath
|
| init:
|
| _buildmagic:build-bypass-checker:
|
| _buildmagic:build-bypass-notice:
|
| _buildmagic:build-bypass-check:
|
| output:
|
| _buildmagic:init:
|
| init:
|
| compile-mbean-sources:
|
| _default:compile-classes:
| [javac] Compiling 594 source files to /var/im/jboss/jboss-4.0.5.GA-src/jmx/output/classes
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/notcompliant/support/InterfaceProblemsMBean.java:25: cannot resolve symbol
| [execmodules] symbol : class InterfaceProblemsSuperMBean
| [execmodules] location: interface test.compliance.notcompliant.support.InterfaceProblemsMBean
| [execmodules] extends InterfaceProblemsSuperMBean
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/implementation/loading/LoaderRepositoryTEST.java:31: warning: javax.management.loading.DefaultLoaderRepository in javax.management.loading has been deprecated
| [execmodules] import javax.management.loading.DefaultLoaderRepository;
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/org/jboss/mx/notification/MBeanServerListenerRegistry.java:94: cannot resolve symbol
| [execmodules] symbol : class MBeanServerListenerRegistrationFactory
| [execmodules] location: class org.jboss.mx.notification.MBeanServerListenerRegistry
| [execmodules] registry = new ListenerRegistry(new MBeanServerListenerRegistrationFactory(name, broadcaster));
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/notification/NotificationSUITE.java:54: cannot resolve symbol
| [execmodules] symbol : class AttributeChangeNotificationFilterTestCase
| [execmodules] location: class test.compliance.notification.NotificationSUITE
| [execmodules] suite.addTest(new TestSuite(AttributeChangeNotificationFilterTestCase.class));
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/notification/NotificationSUITE.java:55: cannot resolve symbol
| [execmodules] symbol : class NotificationBroadcasterSupportTestCase
| [execmodules] location: class test.compliance.notification.NotificationSUITE
| [execmodules] suite.addTest(new TestSuite(NotificationBroadcasterSupportTestCase.class));
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/openmbean/OpenMBeanSUITE.java:63: cannot resolve symbol
| [execmodules] symbol : class OpenMBeanConstructorInfoSupportTestCase
| [execmodules] location: class test.compliance.openmbean.OpenMBeanSUITE
| [execmodules] suite.addTest(new TestSuite(OpenMBeanConstructorInfoSupportTestCase.class));
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/implementation/loading/LoaderRepositoryTEST.java:100: warning: javax.management.loading.DefaultLoaderRepository in javax.management.loading has been deprecated
| [execmodules] DefaultLoaderRepository.loadClass(classes);
| [execmodules] ^
| [execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/implementation/notification/NotificationSUITE.java:54: cannot resolve symbol
| [execmodules] symbol : class AsynchNotificationBroadcasterSupportTestCase
| [execmodules] location: class test.implementation.notification.NotificationSUITE
| [execmodules] suite.addTest(new TestSuite(AsynchNotificationBroadcasterSupportTestCase.class));
| [execmodules] ^
| [execmodules] 6 errors
| [execmodules] 2 warnings
|
| BUILD FAILED
| /var/im/jboss/jboss-4.0.5.GA-src/tools/etc/buildmagic/buildmagic.ent:435: Compile failed; see the compiler error output for details.
|
| Total time: 20 seconds
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220423#4220423
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220423
17 years, 1 month
[Installation, Configuration & DEPLOYMENT] - Jboss Installation failure on Solaris SPARC with error can n
by apsingh1
# build.sh
Searching for build.xml ...
Buildfile: /var/im/jboss/jboss-4.0.5.GA-src/build/build.xml
check.inhibit.downloads:
check.proxy:
set.proxy.withoutauth:
set.proxy.auth:
set.proxy:
createthirdparty:
_buildmagic:init:
Trying to override old definition of task property
_buildmagic:init:local-properties:
_buildmagic:init:buildlog:
configure:
[echo] groups: most
[echo] modules: jmx,test,system,naming,j2ee,transaction,security,server,deployment,messaging,connector,remoting-int,jaxrpc,cluster,varia,iiop,management,console,aspects,tomcat,hibernate-int
init:
_buildmagic:modules:most:
======================================================================
== Executing 'most' in module 'jmx'...
==
_buildmagic:init:
configure:
Overriding previous definition of reference to xdoclet.task.classpath
init:
_buildmagic:build-bypass-checker:
_buildmagic:build-bypass-notice:
_buildmagic:build-bypass-check:
output:
_buildmagic:init:
init:
compile-mbean-sources:
_default:compile-classes:
[javac] Compiling 594 source files to /var/im/jboss/jboss-4.0.5.GA-src/jmx/output/classes
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/notcompliant/support/InterfaceProblemsMBean.java:25: cannot resolve symbol
[execmodules] symbol : class InterfaceProblemsSuperMBean
[execmodules] location: interface test.compliance.notcompliant.support.InterfaceProblemsMBean
[execmodules] extends InterfaceProblemsSuperMBean
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/implementation/loading/LoaderRepositoryTEST.java:31: warning: javax.management.loading.DefaultLoaderRepository in javax.management.loading has been deprecated
[execmodules] import javax.management.loading.DefaultLoaderRepository;
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/org/jboss/mx/notification/MBeanServerListenerRegistry.java:94: cannot resolve symbol
[execmodules] symbol : class MBeanServerListenerRegistrationFactory
[execmodules] location: class org.jboss.mx.notification.MBeanServerListenerRegistry
[execmodules] registry = new ListenerRegistry(new MBeanServerListenerRegistrationFactory(name, broadcaster));
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/notification/NotificationSUITE.java:54: cannot resolve symbol
[execmodules] symbol : class AttributeChangeNotificationFilterTestCase
[execmodules] location: class test.compliance.notification.NotificationSUITE
[execmodules] suite.addTest(new TestSuite(AttributeChangeNotificationFilterTestCase.class));
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/notification/NotificationSUITE.java:55: cannot resolve symbol
[execmodules] symbol : class NotificationBroadcasterSupportTestCase
[execmodules] location: class test.compliance.notification.NotificationSUITE
[execmodules] suite.addTest(new TestSuite(NotificationBroadcasterSupportTestCase.class));
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/compliance/openmbean/OpenMBeanSUITE.java:63: cannot resolve symbol
[execmodules] symbol : class OpenMBeanConstructorInfoSupportTestCase
[execmodules] location: class test.compliance.openmbean.OpenMBeanSUITE
[execmodules] suite.addTest(new TestSuite(OpenMBeanConstructorInfoSupportTestCase.class));
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/implementation/loading/LoaderRepositoryTEST.java:100: warning: javax.management.loading.DefaultLoaderRepository in javax.management.loading has been deprecated
[execmodules] DefaultLoaderRepository.loadClass(classes);
[execmodules] ^
[execmodules] /var/im/jboss/jboss-4.0.5.GA-src/jmx/src/main/test/implementation/notification/NotificationSUITE.java:54: cannot resolve symbol
[execmodules] symbol : class AsynchNotificationBroadcasterSupportTestCase
[execmodules] location: class test.implementation.notification.NotificationSUITE
[execmodules] suite.addTest(new TestSuite(AsynchNotificationBroadcasterSupportTestCase.class));
[execmodules] ^
[execmodules] 6 errors
[execmodules] 2 warnings
BUILD FAILED
/var/im/jboss/jboss-4.0.5.GA-src/tools/etc/buildmagic/buildmagic.ent:435: Compile failed; see the compiler error output for details.
Total time: 20 seconds
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220421#4220421
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220421
17 years, 1 month
UseJBossWebLoader True or False (which setting means isolated)
by Kashif Ali
Hi,
I have just setup a jboss 4.2.3 server and I have deployed 10 applications
all the applications are WAR files and all of them contain saxon.jar. When I
leave the value:
UseJBossWebLoader to its default to false.... however this causes
exceptions.
if I set this to true, everything seems happy?
reading the config
<!-- A flag indicating if the JBoss Loader should be used. This loader
uses a unified class loader as the class loader rather than the tomcat
specific class loader.
The default is false to ensure that wars have isolated class loading
for duplicate jars and jsp files.
-->
false
One would think that to have isolated you leave this value as is? However in
my experiance this is not the case. Can someone please confirm if I am wrong
or not?
If I am not the config file and the wiki documentation should be updated.
Just to note:
Jboss version 4.2.3:
file edited
/opt/jboss/server/test/deploy/jboss-web.deployer/META-INF/jboss-service.xml
17 years, 1 month
[JBoss jBPM] - Working with holidays
by desson
Hi all,
I am using the business calendar to calculate the time for a task occurs, actually I'm scheduling a job.This class reads jbpm.business.calendar.properties to know about the business hour and holidays. So, to add holidays I need open this file and edit it, I think it is boring and a common users can't do that..I would you like to know if there's a another way to do that?
Another question is about the absolute duetime.
For example: I create a job today (March 23) with the duration of 3 days. So the duedate is today + 3 (March 26). But let's suppose that I add a holiday (March 24), the duedate should be calculated again. I think JBPM doesn't know how to deal with this situation. Do you understand me? Any idea how to solve it?
thanks in advance
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220418#4220418
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220418
17 years, 1 month
[JBoss Messaging] - Question on understanding durable subsciber
by CarstenRudat
Hi all,
I have a question on duralbe subscriptions. I create subscription with the following code:
| TopicConnectionFactory tcf = ...
| TopicConnection conn = tcf.createTopicConnection(user, pw);
| Topic topic = (Topic) iniCtx.lookup(...);
| TopicSession session = conn.createTopicSession(false, TopicSession.AUTO_ACKNOWLEDGE);
| conn.start();
| TopicSubscriber recv = session.createDurableSubscriber(topic, suscrId);
|
If anything with my client fails and I cannot stop conn or session and I again try the above code, I will get an error (IllegalStateException "Cannot create a subscriber on the durable subscription since it already has subscriber(s)").
What could I do now? I tried to unsubscribe, but then, I get a second IllegalStateException "Cannot unsubscribe durable subscription <my subsciption id> since it has active subscribers" (JBM says, that there is an active subscriber... but it's not active, since my client crashed...). If I restart the JBoss Server everythink is ok.
I cannot find it in the JavaDoc/JEE Tutorial, so I wounder what I'm doing wrong.
Any advice?
Thank you,
Carsten
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220414#4220414
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220414
17 years, 1 month