Announcement

Collapse

Mirth Connect 4.1.0 Released!

Mirth Connect 4.1.0 is now available as an appliance update and on our GitHub page. Mirth Connect 4.1.0 includes new features such as new event log messages, additional fields to the Welcome to Mirth Connect screen, new information included in alerts as well as many smaller changes, updates, and improvements. This release also contains several improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

ERROR while deploying mirth.sar in Jboss3.2.7

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    ERROR while deploying mirth.sar in Jboss3.2.7

    Hi,

    I am trying to deploy mirth.sar(1.7.1) in Jboss3.2.7.
    The following error occurred while deploying:

    2008-07-14 16:19:51,234 DEBUG [org.jboss.mx.modelmbean.ModelMBeanInvoker] No persistence-manager descriptor found, null persistence will be used
    2008-07-14 16:19:51,250 DEBUG [org.jboss.system.ServiceCreator] About to create bean: com.webreach.mirth.server.mbeans:service=MirthServ ice with code: com.webreach.mirth.server.mbeans.MirthService
    2008-07-14 16:19:51,265 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled= true
    2008-07-14 16:19:51,265 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled= false
    2008-07-14 16:19:51,265 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNest ing=true
    2008-07-14 16:19:51,265 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/D:/jboss-3.2.7/server/default/deploy/mirth.sar/
    org.jboss.deployment.DeploymentException: Unexpected error during load of: com.webreach.mirth.server.mbeans.MirthService, msg=com/webreach/mirth/server/mbeans/MirthService (Unsupported major.minor version 49.0); - nested throwable: (java.lang.ClassNotFoundException: Unexpected error during load of: com.webreach.mirth.server.mbeans.MirthService, msg=com/webreach/mirth/server/mbeans/MirthService (Unsupported major.minor version 49.0))
    at org.jboss.system.ServiceConfigurator.install(Servi ceConfigurator.java:142)
    at org.jboss.system.ServiceController.install(Service Controller.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(R eflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(Ab stractMBeanInvoker.java:198)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyE xt.java:176)
    at $Proxy4.install(Unknown Source)
    at org.jboss.deployment.SARDeployer.create(SARDeploye r.java:204)
    at org.jboss.deployment.MainDeployer.create(MainDeplo yer.java:783)
    at org.jboss.deployment.MainDeployer.deploy(MainDeplo yer.java:640)
    at org.jboss.deployment.MainDeployer.deploy(MainDeplo yer.java:604)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(R eflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(Ab stractMBeanInvoker.java:198)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyE xt.java:176)
    at $Proxy8.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner. deploy(URLDeploymentScanner.java:304)
    at org.jboss.deployment.scanner.URLDeploymentScanner. scan(URLDeploymentScanner.java:478)
    at org.jboss.deployment.scanner.AbstractDeploymentSca nner$ScannerThread.doScan(AbstractDeploymentScanne r.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentSca nner.startService(AbstractDeploymentScanner.java:2 74)
    at org.jboss.system.ServiceMBeanSupport.jbossInternal Start(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternal Lifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(R eflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(Ab stractMBeanInvoker.java:198)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:473)
    at org.jboss.system.ServiceController$ServiceProxy.in voke(ServiceController.java:899)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceCo ntroller.java:415)
    at sun.reflect.GeneratedMethodAccessor5.invoke(Unknow n Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(R eflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(Ab stractMBeanInvoker.java:198)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyE xt.java:176)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer .java:251)
    at org.jboss.deployment.MainDeployer.start(MainDeploy er.java:829)
    at org.jboss.deployment.MainDeployer.deploy(MainDeplo yer.java:641)
    at org.jboss.deployment.MainDeployer.deploy(MainDeplo yer.java:604)
    at org.jboss.deployment.MainDeployer.deploy(MainDeplo yer.java:588)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(R eflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:62)
    at org.jboss.mx.server.Invocation.dispatch(Invocation .java:54)
    at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:82)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(Ab stractMBeanInvoker.java:198)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyE xt.java:176)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerI mpl.java:407)
    at org.jboss.system.server.ServerImpl.start(ServerImp l.java:311)
    at org.jboss.Main.boot(Main.java:191)
    at org.jboss.Main$1.run(Main.java:480)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: com.webreach.mirth.server.mbeans.MirthService, msg=com/webreach/mirth/server/mbeans/MirthService (Unsupported major.minor version 49.0)
    at org.jboss.mx.loading.UnifiedClassLoader3.loadClass Impl(UnifiedClassLoader3.java:229)
    at org.jboss.mx.loading.UnifiedClassLoader3.loadClass (UnifiedClassLoader3.java:136)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:2 35)
    at org.jboss.mx.server.MBeanServerImpl.instantiate(MB eanServerImpl.java:843)
    at org.jboss.mx.server.MBeanServerImpl.instantiate(MB eanServerImpl.java:290)
    at org.jboss.mx.server.MBeanServerImpl.createMBean(MB eanServerImpl.java:317)
    at org.jboss.system.ServiceCreator.install(ServiceCre ator.java:124)
    at org.jboss.system.ServiceConfigurator.internalInsta ll(ServiceConfigurator.java:152)
    at org.jboss.system.ServiceConfigurator.install(Servi ceConfigurator.java:117)
    ... 81 more

    But then I changed to JDK1.5 from JDk1.4.2_07 guessing that, this may be
    related to JAVA version and after using JDK1.5 error is gone. But another
    error occurred which user 'apalmero' already mentioned in his thread:

    http://www.mirthproject.org/index.ph...3&catid=2#3533

    Is it possible that mirth(1.7.1) can be deployed in JBoss version 3.2.7 ???
    How to resolve these issues. Any workaround ???


    Thanking in advance for any help.
    Regards,
    Raj.
    Tags: None
  • #2
    Re:ERROR while deploying mirth.sar in Jboss3.2.7

    This has nothing to do with Jboss. It's beacuse the jRE version JBoss is using.

    You need to change the JBOSS's JRE version to a 1.5

    Comment

    • #3
      Re:ERROR while deploying mirth.sar in Jboss3.2.7

      Please read the installation notes to make sure you are using JBoss for the right reasons. If you do have some good reason for not using the standalone version of Mirth, then you should know that we did not test it on versions prior to 4.2.0. We have heard of some problems when using it with previous versions, as well.
      Jacob Brauer
      Director, Software Development
      NextGen Healthcare

      sigpic

      Comment

      Previous template Next
      Working...
      X

      We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

      By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

      I Agree