Tamino - deadlocks

>-----Original Message-----
>From: [hidden email] [mailto:[hidden email]]
>Sent: 16 January 2006 11:14
>To: [hidden email]
>Subject: [ops-users] Tamino - deadlocks
>
>Hello,
>
>We have some strange deadlock exceptions when using our application with
>concurrent users accessing our OPS app parallely. One of the hints I found
>on a forum is to upgrade  the API to 4.2.1.7.
>I noticed that Orbeon is using some older compilation inside
>TaminoAPI4J.jar dating to 2003. Does someone have a newer compilation for
>Tamino 4.2.1.8 ?
>
>regards,
>Balazs

> Hello Ryan,
>
> Thanks for the tip. I actually have a Tamino installation with the SDK folder that I assume contains the right jar. I thought there was a special compilation of class files that  got installed with Orbeon. When I tried to install the TaminoAPI4J.jar from there I got this exception:
> -------------------------------------------------------------------------------
> java.lang.VerifyError: (class: com/softwareag/common/instrumentation/logging/Log4jLogger, method: isLoggable signature: (I)Z) Incompatible argument to function
> com.softwareag.common.instrumentation.logging.LoggerFactory.getLogger(Unknown Source)
> ...
> -------------------------------------------------------------------------------
> Do you know how to resolve this ?
>
>  

> regards,
> Balazs
>
>  
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  

> Hello Dave,
>
> I would very much appreciate to hear your experiences with Tamino V4.4.
>
> regards,
> Balazs
>
>  
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  

> [hidden email] wrote:
>> Hello Ryan,
>>
>> Thanks for the tip. I actually have a Tamino installation with the SDK
>> folder that I assume contains the right jar. I thought there was a
>> special compilation of class files that  got installed with Orbeon.
>> When I tried to install the TaminoAPI4J.jar from there I got this
>> exception:
>> -------------------------------------------------------------------------------
>>
>> java.lang.VerifyError: (class:
>> com/softwareag/common/instrumentation/logging/Log4jLogger, method:
>> isLoggable signature: (I)Z) Incompatible argument to function
>>     com.softwareag.common.instrumentation.logging.LoggerFactory.getLogger(Unknown
>> Source)
>> ...
>> -------------------------------------------------------------------------------
>>
>> Do you know how to resolve this ?
>>
>>  
>
> Balazs,
>
> Strangely we seem to be having exactly the same problem as you - we are
> trying to upgrade to tamino 4.4 and are finding the same incompatibility
> problems.   It looks like Tamino use a newer version of log4j than
> Orbeon do or something.
> Alex / Erik, any ideas on how we can resolve this - we want to be able
> to take advantage of new feature in the Tamino API ...
>
> Dave
>
>> regards,
>> Balazs
>>
>>  
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>  
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

> -Erik
>
> David Sinclair wrote:
>> [hidden email] wrote:
>>> Hello Ryan,
>>>
>>> Thanks for the tip. I actually have a Tamino installation with the
>>> SDK folder that I assume contains the right jar. I thought there was
>>> a special compilation of class files that  got installed with
>>> Orbeon. When I tried to install the TaminoAPI4J.jar from there I got
>>> this exception:
>>> -------------------------------------------------------------------------------
>>>
>>> java.lang.VerifyError: (class:
>>> com/softwareag/common/instrumentation/logging/Log4jLogger, method:
>>> isLoggable signature: (I)Z) Incompatible argument to function
>>>    
>>> com.softwareag.common.instrumentation.logging.LoggerFactory.getLogger(Unknown
>>> Source)
>>> ...
>>> -------------------------------------------------------------------------------
>>>
>>> Do you know how to resolve this ?
>>>
>>>  
>>
>> Balazs,
>>
>> Strangely we seem to be having exactly the same problem as you - we
>> are trying to upgrade to tamino 4.4 and are finding the same
>> incompatibility problems.   It looks like Tamino use a newer version
>> of log4j than Orbeon do or something.
>> Alex / Erik, any ideas on how we can resolve this - we want to be
>> able to take advantage of new feature in the Tamino API ...
>>
>> Dave
>>
>>> regards,
>>> Balazs
>>>
>>>  
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>  
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  

> -Erik
>
> David Sinclair wrote:
>> [hidden email] wrote:
>>> Hello Ryan,
>>>
>>> Thanks for the tip. I actually have a Tamino installation with the
>>> SDK folder that I assume contains the right jar. I thought there was
>>> a special compilation of class files that  got installed with
>>> Orbeon. When I tried to install the TaminoAPI4J.jar from there I got
>>> this exception:
>>>

>>>
>>> Do you know how to resolve this ?
>>>
>>>  
>>
>> Balazs,
>>
>> Strangely we seem to be having exactly the same problem as you - we
>> are trying to upgrade to tamino 4.4 and are finding the same
>> incompatibility problems.   It looks like Tamino use a newer version
>> of log4j than Orbeon do or something.
>> Alex / Erik, any ideas on how we can resolve this - we want to be
>> able to take advantage of new feature in the Tamino API ...
>>
>> Dave
>>
>>> regards,
>>> Balazs
>>>
>>>  
>>> ------------------------------------------------------------------------

>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>  
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email]

> cheers
> Doug
>
>
> Doug Young
> Software Engineer
>  
> Teleflex IT
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotland
> EH54 7DP
> +44 (0) 1506 407107
>
> -----Original Message-----
> From: David Sinclair [mailto:[hidden email]]
> Sent: 17 January 2006 13:54
> To: [hidden email]
> Subject: Re: [ops-users] Tamino - deadlocks
>
> Erik Bruchez wrote:
>  
>> It does looks like a log4j compability issue. The name
>> "instrumentation" in the Tamino stack trace seems to indicate that
>> Tamino is using reflection to access some log4j method, and fails.
>>
>> First thing to try is to locate the different log4j jars, and try to
>> keep only one.
>>
>>    
>
> Erik / Balazs,
>
> I just replaced the orbeon log4j jar with the one distributed with
> tamino and this seems to have fixed the problem...
>
> Thanks,
>
> Dave
>
>
>  
>> -Erik
>>
>> David Sinclair wrote:
>>    
>>> [hidden email] wrote:
>>>      
>>>> Hello Ryan,
>>>>
>>>> Thanks for the tip. I actually have a Tamino installation with the
>>>> SDK folder that I assume contains the right jar. I thought there was
>>>> a special compilation of class files that  got installed with
>>>> Orbeon. When I tried to install the TaminoAPI4J.jar from there I got
>>>> this exception:
>>>>
>>>>        
> ----------------------------------------------------------------------------
> ---
>  
>>>> java.lang.VerifyError: (class:
>>>> com/softwareag/common/instrumentation/logging/Log4jLogger, method:
>>>> isLoggable signature: (I)Z) Incompatible argument to function
>>>>    
>>>>
>>>>        
> com.softwareag.common.instrumentation.logging.LoggerFactory.getLogger(Unknow
> n
>  
>>>> Source)
>>>> ...
>>>>
>>>>        
> ----------------------------------------------------------------------------
> ---
>  
>>>> Do you know how to resolve this ?
>>>>
>>>>  
>>>>        
>>> Balazs,
>>>
>>> Strangely we seem to be having exactly the same problem as you - we
>>> are trying to upgrade to tamino 4.4 and are finding the same
>>> incompatibility problems.   It looks like Tamino use a newer version
>>> of log4j than Orbeon do or something.
>>> Alex / Erik, any ideas on how we can resolve this - we want to be
>>> able to take advantage of new feature in the Tamino API ...
>>>
>>> Dave
>>>
>>>      
>>>> regards,
>>>> Balazs
>>>>
>>>>  
>>>> ------------------------------------------------------------------------
>>>>        
>
>  
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>>  
>>>>        
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>      
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>>    
> mailing list.
>  
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>  
>>    
>
>
>
>
>  
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  

>-----Original Message-----
>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>Sent: 18 January 2006 10:42
>To: [hidden email]
>Subject: Re: [ops-users] Tamino - deadlocks
>
>Doug Young wrote:
>> Hi,
>>   Replacing the log4j jar solves the access problem, but now no events
>> appear in the logging events window. I can still get them in the console
>and
>> appended to a file but not to the logging events window.
>>
>> Alex/Eric Is there an incompatibility between the OPSMonitor code and the
>> (newer ?) version of log4j that has been shipped with Tamino ?
>
>It looks like the latest stable version of log4j is 1.2.x. and we are
>using a version 1.3 alpha. According to:
>
>   http://logging.apache.org/log4j/docs/download.html
>
>"The next major release of log4j will be version 1.3. It will contain
>many new features and changes, and if you have written custom code, it
>may need to be modified to work with it. Please see the document
>entitled preparing for log4j 1.3 for a more detailed discussion."
>
>So it is quite possible that there are incompatibilities.
>
>-Erik

> Hi all,
>         We have solved the Log4J problems, we are now using version 1.2.8
> rather than 1.3 alpha. We had to change the OPS Monitor appender in
> log4j.xml. We changed the locationInfo param to false and all the messages
> come through. Any ideas on how this affects OPS? Or what this param does?
>
> Ryan
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7  01506 407 108
>
> >-----Original Message-----
> >From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> >Sent: 18 January 2006 10:42
> >To: [hidden email]
> >Subject: Re: [ops-users] Tamino - deadlocks
> >
> >Doug Young wrote:
> >> Hi,
> >>   Replacing the log4j jar solves the access problem, but now no events
> >> appear in the logging events window. I can still get them in the console
> >and
> >> appended to a file but not to the logging events window.
> >>
> >> Alex/Eric Is there an incompatibility between the OPSMonitor code and the
> >> (newer ?) version of log4j that has been shipped with Tamino ?
> >
> >It looks like the latest stable version of log4j is 1.2.x. and we are
> >using a version 1.3 alpha. According to:
> >
> >   http://logging.apache.org/log4j/docs/download.html
> >
> >"The next major release of log4j will be version 1.3. It will contain
> >many new features and changes, and if you have written custom code, it
> >may need to be modified to work with it. Please see the document
> >entitled preparing for log4j 1.3 for a more detailed discussion."
> >
> >So it is quite possible that there are incompatibilities.
> >
> >-Erik
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>